Database Info

Phone won't boot...need help quick!

I was running CarbonROM and wanted to try out a TW ROM. I booted into my recovery (TWRP), backed up Carbon, went to wipe options, did a Factory Reset, pushed the button to wipe system, it started but after a couple seconds the phone rebooted. I try boot back into recovery by holding down the power, VOL up, and home button. I get the "Samsung" splash screen and it says "recovery booting....", then the TWRP screen will show for a couple seconds, then my phone will reboot. I can't boot into the phone because I did a factory reset.
So I can't get into the phone and only get the start screen for TWRP but can't actually get into TWRP. Any help?

I found out I can boot into download mode. I should be able to find a stock rooted image there, right? Not sure how to do that though.

Had the same problem a little while back.
It;s been a few weeks since this happened to me so it's a little hazy so bear with me.
You are going to want to use ODIN to flash a rom with root, and once you get that you are going to want to reinstall a recovery pronto. (I suggest EZ-recovery 1.2)
A quick search will give you a few tutorials, just basically start like you are coming from a stock firmware and are rooting through ODIN.
Hope this helps!

schmaltzy said:
I found out I can boot into download mode. I should be able to find a stock rooted image there, right? Not sure how to do that though.
Click to expand...
Click to collapse
It sounds like you TWRP might be broken. I'd try Odin first and pda push the newest TWRP again. If That fails then I'd push the newest CWM in Odin and see if that works. After getting CWMI to boot if you want to go back to TWRP again, pda it over thru Odin. If these fail then push a stock ROM from Odin and start all over again.
Sent from my SCH-I535 using Tapatalk HD

Sounds like a soft brick I did once too. I believe what I did was use Odin to go back to factory defaults, then I rerooted my phone
Sent from my SCH-I535 using Tapatalk 4 Beta
---------- Post added at 05:13 PM ---------- Previous post was at 05:08 PM ----------
Try googling "boot looping"
Sent from my SCH-I535 using Tapatalk 4 Beta

Corrupted Recovery and Missing Launcher

I rooted my Nexus 5 this morning for the first time using chainfire and everything was fine and dandy. I then downloaded goomanager to install twrp and thought it was all good. Turns out when I booted into recovery, it was corrupted with the red triangle android. I restarted the device, but as I started it up, the device automatically went into action launcher as the default launcher. I thought this was strange (as the stock laucher has been my default since I got the phone) so I tried to change it back to the Google home launcher, but it was missing. Here's where I made the mistake. I figured if I deleted action launcher, the system would reinstall home, but it turns out I was greeted with a launcher-less and recovery-less nexus 5.
I tried to use adb on my computer but it would not connect. I do not have the option in device manager to update drivers, just to view them. Now my phone is at the splash screen with access to fastboot but no recovery.
Thanks in advance for assistance.

sully212121 said:
I rooted my Nexus 5 this morning for the first time using chainfire and everything was fine and dandy. I then downloaded goomanager to install twrp and thought it was all good. Turns out when I booted into recovery, it was corrupted with the red triangle android. I restarted the device, but as I started it up, the device automatically went into action launcher as the default launcher. I thought this was strange (as the stock laucher has been my default since I got the phone) so I tried to change it back to the Google home launcher, but it was missing. Here's where I made the mistake. I figured if I deleted action launcher, the system would reinstall home, but it turns out I was greeted with a launcher-less and recovery-less nexus 5.
I tried to use adb on my computer but it would not connect. I do not have the option in device manager to update drivers, just to view them. Now my phone is at the splash screen with access to fastboot but no recovery.
Thanks in advance for assistance.
Click to expand...
Click to collapse
first off, you need to do some reading on android.
2nd, your recovery is not corrupted, the red triangle android is the stock recovery. you didnt flash a recovery because goomanager isnt flashing twrp recovery since 4.4. it didnt even download it probably. what you have to do is flash the recovery while you are in fastboot. everything else you wrote i about the launcher i dont understand what you wrote. but before you go any further, you should learn about what you are doing before you do it. do not use a toolkit, you will not learn anything that way and could get yourself into an even worse circumstance http://forum.xda-developers.com/showthread.php?t=2508292

