[Q] Phone stuck in bootloop after flashing recovery - HTC First

Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!

help me
lastrastuff said:
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
Click to expand...
Click to collapse
Did this work? my first has been in a boot loop for months. I can't get ADB, Fastboot or RUU to recognize the device.

sara_groves said:
Did this work? my first has been in a boot loop for months. I can't get ADB, Fastboot or RUU to recognize the device.
Click to expand...
Click to collapse
Well I have a working phone if that's what you mean. If you are able to get your phone into fastboot you can go through with an RUU usually.

lastrastuff said:
Well I have a working phone if that's what you mean. If you are able to get your phone into fastboot you can go through with an RUU usually.
Click to expand...
Click to collapse
I with it some more last night. I did finally get ADB to work, but still no fastboot. Shop i was able to push in filters... i just have no way of flashing.

bootlaoder block you should have before making the ruu to lock the bootloader needs to enter fastboot, in fastboot type this command fastboot oem lock, try it on mac as it would not need to install drivers.

Ok this guide works for me!
the problem is this traslate for spanish, a don't speak english, i hope you fix your phone...
http:/ /www. htcmania. com/ showthread. php?t=548748

lastrastuff said:
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
Click to expand...
Click to collapse
It seems your phone stuck in a bootloop after flash a rom and kernel,are you sure the rom and kernel is ok?

Related

[Q] Nexus One won't boot

Hi all. I haven't been able to boot my Nexus One for months now. It all started with the random reboot problems that many have reported, but now it won't boot at all. I never rooted it or flashed it with a non-stock Android. It's always run stock OS. If I remember well, the last build installed was FRF91.
I've read dozens of threads, tried hard resetting, Recovery, and the latest thing I tried was a restore with the PASSIMG.zip method explained here http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
It does not seem to have gone well, because step [2]Radio_V2 showed error message "Fail-UZ" and [6] System "Fail-PU". Then it got stuck at the screen attached.
I'm starting to think I've got a faulty battery along with a software problem: when I've got a full charge, I can only perform one operation (power on, recovery, hard reset, whatever), and it usually freezes in the middle of it, usually with that three time vibration. Then, I've got to wait a long time before it can even charge and show the charging LED again.
Any help in getting my agonizing Nexus back will be highly appreciated. Thanks a lot.
Am I seeing what I'm seeing?
You have SHIP S-OFF Nexus, which means - no security. And you're still locked???
Unlock your bootloader, and execute "Unroot/restore" guide from Wiki, for unlocked bootloader. Which means - direct flash to partitions using "fastboot flash" command.
Thanks a lot, Jack. I'll give it a try this weekend. I've got my Nexus as a present at an Android event at Mobile World Congress 2010, that might explain unusual factory settings.
Unlock bootloader OK, but still no restore
I unlocked the bootloader, but still couldn't restore with PASSIMG.zip method. It still gives out radio fail, and restoring the system got frozen at "unzipping". After a long while, it vibrated 7 times, but is still frozen there.
Should I try older stock versions for the PASSIMG.zip restore? I'm using FRG33 right now. Hopefully I didn't brick it.
Thanks again in advance. Best.
Read my suggestion above again, please.
I didn't suggest you to use PASSIMG method. I suggested something else.
Got it
I see what I did wrong, thanks for the response again and putting up with a novice. I somehow missed the link to the Fastboot flash method, thought I was doing the right thing. I'll try fastboot when and if my N1 wakes up from one of it's long slumbers. Best

[Q] flashing boot.img help please

