User-agent: Mediapartners-Google Disallow: User-agent: * Disallow: /search Allow: / Sitemap: http://nox4developper.blogspot.com/sitemap.xml Nox 4 developper: partition
Affichage des articles dont le libellé est partition. Afficher tous les articles
Affichage des articles dont le libellé est partition. Afficher tous les articles

HTC One M8, Sensor Hub partition dead topic






Hello everyone,

since 2 days im trying to restore my M8 too stock. I tried all ways, via RUU, nandroid backups etc. I always flashed the firmwares, made sure I did everything the way it is supposed to be.
But every flash ends with the same ending: Either the phone wont boot into android at all, or all sensors and the camera wont work.
When i open the camera app, there is a black screen displayed for like 4 secs, and then im straight back at the home screen. I can see the shutter button, but nothing happens when i press it.
Furthermore, no sensor works. Orientation is dead, proximity, light, everything. There is also a 2 sec delay between pressing the power button and the screen coming to life.

After doing everything again step by step i discovered something, that might cause everything. While flashing the firmware, the CMD gives me following lines: (cut-out)

(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6

(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=7

(bootloader) start image[sbl1-4] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-4,0
(bootloader) [RUU]UZ,sbl1-4,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=8

(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) ..... Bypassed
(bootloader) current_image_number=9

(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,99
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) current_image_number=10

as you can see, the RUU for the sensor hub isnt flashed how it should be. The CMD even stops for like 5 secs after displaying


(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100

After 5 secs, it continues with the line


(bootloader) .... bypassed


Is there some way to get the sensor hub working again? Im rly clueless and would be very happy if someone could help me!

Thank You!






[Howto][Android-x86] Mount Internal Windows Partition (NTFS) in Android-x86 topic






Mount Internal Windows Partition (NTFS) in Android-x86.

Android-x86 project is one of the new and exciting offshoot of Android platform solely developed by the community. Our Android community has contributed very heavily for the development of Android as one of the most loved platform for both users and the development community as a whole. Custom ROMs such as CyanogenMod, OmniROM, SlimRom, AOKP, Paranoid Android and many more community developed ROM's rock our beloved devices, including latest flagships to aged Legends such as HTC HD2, Motorola Defy(+). One such community developed Android ROM is the Android-x86 Project.

Android-x86 project aims porting the android experience as whole to the x86 architecture platform. This includes our laptops, desktops and x86 based tablets. Although android is a mobile platform specifically developed for phones, tablets and newly introduced wearable devices such as smart watches and Google Glass eyewear, google has not introduced the android as an operating system into the desktop-laptop segment. Google is sticking with its Chrome OS for desktops and is now trying to introduce android app to the Chrome OS. Android-x86 project patches that gap for us.

Android-x86 is like an elixer for our old desktops and laptops wiith lower capability processors and rams, such as pentium and atoms by introducing a modern OS with a lower requirement. It gives those devices a new life. But it is also not perfect yet and has many drawbacks. One such drawback is that it can't mount the internal NTFS partitions of the HDD, in case of the Multibooting Android-x86 with Windows Operating Systems. Many has tried it before but failed. Recently I came upon a chinese website which depicted a process of mounting internal ntfs partitions using a library named mount_nfsd_fuse.

Steps :
1. Download the mount_nfsd_fuse file from the download link provided below or here
2. Place the the downloaded file in the /system/xbin/ folder using a root enabled file manaager, eg. ES File Explorer, Root Explorer and and change to approriate permission.
3. Open Terminal ( If no terminal app installed, download one from Google Play), and obtain Su permission.
4. Mount the NTFS partitions using the code for example :
mkdir /storage/D
mount_nfsd_fuse /dev/block/sda2 /storage/D
format : mount_nfsd_fuse /dev/block/(partition) /(mount point)
5. (Optional) You can automate the process of mounting on boot by adding these lines to the /etc/init.sh file.
6. You can make a Windows style My Computer Icon using ES explorer widget pointing to the mounting folder such as in my example /Storage use it as a my computer alternative for android.

NOTE : All internal HDD partitions are stored at /dev/block/ folder. And so far I have failed mounting C drive , sda1, and sda10 partitions. Feel free to poke around.
Disclaimer : I'm note the developer of this tool and i take no responsibility for any damages caused.

Download : http://www.jemshi101.tk/tools/androi...ount_nfsd_fuse

Ref : http://tieba.baidu.com/p/2094586835






Change Partition Size? topic






Hi,

I have a cheap'ish tablet from Amazon that didn't come with full root access (superuser didn't work), all I had to do was install SuperSU and update the su binary and then both supersu and superuser work.

Now that I have root, surely there must be someway I can change my partition sizes?

The "Internal Storage" says that it's 1GB which is nearly full, 800mb of it is taken up by "Apps and Media" even though I've moved as many apps as I can to the "SDCard" which is 11GB.... however I believe both the Internal Storage & SDCard are the same storage hardware because there is no sdcard visible anywhere.

How can I check the storage out and if possible how can I change the partition sizes?






[Q&A] [MOD] [GUIDE] [250214] Pit Files for creating a larger partition for app data topic






Q&A for [MOD] [GUIDE] [250214] Pit Files for creating a larger partition for app data

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [MOD] [GUIDE] [250214] Pit Files for creating a larger partition for app data. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)






[List] Partition List - LG G Watch topic






Hi,

i've checked out the partition list of my watch, using adb and parted.


Code:



D:\Handy\LG_G_Watch\ota>cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.

D:\Handy\LG_G_Watch\ota>adb shell cat /proc/partitions
major minor  #blocks  name

 179        0    3817472 mmcblk0
 179        1      1024 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3        512 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6      1024 mmcblk0p6
 179        7        512 mmcblk0p7
 179        8        512 mmcblk0p8
 179        9        512 mmcblk0p9
 179      10      2048 mmcblk0p10
 179      11        512 mmcblk0p11
 179      12      16384 mmcblk0p12
 179      13      16384 mmcblk0p13
 179      14      22528 mmcblk0p14
 179      15      22528 mmcblk0p15
 179      16      22528 mmcblk0p16
 179      17        512 mmcblk0p17
 179      18        512 mmcblk0p18
 179      19    262144 mmcblk0p19
 179      20    262144 mmcblk0p20
 179      21    3182592 mmcblk0p21
 179      22        495 mmcblk0p22
 179      32      4096 mmcblk0rpmb

D:\Handy\LG_G_Watch\ota>
root@dory:/ # ls /dev/block/platform/msm_sdcc.1/by-name
ls /dev/block/platform/msm_sdcc.1/by-name
DDR
aboot
abootb
boot
cache
grow
imgdata
laf
metadata
misc
persist
recovery
rpm
rpmb
sbl1
sbl1b
sdi
ssd
system
tz
tzb
userdata

Model: MMC H4G1d♦ (sd/mmc)
Disk /dev/block/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start  End    Size    File system  Name      Flags
 1      524kB  1573kB  1049kB              sbl1
 2      1573kB  2097kB  524kB                rpm
 3      2097kB  2621kB  524kB                tz
 4      2621kB  3146kB  524kB                sdi
 5      3146kB  3670kB  524kB                aboot
 6      3670kB  4719kB  1049kB              sbl1b
 7      4719kB  5243kB  524kB                rpmb
 8      5243kB  5767kB  524kB                tzb
 9      5767kB  6291kB  524kB                abootb
10      6291kB  8389kB  2097kB              imgdata
11      8389kB  8913kB  524kB                metadata
12      8913kB  25.7MB  16.8MB              misc
13      25.7MB  42.5MB  16.8MB  ext4        persist
14      42.5MB  65.5MB  23.1MB              laf
15      65.5MB  88.6MB  23.1MB              boot
16      88.6MB  112MB  23.1MB              recovery
17      112MB  112MB  524kB                ssd
18      112MB  113MB  524kB                DDR
19      113MB  381MB  268MB  ext4        system
20      381MB  650MB  268MB  ext4        cache
21      650MB  3909MB  3259MB  ext4        userdata
22      3909MB  3909MB  507kB                grow

(parted)


regards

starbase64






galaxy s5 partition topic






ive lost the partitions on my s5.. all it has is safestrap3.71 can anyone help me with the partition layout or how to recover






Backing up TA partition instructions for Sony Xperia M2 Aqua topic






Hello. Me and the guys from 4pda.ru invented and embodied the bold idea.
In order to make a backup of TA, you just need to flash Android 4.3 for D2303 and get root access through Towelroot and save TA through known methods
Then you can flash your stock. And then open the boot..

Original post 4pda.ru






[APP] [4.1+] DDTools - Partition Flash/Backup topic






DDTools is an application to handle your partitions using Unix binary "dd", There are some applications
capable of such a feat, but not all devices are compatible, then the DDTools slap this hole.

With DDTools you can flash and backup a kernel, recovery, modem, bootlogo, efs and other partitions easily,
You just need to know the partition layout of your device.

Features
  • Flash and backup partitions.

  • Check MD5 of your partitions.

  • Generate MD5 for your backups.

  • If you are too lazy to type the full path of the partition,
    just type the block number that DDTools does the rest!

  • Get all output processes.

  • Device power menu and informations.

  • Free, No Ads.


Requirements
  • Any device running Android 4.1.2+

  • Device with root and busybox.

  • Partition layout of your device.

  • Fingers, For without fingers will be a little tricky. :good:


Credits
Thank you and have a nice day! Get it on DOWNLOAD page.

XDA:DevDB Information
DDTools, App for all devices (see above for details)

Contributors
ferreirawax

Version Information
Status: Testing

Created 2014-12-11
Last Updated 2014-12-11






[Q] /data partition unable to wipe topic






Hey guys,

I had previously encrypted my phone with the inbuilt android encryption, but it just didn't work (the PIN wasn't my password)
I tried to factory reset it but it didn't work either, from both fastboot or recovery.

So I reflashed my entire system from fastboot (which worked perfectly). Now I want to install the unofficial cm12 zip, but I can't erase userdata from my phone at all.. Either through fastboot or recovery, and I'm locked to the GPe image I am using currently.

The recovery error I get when trying to delete my data partition is:

Code:


-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
E:unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.


I have no idea what to do help please?






Data partition size? Best setting? HDX7 [noob] topic






Dear community,

I have the new Kindle Fire HDX7 (32GB). I have rooted it and installed Safetrap 3.75. My ultimate goal is to install the Nexus-Rom. Therefore I have already backed up the Stock-Rom with Safetrap. I think the next step is to create Rom-Slot-1. I'm stuck here as I have no idea which values to choose. I dont need the Stock-Rom (FireOS). I'd like to have my Nexus Rom as the only Rom I want to work with. I have read that it would be better to keep the Stock-Rom on the device nonetheless in case of an emergency. Though I have saved the backup on my PC as well I would leave it on the device too.
When using my kindle with the Nexus-Rom I'd like to use apps, games (especially Point-and-Click Adventure such as Brokens Sword (700MB), Broken Age, Monkey Island etc.) and surf the internet. I'd store some music as well if possible.

I have read that most people say: choose the values to your liking/depends on what you want to do. I tried to explain what I would like to do but I really don't know what values would fit my purpose best. I'd assume that I take the highest values as I want the Rom-Slot to be my only working-station? I've read so many threads now but I still haven't been able to figure that out. :(

My options are:

ROM-SLOT-1:
  • System partition size: 1248 MB (value cant be changed)

  • Data partition size: I can chooose a value between 1.000 MB and 16.000 MB

  • Cache partition size: I can choose a value between 300 MB und 1.000 MB

  • Selected Space: varies depending on the

  • Free Space: 23366 MB (value cant be changed)


STOCK-ROM:
  • System partition size: 1230 MB (193 MB Free)

  • Data partition size: 26901 MB (23367 MB Free)

  • Cache partition size: 1009 MB (990 MB Free)


I'm really lost here. Any kind of advice is really welcome. Thank you. :o