Database Info

Recovery bootloop. No USB debugging. No Recovery.

So long story short, tried installing unofficial CWM recovery, and phone bootlooped. It just boots up, says it's booting to recovery, and restarts. Boots to recovery restarts. I can boot into download mode, but I don't think USB debugging is enabled because I can't see my device on adb. I think my only option might be fastboot, but I don't know how to set it up or use commands to reinstall philz custom recovery. I had that before I tried the unofficial CWM. Anyone have an idea on how I can get myself out of this one? Any help will be very much appreciated!

Use Odin to flash a recovery. Should bring it back to life
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
http://forum.xda-developers.com/showthread.php?t=2958614
Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_2_7_15

metalfan78 said:
Use Odin to flash a recovery. Should bring it back to life
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
http://forum.xda-developers.com/showthread.php?t=2958614
Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_2_7_15
Click to expand...
Click to collapse
I'm on Antergos right now, so I can't use Odin. My phone tries to boot to recovery mode when I just hold the power button down, fails, then keeps trying to reboot to recovery.

Dont know if this was somved or not, but it sounds like your recovery didnt take, thats why it keeps trying boot into recovery and failing. Its missing. Either restore a backup, find a way to flash a recovery since you cant use odin, or find a way to flash back to complete stock package which will include a recovery.

I just took the phone to sprint and got a new one free of charge.

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !
I recently rooted my Motorola Moto G3 and it worked.... ish, when I opened my phone from it being turned off I was greeted with the message telling me that it was super duper dangerous to root your phone and I could damage my phone, that normally goes as it is just a mandatory thing that they have to say, I waited for a while and it didn't go, I waited for a day and it didn't go. So I let it run out of charge and tried to boot it again, this didn't work, I was still seeing the same white screen with red and black writing. I then let it run out of charge and open it in fast boot mode by pressing the power button and volume down, this did work and from there I have managed to open the team win recovery project but whenever I do anything from then, it will go back to the error page and then will never load. I have even reset the phone to factory settings. If I hold the power button it will turn off the phone but very shortly after automatically turn itself back on to this same image.... please help!

How did you end up rooting it? Have you tried flashing a factory image?

If I were you, I would try to reflash stock firmware with factory reset

@Artyb52
hi, what did you do to Root ??
check these , if you have done evrything :
1) USB debugging enabled, allow OEM unlocking Enable ( developer options )
2) install ADB and fastboot. ( in PC)
3) Unlock bootloader in Fastboot mode .. (After unlocking did you PowerOn your phone, and check ? did it ON with out any problems? )
4) Installing a recovery , by following proper commands and choosing right version ..
5) flashing SuperSU with that Recovery.
If you have done everything Right, then Do onething.. Change CustomRecovery Version ( if on TWRP ) ,
else Goto Fastboot.. press POWER OFF, so that your phone gets SHUT DOWN, then On it normally ..
i have seen a problem where REBOOT function causes Bootloops..

i tried that and it didnt work :/
@nandakis4 shame it didn't work. Do you have any other tips, I would be really grateful

@Acetyloaceton how do you do that ? sorry for sounding like such a noob, i'm new to the game

l3ones said:
How did you end up rooting it? Have you tried flashing a factory image?
Click to expand...
Click to collapse
@13ones I tried flashing the TWRP image, is that different to the factory image ?

The same thing happened me when I rooted my phone. To fix it I downloaded cm 13 then placed it on internal storage and flashed it (and gapps) from twrp and it worked fine.

Acetyloaceton said:
If I were you, I would try to reflash stock firmware with factory reset
Click to expand...
Click to collapse
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Artyb52 said:
@13ones I tried flashing the TWRP image, is that different to the factory image ?
Click to expand...
Click to collapse
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.

l3ones said:
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.
Click to expand...
Click to collapse
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this

Try this
Using adb sideload on twrp
1. Flash supersu 2.62, then
2. Flash supersu 2.65
Command : adb sideload supersu.xx.zip
In my case, it works.

Artyb52 said:
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this
Click to expand...
Click to collapse
If I'm not too late, sure. What model do you have?

