Hey!
I decided to install a new custom ROM. I went from Revolution HD and tried Viper v2.0, after installing it, my phone has been refusing to boot. (I used Revolution HD Super wipe before installing Viper v2.0) It freezes at "htc quietly brilliant" and stays there and doesnt do anything. Ive jumped into bootloader several times, first i tried the obvious and start Recovery. But everytime I press recovery i can see the "Clockwork recoverymode" for about 0.5 seconds, then some sort of loading and then it reboots and goes back to the startup screen and stays there. Ive alos tried the factory reset, but that didnt work either, so now im wondering what to do and im a little worried.
All help is appreciated.
Thanks alot!
skogaern said:
Hey!
I decided to install a new custom ROM. I went from Revolution HD and tried Viper v2.0, after installing it, my phone has been refusing to boot. (I used Revolution HD Super wipe before installing Viper v2.0) It freezes at "htc quietly brilliant" and stays there and doesnt do anything. Ive jumped into bootloader several times, first i tried the obvious and start Recovery. But everytime I press recovery i can see the "Clockwork recoverymode" for about 0.5 seconds, then some sort of loading and then it reboots and goes back to the startup screen and stays there. Ive alos tried the factory reset, but that didnt work either, so now im wondering what to do and im a little worried.
All help is appreciated.
Thanks alot!
Click to expand...
Click to collapse
did you flash the boot.img for the rom?
also type this command in cmd to get into recovery --> fastboot erase cache
Doo Doo said:
did you flash the boot.img for the rom?
also type this command in cmd to get into recovery --> fastboot erase cache
Click to expand...
Click to collapse
Yes, i flashed the boot.img.
When i type "fastboot erase cache" I only get < waiting for device >
And ye, my phone booted about twice, i got to the lock screen i tried to unlock, then it froze and died.
Have you chosen the fastboot option in the boot loader, plugged in the usb before trying to talk to your phone with fastboot?
Sent from my One X using xda app-developers app
brucezepplin said:
Have you chosen the fastboot option in the boot loader, plugged in the usb before trying to talk to your phone with fastboot?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
ye i did. Ive tried about everything now, and still nothing. Is there any complete reset option?
skogaern said:
Hey!
But everytime I press recovery i can see the "Clockwork recoverymode" for about 0.5 seconds, then some sort of loading and then it reboots and goes back to the startup screen and stays there.
This problem happened to me a while back, it causes due to cache getting accumulated, fastboot erase cache got my CMW recovery working again..
i dont know why isnt it working in your case..
And about ROM not booting looks like boot.img problem, i hope u made a nandroid
Click to expand...
Click to collapse
OrmaZ said:
skogaern said:
Hey!
But everytime I press recovery i can see the "Clockwork recoverymode" for about 0.5 seconds, then some sort of loading and then it reboots and goes back to the startup screen and stays there.
This problem happened to me a while back, it causes due to cache getting accumulated, fastboot erase cache got my CMW recovery working again..
i dont know why isnt it working in your case..
And about ROM not booting looks like boot.img problem, i hope u made a nandroid
Click to expand...
Click to collapse
I didn't have the lates clockwork version, so when i managed to access the phone through CMD i flashed the newest version and restored my backup. Then i got it working again. So thanks for all your help!
Click to expand...
Click to collapse
Related
Hi !
After rooting and installing CM9 on my friends OneX, it no longer will shut down and stay off (phone reboots automatically) and also wont boot in to recovery mode, it flashes up in a split second but just restarts the phone.
Ive tried flashing another recovery but to no avail...
Unable to boot into recovery
Andyokane said:
Hi !
After rooting and installing CM9 on my friends OneX, it no longer will shut down and stay off (phone reboots automatically) and also wont boot in to recovery mode, it flashes up in a split second but just restarts the phone.
Ive tried flashing another recovery but to no avail...
Click to expand...
Click to collapse
I've got this problem too, flashed CM9 and now won't boot into recovery at all, tried reflashing CWM Touch twice now!! Help!!!
Hey dude, I figured it out! dunno if it works for you but I had to use adb and this:
fastboot erase cache
worked a treat
That step is vewy vewy impowtant
I learned that the hard way
on xda for android and mistyping like a boss
Andyokane said:
Hey dude, I figured it out! dunno if it works for you but I had to use adb and this:
fastboot erase cache
worked a treat
Click to expand...
Click to collapse
That's not adb that command needs to be executed while the phone is in fastboot
Sent from my HTC One X using xda app-developers app
I have the International version of the One X and I tried to flash CM9 to it today. Everything was fine until I booted it up and it got stuck on the boot screen. Thought it wouldn't be a problem and I'd just try redoing the steps.. However, every time I select recovery from the bootloader, it restarts my phone. If I then hold the power button, it will turn off and then restart without me telling it too. The only way I can switch it off is by quickly booting into the bootloader and selecting 'Power Down'. Any help or guidance would be appreciated!
Have you tried "fastboot erase cache" without the commas
Sent from my HTC One X using XDA venom premium
Yes. Didn't change anything. Still stuck on the bootscreen and restarts everytime I enter recovery. Just tried reflashing recovery too.
Could Installing the stock bootloader and starting again help? or will that make no difference?
Is there any way of completely clearing the system without using recovery?
Did you flash the boot.img in fastboot
Sent from my HTC One X using XDA venom premium
Yes, However I fixed the bootup problem by using the following:
1.) Wiped with fastboot rather than recovery:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
2.) Re-flash recovery (fixed booting into recovery (ONLY when fastboot wipe is done)):
fastboot flash recovery recovery.img
3.) Re-flash boot kernel:
fastboot flash boot boot.img
4.) Flash ROM and GApps using recovery
This worked fine BUT everytime I try and power down my phone it automatically restarts. This is incredibly annoying. The only way I can get it to turn off is to boot into fastboot and select power off. If my phone is plugged in it will still reboot after about 10 seconds which means I can't charge it unless it's on.
At least you got your main problem sorted
Sent from my HTC One X using XDA venom premium
True. Thanks for your help too
I'm going to leave this to die, but if I can't fix my other problem I'll open a new thread.
In the mean time. If anyone knows a fix for this problem, please pm me! Thank you
petedavison93 said:
True. Thanks for your help too
I'm going to leave this to die, but if I can't fix my other problem I'll open a new thread.
In the mean time. If anyone knows a fix for this problem, please pm me! Thank you
Click to expand...
Click to collapse
Which version of recovery are you using? I seem to remember there was a problem with cwm recovery 5.8.3.1 maybe? Try flashing 5.8.4.0 if not done so already
Sent from my HTC One X using xda premium
eyosen said:
Which version of recovery are you using? I seem to remember there was a problem with cwm recovery 5.8.3.1 maybe? Try flashing 5.8.4.0 if not done so already
Click to expand...
Click to collapse
Clockwork Touch 5.8.2.4
I've just seen that the ROM I've been using (TripNDroid's) has been updated to version 005. Working Wi-Fi!
Just spent the whole day setting up my phone.. Kinda annoying.
I'm gunna try flashing that and see if it fixes the problem. Will post here when I've tried it
petedavison93 said:
Clockwork Touch 5.8.2.4
I've just seen that the ROM I've been using (TripNDroid's) has been updated to version 005. Working Wi-Fi!
Just spent the whole day setting up my phone.. Kinda annoying.
I'm gunna try flashing that and see if it fixes the problem. Will post here when I've tried it
Click to expand...
Click to collapse
Now I remember. Problem is with touch recovery. Only install 5.8.4.0.
Sent from my HTC One X using xda premium
Installed Touch Recovery 5.8.4.0. Phone still reboots when switched off and cannot boot into recovery mode.
Boots up fine so it mostly isn't an issue but I was hoping to do a nandroid backup via recovery which is looking unlikely.
When i flashed cm9 for the first time, i got the same issue, i was stuck at boot screen...but at least i could boot into recovery, and from there, i used android revolution hd superwipe script, and then did the flashing process again...worked fine after that. So my main point is, if u can boot into recovery, from there you need to do a wipe script or wipe data/factory reset and THEN flash cm9...
Sent from my HTC One X using Tapatalk 2
Hi there,
I recently installed ARHD 9.0 on my One-X but didn't like it, so i tried to revert to CM10 and now i think i've screwed things up. I rebooted, ran CWM, did a full wipe, cleared the cache and dalvik cache, installed CM10, installed GApps and tried to reboot and flash the CM10 boot.img - however instead of booting back into the bootloader the phone just continued booting and is still at the CM10 boot screen. I can't access bootloader for some reason - i hold down power and volume down, but no bootloader. Is my phone bricked? What can i do?
Appreciate any help. Thanks.
JMCNZ said:
Hi there,
I recently installed ARHD 9.0 on my One-X but didn't like it, so i tried to revert to CM10 and now i think i've screwed things up. I rebooted, ran CWM, did a full wipe, cleared the cache and dalvik cache, installed CM10, installed GApps and tried to reboot and flash the CM10 boot.img - however instead of booting back into the bootloader the phone just continued booting and is still at the CM10 boot screen. I can't access bootloader for some reason - i hold down power and volume down, but no bootloader. Is my phone bricked? What can i do?
Appreciate any help. Thanks.
Click to expand...
Click to collapse
Problem sorted now.
what was the problem?
lazo07 said:
what was the problem?
Click to expand...
Click to collapse
I've no idea. I managed to get into the boot loader eventually - It just took multiple attempts! I was sweating bullets for a while there
JMCNZ said:
I've no idea. I managed to get into the boot loader eventually - It just took multiple attempts! I was sweating bullets for a while there
Click to expand...
Click to collapse
How did you manage to fix it? I got into bootloader but everytime i try to get into recovery i get the same bootloop again.
shahravi94 said:
How did you manage to fix it? I got into bootloader but everytime i try to get into recovery i get the same bootloop again.
Click to expand...
Click to collapse
How did you find yourself in that position to begin with? Was it flashing a new rom? Did you flash the boot.img? Don't panic, so long as you have access to the bootloader, you will be ok.
Fastboot erase cache
Then try to enter recovery
Sent from my HTC One X using xda app-developers app
Hi! All my problems became today, when I decided to root that samsung ROM. I used evervolv (old version) I red the instructions and I flashed kernel and boot.img with the htc one V all-in-one toolkit. It said that: "boot.img flashed" I was like: nice, and continued, did full wipe, and wiped cache then I flashed ROM and update. I tried to boot, but it did not boot. After waiting for about an hour I decided to do something. I was able to get to fastboot, and I flashed boot.img manually trough adb and fastboot, did everything like before, and still no boot.
I decided to try some else rom, because I have SD- card reader in my laptop. I putted sphongle to SD- card and I was able to get to fastboot, flashed boot.img, and flashed ROM. Phone was not able to boot, and it just got stuck in a boot loop. I tried samsung again, and now I can only get to recovery or to the white HTC- screen, that has text about build being for developement purposes only. Does anyone have any ideas how-to get my phone back to life, or is it totaly dead? Answes appreciated =)
Enpo said:
Hi! All my problems became today, when I decided to root that samsung ROM. I used evervolv (old version) I red the instructions and I flashed kernel and boot.img with the htc one V all-in-one toolkit. It said that: "boot.img flashed" I was like: nice, and continued, did full wipe, and wiped cache then I flashed ROM and update. I tried to boot, but it did not boot. After waiting for about an hour I decided to do something. I was able to get to fastboot, and I flashed boot.img manually trough adb and fastboot, did everything like before, and still no boot.
I decided to try some else rom, because I have SD- card reader in my laptop. I putted sphongle to SD- card and I was able to get to fastboot, flashed boot.img, and flashed ROM. Phone was not able to boot, and it just got stuck in a boot loop. I tried samsung again, and now I can only get to recovery or to the white HTC- screen, that has text about build being for developement purposes only. Does anyone have any ideas how-to get my phone back to life, or is it totaly dead? Answes appreciated =)
Click to expand...
Click to collapse
Are you flashing correct kernel check that first.
sent from HOV
powered by sphongle 4.2.2
Hmm... I'm pretty sure that I flashed right kernel, but now I can't get to fasboot screen. Only to ClockWork mod recovery. When I boot device, and press vol. down, and power, it always goes to recovery, or if I start to press those buttons a bit later, it only goes to that white HTC screen with red text. =(
E: After a while phone turns screen off, vibrates, and makes the screen again, so some kind of boot loop i guess?
Use the computer, turn it on normally and type in adb reboot bootloader
Sent from my HTC One V using xda app-developers app
mr_nooby said:
Use the computer, turn it on normally and type in adb reboot bootloader
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Was able to get it into fastboot. I flashed kernel and boot.img, those that came with shpongle. Then I did all the wipes and flashed the ROM. Still nothing. Goes into that same screen, and loops there.
Enpo said:
Thanks!
Was able to get it into fastboot. I flashed kernel and boot.img, those that came with shpongle. Then I did all the wipes and flashed the ROM. Still nothing. Goes into that same screen, and loops there.
Click to expand...
Click to collapse
flash this boot img as the one which comes with sphongle rom doesnt boot
http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img :good: :highfive:
I love you so much <3 :victory: :highfive: :good: No homo. Got it working. Thaks everyone *spams that "thanks" button*
Enpo said:
I love you so much <3 :victory: :highfive: :good: No homo. Got it working. Thaks everyone *spams that "thanks" button*
Click to expand...
Click to collapse
haha no problem!
I wish 1ce would post the correct kernel for his ROM
wud save a lot of questions
Hello guys,
So basically my phone shut down while I was using the app drawer. And it got into a boot loop. The phone is rooted, and it has Lean Kernel and Paranoid Android 3.6 installed on it. It tried to factory reset, wipe data, wipe cache, basically do everything in the recovery mode, but it still wouldn't boot. So then I formatted the sd card, and everything else there was to format. And now the phone is just stuck on the word Google. I understand (guess) that's because I've formatted the internal memory. How do I get to flash a rom to the phone now? The computer can't seem to get a connection via USB while the phone is stuck on the word Google. Thanks for your help
Isstatu1 said:
Hello guys,
So basically my phone shut down while I was using the app drawer. And it got into a boot loop. The phone is rooted, and it has Lean Kernel and Paranoid Android 3.6 installed on it. It tried to factory reset, wipe data, wipe cache, basically do everything in the recovery mode, but it still wouldn't boot. So then I formatted the sd card, and everything else there was to format. And now the phone is just stuck on the word Google. I understand (guess) that's because I've formatted the internal memory. How do I get to flash a rom to the phone now? The computer can't seem to get a connection via USB while the phone is stuck on the word Google. Thanks for your help
Click to expand...
Click to collapse
Just ran in to the exact same problem on my girlfriend's phone. Please help. It turns on and I can get into bootloader mode and recovery but when I go to reboot, it just stays on Google startup screen. I did the same things, formatting and such. The sd card is empty with nothing to flash. Help!
Ok, so I've managed to flash another rom. But it only shows me the boot animation and back to the Google logo...
Isstatu1 said:
Ok, so I've managed to flash another rom. But it only shows me the boot animation and back to the Google logo...
Click to expand...
Click to collapse
Flash the stock kernel from The Rom package.
It will boot up.
Sent from my LT26i using xda premium
ADDICT.ANK said:
Flash the stock kernel from The Rom package.
It will boot up.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
I tried installing this kernel and this rom. But it still doesn't boot up. It seems that the kernel is installed on the phone, but the rom isn't, because the command line on the phone doesn't actually write Done or anything else, it just sits there for a while doing nothing.
why dont you flash back to stock using fastboot?
Been there and the "Nexus Root Toolkit" by WugFresh really came in handy. Used the software to go back to stock and since then no problem
Isstatu1 said:
I tried installing this kernel and this rom. But it still doesn't boot up. It seems that the kernel is installed on the phone, but the rom isn't, because the command line on the phone doesn't actually write Done or anything else, it just sits there for a while doing nothing.
Click to expand...
Click to collapse
Via fastboot flash the recovery first and restore from there
and then see..
it should boot up..
or
just flash a stock rom too then.
check the link for stock kernel
http://forum.xda-developers.com/showthread.php?p=44521651
and post here
Ok, so I'm trying the Nexus Root Toolkit right now to get back to stock. But the log shows that archive does not contain:'boot.sig' , 'archive.sig', and 'system.sig'. The process was finished, and it says that stock was isntalled on the phone, but it still stuck in boot loop. It says in the CMD that it might be stuck in boot loop for 5-10 minutes, but it will eventually boot. But the phone still doesn't. And I've also tried to install each .img file through fastboot using this guide. But it still seems to be stuck in bootloop. I've been waiting for 5 minutes, but I'll keep it on for longer...
Update:
Ok, once it showed that :"apps are updating x out of y" and then it started looping again, and then another time it booted until the place where I could choose my language, aaaand it started looping again.
Isstatu1 said:
Ok, so I'm trying the Nexus Root Toolkit right now to get back to stock. But the log shows that archive does not contain:'boot.sig' , 'archive.sig', and 'system.sig'. The process was finished, and it says that stock was isntalled on the phone, but it still stuck in boot loop. It says in the CMD that it might be stuck in boot loop for 5-10 minutes, but it will eventually boot. But the phone still doesn't. And I've also tried to install each .img file through fastboot using this guide. But it still seems to be stuck in bootloop. I've been waiting for 5 minutes, but I'll keep it on for longer...
Update:
Ok, once it showed that :"apps are updating x out of y" and then it started looping again, and then another time it booted until the place where I could choose my language, aaaand it started looping again.
Click to expand...
Click to collapse
Well that is a progress
Try to update the recovery using Nexus Root Toolkit. Push the stock ROM using the advanced option and then flash the stock again using recovery. Wipe cache and dalvik cache then reboot.
Isstatu1 said:
Ok, so I'm trying the Nexus Root Toolkit right now to get back to stock. But the log shows that archive does not contain:'boot.sig' , 'archive.sig', and 'system.sig'. The process was finished, and it says that stock was isntalled on the phone, but it still stuck in boot loop. It says in the CMD that it might be stuck in boot loop for 5-10 minutes, but it will eventually boot. But the phone still doesn't. And I've also tried to install each .img file through fastboot using this guide. But it still seems to be stuck in bootloop. I've been waiting for 5 minutes, but I'll keep it on for longer...
Update:
Ok, once it showed that :"apps are updating x out of y" and then it started looping again, and then another time it booted until the place where I could choose my language, aaaand it started looping again.
Click to expand...
Click to collapse
try to lock your bootloader. if its still unlocked after you reboot your phone, your emmc chip is fried.
Having the bootloop. I've tried the Universal Nexus Tool for Linux and get no boot SIG and recovery SIG error.
I can't get it to boot at all. :/
Sent from my Nexus 7 using xda app-developers app
Zepius said:
try to lock your bootloader. if its still unlocked after you reboot your phone, your emmc chip is fried.
Click to expand...
Click to collapse
I locked it with "fastboot oem lock" and after taking out the battery it says that the bootloader is locked. So I guess the emmc chip is fine?
By the way, is emmc memory related in anyway to the Lagfix(fstrim) app that I've got from Google Play to speed up my Nexus? Maybe the problem is somewhere there?
Also, If I'd locked the bootloader and took it to the Sprint store, would they try to fix it even though I had the phone for more than a year?
I've tried everything and still a bootloop. No matter if I recover to stock or flash a custom ROM.
Sent from my Nexus 7 using xda app-developers app
Fixed the problem by buying a Nexus 5...