Database Develop

Trouble flashing any update.zip

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

I need an RUU.

Baiscly on my first rom flash i used a GSM only rom. Phone won't boot so i restored. Once loaded it would show all of my apps but would show no service. then after about a min it would reboot. I took the latest OTA update which i can find no ruu's that work with this.
Any help Apreciated.

Wyley87 said:
Baiscly on my first rom flash i used a GSM only rom. Phone won't boot so i restored. Once loaded it would show all of my apps but would show no service. then after about a min it would reboot. I took the latest OTA update which i can find no ruu's that work with this.
Any help Apreciated.
Click to expand...
Click to collapse
there is no 4.3 RUU yet....
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456

O.M.J said:
there is no 4.3 RUU yet....
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Click to expand...
Click to collapse
Im S On just tried to flash the full firmware. Says its corupt.

Before I did anything I updated to the newest firmware. Then using twrp I created back ups and transfured them to my computer. I flash the Android Rev 4.3 not knowing it was GSM only. The phone never would go past the boot loader. So i restored from my twrp back up. All of my stuff came back but I had no service and after about a min the phone would reboot it self. So i did the factory wipe and have been trying to get a rom to flash since then. I was finally able to get one to load today but i still have the same no service/reboot issue, however now i can't access the menu. When i swipe up it just says HTC till it reboots it self.
I have resorted to using ADB to load roms I have even used super wipe with no changes. I'm out of ideas here.

Well I just got done flashing the firmware and installing a rom. Before reboot twrp said there was no OS.
Problem still persists.

I was able to fid a back up I did.
I restored it and everything seemed normal excecpt I was getting some system errors then the boot cycle started again.
The error was like "Qualcomm location servies" or something.
Still didn't have signal though.

I am having a similar problem. Can not load past bootloader. When I try to flash a file I get:
C:\android-sdk>fastboot flash boot viperROM_One_v1.1.0.zip
< waiting for device >
sending 'boot' (776879 KB)... OKAY [ 45.619s]
writing 'boot'... FAILED (remote: image error! (BootMagic
fail))
finished. total time: 45.641s
Any help with this would be greatly appreciated!
Thank you in advance

[Q] Bricked after cm11 flash?

Just flashed to cm-11-20131112-NIGHTLY-mb886-epinter.zip and now the phone appears to be a paperweight! Here's the process, anyone have any ideas?
1) Atrix HD
2) Unlocked bootloader
3) installed all necessary software (drivers, ADB, fastboot, etc.)
4) enabled USB debugging, unknown sources on device
5) installed CWM
6) downloaded rom
7) used Myth Tools to flash ROM. Noted that it marked the flash as successful.
8) Rebooted phone, got to Motorola splash screen, went black, back to splash, black..
9) now has the backlight coming on and off
10) Can't enter recovery from phone, does not boot up enough for the PC to recognize it.
Any ideas on what I could be looking for at this point?
{edit} I can get to AP Fastboot Flash Mode (S), and the device is recognized by my PC, but not as a phone (as a storage device). I can't do anything from this point.

