[[[{HELP}]]]
So, I have just rooted my HTC Wildfire S (CDMA/marvelc) and flashed a build of CM9. From that point i realized that I was stuck at HBOOT every time i booted my phone, so I proceeded to enter recovery mode. In recovery mode i performed a factory reset and cleared the cache and the dalvik cache. After making sure my phone was completley clean, i reflashed CM9. IT BOOTED!!! I was very happy so i began making customizations to it. Later that day (yesterday) i was going out to dinner and had noticed my phone had a low battery charge. to stop it from running out, i turned it off. when i got home it booted into HBOOT and would not boot CM9. Though i did find a trick around this, i entered Fastboot USB and typed this comment 'fastboot oem boot' and like magic, the phone turned on. Just to test i powered off my phone and turned it back on. It was stuck in HBOOT again. I got out using the fastboot command. the same thing happened when i restarted my phone. So, it clearly flashed well but there is something wrong.... I flashed using the latest build of CWM. the build is CM version 9.0.0 Any help would be much appreciated!
Thanks,
Matt
Related
My One X was working perfectly on Leedroid 5.1. I downloaded 6.2, put it on the SD card, held the power button and went to reboot into recovery, but it got stuck on the HTC ONE boot screen and wouldn't go any further. I thought it was a little odd but ignored it. Then I realised I needed to flash the boot.img anyway, so I turned the phone off then booted into bootloader, fastboot, flashed the boot.img. At the end of the process the phone was sent to recovery again, but again, the same thing happened, it wouldn't go past that screen.
I figured my recovery was corrupted, so I went back into bootloader and flashed CWM touch through fastboot.
Rebooted into recovery again, exact same problem. What gives?
Furthermore, every time I turn the phone off from that screen, it turns itself back on. I finally rectified that by turning it off, then holding vol- and powering down from bootloader.
What can I do?
EDIT: RESOLVED
fastboot erase cache fixed the whole thing!
So this has happen twice. My gnex has just restarted and get stuck at the bootloader in an endless loop.
I have a stock, rooted, 4.0.4 gnex.
Last time this happen I had to completely wipe my phone and start over. Dont want to do that again.
Has this happen to anyone else?
Thanks
-J
When I load in to recovery I cant even see the CWM menu.
Can you run fastboot commands
Sent from my Galaxy Nexus using xda premium
I could but now the phone wont turn on at all. Im actually one the phone with google right now to try to figure this out.
charge the phone (plug it in).
unplug it, press and hold both volume buttons, and press and hold power
bootloader comes up, plug it into computer
in this screen, flash the latest cwm file using the command:
fastboot flash recovery clockworkfilenamehere.img
press vol buttons to restart the bootloader, then select recovery, should pull up cwm.
Go wipe cache and dalvik cache (in advance), then pick restart, see if phone boots up.
If not, you'll need to reflash stock google image.
Charged phone over night and still wouldnt turn on.
Have you tried reseating the battery?
jp555soul said:
Charged phone over night and still wouldnt turn on.
Click to expand...
Click to collapse
Funny, my CDMA gnex just started doing exactly the same thing. Verizon is overnighting me another one, with Saturday delivery even.
you must factory restore your phone
you need to restore your phone to the factory image, use wugs toolkit,
galaxynexusforum.com/forum/galaxy-nexus-hacking-mods-lte-cdma/1445-wugs-galaxy-nexus-root-toolkit.html
it will download the 4.0.2 factory img for you. then use the same tool to root your phone. then install your rom. Install Liquid rom 1.4. i have tried them all it is by far the most stable and the fastet. coupled with franco or imoseyon kernel i am getting 20+ hrs of battery life and a smokin fast phone.
stuck in bootloader
My GSM nexus running aokp milestone 4 randomly got stuck in the bootloader the other day. It was working fine and after hitting my snooze button on my alarm and waiting a few minutes I realized it was off. when i turned it on it was stuck. I tried clearing cache and dalvik cache which wouldnt work so I was forced to do a factory reset. Came right back to life (with none of my data obviously).
This happened to me last night after trying to restore a nandroid. Wouldn't go past the Google screen when trying to boot the rom and wouldn't go past the team win recovery plash screen.
Luckily I have basic fastboot and adb command skills. Flashed fully back to stock, boot loader, radios, from, kernel. Booted up fine after that and no issues since.
hi!
a friend of mine brought his wfs (gsm) to me that i've unlocked and flashed custom rom before. it froze during the day when the phone was idle and when he tried restarting it was stuck on the white htc splash screen. nothing has been tampered with so i tried the following:
*trying to boot into recovery(which it had cwm and running without problems before): still stuck on white htc splash screen after selecting recovery option.
*trying to re-flash recovery-boot-system (different kinds, custom, stock) from hboot, successfully flashes, doesn't boot
*at last resort, i relocked the bootloader, created a goldcard and flashed "RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe" which successfully flashed, updated hboot, radio and flashed stock everything.
it finally booted into stock after 15 mins of splash screen. but when it gets to the locksreen, it doesn't respond to the touchscreen or the hardware buttons, the screen sleeps after some time, but hardware button lights stay on, and there's nothing i can do except for removing the battery.
i can't use adb logcat at this point since the debugging isn't enabled on the fresh rom.
after removing the battery and trying to reboot, it's stuck on htc splash again, i have to boot into fastboot, do a factory reset, wait another 15 mins to boot into the fresh rom to get stuck again.
my educated guess is that the nand is worn out.
any suggestions or questions about diagnosing what we might have?
thanks in advance!
up
anyone?
Did you try to reflash recovery?
Sent from my bowl of jelly!
i've reflashed cwm, didn't work. flashed stock recovery, but booting to stock recovery also took like 2-3 mins, more than it should have. flashed cwm again, doesn't boot into it, stays at white htc splash.
Well most of the methods that i know involve recovery, so you are pretty much screwed...
Sent from my bowl of jelly!
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Why don't you try flashing the latest version of ICJ (3.4) with a full wipe and see whether the problem persists? Can you enter recovery now??
However, there's always a possibility of a hardware failure... and your situation with the random reboots / recovery reboots suggests somethings wrong!
ViktorN said:
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Click to expand...
Click to collapse
Sounds alot like a issue I had on ICJ quite a while ago.
If you select recovery at the bootloader, do you see the recovery for a split second and after that it reboots? I did flash multiple recoveries but it all didn't help. The luck I had is that fastboot was still working
I tried everything to get it to work, but nothing seemed to help. The only luck I had was that fastboot worked, and with that I managed to flash a RUU. What actually happend I don't know, but it worked again.
Hi guys,
I've got a big problem with my Gnex. I was running AOSPAL Paranoid SaberDroid ROM with Dirty V kernel and Nephilim's settings. Just the read ahead buffer was set as default so it was 512 I think. I think I just forgot to change it. Everything was ok and then I changed RAB to this value about 4000 (max). I started antutu benchmark and while it was running the phone restarted and got into boot loop. I don't know if it was the reason of the issue, but I wanted to tell you all the circumstances. When I tried to turn it on the Google logo appeared and then the system loading animation started, after about 3-5 seconds it restarted and so over and over again. I was able to enter recovery mode, so I wiped cache and dalvik cache. Nothing changed. I flashed Dirty V kernel again, thinking that settings would turn back to default, but it also didn't change anything. I flashed franco kernel, and also nothing happened. I returned nandroid backup but it also didn't help with this boot loop. Then I wiped cache, dalvik cache, system, data and clean flashed SaberDroid ROM with stock kernel and PA gapps. Nothing. I plugged my phone to computer and flashed Google factory image using WugFresh Toolkit, so it wiped everything unrooted my phone and flashed stock clean 4.1.2 android and everything. I thought that will solve my problem, but also it didn't help. Nexus is still in boot loop - it keeps restarting when there is nexus logo animation. I was scared at that moment. I forgot to mention, that I could get to fastboot mode, recovery and the battery logo was showing correctly when phone was plugged to charger. Then I locked the bootloader so it is completly stock right now, it just doesn't turn on...
I read the topic about omap flashing, but as I understand it is for those devices, which can not turn into fastboot mode (and mine does) and then the solution is to flash google factory image, what I did... When phone is turned off and plugged to computer the device menager shows for 2 secs omap4440, and when it is in fastboot mode and plugged to comp it shows normally as Android Phone (Google Galaxy Nexus BootLoader Interface, because I had drivers installed to use the Toolkit.
It is all what I could do and I don't know what else could be done to ressurect my loved Gnex .
Do You guys know what's going on?
Please help me.
I think I have read somewhere in the Dirty V thread that some bug in the kernel was causing the Google logo boot loop. Have you tried using 0sm0sis' Emergency Kernel Cleaning Script listed in his signature? I remember him telling someone to use that script in the kernel thread.
osm0sis's zip only restores kernel tweaks and settings to default. I didn't try it, but now I don't have to, because I don't have any custom kernel right now. My phone is pure stock.
Yesterday I tried omap flashing, and it run properly, but also didn't change anything. I also flashed Google factory image again after omap flashing.
Any other tips? It doesn't look optimistic ;/. Maybe it's hardware? But I thought reboot loops are connected to software and it is soft brick, which can be repaired.