Hi.
Can anyone enlighten me on the file system on the Nexus 7. Is there a single partition or several ? I want to dd the _whole_ contents of the flash chip to a usb-attached SD card.
I have the 16GB version just upgraded to 4.1.2 but i haven't been successfull with the rooting, so i have not been able to look at the data organization.
I guess the clockworkmod can backup the ROM, but does it backup all the files/partitions on the flash, so the bootloader is a part of the file?
I am looking into removing the eMMC flash chip and replacing with a bigger one, or even an SD card. I have an BGA rework machine, so it's not a problem hardware-wise.
Anyone with knowledge on this ?
// Per.
N7 has multiple partitions. CWM backups do not include the bootloader.
Here's a list of positions:
Ref: http://forum.xda-developers.com/showthread.php?t=1739119
Note: Command to list partitions and their name (size came from /proc/partitions):
ls -l /dev/block/platform/sdhci-tegra.3/by-name/
Partition Size (1k blks) Name Description
mmcblk0p1 12288 SOS recovery
mmcblk0p2 8192 LNX boot.img
mmcblk0p3 665600 APP system
mmcblk0p4 453632 CAC cache
mmcblk0p5 512 MSC Misc (bootloader commands and other misc stuff )
mmcblk0p6 10240 USP Staging
mmcblk0p7 5120 PER usually a fat partition containing sensor calibration etc. - per device provisioned.
mmcblk0p8 512 MDA Unknown
mmcblk0p9 14103552 UDA data (user data area)
Sent from my Nexus 7
Hi everyone
After days of research to find the solution for my problem I have to finally admit that I can find it by myself. Therefore that’s my first post. Here’s the problem:
I got a used Nexus 10 for a bargain. Problem it was stuck in a lollipop bootloop. I thought that won’t be that much of a problem…. Wrong!
Lollipop: I tried serveral suggestion to fix the bootloop
- installed TWRP 2.8.7.0, fastboot and adb working fine,
- Tried manual flashing as suggested in the forum (like: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008)
- Flashing with NRT 2.1.4 results in bootloop, even in bootloop mode
- Tried to stock rom (5.0.2, 5.1.1, CM13, omni6.0.1, OTA from 4.4.4) all the same…
- waited for around 30min each time
- did several wipes and reboots
So I tried Kitkat (Stock 4.4.4 and CM11 + SU). And there started getting strange…
- worked immediately, but system can’t find sdcard storage (eg. gallery says ‘no external storage available’)
- in TWRP can’t mount sdcard
- in TWRP can’t partitioning sd card (E:unable to locate device to partion)
- in TWRP when wiping internal storage sd card cant be wiped (same as above)
- in TWRP internal storage cant be repair or file system cant be changed (invalid partition selection)
- in TWRP I can access to internal storage in Windows (copy zip), in Android Windows recognizes Nexus but not as unknown storage
- tried all methods (restorecon –FR) in this thread http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749
- same problems here, but he found a solution: http://forum.xda-developers.com/nexus-10/help/storage-problems-t3170098/post62137822#post62137822
Partionion table shows following:
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB efs
2 25.2MB 33.6MB 8389kB param
3 33.6MB 50.3MB 16.8MB boot
4 50.3MB 83.8MB 33.5MB recovery
5 83.8MB 83.9MB 65.5kB metadata
6 83.9MB 88.1MB 4194kB misc
7 88.1MB 642MB 554MB ext4 cache
8 642MB 1481MB 839MB ext4 system
9 1481MB 15.8GB 14.3GB ext4 userdata
any ideas???
thanks in advance!
still no solution...
has anyone an idea?
Code:
mmcblk0p1 ---- modem ---------- [Firmware][Radio]
mmcblk0p2 ---- fsc ------------ []
mmcblk0p3 ---- ssd ------------ []
mmcblk0p4 ---- sbl1 ----------- [Firmware][]
mmcblk0p5 ---- sbl1bak -------- [Firmware][Backup]
mmcblk0p6 ---- rpm ------------ [Firmware][]
mmcblk0p7 ---- rpmbak --------- [Firmware][Backup]
mmcblk0p8 ---- tz ------------- [Firmware][]
mmcblk0p9 ---- tzbak ---------- [Firmware][Backup]
mmcblk0p10 --- hyp ------------ [Firmware][]
mmcblk0p11 --- hypbak --------- [Firmware][Backup]
mmcblk0p12 --- dsp ------------ [Firmware][]
mmcblk0p13 --- modemst1 ------- [EFS]
mmcblk0p14 --- modemst2 ------- [EFS]
mmcblk0p15 --- DDR ------------ []
mmcblk0p16 --- fsg ------------ [EFS][Backup]
mmcblk0p17 --- sec ------------ []
mmcblk0p18 --- splash --------- [SplashScreen]
mmcblk0p19 --- aboot ---------- [Bootloader]
mmcblk0p20 --- abootbak ------- [Bootloader][Backup]
mmcblk0p21 --- boot ----------- [Kernel]
mmcblk0p22 --- recovery ------- [Recovery]
mmcblk0p23 --- devinfo -------- [UnlockToken]
mmcblk0p24 --- system --------- [System]
mmcblk0p25 --- cache ---------- [Cache]
mmcblk0p26 --- persist -------- [Persist][Sensors]
mmcblk0p27 --- misc ----------- []
mmcblk0p28 --- keystore ------- []
mmcblk0p29 --- config --------- []
mmcblk0p30 --- oem ------------ []
mmcblk0p31 --- limits --------- []
mmcblk0p32 --- mota ----------- []
mmcblk0p33 --- devcfg --------- []
mmcblk0p34 --- dip ------------ []
mmcblk0p35 --- mdtp ----------- [Firmware][]
mmcblk0p36 --- cust ----------- [Cust][Bloatware]
mmcblk0p37 --- syscfg --------- []
mmcblk0p38 --- mcfg ----------- []
mmcblk0p39 --- cmnlib --------- [Firmware][]
mmcblk0p40 --- keymaster ------ [Firmware][Backup]
mmcblk0p41 --- cmnlibbak ------ [Firmware][]
mmcblk0p42 --- keymasterbak --- [Firmware][Backup]
mmcblk0p43 --- apdp ----------- []
mmcblk0p44 --- msadp ---------- []
mmcblk0p45 --- dpo ------------ []
mmcblk0p46 --- userdata ------- [Userdata]
Partition Layout
[Firmware] - These partition contains firmware files. These partition are updated when you flash a new ROM.
[Backup] - These are backup partitions which store backup files of the original partition. User can use these partitions in case the original partitions are messed up. These partition are also updated when you flash a new ROM.
[UnlockToken] - This is the partition where the unlock state of the bootloader is stored. This partition is updated when you use mi unlock tool to unlock the bootloader. This partition changes with the change of the bootloader. If the bootloader is changed, this partition must be recreated using the mi unlock tool.
[Persist] - This partition contains all the sensors calibration, without this partition no sensor will be displayed. Not even the rotation sensor will work. This partition does not effect GPS, WiFi or Bluetooth.
[Cust] - This partition contains some more bloatware apps distributed by Xiaomi.
[EFS] - Now this is the most important partition. This partition contains all the unique identification of your devices, like your IMEI, Mac address, Bluetooth address and some other stuff. This partition is very complex and updates on every flashing. So it is mandatory to create a backup of this partition.
[ ] - These partitions are unknown and are created automatically during first boot. Erasing these partitions seems to do nothing.
reserve 1
reserve 2
Can i simply restore devinfo after flashing a new miui rom which relock bl or have to restore emmcappsboot.mbn aka aboot to escape bootloop on rebooting .pls tell me what make a phone bootloop while i flash multirom which locks bl or downgrade miui or flash official miui rom first time over other roms .i have to umlick it through fastboot mode by mi unlock.how can i evade this.thanks
Edit:- what is this state ,starting phone after flashing miui rom and logo blink for a second and then red led start blinking and screen is off,and on connecting pc it is showed as qhusb bulk like something under device manager and can boot into fastboot mode from where i can unlock with mi unlock then every thing go well
Camlin3 said:
Can i simply restore devinfo after flashing a new miui rom which relock bl or have to restore emmcappsboot.mbn aka aboot to escape bootloop on rebooting .pls tell me what make a phone bootloop while i flash multirom which locks bl or downgrade miui or flash official miui rom first time over other roms .i have to umlick it through fastboot mode by mi unlock.how can i evade this.thanks
Edit:- what is this state ,starting phone after flashing miui rom and logo blink for a second and then red led start blinking and screen is off,and on connecting pc it is showed as qhusb bulk like something under device manager and can boot into fastboot mode from where i can unlock with mi unlock then every thing go well
Click to expand...
Click to collapse
Restoring devinfo should solve the problem.
Tnx
Hi were the download link?
Great info. Many thanks
UmarAbid3DArtist said:
Hi were the download link?
Click to expand...
Click to collapse
What download links?
For the Partition Layout program that can back up and restore.
I am unsture on how to do this.
BlueJeans said:
What download links?
Click to expand...
Click to collapse
UmarAbid3DArtist said:
For the Partition Layout program that can back up and restore.
I am unsture on how to do this.
Click to expand...
Click to collapse
You can backup and restore partitions using TWRP recovery (ZCX, Alka, cofface). All these recoveries can backup every partition.
Good morning.
How to flash all partitions?
Do i need to use qfil and a qfil rom?
I wiped everything trying to fix a weir error related to play services, after every fresh installation it said "google play services has stopped" i have the qcn file backup.
I have the kate variant, locked bootloader.
Thanks.
avercros said:
Good morning.
How to flash all partitions?
Do i need to use qfil and a qfil rom?
I wiped everything trying to fix a weir error related to play services, after every fresh installation it said "google play services has stopped" i have the qcn file backup.
I have the kate variant, locked bootloader.
Thanks.
Click to expand...
Click to collapse
Use the miflash tool. It have all the partitions important to your device. Edit the xml file to add the remaining files to the flash procedure. Use edl mode for full functionality.
Archit9169 said:
Use the miflash tool. It have all the partitions important to your device. Edit the xml file to add the remaining files to the flash procedure. Use edl mode for full functionality.
Click to expand...
Click to collapse
I flashed a rom with miflash in edl mode using clear all option, it's booting for about 2 hours :s.
I think is dead.
Which lines?
Thanks for your time.
avercros said:
I flashed a rom with miflash in edl mode using clear all option, it's booting for about 2 hours :s.
I think is dead.
Which lines?
Thanks for your time.
Click to expand...
Click to collapse
Its not dead. Wait for a while longer. Or better yet unlock the bootloader and reflash the cust partition. Just check the xml file and you will understand how to edit it. Like add config.bin in the file name pertaining to config partition. Add all the file given in the folder.
Archit9169 said:
Its not dead. Wait for a while longer. Or better yet unlock the bootloader and reflash the cust partition. Just check the xml file and you will understand how to edit it. Like add config.bin in the file name pertaining to config partition. Add all the file given in the folder.
Click to expand...
Click to collapse
Thank you, i tried with that method but the result was the same.
EDIT:
Can you help me or guide me in this? i can't use my phone and at this moment i can't afford a new one.
Thanks.
Archit9169 said:
Code:
mmcblk0p1 ---- modem ---------- [Firmware][Radio]
mmcblk0p2 ---- fsc ------------ []
mmcblk0p3 ---- ssd ------------ []
mmcblk0p4 ---- sbl1 ----------- [Firmware][]
mmcblk0p5 ---- sbl1bak -------- [Firmware][Backup]
mmcblk0p6 ---- rpm ------------ [Firmware][]
mmcblk0p7 ---- rpmbak --------- [Firmware][Backup]
mmcblk0p8 ---- tz ------------- [Firmware][]
mmcblk0p9 ---- tzbak ---------- [Firmware][Backup]
mmcblk0p10 --- hyp ------------ [Firmware][]
mmcblk0p11 --- hypbak --------- [Firmware][Backup]
mmcblk0p12 --- dsp ------------ [Firmware][]
mmcblk0p13 --- modemst1 ------- [EFS]
mmcblk0p14 --- modemst2 ------- [EFS]
mmcblk0p15 --- DDR ------------ []
mmcblk0p16 --- fsg ------------ [EFS][Backup]
mmcblk0p17 --- sec ------------ []
mmcblk0p18 --- splash --------- [SplashScreen]
mmcblk0p19 --- aboot ---------- [Bootloader]
mmcblk0p20 --- abootbak ------- [Bootloader][Backup]
mmcblk0p21 --- boot ----------- [Kernel]
mmcblk0p22 --- recovery ------- [Recovery]
mmcblk0p23 --- devinfo -------- [UnlockToken]
mmcblk0p24 --- system --------- [System]
mmcblk0p25 --- cache ---------- [Cache]
mmcblk0p26 --- persist -------- [Persist][Sensors]
mmcblk0p27 --- misc ----------- []
mmcblk0p28 --- keystore ------- []
mmcblk0p29 --- config --------- []
mmcblk0p30 --- oem ------------ []
mmcblk0p31 --- limits --------- []
mmcblk0p32 --- mota ----------- []
mmcblk0p33 --- devcfg --------- []
mmcblk0p34 --- dip ------------ []
mmcblk0p35 --- mdtp ----------- [Firmware][]
mmcblk0p36 --- cust ----------- [Cust][Bloatware]
mmcblk0p37 --- syscfg --------- []
mmcblk0p38 --- mcfg ----------- []
mmcblk0p39 --- cmnlib --------- [Firmware][]
mmcblk0p40 --- keymaster ------ [Firmware][Backup]
mmcblk0p41 --- cmnlibbak ------ [Firmware][]
mmcblk0p42 --- keymasterbak --- [Firmware][Backup]
mmcblk0p43 --- apdp ----------- []
mmcblk0p44 --- msadp ---------- []
mmcblk0p45 --- dpo ------------ []
mmcblk0p46 --- userdata ------- [Userdata]
Click to expand...
Click to collapse
Hey,
Can you tell which partition is associated with WIFI,BT and Radio, and how can i know if that partition is corrupted? there is a way to test it?
I've the "no wifi" problem with the mac 02:00:00... and nothing results so maybe its something missing,
i've noticed when we flash through Miflash even with flash_all.bat selected some things aren't flashed and i wanna flash all so i can descart software problem... for example ("dummy.img" ; "mdtp.img"; "misc.img" and others...)
i've noticed that everytime i reboot the phone it appears the Mi logo and the three blinking dots then appears a bar, "it seems that the phone is trying to repair something" then he enters the SO but no wifi... i left the attach files so you can see what im talking about.
Do you have any idea what can be wrong?
hed190 said:
Hey,
Can you tell which partition is associated with WIFI,BT and Radio, and how can i know if that partition is corrupted? there is a way to test it?
I've the "no wifi" problem with the mac 02:00:00... and nothing results so maybe its something missing,
i've noticed when we flash through Miflash even with flash_all.bat selected some things aren't flashed and i wanna flash all so i can descart software problem... for example ("dummy.img" ; "mdtp.img"; "misc.img" and others...)
i've noticed that everytime i reboot the phone it appears the Mi logo and the three blinking dots then appears a bar, "it seems that the phone is trying to repair something" then he enters the SO but no wifi... i left the attach files so you can see what im talking about.
Do you have any idea what can be wrong?
Click to expand...
Click to collapse
Modemst1 modemst2 and fsg are related to those.
In images folder when you download fastboot rom, there is a file which contains all the partition info and images that are to be flashed in the phone. The file is in xml format and very easy to modify. Just modify that file, that is add the name of the image respective to its partition and flash the rom using edl mode.
Archit9169 said:
Modemst1 modemst2 and fsg are related to those.
In images folder when you download fastboot rom, there is a file which contains all the partition info and images that are to be flashed in the phone. The file is in xml format and very easy to modify. Just modify that file, that is add the name of the image respective to its partition and flash the rom using edl mode.
Click to expand...
Click to collapse
I remember a thread created by you with the way to flash those and i did but nothing happened...
there is a test or log to see if my WIFI IC has problems?
Hi all,
I have downloaded the latest Oppo ROM straight from their website, the latest SPFlash Tool and followed numerous guides.
But when I select the scatter file I keep getting an error that the scatter file is the incorrect scatter file format.
I've seen guides about how to edit the scatter file, but my file format looks nothing like the examples where a simple edit will fix it.
Heres what the file looks like:
preloader 0x0
pgpt 0x0
recovery 0x8000
para 0x1008000
reserve1 0x1088000
reserve2 0x1288000
reserve3 0x2288000
reserve4 0x2488000
oppo_custom 0x3488000
expdb 0x3588000
frp 0x3f88000
nvdata 0x4088000
metadata 0x6088000
protect1 0x8088000
protect2 0x8888000
seccfg 0x9800000
oemkeystore 0xa000000
proinfo 0xa800000
md1img 0xab00000
md1dsp 0xc300000
md1arm7 0xc700000
md3img 0xca00000
nvram 0xcf00000
lk 0xd400000
lk2 0xd500000
boot 0xd600000
logo 0xe600000
tee1 0xee00000
tee2 0xf300000
secro 0xf800000
keystore 0xfe00000
reserve_exp1 0x10600000
system 0x10800000
reserve_exp2 0xd0800000
reserve_exp3 0xd0c00000
cache 0xd1000000
userdata 0xe1000000
flashinfo 0xFFFF0080
sgpt 0xFFFF0000
Cheers
Willosy
Anyone??