Related
I recently exchanged my Nexus One for another guy's N-1 which works on ATT 3G. I had done a nandroid backup of my phone, and used that same image to recover the "new" phone to exactly how it was before the switch. It failed first, but after I moved my BCDS folder to the new HTPXXX folder, it went through.
However, now when I try to flash a zip from recovery (Amon-RA 2.2.1), I always get the "Signature verification failed" error. I tried flashing newer radio, after verifying the MD5SUM. I tried flashing the 0.35.017 HBoot. Both of them failed. I am wondering if it's because of the mismatched nandroid recovery I did.
Any help would be greatly appreciated -- thanks!
Edit: Needless to say, after disabling signature verification, everything flashes correctly.
I doubt that it would be the ROM cause it shouldn't mater while your in recovery. So I would try reflashing your recovery through ROM manager, terminal or fastboot if your bootloader is unlocked.
Dude Random21 said:
I doubt that it would be the ROM cause it shouldn't mater while your in recovery. So I would try reflashing your recovery through ROM manager, terminal or fastboot if your bootloader is unlocked.
Click to expand...
Click to collapse
Thank you, nice idea -- I never thought about reflashing the recovery. I'll try this tonight! Thanks.
Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Visosilver said:
Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Click to expand...
Click to collapse
Since you have Rvolutionary S-Off, you cannot simply overwrite the HBOOT with stock 2.00.0000. You need to follow this procedure:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
Then you would able to use the PG32IMG.zip.
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
If your bricked than its definately worth trying. Sounds to me like your internal memory has some kind of error on it if you can't wipe. And it might not be hung when you try to flash the pg32 as it as it says don't power off and you did anyway you might own an unbrickable phone.
Sent from my Incredible S using xda premium
Visosilver said:
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
Click to expand...
Click to collapse
That depends on if you can update the HBOOT. In order to make your current HBOOT 6.13.1001 overwritable, you need to follow the procedure steps 1-2d in the procedure I posted.
If that doesn't work, then there is no sense trying to go on. As the previous posted suggested there is something wrong with your phone's partitions.
If it does work, then I would defintely run a stock RUU to get back to a known working state.
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Visosilver said:
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Click to expand...
Click to collapse
Yes it appears that you are unable to flash any of the partitions on your phone, including the HBOOT partition.
Do you have another PC and USB cable to try just to rule out that those aren't causing an issue? If you do, make sure you have the latest HTC drivers installed.
didn't work but thanks for your help anyway
greez visosilver
Visosilver said:
didn't work but thanks for your help anyway
greez visosilver
Click to expand...
Click to collapse
There's no harm in trying a ruu
Sent from my Incredible S using xda premium
try fastboot boot recovery.img
where recovery.img is the recovery image CWM or 4EXT
this wont flash the image..i will just push the recovery on your mobile and then would start it..then try to format all the partions
and can u provide us with all details..like exactly how the error happened..???
and is your phone under warranty..??
i just tried to boot the cwm via fastboot.
the phone vibrated 8 times, three android dudes on a skateboard appeared and the phone rebooted into HBOOT.
I tried also this RUU: http://forum.xda-developers.com/showthread.php?t=1705913, but it results in a 171 USB Error...
The phone isn't under varranty anymore.
How the error occured: I was browsing around, when suddenly whatsapp crashed. So i rebooted the phone and it was stuck in a bootloop. Then i tried to flash a new rom and the error occured
edit: after following to this guide here http://community.htc.com/na/htc-forums/android/f/113/t/10043.aspx, i was able to flash the device using the RUU. But I couldn't use the phone due to crashing processes (mostly android.process.arcore), so I rebooted. Now the phone is stuck again in a bootloop...
try installing the RUU again...and if possible if you are installing a custom rom please wipe all partition ,cache and dalvik cache...
and try booting the mobile withouth the sim card...lets see if it works
i just tried it, with the same result
I tried flashing the renovate rom to my sprint one and got a kernal error at the end and it would not boot. I somehow also managed to wipe everything off the phone including the backup so i can even go back to stock. I tried pushing a rom via adb but i can get that to work and when i try use fastboot it says failed and i get a signature verified error. I am really starting to panic because i spent all of last night trying to find a solution and was unsuccessful. I also tried flashing using the ruu but it was unsuccessful but im pretty sure thats because i am on the 1.31 ota and it was a 1.29 ruu because i cant find a 1.31 ruu. Any help would be greatly appreciated.
which recovery do you have installed? if you have TWRP, you could try adb sideloading a ROM.... in TWRP, choose Advanced/ADB Sideload. then you send the ROM to the phone from your computer with 'adb sideload <rom name>.zip'.
if you don't have TWRP installed maybe you can install it from fastboot. there are probably other solutions too, but hopefully this would work. good luck!
Did you relock the bootloader before you tried the RUU?
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
wingman358 said:
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
Click to expand...
Click to collapse
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
alray said:
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
Click to expand...
Click to collapse
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
wingman358 said:
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
Click to expand...
Click to collapse
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
On boot, it cleared the HTC logo (finally!). Then it hit me with "Google search has stopped unexpectedly" and goes back to the HTC logo... wtf... then it popped up "Dialer has stopped unexpectedly"... then the home screen came up, and it rebooted itself.
After rebooting, I swiped to unlock the screen and it showed the dreaded white HTC logo... ugh, then it hits me in quick succession with "Hangouts has stopped" "Google Play Music has stopped" "Youtube has stopped" and so on. If I hit the screen off button then turn it on, it showed the lock screen. The lock screen seemed fine, the clock worked, and swiping to unlock worked, but when it unlocked instead of the home screen it showed the white HTC logo. Eventually it rebooted itself. After I think the third time rebooting itself, the android setup/configuration came up. "_____ has stopped" keeps popping up.
I was able to restore contacts and stuff by signing into my google account, but I am almost continually getting "_____has stopped" pop-ups, and if I let the phone sit for a few minutes it reboots itself maybe every 5 minutes or so. Also I don't think I have cell service (it just shows an X with no bars). It seems normal aside from those (not much home screen lag, apps open, wifi seems to work).
I did a permissions fix from recovery which completed without errors, but it didn't seem to help.
wingman358 said:
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
Click to expand...
Click to collapse
Why flashing gapps over a stock sense rom?
alray said:
Why flashing gapps over a stock sense rom?
Click to expand...
Click to collapse
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
wingman358 said:
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
Click to expand...
Click to collapse
Yes, wipe everything and reflash the rom
alray said:
Yes, wipe everything and reflash the rom
Click to expand...
Click to collapse
That did it! Wiped, reflashed, and no more force closes, not one. Thanks a bunch alray!!!
Tried updating the S8 to latest firmware and it failed. I am not stuck in a boot loop where attempting to get back into download mode results with
"An error has occurred while updating the device software"
I can't seem to do anything else. Does anyone know of a way to recover from this or am I SOL?
cbb77 said:
Tried updating the S8 to latest firmware and it failed. I am not stuck in a boot loop where attempting to get back into download mode results with
"An error has occurred while updating the device software"
I can't seem to do anything else. Does anyone know of a way to recover from this or am I SOL?
Click to expand...
Click to collapse
First you can try is wiping cache through stock recovery, and try to boot, if this doesn't solve it, you must need to factory reset (your data will be gone), try to boot, if this doesn't fix it, then flash the last firmware you had previously the failed update. Also, if you don't want to lose your data, you can try only the first step, and if this doesn't fix it, flash the latest firmware that was working previously to the failed update, and untick the userdata partition in Odin.
Ok, so it looks like I am back up and running. I did not realize that although I had this error, Odin was still able to communicate with the tablet. Thus I flashed the latest firmware again and now I am back up and running. Lost everything, but didn't have anything important, and what was semi-important, already had on the SD. I am at least happy I don't have an expensive paperweight.