Develop Bugs

[Q] so this is my problem

I have a one X unlocked international version which I had rooted and set up a recovery. I then went on to try to flash over ARHD after super wiping, and did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery. Anyways, from here this is where it goes bad. After restarting it goes into a boot loop and ends up getting kicked back into bootloader. After this I try to factory reset to no avail. After trying to reflash the rom a couple times using recovery, recovery just died and won't even load anymore. In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Any suggestions on how to fix this and get it back up and running, or am I forced to send it to HTC the moment they bring in parts for it. (right now HTC says there is a wait on parts as they do not have any in stock as its a new phone and their texas facility has diddly on hand)
Any suggestions are welcome as to fixing this predicament.

phil.W said:
did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery.
Click to expand...
Click to collapse
How did you wipe batterystats, from CWM? As the recoveries are new I suppose it's possible something went wrong if you did it that way, but it seems unlikely.
However, though probably not the root of your problem, there's no point in wiping batterystats.bin, as all that file holds in information on what processes have been using battery since your last unplugged your charger. This was one of those android myths (I used to do it too ) that was officially put to bed early in the year:
http://www.xda-developers.com/andro...g-battery-stats-does-not-improve-battery-life
In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Click to expand...
Click to collapse
I'm pretty sure I've seen others with this issue, have a search around the forums. Have you tried turning the phone from the bootloader screen, and leaving it plugged in to charge for a while?
Try this:
1. Boot into bootloader
2. Select Fastboot menu
3. Select "Power off" to shut down the phone
5. Plug in charger
Leave it for a while. From what I've read, the power LED may flash at first, but should settle after a few mins to a solid red. I'd leave it till it's green and fully charged then try again.
If that works, and you can get into recovery again, try restoring your backup of the stock ROM if you have one, to check the phone boots okay. (If you didn't take a backup first, you will next time. ) Otherwise try re-flashing the ROM, or if that fails you might have to re-flash stock recovery, re-lock your bootloader and then run the relevant RUU for your device to flash the stock firmware back. You'll have to unlock and root again in that case.
Good luck, hope it works for you!

[Q] htc one x bricked. not charging. not booting. only bootloader

usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed

http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!

kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...

FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up

hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)

Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA

Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.

Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/

Flashed Firmware S-ON

After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON. The device had never been Rooted or tampered with previously.
So now the phone does not boot at all. I've tried every button combination, but nothing seems to work. If I plug in the phone to charge the orange light flashes, endlessly. Even after I've left the device to charge for 6hours, the orange light still flashes.
When I plug in the phone to my PC, all I get it seems is this new device: QHSUSB_BULK, which shows with an exclamation mark next to it. I've read similar threads for different phones where they've unbricked devices while they were in this mode, is that even possible? I can hear Windows recognizing a device was plugged in, and if I press Power+VolumeUP, it will disconnect the phone and reconnect it, at least based on the sounds Windows is playing. The screen is Black at all times.
How badly have I bricked this device and is there any hope to revive it? Thanks to everyone who chimes in on this.

arrayy said:
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON.
Click to expand...
Click to collapse
Most likely it's a soft break. So you can fix it. First of all get yourself a working usb cable. Your's maybe broken.
Your phone's data partition had been encrypted. It never boots up completely without lux password. You could've format the data partition with a custom recovery such as TWRP. Instead you tried the reflash firmware but obviously it didn't finish and failed. All you need is reflash again but doing it correct way so it can finish. Your old data is gone atm. You will have factory reset phone at the end. Before giving you any instructions, you need to answer a few questions so anyone can help.
Have you ever updated your phone to marshmallow which is android 6? If no: You can recover it with voidzero's wonderful answer titled back to stock. Follow that exactly. If yes you can't flash old versions since they are using different bootloaders. Also you will have to reflash it manually. It's long and difficult for anyone who is new. If you don't know if it was updated. Just boot into bootloader then Fastboot mode, connect usb. Then use htc's Fastboot. Run htc_fastboot getvar all command. Paste output here.

Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader using the Power+VolumeUP keys, or any other combination.
Instead of flashing the RUU, or maybe turning to S-OFF(I still don't know if this would've made a difference), I flashed a firmware, one that matched my version. This is the exact filename: 0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed
I've renamed it to 0PKVIMG.zip and booted using the Power+VolumeUP keys. For whatever reason, everything went OK, no errors whatsoever. In the end it told me to press Power to reboot the phone. I've pressed Power and nothing happened since.
If anyone can help me figure this out, I'd be forever grateful.

