Database Info

[Q] Stuck in boot loop, can't enter download mode

like title says, when I try to enter download mode it just goes black again like it's booting and nothing happens. I thought it might be a bad power button but when I went back to stock with Odin a few months ago it was working fine (power button problem but could still get to download).. so I think it might have been the rom (carbon 4.3)
I've been running Carbonrom 4.3 nightlies and they've been ok but then the power button problem started coming back up, and last night when I went back to stock again it was fine, the power button worked fine until I flashed a nightly I knew would work back from Sept. Now I can boot up the phone, the power button does NOT work, and when I try to reboot to recovery or download mode it just goes black and nothing happens like it's restarting. Taking the battery out and plugging to my PC does nothing, the red notification light comes on and then goes off.. Odin never sees it
Only thing I know to do now is let the batter drain all the way down and see what happens, but for now I can't even Odin back to stock. Any ideas at all?

little bit of an update: I was able to finally get into download mode by removing the plastic power button, booting normally and shutting it down completely, and then using the power-down-home combo.... after going back to stock via Odin, the power button works perfectly.. gonna reroot and try to update to 4.3 gradually

after 4 days of perfectly running Liquidsmooth rom 2.37 (4.3.1) the power button is acting up again so I removed the button completely again and just won't use it, seems to be working at the moment
if anyone knows a way to fix this besides taking it in for repair please post

[Q] Moto G won't turn on

Hey! I have a Moto G LTE and about six hours ago I returned to stock after trying out some CM ROMs, everything was fine, I was in 4.4.4 with no issues and after updating all the apps that required it I had an update to Lollipop. I clicked the download button and after it finished downloading the phone restarted and started to update the system. After it was done the screen turned black and the phone just turned off. And that was it.
I literally have tried everything I saw in the net, I left it charging for about two hours, but it didn't solve anything, I pressed the Power + Volume Down button for 30 seconds, the Power button itself from 30 seconds to 5 minutes, yet nothing happens.
When I connect it to a PC Windows plays the sound when a device is connected, but it does not show the phone and doesn't seem to turn it on or anything.
Is there any way of solving this? I don't know what else to try, if at least I could get into the fastboot menu I will install a ROM, but I cannot.
Thanks in advance.

@Zox09 - How did you return to Stock? Did you use a firmware image? If so, provide the exact title.

lost101 said:
@Zox09 - How did you return to Stock? Did you use a firmware image? If so, provide the exact title.
Click to expand...
Click to collapse
I used Android 4.4.4 (Retail Europe) KXB21.14-L1.56-1 CID7 taken from this thread:
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
It's the one I've always used and gave me no problems.

Zox09 said:
I used Android 4.4.4 (Retail Europe) KXB21.14-L1.56-1 CID7 taken from this thread:
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
It's the one I've always used and gave me no problems.
Click to expand...
Click to collapse
Try the following again.
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.

lost101 said:
Try the following again.
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
Click to expand...
Click to collapse
Thanks, I've already tried both of them a couple of hours ago and still nothing.
Someone in the Motorola Forum has said that I probably have bricked the device because of downgroading to 4.4.4 and then updating again. I didn't know this was possible since I have made this a couple of times with ROMs.
Is there anything else I can try?

Zox09 said:
Thanks, I've already tried both of them a couple of hours ago and still nothing.
Someone in the Motorola Forum has said that I probably have bricked the device because of downgroading to 4.4.4 and then updating again. I didn't know this was possible since I have made this a couple of times with ROMs.
Is there anything else I can try?
Click to expand...
Click to collapse
The reference to hard-bricking due to doing a downgrade does not apply in your case. It would only apply if you upgraded to Lollipop, and then flashed the KitKat firmware. Even then, the hard-brick is due to a specific order of events: downgrading from 5.0.2 to 4.4.2 and OTA Update to 4.4.4.
It can be tricky following those steps sometimes. Are you sure the power cable is working? plugged into a wall socket?
If that method still fails to work, you have a hard-brick and need to wait with others for a Lollipop solution in this thead: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

