Hey guys i don't know if anyone of you had the same issue but any info/help could be helpful.
I used to flash my N1 A LOT! but today i have this strange issue. I wiped and flashed rodriguezstyle again for a clean start, but i only got the colorful X with the unlocked symbol at the bottom and then just a black screen. i thought I've done something wrong and flashed again, but with the same results.
i changed my sd and downloaded again the rom but still no luck, did a nandroid restore and the phone was working properly. then i got a bit frustrated. downloaded 2-3 more roms but the result was the same.
i read somewhere that flashing with battery <50% may cause some errors so left the phone off to fully charge and tried again... no luck
then i remembered i upgraded the radio and i downgraded it to the old one, but still the same results and nandroid doesn't work... jeeeesh... back to the new radio and to my nandroid, but its no fun owning a smart-phone if you cannot flash it.
anyone with the same issue or any helpful tips/instructions?
Try this:
When the phone hangs at boot, reboot to recovery, wipe cache and dalvik-cache and reboot from recovery. Does that work?
If not, you'll need to logcat the boot process and post the log somewhere for us to have a look at.
So, assuming adb is working on your computer, plug in via usb, use adb logcat > output.log and reboot the phone. Continue logging for about 60 seconds after the phone stops.
Post the log to www.pastebin.com and then link back here.
hmmmm ok i will post results in abt an hour. thanx!
hmmmm i think i sorted it out... reflashed recovery. propably i messed smthing in there! thanx for your effort!
Hello everyone!
Weird problem here, too.
I was backing up my SD card in view of a format/cleanup....and when I went to boot into recovery, my N1 was stuck on the black screen with the white letters at the bottom "Build : RA-nexus-v1.7.0.1"... The phone actually boots great, it is just not loading the recovery image. Is it possible that part of the flash got corrupted? If so, I'm pretty much done flashing my N1, right???
I'll post a log asap (if it could help any)...
Oh and btw i tried to re-flash Amon-RA's recovery twice already...Superboot said it was successful....but I doubt it...
Well try flashing stock rom! I flashed it through fastboot step by step and it worked. Also check if the rom you try to flash needs ext partition or if apps2sd is enabled
Sent from my Nexus One
Test
Sent from my Nexus One using XDA App
Thanks nica.
I had to flash stock boot and rom to fix it...
Sent from my Nexus One using XDA App
Related
anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.
I'm new to this whole flashing custom ROMS business. I have a CDMA HTC Hero 2000 and I downgraded to the original 2.1 before the update just fine, rooted my phone just fine. Then I tried to flash Aloysius to it using instructions I found here: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police
After all was said and done, my phone starts to boot with the "HTC quitely brilliant" logo, following by "SPRINT the Now network" logo and after it shows "Now" for many seconds (as it normally does before pulling up the home screen), it reverts back to the HTC logo and repeats this process until I remove the battery.
I removed the microSD and attempted to boot, same thing. Then I held down HOME+BACK+POWER to do a manual hard reset, this took a little longer but again had the same result.
I may just cry now. Please help!!
Run the official sprint ruu, and see what that does for u. Then read the rooting guide here on xda and try it. I personally recommend amon ra recovery to flash roms, rom manger never seemed to work right. Feel free to pm for more help, dont worry u prob arent bricked unless u flashed a gsm rom (which aloysius isn't)
Sent from my HERO200 using XDA App
That's a bootloop not a brick You could try downloading a different rom and flashing it in recovery, nandroid restoring - if you made one, or flashing the same rom again. just wipe your phone before (data/cache/dalvik)
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
chrisdegraw said:
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
Click to expand...
Click to collapse
Four key words to remember when trying out any new rom
Nandroid is your friend!
additionally, you should always remember to wipe before loading a new rom!
Enjoy!
Yeah, don't ever panic, that was, as everyone said, a bootloop by textbook definition. I've never seen a brick before, but I'm damn sure it won't get as far as the Sprint logo. The only way to brick a CDMA Hero is to flash a GSM Radio/Bootloader to it.
I tried to flash the boot image for my first custom rom using easy kernel flasher, and my Vivid is now stuck at the white HTC screen. I then realized that I had used rom manager to flash CWM, even though I had already flashed the custom CWM from the superguide. Is this what caused my phone to hang at the HTC screen?
Is it safe to pull my battery? What is the next step, repeat step 2 from the superguide and then reflash the new kernel and rom?
I apologize if this has already been answered, I just haven't seen this exact question elsewhere and I don't want to pull my battery without being sure that I won't brick my phone or make my problem worse.
Rom manager does not work for our phones. That is why your phone is stuck. I remember another post like this. The guy pulled the battery and flashed the new cwm image without rom manager and it worked. I believe you would start at step two to correct your issue. Let us know how it goes for you.
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
androuglas said:
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
Click to expand...
Click to collapse
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
I tried again and it went in to h-boot, and i was able to reinstall the custom vivid CWM. But now I'm not sure if the kernel flash which started all this worked. Is there a way to find out while in recovery?
Should I reboot the phone now, or just flash the rom I was planning on flashing originally? Or should i try to return everything to stock and start all over?
cbronson41 said:
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
Click to expand...
Click to collapse
Thanks man. I got into recovery and fixed the CWM problem, but now I'm not sure what kernel I have running so I don't know if its safe to reboot.
Though I know how to use CWM I couldn't tell you how to check your kernel and whatnot from there. Best thing I can think of, or what I'd do, would be to wipe everything out and restore a nandroid, granted if you have one I've never really messed with kernels untill now so I don't even know if that would work
I realized I could just reflash the kernel while I was in recovery. It hung at the htc screen on the reboot like before, but i just pulled the battery, went back into recovery, flashed the rom, and now everything is working perfectly with the new rom. What a relief.
I think the original kernel flash may have actually worked, and I just freaked out when it hung at the htc screen and assumed it was because of the rom manager/cwm thing. It may have been fine all along.
Here is something that will help with flashing kernels.
http://forum.xda-developers.com/showthread.php?t=1423151
Flash Image GUI
ok i did the same thing awhile ago, i flashed new CWM then insatlled rom ...the Kernal did load thats the reason you got the white screen ..so just go ahead and load your rom you should be fine
Ok, so i upgraded htc vivid to new ics through official ruu.exe whatever file that is. From there i unlocked bootloader flashed boot image and Paranoid 4.1.2 rom. Phone was great until today when i started to move music files from pc to phone. would shut down and restart by itself......every five minutes or so. Now, if i turn the phone on at all it is constantly in this boot, run fortyfive seconds, reboot again, dreadful cycle. So now i am trying to get back to stock if i can. i first tried to flash a new rom, cm10 nightly to be exact. NO LUCK! still boots into paranoid and dreadful reboot cycle continues. Now, i am looking to go back to stock but when i run "fastboot oem lock" fails and phone remains "unlocked" in fastboot ui. What in the world do i do? I read very thoroughly, have even had to learn to push my zip and img files through adb because my sdcard or internal_sdcard wil not mount in recovery. Recovery is not CWM or TWRP but i can not remember which it is
"RA REVAMPED
Build : Made for WCX ILLUMINATE SERIES by GINM"
blue lettering.....
any help would be greatly appreciated.
:crying::crying::crying::crying:
Note.......Vivid runs allot longer when transferring files from PC. Has been running now approximately 4 minutes no problems. Files still moving though....i will wait and see what happens after file transfer completes.
Yep!!! Just shut down again...but definately runs longer when transfering files...very confusing to me....
You must have the WCX recovery. What RUU did you flash exactly? If you could give me a link to it that would be great
Official att ruu.
http://forum.xda-developers.com/showthread.php?t=1564776
my phone is running paranoid android though from this thread.
http://forum.xda-developers.com/showthread.php?t=2029534
it is having a problem wioth the sd card i beleive. When i attempt to go to gallery is shuts down. when i go to music it shuts down. when i try to uninstall juicedefender it shuts down. Excited to get a response and look forward to getting some help thank you!
Also let me add.... i have tried a full wipe sdcard and internal_sdcard included but each time i try all contacts photos screen widgets and my user specified settings remain intact on phone. i would imagine that after this full wipe i would have a fresh clean phone. NOT THE CASE! Very weird
Might try flashing a diff recovery (TWRP) and wipe install, see if that works. Then you can go back to the WCX and test that again.
ok tried cwm recovery from fastboot to no avail still stuck on previous recovery. phone wont stay on long enough for goo.im to download or run twrp recovery. i really have no clue what the issue is. I also downloaded tapatalk was able to use it for about 2 inutes then phone shut off rebooted itself and tapatalk is no longer installed. i am stumped! No help either...........:silly:
[email protected] said:
ok tried cwm recovery from fastboot to no avail still stuck on previous recovery. phone wont stay on long enough for goo.im to download or run twrp recovery. i really have no clue what the issue is. I also downloaded tapatalk was able to use it for about 2 inutes then phone shut off rebooted itself and tapatalk is no longer installed. i am stumped! No help either...........:silly:
Click to expand...
Click to collapse
Maybe you have a crap battery...
Maybe your sim card isn't making good contact...
Maybe your external SD card is borked...
First... try removing your external SD and boot...
Second try removing your sim card and see if it boots...
Finally... try another battery and see if that fixes it to the point it stays on...
Sent from my Vivid 4G using Tapatalk 2
Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.
I hope you're not also flashing any of the custom kernels on here....cos they're not compatible with 4.2.2
Nope not flashing anything else but the ROM itself..
after flashing did you try "fastboot erase cache" ?
sometimes that helps when phones get stuck on the HTC logo after a rom flash.
Use the toolkit to erase cache
Sent from my HTC One using xda premium
Yeah done that several times too. Can't seem to work out why it isn't working and I too can't find the correct RUU for my device meaning I can't even take it back to stock
try to hold power + volume down to get into the bootloader to get back into recovery. Once in recovery factory reset, erase cache, erase dalvik, and reflash the rom.
also download the andorid SDK for fastboot and adb, then try "adb reboot bootloader" if you can not get back into the bootloader to get into recovery
My friend had his do this loop as well, we had trouble getting it into recovery, but held the button combo of power and vol down several times (probably 10) and it FINALLY booted into the custom Clockwork recovery, then we reflashed and it worked like a charm.
Also try redownloading... it could be a bad download
Sent from my Nexus 10 using Tapatalk HD
rilee said:
Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.
Click to expand...
Click to collapse
Just a word of advice. Update your profile to say your country and carrier. It helps people identify which device model and carrier you use.
Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.
rilee said:
Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.
Click to expand...
Click to collapse
I would be restoring my nandroid backup and make sure the phones that way first and then start again
Thanks again for the help guys, went to phones 4 u this afternoon and he exchanged the device for me.