arrayy said:
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader
Click to expand...
Click to collapse
That is a big problem. I assume you never tried to go S-OFF (which is dangereous). While phone was S-ON. You could always boot into bootloader. That's one of the purpose of staying S-ON.
Combination is Power + Volume down. But if your phone is up & somehow can not continue to boot. eg: stuck at reading system or kernel etc. You can do a hard reset which is pressing Volume up + volume down + power for at least 15 seconds. phone will shut down. then you can try bootlader combination. Make sure it's has power on with light at screen edges you must look at carefully. After trying this if you still can not see bootloader. That's a problem beyond my experiences, so I don't have any idea to fix it.
I have never tried the firmware you have used. Maybe that firmware is not usable, broken or even dangerous.
We need to confirm that here. if anyone else tried and brick their phone with that.

Razer phone stuck on boot screen after attempted root

I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.

Hi
to get to another mode you need to have the phone connected to a PC or Mac, so plug it into the usb and power off, once it is off hold volume down, this should make it go into download mode from there follow this link ( https://forum.xda-developers.com/razer-phone/help/razer-phone-os-t3772424 ) and you should get back to stock and you can retry to root from scratch or leave your phone as stock
Hope this helps

adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
If you got it to download mode but cannot communicate with the phone check your fastboot and drivers. You need Google USB drivers and the absolute latest fastboot. There are other posts here that can help you find the right stuff

adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.

incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me

tabletalker7 said:
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me
Click to expand...
Click to collapse
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/

incinandseril said:
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/
Click to expand...
Click to collapse
Hi follow the link from my comment above and give yours a try, don't think yours is toast just think it's in a boot loop cycle
My comment is second one down

incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
I´ve got this Screenproblem with the Oreo Update with sideload, it flash but then only this Screen, i found my mistake.
My solution was to do an critical unlock for Bootloader, than install 7.1 and than sideload 8.1 OTA, now it works very fine and much smother than before

[EDIT] After letting the battery run dry again last night, plugging my phone back into my laptop booted into download mode, again with the same display as below. Fastboot again recognised the device & after doing some searching, I'd seen another suggestion somewhere else I hadn't yet tried, which was forcing the phone to partition a (to be honest I couldn't even remember which partition I'd left it in from the attempted root)
The command is "fastboot set_active a && fastboot reboot"
I did this as soon as I was able to, rather than leaving it charging (this may be unrelated, but worth considering if you're still stuck)
after this, I got to the Razer logo screen lock (instead of the blank screen lock below), I was then able to follow Razer's instructions - which are linked in one of the comments on the link from the 2nd post here (hope that makes sense)
Now I'm happy to report everything is working, back to factory
I hope this can help someone else [EDIT]
I'm unfortunately in the same position, did you have any luck flashing back to factory?
I also tried following the guide from the 2nd link, these were the steps I took:
(I can confirm my bootloader is unlocked & critical also unlocked)
1. allowed battery to run dry
2. plugged into laptop whilst holding volume -
3. phone now in download mode with battery charge symbol on screen, I left it some time to charge but noticed it got stuck as per the screenshot (for approx. 6 hours)
4. device not recognised by adb, but recognised by fastboot
5. phone not accepting any fastboot commands, when attempting 'flash_all.bat' just hangs on the first line (flash partition:0 gpt_both0.bin), I have to close command line & reopen to try anything else, however whatever I try I get the same result, so basically the only responses I'm getting from fastboot are that it is aware of the device and confirms the bootloader incl. critical is unlocked
My next thought was the perhaps the phone attempted to boot once it reached the picture charge level and therefore locked in the same way it had initially on the razer logo. Should I attempt flashing the factory image immediately once the phone enters download mode, rather than allowing it to continue charging until it's flashed? Any ideas would be greatly appreciated!
Cheers

Been a while since anybody posted, I know... but did anyone who had this problem end up figuring it out? I am in the same situation and am freaking out a little bit, I JUST got this phone...

Just try this and should solve your problems
https://s3.amazonaws.com/cheryl-factory-images/cheryl-p-release-7083-user-full.zip

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.