[Tutorial] Manual TA partition management (Win/OS X/*nix) - Xperia Z1 Android Development

There are tools that do this automatically for you, but to date they only work on Windows and as a general rule of thumb it is a bad idea to blindly run scripts found on the internet on your computer, even if the author doesn't mean any harm, things can go wrong. Furthermore it is generally a good idea to actually learn how your device works rather than just using tools that do everything for you.
However if you do not feel up to the task, and are running Windows, you can use this automated tool instead if you want.
Fair warning: Flashing your TA partition is dangerous stuff, do this wrong and you can most certainly hard-brick your device. I will not take any responsibility at all for anything you deem might have (or might not have) been a result of these procedures, be it bricked devices, lost DRM-keys, your milk going sour, your computer exploding, your friends computer exploding, repetitive stress injury, the loss of any limbs and/or digits or literally anything else.
General requirements before getting started:
Android SDK platform-tools (namely ADB)
Rooted Sony Xperia Z1
For this guide I am going to assume you know how ADB works and that you know how to get access to ADB in your preferred operating system.
Backing up your TA partition
For this part you will need both a locked and rooted Xperia Z1. Ok, you don't actually need a locked device, but the most common reason for backing up this partition is to keep your DRM-keys intact, and this means your device needs to be locked.
Steps:
Open your favourite terminal emulator
Acquire a shell with your device (adb shell)
Acquire a root shell with your device (su)
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
Verify that the hashes match!
Leave root shell (exit)
Leave device shell (exit)
adb pull /sdcard/TA.img TA.img
Use your favourite tool to verify the hash hasn't changed after copying to your computer (openssl md5 TA.img)
Put this file (and the hash) in a safe place, this is your TA backup.
Restoring your TA partition
For this part you will need your TA partition backup and the matching rooted Xperia Z1 (literally the exact same device you got the backup from). You will also need to restore an unmodified stock boot partition (a boot partition from any ROM claiming to work on locked bootloaders will do fine) prior to restoring the TA partition backup, otherwise you will not be able to boot after restoring the TA partition. Also, do not attempt this with someone elses TA partition, I haven't personally tried it but I am told you will hard-brick your device! It sucks but if you've lost your DRM keys then you will not be able to recover them.
Steps:
Open your favourite terminal emulator
adb push TA.img /sdcard/TA.img
Acquire a shell with your device (adb shell)
Acquire a root shell with your device (su)
cd /sdcard/
If you have the hash you read during the backup procedure stored, now is a good time to verify that it still matches the backup
dd if=TA.img of=/dev/block/platform/msm_sdcc.1/by-name/TA
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
Make absolutely certain that the hashes match!
If they don't, DO NOT REBOOT YOUR DEVICE!
Leave root shell (exit)
Leave device shell (exit)
Done!
Good luck! If I have helped you, please click the thanks button!

there is a good reason why there is a script to do this...
the TA is VERY VERY DANGEROUS AREA... any minor mistake and you WILL BE LEFT with bricked device...
DO NOT TRY MANUAL WAY!
one small mistake in the partition layout (command typo) and you might wipe the bootloader or corrupt the partition table...
please i strongly advise that you DO NOT play with TA...
FYI this is the partition layout for the Z1:
Code:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-21 17:03 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-21 17:03 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-21 17:03 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-21 17:03 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-21 17:03 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-21 17:03 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-21 17:03 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-21 17:03 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-21 17:03 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-21 17:03 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-21 17:03 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-21 17:03 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-21 17:03 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-21 17:03 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-21 17:03 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-21 17:03 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-21 17:03 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-21 17:03 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-21 17:03 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-21 17:03 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-21 17:03 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-21 17:03 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-21 17:03 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-21 17:03 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-21 17:03 userdata -> /dev/block/mmcblk0p25
thanks to @yeeson for fetching this info!

DooMLoRD said:
there is a good reason why there is a script to do this...
the TA is VERY VERY DANGEROUS AREA... any minor mistake and you WILL BE LEFT with bricked device...
DO NOT TRY MANUAL WAY!
one small mistake in the partition layout (command typo) and you might wipe the bootloader or corrupt the partition table...
please i strongly advise that you DO NOT play with TA...
FYI this is the partition layout for the Z1:
Code:
<partition layout for Xperia Z1>
thanks to @yeeson for fetching this info!
Click to expand...
Click to collapse
Thanks for the info mate, though I do understand your point I would like to point out that running random scripts on sensitive areas is in my opinion much more dangerous than actually knowing what you are doing, and really isn't something that should be promoted in general (I understand why it is in this case). I personally trust myself not to make those kinds of mistakes much more than I do some random person on the internet. Especially when options aren't provided for operating systems other than Windows I feel that this guide is still needed.
We should be teaching people, not simply providing a solution (to something which someone who doesn't know what he is doing should even be tinkering with to be honest).
Had forgotten about the named symlinks, thanks for that! Updated tutorial.

OMG !!! So many partitions. Is there a place where to find their purpose ?
One question please: waht does "TA" stand for ?
And finally: I agree... Such informations are HIGHLY dangerous in unexperienced hands. Sooooo easy to brick a phone...

bbkdhumm said:
OMG !!! So many partitions. Is there a place where to find their purpose ?
One question please: waht does "TA" stand for ?
And finally: I agree... Such informations are HIGHLY dangerous in unexperienced hands. Sooooo easy to brick a phone...
Click to expand...
Click to collapse
Aw come on guys, it's not that difficult of a guide to follow is it? Besides, how do you become experienced without ever trying? After all, this is a fairly technical forum.

Did you never notice posts by novices having problems following guides?
Envoyé depuis mon GT-I9300 avec Tapatalk 4

Rekoil said:
Aw come on guys, it's not that difficult of a guide to follow is it? Besides, how do you become experienced without ever trying? After all, this is a fairly technical forum.
Click to expand...
Click to collapse
I do agree with you completely.
When playing with partitions, manual way is the best way. And this is development forum. All possible info should be here. Noone should discourage you from posting any info, if you are warning the people that it's dangerous.

I seem to remember a time when people wouldn't host kernels or recoveries as update-able zips, because it didn't drive any knowledge into the users. Then, if something went wrong, they were ill equipped to deal with it. I'm all for automated tools, but see absolutely nothing wrong with sharing the manual know how.

Linux is best for all mods

Although I appreciate your efforts in creating this thread. I advice users to use this automatic tool and full of safety checks. It worked for me. And another thing, this is used to backup and restore your bootloader unlock status, drm keys and warranty!
http://forum.xda-developers.com/showthread.php?t=2292598
Greetings

Option58 said:
Although I appreciate your efforts in creating this thread. I advice users to use this automatic tool and full of safety checks. It worked for me. And another thing, this is used to backup and restore your bootloader unlock status, drm keys and warranty!
http://forum.xda-developers.com/showthread.php?t=2292598
Greetings
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2292598 said:
"Mac and Linux will not be supported."
Click to expand...
Click to collapse
Yeah, great option for Mac and Linux users.
Option58 said:
And another thing, this is used to backup and restore your bootloader unlock status, drm keys and warranty!
Click to expand...
Click to collapse
So does the manual method. In fact, I learned how to do it manually from studying that tool.

Rekoil said:
Yeah, great option for Mac and Linux users.
So does the manual method. In fact, I learned how to do it manually from studying that tool.
Click to expand...
Click to collapse
No one will ever learn without trying new things.
You can even break a phone by flashing it with proven programs not reading instructions carefully, so I find it OK to give the opportunity for the users not using windows especially as you have given good warnings.

Anyone have noted that in 5.34 commercial&journalist version ta file it's cust-reset.ta and in central europa simlock.ta?

Do I have to make a new TA backup after I have updated to .534 ?

Planet X said:
Do I have to make a new TA backup after I have updated to .534 ?
Click to expand...
Click to collapse
no

@ OP why /platform/msm_sdcc.1/by-name/TA why not point directly the mmcblk0p1 TA partition?
e.g.
This:- dd if=/dev/block/mmcblk0p1 of=TA.img
Instead of:-dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
I'm just nitpicking lol

Shaky156 said:
@ OP why /platform/msm_sdcc.1/by-name/TA why not point directly the mmcblk0p1 TA partition?
e.g.
This:- dd if=/dev/block/mmcblk0p1 of=TA.img
Instead of:-dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
I'm just nitpicking lol
Click to expand...
Click to collapse
Both are fine, but in case a new phone comes to market that for some reason puts boot image at /dev/block/mmcblk0p1 and TA at /dev/block/mmcblk0p2 or something like that, I thought it was best to just point to the symlink instead, so as to definitely make it future proof.

Thank you for this thread. I have backed up my TA for my new Z1 and stored it away.
malty

Planet X said:
Do I have to make a new TA backup after I have updated to .534 ?
Click to expand...
Click to collapse
Desperanto86 said:
no
Click to expand...
Click to collapse
How sure is that? I noticed that my TA did change with the update to .534 (based on md5sum). Can I freely mix-and-match my different TA backups (from the same device of course) with whatever (official) kernel version? Are they perhaps forward-compatible only (perhaps for downgrade prevention or something) and I should really keep the oldest one?

iconoclastnet said:
How sure is that? I noticed that my TA did change with the update to .534 (based on md5sum). Can I freely mix-and-match my different TA backups (from the same device of course) with whatever (official) kernel version? Are they perhaps forward-compatible only (perhaps for downgrade prevention or something) and I should really keep the oldest one?
Click to expand...
Click to collapse
TA is CONSTANT like IMEI!

Related

[GUIDE] Backup/Restore LG Optimus G EFS Partitions

LG Optimus G EFS Backup/Restore
Every rooted Optimus G user should backup their EFS partitions! Included in this thread is a flashable EFS backup script and terminal/adb commands if you want to do it manually. The script automates the entire backup of all 3 EFS partitions and then packs the files into a flashable zip for easy restoring later. Place this zip somewhere safe other than your sdcard!
Thanks goes to toastcfh for the script help and everyone in #lg-optimus-g that helped out with EFS testing.
Original Optimus G EFS Thread(ZERO EFS) - HERE
Background
You never know when your NV/EFS may stop working correctly. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. Our issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: IMEI, phone number, etc
m9kefs3 seems to be blank 00s​
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar). Confirmed working on TWRP 2.3.2.3/2.4.1.0 and CWM 6.0.2.7. Confirmed NOT working on CWM 6.0.1.5. Please check to make sure the backup zip worked and actually made a .zip file in /sdcard/EFS_Backup. Any issues please list what recovery and version you are using and please post the recovery.log.
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Code:
[B]Changelog[/B]
[I]v1 EFS backup zip[/I]:
backed up m9kefs1.img and m9kefs2.img then .tar'd them.
[I]v2 EFS backup zip[/I]:
backed up EFS then creates a flashable .zip containing the EFS partitions.
[I]v3 EFS backup zip[/I]:
zip script is now "safer" and should work on all Optimus G variants.
[I]v4 EFS backup zip[/I]:
backup zip now backs up m9kefs3. this is for "completeness" only.
I believe m9kefs3 contains no worthwhile data.
Thanks for posting this, it is very much needed and all OG users must have their EFS partitions backed up. And i can confirm that m9kefs3 doesnt contains anything except zeroes, still its good to have it backed up
I'm on CWM 6.0.1.5, what is the newest CWM version that works the the Canadian LGOG variants that doesn't give sd-ext mount errors?
I tried 6.0.1.7 but got constant errors.
jiexi said:
I'm on CWM 6.0.1.5, what is the newest CWM version that works the the Canadian LGOG variants that doesn't give sd-ext mount errors?
I tried 6.0.1.7 but got constant errors.
Click to expand...
Click to collapse
I also get sd-ext mount errors on my Sprint Optimus G(ls970). The errors don't seem to get in the way of anything.. seems it's just visually annoying. I'd love to see official TWRP versions for LGOG device.
autoprime said:
I also get sd-ext mount errors on my Sprint Optimus G(ls970). The errors don't seem to get in the way of anything.. seems it's just visually annoying. I'd love to see official TWRP versions for LGOG device.
Click to expand...
Click to collapse
Exactly! 720p screen for viewing errors
Some information: flashable zip does work correctly on official at&t twrp 2.4.2.0 on my rogers e971. sdcard/EFS_Backup only the 3 .img files and no zip
billybest said:
Some information: flashable zip does work correctly on official at&t twrp 2.4.2.0 on my rogers e971. sdcard/EFS_Backup only the 3 .img files and no zip
Click to expand...
Click to collapse
Thanks for the update. Apparently the 7z binary Im using in the script is dynamic.. and won't work with everyones setup. All my tests were done using CFX 4.2.2... seems there's stuff in that rom not found in some other LGOG roms. You will just have to dd the partitions if you ever need to restore. I guess at this point.. consider a working flashable .zip a "bonus" :-/
Also... the newest FreeGee app in the Play store supports EFS backup.. also backs up 3 separate .img files. :good:
The official TWRP for the Sprint LGOG also has EFS backup support added into the normal backup section. I would *think* this would run on Canadian LGOG's... you guy's don't have external SD right?
We have external sd. There is no sd card slot on my Canadian Rogers E971 phone.
Just backed em up using the FreeGee app.. Aren't EFS flashed every time you flash a ROM?
geokilla said:
Just backed em up using the FreeGee app.. Aren't EFS flashed every time you flash a ROM?
Click to expand...
Click to collapse
No.
Thanks for this great tutorial!
I've been having an issue with LTE on my Rogers LGOG. I've tried KDZ-ing back to stock, factory resets multiple times, many different ROMs, and I can't seem to get LTE any longer. It was working before the data partition got damaged though, causing me to need to factory reset for the first time a couple days ago. I believe after that this started to happed.
Just wondering if anyone has a stock clean Rogers EFS backup I could use, or modify and use, if possible. Or if there is something else I could try. I've tried various radios, wiping caches in between, ensured everything like APN and setting were correct, even got Rogers to re-push my account. My SIM is fine in my roommate's HTC One X for LTE right away, and his SIM card is NOT fine in my LGOG, no LTE.
Not sure if the EFS is the only thing left or not. Even after multiple factory resets and everything it seems like this is the only thing left that will solve the issue!
Thanks to all!
Sent from my Optimus G using xda app-developers app
hv6478 said:
Thanks for this great tutorial!
I've been having an issue with LTE on my Rogers LGOG. I've tried KDZ-ing back to stock, factory resets multiple times, many different ROMs, and I can't seem to get LTE any longer. It was working before the data partition got damaged though, causing me to need to factory reset for the first time a couple days ago. I believe after that this started to happed.
Just wondering if anyone has a stock clean Rogers EFS backup I could use, or modify and use, if possible. Or if there is something else I could try. I've tried various radios, wiping caches in between, ensured everything like APN and setting were correct, even got Rogers to re-push my account. My SIM is fine in my roommate's HTC One X for LTE right away, and his SIM card is NOT fine in my LGOG, no LTE.
Not sure if the EFS is the only thing left or not. Even after multiple factory resets and everything it seems like this is the only thing left that will solve the issue!
Thanks to all!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Just wanted to mention this has now been FIXED! Thanks to some hard work from autoprime, Paulicat and a little by me (lol) I'm fully back on LTE. Will have some documentation about this issue in the next little while as we confirm more information about the issue.
need help no 3G/LTE
I bought an F180L from Hong-Kong. It is a Korean version (U+) LG Optimus G. When I turned on the phone (before I put sim into) offered me to upgrade it. After upgrade there is no 3G/LTE. I have tried almost everything (rooted, unlocked bootloader, installed KDZ, intsalled stock and other ROMs) nothing worked.
I read about backup/restore efs, but I don't have efs backed up, so nothing to restore it. I tried to find old ROM (F180L 10q) to make a backup of efs, but I wasn't able to find any KDZ file to make 3G/LTE working.
I'm not a beginner rooting, unlocking phones but I need a tutorial how to make it working. Luckily I know my IMEI, Baseband, kernel, software version, but nothing else. Is it possible to fix this problem.
[email protected]
Best,
Cope007
autoprime said:
LG Optimus G EFS Backup/Restore
Every rooted Optimus G user should backup their EFS partitions! Included in this thread is a flashable EFS backup script and terminal/adb commands if you want to do it manually. The script automates the entire backup of all 3 EFS partitions and then packs the files into a flashable zip for easy restoring later. Place this zip somewhere safe other than your sdcard!
Thanks goes to toastcfh for the script help and everyone in #lg-optimus-g that helped out with EFS testing.
Original Optimus G EFS Thread(ZERO EFS) - HERE
Background
You never know when your NV/EFS may stop working correctly. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. Our issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: IMEI, phone number, etc
m9kefs3 seems to be blank 00s​
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar). Confirmed working on TWRP 2.3.2.3/2.4.1.0 and CWM 6.0.2.7. Confirmed NOT working on CWM 6.0.1.5. Please check to make sure the backup zip worked and actually made a .zip file in /sdcard/EFS_Backup. Any issues please list what recovery and version you are using and please post the recovery.log.
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Code:
[B]Changelog[/B]
[I]v1 EFS backup zip[/I]:
backed up m9kefs1.img and m9kefs2.img then .tar'd them.
[I]v2 EFS backup zip[/I]:
backed up EFS then creates a flashable .zip containing the EFS partitions.
[I]v3 EFS backup zip[/I]:
zip script is now "safer" and should work on all Optimus G variants.
[I]v4 EFS backup zip[/I]:
backup zip now backs up m9kefs3. this is for "completeness" only.
I believe m9kefs3 contains no worthwhile data.
Click to expand...
Click to collapse
Will this work on the LG Options G Pro E980?
n0rthstar88 said:
Will this work on the LG Options G Pro E980?
Click to expand...
Click to collapse
probably not.. but id need a partition list from the optimus pro first to correctly respond.
my efs backup script for the lg optimus g might work instead. btu again.. ill have to see your partition list first.
run the code below in adb shell. paste output in pastebin.. post link here.
ls -al /dev/block/platform/msm_sdcc.1/by-name/
autoprime said:
probably not.. but id need a partition list from the optimus pro first to correctly respond.
my efs backup script for the lg optimus g might work instead. btu again.. ill have to see your partition list first.
run the code below in adb shell. paste output in pastebin.. post link here.
ls -al /dev/block/platform/msm_sdcc.1/by-name/
Click to expand...
Click to collapse
I ran the command and this is what I got. I have F240L!
Code:
lrwxrwxrwx root root 1970-01-02 15:05 DDR -> /dev/block/mmcblk0
p30
lrwxrwxrwx root root 1970-01-02 15:05 aboot -> /dev/block/mmcbl
k0p5
lrwxrwxrwx root root 1970-01-02 15:05 bnr -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 1970-01-02 15:05 boot -> /dev/block/mmcblk
0p7
lrwxrwxrwx root root 1970-01-02 15:05 cache -> /dev/block/mmcbl
k0p24
lrwxrwxrwx root root 1970-01-02 15:05 drm -> /dev/block/mmcblk0
p15
lrwxrwxrwx root root 1970-01-02 15:05 eksst -> /dev/block/mmcbl
k0p22
lrwxrwxrwx root root 1970-01-02 15:05 encrypt -> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 1970-01-02 15:05 factory -> /dev/block/mmc
blk0p19
lrwxrwxrwx root root 1970-01-02 15:05 fota -> /dev/block/mmcblk
0p31
lrwxrwxrwx root root 1970-01-02 15:05 fsg -> /dev/block/mmcblk0
p29
lrwxrwxrwx root root 1970-01-02 15:05 grow -> /dev/block/mmcblk
0p38
lrwxrwxrwx root root 1970-01-02 15:05 lcdlog -> /dev/block/mmcb
lk0p36
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs1 -> /dev/block/mmc
blk0p12
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs2 -> /dev/block/mmc
blk0p13
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs3 -> /dev/block/mmc
blk0p14
lrwxrwxrwx root root 1970-01-02 15:05 misc -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1970-01-02 15:05 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1970-01-02 15:05 modemst1 -> /dev/block/mm
cblk0p10
lrwxrwxrwx root root 1970-01-02 15:05 modemst2 -> /dev/block/mm
cblk0p11
lrwxrwxrwx root root 1970-01-02 15:05 mpt -> /dev/block/mmcblk0
p32
lrwxrwxrwx root root 1970-01-02 15:05 pad -> /dev/block/mmcblk0
p9
lrwxrwxrwx root root 1970-01-02 15:05 persist -> /dev/block/mmc
blk0p26
lrwxrwxrwx root root 1970-01-02 15:05 rct -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 1970-01-02 15:05 recovery -> /dev/block/mm
cblk0p28
lrwxrwxrwx root root 1970-01-02 15:05 reserved -> /dev/block/mm
cblk0p37
lrwxrwxrwx root root 1970-01-02 15:05 rpm -> /dev/block/mmcblk0
p6
lrwxrwxrwx root root 1970-01-02 15:05 rpmbak -> /dev/block/mmcb
lk0p34
lrwxrwxrwx root root 1970-01-02 15:05 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1970-01-02 15:05 sbl2 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 1970-01-02 15:05 sbl3 -> /dev/block/mmcblk
0p4
lrwxrwxrwx root root 1970-01-02 15:05 sns -> /dev/block/mmcblk0
p16
lrwxrwxrwx root root 1970-01-02 15:05 ssd -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1970-01-02 15:05 system -> /dev/block/mmcb
lk0p23
lrwxrwxrwx root root 1970-01-02 15:05 tombstones -> /dev/block/
mmcblk0p27
lrwxrwxrwx root root 1970-01-02 15:05 tz -> /dev/block/mmcblk0p
8
lrwxrwxrwx root root 1970-01-02 15:05 tzbak -> /dev/block/mmcbl
k0p33
lrwxrwxrwx root root 1970-01-02 15:05 userdata -> /dev/block/mm
cblk0p25
aatish said:
I ran the command and this is what I got. I have F240L!
Code:
lrwxrwxrwx root root 1970-01-02 15:05 DDR -> /dev/block/mmcblk0
p30
lrwxrwxrwx root root 1970-01-02 15:05 aboot -> /dev/block/mmcbl
k0p5
lrwxrwxrwx root root 1970-01-02 15:05 bnr -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 1970-01-02 15:05 boot -> /dev/block/mmcblk
0p7
lrwxrwxrwx root root 1970-01-02 15:05 cache -> /dev/block/mmcbl
k0p24
lrwxrwxrwx root root 1970-01-02 15:05 drm -> /dev/block/mmcblk0
p15
lrwxrwxrwx root root 1970-01-02 15:05 eksst -> /dev/block/mmcbl
k0p22
lrwxrwxrwx root root 1970-01-02 15:05 encrypt -> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 1970-01-02 15:05 factory -> /dev/block/mmc
blk0p19
lrwxrwxrwx root root 1970-01-02 15:05 fota -> /dev/block/mmcblk
0p31
lrwxrwxrwx root root 1970-01-02 15:05 fsg -> /dev/block/mmcblk0
p29
lrwxrwxrwx root root 1970-01-02 15:05 grow -> /dev/block/mmcblk
0p38
lrwxrwxrwx root root 1970-01-02 15:05 lcdlog -> /dev/block/mmcb
lk0p36
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs1 -> /dev/block/mmc
blk0p12
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs2 -> /dev/block/mmc
blk0p13
lrwxrwxrwx root root 1970-01-02 15:05 m9kefs3 -> /dev/block/mmc
blk0p14
lrwxrwxrwx root root 1970-01-02 15:05 misc -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1970-01-02 15:05 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1970-01-02 15:05 modemst1 -> /dev/block/mm
cblk0p10
lrwxrwxrwx root root 1970-01-02 15:05 modemst2 -> /dev/block/mm
cblk0p11
lrwxrwxrwx root root 1970-01-02 15:05 mpt -> /dev/block/mmcblk0
p32
lrwxrwxrwx root root 1970-01-02 15:05 pad -> /dev/block/mmcblk0
p9
lrwxrwxrwx root root 1970-01-02 15:05 persist -> /dev/block/mmc
blk0p26
lrwxrwxrwx root root 1970-01-02 15:05 rct -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 1970-01-02 15:05 recovery -> /dev/block/mm
cblk0p28
lrwxrwxrwx root root 1970-01-02 15:05 reserved -> /dev/block/mm
cblk0p37
lrwxrwxrwx root root 1970-01-02 15:05 rpm -> /dev/block/mmcblk0
p6
lrwxrwxrwx root root 1970-01-02 15:05 rpmbak -> /dev/block/mmcb
lk0p34
lrwxrwxrwx root root 1970-01-02 15:05 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1970-01-02 15:05 sbl2 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 1970-01-02 15:05 sbl3 -> /dev/block/mmcblk
0p4
lrwxrwxrwx root root 1970-01-02 15:05 sns -> /dev/block/mmcblk0
p16
lrwxrwxrwx root root 1970-01-02 15:05 ssd -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1970-01-02 15:05 system -> /dev/block/mmcb
lk0p23
lrwxrwxrwx root root 1970-01-02 15:05 tombstones -> /dev/block/
mmcblk0p27
lrwxrwxrwx root root 1970-01-02 15:05 tz -> /dev/block/mmcblk0p
8
lrwxrwxrwx root root 1970-01-02 15:05 tzbak -> /dev/block/mmcbl
k0p33
lrwxrwxrwx root root 1970-01-02 15:05 userdata -> /dev/block/mm
cblk0p25
Click to expand...
Click to collapse
ok going to be hard to say without actually seeing the actual partitions... because you have both m9kefs1/2/3 and modemst1/2 . your efs is either m9kefs1/2/3 or modemst1/2... the optimus g used m9kefs1/2/3... the g2/nexus 5 uses modemst1/2.
im going to guess and say lg og pro uses m9kefs1/2/3 tho(same as lgog)...
if not.. then the g2/nexus 5 efs backup would work - http://forum.xda-developers.com/showthread.php?t=2514095
if u wanna run both.. then send me the backup zips it creates.. i could look thru them and give you an exact answer on which one to keep. again.. im leaning towards your efs being in m9kefs1/2/3 tho.. which means this lgog backup method would work.
autoprime said:
ok going to be hard to say without actually seeing the actual partitions... because you have both m9kefs1/2/3 and modemst1/2 . your efs is either m9kefs1/2/3 or modemst1/2... the optimus g used m9kefs1/2/3... the g2/nexus 5 uses modemst1/2.
im going to guess and say lg og pro uses m9kefs1/2/3 tho(same as lgog)...
if not.. then the g2/nexus 5 efs backup would work - http://forum.xda-developers.com/showthread.php?t=2514095
if u wanna run both.. then send me the backup zips it creates.. i could look thru them and give you an exact answer on which one to keep. again.. im leaning towards your efs being in m9kefs1/2/3 tho.. which means this lgog backup method would work.
Click to expand...
Click to collapse
I have actually able to extract my efs modem file using a script which was made for LGOG i got back 3 files one is larger 65Meg file others are 3 mb each approx.
I think you are right that it uses m9kefs1/2/3 though I am not sure what it means but can you help me in one thing? I want to flash other stock rom than my own which has less carrier stuff (specially korean U+) and is in english entierly including the dialpad, sms limit and annoying call to korea or local call options!
but i have like tried telcel, claro, panama, hong kong and indian roms on my cell but after flashing the modem i can't seem to get it working. e.g. panama takes the modem i get the signal but when i tried dialing or pickup a call it crashes!
I am going back to korean f240L but i really like to leave it!
here is the link to download modem
https://www.dropbox.com/s/9p9dz3p0dyd1m65/modemBackup.rar
thank you in advance!
is this possible to do with LG Optimus LTE2? Can you tell me how to actually find the EFS parition to be sure to backup?
pls help
buddy, i need some help from you...i have messed up my E970 phone's network.
Actually, i messed up with its EFS parititon and now i am not getting any network in my phone. My phone is ON, everything working but it is not detecting any sim
i read on XDA forum and got that i need to replace my EFS paritions again with system actual EFS partition file.
Any user friend who has E970 and who is rooted, pls download below file and run in recovery to back up the phone's EFS parition, then pls mail me that backed up EFS parition file so that i can replace it to run my sim card:
http://dl.xda-developers.com/attach.../8/4/9/9/Optimus_G_Create_Flashable_EFSv4.zip
pls download, its only 1 MB file and it will create a single file of small size (in KBs), that file will be placed in /sd card/ EFS_backup
pls mail me that file to save my phone...pls help ppl...it will not take much of your time...help

ZTE Z995 Overture custom recovery

EDIT: Here's the recovery thread.
Original post:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.
Nobody?
METDeath said:
Nobody?
Click to expand...
Click to collapse
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.
cooldudezach said:
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.
Click to expand...
Click to collapse
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.
METDeath said:
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.
Click to expand...
Click to collapse
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
METDeath said:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.
Click to expand...
Click to collapse
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy
cooldudezach said:
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy
Click to expand...
Click to collapse
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
Thanks! So does your phone boot normally, or does it bootloop? I wasn't sure when you wrote that if you were just referring to the recovery boot or not. FTM is integrated with boot.img, which is why i am confused lol.
I'm just trying to figure out what's wrong exactly so I can get your phone up and running.
If you want to hop into irc chac #zte8930 on freenode, that's where I hang out, and where the devs for this group of phones also hangout.
For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.
chongbos said:
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.
Click to expand...
Click to collapse
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
thanks.sorry for my poor english!
---------- Post added at 10:13 AM ---------- Previous post was at 10:09 AM ----------
METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
oh,i have been focus on this forum for a long time,and now i have found it.thank u a lot.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!
chongbos said:
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!
Click to expand...
Click to collapse
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!
METDeath said:
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!
Click to expand...
Click to collapse
hah，it's really funny to met u.
i will back contact u~~~~
thanks.
Hmmmm METdeath, perhaps you could enlighten me (pm) the whereabouts of said recovery and other useful info.
If wanted a custom recovery and ROM on this phone since day 1 . I kinda gave up on any hope for it. Please any information to lead me in the correct direction would be greatly appreciated.
METDeath said:
For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.
Click to expand...
Click to collapse
Where is a link to this recovery?
Does anybody know where to get a firmware for new ZTE devices, like Z995, Z993, z740 etc?
Hello Help PLZ!!
Hello, I have a softed bricked zte overture z995. I saw in one of your replies you are familiar with reflashing this ROM. Is there any possible way that you can help guide me in fixing this problem? I'm not too familiar with all the concepts. I will be forever grateful!!! THanks!
~Caleb
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
Updated first post with the URL to the recovery.

[APP] Boot Logo Changer [2016/04/05]

Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the P901, but should work on other Galaxy Note Pro 12.2s.
If in doubt, check to see if your PARAM partition is mmcblk0p8.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Note Pro 12.2.
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy Note Pro 12.2 display is 2560x1600.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select P901-BootLogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: P901-BootLogoChanger.zip
Mega: P901-BootLogoChanger.zip
Great work.
emremutlu said:
Great work.
Click to expand...
Click to collapse
Thanks!
It was working. Now unable to boot to twrp. Can get to download and Odin is flashing. Will a current firmware Odin flash get me booting again? Thank you
Sent from my Nexus 7 2013 using XDA-Developers mobile app
amityg said:
It was working. Now unable to boot to twrp. Can get to download and Odin is flashing. Will a current firmware Odin flash get me booting again? Thank you
Sent from my Nexus 7 2013 using XDA-Developers mobile app
Click to expand...
Click to collapse
Got it booting again by using the param t311 Odin file. Now I will fix with the backup file. Thank you. I still going to use custom logo.jpg as it looks clean.
Sent from my Nexus 7 2013 using XDA-Developers mobile app
gcrutchr said:
Boot Logo Changer
This has only been tested on the P901, but should work on other Galaxy Note Pro 12.2s.
If in doubt, check to see if your PARAM partition is mmcblk0p8.
Click to expand...
Click to collapse
On P900 can confirm PARAM is still partition mmcblk0p8.
[email protected]:/ $ ls -l /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2016-07-13 15:11 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-07-13 15:11 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-07-13 15:11 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-07-13 15:11 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-07-13 15:11 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-07-13 15:11 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-07-13 15:11 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-07-13 15:11 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-07-13 15:11 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-07-13 15:11 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-07-13 15:11 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-07-13 15:11 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-07-13 15:11 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-07-13 15:11 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-07-13 15:11 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-07-13 15:11 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-07-13 15:11 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-07-13 15:11 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs3 -> /dev/block/mmcblk0p6
So this should work, will try and report back.
Edit: worked just fine, p900 users are safe.
Gatsrom said:
On P900 can confirm PARAM is still partition mmcblk0p8.
[email protected]:/ $ ls -l /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2016-07-13 15:11 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-07-13 15:11 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-07-13 15:11 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-07-13 15:11 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-07-13 15:11 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-07-13 15:11 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-07-13 15:11 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-07-13 15:11 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-07-13 15:11 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-07-13 15:11 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-07-13 15:11 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-07-13 15:11 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-07-13 15:11 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-07-13 15:11 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-07-13 15:11 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-07-13 15:11 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-07-13 15:11 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-07-13 15:11 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs3 -> /dev/block/mmcblk0p6
So this should work, will try and report back.
Edit: worked just fine, p900 users are safe.
Click to expand...
Click to collapse
Great to here it worked!
Make sure you keep a backup of the original PARAM file just in case you want to go back to stock.
where do i locate tmp folder with logo.jpg to replace with another logo
gcrutchr said:
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the P901, but should work on other Galaxy Note Pro 12.2s.
If in doubt, check to see if your PARAM partition is mmcblk0p8.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Note Pro 12.2.
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy Note Pro 12.2 display is 2560x1600.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select P901-BootLogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: P901-BootLogoChanger.zip
Mega: P901-BootLogoChanger.zip
Click to expand...
Click to collapse
anayajade said:
Click to expand...
Click to collapse
It's in the .zip file
Back up
Hi, thanks for thisgreat work. Running a modified version of stock rom lollipop, where can I find my tmp folder with logo.jpg to make a backup incase something goes wrong?
Edit: re-read the op and understood the second time. Works great on p900
bricked
hi, I think I bricked my p900 using this zip file. At first everything went good, then I tried a different logo.png in the temp file and now my p900 wont boot at all, it goes in download mode only, not even recovery works.
Tried odin back to stock but still nothing.
I was on civZ p900 lollipop 5.0.2 with latest twrp recovery before. Can anyone help me please
coco1476 said:
hi, I think I bricked my p900 using this zip file. At first everything went good, then I tried a different logo.png in the temp file and now my p900 wont boot at all, it goes in download mode only, not even recovery works.
Tried odin back to stock but still nothing.
I was on civZ p900 lollipop 5.0.2 with latest twrp recovery before. Can anyone help me please
Click to expand...
Click to collapse
Please explain what you did the 1st time.
What size is the new logo.png (2560x1600 ?) ; also what is the file size of the logo.png?
How did you replace the logo.png file?
How did you try to go back to stock? With a custom rom or a stock .md5 rom?
gcrutchr said:
Please explain what you did the 1st time.
What size is the new logo.png (2560x1600 ?) ; also what is the file size of the logo.png?
How did you replace the logo.png file?
How did you try to go back to stock? With a custom rom or a stock .md5 rom?
Click to expand...
Click to collapse
Hi, I manage to find a complete firmware including pit, bootloader and csc to install with odin and it's alive again.
The new logo was 2560x1600 but I can't recall the file size. I used ES File Explorer apk to copy the new logo image to the temp folder in the zip file and deleted the original logo.png.
I downloaded the latest stock firmare on Sam mobile for my p900 and used odin, everything went perfect with odin but it rebooted in download mode again, no access to recovery, I tried every methods I know to boot in recovery but it didn't work.
So I found a complete Arabic 4.4.2 stock firmware and used odin and boom everything is back an running now, got 5.0.2 OTA update up and running
coco1476 said:
Hi, I manage to find a complete firmware including pit, bootloader and csc to install with odin and it's alive again.
The new logo was 2560x1600 but I can't recall the file size. I used ES File Explorer apk to copy the new logo image to the temp folder in the zip file and deleted the original logo.png.
I downloaded the latest stock firmare on Sam mobile for my p900 and used odin, everything went perfect with odin but it rebooted in download mode again, no access to recovery, I tried every methods I know to boot in recovery but it didn't work.
So I found a complete Arabic 4.4.2 stock firmware and used odin and boom everything is back an running now, got 5.0.2 OTA update up and running
Click to expand...
Click to collapse
Good to hear you are back up and running ok. Make sure you copy the backup file of the logo partition to your PC for safe keeping.
coco1476 said:
Hi, I manage to find a complete firmware including pit, bootloader and csc to install with odin and it's alive again.
The new logo was 2560x1600 but I can't recall the file size. I used ES File Explorer apk to copy the new logo image to the temp folder in the zip file and deleted the original logo.png.
I downloaded the latest stock firmare on Sam mobile for my p900 and used odin, everything went perfect with odin but it rebooted in download mode again, no access to recovery, I tried every methods I know to boot in recovery but it didn't work.
So I found a complete Arabic 4.4.2 stock firmware and used odin and boom everything is back an running now, got 5.0.2 OTA update up and running
Click to expand...
Click to collapse
Any chance you can share this firmware? I'm in the same boat but I can't find a stock firmware that gets me running again. I've downloaded and flashed a couple but I can still only get to download mode.
Nikoli4 said:
Any chance you can share this firmware? I'm in the same boat but I can't find a stock firmware that gets me running again. I've downloaded and flashed a couple but I can still only get to download mode.
Click to expand...
Click to collapse
Sorry to hear that it happened to you also. I don't have this tablet anymore but if I remember correctly, this is the firmware I used,
https://www.androidfilehost.com/?fid=24269982087019604
Hope you will be good and running in no time
Awesome, thanks! Downloading now. I'd like to find a XAR version of this too, but hopefully this gets me working again.
coco1476 said:
Sorry to hear that it happened to you also. I don't have this tablet anymore but if I remember correctly, this is the firmware I used,
https://www.androidfilehost.com/?fid=24269982087019604
Hope you will be good and running in no time
Click to expand...
Click to collapse
That did the trick, I'm back up and running. Thanks again, I appreciate it.
Nikoli4 said:
That did the trick, I'm back up and running. Thanks again, I appreciate it.
Click to expand...
Click to collapse
Glad I can help and if wait a bit it will give you 2 or 3 system update that will bring you back to the latest firmware from Samsung, I think it's 5.0.1
Edit: it's 5.0.2
I created a bunch of splash screens and figured I'd share. I tested all of these on my p900 and they all worked for me. Check them out here. I also added the recovery software and Odin that I used to unbrick mine after a bad flash in case anyone else needs it. Thanks to coco1476 for the original link.

[HELP] Create a nandroid backup (Xperia C6 Clone/China)

Hello.
So, as I described here, I success got root on this device. Now, I want a full backup in case things going bad. And obvious, a way to restore this backup.
I was searching for days for a ROM, but it simply don't exist (yet). This model have an identification (alps l1 mp6 v2 gxq6580 weg l p69) wich is used in some other devices (includings Samsung clones), so, I checked all the ROMs I found looking into /system partition on my device and comparing with /system image of the ROMs (I used SuperR's Kitchen), and none of them are equal, I mean, a lot of files (includind build.prop) are different, so there is a great chance to brick my phone if I use it.
Even if it is found, I can't restore with SP Flash Tools, because it don't work with this phone. I tried to readback, but it recognizes but never start. As the phone is a MT6580 based SoC, maybe is compatability issue also. MTK Droid Tools don't work also. It recognizes, but can't do anything (don't generate scatter, don't root, don't nothing), again maybe a compatibility also.
The stock recovery have no option to backup, and I'm afraid to flash a CWM or TWRP, because I don't know much about porting these things, and I don't have much information about partitions and these things yet. ADB while in recovery give me an unauthorized device, by the way.
The phone accept fastboot commands, but don't accept the 'fastboot boot image.img", to try a temporary recovery, it only accept the 'fastboot flash image.img'. As sayed on the thread above, the bootloader is now unlocked, by the way.
So... this the situation... Can't have backup for now. If it help you to help me, there is the result of ls -all /dev/block/platform/mtk-msdc.0/by-name/ command in adb shell:
Code:
1|[email protected]_weg_l:/ # ls -all /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-03-30 00:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-30 00:16 cache -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-30 00:16 expdb -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-30 00:16 flashinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-30 00:16 frp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-30 00:16 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-30 00:16 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-30 00:16 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-30 00:16 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-30 00:16 nvdata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-30 00:16 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-30 00:16 oemkeystore -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-30 00:16 para -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-30 00:16 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-30 00:16 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-30 00:16 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-30 00:16 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-30 00:16 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-30 00:16 secro -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-30 00:16 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-30 00:16 userdata -> /dev/block/mmcblk0p20
[email protected]_weg_l:/ #
I sucessfully (I think) dump a boot image with dd command (dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img), but I'm not sure it is 100% perfect and if it can be safely used to restore (and how to restore... maybe 'fastboot flash'?). Maybe I can dump some other images, but I don't tried yet.
If you need any other information, I reply in almost same time.
Thanks in advice.
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
romulocarlos said:
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
Click to expand...
Click to collapse
Hello, i have recently posted a complete ROM on needrom. https://www.needrom.com/download/sony-xperia-c6-clone-mt6580/
i guess that is the one your are looking for. Good luck and sorry for my bad englich.
Help
Rom is corrupted, is not it? It's working? tell me how to download, I thank you

Please help its a request.

Hi friends,
I lost imei on my moto g5 because I had installed oreo 8.1 rome on it.
while I was trying to fix the imei on its stock rom that I had flash after flashing oreo 8.1.
I thought dhob -> /dev/block/mmcblk0p20
and hob -> /dev/block/mmcblk0p19 are the two files that contain all the data of IMEI and network.
so I searched on web and foun these two files of some other moto device. I went ahead and flashed these two files onto my file. which actually didn't resolve the issue. but gave me some more issue. now after doing this fingerprint stoped working.
Then I went ahead and ran fastboot clear all command from the cmd in fast boot thinking that it might remove these two file that I have flashed. but by doing that I lost wifi as well.
now the situation is this that there is no imei on my moto g5, wifi is not working, finger print senser is not working.
so finally i relocked the boot loader and thought maybe I will take it to service center and they will fix it. but they found that it is out of warranty and asked for money which is 80% cost of the mobile phone. actually they are telling me to replace the mother board.
I know there should be someone on XDA who can actually help me. I understand I have messed it real bad. But I really need this phone.
so this is my final request to all XDA members and all DEV's out there please help me.
According to my knowledge I will need the back up of some files from a working moto G5 cedric, That I can flash to my moto g5 cedric:
here are the files that I need:
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
persist -> /dev/block/mmcblk0p29
rpm -> /dev/block/mmcblk0p5
Here is the script to take the back up:
This one is for about. please make the changes accordingly to take the backup for others:
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4.img"
you will have to use this script on fastboot in cmd. while your phone is turned on and first you will have to give fastboot root access.
Again This is a request someone please please please help.....:crying::crying::crying:
If you need any help in taking backup please reply I will surely help with that.
Requirements:
- Device has to be rooted, with USB debugging enabled.
- Motorola fastboot (see attachment).
- ADB installed, minimal or the full ADK.
You can search the forum to find how to meet these requirements or for the terms described in this post beginning here:
http://forum.xda-developers.com/show....php?t=2558638
Weirdly when I backed up the /dev/mmcblk0p29 persist partition it was 8MB, meanwhile when I backed up the /dev/block/bootdevice/by-name/persist it was 32MB

Categories

Resources