Database Users

[Q] Rooted phone doesn't boot

- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?

mufc786 said:
- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?
Click to expand...
Click to collapse
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...

abaaaabbbb63 said:
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...
Click to expand...
Click to collapse
I bought it 2nd hand from Cex (second hand retailer in UK). Luckily I still had 2 months of warranty left so they've taken it in for repairs. I don't know if they'll find out it's hard bricked (if it is), or not.

Unfortunately happened to me, too, yesterday, while rebooted my Nexus 4. It doesn't boot. The LED blink once, red, and nothing. The worst thing is it's the Service page from LG Romania website "is not available". Now I'm digging the web to find a solution

okay guys screw CeX (second hand UK retailer with 1 year warranty on ALL electronics). I took my supposed dead nexus 4 to them and the guy took it in for repairs (I'm 2 months from the end of my warranty). So they take it in and I go in 2 weeks later as they haven't updated me on the progress.
Get into the store and the guy pulls my phone out. He says because it has a crack on the back they can't book it in for repairs. I ask him why did they take it in if it wasn't going to be booked in, his reply, well its obvious no one would fix a phone with a crack in it! This guy was the goddamn manager.
So since about 2/3 weeks my phone's been dead I haven't touched it. I'll try again tomorrow but hopefully it will start working. Wish me luck.
And is it possible to hardbrick a phone because its battery dies out AND the ROM/Bootloader can't allow the device to charge?

my yotaphone is dead

it was working and suddenly it just died ive tried charging it and ive tried pressing power and power + volumen up and down and nothing seems to work. Any thoughts, ideas? the back cover is stuck in a notification it doesnt work also it seems to charge on the Wireless charger

luisumf said:
it was working and suddenly it just died ive tried charging it and ive tried pressing power and power + volumen up and down and nothing seems to work. Any thoughts, ideas? the back cover is stuck in a notification it doesnt work also it seems to charge on the Wireless charger
Click to expand...
Click to collapse
Try to get into download mode. Or wait a while
Sent from my YD201 using Tapatalk

luisumf said:
it was working and suddenly it just died ive tried charging it and ive tried pressing power and power + volumen up and down and nothing seems to work. Any thoughts, ideas? the back cover is stuck in a notification it doesnt work also it seems to charge on the Wireless charger
Click to expand...
Click to collapse
Try pressing power for about 15 seconds, it should reset then.

SteadyQuad said:
Try pressing power for about 15 seconds, it should reset then.
Click to expand...
Click to collapse
it doesnt reset the power button is useless, i guess ill have to wait for the battery to drain maybe then it restarts

adamo86 said:
Try to get into download mode. Or wait a while
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
how do i get it in download mode?

luisumf said:
how do i get it in download mode?
Click to expand...
Click to collapse
The easiest way is plugging the usb cable (which is connected to your computer) to your phone while holding volume down button. No need to press power button. From download mode you can boot to recovery etc with the help of your pc.

Jeopardy said:
The easiest way is plugging the usb cable (which is connected to your computer) to your phone while holding volume down button. No need to press power button. From download mode you can boot to recovery etc with the help of your pc.
Click to expand...
Click to collapse
did not work

This sounds more and more like a case for Yota's repair center. If there wasn't something broken in the device one of these methods described in this thread should have worked.

Sounds like hardware to me.

I had the same issue. Left it on the table with the e-ink screen on top, came back hours later, the clock was 90 minutes behind and the phone dead. Resetting with 10 Seconds ON/OFF button didn´t work. Had to send it in. 2 weeks later got it back. They said they had to change the whole motherboard, even got a new IMEI with it. Then a few days later I tried the main camera and it did not work, error message by Android, unaccessible camera... Then by pressure on the camera it worked sometimes, sometimes only misty lines, sometimes splitscreen mode, sometimes not. Maybe a mistake by the service while reassembling the phone? Anyway, had to send it in AGAIN, got it back, sold it on ebay with 130 Euros loss and bought a new white one because I love the principle and options of the second screen so much. The white one is a newer batch, they say with some new (and probably more reliable?) hardware, so up until now I am completely satisfied, no error for 6 weeks (fingers crossed...)
My old black one was maybe a monday batch

petra333 said:
I had the same issue. Left it on the table with the e-ink screen on top, came back hours later, the clock was 90 minutes behind and the phone dead. Resetting with 10 Seconds ON/OFF button didn´t work. Had to send it in. 2 weeks later got it back. They said they had to change the whole motherboard, even got a new IMEI with it. Then a few days later I tried the main camera and it did not work, error message by Android, unaccessible camera... Then by pressure on the camera it worked sometimes, sometimes only misty lines, sometimes splitscreen mode, sometimes not. Maybe a mistake by the service while reassembling the phone? Anyway, had to send it in AGAIN, got it back, sold it on ebay with 130 Euros loss and bought a new white one because I love the principle and options of the second screen so much. The white one is a newer batch, they say with some new (and probably more reliable?) hardware, so up until now I am completely satisfied, no error for 6 weeks (fingers crossed...)
My old black one was maybe a monday batch
Click to expand...
Click to collapse
Hi Petra. Since you're using a Yotaphone as well, could I ask you to do a small favour for me please? After I had my YP rooted I accidentally deleted the system app "back screen manager". My back screen has stopped working since then. It'd be fantastic if you could just extract the system app from your phone and send it to me so that I can manually place the system app on my phone root folder. You don't have to root your phone for this. All you need is an App extractor from play store. And it will take less than 5 mins to extract and send it to me(Assuming that you are well versed with android OS). Here's my email address [email protected] or you could send me a link to the shared file. Do let me know if you are willing or not. Thanks a ton.

"Your device is corrupt. It can't be trusted and may not work properly." (Red)

"Your device is corrupt. It can't be trusted and may not work properly." (Red)
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
https://support.google.com/nexus/an...6399943843044-1589582643&p=verified_boot&rd=1
Has anyone else experienced this?

I also got that message when I first got device. Set up my Google account and then let it sit and charge. Looked 30 mins later that message appeared. It was also followed up by another screen talking about unsecure boot or something and powered it self off. It said can not boot when I tried to restart phone and I tried again and no response from the phone at all.waited 5 mins and it booted fine and never seen the messages again .

that screen appears when the bootloader is unlocked. did you guys unlock your bootloader? or, did you purchase from T-Mo/someone else?

Bl still locked and bought online from tmobile never even loaded any apps yet

anoymonos said:
Bl still locked and bought online from tmobile never even loaded any apps yet
Click to expand...
Click to collapse
if you reboot to bootloader mode, does your screen look like the picture below:

Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.

maruichan said:
Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.
Click to expand...
Click to collapse
if your phone screen in bootloader mode does not look like the one in my post, you purchased the phone direct from T-Mobile/Other Retailer and you didn't unlock the bootloader, i'd ask for a replacement. if your phone screen in bootloader mode looks like the one in my post, the bootloader has been unlocked somehow/by someone...

cortez.i said:
if you reboot to bootloader mode, does your screen look like the picture below:
Click to expand...
Click to collapse
Power + Vol Dwn gives me this screen...

maruichan said:
Power + Vol Dwn gives me this screen...
Click to expand...
Click to collapse
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.

cortez.i said:
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.
Click to expand...
Click to collapse
K, will try it in a bit

maruichan said:
K, will try it in a bit
Click to expand...
Click to collapse
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.

cortez.i said:
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.
Click to expand...
Click to collapse
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.

maruichan said:
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.
Click to expand...
Click to collapse
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.

See still locked

cortez.i said:
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.
Click to expand...
Click to collapse
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.

maruichan said:
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.
Click to expand...
Click to collapse
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.

BTW, did anyone get a second screen saying contact customer support (some kind of language like that)? It is very similar to the red error screen, but it read like the device was basically bricked. It disappeared after a while and the phone turned off while I was trying to get a picture.

Got both screens

cortez.i said:
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.
Click to expand...
Click to collapse
I did, that is how I got the return date. They notated my account massively and it looks like it'll be a root canal to a exchange.
I'm not sure that it's anything more than a bug... it hasn't stopped the phone from working and possibly may be an oversensitive security measure on Android's part. So far it seems only related to Nexus(?) that I could find... I am only posting here so others can inform themselves. Maybe others with similar errors who have owned a Nexus could enlighten us.
Either case, doing a factory reset in a little bit. I also received the latest update and applied it. So maybe that'll help too...

franki_667 said:
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
Has anyone else experienced this?
Click to expand...
Click to collapse
Yes I have had this happen 2 different times and 4 days apart on my AT&T LG G6, U.S. Variant. NO I don't unlock my devices ever. And I only install well known apps from the Play store. One possible pattern I noticed was that both times it happened relatively soon after turning OFF the always on display. Then when I rebooted the AOD was turned back on by itself. No other settings appear to be changed and my Nova launcher is running normal.
Did you happen to turn off your AOD as well?

Bricked Le Pro 3 727 (Blue Screen of Death)

Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.

Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium

My one did the same, the issue was motherboard. You should send it back to repair.

mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.

Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium

That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.

Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.

shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.

i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?

oneplus 2 not working after screen replacement

My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe

Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.

there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..

Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx

Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs

@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.

dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs

Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.