Database Info

[Q] Red Triangle, Dead Android

After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.

ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..

Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."

ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.

Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?

ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium

Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.

ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.

Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?

ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium

Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.

Can't Access TWRP Recovery

Hi guys, I flashed the latest factory image, then flashed the latest TWRP but can access it 1 out of 10 tries.. What am I doing wrong? Is it a faulty replacement phone? Never had this issue with my other nexus 5 (same recovery file but lollipop and not marshmallow) and now I have this problem.. Tried to riflashato the factory image 5 times, boot to recovery without installing but nothing changed.. Thanks in advance!

If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.

beekay201 said:
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
Click to expand...
Click to collapse
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..

carlese said:
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
Click to expand...
Click to collapse
do you finde fix

slavisa037 said:
do you finde fix
Click to expand...
Click to collapse
Downloaded twrp again and used flashify..

carlese said:
Downloaded twrp again and used flashify..
Click to expand...
Click to collapse
This is not really a fix, since to use Flashify one needs to be rooted already.
What I did to work around this was reflash LMY48M. After reflashing that, fastboot correctly boots/flashes twrp.
I've read that the issue arises when trying to boot and/or flash twrp with MRA56K installed, AND the device is connected to USB.

Ok, i got some of problems here, i tryied to root my Nexus 5 with other Android 6 version, it was the first one launched after development version. Now i have MRA58K version.
Problem 1 : I have no stock recovery, i first rooted original version of Marshmallow with CWM and i soft bricked, so no backup, no factory images. Installed MRA58K and there is no stock recovery, thanks god i can use bootloader. I can install TWRP, but i want to install the old recovery, Tell me how to do it.
Problem 2: Actual version of Marshmallow ask me to install a patch, but when installing i got stuck in TWRP, it cant install it (yes, android was rooted, but i installed twrp before root, and the update were before it.)
Thanks.

You can flash a stock ROM using the flash-all file in a command prompt. This will install stock ROM with stock recovery. Make sure the phone has an unlocked bootloader and you should be fine.
Official OTA updates cannot be installed with a custom recovery.

I tryied 3 times to install OS with flash-all. All the problems start after i installed CWM and try to root the phone, but after that, i used a stock rom image that was different build than actually one.
I`m not sure yet who`s fault is.
Any ideas?

I don't recommend using CWM, only TWRP.

After you flash TWRP always boot into it, and since you're flashing a custom recovery I'm going to assume you don't care about OTA's, swipe to allow system to be mounted. TWRP will automatically patch the system to survive android trying to overwrite it. Reboot into TWRP a second time to be safe. TWRP should stick from now on until you flash over it or restore stock system partition.

Yes, now i have TWRP as recovery, but i want to replace it with stock recovery.
Problem is, when i upload stock recovery and try to boot in recovery mode, i got the green dead android with red triangle.
But after TWRP uploading and booting in recovery mode, TWRP is there..
I really don`t know what`s wrong.

Flash stock recovery, select recovery from the fastboot menu, hold the power button and press volume up button.

Help, MMB29Q update wipes TWRP

Hi all,
Recently I updated my Nexus 5 from Lollipop to Marshmallow 6.0.1 (MMB29Q) - latest build.
everything stock works fine but, once I flash a customer recovery, in my case TWRP it stops working...I get either a startup loop or TWRP gets erased by stock recovery.
I tried various steps ...
flashed TWRP 2.8.7.1 - rebooted to boot loader was able to get into TWRP but, once I reboot system, everything works but TWRP is gone/erased and replaced by stock recovery?
Flash TWRP 2.8.7.1, then flash latest TWRP 3.0, reboot to boot loader and can get into TWRP but once i reboot into system, I am stuck on the initial boot loop.
I have to start from scratch of flashing system and boot etc to get past the loop and it still replaces TWRP with stock recovery.
I can always get into Fastboot but when I go to recovery it seems its being replaced by stock recovery.
anyone experiencing this issue? thanks for your help.

I guess I am doing something stupid but, not sure what...and thanks for your help

If you give more detail on the steps you are taking it will be easier for someone to help. Also, have you tried doing a factory reset when it bootloops?

thanks for the response..here are the details..
I had Lollipop with TWRP 2.8.7.1
yesterday, I downloaded latest build from android site...extracted all files....booted into bootloader and flashed all files..
rebooted - Marshmallow works perfectly...offcourse it not rooted yet or its locedback due to this flash
Scenario:1
So downloaded TWRP 2.8.7.1 and flashed it as recovery, no errors nothing...i rebooted to bootloader and went to recovery to confirm TWRP is there
I rebooted the system - TWRP gives option to root which I said yes so its rooted. I reboot system, this goes into bootloop - I wait for say 5-10 min in this loop mode and I see that adb can recognize the device but nothing else....its stuck in loop
when I force shut down by holding power button for few sec - and go back bootloader/recovery - TWRP is still there
***note*** I did factory wipe in TWRP but that did not fix above condition.
Scenario2:
exact same steps but after I flashed twrp2.8.7.1, I rebooted bootloader and flashed twrp 3.0 as well confirmed twrp 3.0 is flashed and rebooted system - phone start normally no issues - when I restart to bootloader - no TWRP exists, its replaced by stock recovery
Scenario 2, I tried couple of other ways and still the same thing happens - twrp 3.0 get erased.
not sure what I am doing wrong but TWRP doesn't stick
since this is my active device - i flash system.img and boot.img to get the phone to working condition
thanks for your help

Try flashing the latest supersu to get root.

audit13 said:
Try flashing the latest supersu to get root.
Click to expand...
Click to collapse
That did the trick.....thank you very much. I was using older version of supersu thinking it was latest.....I downloaded V2.65 and installed it and that fixed all my troubles..
muchas gracias

OPO Only Boots into TWRP Need Help

So I rooted and installed twrp on my sis's OPO, then installed Resurrection Remix and it worked fine. She decided to restart her phone and now it's stuck in twrp no matter what. What can I do? I've tried searching and can't find a good forum thread about my situation.
I try to enter bootloader, guess what? Goes back to TWRP.
Install new rom? Goes back to TWRP.
Wipe then install new rom? Goes back to TWRP.
I have adb control, what can I do?

I'm going to try this post and will update soon.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Just realized I can't do this because I can't boot into fastboot and can only boot into twrp.

restore nandroid backup. or flash firmware again.

Found my issue. My volume down button is broken now so it just keeps pressing it when I'm not so it kept going into twrp. Manged to get into fastboot, I just have to kept trying and it just sometimes doesn't press down every second.

Can't install Custom Roms.

Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.

Observer000 said:
Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Click to expand...
Click to collapse
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Alright, I check bootloader state, it says bootloader unlock done means it's unlocked.
I am going to flash twrp 3.0.2 and will update you soon!

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.

Observer000 said:
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Click to expand...
Click to collapse
Did TWRP 3.0.2 ultimately work with this?
If worked, I am also curious to know how much space is left there for apps in device memory, since the ROM seems to be Marshmallow based.