lost101 said:
The reference to hard-bricking due to doing a downgrade does not apply in your case. It would only apply if you upgraded to Lollipop, and then flashed the KitKat firmware. Even then, the hard-brick is due to a specific order of events: downgrading from 5.0.2 to 4.4.2 and OTA Update to 4.4.4.
It can be tricky following those steps sometimes. Are you sure the power cable is working? plugged into a wall socket?
If that method still fails to work, you have a hard-brick and need to wait with others for a Lollipop solution in this thead: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
I have tried with two different cables and two wall sockets, the USBs are one the original of the Moto G and the other from a LG tablet I have, and the sockets one from a Samsung mobile and the other from the tablet (the Moto G came with no wall socket), and in neither of them are working.
I think I'll have to wait for a solution :crying:
Thanks for your help anyway!

@lost101, I don't know how, but the LED just started working and it was on for a couple of minutes. I tried to turn on the device but it didn't work and the LED turned off a few seconds later. Does this actually mean something?

Zox09 said:
@lost101, I don't know how, but the LED just started working and it was on for a couple of minutes. I tried to turn on the device but it didn't work and the LED turned off a few seconds later. Does this actually mean something?
Click to expand...
Click to collapse
I've had a few occasions when I thought my Moto G was dead. Keep trying to charge it and follow the steps for another 24 hrs. That being said, I believe hard-bricked devices sometimes also only show some LED activity. You are best asking in the thread I mentioned above.

lost101 said:
I've had a few occasions when I thought my Moto G was dead. Keep trying to charge it and follow the steps for another 24 hrs. That being said, I believe hard-bricked devices sometimes also only show some LED activity. You are best asking in the thread I mentioned above.
Click to expand...
Click to collapse
Alright, thanks a lot for your help!

Bricked My Phone - Please Help!

I wanted to make a clean start on my phone after flashing way too many ROM's, so I RUU'd via HBOOT using a .zip on my Ext SD card. I used Dottat's 5.0.1 file. Everything seemed to work fine. Once I got up and running and rebooted, I went back into my bootloader (vol - + power) and did a factory reset. Everything worked smoothly and I got through first boot to the setup screen. At this point I wanted to install enewman's 5.1.1 GPE ROm then upgrade to the 6.0 Marshmallow build I had just been running. I powered down the phone and went back into bootloader. I selected Recovery and pressed power button to select. Phone turned off and never rebooted. And now I can't get it to turn on at all. I've tried holding power button for a long time, power + vol up, power + vol down. I get no bump, no lights, no nothing. When I plug it in to a charger I get no charging symbol.
Is it possible that when I RUU'd I removed my TWRP recovery, then when I tried to boot into recovery it got lost? A few things that might help - I am S-OFF, and I did notice right before I tried to reboot that the phone did say it was still unlocked.
Can anybody please suggest a fix? Or do I have a fancy paperweight to gift someone with this holiday season?
Thanks in advance for your help.

bdyer said:
I wanted to make a clean start on my phone after flashing way too many ROM's, so I RUU'd via HBOOT using a .zip on my Ext SD card. I used Dottat's 5.0.1 file. Everything seemed to work fine. Once I got up and running and rebooted, I went back into my bootloader (vol - + power) and did a factory reset. Everything worked smoothly and I got through first boot to the setup screen. At this point I wanted to install enewman's 5.1.1 GPE ROm then upgrade to the 6.0 Marshmallow build I had just been running. I powered down the phone and went back into bootloader. I selected Recovery and pressed power button to select. Phone turned off and never rebooted. And now I can't get it to turn on at all. I've tried holding power button for a long time, power + vol up, power + vol down. I get no bump, no lights, no nothing. When I plug it in to a charger I get no charging symbol.
Is it possible that when I RUU'd I removed my TWRP recovery, then when I tried to boot into recovery it got lost? A few things that might help - I am S-OFF, and I did notice right before I tried to reboot that the phone did say it was still unlocked.
Can anybody please suggest a fix? Or do I have a fancy paperweight to gift someone with this holiday season?
Thanks in advance for your help.
Click to expand...
Click to collapse
An RUU unless edited will have stock recovery in it..
As to why it won't turn on - what was the battery at, could it have died? Their are some sites online to try and get your battery to charge if it dies. Try plugging into USB computer for 24h with phone off was one I read at some point. Best of luck.