[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

S6 Issue - Wont boot

Hi guys,
A friend of mine has given me a S6 which they said did not work, after a bit of fiddling I found:
Download Mode, was working
Recovery mode can't be accessed
Normal boot doesn't seem to work at all (no boot logos including samsung one)
I have attempted to flash the correct ROM but to no success, also attempted to flash just the boot loader to see if that would help, all passes through odin without errors restarts the phone but still doesn't boot.
Am I missing anything, anything I could try? It's rather an annoying situation as the phone must be operational for download mode to work but seems bricked.
Thanks all

Did you use rom with consisting of 4 files or one?

snowqwer said:
Did you use rom with consisting of 4 files or one?
Click to expand...
Click to collapse
One being a md5 file of 3.7GB

I think you should use rom consisting 4 files ( ap, bl, cp, csc ) and PIT ( you can extract from csc file). Then the entire phone will be reset.
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 Mark "Binary Nature" option.

JRNetwork said:
One being a md5 file of 3.7GB
Click to expand...
Click to collapse
What model of device do you have? And can you enter recovery?
And this file is good, i am using firmwares from updato.com and are in that format.

Gara91 said:
What model of device do you have? And can you enter recovery?
And this file is good, i am using firmwares from updato.com and are in that format.
Click to expand...
Click to collapse
Its a SM-G920F
Recovery not accessible, only thing that is, is download mode

JRNetwork said:
Its a SM-G920F
Recovery not accessible, only thing that is, is download mode
Click to expand...
Click to collapse
What happens when you attempt to enter recovery?
---------- Post added at 04:46 PM ---------- Previous post was at 04:44 PM ----------
Gara91 said:
What happens when you attempt to ebter recovery?
Click to expand...
Click to collapse
And one more thing, when you flash stock rom with odin you must force restart your device, then factory reset in recovery otherwise it will not boot... but you cant access recovery

Gara91 said:
What happens when you attempt to enter recovery?
---------- Post added at 04:46 PM ---------- Previous post was at 04:44 PM ----------
And one more thing, when you flash stock rom with odin you must force restart your device, then factory reset in recovery otherwise it will not boot... but you cant access recovery
Click to expand...
Click to collapse
Literally nothing, it stays with a black screen, its weird as hell. Any other ideas?
On this as well, when trying to boot plugged in to the computer nothing on the USB controller. If I boot in to download mode it shows. I don't get why it's bricked in this way :/

JRNetwork said:
Literally nothing, it stays with a black screen, its weird as hell. Any other ideas?
On this as well, when trying to boot plugged in to the computer nothing on the USB controller. If I boot in to download mode it shows. I don't get why it's bricked in this way :/
Click to expand...
Click to collapse
Don't know man, if everything is ok with your hardware and if you are attempting to flash right firmware for your device model then i have no idea what is wrong... i am also new to samsung and maybe someone else can help... good luck

Thanks anyway mate.
Anyone else have an idea?

I am in exactly the same position as you, have you made any progress?
I flashed the latest stock rom and I get to the boot screen but no further. no access to recovery either so only have download mode.
The Firmware I flashed was in one file. Where can I source the latest firmware in separate files to see if that works?

Help! OP6 stuck in 'the boot loader is unlock and software... etc' screen!

So i tried flashing blu-spark twrp.. and magisk up until the moment i had to reboot after installing magisk... now the phone is stuck in this screen i dont know what do, help

What screen? Pictures would help others give feedback and information to assist you. I have yet to update to Android Pie because I am waiting for an official TWRP release myself and I like to gather as much information as I can before I make a leap into the next update

dgunn said:
What screen? Pictures would help others give feedback and information to assist you. I have yet to update to Android Pie because I am waiting for an official TWRP release myself and I like to gather as much information as I can before I make a leap into the next update
Click to expand...
Click to collapse
thanks, sorry dont have another phone to take a picture of this but its basically the screen we get when first booting that shows the device has an unlocked bootloader... the 'warning screen'
edit: **** the link was wrong
edit2: this one but in our device http://i.imgur.com/88NcI2K.jpg

+1 same procedure and same problem.
No connection to PC possible and no "reset-buttons" work.
---------- Post added at 11:18 AM ---------- Previous post was at 10:52 AM ----------
Okay, I managed to get my phone booting up again.
1. Turn off phone by holding just the power-button
2. Boot phone into fastboot-mode by holding vol-up and power-button
3. In Fastboot-mode connect phone to pc
4. get stock OxygenOS-boot.img (Stock boot-recovery images) from here
5. flash the boot.img via fastboot: "fastboot flash boot stockboot.img"
After that my phone booted up again. TWRP is removed through that procedure. I will wait a while before testing it again.

Got the same as you. Booted back into Blu Spark TWRP, wiped Dalvik and cache and then selected the other boot partition. Booted up for me.

lal000r said:
+1 same procedure and same problem.
No connection to PC possible and no "reset-buttons" work.
---------- Post added at 11:18 AM ---------- Previous post was at 10:52 AM ----------
Okay, I managed to get my phone booting up again.
1. Turn off phone by holding just the power-button
2. Boot phone into fastboot-mode by holding vol-up and power-button
3. In Fastboot-mode connect phone to pc
4. get stock OxygenOS-boot.img (Stock boot-recovery images) from here
5. flash the boot.img via fastboot: "fastboot flash boot stockboot.img"
After that my phone booted up again. TWRP is removed through that procedure. I will wait a while before testing it again.
Click to expand...
Click to collapse
Did this wipe anything when you flashed the stockboot.img? Just data or internal too?
ptoner said:
Got the same as you. Booted back into Blu Spark TWRP, wiped Dalvik and cache and then selected the other boot partition. Booted up for me.
Click to expand...
Click to collapse
Sorry, can you clarify your last bit about selecting the other boot?

habylab said:
Did this wipe anything when you flashed the stockboot.img? Just data or internal too?
Nothing was wiped. All data remain in place.
Click to expand...
Click to collapse