Hey all,
I'm having some issues with TWRP.
I've flashed it across through fastboot, but whenever I boot into recovery via the phone, all I get is a black screen and the notification light in the top left of the phone constantly on in the colour white.
It never changes from that and is rather frustrating, as the only way I can get into TWRP is via my PC and fastboot from the bootloader. I have to run the "fastboot boot twrp.img" command in CMD to get it to actually boot into TWRP.
I've tried every TWRP version out there for my device, and some boot me into the black screen, and others simply boot it back into the bootloader. I cannot get my phone to boot into TWRP itself, without needing to be plugged into my pc and manually started via the fastboot command.
Do you guys have any idea what my issue is? I'm starting to give up hope lol.
Thank you for your time,
all the best.
If i am not wrong, you came here after using the unbrick tool. To resolve this issue, boot into twrp by the fastboot command, wipe system+data+cache, transfer the oos 3.5.4 stock zip to the phone, install it, and the issue should be fixed when you boot into recovery next. From here on you can install the rom of your choice.
Oh my god..
I can't believe it. It worked.
This has been grinding at me for at least 2 months now and I basically gave up all hope, thinking my device was borked.
You have no idea how grateful I am for your help. If I could gift you everlasting life I most certainly would.
An infinite number of thank you's, you are now considered god status in my eyes.
Thank you!
ayush2901 said:
If i am not wrong, you came here after using the unbrick tool. To resolve this issue, boot into twrp by the fastboot command, wipe system+data+cache, transfer the oos 3.5.4 stock zip to the phone, install it, and the issue should be fixed when you boot into recovery next. From here on you can install the rom of your choice.
Click to expand...
Click to collapse
Oh my god..
I can't believe it. It worked.
This has been grinding at me for at least 2 months now and I basically gave up all hope, thinking my device was borked.
You have no idea how grateful I am for your help. If I could gift you everlasting life I most certainly would.
An infinite number of thank you's, you are now considered god status in my eyes.
Thank you!
Related
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
bazanster said:
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
Click to expand...
Click to collapse
Flash a stock ROM, preferably LP and see if it works, this is done through fastboot, look around.
bazanster said:
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
Click to expand...
Click to collapse
I faced the same problem here is what i did
flash the twrp2.8.x again in fastboot mode
boot into recovery
restore your backup if you have backedup your previous rom
Rohit99 said:
I faced the same problem here is what is did
flash the twrp2.8.x again in fastboot mode
boot into recovery
restore your backup if you have backedup your previous rom
Click to expand...
Click to collapse
Thanks man, as simple as it was, it worked <3
I have update my rooted OP 3T by flashing the complete rom through TWRP.. But the problem is whenever I flash the Supersu version : SuperSU-v2.79-201612051815 or SR3-SuperSU-v2.79-SR3-20170114223742, I am getting bootloop.
Please anyone advise me.
I checked that without flashing SuperSU phone is able to Boot safely.
Thank you in advance.
It's normal if it bootloops once or twice
But if it's more than that then it's problematic
So which one is it
Another thing you can try is try magisk root instead of supersu and see if gets the same result
Phone was stucked in bootloop for an hour without any reboot.
I am not fond of magisk yet... So dont have any plan for it.
Just want to know if this happens to only me or there are many others with same issue.
Edit:
Finally installed Magisk for root... Issue closed.
help!?
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
plzz can anyone help me
amber sachdeva said:
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
Click to expand...
Click to collapse
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
redpoint73 said:
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
Click to expand...
Click to collapse
well i tried unlocking bootloader but it says failed (remote: oem unlock not allowed)
Iam i stuck here for ever ?
can u tell me the command that i can try on an phone with a locked bootloader
I forgot this is an edit the first time Gentlemen, I am absolutely at wit's end now I am no geek with a capital G however I have been modifying phones for some 3 years now and I can't even tell you how many times I flashed ROMs my beloved 3T 3T has had been acting glitchy lately like when I would reboot the circle that turns - instead of just turning evenly it would twitch, it was such a small thing I ignored it but I think now that that's must be have been indication something was not right few other things like that. I flashed the Freedom ROM cuz I'm so sick a Google and Google Assistant when I came out I was in a bootloop so I wiped everything except OTG everything and formatted data did the ROM Flash again the a boot Loop still abides and I've done it a dozen times now sometimes a couple of times it it just it kept recycling the bootloop another time and got hung up on the OnePlus it just sat there on the logo and if I miss something obvious I do apologize I'm tired and I'm at wits end because I'm not used to not being able to solve my own problems I guess so any help at all or just even a heading in the right direction would be so much appreciated that I don't even know how to call it quantify it thank you
By the way I seldom post or even post questions but when I do I always pretty much say the same thing you guys are the best this is the one place I can come for Andrew Android advice or or guidance and I just I absolutely trust what I read so thank you thank you thank you thanks for being there
Edit - I'm so tired I forgot the first time I went to reflash the ROM it told me that my 3T was in fact not a 3T that it was a three and I read someplace so I'm XDA that that's just Corruption of the install script so I downloaded it again I ran 7-Zip it said it was coherent so I flash it again if that's important but thanks again
Help required
kunal1540 said:
it's normal if it bootloops once or twice
but if it's more than that then it's problematic
so which one is it
another thing you can try is try magisk root instead of supersu and see if gets the same result
Click to expand...
Click to collapse
sir, i have oneplus 3t a3010. Last night my phone was crashed and after crashing it restarts and jumps to recovery mode. In recovery mode i wipe all data and restart my phone. But i still doing the restart thing. Please help, what to do now.
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
My oneplus 3 is stuck in recovery mode
My bootloader is locked
Everytime i switch on my phone there is a message
Which is on photo below
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
flobbadob said:
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
Click to expand...
Click to collapse
Which twrp version are you using?
Did you actually flash any custom rom or do you try to start miui?
Did you change any partition?
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
lanceindie said:
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
Click to expand...
Click to collapse
+1! Thanks :highfive:
Did you solve it? I might have some ideas.
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here http://bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
MDV106 said:
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
Click to expand...
Click to collapse
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
t0r3n0 said:
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
Click to expand...
Click to collapse
you can install it using Magisk Manager apk, or flash the Magisk zip file inside TWRP, your choice. I dont think either of the two menthods are risky
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
shadow87qft said:
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
Click to expand...
Click to collapse
For me, i found that fastboot was being exposed for a few seconds when it would start to turn back on after the battery dying out. I was able to send 'fastboot reboot recovery' and it didn't boot into recovery, but it booted into Android... A bit strange.