andybones said:
An RUU unless edited will have stock recovery in it..
As to why it won't turn on - what was the battery at, could it have died? Their are some sites online to try and get your battery to charge if it dies. Try plugging into USB computer for 24h with phone off was one I read at some point. Best of luck.
Click to expand...
Click to collapse
Thanks @andybones, I was hoping someone like you would reply (I've been following your work since running BoneStock on my SIII - we have similar taste in stripped down OS's). There should have been plenty of juice on it, I think I was in the 60% range last time I booted. In fact, the phone was plugged into the charger when it died. Yeah, really concerning that I get nothing at all...
Anyone else have any suggestions? Thanks in advance...

bdyer said:
Thanks @andybones, I was hoping someone like you would reply (I've been following your work since running BoneStock on my SIII - we have similar taste in stripped down OS's). There should have been plenty of juice on it, I think I was in the 60% range last time I booted. In fact, the phone was plugged into the charger when it died. Yeah, really concerning that I get nothing at all...
Anyone else have any suggestions? Thanks in advance...
Click to expand...
Click to collapse
What steps have you taken thus far as to rule them out?
first check out this link and try this
also check out this link about fixing the charging logic
https://www.ifixit.com/Answers/View/219029/Device+will+not+power+on+after+battery+ran+dry
Also could call HTC, they may send you a new device, which sucks but better than nothing.

andybones said:
What steps have you taken thus far as to rule them out?
first check out this link and try this
also check out this link about fixing the charging logic
https://www.ifixit.com/Answers/View/219029/Device+will+not+power+on+after+battery+ran+dry
Also could call HTC, they may send you a new device, which sucks but better than nothing.
Click to expand...
Click to collapse
Thanks for the suggestions. I held pow and vol+ for 10 seconds, pow and vol - for ten seconds.. I held pow and vol + and vol - for two minutes. No joy. I called HTC, they were super nice and very helpful, but unfortunately none of their suggestions helped. They had me plug it into my pc to see if it registered, had me do the pow and vol +/- for two minutes. After that, they recommended I send it in for repair. Unfortunately, since my phone is out of warranty, they said I would need to pay for repair.
I filed an insurance claim, got a new one coming Friday. Gotta refresh myself on getting s-off... Thanks again for your help. If anyone else has any suggestions (or questions), wouldn't be a bad thing to repair the phone and have a spare waiting in the wings... Is there a way to change the IMEI in case I can repair the old one? :silly:
Happy Thanksgiving, all!

phone not booting, charging, doing anything

So I had a rooted samsung galaxy s8+ with magisk on android noughat and I wanted to update it to oreo, so I updated it using Samsung Switch, but then my apps started to crash a lot and it seemed like it wasnt rooted anymore (all my root apps were not working and event magisk was saying that it was not rooted). So I made a factory reset, run TWRP and tried to run the magisk root again, but then i got a bootloop. After that i tried to run firmware which i found on pangu.in in odin (I basically just followed this video "How to Fix Boot Loop || Stuck on Samsung logo S8 plus Samsung Galaxy S8 Plus review" on YT) and than it frosed in samsung loading screen for about 15min and after that i hard reseted it and since than the phone is completly not doing anything. Is there any solution to this, or i just completly destroyed my phone? I tryied every possible key combinations, but neither of them is doing anything.

Have you tried holding Power + Volume Down for 10-15 (maybe more) seconds? simulates a battery removal. Worked for me when phone seemed unresponsive.

JeffDC said:
Have you tried holding Power + Volume Down for 10-15 (maybe more) seconds? simulates a battery removal. Worked for me when phone seemed unresponsive.
Click to expand...
Click to collapse
Yes. I tried every combination I know.
power + vol down
power + vol down + bixby
power + vol up + bixby
If there is any other combiantion that could work, i would be really thankful for it.

