Develop Bugs

HTC One X Dead after CM Update

Hey guys,
about 8 or 9 hours ago I updated to 20140209 Nightly via CM Updater.
Everything went fine, phone booted as usual. But then after some minutes of using the phone started lagging got warm around the camera and the screen froze.
After that I pressed and held the power button until the phone rebooted.
Then things went weird. The phone seemed to crash while booting about 3-4 times.
Some times while the CM Boot logo was there, sometimes when the HTC logo what there.
And then the screen went black, Battery LED went off and the phone seems dead.
I cant get it back on. ADB doesn't work. Holding Power Button doesn't work.
And every other button combination (like Power+Vol. Down for 2min) doesn't work.
The phone was plugged into the wall charger for about 7 hours now and still not a single reaction.
Not even the PC gets any connection so its not APX I think.
Is there any way to fix this ?

.K' said:
Hey guys,
about 8 or 9 hours ago I updated to 20140209 Nightly via CM Updater.
Everything went fine, phone booted as usual. But then after some minutes of using the phone started lagging got warm around the camera and the screen froze.
After that I pressed and held the power button until the phone rebooted.
Then things went weird. The phone seemed to crash while booting about 3-4 times.
Some times while the CM Boot logo was there, sometimes when the HTC logo what there.
And then the screen went black, Battery LED went off and the phone seems dead.
I cant get it back on. ADB doesn't work. Holding Power Button doesn't work.
And every other button combination (like Power+Vol. Down for 2min) doesn't work.
The phone was plugged into the wall charger for about 7 hours now and still not a single reaction.
Not even the PC gets any connection so its not APX I think.
Is there any way to fix this ?
Click to expand...
Click to collapse
Are you flash the boot.img from build 20140209 I thing there have kernel changes
Update compat-wireless from R5.SP6.01 to R5.SP7.01 this is kernel changes

Sounds more of a motherboard failure to me..

SlashSpeed said:
Sounds more of a motherboard failure to me..
Click to expand...
Click to collapse
Not even close to me..As Thant say's did you flash boot.img? And try another ROM..

.K' said:
Hey guys,
Is there any way to fix this ?
Click to expand...
Click to collapse
Connect the phone in charger and start in bootloader and try to go in recovery and charge the phone. After this flash the boot.img

Thant said:
Connect the phone in charger and start in bootloader and try to go in recovery and charge the phone. After this flash the boot.img
Click to expand...
Click to collapse
Seems like the phone is completely dead.
I don't think it's software related.
I cant even boot into bootloader or recovery.
The phone simply doesn't do anything. :/

.K' said:
Seems like the phone is completely dead.
I don't think it's software related.
I cant even boot into bootloader or recovery.
The phone simply doesn't do anything. :/
Click to expand...
Click to collapse
Try change the battery or try to find battery extendet pack to charge it from the back pin maybe the battery die just I think it is not the mainboard

Xiaomi Redmi 1S Boot Loop every 5 Seconds.

Hi All,
I have a Xiaomi Redmi 1S running on MIUI 9 7.9.7 China Beta and TWRP as recovery, it was working fine. Couple of days earlier I removed the battery and inserted again the phone suddenly restarted and keep boot looping every 6 seconds. The phone will power on without pressing the power button when the battery is inserted. I could enter into the recovery mode by pressing the the Volume Up button, but it's no use because it's boot looping. Did anyone face any similar issue? Could it be a hardware problem? Any help will be appreciated. Thank you.

Try this:
1. Remove the battery
2. Charge the phone
3. press power button to open system (if not try to boot to recovery using this method)
4. power off again
5. insert the battry
6. charge it
7. while charging turn on the phone

EmanzzKie said:
Try this:
1. Remove the battery
2. Charge the phone
3. press power button to open system (if not try to boot to recovery using this method)
4. power off again
5. insert the battry
6. charge it
7. while charging turn on the phone
Click to expand...
Click to collapse
Tried with removing battery and charging the phone, same result. Phone keep boot -looping. Can't access recovery. .

i have same problem with you. i have tried fastboot but still fail.

arkhaaji said:
i have same problem with you. i have tried fastboot but still fail.
Click to expand...
Click to collapse
Found a similar issue here https://android.stackexchange.com/questions/181908/xiaomi-redmi-1s-bootloop-on-inserting-battery.

Ajithkmr said:
Not sure why this is happening. I found a similar issue here https://android.stackexchange.com/questions/181908/xiaomi-redmi-1s-bootloop-on-inserting-battery.
Click to expand...
Click to collapse
Ok, not sure why this is happening. Found a solution here. http://en.miui.com/forum.php?mod=viewthread&tid=663881&page=1#pid13355815, gonna try that and will keep the thread updated.