Why would you use Myth tools to flash the ROM if you installed CWM - isn't that the whole purpose for CMW and recovery tools like it in the first place (given the Nandroid backup potential, that is) ?
I honestly don't know hence me asking, but it seems like with step 7 perhaps it should have said:
7) copied ROM zip file to internal storage, rebooted to recovery/CWM and did a full wipe (that means FULL wipe: format cache/data/Dalvik/system, all 4 of them before proceeding), then installed the CM11 ROM + Gapps (I'm guessing)
Least that's how I always do things, the only time I ever flash a ROM from Windows is either a full back-to-stock thing using RSD Lite or whatever tool is necessary for whatever device (I just happen to own an Atrix HD at this moment so it's RSD Lite). Sounds to me like you need to do a full stock ROM recovery (flashed with RSD Lite) and start over again.
You say that you can get to AP Fastboot mode - if that's the case you should be able to flash the CMW image file using fastboot (you need to make sure you're using the Motorola fastboot.exe file, not the "standard" Android fastboot.exe that comes with the Android SDK because it can cause issues).
Get the CWM zip archive, extract it, get the recovery.img file and use:
fastboot flash recovery recovery.img
to flash it to the AHD in AP Fastboot mode - this should get you a working recovery once again (boot using all three keys, Vol Down to Recovery, Vol Up to select it and then go from there when recovery loads). This assumes, of course, that fastboot is going to work - before attempting to flash try using:
fastboot devices
and see if it lists the device at all - if it's not seeing it, you're kinda stuck for a solution (that I can't offer, sadly). If it does then flash the recovery.img manually and then disconnect the USB and power it down by holding the Power button for at least 15 seconds; if the Power button doesn't do anything, hold all 3 buttons for up to a full minute and hopefully it'll die. Mine did that last night at one point: it was stuck on the Motorola logo and nothing worked, so I held all 3 buttons for about 55 seconds and it finally 'died' so I could do a proper boot into recovery.
I'm guessing that since you used Myth Tools to flash the ROM it's not actually sitting on the internal storage so... you're going to need to get a microSD card and put the ROM zip archive on the card along with Gapps or whatever if needed and use recovery to install it from sdcard1.
Hopefully this'll get you up and running again. I just got this Atrix HD of mine yesterday and did the following last night:
- contacted AT&T to get the carrier unlock code (all automated through the website, got the email containing the code early this morning and used it earlier, now working fine with T-Mobile and LTE is working as expected)
- rooted using motochopper
- unlocked bootloader with motopocalypse
- installed CWM 6.0.4.4 recovery.img by using fastboot to flash it directly
- copied the CM11 ROM zip archive to the microSD card (while attached to the PC since it was still stock ROM at that point and MTP was working fine) + Gapps
- disconnected the AHD from the PC and shut it down
- rebooted with 3 buttons to CWM recovery
- full wipe (did factory reset, then cache, then Dalvik, then system)
- install CM11
- install Gapps
- reboot
No issues encountered in the process but I rarely do have problems, maybe I'm lucky, who knows...
ps
Just for the record, I use the official CM11 nightly builds, the one I installed last night was cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip - not sure if that will or would matter (I'm guessing not) but I figured I'd mention it, and I used gapps-kk-20140606-signed.zip for Gapps.

Why did I use Myth Tools is a great question... I guess it's because I couldn't find a really clear step-by-step on flashing a new ROM. There's a lot of "download this", "Download that" "Flash this, delete this", etc.
Your 11 step process is the best how to guide I've seen!
Anyways, I used fastboot to flash the recovery for CWM. Here's the "log":
Code:
>Fastboot devices
TA300049SJ fastboot
>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6824 KB)...
OKAY [ 0.543s]
writing 'recovery'...
OKAY [ 2.479s]
finished. total time: 3.022s
The end result was that I could boot to the recovery options, but it looked like the standard Motorola recovery and not CWR. I selected Recovery and the phone went to the Motorola logo, then black, then the logo, then black, and then the backlight would go on and off forever.
I tried the same process with the recovery file I downloaded from the clockworkmod website "CWM_T_6.0.4.4.img" and got the to the same recovery screen, but then when selecting recovery the Motorola logo would stick on for about 15 seconds, and then off for two and repeat. Not sure if this was an improvement or not
It worries me that fastboot says variable not supported. I'm wondering if that means that it's not actually writing the recovery to the device, or if it's not sticking and reverting back to the Motorola recovery upon reboot.
I have the ROM and GAPP zips on my micro SD ready to go, and I think if I could get into a working recovery I could get them flashed.
Any other ideas?

Have you attempted a full RSD Lite session going back to the pure stock AT&T ROM yet? If not, that might be what you need to do or at least you should make the attempt to do so (could be the last resort).
The fastboot thing could prove to be an issue, definitely - I'm going to assume you are using the Motorola specific version of the fastboot.exe file, of course.
Try to do the stock restore using RSD Lite and if that fails then and only then attempt to do the stock restore using Myth Tools. I just used that myself to install the stock Mexico ROM earlier for some testing and didn't have any issues - it does a complete full restore obviously (not the same as how CWM or some other recovery does an installation but you're most likely aware of this anyway.
So, stop worrying about CM or any custom ROM at this moment, the focus right now is just getting the AHD in a functional stock condition so you can do something else with it - you're not totally bricked but you may have to jump through a few hoops to get it back to working condition, and stock is pretty much step one.
Also, the CWM that I use (6.0.4.4) can be found here (since I know for sure this is the source of it, at least for myself, meaning it is specifically for our Atrix HD devices):
http://forum.xda-developers.com/showthread.php?t=2421418
Probably not the latest or the greatest but it works for me without issues. I pulled the recovery.img file from the archive and flashed that manually with fastboot.exe and haven't have a problem yet. I just found this but I cannot speak for stability or usefulness, it appears to be the latest version of CWM for our Atrix HD:
http://forum.xda-developers.com/atrix-hd/development/recovery-cwm-6-0-5-1-jbbl-t2891842
Will test it here shortly I suppose and see how it works - there are two of them, one was created/posted on Sept 30 then the poster did it again (synced with CM's builds) for Nov 1, wouldn't guess they're all that different so give the Nov 1 build a shot if you wish.

[Q] "Operating System Safety Warning" after flashing TWRP 2.8.7.1 on 6.0.1

This has been frustrating me to no end for several weeks.
So recently I decided to take the plunge and do a clean firmware flash on my N6 from 6.0 -> 6.0.1 (shamu-mmb29s)
All boots up and all is fine and dandy - until..
Rooting it.
I flash TWRP 2.8.7.1.
"fastboot flash recovery twrp-2.8.7.1-shamu.img
target reported max download size of 536870912 bytes
sending 'recovery' (11700 KB)...
OKAY [ 0.386s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.562s"
Wooo. Great.
Next. Restart into recovery.
*Que TWRP Splash Screen*
Still good...
Next. Restart system.
Do I want to install Super User?
Of course I do. Swipe to install.
Install complete.
System restarting.
*google boot screen*
And then I get this error. (seen here https:// support.google . com/nexus/answer/6185381?hl=en)
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this line on another device:
g.co/ABH"
Below it says "press power to pause boot" but you aren't left with enough time to react and press the power button.
My device then turns off. If I turn it back on, I'm left with the same result. Boot screen -> error -> off.
This is when I discover I failed to remember rule #1. I didn't create a nandroid backup.
I can boot into the bootloader and re-flash everything, but that gets tedious.
Good News:
-I can boot into recovery
-I backed up most everything on TiBu
Bad News:
-I can't root.
Someone help

Do not let twrp install su, you'll have to install a different .zip to acquire root on 6.0 and 6.0.1

reflash everything again, never ever except SuperSU from twrp(press no), then boot up. then, go back into recovery and flash the latest SuperSU. when you will boot up, you'll get that message again. ignore it and press power button. that message was put into the ROM by google, you'll see it no matter what. if you don't want to see that message, flash a custom kernel as well.

Follow the steps from here and you won't need to flash a custom kernel and you won't get that message when you start. I'm currently using BETA-SuperSU-v2.66-20160103015024.zip

What they said... When TWRP asks if you want it to install SuperSU, say no.
Download SuperSU v2.66 to your internal storage, and then flash the .zip through TWRP to achieve root.
Make sure you make a backup in TWRP first though.

holeindalip said:
Do not let twrp install su, you'll have to install a different .zip to acquire root on 6.0 and 6.0.1
Click to expand...
Click to collapse
Thank you! This work.

Thank you!

What am I doing wrong? (Problems with custom recovery on 3T and OOS5)

I have had the OP3 (not T) for a while, no problems rooting with custom recovery.
I just got a 3T and this has me stumped. My process has been as follows.
Wipe device, start with a clean slate. USB Debugging and OEM Unlock enabled.
Reboot to Fastboot. Fastboot OEM Unlock. select yes.
Let it fully boot.
Reboot to Fastboot.
Fastboot flash recovery "twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img"
Code:
fastboot flash recovery B:\!Desktop\twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img
< waiting for device >
target reported max download size of 435159040 bytes
sending 'recovery' (22296 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.672s
Success!
Reboot device, let boot fully. Everything works.
Reboot recovery. Still stock recovery?!?
Why am I unable to flash custom recovery and have it stick?
Also, If I try going into custom recovery straight from flashing it seems to be fine but then never boots.
Can someone more experienced than me please point out where Im going wrong?

I also tried an older recovery I had for my OnePlus3 (not T), twrp-3.1.1-x_blu_spark_v8.54-op3_op3t.img, still no luck.

You can't boot an original ROM after flashing TWRP, as just like on Samsung phones, booting up the original ROM it restores the original recovery.
However there's guides for disabling this process around in the forum, never done it myself, but I guess you simply delete the recovery image from the system partition wherever it's stored.

You already have your answer. Booting straight to the OS without further modifications replaces the custom recovery with the stock one.
To keep the stock recovery you need to boot to TWRP and flash a custom kernel, dm-verity remover, root (Magisk or SuperSU), or something like that.

You have to boot straight into recovery from fastboot with "fastboot reboot recovery" before booting into the ROM

mikex8593 said:
You have to boot straight into recovery from fastboot with "fastboot reboot recovery" before booting into the ROM
Click to expand...
Click to collapse
This way doesn't work any more. TWRP doesn't patch the kernel.
You have to use a custom kernel, a patched stock kernel (https://forum.xda-developers.com/on...force-encryption-op3t-t3688748/post74155053), or install Magisk or SuperSU.

all I have to do after flashing OxygenOS (which overwrite recovery) is flash twrp immediately after flashing the rom (no reboot) and then REBOOT to recovery! This always worked for me. I have done this yesterday after flashing latest OOS beta 20. No magisk or supersu needed.

My problem with booting straight to recovery is it would fail to boot after, I waited on that oneplus screen for like 2 hours lol.
For whatever reason I flashed recovery twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img
Booted to recovery
ADB push blu_spark_r209-oos-oreo_op3-op3t_a9745b4.zip
Install THAT in recovery
Success! it booted.
No idea what the difference is, I dont know why its such a bother now it used to be so easy just flash custom recovery and continue on my way but now it seems theres a lot of dicking around.
Thanks to all those who offered help.

pileot said:
My problem with booting straight to recovery is it would fail to boot after, I waited on that oneplus screen for like 2 hours lol.
For whatever reason I flashed recovery twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img
Booted to recovery
ADB push blu_spark_r209-oos-oreo_op3-op3t_a9745b4.zip
Install THAT in recovery
Success! it booted.
No idea what the difference is, I dont know why its such a bother now it used to be so easy just flash custom recovery and continue on my way but now it seems theres a lot of dicking around.
Thanks to all those who offered help.
Click to expand...
Click to collapse
The reason it's more complicated is that the boot process now ensures that the stock recovery is used (it will restore it automatically), that the system partition hasn't been touched, and that encryption is on.
Custom kernels don't enforce these security checks.