negjo said:
Yes. I tried every combination I know.
power + vol down
power + vol down + bixby
power + vol up + bixby
If there is any other combiantion that could work, i would be really thankful for it.
Click to expand...
Click to collapse
Have you a SD card installed you could put new firmware on and boot from there.

deakodude said:
Have you a SD card installed you could put new firmware on and boot from there.
Click to expand...
Click to collapse
Yes I have, how can that be done?
Btw. I realy dont know how, but few minutes ago I just randomly tried to turn it on and I managed to get into download mode (after about 1000 tries). Unfortunatelly the phone turned off again before I managed to ge to the computer and run Odin. But I might keep trying to boot it into download mode and this time be prepared to put a new firmware into it.

negjo said:
Yes I have, how can that be done?
Btw. I realy dont know how, but few minutes ago I just randomly tried to turn it on and I managed to get into download mode (after about 1000 tries). Unfortunatelly the phone turned off again before I managed to ge to the computer and run Odin. But I might keep trying to boot it into download mode and this time be prepared to put a new firmware into it.
Click to expand...
Click to collapse
Put Sd card in adapter if you have one in laptop install firmware to card, boot firmware from card.
Sent from my SM-G965F using Tapatalk

deakodude said:
Put Sd card in adapter if you have one in laptop install firmware to card, boot firmware from card.
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
But you need to get into recovery mode to do that, dont you ?

negjo said:
But you need to get into recovery mode to do that, dont you ?
Click to expand...
Click to collapse
Sorry missed you can't get into recovery.

So I somehow managed to get into download mode and i wanted to flash new firmware, but it got stuck on sboot.bin.lz4 (apparently it was bcs of outdated odin), so i restarted it and since than everytime I try to charge it, it shows loading screen and I still cant do anything (go to recovery mode or download mode). When I unplug the charger it again turns off and I still cant do anything. This is really weird.

It would seem like your phone needs charging, low charge would seem consistent with it switching off when charger not connected.
Suggest leaving on charge for 60 to 90 minutes then try previously given advice.
Get latest Odin from XDA and official software from Sammobile

Honor View 10 Bricked (in a bootloop) after Official update.

Hi,
I recently tried to install the most recent update (the update was for EMUI 9 I think) on my V10 and it is now stuck in a bootloop. I cannot access recovery mode, when I enter fastboot mode, it says my FRP is locked and my PHONE is locked. I can't flash anything because my bootloader is locked. I have no idea what to do, any help is appreciated although I would rather the solution be free (ie not DC Unlocker or funky Huawei).
I had this once before and I solved it by getting into recovery mode, however, I don't know how I got into recovery mode last time it just happened randomly. I tried Vol up + power button, it does nothing just reboots my phone. I have tried vol up + vol down + power button, the same result.
I don't know what to do anymore.
Thanks in advance.
EDIT:
so I solved my problem, I let the battery die overnight and in the morning I tried plugging it in and booting into recovery mode (vol up + power button) and after trying several times (and unplugging my phone so it would die then plugging it back in to try again) I finally got it into recovery mode. From there I pressed download and recover and I got my phone back. The only problem now is that I can't update my phone through the official process as it just puts my phone back into the bricked state. Hope this helps anyone else who was in this situation.

Since the problem is caused by an official OTA, I recommend to send it to the service center

PalakMi said:
Since the problem is caused by an official OTA, I recommend to send it to the service center
Click to expand...
Click to collapse
Yeah, I resorted to this last night and called them up for repairs. They were going to take it in but I now fixed my phone (look at my edit in the original post for info).
Thanks for your help though.

I'm glad that you've found a solution

Same issue but no luck for me.
No repair center because my bootloader is unlocked.
My issue :
https://forum.xda-developers.com/honor-view-10/help/9-0-0-official-pie-update-failed-boot-t3889378

Try edl flash