Develop Bugs

Need Help: Restoring Nandroid backup from PC [SOLVED]

Hello Everyone
I tried something stupid and now my Desire doesn't boot anymore. I have made a Nandroid backup, but I am unable to restore with my device, because I don't seem to have the ClockworkMod Recovery
I can go to the screen with the 3 skateboarding androids, but when I choose recovery, It goes to "Android system recovery <2e>". There doesnt seem to be an option to restore Nandroid backups there.
What's the easiest way to restore my backup? I can access my SD-card on my PC.
Or maybe it is easier just to install a random fresh ROM and from there restore my nandroid backup? (but I don't know how to do that from the recovery screens I have access to)
PS: I already tried some things on I found on google, I tried restoring using fastboot method, but get this message:
c:\Android>fastboot flash system system.img
sending 'system' (232637 KB)... FAILED (remote: data length is too large)
Please help, Thanks!
Edit: Tried to manually 'install' ClockWorkMod Image 2.5.0.7 with fastboot... I get the following error:
c:\Android>fastboot flash recovery recovery-clockwork-2.5.0.7-bravo.img
sending 'recovery' (4216 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)

You need to be s-off to be able to use those fastboot commands. Have you tried reflashing a custom recovery with unrevoked? Otherwise you probably need to use a Ruu and root again.
Sent from my HTC Desire using XDA Premium App

Hi, Thanks
you're right, I do have S-On
I also have H-boot 0.75
(Radio-5.11.05.27 just to be complete)
What do I need to do first? Remember that I am stuck on the HBoot screen (3 skateboarding androids).
Can I get S-off from here and flash ClockworkMod Recovery? Or do I need to flash a RUU Rom first?
Also do I need to update HBoot to 0.80?
And are 'HBoot drivers' the same as the 'Fastboot/ADB drivers' ?
Need more help please. Most tutorials start with a working phone
Thanks!

Need some help guys please, Everything I try doesn't seem to work.
I figured out my phone is stuck in HBOOT with USB debugging disabled. Because Unrevoked doens't recognize my phone. Next step was to try and install a RUU. But the version I needed is corrupt. (I think) I downloaded twice and it just doens't work, I get an error even before the program loads.
I downloaded from RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed here: http : / / shipped-roms . com/shipped/Bravo/
Should I maybe try another RUU? Maybe 2.29.405.5 ? Or is that not safe?
Grtz!

Solved,
xda forum member EddyOS pointed me to this RUU http://www.multiupload.com/LEJCW182AH
(filename: RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed)
Thanks!

[Q] Issues flashing new recovery

I have been running MIUI flashed via clockwork app/recovery for the past few months. Today, suddenly a bunch of my apps were not working and I was getting a load of force closes. I figured I reboot and I find myself in a bootloop.
At this point, it isn't a huge deal. I figured, I would boot into recovery and load up my backup from CM7. Only problem is I can't seem to get into my recovery, as thought it is gone. Also no big deal, I'll just try to reflash my recovery via fastboot. I load up on hboot and run it with the latest version from clockwork:
Code:
D:\Desktop>fastboot devices
HT08JHJ04373 fastboot
D:\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm looking several places for this exact problem, but I can't seem to find anything that works for me. My SD is backed up and while I would like to be able to keep my other stuff and/or just get up and running again without a wipe, any suggestion would be helpful right about now.
Thank you,
Drox

droxpopuli said:
I have been running MIUI flashed via clockwork app/recovery for the past few months. Today, suddenly a bunch of my apps were not working and I was getting a load of force closes. I figured I reboot and I find myself in a bootloop.
At this point, it isn't a huge deal. I figured, I would boot into recovery and load up my backup from CM7. Only problem is I can't seem to get into my recovery, as thought it is gone. Also no big deal, I'll just try to reflash my recovery via fastboot. I load up on hboot and run it with the latest version from clockwork:
Code:
D:\Desktop>fastboot devices
HT08JHJ04373 fastboot
D:\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm looking several places for this exact problem, but I can't seem to find anything that works for me. My SD is backed up and while I would like to be able to keep my other stuff and/or just get up and running again without a wipe, any suggestion would be helpful right about now.
Thank you,
Drox
Click to expand...
Click to collapse
Have you tried flashing recovery thru hboot with a PB31IMG.zip? You can get it here http://pvillecomp.com/?page_id=28

I got it installed from there. I loaded up the recovery and it must have done a restore since I booted and it was fresh miui like when i did a backup from before. Nothing to be done there sadly :/ But thanks for the help and the link. I didn't even know this site existed.

[Q] cannot update cwm 2.5.0.7 to anything at all

Hi there,
well i bricked one SD card in the process so far, not bad
So, here is my problem. I got my RMA Desire back und rooted it with unrevoked. After that installed ginger villain, anyhow i wanted to install myself another ROM which required repartioning sd ext to a larger partition. Smart as I am, I saw that newer versions of cwm can do that for you, so i wanted to update my outdate 2.5.0.7 version to 5.xxxx. Hell it won't work, neither installing via ROM Manager nor installing via cwm itself. Not even via fastboot. No chance there either.
So there i sat, 1 o'clock in the morning and thought why not give some partitioning program a shot, worked fine with my harddrives. this is where i made the fat partition smaller, deleted the ext3 partition since i couldnt resize it, made a 1.6 gig ext3 partition and thought i was king of the hill. yall might know already that i bricked that sd card. Now running on the ****ty 4 gig original one.... that has no ext3 or swap at all.
So, now my question is, how can i update my cwm to something that isnt as outdated as my underwear?! And any way that i could unbrick my fine 16 gig sd card?
thanx in advance and apologies for any grammar or spelling mistakes.
cheers

Are you S-OFF? Please post fastboot output after flashing recovery.
Sent from my HTC Desire using Tapatalk

Even tho i checked security off in phone with unrevoked, s-on states the post in Hboot.....
ahyhow.
Installing CWM_Recovery_5.0.2.3.carebear.jr0dd.zip in recovery gives me:
Code:
assert failed: getprp("ro.product.device") == crespo"
getprop("ro.build.product") == "crespo"
E:Error in /sdcard/CWM_Recovery_5.0.2.3.carebear.jr0dd.zip
Status 7
Installation aborted.
Guessing there should be standing desire not crespo.
Anyhow, trying to flash recovery-clockwork-5.0.2.0-bravo.img or recovery-clockwork-touch-5.8.0.2-bravo.img via fastboot gives me this:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.440s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.781s

Did you try flashing it again with signature check disabled? Be careful with this tho, if you bootloader gets messed up you phone will be unbrickable... Where did you get the recovery from?

I did try that.
Thanks for pointing me to S-OFF, that was my problem. I used aplharev to get to S-OFF and then flashed via fastboot cwm touch and now it is actually installed.
at the moment cwm is partitioning my sd card. so hopefully my desire will be up and running in the next half hour.
If anyone is having the same problems, feel free to ask.
for now i am happy

[Q] GPE 5.0.1 Bricked my phone - can anybody help?

Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!

should be in Q&A mate
I have requiested the mods to move this

So first things first. You are not bricked, you are just stuck. Bricked means your device cannot boot, cannot turn on, cannot access any bootloaders or recovery.
You messed something up and it is failing to boot, it isnt bricked.
Second, running disk encryption on rooted devices is especially dangerous for these scenarios. Disk encryption attempts to prevent many of the things running roms, custom recoveries and such put on the device.
Now, I cannot recall if a full GPE version can do this or not, but from Fastboot you should be able to flash just the system partition. But being you are encrypted it may fail to access your old data. The command for that would be:
Fastboot flash system system.img (if you were able to obtain a system.img)
Again that works on Nexus devices, I cant recall if the GPE fastboot accepts it as well.
Wish you well, but honestly I would expect to lose your data. The reason the update failed the second time was because you are Rooted. 5.0+ has a new OTA system where any changes to the system partition can/will fail the OTA.

tschakk said:
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
Click to expand...
Click to collapse
First, your phone isnt bricked, its not bricked as long as you can access HBOOT, second, why would you encrypt your phone? uhg... I dont know what to tell you, try RUUing to stock, but dont expect to keep your data...

I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..

tschakk said:
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
Click to expand...
Click to collapse
You can only flash boot and recovery individually, you would have to put system.img and android-info.txt in a zip and flash in ruu mode

UNBELIEVABLE!
I could restore the system with dd... Just copied the system.img from Android 4.4.4 to the block device.. now the phone is booting up and i can see my data... uffff.. :victory:
so now i will do a backup and then go on...

Solution
If someone should encounter the same issue, this is what I have done to fix it:
I didn't want to lose my data, so I did not reinstall the RUU.. I couldn't get my data with ADB backup, because you need a system display to do it. And I also couldn't find any recovery which supported device encryption for the m8.. So I thought to backup my data partition with 'dd' to an external SD card and then if necessary I would reinstall the full system with RUU..
Code:
$ cat /fstab.qcom #to find the needed partitions
$ dd if=</dev/block/DATA-DEVICE> of=/external-sd/backup.bin
Now I knew I had a backup and was on the safe side. So I wanted to try to rewrite the system partition with the system.img from 4.4.4 GPE RUU. But fastboot flash didn't work. I always got this error message:
Code:
$ fastboot flash system system.img
...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
So what the hell, I used 'dd' also for this... :
Code:
$ cat /fstab.qcom #again to find the needed partitions
$ dd if=/external-sd/system.img of=</dev/block/SYSTEM-DEVICE>
And this actually worked, my m8 booted up with Android 4.4.4. First thing I did when Android booted was a full Android backup with adb.. To be safe to have my data back, because I didn't really know how to extract my encrypted data from the bin file I've created before... Then I just installed the update to 5.0.1 and this time it worked...

after encryption rom flashing soft brick help

condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains

try to use EMMA with UB to restore your phone.
VooDoo.maGiK said:
condensed version
encrypted phone, flashed, not working properly, used flashtool to try to use a stock image to restore phone, did not work, need help to save myself from a expensive waterproof brick
--------
The longer version of the story (in a galaxy far, far away....)
Just tried updating from last AOKP nightly (yer that old) to RR 5.4.0 but ran into issue flashing it namely from what i believe was from my phone being encrypted previously. It seemed to install the ROM well enough but i kept seeing this little error message popup during the recovery install (i did do a complete wipe etc)
Code:
E: cannot load volume /misc
but i assumed all well and good as it did not give a fail or anything so i continue on and try to install gapps for it but then get this error message
Code:
Install failed
E:cannot load volume /misc!
Finding update package…
Opening update package…
Verifying update package…
E: footer is wrong
E: signature verification failed
Installation aborted
E: cannot load volume /misc
accepting defeat after this failing after attempting again, rebooted the rom which loaded up well enough and tried to reinstall a different version of gapps, same problem, tried to install via fastboot same problem. Tried wiping the rom and formatting the internal memory via fastboot but got this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
erasing 'userdata'...
OKAY [ 1.046s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.007s]
erasing 'cache'...
OKAY [ 0.043s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 1.108s
could not flash the rom due to the android-info.txt issue with fastboot, flash a boot.img from RR, got the z1c running again and settled into a life without gapps and actually felt like it was a really good thing after a bit of research and finding alternatives but kept running into odd app errors and force closes and issues with receiving sms that forced me to have to figure out why it was not letting me install zips. Tried my luck on cm-12-20150402-NIGHTLY-amami build but had some issues with a few things got stuck in bootloop so decided i would try to start fresh so i moved on to my next step
Used this reference point for the ftf file and how to repair soft bricks http://forum.xda-developers.com/showthread.php?t=2631291&nocache=1, used flashtool after locking and unlocking my phone option (seen a few threads where people recommended it in the past) tried to flash the ftf file then got this (check attachment from flashtool for log), now really stuck phone reports that OS install failed and to try again but i know better than to keep doing the same thing over and over and to expect a different result so I ask the xda saviours for some assistance in getting me out of this problem.
Thank you for your time if you stopped in here to look at my request for help, it really is appreciated and to show that i will put a bounty/donation up for whoever solves my issue first as a sign of my good will and gratitude for your brains
Click to expand...
Click to collapse

will do, i think i may have had given emma a shot at saving my little z1c but will double check to be sure, what is UB? cant seem to find anything related to that acronym
cheers for the tip

Unlocked bootloader
Wysłane z mojego D5503 przy użyciu Tapatalka

cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee

VooDoo.maGiK said:
cheers, emma did the trick, i think i had started to use it as once of my first solutions but then realised it was going to take forever downloading the file in it i decided to try other things first but forgot to come back to it
throw me your paypal dets for a free coffee
Click to expand...
Click to collapse
if flashtool fails and you have luckily a unlocked bootloader and fastboot works you can allways restore your phone with EMMA.
unfortunately EMMA works only with unlocked bootloader.
thanks for the offer. but to me it is enough that the phone working again :good: