Develop Bugs

One X Won't Turn On

Hey guys, I was flashing a rom on my One x but for some reason it got stuck in a bootloop. After that, I tried restoring to my earlier rom using CWM but I forgot to flash the boot.img from cmd first so it didn't work. After that I tried restarting my phone but it wouldn't turn on after turning off. When I plug in my charger the red light comes up but I can't turn it on. I left it to charge for a few hours but it still won't turn on, the only sign of it working is that it vibrates when I attempt to turn it on. I also tried connecting it to my pc and it senses it but I get no results when I type adb devices in cmd. Can someone please help me with this issue? Thanks!

What can you see in windows device management? Does
Code:
fastboot devices
give you any info?

No, nothing, but when I connect to pc it says installing device software

Oh yeah, I also forgot to mention that it did turn on before and I got into the bootloader but then it turned off again

I mean the device management in the control panel. It should be there if it says something about drivers.

It says MTP USB Device

What ROM are you on?

I was attempting to flash Blade rom when it got stuck in bootloop

MTP should be only available when the phone is booted. I really don't know what is the problem here, sorry.

Ok, Thanks anyway

I just restarted my pc and after running cmd and entering adb devices I get: SH24KW107359 recovery. But the phone is still off. Any ideas?

If the phone vibrates and your computer sees it like MTP that it might be a hardware failure. Contact HTC for further assistance, or try search the forum. I am sure many faced the same problem, and some got it working finally.

I'm no longer getting MTP, it now says E:\

Wait, were you on android 4.0.4 just before you tried flashing Blade?

BlueSingA said:
Wait, were you on android 4.0.4 just before you tried flashing Blade?
Click to expand...
Click to collapse
No, I was not. At least I don't think so. It's my sisters phone so I'm not sure. Why?

I believe that the phone is switched on, but the screen remains off. Try this:
Code:
fastboot getvar all

I tried turning it on and it turns on then it shows the HTC logo, then when I try to get into CMW it shows a dark screen but u can tell its on.

Ok, if your in cwm, from a cmd prompt run:
adb reboot bootloader
That should put you in the bootloader.
From there use fastboot to flash the kernel to boot as you should have done earlier.
When your done just:
fastboot reboot
-SLS-

When I type fastboot devices in cmd i get: SH24KW107359 fastboot. Can I flash a boot.img by using fastboot flash boot boot.img?

Yes, and also reflash cwm. Dl from clockworkmod site and flash using:
fastboot flash recovery nameofthefile.zip
Sent from my HTC One X using xda app-developers app

[Q]GSM GNex soft bricked, doesn't connect to PC

I have a soft bricked GNex that goes into a bootloop of the "Google" splash logo. I can volume up + down + power and get it into the screen that gives options for recovery mode. However, when I click recovery mode, it takes me to a screen with a dead android with the red triangle sign on it. When I connect the phone to my PC, it is not even registering that a device was plugged in.
Are there any other methods or options I have to attempt to get the phone up and running?

1) thats stock recovery
2) if you want your pc to recognize it, just boot into fastboot and install the universal naked drivers.

Zepius said:
1) thats stock recovery
2) if you want your pc to recognize it, just boot into fastboot and install the universal naked drivers.
Click to expand...
Click to collapse
It's not that my PC doesn't recognize it because I don't have the drivers, I have another GNex and it plugs in just fine. My PC acts as if there was no device plugged in, there is no notification, no unknown device detected, nada. The owner claims there was water damage to the phone so maybe it's hardware bricked?

update: tried a different USB cable and got my PC to recognize the device. Using the toolkit to try and flash stock rom on there. Will keep updated if all goes well

toolkit goes through the whole stock rom flash process but phone is still doing bootloops. any other ideas?

Do it the right way. Follow the sticky on setting up adb and fast boot and put some hair on tour chest. Toolkits are terrible.

063_XOBX said:
Do it the right way. Follow the sticky on setting up adb and fast boot and put some hair on tour chest. Toolkits are terrible.
Click to expand...
Click to collapse
Ok, been following the instructions via this topic: http://forum.xda-developers.com/showthread.php?t=1529058
Have gotten all the way to the part where it's telling me to restart in recovery mode and that's when the dead android with the red warning triangle shows up. I also want to make note that I received the phone in this condition so I'm pretty sure the USB debugging mode has not been enabled.

[Q] Bricked Kindle Fire HD - is it hopeless?

In November (just about one week after the warranty was up) the $300++ Kindle Fire HD we bought just stopped working. Amazon basically said sorry, your warranty is up - wanna buy another? (no thanks)
When it's turned on, the Kindle Fire logo appears, then the screen goes black. Nothing else.
We've tried the usual tricks. I bought a fastboot cable and tried the KFHD System.img Recovery Tool and all I get is "device not found." My computer doesn't seem to recognize the device at all.
Is there anything else I can try.... or is it just a lost cause??

Peppsico said:
In November (just about one week after the warranty was up) the $300++ Kindle Fire HD we bought just stopped working. Amazon basically said sorry, your warranty is up - wanna buy another? (no thanks)
When it's turned on, the Kindle Fire logo appears, then the screen goes black. Nothing else.
We've tried the usual tricks. I bought a fastboot cable and tried the KFHD System.img Recovery Tool and all I get is "device not found." My computer doesn't seem to recognize the device at all.
Is there anything else I can try.... or is it just a lost cause??
Click to expand...
Click to collapse
first of all, is it a 8.9 inch? if so DO NOT use fastboot cable, it can actually CAUSE damage to 8.9 incher. you just need the regular microUSB that came with your kindle. "special" fastboot cables are only required for the 7 incher... if you have the 8.9 inch "jem" i can try to point you to a few threads that may help unbrick it.
Mike

Thanks... Yes it is 8.9! I'd greatly appreciate any help!!

Anybody?
If I could get a computer to recognize the Kindle, I'm sure I could apply some of the fixes and find something to get it going again. It doesn't show up in device manager and makes an 'error' sound.

You can recover from this but first i will need to know how you bricked it, which operating system do you have, and do you have a sdk installed.
A few moths ago i ran into the same problem but now my kindle is working just fine.
DO NOT USE THE FASTBOOT CABLE TO DO ANYTHING IT CAN DAMAGE YOUR KINDLE

skullarc said:
You can recover from this but first i will need to know how you bricked it, which operating system do you have, and do you have a sdk installed.
A few moths ago i ran into the same problem but now my kindle is working just fine.
DO NOT USE THE FASTBOOT CABLE TO DO ANYTHING IT CAN DAMAGE YOUR KINDLE
Click to expand...
Click to collapse
In an attempt to not start new threads where they aren't needed. I'm in a very similar boat, so here are the answers to your questions:
I was attempting to flash CM11 to my 8.9 Kindle. I was following the following instructions:
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Parts 1-6 of Step 1 completed successfully, and somewhere between Step 1 and 3 the screen turned off. I have not yet been able to get the screen to turn on again or the device to light up when charging or anything.
Thoughts?

clemsongt said:
In an attempt to not start new threads where they aren't needed. I'm in a very similar boat, so here are the answers to your questions:
I was attempting to flash CM11 to my 8.9 Kindle. I was following the following instructions:
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Parts 1-6 of Step 1 completed successfully, and somewhere between Step 1 and 3 the screen turned off. I have not yet been able to get the screen to turn on again or the device to light up when charging or anything.
Thoughts?
Click to expand...
Click to collapse
Can you get into fastboot? I was able to recover mine by restoring my backup and then starting over with pushing stack and all that stuff. So getinto adb wtih the getvar, then just plug a normal cable into the kindle, and see if your PC recognizes it, and it drops into fastboot.

turn off your device and then connect your normal cable then type
fastboot -i 0x1949 getvar product
in your cmd or shell (if you are using linux or unix based operating system)
it should show
< waiting for device >
then turn on your device
it should go into fastboot then download the neccery files follow step 5 form the link
forum.xda-developers.com/showthread.php?t=2128175
and
follow the installation for cyanogenmod from
forum.xda-developers.com/showthread.php?t=2543481

skullarc said:
turn off your device and then connect your normal cable then type
fastboot -i 0x1949 getvar product
in your cmd or shell (if you are using linux or unix based operating system)
it should show
< waiting for device >
then turn on your device
it should go into fastboot then download the neccery files follow step 5 form the link
forum.xda-developers.com/showthread.php?t=2128175
and
follow the installation for cyanogenmod from
forum.xda-developers.com/showthread.php?t=2543481
Click to expand...
Click to collapse
I'm on Windows with minimal adb and fastboot. I get the < waiting for device > but when I plug in in my tablet nothing happens on either end. It doesn't matter if I have the device plugged in before or after running the command.
mrcpu said:
Can you get into fastboot? I was able to recover mine by restoring my backup and then starting over with pushing stack and all that stuff. So getinto adb wtih the getvar, then just plug a normal cable into the kindle, and see if your PC recognizes it, and it drops into fastboot.
Click to expand...
Click to collapse
By get into fastboot, I assume you mean with the command skullarc referenced since there is no button combination one can use to get into fastboot? Then your answer is shown above. The device has been completely unresponsive to anything I throw its way so far.

when you turn on your kindle what does it show?
If it does not even turn on then press the power button continuously for 20-30 seconds. Then press the power button again

skullarc said:
when you turn on your kindle what does it show?
If it does not even turn on then press the power button continuously for 20-30 seconds. Then press the power button again
Click to expand...
Click to collapse
It does not respond to anything I throw at it. If you mean to press and hold the power button for 30 seconds, let go, then press and release, that also gets no response.

clemsongt said:
It does not respond to anything I throw at it. If you mean to press and hold the power button for 30 seconds, let go, then press and release, that also gets no response.
Click to expand...
Click to collapse
Could it be that your charger is not working and doesn't device even blink when you press the power button

skullarc said:
Could it be that your charger is not working and doesn't device even blink when you press the power button
Click to expand...
Click to collapse
Not a charger issue, as I have used a known good one overnight with no difference.

clemsongt said:
Not a charger issue, as I have used a known good one overnight with no difference.
Click to expand...
Click to collapse
were you able to perform the third step ?

skullarc said:
were you able to perform the third step ?
Click to expand...
Click to collapse
What's the third step?

clemsongt said:
What's the third step?
Click to expand...
Click to collapse
Third step in installing CM11 and did you use fastboot cable ?

skullarc said:
Third step in installing CM11 and did you use fastboot cable ?
Click to expand...
Click to collapse
The third step found here?
http://forum.xda-developers.com/showthread.php?t=2128175
hashcode said:
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS -- May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to permissions changes
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/s
Click to expand...
Click to collapse
If so, I got the response "device not found" when attempting to push to sd card.
I tried with and without fastboot cable (have not verified functionality of fastboot cable as it was bought after bricking my device(.

clemsongt said:
The third step found here?
http://forum.xda-developers.com/showthread.php?t=2128175
If so, I got the response "device not found" when attempting to push to sd card.
I tried with and without fastboot cable (have not verified functionality of fastboot cable as it was bought after bricking my device(.
Click to expand...
Click to collapse
I was trying to ask at what step did your kindle turn off when you were trying to install cm11 and was bricked in this were you able to start the 3rd step

skullarc said:
I was trying to ask at what step did your kindle turn off when you were trying to install cm11 and was bricked in this were you able to start the 3rd step
Click to expand...
Click to collapse
Ohhhh...Sorry for being confused.
following these steps, I was able to successfully complete all of step 1, step 2, and step 3. it was in recovery while I was reading up on the "Installing CyanogenMod from recovery" section and when I looked back at the device, the screen had gone black. Since then I have not gotten it to do anything.
wiki.cyanogenmod.org/w/Install_CM_for_otter2

clemsongt said:
Ohhhh...Sorry for being confused.
following these steps, I was able to successfully complete all of step 1, step 2, and step 3. it was in recovery while I was reading up on the "Installing CyanogenMod from recovery" section and when I looked back at the device, the screen had gone black. Since then I have not gotten it to do anything.
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Click to expand...
Click to collapse
Did you check the md5sum for the files that you flashed in step 3 and downloaded in step 2
it will tell you if they are corrupt

Amazon fire phone stuck at boot logo and cant access to recovery mode.

I was recently planning to install Miui 7 on my Fire Phone. So, i installed safestrap 4.01.
1. I opened safestrap recovery mode
2. I wiped (First screen of Safestrap recovery mode)
3. I installed Cleansystempartition.zip
and then i don't know why, but i lost my mind and decided not to install Miui 7 and i went back and clicked on reboot.
So, now my Amazon Fire phone is stuck at boot logo and i can't even enter recovery mode.
It doesn't respond when connected to PC. It is charging and again when i boot again get stuck on boot logo.
Please reply ASAP.

Erictic67108 said:
I was recently planning to install Miui 7 on my Fire Phone. So, i installed safestrap 4.01.
1. I opened safestrap recovery mode
2. I wiped (First screen of Safestrap recovery mode)
3. I installed Cleansystempartition.zip
and then i don't know why, but i lost my mind and decided not to install Miui 7 and i went back and clicked on reboot.
So, now my Amazon Fire phone is stuck at boot logo and i can't even enter recovery mode.
It doesn't respond when connected to PC. It is charging and again when i boot again get stuck on boot logo.
Please reply ASAP.
Click to expand...
Click to collapse
What you need:
1 x USB Cable, 1 x PC, 1 x Fire Phone update bin, adb and correctly installed drivers. GOOGLE
How too:
1. Ensure phone is turned OFF
2. Plug the USB cable into your phone.
3. Press and keep held the Volume UP (+) button only
4. Now plug the other end of the USB cable into the PC. (keeping the Volume UP held)
5. The phone will now boot into recovery and you can let go of the volume button.
6. Select "apply update from ADB"
7. type
Code:
adb sideload your-firmware-version.bin
Use google or search the Fire Phone threads on how to install adb and drivers etc etc.

bigrammy said:
What you need:
1 x USB Cable, 1 x PC, 1 x Fire Phone update bin, adb and correctly installed drivers. GOOGLE
How too:
1. Ensure phone is turned OFF
2. Plug the USB cable into your phone.
3. Press and keep held the Volume UP (+) button only
4. Now plug the other end of the USB cable into the PC. (keeping the Volume UP held)
5. The phone will now boot into recovery and you can let go of the volume button.
6. Select "apply update from ADB"
7. type
Code:
adb sideload your-firmware-version.bin
Use google or search the Fire Phone threads on how to install adb and drivers etc etc.
Click to expand...
Click to collapse
Thanks for your time, but i couldn't understand how ADB is used. I installed adb drivers (tried bunch of times) but can't figure out how to do steps you suggested.
Could you please elaborate in detailed step-by-step, or provide me some revalent link so that I (noob) could understand easily. Once again thanks for help !
Code:
Is there any way i can ensure that proper drivers are installed for my Fire Phone?

Since i understood how adb is used, I categorized further remaining problem into two type:-
1. If I hadn't installed right drivers...
I tried installing driver from different source but i failed (i guess).
So anyone can provide me link for Drivers for Fire Phone?
2. If i have installed right drivers then :
I tried steps as you suggested but my phone won't boot into recovery mode. When i connect Phone to my pc holding volume + , It shows charging symbol as usual.
If i am doing the process in wrong way, please correct me. I will be waiting for helps...:crying:

@Erictic67108
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62768812
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62844581
Firmware for sideload you can download from Amazon. Your need last version.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550

Kramar111 said:
@Erictic67108
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62768812
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62844581
Firmware for sideload you can download from Amazon. Your need last version.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.

Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
If Fire Phone detected in Windows Device Manager with PID 9008 you can't do anything (as i know). PID 9006 give you a little chance.

Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
Talk with amazon for warranty, if you are from europe, talk with amazon.de, you will get a new one, but u must return to amazon germany the bricked fire phone.

Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
Your only hope to revive this phone is to get into the stock recovery.
If you wiped the stock recovery or messed with it then your screwed as there is no PC flashtool like odin, spflashtool, etc etc that works on the fire phone that I am aware of so you need the stock recovery to be functional.
To get into recovery re-read post #2 HERE very carefully on how to do it. :fingers-crossed:
There is no need to PM me just simply quote me in this thread and I will then get notified.
You also need to provide as much info as possible things such as screenshots, photo's, Videos, logs etc etc as these will help when people try to assist you.
Once you are in stock recovery we can move on.

I quit guys. I just can't get that thing on recovery mode. I tried several times, tried other ways but nope. My phone is not giving a damn ****. Its just gets stuck on boot screen logo. That's all. I guess, i won't get my phone returned/exchanged since had i rooted it which violates its warranty.

Am having thee same issue
Erictic67108 said:
I quit guys. I just can't get that thing on recovery mode. I tried several times, tried other ways but nope. My phone is not giving a damn ****. Its just gets stuck on boot screen logo. That's all. I guess, i won't get my phone returned/exchanged since had i rooted it which violates its warranty.
Click to expand...
Click to collapse
i also quit gyz i tried almost every thing but its stuck on amazon logo

Weirdly enough -my gfs fire phone started exhibiting the same exact issue just yesterday(amazon logo blinks on start up and doesnt go any further no matter how long you wait) and this is the first link google gave on the problem. Did anyone find a resolution to this? She loves this phone and I already replaced battery once few months ago.

[HELP] Bricked Begonia [SOLVED]

My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP

crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing

beachfl said:
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing
Click to expand...
Click to collapse
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU

crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
So Sad, was stuck in the same situation tried 100 of methods but all in vain, in the end had to send my device to customer care center & received after 15 days without charges

I use to flash rom`s when i was younger phones and tablets and never had a brick, I am glad it`s out of my system, Anyway the 8pro works fine for me as a non-gamer as it seem to be very risky to flash.
Good luck getting your problem solved.

crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
crazyfox21 said:
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU
Click to expand...
Click to collapse
Greetings,
First thing I would do is grab the latest version of ADB/Fastboot, uninstall previous version and reinstall it on your Laptop as Admin, turn off your Anti-virus anti-spyware, optimization program or whatever app you may have running on your Laptop and which could prevent system modification, then run it as Admin. If during installation you are poped with installing more things like MS or google's libraries and such, install them.
You may also try to reboot your phone to fastboot while already being connected to computer which may prevent it to boot to the charging page.
If you manage to get fastboot stable enough when connected and if you have no done already, you may want to proceed with reading the [GUIDE][INFO][PSA] Redmi Note 8 Pro - Megathread + CFW and applying the anti-brick solution before flashing anything else like a recovery again.
Assuming you have not damaged anything else, to recovery from a Magisk installation failure you may only need to flash the boot.img from your exact same Stock image you were on.
If that does not suffice, flashing additionally system and userdata (all data will be lost) should fix it.
Hope this helps,
Good Luck!
PS: I am assuming your bootloader is unlocked right?

[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ??
Edit : my false because i'm forget to close AVB before flashing Magisk

crazyfox21 said:
[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ?
Edit : my false because i'm forget to close AVB before flashing Magisk
Click to expand...
Click to collapse
So glad you could fix it and make it work in the end! That's all what matters!
You can now mark your thread as "[SOLVED]" by editing original message tittle
Cheers!