hello , after unlocking bootloader and rooting phone i had a real hard time getting s-off so i just left that part , i installed a few custom roms that just stayed on the htc boot logo but i backed up my stock rom so i could go back to it if needed , but now when i click restore in cwm it gets to white htc screen then reboots back to recovery , ive tried flashing boot.img but it says "error: cannot load 'boot.img'" so im just stuck at the minute so any help would be great , my phone is >>>>
UNLOCKED
VIVO PVT SHIP S-ON IRL
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
eMMC-boot
May 22 2012,14:22:08
http://bit.ly/RZr2S8
hmmmmm
ive tried searching for it and found ways to do it but its not working for me so i came in here looking for help only to get sarcastic reply , not helpfull at all
You should not be attempting something that you obviously have no knowledge about. Your reply that you have searched and have found ways but they are not working is proof enough of this. The first hit of my "sarcastic" reply is a method that will definitely work on our phone, there are also guides in this very section as well as many other noobs asking this very same question countless times.
You may have "searched", but you obviously have not "looked" or "read".
oh lord
Nonverbose said:
You should not be attempting something that you obviously have no knowledge about. Your reply that you have searched and have found ways but they are not working is proof enough of this. The first hit of my "sarcastic" reply is a method that will definitely work on our phone, there are also guides in this very section as well as many other noobs asking this very same question countless times.
You may have "searched", but you obviously have not "looked" or "read".
Click to expand...
Click to collapse
ive rooted , unlocked bootloader , gained s-off on lots of android devices before its this one is throwing up problems that i cant figure out i came here for a bit of friendly advice nothing more , and everyone started out having no knowledge of this at one point but had to start somewhere !! please dont reply you've had your say now ty
DJxDECKSTAR said:
ive rooted , unlocked bootloader , gained s-off on lots of android devices before its this one is throwing up problems that i cant figure out i came here for a bit of friendly advice nothing more , and everyone started out having no knowledge of this at one point but had to start somewhere !! please dont reply you've had your say now ty
Click to expand...
Click to collapse
Make sure you change to your fastboot directory and your boot.img file exists in your fastboot directory....
Once entered command
fastboot flash boot boot.img
it should work, even I had got the same error, so I just pulled cable, connected back and entered same command.. It worked..
Psst: make sure that its written fastboot usb in the bootloader screen. If not written, then USB is faulty
Rah0ol said:
Once entered command
fastboot flash boot boot.img
it should work, even I had got the same error, so I just pulled cable, connected back and entered same command.. It worked..
Psst: make sure that its written fastboot usb in the bootloader screen. If not written, then USB is faulty
Click to expand...
Click to collapse
When you're in fastboot you can do
"Fastboot devices" to see of its connected properly
You will see your serial number.
Sent from my Nexus 7

[Q] HTC One Soft/Bricked Boot Loop

Hi Everyone
I humbly approach you today with a HTC One issue, that needs solving as I have no phone as a result.
So to put it simply I Unlocked and Rooted my device through this guide .
/watch?v=kJYAS2KN17Y
Following that I proceeded to gain S-OFF, or at least I believe I did. Checked the Bootloader after and it said S-ON :S Through this guide.
/watch?v=NeFwsqU4YL4
All seemed well up to this point, so then I followed to this guide to install 4.4 KitKat on my HTC One (I am based in the UK, and the network my phone runs in is O2).
/watch?v=AySbx90YB-s
However as it turns out, my phone will now turn on, I will reach the default Android Language Selection menu, and my phone reboots automatically before I can even press anything. I have tried to re-install the "bigxie_Reset_M7_3.62.401.1.zip" several times, and nothing has come from it.
So I attempted to restore my stock HTC rom, using the "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_A4.13.3231.27_10.31.11131.05_release_310878_signed.exe" and it fails every time, and it also detects no image when I run it, it simply shows what image it will install.
Additionally I tried all possible USB ports on my computer to check for a faulty USB port with RUU, I have tried to push "Guru_Reset_M7_3.62.401.1.zip" through CMD (I am running windows of course) and naturally it hasn't worked (the push). Having not made a Backup because I blindly followed the tutorials, I have nothing to go back to.
I think the problem is that S-ON is enabled and I can't seem to find how to solve it, or enable S-OFF using the AIO Toolkit and pushing Revone. Anything that could help me get my phone working, and hopefully with stock Android will be greatly valued. Thank you for taking the time to read this .
Do not lock bootloader
sent from my mobile device
I am not so good at android but.......a way to S-OFF HTC One would be using this video - /watch?v=MCMJkVbIiIg
It basically uses rumrunner to do so and for me it worked flawlessly
Hope you can fix your One soon.
FIXED!
DroxX said:
I am not so good at android but.......a way to S-OFF HTC One would be using this video - /watch?v=MCMJkVbIiIg
It basically uses rumrunner to do so and for me it worked flawlessly
Hope you can fix your One soon.
Click to expand...
Click to collapse
Thank you for replying guys!
I actually managed to fix it by pushing TWRP instead of CWR and then installed Android_Revolution_HD-One_31.6.zip got my OS back and now trying to enable S-OFF.
:good:
DroidDoode said:
Thank you for replying guys!
I actually managed to fix it by pushing TWRP instead of CWR and then installed Android_Revolution_HD-One_31.6.zip got my OS back and now trying to enable S-OFF.
:good:
Click to expand...
Click to collapse
Gratioz!!!!! Good luck for getting S-OFF.
I used rummrunner to get S-off. Works like a charm. Takes a bit of time to do it though, don't close it whilst it's doing it's thing!