simms22 said:
first off, you need to do some reading on android.
2nd, your recovery is not corrupted, the red triangle android is the stock recovery. you didnt flash a recovery because goomanager isnt flashing twrp recovery since 4.4. it didnt even download it probably. what you have to do is flash the recovery while you are in fastboot. everything else you wrote i about the launcher i dont understand what you wrote. but before you go any further, you should learn about what you are doing before you do it. do not use a toolkit, you will not learn anything that way and could get yourself into an even worse circumstance http://forum.xda-developers.com/showthread.php?t=2508292
Click to expand...
Click to collapse
Thank you for the clarification. I attempted to flash recovery through adb commands, however, the device did not show up. I have tried multiple times to reinstall drivers, but to no success. When I go to device manager => nexus 5 => hardware => properties => drivers, the only available option is to view driver details, with no option to update, roll back, disable or uninstall them. Do you know how to fix this?

sully212121 said:
Thank you for the clarification. I attempted to flash recovery through adb commands, however, the device did not show up. I have tried multiple times to reinstall drivers, but to no success. When I go to device manager => nexus 5 => hardware => properties => drivers, the only available option is to view driver details, with no option to update, roll back, disable or uninstall them. Do you know how to fix this?
Click to expand...
Click to collapse
you dont flash the recovery via adb, you use fastboot while youre plugged into your computer and are in your bootloader. again, fastboot, not adb.
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
oh, and if you have root already, you can flash twrp recovery using the flashify app(download twrp recovery to your phone, flash with flashify. and you can use the twrp manager app to download and install twrp

simms22 said:
you dont flash the recovery via adb, you use fastboot while youre plugged into your computer and are in your bootloader. again, fastboot, not adb.
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
oh, and if you have root already, you can flash twrp recovery using the flashify app(download twrp recovery to your phone, flash with flashify. and you can use the twrp manager app to download and install twrp
Click to expand...
Click to collapse
Again, still a little puzzled. All this makes sense, but for some reason, all of my launchers were uninstalled in a reboot. Like this (http://forum.xda-developers.com/showthread.php?t=1212448). When I boot up, the splash screen is persistent and keeps rotating without the lock screen showing up. So, in a sense, the only thing I have access to on my phone is the fastboot menu. In all cases, I need to use adb to either push a new launcher app to my phone or flash a complete recovery.

sully212121 said:
Again, still a little puzzled. All this makes sense, but for some reason, all of my launchers were uninstalled in a reboot. Like this (http://forum.xda-developers.com/showthread.php?t=1212448). When I boot up, the splash screen is persistent and keeps rotating without the lock screen showing up. So, in a sense, the only thing I have access to on my phone is the fastboot menu. In all cases, I need to use adb to either push a new launcher app to my phone or flash a complete recovery.
Click to expand...
Click to collapse
adb doesnt work in the bootloader, but works in recovery. fastbootcworks while youre in your bootloader. try flashing a recovery. or you can start over by flashing the factory img via fastboot while in the bootloader. another reason i hate root toolkits, occasionally they themselves mess things up.
---------- Post added at 06:43 PM ---------- Previous post was at 06:41 PM ----------
btw, some bad info in that thread you linked. bootloops dont happen if you have no launcher. nothing happens actually, just no launcher.

simms22 said:
adb doesnt work in the bootloader, but works in recovery. fastbootcworks while youre in your bootloader. try flashing a recovery. or you can start over by flashing the factory img via fastboot while in the bootloader. another reason i hate root toolkits, occasionally they themselves mess things up.
---------- Post added at 06:43 PM ---------- Previous post was at 06:41 PM ----------
btw, some bad info in that thread you linked. bootloops dont happen if you have no launcher. nothing happens actually, just no launcher.
Click to expand...
Click to collapse
It works! So fastboot recognizes my device, now I just need to flash twrp through fastboot commands, correct? Thank you so much for your help!

Got it working! Thanks so much again... Thought I had a brick on my hands for a little while there. You're a lifesaver! +1!!!

sully212121 said:
Got it working! Thanks so much again... Thought I had a brick on my hands for a little while there. You're a lifesaver! +1!!!
Click to expand...
Click to collapse
sweet.. now im happy for you

How to reverse to stock recovery? (non twrp)

I was trying to install TWRP to root but unsuccessful. Now, how can I reverse it back to stock eRcovery please? thanks

Extract the firmware and flash stock recovery via fastboot.
https://forum.xda-developers.com/showthread.php?t=2433454 can't find if there is a newer version at the moment.

aznboix said:
I was trying to install TWRP to root but unsuccessful. Now, how can I reverse it back to stock eRcovery please? thanks
Click to expand...
Click to collapse
Even if you installed TWRP, it won't matter. You'll still have eRecovery because it's on the recovery2 partition, not the recovery partition.
Long story short, to get into eRecovery, you have to hold volume up key with the USB plugged in.

duraaraa said:
Even if you installed TWRP, it won't matter. You'll still have eRecovery because it's on the recovery2 partition, not the recovery partition.
Long story short, to get into eRecovery, you have to hold volume up key with the USB plugged in.
Click to expand...
Click to collapse
Hi. what is a erecovery? I tried to root my phone and install twrp with the method given. However no root required apps seems to work. I am flashing through twrp but no luck. Even the titanium backup says i am rooted, it does not work properly.
So should I use that erecovery thing to return back to stock firmware? does the root process has problems?
Thanks.

erecovery does not work -- not if you have twrp installed
---------- Post added at 01:40 PM ---------- Previous post was at 01:15 PM ----------
The extractor works, but the tool that suppose to rename them to the right thing does not -- it just dies after renaming a few of the files with FINDSTR line too long error messages..

Neither Can't Get out of (Odin Mode/Download Mode) nor Can't Enter in Recovery Mode.

Hello Every One,
I had Installed Lollipop (android 5.0) Custom ROM in my Samsung Galaxy S3 GT-19300 & I wanted to install marshamallow (android 6.0) I Had Downloaded The Zip Files of ROM in my Mobile but before Starting the Installation I had to Go to Recovery mode But i was Receiving The Download or You can say Odin mode screen After Pressing Vol up+home+Power button So i Tried To Reboot it in Recovery Mode From Reboot option But That Made that a Bootloop Becuase i Couldn't Enter To Recovery Mode & Stucked in Download Mode & Now When ever i restart My Mobile The Same Download Mode Comes & Becuase i Cannot Go Further So No Softwear (odin,Kies,Kingo root,Mobile go,mobogenie etc) can't Detect my phone after plugging it to computer, Please Any one help It has been days that i am searching for any solution.

Why not reflash your recovery with odin? It will probably let you out of download mode and be able to get to recovery.
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
Sorry. I just noticed that not even odin detects it any more.
---------- Post added at 08:38 PM ---------- Previous post was at 08:28 PM ----------
I guess you already tried the usual stuff like uninstall kies and all other stuff that might interfear with odin, tried different ports and cables. Started odin with admin rights and tried other versions of odin ? Does it get recognised as anything in device manager?

yeah The Device Icon Does Come in Device Manager but Odin says that "Connected Device has stopped responding", And yeah i tried odin with admin Rights too but not of any use & Also i tried different ports and uninstalling odin etc & installing odin again but it was useless as it was giving the same result.

[RECOVERY] TWRP 7.1 (unofficial)

Current build
tulip-twrp-7.1-r1.img
MD5: bdf289666fc7262b8f3af7f5b579ecaa
Built: Oct 18, 2017
Installation instructions
The easiest way to install is using tuliptool. See the tuliptool thread for details.
Notes
r1 should be fully functional. Please report any bugs.

Tried it, but...
I flashed the beta to recovery, and this is what I got:
Code:
PS C:\tuliptool> .\tuliptool-win64.exe write recovery
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
log: start 1181696, num 45220
Write 23152640 bytes, 45220 sectors
Failed: Unknown error
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
Failed: Unknown error
Afterwards, I tried to boot into recovery, and I got some sort of "Factory Test Mode" screen. I'm assuming that means I don't have a recovery or something, because the flashing failed.
Phone Info:
Code:
ZTE/P852A11/tulip
7.1.1/NMF26V/20170519.163520
user/release-keys
v1.2.0B09 installed

Oh. Yeah. I'll fix that. The problem is that the flash tool wants an image that is an even multiple of the sector size.
In the mean time, you should be able to use dd in adb shell from the old twrp to update.
mattx1002 said:
I flashed the beta to recovery, and this is what I got:
Code:
PS C:\tuliptool> .\tuliptool-win64.exe write recovery
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
log: start 1181696, num 45220
Write 23152640 bytes, 45220 sectors
Failed: Unknown error
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
Failed: Unknown error
Afterwards, I tried to boot into recovery, and I got some sort of "Factory Test Mode" screen. I'm assuming that means I don't have a recovery or something, because the flashing failed.
Phone Info:
Code:
ZTE/P852A11/tulip
7.1.1/NMF26V/20170519.163520
user/release-keys
v1.2.0B09 installed
Click to expand...
Click to collapse

File is now padded to 1mb boundary. OP updated with new MD5. Please re-download and try again.

Is this for b12 or b14?

Should work with both b12 and b14.
MrWhite0429 said:
Is this for b12 or b14?
Click to expand...
Click to collapse

Is the phone able to boot properly if I flash just the recovery without flashing the boot.bin

Yes just flash the recovery. Boot to recovery by holding the volume up button with the power button. I don't think stock updates recovery at boot, but I'm not sure.
Note you will need the custom boot image with verity disabled if you change anything in the system partition. I think SuperSU also disable verity, or at least can.
MrWhite0429 said:
Is the phone able to boot properly if I flash just the recovery without flashing the boot.bin
Click to expand...
Click to collapse

Ok. Twrp flashed successfully. Now my device just hangs at the splash screen and will not go any farther.
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
I can not get back into EDL or Recovery. ugh....
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
UPDATE: I am able to get back into TWRP if i pull off some very specific button combinations. However thats all im able to do. Android will not boot.

I'm confused how you killed android by flashing recovery.
Is it possible you flashed the modified b12 boot image on a b14 system? If that's the case just flash back the backup. I'll create a b14 boot image asap.
MrWhite0429 said:
Ok. Twrp flashed successfully. Now my device just hangs at the splash screen and will not go any farther.
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
I can not get back into EDL or Recovery. ugh....
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
UPDATE: I am able to get back into TWRP if i pull off some very specific button combinations. However thats all im able to do. Android will not boot.
Click to expand...
Click to collapse

I didnt flash any boot image. I flashed the TWRP in this thread with the tulip tool. and did not flash any boot.bin at all. I am on B14
---------- Post added at 02:39 AM ---------- Previous post was at 02:37 AM ----------
Also Ive noticed to get back into TWRP if this happens to anyone else. You have to hold
Power button THEN press and hold volume up.
Once the ZTE Screen loads you must tap the power button repeatedly and then for some reason TWRP will boot.
---------- Post added at 02:46 AM ---------- Previous post was at 02:39 AM ----------
Flashed backup and now device will not boot into recovery or android at all, However I am able to still get into EDL.

Let me know if you get the device working again. I can help if you can't figure it out.
I am still confused about what could have happened...
MrWhite0429 said:
I didnt flash any boot image. I flashed the TWRP in this thread with the tulip tool. and did not flash any boot.bin at all. I am on B14
---------- Post added at 02:39 AM ---------- Previous post was at 02:37 AM ----------
Also Ive noticed to get back into TWRP if this happens to anyone else. You have to hold
Power button THEN press and hold volume up.
Once the ZTE Screen loads you must tap the power button repeatedly and then for some reason TWRP will boot.
---------- Post added at 02:46 AM ---------- Previous post was at 02:39 AM ----------
Flashed backup and now device will not boot into recovery or android at all, However I am able to still get into EDL.
Click to expand...
Click to collapse

Ok. I am able to get the device to boot into stock recovery and EDL mode now. However android still will not load. Device has been sitting at ZTE Splash screen for almost 10 mins.

Oh.... by any chance did you let twrp mount system read/write? Even once? That destroys the verity integrity.
MrWhite0429 said:
Ok. I am able to get the device to boot into stock recovery and EDL mode now. However android still will not load. Device has been sitting at ZTE Splash screen for almost 10 mins.
Click to expand...
Click to collapse

The Device is also not responding to the wall charger any more. Im afraid if the battery dies I may have a perminantly bricked device.

Don't worry, you can't brick the device if you can get to EDL.
MrWhite0429 said:
The Device is also not responding to the wall charger any more. Im afraid if the battery dies I may have a perminantly bricked device.
Click to expand...
Click to collapse

I dont believe I did. Unless I did it without knowing. When TWRP booted it asked me for a password. I selected cancel. Then I selected Read Only. And then I selected reboot to system. and Here I am. With That being said if it may have destroyed the verity then im stuck until I can flash a B14 Non-Verity boot?

Let's assume you did allow twrp to mount system RW and your verity integrity is destroyed. Just upload the original b14 boot image and I'll make a modified version with verity disabled. That should get you running again.
Note I'm getting ready to go out with my wife so it will be a few hours until I can do that.
MrWhite0429 said:
I dont believe I did. Unless I did it without knowing. When TWRP booted it asked me for a password. I selected cancel. Then I selected Read Only. And then I selected reboot to system. and Here I am. With That being said if it may have destroyed the verity then im stuck until I can flash a B14 Non-Verity boot?
Click to expand...
Click to collapse

Just flashed the backup B14 boot that I had and no luck. Device still hangs at splash.

MrWhite0429 said:
Just flashed the backup B14 boot that I had and no luck. Device still hangs at splash.
Click to expand...
Click to collapse
Flash stock recovery and try to flash with the original firmware zip