Develop Bugs

[Q] stupid family...stuck on htc boot screen

OK so I need some serious help. I'm not a total n00b but I'm still fairly new to the rooting world.
I recently rooted my dinc and installed the new cyanmogen 7 to bring it to gingerbread. I had let my sister use my updated phone because she has a dinc too and was considering doing the same.
She was messing around with it and downloaded something from the marketplace and when she ran it the entire phone shut off. I don't know what she installed and when asked she doesn't know either. When I boot the phone it stays at the htc boot screen and will not go any further. I've tried a recovery which all the forum topics tell me to do and unfortunately it doesn't give me the option to load anything from my sd card. The only menu options under recovery are: Bootloader, reboot, reboot bootloader and power down.
When I plug my phone in my Windows 7 comp it isn't found as a drive and only shows up under device manager. If it makes a difference I rooted using unrevoked3. I'm not sure what I can do at this point. Please keep in mind that although I'm not 100% new at this I'm still really unfamiliar with it all.
What can I do to get my phone working properly again? I don't care if its from a factory reset I just need to get it working.
Thanks!

The white screen with your device info is not the recovery menu, it's the Bootloader/HBOOT menu. Select Bootloader from that menu and you will be given an option to reboot into recovery, most likely ClockworkMod Recovery. Once there you should be able to restore from a backup or reinstall Cyanogen 7.0.
If you cannot boot into recovery download the latest OTA update here. Rename it to "PB31IMG.zip" and put it on your SDcard. Reboot into the bootloader and it will detect the PB31IMG update and press Volume Up to apply it.
You'll need to root your phone again after this, though.

thank you!!
it worked perfectly...thanks!!!!!!!!

Glad to hear it!

TWRP boot loop...

So I have been running the AOKP nightlies in Goo and Ktoons kernel. This has been a very trouble free combo. However, out of nowhere I go to reboot in recovery and it takes a dump. Mind you its been running fine all weekend. It will get right to the Teamwin splash and start boot looping. All I did was reboot. Recovery is now broken, so I odin CWM on and that gets me back to a recovery, but when I try to flash TWRP again same issue. So I put CWM back on, factory reset, reflash, wipe everything, sticks on boot splash on every build. Finally, I gave up flashed back to stock, and re-rooted....lost all my stuff on the internal card but I was able to re-install TWRP and restore my backup.
This is so very random and frustrating...it just randomly for no reason stopped booting to recovery. Is this a common thread with TWRP? Maybe I should go back to CWM...anyone had this same experience?

I had that problem too. It lead to me getting bricked because I can't get Odin to work. Could you view over the post and confirm similar problems? I think some of my issue is with TWRP. I made dumb with my ROM, but the recovery shouldn't have messed up... Anyway here's the post. Let me know if you think the problems (with TWRP) are similar. If they are, there might be something wrong with TWRP
Kilo__ said:
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 1 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Click to expand...
Click to collapse

Phone turns on, HTC logo shows up, recovery works but phone DOES NOT BOOT

My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?

rfgamaral said:
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
Click to expand...
Click to collapse
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely

Tarima said:
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Click to expand...
Click to collapse
Tried to reflash Maximus, didn't work, still didn't boot. Backed up everything I could and wiped everything, I'm now on Lineage OS 16.0. Thanks for your reply.

Stuck in boot loop even after factory reset. Able to get into bootloader and recovery

Hoping for some help or alternatives to fix my fiancee's Pixel XL. Last night the phone just kept flashing the 'G' logo on for 10 seconds, off for 10 seconds. She said the phone was close to dying before it happened, and I imagine it probably ended up draining the battery afterwards with the constant bootloop. Plugged it in all night but the charging screen didn't come up and would just stay in the bootloop. I could get it into the boot loader (power button and volume down), but it wouldn't go into recovery mode and instead would go right back to the boot loop.
So I tried a battery pack to charge it and it still didn't show charging, but I was able to get it into recovery mode eventually, but still boot loop afterwards. At one point, after leaving it on boot loader menu while attempting to charge, it eventually just tried to start itself and made its way to the second Google splash screen after the main G logo. Looked like it froze there though and I couldn't get it to that point again.
On my way to work this morning I tried plugging it into my car's USB port after powering off from the boot loader, and this time I kept flashing that it was charging (looked like it was 3/4 charged but not sure how accurate that is). So I got into recovery again and tried 3 factory resets consecutively. Still bootloop after attempting a startup afterwards. There was a similar issue a couple weeks ago where it looked like it was stuck in a bootloop, but it turned out the phone actually was dead that time and the charger wasn't working. Once we switched chargers it booted right up.
Any other suggestions or possibilities? I don't have much troubleshooting experience otherwise. Phone is fully stock, Google Fi. Any other info I can provide please let me know!

well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.

cgibsong002 said:
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
Click to expand...
Click to collapse
I assume you can't get into the bootloader using power and volume down buttons?

I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.

My OG Pixel did the same thing to me one morning. I tried everything to revive my pixel but nothing worked. I did some digging and it turns out there is an issue with the storage on the phone. It's just a old fancy paper weight.

cgibsong002 said:
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
Click to expand...
Click to collapse
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?

mozhno said:
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
Click to expand...
Click to collapse
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.

cgibsong002 said:
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
Click to expand...
Click to collapse
Sounds as if it's time to just try stuff and see what sticks. Regarding using an ota, it works if you are stock, and I sideload it even if I have installed majisk or installed another kernel. It typically works for me with fewer chances of blowing things up than flashing a stock image. Regarding what to try next, you may have already gone into recovery to check the install function to see if your storage still appears and try to flash anything that worked in the past; if you have a backup in twrp you could try to restore it; you could wipe cache and dahlvik; or even sideload an earlier ota version that worked. Since the 6-5 ota did not work nothing really jumps out to me as obvious. One final caveat, I once had to reboot a sideloaded ota a second time before my pixel booted properly. If I think of something else I'll post again.

I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.

cgibsong002 said:
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
Click to expand...
Click to collapse
Good luck

I'm assuming you tried booting into twrp recovery, going to reboot, and picked slot A ( or B if already in A) to reboot to and then rebooted system? A lot of the times simply switching slots from recovery and then rebooting is the fix. At least for me.

手机早期经历的情况得说明一下。root没有？Twrp是谁的？

Also, for anyone else having this issue, try rebooting into the bootloader. Connect to PC, and try fastboot --set-active=a
If this doesn't work, try booting back into your recovery image using fastboot boot *whatever you named your TWRP recovery image* and then flashing your twrp.zip again in recovery, and when rebooting if you're in slot B choose slot A in recovery to boot into.
Also keep in mind in Windows 10, it uses Powershell, so commands have to be typed in .\fastboot not just fastboot or it won't take it.

Razer phone 1 bootloop

I was recently trying to do the latest OTA update on y razer phone 1, but I seem to have messed things up. Now my phone is in a boot loop, I can't get to the bootloader or recovery with the volume buttons, and it won't boot past the logo, so I can't use adb to get there either. Not sure what to do. Basically it's turning on, showing that the device is untrusted cause of the unlocked bootloader for 5 seconds, then turning off. I'm not sure what to do.
I have/Had (Not sure) Twrp as my recovery, and reflashed my boot.img... I'm guessing I flashed the wrong one.
I can confirm that I no longer have twrp. I managed to boot to recovery, and it's the OG. It's all rainbow static, but I can tell that it's a menu with 9 options, and the third one lets adb see my phone. At this point, I'm not flashing anything or really touching anything till someone can tell me what I did wrong/how to fix it. Would a factory reset make things better? Or worse?