Related
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!
I'm sure you've had thousands of threads about this and I've probably looked through 90% of them, I've also looked through the Desire troubleshooting to no avail. I believe I have a specific issue. I have a HTC Desire S which, whenever I turn it on, gets stuck on the '3' logo (it's a Three branded phone I believe). I can go into HBoot where I have the options of fastboot, recovery, factory reset, simlock and image crc. Both recovery and factory reset give me the '3' logo screen. Also, I have no idea why it has this boot problem, my brother bought this phone from someone and I'm trying to fix it for him.
Attempted Solutions:
1. I've tried RUU. This goes past the 'Updating Signature' upto 18% where it is "checking MID/CID" which makes the phone boot up (?) and I get the same '3' logo screen for ages.
2. I've tried S-OFF and flashing boot.img, recovery.img, system.img but I get the same screen when I reboot.
3.I noticed hboot looking for a PG88DIAG.ZIP? So I downloaded this, extracted it and put it on a SD card. It boots up into some diagnosis thing where I can run a few tests and write something (mentions something about IMEI). Obviously have no idea what this is for so I'm not messing about with it. It probably is of no use to me.
Basically it seems whatever I do I still get stuck on the boot screen.
Do you guys have any ideas or is it a hardware fault?
Your help is greatly appreciated.
Thank you.
Install abd and fasboot (follow the guide in my signature)
Reboot it to bootloader screen (whre you see RECOVERY/IMAGE CRC, etc options). There should be written "FASTBOOT USB" on the screen when you connect it to PC. If not select the fastboot option from the menu
Type in cmd on the PC while connected in fastboot mode:
Code:
fastboot getvar version-main
Download a RUU that hav the same number like your version in its name (example 2.10.401.8 is for Europe) and run it, while connected in fastboot usb mode
themetcast said:
3.I noticed hboot looking for a PG88DIAG.ZIP
Click to expand...
Click to collapse
edit: sorry, was wrong
What does your bootloader show exactly ?
There are too many things you're doing wrong, while thinking that your issue is "special" - instead of reading more thoroughly and understanding that you're doing just about everything wrong.
1) You're trying to install a wrong RUU. RUU should either match your CID or you should use goldcard - and in any case RUU version number should be same or bigger than your current main version.
2) You're unlocking the phone, since you can't achieve S-OFF without functional ADB. If you're unlocked - your bootloader should read "UNLOCKED" and remain S-ON. In any case fastboot flash system.img will likely fail.
3) You didn't attempt a basic thing - factory reset (can be done using bootloader menu).
But I can already tell that things don't look good for you - if you've successfully unlocked through HTCDev and flashed recovery, the flash went well but you still see the phone stuck on logo when trying to boot into recovery - it means that your eMMC has probably failed, which means your phone is dead.
amidabuddha said:
Install abd and fasboot (follow the guide in my signature)
Reboot it to bootloader screen (whre you see RECOVERY/IMAGE CRC, etc options). There should be written "FASTBOOT USB" on the screen when you connect it to PC. If not select the fastboot option from the menu
Type in cmd on the PC while connected in fastboot mode:
Code:
fastboot getvar version-main
Download a RUU that hav the same number like your version in its name (example 2.10.401.8 is for Europe) and run it, while connected in fastboot usb mode
Click to expand...
Click to collapse
version-main: 2.13.771.4
I've tried RRUs that are above that and below. I've tried H3G, Europe, WWE? Any ideas?
Thank you.
Jack_R1 said:
There are too many things you're doing wrong, while thinking that your issue is "special" - instead of reading more thoroughly and understanding that you're doing just about everything wrong.
1) You're trying to install a wrong RUU. RUU should either match your CID or you should use goldcard - and in any case RUU version number should be same or bigger than your current main version.
2) You're unlocking the phone, since you can't achieve S-OFF without functional ADB. If you're unlocked - your bootloader should read "UNLOCKED" and remain S-ON. In any case fastboot flash system.img will likely fail.
3) You didn't attempt a basic thing - factory reset (can be done using bootloader menu).
But I can already tell that things don't look good for you - if you've successfully unlocked through HTCDev and flashed recovery, the flash went well but you still see the phone stuck on logo when trying to boot into recovery - it means that your eMMC has probably failed, which means your phone is dead.
Click to expand...
Click to collapse
First of all, thank you for taking your time out to reply. Really appreciate it.
1) I'm using a gold card, I'm not sure if I successfully managed to create one? How do I tell once I've plugged it in? Another option for me was to order a 2GB Kingston card just to be sure I have a fully functioning gold card as this unbranded microsd card might not be compatible?
2) Oh yes, you're right! Would S-OFF help me? (even though it's not possible right now).
3) If you read OP I said that the factory reset takes me to the '3' screen.
I believe the phone is pretty much dead so it could be that.
themetcast said:
version-main: 2.13.771.4
I've tried RRUs that are above that and below. I've tried H3G, Europe, WWE? Any ideas?
Click to expand...
Click to collapse
The only availabe that will work for you is RUU_Saga_H3G_UK_1.31.771.1_Radio_20.28b.30.0805U_3 8.03.02.14_M_release
But it needs a change of the main version which is possible only via adb that you do not have.
Actually the ICS RUU should debrand your device but if it failes than JackR1 is most probably right and your chip is gone
themetcast said:
1) I'm using a gold card, I'm not sure if I successfully managed to create one? How do I tell once I've plugged it in? Another option for me was to order a 2GB Kingston card just to be sure I have a fully functioning gold card as this unbranded microsd card might not be compatible?
2) Oh yes, you're right! Would S-OFF help me? (even though it's not possible right now).
3) If you read OP I said that the factory reset takes me to the '3' screen.
I believe the phone is pretty much dead so it could be that.
Click to expand...
Click to collapse
1) If RUU fails CID check - it means goldcard doesn't work. That's pretty much the only check I know. You can try a separate card, or you can try to format your card in PC and make a goldcard again - there are several methods and several tools for the job.
2) It would help you - because it would allow you to flash unsigned PG88IMG.ZIP that you could create with whatever you want as main_version. But you can't achieve it without a functional ADB, which you're not getting to, and even with HTCDev unlock you should still be able to boot into the recovery you're flashing. If it doesn't happen - it means something is bad, and it's most likely the HW.
The suggested method would be to create a good goldcard and run ICS RUU. If it fails - the diagnosis is clear, if it succeeds - you'll either boot or know that the boot fails because of HW failure - but not eMMC, something else.
My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP
Hi guys n gals
it appears ive inadvertantly deleted my rom i successfully unlocked bootloader installed recovery but over killed me wiping. Sso ive got an unlocked bootloader, have access to fasboot and recovery but fone is stuck at bootlader screen. How do I flash a rom now? as when hooked to a pc its no longer recognised. any help much appreciated!!!
moh19814 said:
My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP
Click to expand...
Click to collapse
I seem to be in the same situations... although I got to it in a different way. Where did you download the RUU from? is it version-main: 4.14.401.2 or higher?
Try: rootwiki dot net and search for htc one mini bootlocker unlock....this helped me to UNLOCK and put TWRP recovery on it... maybe it gets you a step closer.
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.
Hi all,
I bricked my device. I was doing a rollback from 380, the rollback package went fine than I used dload to install 131 , it went to 55% then an error occured - the phone was supposed to reboot but nothing happened. The phone does not respond to any combinations of buttons and I can't manage to wake it up in any way. Does anyone have this issue? Many thanks
me too, but after many methods i found the bootloader locked even if show unlocked, and i use "HCU Client" and spend 4$ to show me new bootloader unlock code ... and after that I unlocked bootloader and flash "Boot, Recovery, System, Cust"
But will I able to do anything / unlock the bootloader if the phone is not reacting to anything? It is not seen by the computer or does not wake up to any button combinations?
thedark1979 said:
me too, but after many methods i found the bootloader locked even if show unlocked, and i use "HCU Client" and spend 4$ to show me new bootloader unlock code ... and after that I unlocked bootloader and flash "Boot, Recovery, System, Cust"
Click to expand...
Click to collapse
HCU can't see my device unfortunately
Ok. My phone was repaired under warranty. They changed the motherboard as well as the screen. It went well after all...