Problem flashing roms - Nexus One Q&A, Help & Troubleshooting

So I've been trying to flash CM5.0.8 and I tried flashing Cm6, but neither of them will boot up, at the moment I have the leaked version of FROYO flashed on my Nexus one, whenever I try to flash one of those mentioned it doesn't work. I have the latest radio, I've tried wiping, but it doesn't work. Help?
FIXED: I Flashed Clockwork Recovery and used that instead of Amon Ra, and now everything is fine.

What steps are you executing to flash your phone?

well, I first do a nandroid backup, and then I do a wipe, and I flash the Cm6 zip file, and then the flash the FR91 zip file. It stays on the X with the pad lock.

latest radio meaning 5.08? or the 4.06?
I never have had problems flashing roms, I recommend going back and checking the md5 sum. Wipe data/factory, cache, dalvik cache, then flash the rom, the gapps. Should do the trick, it could take awhile to boot up on first time. Cyangoen has typically taken alittle extra time for me.

I have the 4.06 radio. I tried to flash FRF50 and it didn't boot up either. SO now I'm trying the FRF90 stock.

So neither the stock version of FRF50 works, or FRF90. I'm out of ideas. Help?

Your phone gets to the bootloader and can load recovery - which is good.
In recovery wipe EVERYTHING before loading ROM, install CM6 from ZIP or whatever ROM you want (shouldn't matter), wipe again (data/cache/dalvik/whatever), and reboot.
Please re-download the ROMs, as you may have faulty downloads (most probably).

Okay, I did as you said, I redownloaded CM6, and I tried wiping, reflashing, and wiping again, but for some reason, it still stays at the X screen with the padlock. Err, I tried it with the FRF50 and it seemed to work though, but I was wondering why I'm having troubles with other roms.

I've realize that a lot of times verification fails on updates. Does this have to do with the recovery?

Which recovery are you using?

AmonRA the latest one.

If you have verification failures - means that your updates are faulty. Nothing good will come out of flashing them.

So I'm guessing it's not the recovery that's messed up, but the zip files I'm trying to flash?

I have a lot of verification fails. :\ I'm not sure why. Anyone know?

Related

Stuck at Loading Screen

Okay, so I have everything flashed and Cyanogen's mod is working. However I decided to flash the radio as well. On entering recovery, it is now stuck at the loading screen (with the 4 color X's). Is this normal after flashing radio? I read that you are supposed to be patient and not remove the battery after flashing radio. How long does it usually take? It has been on this screen for about 20 minutes now.
How did u flash the radio? Did u do it from recovery? Normally after initiating flashing radio through recovery, it will extract the package, then reboot and install the new radio, THEN reboot again.
It's hard to say where u might have gone wrong without more info.
I flashed from fastboot using "fastboot flash radio radio.img". It said done on the two lines (Flashing and writing?). Anywho, I decided to go ahead and boot to the recovery to install my gapps. This is when it got stuck on the 4 color logo X. It is still there.
Can you go into the bootloader, or the recovery console? I just want to know if you have bricked your phone or not, if you haven't - then I recommend you just try wiping everything (as usual) and reflashing the ROM. If that doesn't work, at least I tried to be helpful.
Well I haven't removed the battery and tried rebooting yet. Should I?
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
cicrockets said:
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
Click to expand...
Click to collapse
I would recommend downloading the radio in a .zip format made to flash through recovery... that's the most reliable in my experience...
Thanks, I might try that next time. Too much suspense in one day pour moi.

[Q] Cannot get CM6 to boot

