Develop Bugs

Why is my device bootlooping after installing TWRP?

So the first thing I did after getting my new Flo was to use the standard OTA update to bring it up to 4.4.4, then unlock the bootloader, and flash TWRP 2.8.0.1. The recovery flashed fine, but take a look at the TWRP log every time I boot into it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is going wrong? If I try to boot back to the stock ROM it just bootloops. Any help is greatly appreciated.
Thanks!

Anyone? I just realized something else that seems odd. When I reboot into recovery (holding down the power button and the volume down button) it doesn't boot into recovery, it boots into fastboot mode. Is this something unique to the N7 or is it part of the device being screwed up?
Thanks.

It's normal that Power/Vol- will bring you to the bootloader first, and from there you can choose to go into recovery.
Something probably happened with the OTA update. Try downloading the factory image (ROM plus recovery) and flashing that. Then you can try flashing a custom recovery again.
https://developers.google.com/android/nexus/images
Just to make sure, you got TWRP from here, right?
http://techerrata.com/browse/twrp2/flo

Pandae said:
It's normal that Power/Vol- will bring you to the bootloader first, and from there you can choose to go into recovery.
Something probably happened with the OTA update. Try downloading the factory image (ROM plus recovery) and flashing that. Then you can try flashing a custom recovery again.
https://developers.google.com/android/nexus/images
Just to make sure, you got TWRP from here, right?
http://techerrata.com/browse/twrp2/flo
Click to expand...
Click to collapse
Thanks for the tip, and even more for linking me straight to it. I really appreciate it.
And yeah I got the recovery straight from TWRP's site, and tried flashing a few different versions numerous times.
I'll try this as soon as I get off work and report back; thanks again.

Pandae said:
It's normal that Power/Vol- will bring you to the bootloader first, and from there you can choose to go into recovery.
Something probably happened with the OTA update. Try downloading the factory image (ROM plus recovery) and flashing that. Then you can try flashing a custom recovery again.
https://developers.google.com/android/nexus/images
Just to make sure, you got TWRP from here, right?
http://techerrata.com/browse/twrp2/flo
Click to expand...
Click to collapse
You're the man! Working perfectly now; re-installed TWRP and rooted no problem. Must have had some sort of issue with the OTA update as you mentioned. Thanks a ton.

Excellent, I'm glad to hear! :good: I had such bad luck upgrading a long time ago to 4.2.2 (soft-bricked my original N7), and since then I don't do any more Android upgrades, only full flashes.

From ViperOne to bricked. How to fix it?

I've got a M8 with ViperOne and the ROM was working well. But I was going to sell my phone, and the buyer wanted stock ROM, so I connected my phone to my computer via USB, set it in fastboot and typed "fastboot oem lock" and afterwards I haven't been able to either get it to stock or turn it on again. It's stuck in that fastboot mode. How is that fixed? Either going back to ViperOne ROM or getting stock ROM would be well.
Here's what I typed in CMD with the phone tethered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's my phone afterwards.

blau77 said:
I've got a M8 with ViperOne and the ROM was working well. But I was going to sell my phone, and the buyer wanted stock ROM, so I connected my phone to my computer via USB, set it in fastboot and typed "fastboot oem lock" and afterwards I haven't been able to either get it to stock or turn it on again. It's stuck in that fastboot mode. How is that fixed? Either going back to ViperOne ROM or getting stock ROM would be well.
Here's what I typed in CMD with the phone tethered.
Here's my phone afterwards.
Click to expand...
Click to collapse
Use on customer rom and type fastboot oem lock, that why you stuck at bootloader
Try to unlock bootloader again, then use ruu go back to stock rom, then lock bootloader

blackbuffalo said:
Use on customer rom and type fastboot oem lock, that why you stuck at bootloader
Try to unlock bootloader again, then use ruu go back to stock rom, then lock bootloader
Click to expand...
Click to collapse
Thank you! I've managed to get it up and going again.

blackbuffalo said:
Use on customer rom and type fastboot oem lock, that why you stuck at bootloader
Try to unlock bootloader again, then use ruu go back to stock rom, then lock bootloader
Click to expand...
Click to collapse
he is having a s-on phone.
blau77 said:
I've got a M8 with ViperOne and the ROM was working well. But I was going to sell my phone, and the buyer wanted stock ROM, so I connected my phone to my computer via USB, set it in fastboot and typed "fastboot oem lock" and afterwards I haven't been able to either get it to stock or turn it on again. It's stuck in that fastboot mode. How is that fixed? Either going back to ViperOne ROM or getting stock ROM would be well.
Here's what I typed in CMD with the phone tethered.
Here's my phone afterwards.
Click to expand...
Click to collapse
your bootloader is relocked . tried flashing RUU via sd card method . RUU cant be flashed on unlocked bootloader .
Sent from my MotoE2(4G-LTE) using Tapatalk