flushing ruu will not end

I'm flushing a tmibile ruu into rooted with custom ROM. I did all step. Installed drivers, relocked bootloader, launched the exe all went well except that the whole operation should take about 10min. It's been an hour now and it's not finished, it's still updating. That's not normal. Am I doing something wrong? Any suggestion on what to do to finish this update up.?
dihcar said:
I'm flushing a tmibile ruu into rooted with custom ROM. I did all step. Installed drivers, relocked bootloader, launched the exe all went well except that the whole operation should take about 10min. It's been an hour now and it's not finished, it's still updating. That's not normal. Am I doing something wrong? Any suggestion on what to do to finish this update up.?
Click to expand...
Click to collapse
If your sure your using the correct ruu it could be HTCSync. Do you have it installed. If you do uninstall it but leave drivers installed. Reboot your pc and try again. HTCSync is known to interfere with RUU mode
Other than that just make sure you have the correct ruu. It should match your MID and CID and if your s-on it must match or have a newer firmware than you currently have :good:
Danny201281 said:
If your sure your using the correct ruu it could be HTCSync. Do you have it installed. If you do uninstall it but leave drivers installed. Reboot your pc and try again. HTCSync is known to interfere with RUU mode
Other than that just make sure you have the correct ruu. It should match your MID and CID and if your s-on it must match or have a newer firmware than you currently have :good:
Click to expand...
Click to collapse
I have htcsync unstalled, I'll try to uninstall it. The ruu is T-Mobile'd that's what it say.
I'll give it another try. Later on. Thanks
finally I was able to flash my m7 to tmobile stock, I did nothing special except I repeated the operation and the third time was a charm. buuuut now I'm confronted with another problem, the phone randomly reboots with no reason, I tried to fix that by booting in safe mode didn't help, got into recovery and wiped cache partition didn't help either and now am stuck again. the phone is unusable as it is. any HELPFUL suggestion will be very welcome.
dihcar said:
finally I was able to flash my m7 to tmobile stock, I did nothing special except I repeated the operation and the third time was a charm. buuuut now I'm confronted with another problem, the phone randomly reboots with no reason, I tried to fix that by booting in safe mode didn't help, got into recovery and wiped cache partition didn't help either and now am stuck again. the phone is unusable as it is. any HELPFUL suggestion will be very welcome.
Click to expand...
Click to collapse
is your phone T-mobile US ?
try this RUU >> http://www.htc.com/us/support/htc-one-t-mobile/news/
clsA said:
is your phone T-mobile US ?
try this RUU >> http://www.htc.com/us/support/htc-one-t-mobile/news/
Click to expand...
Click to collapse
Yes T-Mobile and I flushed the same RUU as in your link it's the latest.
dihcar said:
Yes T-Mobile and I flushed the same RUU as in your link it's the latest.
Click to expand...
Click to collapse
Check in the phone settings
Settings>About>Phone Identity - Is your Imei displayed as Unknown? Also check baseband in
Settings>About>Software Information>More - is it displayed as Unknown also?
Danny201281 said:
Check in the phone settings
Settings>About>Phone Identity - Is your Imei displayed as Unknown? Also check baseband in
Settings>About>Software Information>More - is it displayed as Unknown also?
Click to expand...
Click to collapse
I did that already all informations are displayed imei...etc. The software too that's how I knew it's the same ruu. The #s match.
dihcar said:
I did that already all informations are displayed imei...etc. The software too that's how I knew it's the same ruu. The #s match.
Click to expand...
Click to collapse
Can you post the output of
Code:
fastboot getvar all
What type of bootloop are you having, looping before its finished booting or is it booting up ok then randomly restarting.
Did it bootloop immediately after flashing the ruu or did you flash something after like a custom recovery or rom?
Danny201281 said:
Can you post the output of
Code:
fastboot getvar all
What type of bootloop are you having, looping before its finished booting or is it booting up ok then randomly restarting.
Did it bootloop immediately after flashing the ruu or did you flash something after like a custom recovery or rom?
Click to expand...
Click to collapse
It reboots randomly sometimes just after boot loop when swept lock screen to get to home, sometimes it for about 10min then reboots. I'm not rooted anymore I have stock recovery that's why I flashed the ruu. Because when I was running custom ROMs, there was no random reboot but the baseband was unknown, no radios I couldn't connect to network. I tried to flash tmo radio through twrp it succeeded but baseband remained unknown. That's why I wanted to unroot and go back to stock. Sorry I don't know the history of this phone. That's the way i got it rooted, unlocked bootloader, twrp recovery running cm11 with no baseband.
dihcar said:
It reboots randomly sometimes just after boot loop when swept lock screen to get to home, sometimes it for about 10min then reboots. I'm not rooted anymore I have stock recovery that's why I flashed the ruu. Because when I was running custom ROMs, there was no random reboot but the baseband was unknown, no radios I couldn't connect to network. I tried to flash tmo radio through twrp it succeeded but baseband remained unknown. That's why I wanted to unroot and go back to stock. Sorry I don't know the history of this phone. That's the way i got it rooted, unlocked bootloader, twrp recovery running cm11 with no baseband.
Click to expand...
Click to collapse
Unknown IMEI and Baseband Most likely a hardware problem. If you have warranty i would return to stock and send it for reapair :good:
That's a why I asked you to check these settings.
Danny201281 said:
Check in the phone settings
Settings>About>Phone Identity - Is your Imei displayed as Unknown? Also check baseband in
Settings>About>Software Information>More - is it displayed as Unknown also?
Click to expand...
Click to collapse
If flashing an RUU didn't fix it then its probably hardware related :good:
Danny201281 said:
Unknown IMEI and Baseband Most likely a hardware problem. If you have warranty i would return to stock and send it for reapair :good:
Click to expand...
Click to collapse
Wow no hope!? how sure are you about that!
Like I said I have no warranty. Maybe a good motherboard will fix it, otherwise like you said I'll send it to the reaper! lol.
dihcar said:
Wow no hope!? how sure are you about that!
Like I said I have no warranty. Maybe a good motherboard will fix it, otherwise like you said I'll send it to the reaper! lol.
Click to expand...
Click to collapse
I have come across many cases of this on the forum. Only one of them I was able to help get working again and the symptoms were slightly different. There was no RUN in that case so we returned it to stock with a ROM and firmware package and it was working normally again. Obviously the RUU will have done this for you.
Only 1 other i know of that was repaired and it was opened up and to the best of my knowledge the Antenna Connector wire was replaced. And it solved the problem. I'll try track down a link for that one and post it here.
Danny201281 said:
I have come across many cases of this on the forum. Only one of them I was able to help get working again and the symptoms were slightly different. There was no RUN in that case so we returned it to stock with a ROM and firmware package and it was working normally again. Obviously the RUU will have done this for you.
Only 1 other i know of that was repaired and it was opened up and to the best of my knowledge the Antenna Connector wire was replaced. And it solved the problem. I'll try track down a link for that one and post it here.
Click to expand...
Click to collapse
Just FYI after the flash the baseband and imei are there.
This is the baseband 4T.28.3218.04_10.33E1718.01L it's a tmobile and it looks normal.
dihcar said:
Just FYI after the flash the baseband and imei are there.
This is the baseband 4T.28.3218.04_10.33E1718.01L it's a tmobile and it looks normal.
Click to expand...
Click to collapse
Well and i'm clutching at straws here, but have you tried flashing it multiple times before booting the device. Maybe that will help it stick??
Danny201281 said:
Well and i'm clutching at straws here, but have you tried flashing it multiple times before booting the device. Maybe that will help it stick??
Click to expand...
Click to collapse
Yeah I'll try that when I get little more time. Meanwhile thanks and happy new year or holidays. :angel:
update
I did flash the ruu once again it was worse, I did not go past the lock screen. as soon as I swipe to get to home it reboots. now I decided rooting it again and using a custom rom like cm11 or smoothliquid, the rebooting problem did not exist when I used them, but I hope the base band holds there this time.
I succeeded to submit a token to htddev to unlock bootloader again, and I'm waiting for the unlock code bin email. it's been like 10hrs and still nothing. should I do something or just wait?
dihcar said:
I did flash the ruu once again it was worse, I did not go past the lock screen. as soon as I swipe to get to home it reboots. now I decided rooting it again and using a custom rom like cm11 or smoothliquid, the rebooting problem did not exist when I used them, but I hope the base band holds there this time.
I succeeded to submit a token to htddev to unlock bootloader again, and I'm waiting for the unlock code bin email. it's been like 10hrs and still nothing. should I do something or just wait?
Click to expand...
Click to collapse
CM11 will stop the rebooting, I don't know why but it does. It won't fix it though. But at least the device will be stable.
This issue is also known to get worse overtime. So I think it will only get worse.
If you have your original unlock_code.bin you can just flash it again you don't need to wait for htcdev.
If you don't have it on your pc see if you still have the original e-mail it was attached to. :good:
Danny201281 said:
CM11 will stop the rebooting, I don't know why but it does. It won't fix it though. But at least the device will be stable.
This issue is also known to get worse overtime. So I think it will only get worse.
If you have your original unlock_code.bin you can just flash it again you don't need to wait for htcdev.
If you don't have it on your pc see if you still have the original e-mail it was attached to. :good:
Click to expand...
Click to collapse
I don't have the first one, I was given the phone already rooted, I checked my spam nothing should I wait or submit again?
dihcar said:
I don't have the first one, I was given the phone already rooted, I checked my spam nothing should I wait or submit again?
Click to expand...
Click to collapse
Well given its new years day it may take a little longer than usual. So I would just wait it out :good:

