Related
Hey Guys
My Nexus one hangs at the startup screen and I can't seem to get it to start. So far, I have tried going into the quick boot screen and clearing the factory settings (i.e hard reset) but it did not change anything. I am bit out of ideas.
Did you do a nandroid, if so revert back to it and proceed forward from there.
sorry, I didn't do an nandroid. Can I do that now?
alright, I installed a recovery image and can enter the menu listed here.
Cyanogen's recovery source based on Amon_RA's post.
I restore the setting just fine but then when I reboot the phone still hangs. Is there another step I am missing? Is just having the recovery tool not enough? How do I restore the original settings?
same problem here did you manage to fix it ?
Same problem here. I have tried everything but I cant make it past the " X " - looking splash screen. If its of any help, the splash screen is STATIC.
Thanks in advance.
it almost sounds like either a bad flash or a bad wipe, if you made a nandroid, try resotring it. If you have not rooted or loaded any roms then the problem may be hardware side.
think the mobo is acting funny, i sent mines in for repair due to t his issue, but unlocked bootloader makes me pay $194..... im trying to figure it out before i pay as a last resort!
I didn't want this to be my first post and I've been holding out for a couple of days now, but here goes.
When the CM6.0 zip installation finishes, I tell clockwork to Reboot Now.
When it reboots, I get the white screen with green HTC letters. I do not ever get to the screen with the black writing on it. It then proceeds to the cyanogen mod boot screen with the swirling circle, but that's all it ever does. It will stay in the "boot loop" forever if I let it. The phone never progresses past that point.
I am able to do a nandroid recovery back to before the CM6 ROM and everything is OK, but its not FROYO nor is it rooted. I followed the instructions from here //forum.xda-developers.com/showthread.php?t=730002
Any help will be greatly appreciated.
Are you connected to the PC when you reboot?
No, I've tried twice and both times I was unplugged.
Let me run down some quick troubleshooting answers
I used CyanogenMod-6.0.0-liberty-signed.zip
I have the Android USB Drivers
I installed HTC Sync, but uninstalled to leave the drivers.
HBOOT is good
Clockwork installed like clockwork.
I did not install the Android SDK, I didn't think this mattered since I had the drivers from the Sync install.
Your best bet is to hop in the IRC and ask for help. http://webchat.freenode.net/?channels=#liberatedAria
I'll have to get on when I get off of work. Thanks for the linkage and taking a look at my issue!
OK, so the guys over on the IRC helped me out....very quickly I might add. I didn't want to start a new thread for this very reason...super simple fix!
My issue was that I did not perform a wipe through clockwork before installing cm6.zip.
According to Yoshiofthewire and jznomoney, the cyanogen boot loader will loop if the old HTC files are still on there. Performing the wipe through clockwork and reflashing did the trick!
Thanks to you all! now to set the rest of the phone up. Amazing resource!
matroe11 said:
OK, so the guys over on the IRC helped me out....very quickly I might add. I didn't want to start a new thread for this very reason...super simple fix!
My issue was that I did not perform a wipe through clockwork before installing cm6.zip.
According to Yoshiofthewire and jznomoney, the cyanogen boot loader will loop if the old HTC files are still on there. Performing the wipe through clockwork and reflashing did the trick!
Thanks to you all! now to set the rest of the phone up. Amazing resource!
Click to expand...
Click to collapse
No problem. I was gonna suggest that you didn't wipe, but I wasn't sure without being able to talk to you. Figured it was faster to send you to IRC. Glad everything is working. Enjoy.
I know this is a known issue but I wanted to see if anyone has had any luck yet.
My phone only gets to the HTC Evo splash screen and reboots. I can get into hboot and when i choose recovery from hboot it goes back into the boot loop.
This just happened to me a few days ago. I went from MikG to Deck to CM7. I just flashed CM7 over Decks 1.3 wiping only cache and dalvik. I was starting to really dig CM7 and I was planning on sticking with it. When it happened I was using the stock web aplication. I finished reading the page I was on and hit the back button (the one at the bottom of the phone) and next thing I knew my phone started rebooting. It never made it past the Evo splash screen since. I've been able to flash different hboots and it takes but it does not take any of the recoveries or RUUs. Has anyone had any luck with this yet? Or does anyone have any different advice with the extra info I have provided?
To reiterate I cannot get into recovery only hboot.
Thanks a ton in advance all.
nanstedt said:
I know this is a known issue but I wanted to see if anyone has had any luck yet.
My phone only gets to the HTC Evo splash screen and reboots. I can get into hboot and when i choose recovery from hboot it goes back into the boot loop.
This just happened to me a few days ago. I went from MikG to Deck to CM7. I just flashed CM7 over Decks 1.3 wiping only cache and dalvik. I was starting to really dig CM7 and I was planning on sticking with it. When it happened I was using the stock web aplication. I finished reading the page I was on and hit the back button (the one at the bottom of the phone) and next thing I knew my phone started rebooting. It never made it past the Evo splash screen since. I've been able to flash different hboots and it takes but it does not take any of the recoveries or RUUs. Has anyone had any luck with this yet? Or does anyone have any different advice with the extra info I have provided?
To reiterate I cannot get into recovery only hboot.
Thanks a ton in advance all.
Click to expand...
Click to collapse
Try getting this:
http://goo-inside.me/amon_ra/supersonic/recovery-RA-supersonic-v2.3-PC36IMG.zip
To thee root of your SD card and then boot into HBOOT to load it.
Make sure it is named PC36IMG.zip
You may be missing your recovery.
atapia984 said:
Try getting this:
http://goo-inside.me/amon_ra/supersonic/recovery-RA-supersonic-v2.3-PC36IMG.zip
To thee root of your SD card and then boot into HBOOT to load it.
Make sure it is named PC36IMG.zip
You may be missing your recovery.
Click to expand...
Click to collapse
I appreciate the link but my issue is that I can flash the recovery files from hboot but to my dismay I still cannot get to recovery from the recovery selection within hboot. There seems to be an issue where hboot hands the reins off to recovery or android. I'm not sure how to troubleshoot or overcome something like that. Maybe my assumption is wrong but who knows.
You don't have to go into recovery to flash a pc36img. It happens in Hboot.
In theory, you should be able to flash that, then flash recovery.
HipKat said:
You don't have to go into recovery to flash a pc36img. It happens in Hboot.
In theory, you should be able to flash that, then flash recovery.
Click to expand...
Click to collapse
Is the link provided not Amra recovery? That is what it looks like to me, but I could be wrong. Please advise. I can flash the recoveries in hboot but when i go to recovery from the hboot screen and select it the boot loops commence.
Unfortunately, that is a problem that you can search and see a fair number of people have had and I don't think anyone has fixed it as it means bad blocks and/or something to do with partitions being resized and I hate to even say this, but all but a very few cases were running CM7
HipKat said:
Unfortunately, that is a problem that you can search and see a fair number of people have had and I don't think anyone has fixed it as it means bad blocks and/or something to do with partitions being resized and I hate to even say this, but all but a very few cases were running CM7
Click to expand...
Click to collapse
Yes, i've noticed that. I was hoping that since it had been a while that someone had found a solution. Hopefully a dev will chime in and give some steps that I haven't taken yet.
nanstedt said:
Yes, i've noticed that. I was hoping that since it had been a while that someone had found a solution. Hopefully a dev will chime in and give some steps that I haven't taken yet.
Click to expand...
Click to collapse
I hope you hear something. Mine is exhibiting a similar behavior. Maybe time to trash this phone or at least flash it back to stock so I can take it back to Sprint.
jerrykur said:
I hope you hear something. Mine is exhibiting a similar behavior. Maybe time to trash this phone or at least flash it back to stock so I can take it back to Sprint.
Click to expand...
Click to collapse
I wish i could flash it back to stock so i could use it again. I paid $200 for this thing. I'd like to get a few more years out of it. Nothing like the OG. I've tried running the RUU files from windows while in hboot and the files do change as I flash different versions. I noticed this when during the ruu program it shows you the from/to screen. So I know the RUU programs are working, it's just that the hboot recovery/ROM handshake is not happening. I guess I'm hosed ATM.
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Don't get too upset. You can still boot from SD. At worst, you may have to (re)install some firmware. If you want the B&N firmware, you can reinstall B&N 1.3 and update, or stay at 1.3 if you prefer.
It's hard to totally brick a NC.
Take a look at the restoring to stock section of the guide in my sig
Sent from space
Listen to the two people above this post. They are right. It is nearly impossible to completely brick it. Trust me I've tried.:what:
Seems no matter what I do to it, short of kick boxing it, I've always been able to start from a brand new running nook. Just by reading many posts and the great help from everyone on this forum, who have usually, "been there, done that.", folks.
I'm sure this will work out and everything will be fine, but then you'll be able to help someone else too.
Sent from my GT-P7510 using Tapatalk
i just use this command "fdisk /dev/block/mmcblk0 -l"
i think it was to see the partitions and they dissapeared just chek the image ;(
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
bobtidey said:
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
Click to expand...
Click to collapse
Nope... you can see he's looking at /dev/block/mmcblk0... that is internal.
Need to find the thread about the nook color partitions and create partitions 5-8 then dd the images to them.
i already fixed ! its working again
i can´t believe,
i was thinking about doing a tutorial in how to soft unbrick your nook, i´m not an expert but is a lot of people with the same problem as mine
basically when i enter in recovery receive errors in logs and he dont let me mount or format any of mine partitions(except boot and sdcard), a lot of people are having the same issues and i was thinking about doing a tutorial in how to do it.
should i do it??
thanks everybody
More tutorials are always good. One thing to remember though, is that if someone is looking for a tutorial that means they are usually starting with a small knowledge base. You not only need to be clear, you need to be right.
All I am saying is an underinformed/incorrect tutorial is worse than no tutorial at all. The information is out there, but can be hard to find. If you know your stuff, and have a place to present it where it doesn't already exist, then sure, people will benifit from your knowledge.
Just a guess, but problems mounting within CWM tend to come from old and/or incompatible versions of Clockwork. Is that where you had your problem? I definitely wished that had been stressed on the tutorial I first followed. Would have saved me untold hours of pointless reflashing.
you are right but in my case and i think that is the same of a lot of people (who follow this tutorial http://www.youtube.com/watch?v=szlGSBtWbKY) i tried about 7 to eight diferent versions of clockworkmod and including change of sdcard, i also tried DD the images of the boot and system, when nothing of this works we start get in panic, with no necessity because its only a partition problem, i fixed my 4 partition and he started working
Yeah, I can see where you are coming from. I followed an older tutorial as well, and never saw anything to indicate the link to the CWM image might be outdated.
For sure, that info should be wider spread.
Good luck on your video (?)
hackerse7en said:
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Click to expand...
Click to collapse
I am not sure where to ask for help. I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install, I power off forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. Am I bricked my nook?? please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stacked at the cw recovery screen. Help...
I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome
YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..
boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here
Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.
Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...
Found a fix, check the forum page