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.

Need help to UN-brick my phone due to frp lock... Please!

I rooted my phone last week and was surprised by the new OEM lock, A.K.A. FRP... At any rate, I rooted it and last night it froze up and when it restarted, it said Custom binary blocked by FRP and then just reboots. I have tried to flash everything and Odin will not work for anything. I can only get it to go into the download mode and then it fails. Any help?

PharQrazyR said:
I rooted my phone last week and was surprised by the new OEM lock, A.K.A. FRP... At any rate, I rooted it and last night it froze up and when it restarted, it said Custom binary blocked by FRP and then just reboots. I have tried to flash everything and Odin will not work for anything. I can only get it to go into the download mode and then it fails. Any help?
Click to expand...
Click to collapse
You must use odin version 3.10.7 only.
Here is odin v3.10.7 in case you need it:
https://www.androidfilehost.com/?fid=24052804347842132
Then odin flash the official Samsung firmware.
After the phone fully boots make sure that the oem unlock is enabled.
Never disable it.
Good luck
Have a nice evening.
Sent from my SM-G928T using Tapatalk

Misterjunky said:
You must use odin version 3.10.7 only.
Here is odin v3.10.7 in case you need it:
https://www.androidfilehost.com/?fid=24052804347842132
Then odin flash the official Samsung firmware.
After the phone fully boots make sure that the oem unlock is enabled.
Never disable it.
Good luck
Have a nice evening.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
i rooted my phone, (forgot to enable oem unlocking), was working fine but now have the same issue as above. flashed stock firmware but phone stays on "samsung" screen...

kc720 said:
i rooted my phone, (forgot to enable oem unlocking), was working fine but now have the same issue as above. flashed stock firmware but phone stays on "samsung" screen...
Click to expand...
Click to collapse
Go into recovery mode and do a factory reset.
Reboot and it should boot normally.
Good luck.
Sent from my SM-G928T using Tapatalk

Misterjunky said:
Go into recovery mode and do a factory reset.
Reboot and it should boot normally.
Good luck.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
Thank you for reply. I did do a reset and erase cache. Still stuck on samsung screen. Pm shows the phone in device manager but this is all I have. More than 15 minutes...
{
"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"
}

Did you flash a custom kernel? That was the only way I could get past this to obtain root.

[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.

Question I think i may have bricked my device help pls

Hey guys i think i may have bricked my device, i keep getting this error whenever i try to use miflash to flash back to stock rom
{
"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"
}
Does anyone know how to fix this? i keep bootlooping back into fastboot mode and whenever i try to restart system it says no os installed

Try redownloading the ROM and the latest version of Mi Flash. Reboot PC and phone.
Go to Mi Flash's Configuration and check "Verbose" and "Erase all", and remove the argument in "CheckPoint".
Also, "Clean All and Lock" is selected in the bottom right corner, keep that in mind, because it'll lock your bootloader once the Flash succeeded.
If you don't want that happening, check "Clean All".
Make sure there are no spaces in the whole ROM path, and perhaps also try a different USB port, or a different cable.
Also, plug in the USB cable after you rebooted Fastboot Mode. Fastboot Mode may stop accepting input after an initiated Flash, so to try and flash again you may need to reboot Fastboot Mode again.
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com

newbo1211 said:
Hey guys i think i may have bricked my device, i keep getting this error whenever i try to use miflash to flash back to stock rom
View attachment 5405925
Does anyone know how to fix this? i keep bootlooping back into fastboot mode and whenever i try to restart system it says no os installed
Click to expand...
Click to collapse
Lucky that it failed... Always remember to disable lock before flashing otherwise you will really brick the phone.
Try a different firmware like eea 12.5.3, that one is the only one I can confirm to be working in all circumstances

Rstment ^m^ said:
Lucky that it failed... Always remember to disable lock before flashing otherwise you will really brick the phone.
Try a different firmware like eea 12.5.3, that one is the only one I can confirm to be working in all circumstances
Click to expand...
Click to collapse
No it doesn't brick the phone. It only locks the bootloader when the flash succeeded.

dreamytom said:
No it doesn't brick the phone. It only locks the bootloader when the flash succeeded.
Click to expand...
Click to collapse
Man off my dik. Ur setting this guy up for a massive headache , yes It bricks it the phone , the hardest way possible when you have no idea what you're doing and are following advices like this. Using community tool to lock bootloader ( Your only way of interacting with this phone ) when you don't even know how the flash went is pure fkin stupidity.
Locks bootloader assuming the phone is fully functional but what if it's not? Then you can't try again , you're screwed. No flashing anymore.
CRC bypass for example like what he's having issues with will flash just fine , report 0 problems but phone doesn't boot. What if he follows one of the many guides out there , removes CRC and then goes flashing ?
Therefore your answer above is nothing but bs. Bad flash is soft brick , locking bootloader after bad flash is a much harder brick

Rstment ^m^ said:
Man off my dik. Ur setting this guy up for a massive headache , yes It bricks it the phone , the hardest way possible when you have no idea what you're doing and are following advices like this. Using community tool to lock bootloader ( Your only way of interacting with this phone ) when you don't even know how the flash went is pure fkin stupidity.
Locks bootloader assuming the phone is fully functional but what if it's not? Then you can't try again , you're screwed. No flashing anymore.
CRC bypass for example like what he's having issues with will flash just fine , report 0 problems but phone doesn't boot. What if he follows one of the many guides out there , removes CRC and then goes flashing ?
Therefore your answer above is nothing but bs. Bad flash is soft brick , locking bootloader after bad flash is a much harder brick
Click to expand...
Click to collapse
No, I agree that he shouldn't accidentally lock his bootloader.
However, choosing to lock the bootloader in Mi Flash won't brick the device.
The command for locking the bootloader comes only at the end.
If any errors occur before that, the script will terminate.
If any of the commands prior to "fastboot oem lock" don't execute successfully, it simply will not lock the BL.
The .bat-files are the logic behind the Flashing-process in Mi Flash.
It's not necessary to use Mi Flash. You could use the naked .bat-files, but I wouldn't recommend it. Mi Flash provides additional info.
About removing the CRC commands to skip CRC errors: I don't have a ROM on my drive to check what those exact commands are, but it's probably not recommended.
I think it's only safe to remove the Anti-Rollback Commands.
I do agree that there's a lot of misinfo out there, and that you need to be careful.