Related
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!
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.
Hello. I was bricked my sm-p605, so I played enough. Can someone make full backup, I mean full - dd if=/dev/block/mmcblk0pxx /sdcard or so, I think I need all partitions, it doesn't mater what version of ROM, Please help me to fix it, Odin does not work, usb does't work to, I think I can flash it via twrp using "send terminal command" function with dd if=system.img of /dev/block/mmcblk0p23. And if you can please make files as partition names like dd if=/dev/block/mmcblk0p23 of=/sdcard(or so)/mmcblk0p23 or jus 0p23. Actually Odin does work, but I can't flash original firmware, I getting errors with sbl1.mbn. Sorry for my bad english and thanks.
I think I need repartition my device using right pit file, so do anyone know where can I get it?
Tautvaldas said:
Hello. I was bricked my sm-p605, so I played enough. Can someone make full backup, I mean full - dd if=/dev/block/mmcblk0pxx /sdcard or so, I think I need all partitions, it doesn't mater what version of ROM, Please help me to fix it, Odin does not work, usb does't work to, I think I can flash it via twrp using "send terminal command" function with dd if=system.img of /dev/block/mmcblk0p23. And if you can please make files as partition names like dd if=/dev/block/mmcblk0p23 of=/sdcard(or so)/mmcblk0p23 or jus 0p23. Actually Odin does work, but I can't flash original firmware, I getting errors with sbl1.mbn. Sorry for my bad english and thanks.
I think I need repartition my device using right pit file, so do anyone know where can I get it?
Click to expand...
Click to collapse
I need all packages except:
/dev/block/mmcblk0p23 \system
/dev/block/mmcblk0p26 \data
/dev/block/mmcblk0p14 \recovery
/dev/block/mmcblk0p15 /boot
So I think I need:
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p22
Please anyone help.
Can you not get your P605 to show up when you connect to Odin? Here is what I would do:
1. Try a different USB port
2. Try a different USB cable
3. Try a different pc
I see no reason why you should not be able to recover your tablet.
Download your firmware from here:
You just need to register to be able to download.
http://www.sammobile.com/firmwares/
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 me, I just bricked my lg k10 2017, and I urgently need a dump file from /dev/block/mmcblk0p7 , please back up this directory/patition ,and upload it to me
To make a backup you need to run this command on terminal if=/dev/block/mmcblk0p7 of=/sdcard/aboot.img , and pls send me the aboot.img via email [email protected]
aboot?
OP -> /dev/block/mmcblk0p48
boot -> /dev/block/mmcblk0p13
cache -> /dev/block/mmcblk0p47
cust -> /dev/block/mmcblk0p44
efuse -> /dev/block/mmcblk0p34
eksst -> /dev/block/mmcblk0p26
encrypt -> /dev/block/mmcblk0p27
expdb -> /dev/block/mmcblk0p18
factory -> /dev/block/mmcblk0p33
flashinfo -> /dev/block/mmcblk0p50
frp -> /dev/block/mmcblk0p45
ftm -> /dev/block/mmcblk0p4
keystore -> /dev/block/mmcblk0p23
laf -> /dev/block/mmcblk0p11
lgfota -> /dev/block/mmcblk0p31
lk -> /dev/block/mmcblk0p9
lk2 -> /dev/block/mmcblk0p10
lo_bak_go -> /dev/block/mmcblk0p17
logo -> /dev/block/mmcblk0p16
md1arm7 -> /dev/block/mmcblk0p42
md1dsp -> /dev/block/mmcblk0p41
md1img -> /dev/block/mmcblk0p40
md3img -> /dev/block/mmcblk0p43
metadata -> /dev/block/mmcblk0p39
misc2 -> /dev/block/mmcblk0p3
mpt -> /dev/block/mmcblk0p30
nvcfg -> /dev/block/mmcblk0p37
nvdata -> /dev/block/mmcblk0p38
nvram -> /dev/block/mmcblk0p5
oemkeystore -> /dev/block/mmcblk0p20
para -> /dev/block/mmcblk0p12
persist -> /dev/block/mmcblk0p36
persist_lg -> /dev/block/mmcblk0p29
proinfo -> /dev/block/mmcblk0p1
protect1 -> /dev/block/mmcblk0p7
protect2 -> /dev/block/mmcblk0p8
rct -> /dev/block/mmcblk0p32
recovery -> /dev/block/mmcblk0p14
recoverybak -> /dev/block/mmcblk0p15
seccfg -> /dev/block/mmcblk0p19
secro -> /dev/block/mmcblk0p21
spare1 -> /dev/block/mmcblk0p2
spare2 -> /dev/block/mmcblk0p6
spare3 -> /dev/block/mmcblk0p22
spare4 -> /dev/block/mmcblk0p28
spare5 -> /dev/block/mmcblk0p35
system -> /dev/block/mmcblk0p46
tee1 -> /dev/block/mmcblk0p24
tee2 -> /dev/block/mmcblk0p25
userdata -> /dev/block/mmcblk0p49
Click to expand...
Click to collapse
And if it's bricked, how you restore that partition?
CXZa said:
aboot?
And if it's bricked, how you restore that partition?
Click to expand...
Click to collapse
I 'll use lglaf in linux
CXZa said:
aboot?
And if it's bricked, how you restore that partition?
Click to expand...
Click to collapse
Protect1 and Protect2 is same? A backup?
JunioJsv said:
Protect1 and Protect2 is same? A backup?
Click to expand...
Click to collapse
Not quite the same. There are texts that say the partition name in them.
No idea if a copy from a different device works at all.
That is, what they are used for... these protects...
Have you tried LGUP using refurbish mode?
It should do some wiping before writing.
Or LGBridge?
>LGlaf
Haven't been able to write a partition with that, in windows.
It "writes", that is, it takes its time but it doesn't stick...
I could write into some partitions in terminal mode,
but not into boot and recovery etc.
Now, with root writing into those partitions is possible but useless.
Corrupted, not trusted, whatever errors if them are modified...
Bootloader...
CXZa said:
Not quite the same. There are texts that say the partition name in them.
No idea if a copy from a different device works at all.
That is, what they are used for... these protects...
Have you tried LGUP using refurbish mode?
It should do some wiping before writing.
Or LGBridge?
>LGlaf
Haven't been able to write a partition with that, in windows.
It "writes", that is, it takes its time but it doesn't stick...
I could write into some partitions in terminal mode,
but not into boot and recovery etc.
Now, with root writing into those partitions is possible but useless.
Corrupted, not trusted, whatever errors if them are modified...
Bootloader...
Click to expand...
Click to collapse
Lgup wont work in my case. Already "unblock" the phone or simply gave a dd if=/dev/block/mmcblk0p8 of=/ if=/dev/block/mmcblk0p7 with lglaf and the revible phone
JunioJsv said:
Lgup wont work in my case. Already "unblock" the phone or simply gave a dd if=/dev/block/mmcblk0p8 of=/ if=/dev/block/mmcblk0p7 with lglaf and the revible phone
Click to expand...
Click to collapse
:highfive:
I fixed the same problem with the help of this forum, Thank you so much!.