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.
Related
I'm sorry if this is posted anywhere, but I spent a couple hours last night and another couple hours today searching here and in Google with no luck.
-Skip me for TL;DR-
I got a G1 when they first came out, and rooted it as soon as I could. I ran JF1.5 then JF1.6 then after a while upgraded to Cyanogen. It was great and my GF still uses it and loves it. I got a Nexus One about a month after they came out and I've been in love. I haven't went to Cyanogen since, only because the stock rom has been great and I haven't needed any extra features yet.
Now that 720p is available along with a few other things I'd like, I want to upgrade finally.
-TL;DR end-
Basically I'm trying to say I'm not an idiot or very new to loading roms and toying with an Android device.
From past experiences I basically know the process of root/recovery/rom etc.
I loaded froyo onto the phone when it was available via the stock recovery console and an update.zip ... no problems.
Yesterday, I unlocked the bootloader.
Installed Modaco's superboot.
And used fastboot to push recovery-RA-nexus-v1.7.0.1-cyan.img
After that I turned the phone on, and logged in to check it out and make sure I had root. Everything was running great (Froyo saves your app installs in the cloud!!!) and I did, in fact, have root. All seemed well.
-The Problem-
Now, I can't load any more update.zip files. Nothing at all. Stock rom, modded rom, rom updates, anything. When I try to install any update.zip I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
At the top of the recovery screen it reads: Android system recovery <3e>
If that makes any difference....
NOTE: I can still use fastboot to push new recovery images, which I've tried.
System information below:
Fastboot/Bootloader Screen:
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP0b15
TOUCH PANEL-SYNT0103
RADIO-4.06.00.12_7
Dec 17 2009, 13:05:23
ABOUT PHONE
Model number: Nexus One
Android version: 2.2
Baseband version: 32.36.00.28U_4.06.00.12_7
Kernel version: 2.6.32.9-27220-g328f560 [email protected] #1
Build number FRF50
Thanks in advance for any help/info!!
Looks like you still have the stock recovery image... do you have backup & restore options iin recovery mode, if not, you still have the stock recovery, reflash Amon-RAs recovery...
No, I don't have backup or restore in the options, neither in recovery or fastboot.
This doesn't make much sense. Here's what I'm doing. It looks like it should be working fine:
Code:
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot devices
HT9CWP806497 fastboot
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot.exe flash recovery
recovery-RA-nexus-v1.7.0.1.img
sending 'recovery' (3948 KB)... OKAY [ 0.582s]
writing 'recovery'... OKAY [ 1.439s]
finished. total time: 2.021s
Edit:
I was thinking maybe I need a different radio image, but then I remembered reading that Froyo came with a new radio image (right?). And I couldn't install a new radio image anyway because the update.zip files won't load. I'm pretty stumped here....
Edit again:
The code above was what I just did to flash the new recovery, and I still don't have the options to backup and restore the data.
Another edit!: I also loaded Modaco's superboot again (successfully) and started the process over again with no luck.
You don't have a backup/restore option with AmonRa's 1.7.0? That means you don't actually have the custom recovery. Your fastboot is lying to you.
In the terminal app,type "reboot recovery". What happens?
And,try dropping the ".exe" from fastboot.
what they said. Sounds like you still have the stock recovery image. Try reflashing the recovery again.
I tried both the regular RA recovery and RA Cyanogen recovery using both commands, fastboot and fastboot.exe but I continue to get the same recovery image.
I know there's no way to relock the bootloader, but is there any way to reverse what Modaco's superboot did and try that again?
Go here. Scroll to the bottom of the first post. Looks at the screenshots. Does your recovery look like that?
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Try using amon ra recovery image stock for n1, not the cyanogen version.
This one:
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-nexus-v1.7.0.1.img
and rename it to recovery.img or something short then try the fastboot flash recovery recovery.img
Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Confirm you have root. Go to the terminal app and type "su". What does it say?
Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.
FaJu said:
Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.
Click to expand...
Click to collapse
OP said he unlocked the bootloader.... so OP verify that when you TURN ON your Nexus One, the logo with the X there is a PADLOCK on the bottom of the screen. If it does, then your bootloader is unlocked and you need to install amon ra recovery.
If no padlock, you're not unlocked.
OP make life easy. Go to Market. Install ROM manager. Either install clockwork recovery, or scroll down. Select the option to flash another recovery. Flash. Done
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
hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?
niekehecv said:
hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?
Click to expand...
Click to collapse
Note what kind of hboot do you have, check your bootloader, if you have Hboot 1.25 then the functional and recommended Recovery for you is by Paul O'Brien, if you are on Hboot 1.28 then the recommended one is bue unlimited.io, if you are lazy to search for them, you have them included in this tool, i really can't understand why people doesn't use this, as it is free and keeps you away from lots of searching, many threads are old, many procedures are old so the guide recommended by me for everything is the guide by stona15, this one
Hope this helps
I don't remember if I deleted it or what but I only have TWRP 2.6.1 on my device as a recovery and I would like to reinstall CWM on my device. However, every "flashable" CWM zip I have tried through TWRP has failed and I'm not sure why. Don't nwant to brick my device and don't necessarily want to WebOS doctor it if I can avoid it, as my device has run fairly well (I am on 4.2.2). Any/all help is appreciated. Thanks!
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
bananagranola said:
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
Click to expand...
Click to collapse
Not yet, although I managed to get a workable CWM running by moving an image to the boot folder and then updating to the latest working version (couldn't get the "touch" version to work via touch, however).
However, I may try flashing via fastboot if something unexpected happens. Thanks for the help
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'