Related
Dear all,
Just wanted to know do we have any methods to do the fully backup an old firmware, just care about the android os no need for any apps or data... so i can return later if can not live on JP9
mine: I5801DXJG2
Sorry if post in wrong section
kenblat said:
Dear all,
Just wanted to know do we have any methods to do the fully backup an old firmware, just care about the android os no need for any apps or data... so i can return later if can not live on JP9
mine: I5801DXJG2
Sorry if post in wrong section
Click to expand...
Click to collapse
hi
i dont know how to back up but u can go to the site : www.samfirmware.com
and download the os u want i got my orignal Asia india os from the same site and i have it saved on my desktop so chek if urs is also available
To backup your rom, unroot and then use Rom Manager that you'll find on the market
Ciao
Thanks m8,
Right there no I5801DXJG2 - but I5801DXJG5.rar available... so maybe i can try! Thanks so much for your effort
slumpolo said:
To backup your rom, unroot and then use Rom Manager that you'll find on the market
Ciao
Click to expand...
Click to collapse
Thanks bro, this way look like the best... so i can keep my origin firmware for future warranty kekeke
BR
slumpolo said:
To backup your rom, unroot and then use Rom Manager that you'll find on the market
Ciao
Click to expand...
Click to collapse
when i try to backup the current rom rom manager asking for install Flash ClockworkMod Recovry => pop-up alist but can not find out galaxy 3 there. How to solve it?
when i try to backup the current rom rom manager asking for install Flash ClockworkMod Recovry => pop-up alist but can not find out galaxy 3 there. How to solve it?
Rom manager doesnt work as yet on samsung galaxy 3 closest is titatium backup but that does only appz.. so for now downloading the firmware from samfirware.com is the only option..
adb shell
su
cat /proc/partitions
you can saw all the partitions
137 1 256 bml1
137 2 1280 bml2
137 3 512 bml3
137 4 8192 bml4
137 5 7680 bml5
137 6 225280 bml6
137 7 207360 bml7
137 8 38912 bml8
137 9 7168 bml9
137 10 16384 bml10
138 4 4352 stl4
138 6 217600 stl6
138 7 200192 stl7
138 8 34816 stl8
use dd copy rom to sdcard
dd if=/dev/block/bml1 of=/sdcard/bml1.bak
dd if=/dev/block/bml2 of=/sdcard/bml2.bak
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
dd if=/dev/block/bml4 of=/sdcard/bml4.bak
dd if=/dev/block/bml5 of=/sdcard/bml5.bak
dd if=/dev/block/bml6 of=/sdcard/bml6.bak
dd if=/dev/block/bml7 of=/sdcard/bml7.bak
dd if=/dev/block/bml8 of=/sdcard/bml8.bak
dd if=/dev/block/bml9 of=/sdcard/bml9.bak
dd if=/dev/block/bml10 of=/sdcard/bml10.bak
dd if=/dev/block/stl4 of=/sdcard/stl4.bak
dd if=/dev/block/stl6 of=/sdcard/stl6.bak
dd if=/dev/block/st7 of=/sdcard/stl7.bak
dd if=/dev/block/stl8 of=/sdcard/stl8.bak
restore you can use fastboot
http://android-dls.com/wiki/index.php?title=Fastboot
god_md5 said:
adb shell
su
cat /proc/partitions
you can saw all the partitions
137 1 256 bml1
137 2 1280 bml2
137 3 512 bml3
137 4 8192 bml4
137 5 7680 bml5
137 6 225280 bml6
137 7 207360 bml7
137 8 38912 bml8
137 9 7168 bml9
137 10 16384 bml10
138 4 4352 stl4
138 6 217600 stl6
138 7 200192 stl7
138 8 34816 stl8
use dd copy rom to sdcard
dd if=/dev/block/bml1 of=/sdcard/bml1.bak
dd if=/dev/block/bml2 of=/sdcard/bml2.bak
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
dd if=/dev/block/bml4 of=/sdcard/bml4.bak
dd if=/dev/block/bml5 of=/sdcard/bml5.bak
dd if=/dev/block/bml6 of=/sdcard/bml6.bak
dd if=/dev/block/bml7 of=/sdcard/bml7.bak
dd if=/dev/block/bml8 of=/sdcard/bml8.bak
dd if=/dev/block/bml9 of=/sdcard/bml9.bak
dd if=/dev/block/bml10 of=/sdcard/bml10.bak
dd if=/dev/block/stl4 of=/sdcard/stl4.bak
dd if=/dev/block/stl6 of=/sdcard/stl6.bak
dd if=/dev/block/st7 of=/sdcard/stl7.bak
dd if=/dev/block/stl8 of=/sdcard/stl8.bak
Click to expand...
Click to collapse
Thanks for tips
and can you provide the restore procedure as well?
fastboot can restore
Why people suggesting "sollutions" that aren't tested himself?
ROM Manager doesn't work with galaxy 3, and fastboot is no available in samsung devices...
kenblat said:
Dear all,
Just wanted to know do we have any methods to do the fully backup an old firmware, just care about the android os no need for any apps or data... so i can return later if can not live on JP9
mine: I5801DXJG2
Sorry if post in wrong section
Click to expand...
Click to collapse
please do not upgrade to JPB. It makes a click during the call. You can download all ROMS from samfirmware.com as it was mentioned here.
I know that stl7 means the /data partition ,and the others?
stl6 = /system
stl7 = /data
stl8 = /cache
There are some more:
bml5 = kernel
bml10 = baseband
deskjeti said:
stl6 = /system
stl7 = /data
stl8 = /cache
Click to expand...
Click to collapse
thx!!!!!!!!!!
deskjeti said:
There are some more:
bml5 = kernel
bml10 = baseband
Click to expand...
Click to collapse
Thanks for the kernel mount! Now all i need to do is know how to flash the kernel in there without fastboot.
If there is a trick to it, how do you copy/backup them
In a lot of batch files (.BAT) the mount is done for stl9 which appears to be the system mount point, how do you get stl9, is it dependent on the rom?
Also in those batch files no su is needed, so adb is in su mode, how do I get adb in system user mode?
(for the record, i'm on JPM rooted)
ralbuh said:
In a lot of batch files (.BAT) the mount is done for stl9 which appears to be the system mount point, how do you get stl9, is it dependent on the rom?
Also in those batch files no su is needed, so adb is in su mode, how do I get adb in system user mode?
(for the record, i'm on JPM rooted)
Click to expand...
Click to collapse
user system ?
Code:
# su system
$ whoami
whoami: unknown user id 1000
My Nexus 7 wifi tablet was working flawlessly for a few months since buying.
It was rooted, unlocked with stock android 4.2.1 and Team Win Recovery 2.3.2.1
Yesterday morning after charging all the night I saw that it was completely turned off. It didn't bother me, because it happened a couple of times before.
But this time, after I'd switched it on it hung on google color logo.
I waited half an hour but to no avail.
So at first I booted to recovery and wiped cache and the like. But the problem remained. Factory reset didn't help either.
So as a last resort I formated everything (including system).
Then I saw surprisingly in fastboot mode that lock state is: LOCKED.
I've tried to unlock it but it ended with an error:
C:\Users\Warp\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
FAILED (remote: (Unknown error code))
finished. total time: 7.241s
After I'd pressed "yes" to the question "unlock bootloader" on tablet it was displaying text "Neither USP nor CAC patition found" in a loop.
Because there is still TWR installed and I can't wipe it out i think I've lost the guarantee.
I can see my device in fastboot mode:
C:\Users\Warp\AppData\Local\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: XXXXXXXXXXXXXXXXXXXXXX
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000364700000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.193s
Is there anything left I can try?
AW: No way to unlock device. Is it bricked?
Have you tried reflashing stock rom? Maybe this rewrites recovery, too
Sent from my SK17i running Android 4.1.2
mihahn said:
Have you tried reflashing stock rom? Maybe this rewrites recovery, too
Click to expand...
Click to collapse
Yes, but it can't be done because the device is locked.
Before you do anything drastic, realize that you still have (in TWRP) a privileged execution environment (a root shell).
That means at a minimum you have a root-privileged shell available and some tools for fooling with partitions known to the TWRP kernel.
By drastic, I mean specifically: don't overflash the recovery partition at the command line from the root shell using /sbin/flash_image. Keep "root" until you are sure that nothing else can be done.
Back in a couple minutes - booting my N7 into TWRP right now to have a look at some things.
[ Edit ] From your post I see you have fastboot drivers set up - can you connect to TWRP via ADB?
Thank you for your reply.
Yes, I can see my device using: adb devices
adb shell also works.
[Edit] One more odd thing, when TWRP starts it asks me to enter my password. I think it's related to data encrypted partition but I've never done it for sure.
Well, I have a couple of hypotheses.
I guess I should ask one more question - is it correct that in TWRP you see none of your backups in /sdcard (TWRP mounts /sdcard on when it starts up) ?
If you have anything left on the SD card you want saved, get it backed up to your PC with "adb pull" before proceeding any further. (All suggestions below assume you have nothing left to save anywhere in /data.)
Also, I note that my N7 discharges slowly when plugged into my computer but sitting at the TWRP screen - so get your nexus fully charged before going any further.
The fact that you can boot TWRP means that the bootloader can find your recovery image, so at a minimum that means the bootloader can still understand some of the partitioning information it has available.
It is possible that the initial problem you had was something as simple as a corruption of a ext4 file system involving /cache, /system, or /data - as they need to be mounted after the early boot (ramdisk) initialization has more or less finished up. If they can not be mounted, the late boot processes never occur. Looking at your subsequent problems with unlocking the bootloader indicate a problem with the /cache partition - maybe?
[ The re-locking of the bootloader is odd, though. It suggests something got erased or mangled in a partition of the flash RAM that normally does not get mounted or touched by any of the usual kernel boots (whether we are talking about a recovery boot or any other android kernel boot). That means something other than /system, /cache, or /data - probably misc1, misc2, mfg, or possibly somewhere else (like slack space at the ends of either the boot or recovery partitions, or even in hard-coded location. ]
What happens if you try to rebuild the ext4 filesystems on /cache, /system, and /data?
[ note the partitions below are for the grouper N7 device; do a "adb shell cat /etc/fstab" to see if there are differences if you are on tilapia (3G version of the Nexus 7) ]
C:\foo> adb shell
# umount /data
# umount /cache
# umount /sdcard
# /sbin/mke2fs -t ext4 -m 0 /dev/block/mmcblk0p4
# /sbin/mke2fs -t ext4 -m 0 /dev/block/mmcblk0p3
# /sbin/mke2fs -t ext4 -m 0 /dev/block/mmcblk0p9
Does this succeed or fail? If it fails, what about first trying
# /sbin/erase_image /dev/block/mmcblk0p??? ( substitute correct # for ???)
prior to the mke2fs operation?
If you can get them to succeed, you might try restoring a backup (adb push to your "SD card"), and then doing a restore from TWRP and see if you can get it to boot.
You may also want to get your misc1 and misc2 partitions backed up - they contain the partitioning information (and usually the android "boot communication block), and they are generally identical (down to the last byte):
C:\foo> adb shell
# mount /sdcard (if this fails then you can't do this obviously)
# dd if=/dev/block/mmcblk0p5 of=/sdcard/part5.img bs=4096
# dd if=/dev/block/mmcblk0p8 of=/sdcard/part8.img bs=4096
# exit
C:\foo> adb pull /sdcard/part5.img
C:\foo> adb pull /sdcard/part8.img
If one of misc1 or misc2 got corrupted - and that is what is confusing the bootloader - it should be possible to flash the bad one with the good spare - but let's leave that alone until we see if /cache, /data, and /system can be re-initialized.
I'll come back to this thread in 8 hours or so - time for bed for me.
bftb0 said:
Well, I have a couple of hypotheses.
is it correct that in TWRP you see none of your backups in /sdcard (TWRP mounts /sdcard on when it starts up) ?
Click to expand...
Click to collapse
Yes it mounts it and it is empty (besides TWRP directory). I don't have backup either but it is no problem for me. I just want to start with stock Android 4.2.1 or if it's not possible - wipe out TWRP and send nexus for repairing.
bftb0 said:
What happens if you try to rebuild the ext4 filesystems on /cache, /system, and /data?
Does this succeed or fail?
Click to expand...
Click to collapse
Everything went smoothly, no errors here.
bftb0 said:
If you can get them to succeed, you might try restoring a backup (adb push to your "SD card"), and then doing a restore from TWRP and see if you can get it to boot.
Click to expand...
Click to collapse
I was trying to install a few roms this way, but the flashing never ends. On nexus I can see all the time: Flashing file 1 of 1 /sdcard/aokp_grouper_jb-mr1_build-1.zip
As I saw in recovery.log the problem is at the moment when filesystem is created:
C:\Users\Warp\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /tmp/recovery.log
[cut]
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/aokp_grouper_jb-mr1_build-1.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Creating filesystem with parameters:
Size: 681574400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6944
Inode size: 256
Journal blocks: 2600
Label:
Blocks: 166400
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41664 inodes and 5415/166400 blocks
and it stops here.
bftb0 said:
You may also want to get your misc1 and misc2 partitions backed up - they contain the partitioning information (and usually the android "boot communication block), and they are generally identical (down to the last byte):
Click to expand...
Click to collapse
Ok, done. I've checked they are identical.
bftb0 said:
I'll come back to this thread in 8 hours or so - time for bed for me.
Click to expand...
Click to collapse
Great I'm waiting impatiently.
Regards
warpek said:
...I don't have backup either...
Click to expand...
Click to collapse
Arrgh - you never made any backups?. I was hoping you had a TWRP backup - they are just tar files, so you can manually untar them into mounted partitions at the command line... and that way see if any errors occur on an individual partition you are working with. But I'll come back to this in a little bit.
warpek said:
Everything went smoothly, no errors here.
Click to expand...
Click to collapse
OK, got it.
warpek said:
As I saw in recovery.log the problem is at the moment when filesystem is created:
[cut]
Creating filesystem with parameters:
Size: 681574400
...
Created filesystem with 11/41664 inodes and 5415/166400 blocks
and it stops here.
Click to expand...
Click to collapse
Well, 650 MB (=681574400 bytes) is the /system partition, and the "Created filesystem" message probably indicates success with a mke2fs operation. But mke2fs does not wipe all the blocks, so it is still possible that the *restore to /system* operation is hanging on a media failure.
warpek said:
Ok, done. I've checked they are identical.
Click to expand...
Click to collapse
Just out of curiosity, do you get a md5sum of 3039dc3a07a56d0392d48787e4a202a1 for your part5.img and part8.img files? In principle, yours should not be identical to mine - especially if there is something unusual in the BCB (Boot Control Block), but there is a chance they are the same as these partitions seem to contain multiple backups of partitioning information. (My N7 appears to have been made in December)
OK, lets try something innocuous - raw read tests on all of your partitions. Let's see if you have a bunch of bad pages in one partition.
With TWRP running
C:\foo> adb shell
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0boot0
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0boot1
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p1
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p2
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p3
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p4
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p5
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p6
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p7
# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p8
These should all go through pretty quickly - I omitted the /data partition (p9) because it is huge. The next largest (system/p3) should take about 20 seconds for a successful raw read. If you get a read failure, repeat the command on the offending partition with the "conv=noerror" option, as in
dd of=/dev/null bs=4096 conv=noerror if=/dev/block/mmcblk0p8
Basically I'm just looking for you to narrow down the search to a problem partition. The next step is to try to manually unpack files into /system, /cache, and /data to see if there is a flash media problem in one of those partitions. Unfortunately, this is where TWRP backup files would have been useful: ROM files are not useful for this, and the google factory images e.g. nakasi-jop40d-factory-6ac58a1a.tgz contain image files which are not archives - they are "sparse ext4 images".
Even though you observed no failures with the mke2fs operations, you might want to also try to repeat that process (only for p3, p4, and p9 !) , but this time using the partition erase command first.
# /sbin/erase_image /dev/block/mmcblk0pN
prior to the mke2fs operation.
OK, standing by.
bftb0 said:
Arrgh - you never made any backups?
Click to expand...
Click to collapse
I always do, but I though that because there are no important files for me on the nexus and everything else can be downloaded (system image, twrp) there is no need. Obviously I was mistaken.
bftb0 said:
Just out of curiosity, do you get a md5sum of 3039dc3a07a56d0392d48787e4a202a1 for your part5.img and part8.img files?
Click to expand...
Click to collapse
I used md5sum to co compare those files, here is mine:
part5.img 59071590099d21dd439896592338bf95
part8.img 59071590099d21dd439896592338bf95
bftb0 said:
OK, lets try something innocuous - raw read tests on all of your partitions. Let's see if you have a bunch of bad pages in one partition.
Click to expand...
Click to collapse
Everything looks ok here. No errors and no long time reads.
bftb0 said:
Basically I'm just looking for you to narrow down the search to a problem partition. The next step is to try to manually unpack files into /system, /cache, and /data to see if there is a flash media problem in one of those partitions. Unfortunately, this is where TWRP backup files would have been useful:
Click to expand...
Click to collapse
Is there anything I can I do then?
bftb0 said:
Even though you observed no failures with the mke2fs operations, you might want to also try to repeat that process (only for p3, p4, and p9 !) , but this time using the partition erase command first.
# /sbin/erase_image /dev/block/mmcblk0pN
prior to the mke2fs operation.
Click to expand...
Click to collapse
Ok, done, still no errors.
I've also tried writing test using dd if=/dev/zero of=/dev/block/partition bs=4096 (for partition p3 and p4) and again without any errors.
warpek said:
I used md5sum to co compare those files, here is mine:
part5.img 59071590099d21dd439896592338bf95
part8.img 59071590099d21dd439896592338bf95
Click to expand...
Click to collapse
Hmmmm. I did a little more looking at my own misc partition images, and they each contain 64 repeated (and identical!) blocks of information that are 1280 bytes long - a group of 8 (at minor offsets of 0x4000, 0x5000, 0x6000, 0x7000, 0xc000, 0xd000, 0xe000, 0xf000) that repeat 8 times every 64kB (major offset of 0x10000). If you want to attach one of your misc partition images, I can have a look at it for comparison (it is small - 512 kB, and should not contain any private data). Wait, I just realized: I have a 32GB WiFi N7 - is yours a 16GB?
warpek said:
Is there anything I can I do then?
Click to expand...
Click to collapse
I could shove a (near stock) boot.img and system.img backup from TWRP someplace, but the system image is huge. I don't have a convenient place to drop it - got any suggestions? In principle - barring any other errors - that should boot correctly so long as the ext4 filesystems on /data and /cache are intact and operating correctly.
warpek said:
I've also tried writing test using dd if=/dev/zero of=/dev/block/partition bs=4096 (for partition p3 and p4) and again without any errors.
Click to expand...
Click to collapse
Barring a tar or other archive file which we could unpack directly into (mounted) /system, that was going to be my next suggestion. Rats.
Maybe it is time to try the read/write tests with the /data partition?
Actually, before you do that, what were the dump lengths you got for each of your partitions? Here are mine (using bs=4096):
Code:
/dev/block/mmcblk0boot0 512 ( 2097152 bytes - 2.0MB)
/dev/block/mmcblk0boot1 512 ( 2097152 bytes - 2.0MB)
/dev/block/mmcblk0p1 3072 ( 12582912 bytes - 12.0MB) recovery
/dev/block/mmcblk0p2 2048 ( 8388608 bytes - 8.0MB) boot
/dev/block/mmcblk0p3 166400 (681574400 bytes - 650.0MB) system
/dev/block/mmcblk0p4 113408 (464519168 bytes - 443.0MB) cache
/dev/block/mmcblk0p5 128 ( 524288 bytes - 512kB) misc1?
/dev/block/mmcblk0p6 2560 ( 10485760 bytes - 10.0MB) -WTF?- "staging?"
/dev/block/mmcblk0p7 1280 ( 5242880 bytes - 5.0MB) mfg
/dev/block/mmcblk0p8 128 ( 524288 bytes - 512kB) misc2?
/dev/block/mmcblk0p9 ?? ( ?? bytes - ??MB) data
Note I didn't do my /data partition - I have a 32GB N7, so I suppose that means that /data is 30+ GB in size. Lazy and didn't want to wait.
---------- Post added at 01:40 PM ---------- Previous post was at 12:55 PM ----------
FYI,
shoving some TWRP backup images (system, boot) to my dropbox right now. Lightly-rooted stock. (Added su and SuperSu in /system, and altered default.prop in the boot image so that the secure flag is disabled and the adb daemon starts up straight away). Other than those changes, 100% stock, including kernel.
I'll send a PM when I figure out how Dropbox works.
bftb0 said:
Wait, I just realized: I have a 32GB WiFi N7 - is yours a 16GB?
Click to expand...
Click to collapse
Yes, I've got 16GB version.
bftb0 said:
I could shove a (near stock) boot.img and system.img backup from TWRP someplace, but the system image is huge. I don't have a convenient place to drop it - got any suggestions?
Click to expand...
Click to collapse
I can create ftp account on and send you login data in a private message. Will it be convenient for you?
bftb0 said:
Maybe it is time to try the read/write tests with the /data partition?
Click to expand...
Click to collapse
Yea, but ... now something really strange happened.
All partitions have disappeared. _I'm sure_ that I didn't zeroed the whole mmcblk0 device. Just the partition I mentioned before.
Code:
ls /dev/block
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0bo
loop1 loop3 loop5 loop7 mmcblk0boot0 platform
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15762194432 bytes
4 heads, 16 sectors/track, 481024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
TWRP still starts but it takes more time.
bftb0 said:
Actually, before you do that, what were the dump lengths you got for each of your partitions? Here are mine (using bs=4096):
Click to expand...
Click to collapse
I don't have partition table now so I it is useless. But for the future use, can you tell me please how I can see this kind of dump?
Edit: I'd be grateful if anyone having Nexus 7 16GB paste output of command:
Code:
adb shell /sbin/fdisk -l /dev/block/mmcblk0
I hope I will be able to create proper partitions on my device then.
But I'm afraid of using fdisk to create partitions because this can lead to destroy current recovery which still starts.
warpek said:
Yes, I've got 16GB version.
I can create ftp account on and send you login data in a private message. Will it be convenient for you?
Click to expand...
Click to collapse
or you could just attach it - should be less than the XDA attachment size limit, and as I mentioned there is no private info in there.
Looking at my own dumped images, it looks like this same partitioning information appears in mmcblk0boot0 190 times (!!), and in mmcblk0boot1 256 times (!!). I need to extract them all and compare checksums to see if they are identical.
warpek said:
Yea, but ... now something really strange happened.
All partitions have disappeared. _I'm sure_ that I didn't zeroed the whole mmcblk0 device. Just the partition I mentioned before.
Code:
ls /dev/block
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0bo
loop1 loop3 loop5 loop7 mmcblk0boot0 platform
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15762194432 bytes
4 heads, 16 sectors/track, 481024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
TWRP still starts but it takes more time.
I don't have partition table now so I it is useless. But for the future use, can you tell me please how I can see this kind of dump?
Click to expand...
Click to collapse
Holy ****.
(My info was just from collected from looking at the output of individual dd read commands on each partition)
Again, holy **** - that's a world of hurt. I suppose recovery might still be possible, but perhaps only with some exhaustive code review of how the mmc driver determines the partitioning. and possibly some very dangerous patching of areas in mmcblk0boot{0,1}. It does appear that partitioning information is stored redundantly in multiple places on the tablet.
I am wondering - if the partitioning information that the TWRP boot was somehow partially corrupted - then running "dd if=/dev/zero" to write without a "count=" size constraint might have caused an over-run past where the actual partition was supposed to live.
At this point, I wouldn't attempt any more writing operations - especially since TWRP doesn't know where anything lives any longer.
---------- Post added at 02:23 PM ---------- Previous post was at 02:16 PM ----------
For the purposes of rescue you might want to capture some dumps of mmcblk0boot0 and mmcblk0boot1
Since you can not mount the /sdcard to store the dumps temporarily, you should be able to stuff them into ramdisk temporarily and then pull them to your PC via adb in the same TWRP session:
C:\foo> adb shell
# mkdir /tmp/dumps
# dd if=/dev/block/mmcblk0boot0 bs=4096 of=/tmp/dumps/mmcblk0boot0.img
# dd if=/dev/block/mmcblk0boot1 bs=4096 of=/tmp/dumps/mmcblk0boot1.img
# exit
C:\foo> adb pull /tmp/dumps/
The worst that can happen here (if the partitioning for mmcblk0boot{0,1} is wrong - and huge - you'll wedge the TWRP session by filling memory.
Without committing to a lot of effort it looks like you are looking at RMA time.
bftb0 said:
I am wondering - if the partitioning information that the TWRP boot was somehow partially corrupted - then running "dd if=/dev/zero" to write without a "count=" size constraint might have caused an over-run past where the actual partition was supposed to live.
Click to expand...
Click to collapse
Yes, I suppose it could be the case.
bftb0 said:
For the purposes of rescue you might want to capture some dumps of mmcblk0boot0 and mmcblk0boot1
Click to expand...
Click to collapse
Done without problems.
bftb0 said:
Without committing to a lot of effort it looks like you are looking at RMA time.
Click to expand...
Click to collapse
[/QUOTE]
I don't want to bother you with too much digging, so maybe it's time to send my device back do the seller.
But before that ... I think I should wipe out TWRP.
Should I use dd on the whole mmcblk0 device to do that?
Nevertheless I'm really greateful for your time and efforts. Thank you very much.
warpek said:
Should I use dd on the whole mmcblk0 device to do that?
Click to expand...
Click to collapse
Hmmm. Dunno. At this point you might end up borking the bootloader trying something like that.
There have been other threads where folks reported returning devices without bothering to do any clean up - and without repercussions.
Seems believable; the folks that are tasked with repairing units under RMA are not approaching each one as if it were a forensic evaluation. From a pure business standpoint that would be a huge waste of time and money. If they ever get rewarded for anything they do, it's probably a throughput metric (devices repaired or scrapped per work shift). Your unit will be one of many.
Your thanks are welcome, but I have an interest in this anyway. I noticed in digging around that (rather bizarrely) there is a partition that TWRP identifies as "staging" (/dev/block/mmcblk0p6). The bizarre part of this is that a hexdump revealed a few strings that were unicode URLs for XDA's ad networks. !! ?? !!
That rather freaks me out - what the frick is user data (I suppose from web browsing?) doing in a partition that never gets mounted and is (apparently) not in any identify-able file system format?
Back when Amon_RA was packaging his recovery for various devices, he would use a STOCK KERNEL in the boot image for his recovery boot. That pretty much is a guarantee that the kernel drivers (e.g. for MTD/MMC) would behave no differently from the way the device manufacturer does things - including for important things like interpreting partition tables.
With TWRP and CWM we currently have no such assurances that subtle bugs have not crept in to important places unless we repackage their boot images to use stock kernels.
Anyway, I am trying to review what I *think* is partitioning information to see what I can figure out - but you probably shouldn't wait for me.
Good luck with your return.
I don't want to bother you with too much digging, so maybe it's time to send my device back do the seller.
But before that ... I think I should wipe out TWRP.
Should I use dd on the whole mmcblk0 device to do that?
Click to expand...
Click to collapse
Hi warpek, I don't mean to butt in to this thread but I encountered a similar issue to yours this past weekend that's gotten to the point where I can no longer turn on nor get into the bootloader anymore. My question is since our devices have been modified, do you know if there is there any chance that Asus could deny and void the warranty upon finding that out?
There have been other threads where folks reported returning devices without bothering to do any clean up - and without repercussions.
Click to expand...
Click to collapse
Alright guess I'll go give it a shot.
Hi fungosaurus,
For the benefit of the rest of the N7 community - could you say a few words about what ROM/kernel was on your tablet, and (if you know) about what the charge state of the battery was like when the first hint of problem occurred?
A few reports don't mean anything conclusive, but it sure is starting to look like something is going on with "low battery" / "can't turn on" syndromes ... which then unfold into full-blown disasters.
bftb0 said:
Hi fungosaurus,
For the benefit of the rest of the N7 community - could you say a few words about what ROM/kernel was on your tablet, and (if you know) about what the charge state of the battery was like when the first hint of problem occurred?
A few reports don't mean anything conclusive, but it sure is starting to look like something is going on with "low battery" / "can't turn on" syndromes ... which then unfold into full-blown disasters.
Click to expand...
Click to collapse
Oh yes of course. CM10.1 Jan 10 nightly with whichever kernel it came with. As far as I could tell the battery was fully charged when I could no longer power it back on or access the bootloader.
My issue was actually a bit complicated and I might've actually been the one to worsen it through my ignorance. I made a post on Reddit that describes in detail what happened. Does this help?
fungosaurus said:
Does this help?
Click to expand...
Click to collapse
Only time will tell - for instance if lots of folks start reporting troubles with the same kernel.
Sounds more like a hardware problem though. Thanks for the info.
I think I saw a recent news article stating that Asus is shipping about 1 million N7's per month now. If they have shipped 5 million cumulatively, and they have a defect rate of only 0.1% in the first year of service, that would be 5000 owners who might end up on message boards looking for help. Although - since rooters are presumably a small fraction of owners - I guess we should see a much smaller number of folks who are rooted AND experience hardware troubles.
@warpek - the data stored in the misc1/misc2 partitions does in fact appear to be partitioning data. But I don't think you can use "fdisk" for the mmcblk0 device in any event.
bftb0 said:
Hmmm. Dunno. At this point you might end up borking the bootloader trying something like that.
There have been other threads where folks reported returning devices without bothering to do any clean up - and without repercussions.
Click to expand...
Click to collapse
Yes, but to be sure that I won't have any problems while returning my device I zeroed the whole block device.
bftb0 said:
Your thanks are welcome, but I have an interest in this anyway. I noticed in digging around that (rather bizarrely) there is a partition that TWRP identifies as "staging" (/dev/block/mmcblk0p6). The bizarre part of this is that a hexdump revealed a few strings that were unicode URLs for XDA's ad networks. !! ?? !!
Click to expand...
Click to collapse
That is really astounding. Please let us now if you have any conclusions.
Meanwhile I'm sending my nexus to Asus.
Thanks again.
fungosaurus said:
My question is since our devices have been modified, do you know if there is there any chance that Asus could deny and void the warranty upon finding that out?
Click to expand...
Click to collapse
As bftb0 said it shouldn't be any problems but to be sure I zeroed the whole block device area before returning it back.
After flashing a 16go kdz in my lg g2 d802 I lost my 32go memory, I followed this tuto http://forum.xda-developers.com/showthread.php?t=2470207&page=3
What I did ; used lg flash tools 2014 to flash 32 go kdz [doesn't solve the problem, just 10.7go] then I rooted my phone with iroot25,check root with root checker, copy files and overwrite by Total Commander to system/bin after making it RW, but when I set permissions to 755 and apply doesn't saved check again and found 602 so I can't use ADB to modify partitions and got permissions denied also I lose my root.
if I reboot phone I lose network
where is the problem??
I really appreciate your help, thank you very much
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
07459cead6cc4ddf device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # adb devices
adb devices
List of devices attached
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC 032G96 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 15.7GB 11.6GB ext4 userdata
36 15.7GB 15.8GB 37.7MB grow
(parted) quit
quit
quit
@ANDROID:/system # quit
quit
sh: quit: not found
127 @ANDROID:/system # ./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512
seek=61071327 conv=notrunc
of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: ./dd: not found
127 @ANDROID:/system # dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 se
ek=61071327 conv=notrunc
=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: dd: can't execute: Permission denied
126 @ANDROID:/system # /dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 s
eek=61071327 conv=notrunc
f=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: /dd: not found
127 @ANDROID:/system #
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Goona work hhh
Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Yes very true I learned a lot but this solution works for a lot of users, im just struggling with system/bin permissions, I know something wrong with SU or root or kdz or lg tools 2014, so im looking for the generosity of experts or people who had the same issue, im very sure its gonna work, in the same time, im trying to be familiar with android/Linux, lol, thank you for your reply
Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Everything is possible with Linux, you may learn something new from this thread too, lol
thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?
RE
Yoinx said:
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?
Click to expand...
Click to collapse
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man
thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
thequietman1979 said:
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man
Click to expand...
Click to collapse
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.
Solved
Yoinx said:
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.
Click to expand...
Click to collapse
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Yes Thanks for mentioning that : su in folder xbin and not system/bin
kindly try with this last 2 commands
2.
adb shell
su
cd /system
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
where can i find the files to download?
http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/
Hello! Please help!!! I try to paste the last two lines
./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
and when press enter it says : sh: ./dd: not found
I also try and these :
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
but with the same results!!
Which link process is the final? And where is a link with the finally sdparted-recovery-all-files?
Which firmware can i use before process? 4.2.2 or 4.4.2?
Which root i can use? With SuperSU or Superuser?
Which programe to use? Total commander or Root explorer??
PLease help me!
if i flash the correct kdz without doing anything else does it fix the problem ??
Please explain
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
How you root your phon, thats my biggest problem
Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
You need to root it before following the tutorial to get back 32go
http://forum.xda-developers.com/showthread.php?t=2470207&goto=newpost
To root your phone use iroot
Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2448887
thequietman1979 said:
http://forum.xda-developers.com/showthread.php?t=2448887
Click to expand...
Click to collapse
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me
Ebaharloo said:
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me
Click to expand...
Click to collapse
What s the model of your lg g2?
If its d802 try to flash it back to kitkat using lg flash tool 2014 than root it using iroot or iroot 10, than follow the tuto, u gonna restore your memory
Root lg g2 d802 : http://forum.xda-developers.com/lg-...ols-how-to-install-twrp-bump-d80230a-t3072186.
Manual method: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
No fancy stuff for now, this guide will be to the point.
We are going to use TWRP that mounts only data and cache and dd command to backup all partitions to external_sd
Things needed:
Unlocked honor 7x with twrpimgmount installed : Go here
A 16gb memory card
Instructions:
1. Reboot your phone to recovery and connect it to PC
2. Open cmd in pc and navigate to adb and fastboot dir (you did this when you flashed twrp using fastboot)
3. run following commands one at a time (wait till it back ups)
Code:
adb shell
dd if=/dev/block/mmcblk0p28 of=/external_sd/boot.img
dd if=/dev/block/mmcblk0p41 of=/external_sd/bootfail_info
dd if=/dev/block/mmcblk0p36 of=/external_sd/cache.img
dd if=/dev/block/mmcblk0p45 of=/external_sd/cust.img
dd if=/dev/block/mmcblk0p34 of=/external_sd/dfx
dd if=/dev/block/mmcblk0p30 of=/external_sd/dts
dd if=/dev/block/mmcblk0p5 of=/external_sd/fastboot
dd if=/dev/block/mmcblk0p4 of=/external_sd/frp
dd if=/dev/block/mmcblk0p27 of=/external_sd/fw_hifi
dd if=/dev/block/mmcblk0p3 of=/external_sd/fw_lpm3
dd if=/dev/block/mmcblk0p37 of=/external_sd/hisitest0
dd if=/dev/block/mmcblk0p38 of=/external_sd/hisitest1
dd if=/dev/block/mmcblk0p39 of=/external_sd/hisitest2
dd if=/dev/block/mmcblk0p20 of=/external_sd/misc
dd if=/dev/block/mmcblk0p31 of=/external_sd/modem_fw
dd if=/dev/block/mmcblk0p18 of=/external_sd/modem_om
dd if=/dev/block/mmcblk0p17 of=/external_sd/modem_secure
dd if=/dev/block/mmcblk0p10 of=/external_sd/modemnvm_backup
dd if=/dev/block/mmcblk0p6 of=/external_sd/modemnvm_factory
dd if=/dev/block/mmcblk0p11 of=/external_sd/modemnvm_img
dd if=/dev/block/mmcblk0p12 of=/external_sd/modemnvm_system
dd if=/dev/block/mmcblk0p21 of=/external_sd/modemnvm_update
dd if=/dev/block/mmcblk0p7 of=/external_sd/nvme
dd if=/dev/block/mmcblk0p8 of=/external_sd/oeminfo
dd if=/dev/block/mmcblk0p40 of=/external_sd/patch
dd if=/dev/block/mmcblk0p16 of=/external_sd/persist
dd if=/dev/block/mmcblk0p48 of=/external_sd/product
dd if=/dev/block/mmcblk0p29 of=/external_sd/recovery.img
dd if=/dev/block/mmcblk0p22 of=/external_sd/recovery2.img
dd if=/dev/block/mmcblk0p23 of=/external_sd/reserved2
dd if=/dev/block/mmcblk0p9 of=/external_sd/reserved3
dd if=/dev/block/mmcblk0p14 of=/external_sd/reserved4
dd if=/dev/block/mmcblk0p15 of=/external_sd/reserved5
dd if=/dev/block/mmcblk0p32 of=/external_sd/reserved7
dd if=/dev/block/mmcblk0p33 of=/external_sd/reserved8
dd if=/dev/block/mmcblk0p43 of=/external_sd/reserved9
dd if=/dev/block/mmcblk0p42 of=/external_sd/rrecord
dd if=/dev/block/mmcblk0p13 of=/external_sd/secure_storage
dd if=/dev/block/mmcblk0p26 of=/external_sd/sensorhub
dd if=/dev/block/mmcblk0p19 of=/external_sd/splash2.img
dd if=/dev/block/mmcblk0p44 of=/external_sd/system.img
dd if=/dev/block/mmcblk0p24 of=/external_sd/teeos
dd if=/dev/block/mmcblk0p25 of=/external_sd/trustfirmware
dd if=/dev/block/mmcblk0p49 of=/external_sd/userdata.img
dd if=/dev/block/mmcblk0p35 of=/external_sd/vbmeta
dd if=/dev/block/mmcblk0p47 of=/external_sd/vendor.img
dd if=/dev/block/mmcblk0p46 of=/external_sd/version
dd if=/dev/block/mmcblk0p1 of=/external_sd/vrl
dd if=/dev/block/mmcblk0p2 of=/external_sd/vrl_backup
How to restore? (consider we have to restore system)
1. Reboot to twprimgmount
2. Copy your backed up image to external_sd
3. Run following command
Code:
adb shell
dd if=/external_sd/system.img of=/dev/block/mmcblk0p44
Join Telegram group if you are willing to test latest stuff.
Note: You can also use the TWRP backup function to get a stock backup. Restore it using twrp to get back to stock
DO NOT UNNECESSARILY RESTORE ALL PARTITIONS, IT MAY BRICK YOUR 7X.
A script @skippotter to make all this easy (not tested by me)
Follow next:
1. Flash magisk 14.0 (I use this) or Super su
2. Use different region firmware without rebranding
Sudeep Duhoon said:
No fancy stuff for now, this guide will be to the point.
We are going to use TWRP and dd command to backup all partitions to external_sd
Things needed:
Unlocked honor 7x with twrp installed : Go here
A 16gb memory card
Instructions:
1. Reboot your phone to recovery and connect it to PC
2. Mount system read only when twrp asks you
3. Open cmd in pc and navigate to adb and fastboot dir (you did this when you flashed twrp using fastboot)
4. run following commands one at a time (wait till it back ups)
How to restore? (consider we have to restore system)
1. Reboot to twrp
2. Copy your backed up image to external_sd
3. Run following command
Follow next:
1. Flash magisk 14.0 (I use this) or Super su
2. Manually Update Your 7x (coming soon)
Click to expand...
Click to collapse
Thank u soo much
reserved, just in case (yeah i got late, still)
Sudeep Duhoon said:
reserved, just in case (yeah i got late, still)
Click to expand...
Click to collapse
I have a question because I think I may be missing something. I understand this is a complete backup to PC. But, if I have flashed twrp to recovery and recovery2, will this method still backup those original .imgs?
Milly7 said:
I have a question because I think I may be missing something. I understand this is a complete backup to PC. But, if I have flashed twrp to recovery and recovery2, will this method still backup those original .imgs?
Click to expand...
Click to collapse
No it won't, it'll backup twrp recovery instead
But you can get stock recoveries from here
https://forum.xda-developers.com/devdb/project/?id=23956#downloads
Just a note for anyone trying this, make sure your external_sd is formatted exFAT not FAT32 or any file over 4gb, (system.img and userdata.img for me) will fail.
Here is a batch file that will work on windows to run all the commands sequentially
Can anyone Backup Vendor,Version,Product and Cust.img for L21C432 and upload please?
Or have anyone a Full Stock Twrp Backup for L21C432?
@Sudeep Duhoon What's the total expected size of userdata.img while backing up?? I'm using a 16gb sd card and it's showing I/O error at first line but copying around 9gb successfully.
is unlocking bootloader necessary for this? can't we just boot twrp by "fastboot boot twrp.img" and make backup with cmd?
Mohan0004 said:
is unlocking bootloader necessary for this? can't we just boot twrp by "fastboot boot twrp.img" and make backup with cmd?
Click to expand...
Click to collapse
anyone? please
Sudeep Duhoon said:
No fancy stuff for now, this guide will be to the point.
We are going to use TWRP and dd command to backup all partitions to external_sd
Things needed:
Unlocked honor 7x with twrp installed : Go here
A 16gb memory card
Instructions:
1. Reboot your phone to recovery and connect it to PC
2. Mount system read only when twrp asks you
3. Open cmd in pc and navigate to adb and fastboot dir (you did this when you flashed twrp using fastboot)
4. run following commands one at a time (wait till it back ups)
Code:
adb shell
dd if=/dev/block/mmcblk0p28 of=/external_sd/boot.img
dd if=/dev/block/mmcblk0p41 of=/external_sd/bootfail_info
dd if=/dev/block/mmcblk0p36 of=/external_sd/cache.img
dd if=/dev/block/mmcblk0p45 of=/external_sd/cust.img
dd if=/dev/block/mmcblk0p34 of=/external_sd/dfx
dd if=/dev/block/mmcblk0p30 of=/external_sd/dts
dd if=/dev/block/mmcblk0p5 of=/external_sd/fastboot
dd if=/dev/block/mmcblk0p4 of=/external_sd/frp
dd if=/dev/block/mmcblk0p27 of=/external_sd/fw_hifi
dd if=/dev/block/mmcblk0p3 of=/external_sd/fw_lpm3
dd if=/dev/block/mmcblk0p37 of=/external_sd/hisitest0
dd if=/dev/block/mmcblk0p38 of=/external_sd/hisitest1
dd if=/dev/block/mmcblk0p39 of=/external_sd/hisitest2
dd if=/dev/block/mmcblk0p20 of=/external_sd/misc
dd if=/dev/block/mmcblk0p31 of=/external_sd/modem_fw
dd if=/dev/block/mmcblk0p18 of=/external_sd/modem_om
dd if=/dev/block/mmcblk0p17 of=/external_sd/modem_secure
dd if=/dev/block/mmcblk0p10 of=/external_sd/modemnvm_backup
dd if=/dev/block/mmcblk0p6 of=/external_sd/modemnvm_factory
dd if=/dev/block/mmcblk0p11 of=/external_sd/modemnvm_img
dd if=/dev/block/mmcblk0p12 of=/external_sd/modemnvm_system
dd if=/dev/block/mmcblk0p21 of=/external_sd/modemnvm_update
dd if=/dev/block/mmcblk0p7 of=/external_sd/nvme
dd if=/dev/block/mmcblk0p8 of=/external_sd/oeminfo
dd if=/dev/block/mmcblk0p40 of=/external_sd/patch
dd if=/dev/block/mmcblk0p16 of=/external_sd/persist
dd if=/dev/block/mmcblk0p48 of=/external_sd/product
dd if=/dev/block/mmcblk0p29 of=/external_sd/recovery.img
dd if=/dev/block/mmcblk0p22 of=/external_sd/recovery2.img
dd if=/dev/block/mmcblk0p23 of=/external_sd/reserved2
dd if=/dev/block/mmcblk0p9 of=/external_sd/reserved3
dd if=/dev/block/mmcblk0p14 of=/external_sd/reserved4
dd if=/dev/block/mmcblk0p15 of=/external_sd/reserved5
dd if=/dev/block/mmcblk0p32 of=/external_sd/reserved7
dd if=/dev/block/mmcblk0p33 of=/external_sd/reserved8
dd if=/dev/block/mmcblk0p43 of=/external_sd/reserved9
dd if=/dev/block/mmcblk0p42 of=/external_sd/rrecord
dd if=/dev/block/mmcblk0p13 of=/external_sd/secure_storage
dd if=/dev/block/mmcblk0p26 of=/external_sd/sensorhub
dd if=/dev/block/mmcblk0p19 of=/external_sd/splash2.img
dd if=/dev/block/mmcblk0p44 of=/external_sd/system.img
dd if=/dev/block/mmcblk0p24 of=/external_sd/teeos
dd if=/dev/block/mmcblk0p25 of=/external_sd/trustfirmware
dd if=/dev/block/mmcblk0p49 of=/external_sd/userdata.img
dd if=/dev/block/mmcblk0p35 of=/external_sd/vbmeta
dd if=/dev/block/mmcblk0p47 of=/external_sd/vendor.img
dd if=/dev/block/mmcblk0p46 of=/external_sd/version
dd if=/dev/block/mmcblk0p1 of=/external_sd/vrl
dd if=/dev/block/mmcblk0p2 of=/external_sd/vrl_backup
How to restore? (consider we have to restore system)
1. Reboot to twrp
2. Copy your backed up image to external_sd
3. Run following command
Code:
adb shell
dd if=/external_sd/system.img of=/dev/block/mmcblk0p44
Join Telegram group if you are willing to test latest stuff.
Follow next:
1. Flash magisk 14.0 (I use this) or Super su
2. Manually Update Your 7x
Click to expand...
Click to collapse
Hello
Is some one can send me only boot.img of honor 7x please?
My phone can't boot after some tests. I do all backups found here before root, and do some tests and now it is not booting. It freez at unlock bootloader screen (black with orange texts)
when i restore my backed boot.img to /dev/block/mmcblk0p28, it is not working too
twrp is working
thanks
Mohan0004 said:
anyone? please
Click to expand...
Click to collapse
yes it will work if you can boot TWRP
But this would still require an unlocked bootloader
someone in another huawei forum have said that booting TWRP was not working (maybe disabled in fastboot)
instead of sdcard can we make backup directly to pc (in adb folder), what will be command for those?
Someone have backup for L24 they can upload?
skippotter said:
Here is a batch file that will work on windows to run all the commands sequentially
Click to expand...
Click to collapse
I did it a bit smaller and more generic in case Huawei is going to add another 200 partitions ... but in general it is your approach.
#!/bin/sh
srcdir=/dev/block/platform/hi_mci.0/by-name
if [ $# -eq 0 ]; then
tgtdir=/wherever/you/want/to/storeelse
tgtdir="$1"fi
echo ${tgtdir}
ls -l ${srcdir} > "${tgtdir}/partitions.list"
if [ $? -ne 0 ]; then
echo "unable to read /dev folder ... probably you are not root?"
exit 1fi
for a in `ls ${srcdir} | grep -v userdata`; do
b=`ls -l ${srcdir}/${a} | cut -f 2 -d '>' | cut -f 2 -d ' '`
echo $a points to $b
if [ "$(ls ${b} | wc -l)" == "1" ]; then
dd if="$b" of="${tgtdir}/${a}" bs=2048 else
echo "$b for $a not found!" fidone
tar -cvf ${tgtdir}/userdata.tar /data
ls ${tgtdir}
tlxxxsracer said:
Someone have backup for L24 they can upload?
Click to expand...
Click to collapse
I would like to know the same thing. I did the backup, but it turns out my system and usersata were 0 bytes. Could really use a L24 backup of those partitions if someone has it available please.
kindly help me please
Can someone post the link to complete backup of the phone , my phone is dead
I need the original system partition so that I can restore the original recovery and update for volte.
Thanks!
If I wish export storage to pendrive with OGT adapter, not need abd shell?
Can you help me about commands 'd use? 'll be possible from terminal emulator with root?
Thanks before!!!!