I rooted my Sprint Hero and have been able to successfully flash and operate Fresh 2.3.3 but CANNOT figure out how to get CM6 to boot. I wiped prior to attempting the flash but all that happens is a lockup on the HTC boot screen. I have attempted to flash it twice, and waited about 20 minutes the first time and 45 the second time with no progress, eventually having to pull the battery and reboot in recovery mode. I was only able to wipe the data but when I tried to wipe the delvik cache, it told me I needed to do it via ADB. I tried to partition my SD card but it ended up cutting the available memory in half, and erasing my backup, and I had to use an external card reader to reload Fresh so that I could actually use my phone (which IS fully functional now). Should I be wiping EVERYTHING on the phone (including the battery and rotate info)? What am I missing?
I have heard nothing but great things about CM6 and am very disappointed that I cannot get it to work. Can anyone help?
Sprint HTC Hero
Firmware version: 2.1-update 1
Software version: 2.27.651.6
try wiping your ext partition
I wiped everything that the recovery menu would allow me to prior to the first attempt at flashing and it wouldn't load. I pulled the battery and rebooted to the recovery menu then partitioned the SD card, wiped just prior to the second attempt at re-flashing, re-flashed and it still locked up at the HTC screen.
I like to think I'm pretty computer savvy but I just can't figure this out. Why would Fresh 2.3.3 load without a hitch, but CM6 not?
make sure you recovery is 1.6 or 1.7 to be able to wipe dalvik i had same prob
My recommendation would be flashing the recovery in this thread here.
This the recovery I used while I was using Fresh 2.3.3, and when I upgraded to the CM6 Nigtlies.
I say Flash The Custon Amon_RA 1.7 in Darchdroid thread->NANDROID!!!!->Wipe Data->Dalvik->sd-ext(if using apps2sd)->Flash RC1 or Latest Nightly (your choice)->Flash Optionally Google Apps->Optionally Flash Uncapped Kernel and/or Battery Tweak(I use the uncapped Kernel, and not the battery tweak, and I get 24 hours+ with average use)
Try that out.
Funny, im running into the same problem after flashing the wrong blackmod... wiped, reflashed cm and now it wont go past the htc white boot screen
It did boot before though which is odd
Edit: Wiped, wiped dalvik and ext part, flashed rom and gapps, working just fine now... will flash batt tweak, bm and round clock in a min, hopefully it doesn't break it
jUgGsY,
Thank you for being so thorough in your response, it all makes sense! My only issue now is trying to re-flash the recovery image. I downloaded the RA-Darchstar image but I'm not sure if it's correctly being pushed to the SD card (all I get is a long list of ADB commands, no particular confirmation) and when I try to flash the image, I get a message telling me that it can't find the partition. What does this mean? Is the recovery image really that important to the updated ROM? How come there is no specific recovery image recommended on the CM forum?
EDIT: I found directions from the Unlockr on the youtubes. Gonna give it a try and see how it goes after that...
So it was decadence#7 kernel that was screwing up my boot... removed it and using stock darchstar
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
jordanjackthomas said:
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
Click to expand...
Click to collapse
Are you flashing RC1 or one of the nightly ones? I had the same issue with RC1. I could not get it to boot past the HTC screen. However, the nightly ones flash just fine. I would suggest flashing a nightly. I now see you said RC1, lol. Try the latest nightly.
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
jordanjackthomas said:
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
Click to expand...
Click to collapse
The latest one seem to be very good. 8/22 but make sure you download the latest google apps for it also.
For some reason, I couldn't get any variation of CM to load on my phone (CM6 or the Vanilla variant). I went with Darch's LegendROM and it is excellent - much better than stock 2.1 for the Hero! Really fast and has some neat extra features. I noticed, though, that my reception is kind of bad now and I usually have excellent coverage at my house. I already downloaded the most up-to-date Sprint radio (2.42.01.04.27) but was just curious: do I need to wipe and re-flash the image FIRST or can I just flash the radio image over the already installed ROM?
AND: Please excuse my inexperience with all of this, but I'm about to ask two already answered questions: I'm not looking for long-winded answers but if someone could point me to a relevant thread, it would be GREATLY appreciated.
1) I keep getting a "process com.google.android.googleapps has stopped working" error when I try to sync with my gmail account. How do get this to work?
2) I remember reading that there was a known MMS issue with Darch's DroidROM, not any issue with the LegendRom, but I just received a "generic network failure" message when my wife tried to send me picturemail. Is there a workaround for this?
Thank you all for your patience!

