Database Info

[Q] Installed TWRP on stock N5 and now in BOOTLOOP

Hi guys,
I have a stock Nexus 5 running 5.0.1.
I wanted to root, so I made the first step by unlocking and then right after flash TWRP
Looked like......
./fastboot oem unlock
./fastboot flash recovery TWRP.img (twrp.img is what i renamed the 8.2 version of TWRP)
Then i restarted and now it goes to google screen ---> TWRP screen for 5 sec ---> reboot ----> TEAMWIN logo BOOTLOOP. I get that Teamwin logo over, and over again.
Any help? All I did was install TWRP and I get this.
What I did to try and remedy, but to no avail is...... erase TWRP with ./fastboot erase recovery, then install the 8.1 version of it.
HELP!?

This is the first I've heard of anyone having problems with TWRP 2.8.1. This is a known issue with TWRP 2.8.2 for some users. What happens when you live boot TWRP (fastboot boot TWRP.img)?

BirchBarlow said:
This is the first I've heard of anyone having problems with TWRP 2.8.1. This is a known issue with TWRP 2.8.2 for some users. What happens when you live boot TWRP (fastboot boot TWRP.img)?
Click to expand...
Click to collapse
boot twrp.img still gives the the BOOTLOOP. I AM BRICKED because I flashed TWRP, WTF!??????????????????
I even tried erasing recovery and installing 8.1, but still same problem.

If you read on pinned post about rooting Nexus 5, you should reboot first after OEM unlock until boot completely into OS then do whatever you want.

b00bs said:
If you read on pinned post about rooting Nexus 5, you should reboot first after OEM unlock until boot completely into OS then do whatever you want.
Click to expand...
Click to collapse
I managed to get to the bootloader and flashed recovery.img
Now my phone is off and wont turn on.
Is this phone destroyed?

Flash factory image from the PC, and then let the phone boot normally, until you see the screen to setup your google account. Only then you can reboot to bootloader and flash trwp, now you won't have any problem.

solhu said:
I managed to get to the bootloader and flashed recovery.img
Now my phone is off and wont turn on.
Is this phone destroyed?
Click to expand...
Click to collapse
Have you ever tried flashing the bootloader yet? If no. Then you should be ok to get back in it. Hold the power button for like 20-30 seconds to make sure it's off properly
Sent from my Nexus 5 using Tapatalk (the older 4.9.5 not that new 4.10 abomination they released for god knows why reason)

Ben36 said:
Have you ever tried flashing the bootloader yet? If no. Then you should be ok to get back in it. Hold the power button for like 20-30 seconds to make sure it's off properly
Sent from my Nexus 5 using Tapatalk (the older 4.9.5 not that new 4.10 abomination they released for god knows why reason)
Click to expand...
Click to collapse
I can get it to turn on, but It goes to the Android L dots load screen, then bootloops that. CANNOT get to Bootloader...............
Will google help me?

If it gets Android dots. It must be able to get bootloader. Hold power for like 20 seconds so it'll look like it's rebooting. But keep holding and a few seconds after it'll shut down completely. Then try holding volume down while powering up
Sent from my Nexus 5 using Tapatalk (the older 4.9.5 not that new 4.10 abomination they released for god knows why reason)

I've opened this thread a few times and cringed each time. Much of the panic and incorrect descriptions such as "bricked" stem from a lack of knowledge. All this knowledge is available in general > sticky roll-up.
Do yourself (and everyone trying to help you) a favour and please read the sticky threads before you do anything else.

rootSU said:
I've opened this thread a few times and cringed each time. Much of the panic and incorrect descriptions such as "bricked" stem from a lack of knowledge. All this knowledge is available in general > sticky roll-up.
Do yourself (and everyone trying to help you) a favour and please read the sticky threads before you do anything else.
Click to expand...
Click to collapse
Same, cried while reading this. People were trying to give him advices and all what he was doing was panicking and saying that his phone is bricked instead of following their advices....

HTC One M7 boots into recovery

Hi, My problem seems to be similar to others but I'm not experienced enough to decide to follow some of the suggestions & end up causing more problems. I'm hoping that exactly the same thing has occurred to others & I can get the right answer. My head is spinning after reading all the options.
So I have an M7 which I decided to root before replacing it. I did root a Desire a few years ago so I'm not totally inept.
Anyway I used the HTCOneRoot.com method, downloaded the HTCOneRoot.zip folder & went ahead. All went well, the bootloader was unlocked & TWRP openrecovery-twrp-2.6.3.0-m7.img installed. I installed CWM-SuperSu-v1.30.zip from recovery which TWRP said was successful & rebooted to system. When started up I found that the phone did not have root. I connected the phone to the PC a couple of times, installed different versions of SuperSu, rebooted into recovery & installed the zip files from TWRP but still had no root. Now when I switch the phone on I get the HTC splash screen & then it goes into recovery. Reboot & the same thing happens. I can get fastboot usb & PC device manager sees android device but it doesn't appear in computer as a drive. I did delete cache a couple of times too. I just don't know what to do next but would like to learn more & not brick it.
HBOOT - 1.61.0000, S-On. Was a Telstra phone but is not locked to a carrier.
Have tried to include all details, hope this isn't too long . Any help will be gratefully received.

