Related
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.
Thanks... a very useful guide. Bookmarked
WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!
I keep getting "md5sum: not found"
Put this in the general android section as it works across most devices. ..
Sent from my One V
Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.
I fixed it in adb
Sent from my SPH-L710 using xda premium
Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!
thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
CWM showing different versions
-Delete-
maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out
Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app
Thank you so much. You saved my phone.
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)
plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Nexus 10 (manta)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
Flashing can brick your phone
This will be removed after people report it is booting fine without bricking their phone
Click to expand...
Click to collapse
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.
espionage724 said:
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.
Click to expand...
Click to collapse
I warn people when I release an untested recovery on a given device
Most noobs tend to forget that flashing is not a safe operation. It can always turn into a nightmare
You can check the list of currently supported devices from main thread here: http://forum.xda-developers.com/showthread.php?t=2201860
And browse into the different device support forums
Till now, the warning never became true except when some people flashed the wrong file in their phone
This warning should keep noobs away from testing it
Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone
espionage724 said:
Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone
Click to expand...
Click to collapse
LoL
It is a generic copy paste message
Well, will you be the first to give a feedback ?
Phil3759 said:
Well, will you be the first to give a feedback ?
Click to expand...
Click to collapse
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
espionage724 said:
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
Click to expand...
Click to collapse
Thank you for the feedback (reached my daily limit for :good
Brightness:
Do you by case know the path for your device brightness file?
Not a big deal though as I can search / look for it in rc files. I used Samsung usual path, but it seems they used a different one for google devices
Battery:
Will check for the battery path used
Touch
It is supposed to be one finger to use
Interesting though...
Can any one run this in adb shell while in recovery
Or you can use the console terminal in aroma file manager while in recovery
Code:
find /sys/. -name '*bright*' >/sdcard/brightness.txt
Then
Code:
find /sys/. -name '*battery*' >/sdcard/battery.txt
And attach the resulting brightness.txt and battery.txt files on sdcard
About multi touch: i will look to allow only slot 0 to ignore second finger
Sent from my GT-I9100 using Tapatalk 2
Forget it. I found path in source
Sent from my GT-I9100 using Tapatalk 2
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/. -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Click to expand...
Click to collapse
see attached - is this what you're looking for?
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
Sorry I'm a bit out of sync with you -- but I've attached the one you asked for just before revising your post.
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
Result is attached. I'll run the other command in a moment.
Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
OK -- re-learning linux command line as I go (it's been many years!). Good to wake up that part of the brain again...
Had to modify command above: needed a space between ls and -l, and I'm assuming you want "/sys" up front in the fully qualified file name... Assuming that's all good, the new result is attached as battery2.txt
Let me know if this is what you need, or if anything else is needed. I've got some time to squeeze in a few of these today as needed. Also REALLY looking forward to trying this out on my N10 (and would love to see this on the Galaxy Nexus if ever possible!).
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:
Phil3759 said:
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:
Click to expand...
Click to collapse
Try the attached...
jonstrong said:
Try the attached...
Click to expand...
Click to collapse
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity
Phil3759 said:
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity
Click to expand...
Click to collapse
Great -- let me know if you need anything else -- I'm home today, and can pull some more if needed.
Does this recovery support USB OTG?
I must be in stupid mode today !!
Have been running Galaxy S3 with PhilZ Touch for some time now .... superb :good:
Got a new Nexus 10 last week and want it on there as well ..... stupid bit coming now
Downloaded latest version from this thread - but it shows as "philz_touch_5.00.7-manta.img"
Not a zip or a tar file for Odin ..... what am I missing from under my nose?
Homer
I flashed franco kernel nighltie r364 on a JB 4.2 stock rom on a Galaxy Nexus, now the internal SD won't mount..
Have I permanently lost all the data? can someone please explain how I can recover/resolve this.
I've tried to mount it in TWRP and it's unselected (default set to mount), yet after a reboot I still can't access the internal sdcard.
Also, no apps work, I guess it's cause they're all on the internal sdcard.
Finally the name 'legacy' appears under the sdcard0 folder (it actually looks like a file now with a golden star against it), I see this using root explorer; the only app that works.
If anyone can help it would be appreciated...
---
smash'n
SGS2 GT-I9100
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
beekay201 said:
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
Click to expand...
Click to collapse
I'll pm you, if you don't mind
---
smash'n
SGS2 GT-I9100
beekay201 said:
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
Click to expand...
Click to collapse
Thanks for poiting me in the direction of adb!
I swear I'll never mess with a Nexus again.
I resolved all I needed but took 12hrs and no sleep to get adb to recognise (with a bit of tom foolery) and pull the files we needed.
I"m just gona wipe the whole phone and start a fresh.
Now time to enjoy the rest of our hols.
At least we saved our child's photos.
Thanks again.
---
smash'n
SGS2 GT-I9100 (and never will be Galaxy Nexus)
UPDATE.
I just want to update this thread regarding my experience.
Firstly, this problem occured again!!
This is how I solved it;
[SOLVED]
Well I spent allnight/day (18hrs really)reading and conducting a whole host of procedures, from; using adb too resorting back to stock.
Needless to say nothing worked correctly!!
What I eventually did was to use WUGFRESH Galaxy Nexus Toolkit v1.6.4 and it stripped (reformatted) the phone and placed a clean stock firmware back.
I say reformatted hestitantly, as all other methods that I used and know of (from my time modding my S2) didn't work, at all (when applied to this phone) as each time the internal storage 'could not be mounted or accessed', I can only imagine something was severely corrupted.
WUGFRESH downloaded the necessary files and during its running, automatically indicated that some files could not be accessed or weren't present on the phone (I read this via the cmd screen on WUGFRESH), it then tx and loaded the necessary files (what I can describe as a reformat) and after all processes I rebooted and vola! access to internal storage regained.
Also, just to add, [before I started the process] the same WUGFRESH SW also allowed me to pull files from the internal storage (personal family photos and videos), even though adb wouldn't mount the storage or push or pull files from the phone, all other procedures/methods I tried wouldn't work either! WUGFRESH was the only one that worked.
After everything, I conducted a nandroid! what a headache, and it aint even my phone (it belongs to my fiancè).
Thanks for all the support in the thread, needless to say I hope all my experience in the last 18hrs helps someone else.
---
smash'n
You're holding it wrong. You should have read the stickies, but your goal wasn't to learn anything anyways so..
and another thing: not that I use it, but it's WUGFRESH toolkit - at least get the name right. It bothers me when people don't call stuff by their names.
don't create 2 threads for the same issue. Reported.
soz on the wrong naming of WUGFRESH.
REPORTED? Why? my two threads were ligit!, all posted in Q&A, based on the same issue but within two areas
1. stock recovery
2. this thread
---
smash'n
SGS2 GT-I9100
So it took you 18 hours and you never tried ADB or Fastboot by itself?
toolkits are nothing more than a front end hiding the commands from the user by using ADB and Fastboot...congrats on learning nothing in the process? I see nothing in your resolution that indicates that the GOOGLE provided tools would not work.
Sigh....another toolkit thread. YAY!
Pirateghost said:
So it took you 18 hours and you never tried ADB or Fastboot by itself?
toolkits are nothing more than a front end hiding the commands from the user by using ADB and Fastboot...congrats on learning nothing in the process? I see nothing in your resolution that indicates that the GOOGLE provided tools would not work.
Sigh....another toolkit thread. YAY!
Click to expand...
Click to collapse
YES, I tried adb cmds and bootloader/fastboot (as I mentioned above) same as I would on a S2, each time reverting back to stock on this nexus never gave access to the internal storage; this was the problem.
Hence I used a toolkit, and it worked.
I'm not an expert in modding android but I know some stuff, and this nexus wasn't playing to a rule book, as all the adb cmds and methods I found online (and are basic) never worked, no thread gave a solution that worked, similar google searchers.
I didn't go into this blind, but I never expected so much hassle modding this phone, as I rooted it and flashed a stock ROM weeks/months ago without problems.
As for learning anything (you're the 2nd person to mention it), I've learned a lot from the xda community (personally) and through threads.. though the issue I experienced was never written about in the sense I experienced it and had to resolve it.
---
smash'n
SGS2 GT-I9100
Hi guys im unsure if you would call me a noob since ive been playing with androids and custom ops for a while, however my girlfriend purchased an lg d855 (stock as a rock)and "all of a sudden" it failed to reboot, now from what i have found it appears to be quite unusual for this to happen but common for the os to crash into a boot freeze or boot loop, i have no complete load of download mode, it comes up with the little blue dots and the picture of the phone or whatever the symbol is. i can get it into fastboot for use with the adb or fastboot apps, i have obtained the stock LAF.img for the 32gb variant, the issue is that after the phone is connected and ready to send operations
i send the command
c:\adb\fastboot erase recovery >
erasing recovery>
FAILED <remote: failed to erase partition>
and on the phone it says
<start>
fastboot: processing commands
fastboot: getvarartition-type: recovery
fastboot erase: recovery
partition getsize 16777216 bytes
erasing card: 0x48000:0x8000
error: command never completed
error: command timeout error
error: command completed with errors
failed to send erase grp start address
mmc erase failed
<end>
so the question, what the hell does that mean, also if i try other commands it also failes to complete them such as erasing the laf file and or replacing it, i feel like i am mostlikely not the only one with this issue, i do have all the correct drivers installed, using the adb that i have which is 1.3 and one that comes with a kit of the sdk tools and all that, i feel like it is a phone issue more than computer as its failing to erase the mmc, i am wondering if there is other commands i could put in the phone to figure this out or if anyone knows what it all means i would greatly appreciate any help Thanks guys an gals.
iv tried also to load a custom recovery but cant do that because it comes up with incomplete bootloader on the phone, is anyone even able to help? i have no idea what the hell i am doing and nobody seems interested to try and help me.
Same problem here
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
ferreirix said:
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
Click to expand...
Click to collapse
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
tallman43 said:
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
Click to expand...
Click to collapse
I can start to see the light with the tuto you recommended thank you so much !
EDIT: THE DEVDB PROJECT HAS RISEN UP!
https://forum.xda-developers.com/moto-z-play/development/project-real-unbrick-hard-bricked-moto-t3927107
This is so easy to do, and can be sooo helpful if one day You will end with hard-brick.
If you have any questions send me a private message. :good:
Hey! My name is Jacob and I must tell you that there is one common problem with Moto Z Play - OTA after downgroading results in hardbrick :silly:
I have also bricked my device some days ago, since then I have gathered interesting info, probably all old and not so old blankflash files (these were used in the past to unbrick, but don't work now) and two tools, that allowed me to make proper rawprogram0, patch0 and gpt_main0.bin needed for making files, that will allow everyone to unbrick.
But this can be worth nothing without your help. Problem with unbricking, is that last OTA, updated chip security making unable to flash older chip firmware rendering all flashfiles useless. To make new one, I must get some files that are not present in the internet, but are present in ALL working phones. All I need is full mmcblk0 backup. If you want to help follow these easy-peasy instructions:
INFO: Procedure bellow excludes EFS, MODEMST1, MODEMST2, FSG, BACKUP partitions from backup. These are your phone specific partitions, that contain sensitive information like IMEI, serial numbers etc, but this guide shows how to avoid them while backing up so you don't have to worry about it
Prerequisites:
1. Your phone might be rooted (but doesn't have to be), definitelly should be working and not messed up too much.
2. You must have at least 32 GB micro sd card
3. Any ROM, even custom will be good, but if you have stock, you get +1 point
Steps:
1. If you have TWRP recovery, boot into it and go to step 2.
If you don't have, here is official one https://eu.dl.twrp.me/addison/ - rename it to "twrp.img" and boot to it with
Code:
fastboot boot twrp.img
2. Backup your /data partition and keep it in safe place
3. Format sdcard in ext4 (it is more robust and failsafe) or FAT32/exFAT (if you are on windows).[/URL]
4. Wipe /data on your phone and insert sdcard. Under "Mount" tab in TWRP, check box next to SD-CARD.
5. Open TWRP terminal emulator (It is in advamced tab), type "su" and run these command:
If you trust me that I won't do bad things with your IMEI:
Code:
dd if=/dev/block/mmcblk0 of=/[U][I]"Ext sd location here"[/I][/U]/Loader.img bs=4096
This just makes full-backup of your all partitions from Qualcomm chip.
OR
If you don't trust me:
Code:
dd if=/dev/block/mmcblk0p[B][COLOR="Red"]X[/COLOR][/B] of=/[B][COLOR="DeepSkyBlue"]Y[/COLOR][/B]/mmcblk0p[COLOR="Red"]X[/COLOR] bs=4096
Where X is number of partition from 1 to 54 BUT NOT: 27 (modemst1), 28 (modemst2), 29 (fsg)
and Y is location of your SD-CARD. This will only back up partitions without IMEI, and other phone-specific info.
6 Generated files will be HUGE (~27GB). Copy them to pc and upload to cloud. Maby https://mega.nz/ - probably only they have enough space for that file for free.
7 Post link here or send it to me via Private Message.
8 That's all! If you managed to get here, all comunity is grateful, :highfive: you will be included as biggest contribuor to the new thread I will make in near future!
If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
The only other way I know would be a USB C OTG adapter and a USB stick...
Artim_96 said:
If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive
Click to expand...
Click to collapse
Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
Thank you very much guys! You don't even know how much did you motivated me to continue research when I got your responses. If you will have any problem, ask me for advice - I will try to help. :highfive:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
In case of Camarda: ...
Code:
adb -d shell su -c busybox dd if=/dev/block/mmcblk0 bs=4096 > D:\mmc.bin
... should do the job, where "D:\mmc.bin" can be any other valid location on your pc.
To make this work, you must have root and busybox installed.
Bobernator said:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
Click to expand...
Click to collapse
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell
Artim_96 said:
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell
Click to expand...
Click to collapse
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, becouse of smaller size and auto merging archives
Bobernator said:
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, because of smaller size and auto merging archives
Click to expand...
Click to collapse
Would it help you to get /data too? It's my old phone, screen is quite damaged so there is nothing worth looking for on it. Plus it was completely wiped twice by flashing the firmware with flashfile and unlocking the bootloader again since flashing the firmware locked it.
Data partition is absolutely not needed, but thanks for asking!
zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?
Artim_96 said:
zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?
Click to expand...
Click to collapse
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?
Bobernator said:
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?
Click to expand...
Click to collapse
I just sent you the file, tell me if everything is ok
Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!
Bobernator said:
Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!
Click to expand...
Click to collapse
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.
Welcome again! My exams have just ended (I hope they went well) I am temporally at my uncle's house so I don't have access to files and info I've gathered, but I will return to home at friday and even Easter will not stop me, becouse I have decided to start DevXDA project!
Stay with me guys
Fulcano said:
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.
Click to expand...
Click to collapse
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.
Bobernator said:
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.
Click to expand...
Click to collapse
Thanks for the reply! Sorry, i've been quite busy with exams as well.
It's been a while since the phone is bricked, and i think fastboot was the wrong word. When it is plugged in it appears as a qualcomm device and the LED blinks, but other than that the phone does absolutely nothing. I remember being unable to unbrick it because of needing a `programmer.pem` file specific to the version of android that was installed.
The phone had an unlocked bootloader, twrp and supersu. It got stuck during an OEM update from 7.1.1 (i think) to 8.0.0. It was stuck for over four hours, I turned it off by force and then it never turned on again .
With regards to the Moto Z2 files, that's fantastic to hear. If there's anything else I can do to help, please say so. I've configured email alerts now so i'll get notified when you reply .
Thanks for the effort!