Database Info

[Q] OnePlus One unique softbrick?

I rebooted my OnePlus One yesterday and found myself in a weird situation. The phone would go to the initial OnePlus logo then after, a smal android logo with a red warning sign appears for a split second, and I boot into the CM stock recovery. I can't turn it on or enter fastboot, nor can I turn on ADB Debugging on my phone and would really appreciate help as I do not want this phone to be gone. Pretty scared guys, help would be much appreciated!

I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.

badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
Thanks for the prompt response. I think you should also know that I attempted to put a custom recovery on my OPO, but after saying that it worked, I only loaded into the CM Stock Recovery. I do not, have my phone with me at the moment as I did not think it would be necessary to bring to school with me, but I will attempt everything you have said. Thanks for the help so far!

badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.

NizzleFish98 said:
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.
Click to expand...
Click to collapse
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?

badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
Yes. It does.
Download the stock image. I'm sure it will be there somewhere in the forums.
Then go to recovery and do the following:
Select 'apply update'. Then you either have the option to apply update from Internal Storage or from adb.
Select adb and enter: adb sideload update_filename.zip

badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
assuming it's the stock android recovery, i'm pretty sure it allows for sideloading.
Def sounds like something got flashed to the wrong parition though

stuck in loop, possibly a different kind of loop

I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.

atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk

soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.

atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk

soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.

Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go

siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.

success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!

stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..

When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.

jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.

audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!

jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:

help? Xperia Z5 TWRP No partitions, No OS, No fastboot

Hi all,
after bootloader unlock, and a few other steps later. I somehow managed to softbrick my Z5.
The phone hangs on bootloader screen. I can still get into TWRP 2.7.8.0.
When rebooting from TWRP says there no OS installed.
Most of the times TWRP is unable to mount system, data etc. After managing to mount all, I tried to go ahead and install either another ROM or a boot.img, recovery.img or twrp.img.
Installing another Rom always seems to fail (and finishes way too fast), and installing another boot.img or recovery.img gives me errors like this:
[IMAGE FLASH STARTED]
Image to flash: '/external_sd/recovery.img'
Calculating restore details...
E: No partitions selected for flashing
Trying to use FlashTool doesn't work either, because I cannot get FastBoot to work either (power off, hold volume Up while attaching device to pc using usb) Only this morning did I manage to FastBoot.
How can I solve this?
Can it be solved through TWRP? by somehow using a PIT file? or any other way?
I am stumped reallly.... So maybe someone with much more knowledge can help me out? Thanks

i got a similar problem but i wasn't able to get into flashmode nor fastboot neither i was able to charge my device when i was comming from XZ Rom bcs i was so buggy but i managed to fix it by force turning it off ( power + vol up 3 vibs ) then i left the phone for 10 seconds then suddenly i entred flashmode without doing anything then i flashed the original FTF
i hope i can help you with this

iSpammer said:
i got a similar problem but i wasn't able to get into flashmode nor fastboot neither i was able to charge my device when i was comming from XZ Rom bcs i was so buggy but i managed to fix it by force turning it off ( power + vol up 3 vibs ) then i left the phone for 10 seconds then suddenly i entred flashmode without doing anything then i flashed the original FTF
i hope i can help you with this
Click to expand...
Click to collapse
Thankx iSpammer, it took me a while to reply, mainly because the battery went to 0%. so first I had to go to a local callshop to fast charge it for a while. Later at home I charged to 100%.
After that I was abled to get into the FlashTool and flash an original TFT, now the phone is also unrooted, had twrp and su, and xposed.
Thanks again, I am one happy camper

pamenja said:
Thankx iSpammer, it took me a while to reply, mainly because the battery went to 0%. so first I had to go to a local callshop to fast charge it for a while. Later at home I charged to 100%.
After that I was abled to get into the FlashTool and flash an original TFT, now the phone is also unrooted, had twrp and su, and xposed.
Thanks again, I am one happy camper
Click to expand...
Click to collapse
any time glad you got your phone bck

Phone is not power up?

I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:

sanrajbhar said:
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
Click to expand...
Click to collapse
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).

xMotoDA said:
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
Click to expand...
Click to collapse
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .

sanrajbhar said:
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
Click to expand...
Click to collapse
I have a similar issue, as my phone also cannot turn on and I have TWRP recovery.
I had rooted my phone with SuperSU and unlocked the bootloader via motorola's tool. But then due to SafetyNet, apps such as Snapchat wouldn't work (cant log in), and I couldn't download Netflix (totally a huge issue).
So I decided to try switching to Magisk instead, as I heard that uses systemless root that doesnt trip Safety Net. While uninstalling SuperSU (using the built in feature for full removal), I was able to uninstall SuperSU and unroot my phone, but was not able to restore the stock boot image in the process. It was at this point I made a NANdroid backup in case I stuffed anything up.
Because of this, I was unable to flash Magisk via the TWRP recovery, so I downloaded a previous version of the firmware from January to flash back to from here. After flashing this and also wiping the user data, my phone booted up fine and worked, and appeared to be in normal condition.
However, then I elected to download and install the firmware update. This all went well, and was installing, until just at the end of the process, when the phone turned off. It had over 60% battery at the time.
At this point in time I'm still unable to get it to boot up, even into recovery or fastboot mode, so I cant really do anything, or restore my NANdroid backup.
If I plug it into my laptop, and hold the power + volume button down for a period of time, I can hear the USB connected tone (Windows 10), which then switches to a disconnected tone and a "USB device malfunctioned" error message pops up.
I tried leaving it unplugged all of last night just in case it was stuck in a boot loop or something so the screen couldn't display anything, in order to flatten the battery, but obviously I couldn't tell any difference. I'm currently now trying to have it plugged into power for an extended period of time just in case it is actually just flat. The current condition is just a black screen as if there was no power at all, with no lights or anything, regardless of a charger being connected, with the buttons not doing anything (I've attempted holding down the power and volume down buttons together for at least 2 minutes to no effect)
Any help would be greatly appreciated.
My specs: Moto G Turbo (2015), model XT1557, running Android 6.0.1. Can't remember exactly, but it previously had the latest firmware available before I tried flashing the January firmware.

Phone stuck at Boot screen after installing TWRP recovery 3.2.1-berlin

I have BLN-L22 device. I installed TWRP recovery 3.1.1- berlin and it installed correctly. Then I found the latest version 3.2.1-berlin on official TWRP app. So I flashed that one and rebooted to recovery. Since then the phone is stuck at the bootscreen which shows 'Phone is unlocked, booting' message.
I can't connect to PC and how can I recover to original?

Official TWRP app (and relative site obviously) leads to a non working build of TWRP, i stumbled upon the same scene too while flashing official 3.1.0 version took by their site... Don't know why. Modded versions of TWRP made by OpenKirin team and HassanMirza01 works correctly instead. Here https://forum.xda-developers.com/honor-6x/development/twrp-honor-6x-hassanmirza01-t3733201 you'll find a working 3.2.1-0 version, i tested it by myself.
Now, to get rid of this and flash a working TWRP, you have to boot to fastboot mode with manual method, so begin with completely shut off the phone by keeping held power button for 10+ seconds.
Then, connect the phone to PC with the USB cable, and boot it up by keeping pressed power button and held down volume - immediately as you hear the vibration. From fastboot, you'll be able to flash back the working TWRP.

Problem Solved
RedSkull23 said:
Official TWRP app (and relative site obviously) leads to a non working build of TWRP, i stumbled upon the same scene too while flashing official 3.1.0 version took by their site... Don't know why. Modded versions of TWRP made by OpenKirin team and HassanMirza01 works correctly instead. Here https://forum.xda-developers.com/honor-6x/development/twrp-honor-6x-hassanmirza01-t3733201 you'll find a working 3.2.1-0 version, i tested it by myself.
Now, to get rid of this and flash a working TWRP, you have to boot to fastboot mode with manual method, so begin with completely shut off the phone by keeping held power button for 10+ seconds.
Then, connect the phone to PC with the USB cable, and boot it up by keeping pressed power button and held down volume - immediately as you hear the vibration. From fastboot, you'll be able to flash back the working TWRP.
Click to expand...
Click to collapse
Hi Thank you so much. The phone was restarting continuously after holding the power button. So I tried by pressing the power and volume down button which took me to fastboot.
Then I could install the compatible version of TWRP successfully.:good:

kpk1307 said:
Hi Thank you so much. The phone was restarting continuously after holding the power button. So I tried by pressing the power and volume down button which took me to fastboot.
Then I could install the compatible version of TWRP successfully.:good:
Click to expand...
Click to collapse
Good job!

RedSkull23 said:
Good job!
Click to expand...
Click to collapse
Hello there!!! help me. i too installed the 3.1 berlin and got stuck.even i have tried installing 3.2 and still i am stuck.no error while installing in both the images though.the screen just got stuck your device is booting..plz help

Venom0425 said:
Hello there!!! help me. i too installed the 3.1 berlin and got stuck.even i have tried installing 3.2 and still i am stuck.no error while installing in both the images though.the screen just got stuck your device is booting..plz help
Click to expand...
Click to collapse
Did you solve your issue.....I am also having same issue now. ..whatever recovery I flash....its get success but still it gets stuck on you are booting now

nokiasatyam said:
Did you solve your issue.....I am also having same issue now. ..whatever recovery I flash....its get success but still it gets stuck on you are booting now
Click to expand...
Click to collapse
You can successfully flash even non compatible images. the problem only arises when you boot them. Simply, they won't be able to boot because they're incompatible.
first, get into fastboot, flash compatible recovery(they are different for emui 5 and 8, so check before you flash). Then boot to recovery by pressing and holding power and volume up button at once from the fastboot mode itself.
Update me with the result. I'll tell you what to do next based on whether the flash works or not.