Ajithkmr said:
Ok, not sure why this is happening. Found a solution here. http://en.miui.com/forum.php?mod=viewthread&tid=663881&page=1#pid13355815, gonna try that and will keep the thread updated.
Click to expand...
Click to collapse
I was gonna try this method, but now the phone works. NO idea what happened, I try to boot the phone to the fastboot but forgot to press the Volume down key and the phone booted. Initially I thought the power button is what causing the problems but after booting up, I tried several times restarting the phone and it works just fine. So unfortunately I can't reproduce the scenario which means I don't know what the problem is. If anyone facing similar issue, kindly check the Miui Forum link on my previous post which have a detailed guide. Thanks for checking out, have a nice day.

My redmi 7 is suddenly in a reboot loop. It cannot stop rebooting for an hour now and my power button also damaged please help me i have tons of work related data in there

Hi, I've successfully resuscitated my redmi 1W. The steps are the same except you have to select the redmi 1S rom from Xiaomi. LEt me know if you need help
The downside is that the phone now has a generic serial number. (If you know of now to reinsert the phone serial number, please let me know) So if you have apps that needs to detect the phone serial number, please do not follow these steps.
Redmi 1W recovery steps

Hard bricked? Bootloop can't get past bootloader unlocked warning

Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.

nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
Click to expand...
Click to collapse
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/

ZVNexus said:
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.

nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
Yeah might just have to wait until it dies.

nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
This has never failed!!! .. Unless its hardware
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
Turnoff.. hold the power button and both v+ and v-
For about 10secs.. hope it works for you

nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
Click to expand...
Click to collapse
Sorry for replying old post. I have been facing this critical scenario for last two days. The phone never turned off, always looped through unlock warning. No, button working. Can you please share , what about your findings at the end ??

erasing screen stuck?

i bought a 2 new phones( mi a2 lite global versions), with first there was no probles (boot up and all works) but second won't boot up on begin and i was think the battery was drained and plug him to charger for 1 hour (all the time led was only flashing, screen with battery doesn't appear) after that i try boot up but it wont, i try boot up recovery(with volume up and power) and nothing again when i press vloume down with power then i recive diffrent screen with coloured circle with sing "erasing" and the phone stuck on this screen for few hours and nothing looks he go finish this.
i first time get something like this and it's with new phone i didn't launch it eaven

Snopski said:
i bought a 2 new phones( mi a2 lite global versions), with first there was no probles (boot up and all works) but second won't boot up on begin and i was think the battery was drained and plug him to charger for 1 hour (all the time led was only flashing, screen with battery doesn't appear) after that i try boot up but it wont, i try boot up recovery(with volume up and power) and nothing again when i press vloume down with power then i recive diffrent screen with coloured circle with sing "erasing" and the phone stuck on this screen for few hours and nothing looks he go finish this.
i first time get something like this and it's with new phone i didn't launch it eaven
Click to expand...
Click to collapse
Try holding down the power button to restart the device, if it doesn't boot again, you may have a defected device, you can try returning it. Or if you are adventurous you can try flashing the stock rom by yourself but I'd suggest you to do the first. :good:

thanks, eany way ill make it with this https://forum.xda-developers.com/mi...ol-tool-one-driversunlocktwrpfactory-t3866191 ill try again and agian perssing volume down and power and i be able to enter fastboot then i unlock bootloader and erased data and phone after reset magicly booted up :laugh:

Question Pixel 6 Pro won't boot / Pixel Rom recovery

Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!

Hi,
If you cannot turn on your phone, it'll be difficult to help you. Pressing other 30 sec power button doesn't run ?
In parallel did you contact the Google pixel support ?
It's not to scare you, but I had the same issue on a old Samsung S8 and it was the motherboard 🫤
Hope it's not the case for you !!

Fadey_Fadington said:
Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!
Click to expand...
Click to collapse
So this is in fact just an undocumented Emergency Download Mode that Google Custom Exynos SoC has natively built into it in case of the rare event of a bad boot loader.
I’ve been doing an extreme amount of research lately about bootROM’s, how they communicate, the Driver rule support for interfacing with the phone while it’s Pixel ROM Recovery. The viewable name for the Exynos USB DownLoading mode.
Can I get you to dm me on Telegram? It might be helpful to have more people. I’ll be glad to help in getting this figured out. It could help a lot of other people who don’t have a Pixel 6 too

I have the same issue after trying to update to 1205. I see the Pixel ROM Recovery and a COM port.

If you cannot enter fastboot mode, no way to recover your phone.

Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.

redplayer5 said:
Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.
Click to expand...
Click to collapse
if u can boot into fastboot just flash the latest factory image from google

w_tapper said:
if u can boot into fastboot just flash the latest factory image from google
Click to expand...
Click to collapse
Can I do that even though my device is locked?
Is there a tutorial?

redplayer5 said:
Can I do that even though my device is locked?
Is there a tutorial?
Click to expand...
Click to collapse
nvm i dont think u can do it if bootloader is locked