[Q] Can't access Recovery when trying to load twrp

Hi Everyone,
First off I am a total novice and I put my hands up to say I should not have tried to root my phone. I merely wanted to root so that I could actually use the space on my SD card, which the HTC Desire doens't.
I did try to do this manually by reading a few guide and walkthroughs with no success. So then I used the sunshine app to unlock my bootloader and then WinDriod to load TWRP recovery and then hopefully root the phone. It does say ***unloacked*** on the fastboot menu. However, I sort of messed up my phone.
I cannot load into recovery mode - it goes to a HTC load screen then right back to fastboot usb menu.
I cannot factory restore the phone either.
Can anyone advise me how to return my phone to its normal state or advise on how to fix this problem?
Appreciate any help anyone can give me!
bbop107 said:
Hi Everyone,
First off I am a total novice and I put my hands up to say I should not have tried to root my phone. I merely wanted to root so that I could actually use the space on my SD card, which the HTC Desire doens't.
I did try to do this manually by reading a few guide and walkthroughs with no success. So then I used the sunshine app to unlock my bootloader and then WinDriod to load TWRP recovery and then hopefully root the phone. It does say ***unloacked*** on the fastboot menu. However, I sort of messed up my phone.
I cannot load into recovery mode - it goes to a HTC load screen then right back to fastboot usb menu.
I cannot factory restore the phone either.
Can anyone advise me how to return my phone to its normal state or advise on how to fix this problem?
Appreciate any help anyone can give me!
Click to expand...
Click to collapse
Hello,
Since you asked for help with returning the phone to it's normal state I have some questions. Does the phone work normally? Can you make calls, text, and do other things when you simply power your phone on or is the OS deleted? Are you just referring to obtaining stock recovery or do you still want to get TWRP? It sounds like some error happened when you tried to flash TWRP and now you have no recovery. Here is a great guide that shows you how to flash TWRP. You can use that same guide to flash the stock recovery. That channel also has videos with an alternate method to unlock your bootloader and how to root the phone.
My phone works fine, makes calls, texts etc, I just can't boot into recovery. I tried several methods, following online videos etc to no avail, but ill give this one a go this evening. I mentioned returning it to its original state so I could start over with the flashing process as nothing seems to allow me to load into twrp, so i wondered if there was a corrupt file or something preventing me from doing so. The phone's bootloader is unlocked I believe as it says so on the hboot screen.
Thanks for the suggestion, ill let you know how it goes.
bbop107 said:
My phone works fine, makes calls, texts etc, I just can't boot into recovery. I tried several methods, following online videos etc to no avail, but ill give this one a go this evening. I mentioned returning it to its original state so I could start over with the flashing process as nothing seems to allow me to load into twrp, so i wondered if there was a corrupt file or something preventing me from doing so. The phone's bootloader is unlocked I believe as it says so on the hboot screen.
Thanks for the suggestion, ill let you know how it goes.
Click to expand...
Click to collapse
The method in that video should work perfect. I doubt there was a corrupt file, but we'll find out soon enough. I have a love/dislike relationship with WinDroid. I love it, because of how easy it is to use and it requires little to no knowledge of what you are actually doing and it is just a beautiful looking program. I dislike the fact that you pretty much learn nothing when you use it, as it does all of the work. Also, if you use the adb drivers it provides and you already have adb drivers, you will receive an error that the adb server is out of date.

Categories

Resources