[Q] Need Help! Soft brick with Screen resolution and FRP lock

I install Android 7.0 custom ROM on my S6 Sprint, and I change screen solution to 1280*720.
I get an FRP lock after I restart my phone, I can't open a phone or access to recovery mode.
I download and install latest stock ROM from sammobile.com via Odin 3.12.5,
but It boot loop after show big Samsung logo on wrong screen resolution.
Now, I can open Download mode. I try to fix screen resolution by ADB commands but doesn't work.
It can't find a phone in download mode .:crying::crying::crying:
Thank you for helping me! :laugh:

First off, make sure that your phone is an SM-G920P. Then get the latest TAR file from my thread here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Be sure to check the MD5 (instructions in the thread on how to do that. Sometimes the downloads from Sammobile are incomplete or corrupted. Flash that with Odin.

koop1955 said:
First off, make sure that your phone is an SM-G920P. Then get the latest TAR file from my thread here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Be sure to check the MD5 (instructions in the thread on how to do that. Sometimes the downloads from Sammobile are incomplete or corrupted. Flash that with Odin.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It still has big Samsung logo.
I'm sorry for creating a thread in the wrong category. I just see that.

If you have been able to flash the TAR, try going into Recovery and doing a factory reset.

koop1955 said:
If you have been able to flash the TAR, try going into Recovery and doing a factory reset.
Click to expand...
Click to collapse
I'm not able to flash recovery.

It looks like your phone is an Edge, SM-G928P. Is that correct? If that is the case, that is why you can't flash the firmware. Have you tried flashing this: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G928P/

koop1955 said:
It looks like your phone is an Edge, SM-G928P. Is that correct? If that is the case, that is why you can't flash the firmware. Have you tried flashing this: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G928P/
Click to expand...
Click to collapse
My phone is 920P. It look like 928 because it have slash line in zero

nutgothic said:
My phone is 920P. It look like 928 because it have slash line in zero
Click to expand...
Click to collapse
Okay, at least then we have the right firmware.
You did download the Nougat firmware from my thread, and checked the MD5? Is it still failing for you in Odin? If that is the case, not sure what to tell you.

koop1955 said:
Okay, at least then we have the right firmware.
You did download the Nougat firmware from my thread, and checked the MD5? Is it still failing for you in Odin? If that is the case, not sure what to tell you.
Click to expand...
Click to collapse
Your firmware is work good while install. when phone start, it show big Samsung in the wrong resolution(First picture)
I tried to open recovery mode and flash recovery by Odin, but it doesn't work because FRP lock.(Second picture)
I think I have to buy a new phone. :crying::crying::crying:

nutgothic said:
Your firmware is work good while install. when phone start, it show big Samsung in the wrong resolution(First picture)
I tried to open recovery mode and flash recovery by Odin, but it doesn't work because FRP lock.(Second picture)
I think I have to buy a new phone. :crying::crying::crying:
Click to expand...
Click to collapse
If that firmware installed, then you can get to recovery either by powering down (shut off) and then holding Volume Up, Home and Power. Or by using ADB. Don't try to flash anything other than the firmware through Odin. In Recovery, select Factory Reset.
Look at this: https://www.digitaltrends.com/mobile/how-to-factory-reset-galaxy-s6/
See the second option.

Thank you. everything works great!!!

nutgothic said:
Thank you. everything works great!!!
Click to expand...
Click to collapse
That is GREAT! So glad that we were able to get you sorted out and thanks for letting us know.

[HELP] SM-A520 stuck in Bootloader after trying to unbrick by installing Stock Rom

Hey guys, my Phone is stuck in the Bootloader after trying to install the Stock Rom with Odin.
I had to try to unbrick it because I wanted to unlock FRP and at least everything I tried has failed.
The last method I tried, bricked the Phone and now it's stuck in the Bootloader despite flashing the Stock Rom with Odin.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help, I don't now what to do anymore...

Hifty said:
Hey guys, my Phone is stuck in the Bootloader after trying to install the Stock Rom with Odin.
I had to try to unbrick it because I wanted to unlock FRP and at least everything I tried has failed.
The last method I tried, bricked the Phone and now it's stuck in the Bootloader despite flashing the Stock Rom with Odin.
Please help, I don't now what to do anymore...
Click to expand...
Click to collapse
Does Odin say the operation succeded? I think you just need to restart the phone lol

Baseminge said:
Does Odin say the operation succeded? I think you just need to restart the phone lol
Click to expand...
Click to collapse
Yes, the process got no problem, Odin said succeded.
I already tried restarting the phone multiple times... for example the phone stays in Bootloader for over an hour at the moment.

Hifty said:
Yes, the process got no problem, Odin said succeded.
I already tried restarting the phone multiple times... for example the phone stays in Bootloader for over an hour at the moment.
Click to expand...
Click to collapse
For "bootloader" you mean download mode or what? Cause I cannot see anything in your "this my screen now". Try to resent pic

Baseminge said:
For "bootloader" you mean download mode or what? Cause I cannot see anything in your "this my screen now". Try to resent pic
Click to expand...
Click to collapse
I mean the pre-boot screen, where the where model name, powered by android and so on stands.
https://imgur.com/a/eDI8PNr

Hifty said:
I mean the pre-boot screen, where the where model name, powered by android and so on stands.
https://imgur.com/a/eDI8PNr
Click to expand...
Click to collapse
Ok, It's download mode. I think you just need to press and hold vol- and power button simultaneously and when screen come black, waiting for the boot.
If won't work:
-Check you downloaded the correct firmware for your phone
-It's recommended to use Odin v3.13.1 and UNTICK auto-reboot
-Try to restart first in recovery and boot phone by recovery

Baseminge said:
Ok, It's download mode. I think you just need to press and hold vol- and power button simultaneously and when screen come black, waiting for the boot.
If won't work:
-Check you downloaded the correct firmware for your phone
-It's recommended to use Odin v3.13.1 and UNTICK auto-reboot
-Try to restart first in recovery and boot phone by recovery
Click to expand...
Click to collapse
Well, at first I took the newest Firmware Update, could it help to install an older version?
And how do I restart the Phone safely after installing the stock rom?

Hifty said:
Well, at first I took the newest Firmware Update, could it help to install an older version?
And how do I restart the Phone safely after installing the stock rom?
Click to expand...
Click to collapse
Now it seems to be stuck in Bootscreen...

LG G3 TWRP Trouble

I've gotten myself into some trouble.
I managed to flash TWRP onto my LG G3 after rooting it but I seem to have flashed the incorrect TWRP variant because when I go to flash ROMs I get error 7 which if I'm not mistaken means the ROM doesn't match the phone/TWRP variant. I already wiped the phone of its LG software so I can't enter the phone that way and I can't get TWRP to flash through download mode (if you even can), and I also can't get my computer to see the phone through ADB Sideload via TWRP.
I have no idea what to do, at the moment, the phone may as well be bricked.

JesseJames1836 said:
I've gotten myself into some trouble.
I managed to flash TWRP onto my LG G3 after rooting it but I seem to have flashed the incorrect TWRP variant because when I go to flash ROMs I get error 7 which if I'm not mistaken means the ROM doesn't match the phone/TWRP variant. I already wiped the phone of its LG software so I can't enter the phone that way and I can't get TWRP to flash through download mode (if you even can), and I also can't get my computer to see the phone through ADB Sideload via TWRP.
I have no idea what to do, at the moment, the phone may as well be bricked.
Click to expand...
Click to collapse
Is the phone booting up into system? i.e. do you have a working ROM on the phone? If so, you could try flashing a recovery using either of the two apps Rashr or Flashify. If you don't have a working system but since you can enter download mode, you could just flash the stock ROM which comes with stock recovery which will replace the one you flashed and you can start over...

The latter is possible though I'd like to avoid it if at all possible. xD

Putting android 4.4.2 back on it and to point it out, the software indicates D852 while the body of the device has imprinted on it D850, so I'm not sure what it REALLY is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have put TWRP for D850 on the phone and when I try to boot to it I get [10490] Fastboot mode started.
Again, not sure what to do.

I have put TWRP for D850 on the phone and when I try to boot to it I get [10490] Fastboot mode started.
Again, not sure what to do.

Haha, I ended up bricking it or something. BSOD.