Reflashing atock system and boot should fix the bootloop
Sent from my Lenovo A7010a48 using XDA Labs

DarkBlood. said:
Reflashing atock system and boot should fix the bootloop
Sent from my Lenovo A7010a48 using XDA Labs
Click to expand...
Click to collapse
Thanks for that. I see I didn't mention that I did a system backup while trying to root & at one stage out of desperation I did a restore but it made no difference. I don't know how I can get hold of a stock system if the computer doesn't see the phone although as I said, the device manager can see an android device. I'm still lost I'm afraid.

What is the name you see in device manager
Sent from my Lenovo A7010a48 using XDA Labs

ZTE Axon7 HELP! [TWRP problems??]

Hey guys,
Longtime lurker but first time encountering a problem and needing to register.
I've previously ran a nethunter build on an old Nexus 6 which went fine. Now I've picked up the ZTE Axon7 as I needed a new phone.
I followed this thread: HERE
I successfully was able to follow along and get TWRP as my bootloader.
I then followed the instructions to go HERE to grab the Axon7 img file and tried the "TWRP Install" method (install the image to recovery and flash it)
Now upon reboot, I get the ZTE logo (the red dot shows up at the same time like a normal boot) then the log and dot disappear with the red dot then doing one quick flash afterwards. From there the device is just off. Even if I try doing a reboot to the bootloader via power + VolUp the same thing happens. Essentially I think this means the entire bootloader from twrp is now gone??? Plugging into my PC I still get the sound of a device connecting but it is not seen in Windows. HOWEVER while the device is connected to my PC I AM still able to see the Qualcomm port in my Device Manager.
Is there any way to go back to having an OS????? Even my backups I made??? It just seems like there isn't even the bootloader anymore and I just don't know what to do :crying:
If someone could PLEASE help it would mean the world to me!

Did you ever get this resolved?

xerxes_ said:
Hey guys,
Longtime lurker but first time encountering a problem and needing to register.
I've previously ran a nethunter build on an old Nexus 6 which went fine. Now I've picked up the ZTE Axon7 as I needed a new phone.
I followed this thread: HERE
I successfully was able to follow along and get TWRP as my bootloader.
I then followed the instructions to go HERE to grab the Axon7 img file and tried the "TWRP Install" method (install the image to recovery and flash it)
Now upon reboot, I get the ZTE logo (the red dot shows up at the same time like a normal boot) then the log and dot disappear with the red dot then doing one quick flash afterwards. From there the device is just off. Even if I try doing a reboot to the bootloader via power + VolUp the same thing happens. Essentially I think this means the entire bootloader from twrp is now gone??? Plugging into my PC I still get the sound of a device connecting but it is not seen in Windows. HOWEVER while the device is connected to my PC I AM still able to see the Qualcomm port in my Device Manager.
Is there any way to go back to having an OS????? Even my backups I made??? It just seems like there isn't even the bootloader anymore and I just don't know what to do :crying:
If someone could PLEASE help it would mean the world to me!
Click to expand...
Click to collapse
First, TWRP is a custom recovery, not a bootloader.
Second, it seems to me that your device has a locked bootloader, you have to have an UNLOCKED bootloader to flash TWRP, flashing TWRP without unlocking bootloader brocks devices. You need to restore your stock firmware.
What exactly does device manager label your device as when you connect to PC?
Sent from my SCH-I535 using Tapatalk

MelloZ said:
Did you ever get this resolved?
Click to expand...
Click to collapse
Yes, DrakenFX helped me out. Ended up being a long complicated process that I couldn't really rewrite here if I tried.

Help me fix a bricked OPO :(

Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?

try charging the phone for a few hours

se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.

sounds like u need a new battery

ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.

@bmark240
help please

se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.

bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.

kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.

Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.

THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os

THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out

FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.

i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.

Phone won't turn on, no system

I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.

Naveenthemi said:
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Click to expand...
Click to collapse
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?

Fcyrp Zip Need to Flash After Flash any Custom Rom
And Come in Telegram Official Group For Any Support of Redmi Note 7 Pro https://t.me/Rn7proGlobal

zhou111 said:
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Click to expand...
Click to collapse
Yes it's hardbricked for sure! But are you sure MiFlash doesn't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...

Naveenthemi said:
Yes it's hardbricked for sure! But are you sure MiFlash doens't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Click to expand...
Click to collapse
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.

zhou111 said:
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
Click to expand...
Click to collapse
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)

Naveenthemi said:
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Click to expand...
Click to collapse
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.

zhou111 said:
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
Click to expand...
Click to collapse
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too

Naveenthemi said:
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Click to expand...
Click to collapse
I entered the command says waiting for device. how do you flash with adb?

zhou111 said:
I entered the command says waiting for device. how do you flash with adb?
Click to expand...
Click to collapse
Oh that means ADB isn't recognizing it.
There isn't much we can do if ADB doens't recognize it!
Did you look up for Service Centres?

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.

hackeroid said:
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
Click to expand...
Click to collapse
He/She said the phone doesn't boot into Fastboot either so that's very unlikely to work :-\