Custom Roms will not boot! Please Help.

Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
JohnPublic said:
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
Click to expand...
Click to collapse
try amon ra recovery, full wipe including dalvik and flash one of the roms you listed above, like cm6.1 stable (from cyanogenmod.com) with the gapps (from jaybob413's rom thread in hero development). once it starts the boot, give it time, it may take a long time (10 min.) Hope it works.
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Now don't I feel silly! I re-downloaded CM6.1 and put it on the card and it seems to be firing up. I'm on the CM logo bootscreen right now. I have no idea how three separate zips all got corrupted en route to my card, but I suppose that must be what happened. Thanks for the help!
JohnPublic said:
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Click to expand...
Click to collapse
have you tried re-downloading the roms? it sounds like something is missing in them, which shouldn't be. if you are downloading from your phone, try a download from a computer and see what happens. where are you dl'ing the roms from? verification failure makes no sense..... also, did you recently update rom manager from market to 3.0.0.7? there was something listed in the changelog about verification failure fixed when using other recovery, i think....
EDIT: saw your last post, maybe your browser was acting up? delete the bad ones, get new ones, flash away

[Q][Still not Solved] Nexus one getting buggy with 7.1 mod

Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!
I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.
So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!
I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.
Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?
Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again
Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.
No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).
I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!
Any advise?
Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version
But how does it matter I checked the md5 checksum and it matches!!
Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1
But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!
Please guys any help would be appreciated!!
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext
Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!

Phone reboots randomly - can't flash anything through ODIN or recovery

So I was running a custom rom for months now for my N910T without issue but yesterday the phone suddenly rebooted by itself while I was using it and would keep rebooting roughly every 3min.
I backed up everything in TWRP and wiped everything to reboot into a clean rom like factory reset but that didn't work as everything was still there and nothing was wiped. So I tried to flash a new rom but it failed and gave an error E: cannot execute upgrade binary.
I'm on TWRP 2.8.1.1 so I can't flash a TWRP update (have to be on 2.8.4 or above) and thought my recovery was too old. I then plugged phone in download mode and used ODIN to flash a new TWRP. It would write fail every time, no matter what I changed. I tried to install different versions of recovery and used different versions of ODIN with no success.
I also changed different cables and ports. I then tried to flash a stock rom through ODIN but it also says write fail. Basically I tried everything and searched on XDA and google and tried every method I came across. Anyone have this issue or suggestions?
tldr: Phone N910T reboots from home screen, write fail flash from ODIN and fail flash from TWRP recovery. Can't use phone because it would boot to home screen for a few min then just reboot again. Help!
tiskewlio said:
So I was running a custom rom for months now for my N910T without issue but yesterday the phone suddenly rebooted by itself while I was using it and would keep rebooting roughly every 3min.
I backed up everything in TWRP and wiped everything to reboot into a clean rom like factory reset but that didn't work as everything was still there and nothing was wiped. So I tried to flash a new rom but it failed and gave an error E: cannot execute upgrade binary.
I'm on TWRP 2.8.1.1 so I can't flash a TWRP update (have to be on 2.8.4 or above) and thought my recovery was too old. I then plugged phone in download mode and used ODIN to flash a new TWRP. It would write fail every time, no matter what I changed. I tried to install different versions of recovery and used different versions of ODIN with no success.
I also changed different cables and ports. I then tried to flash a stock rom through ODIN but it also says write fail. Basically I tried everything and searched on XDA and google and tried every method I came across. Anyone have this issue or suggestions?
tldr: Phone N910T reboots from home screen, write fail flash from ODIN and fail flash from TWRP recovery. Can't use phone because it would boot to home screen for a few min then just reboot again. Help!
Click to expand...
Click to collapse
have you tried doing a factory reset/data wipe
xnknown said:
have you tried doing a factory reset/data wipe
Click to expand...
Click to collapse
Yes I tried every wipe option possible. Wipe system, boots right into rom. Wipe internal, everything still there. Wipe data, factory reset, everything still there.
tiskewlio said:
Yes I tried every wipe option possible. Wipe system, boots right into rom. Wipe internal, everything still there. Wipe data, factory reset, everything still there.
Click to expand...
Click to collapse
Then something I'm your phones been corrupted probably, your going to have to rma for a new device
has anybody come up with a solution to this problem im having serious boot and loading issues. i have flashed many roms and have never had a problem. i odin flashed the cog2 firmware then twrp flashed the tekxodus rom. something happened changing permissions with the built in setting with the rom and twrp was lost and i cant get back to a usable phone. odin flashed everything i can find for my phone and its not working everything either falis or goes to loop.
You probably corrupted your partition doing something wrong

Categories

Resources