Develop Bugs

Stuck at boot loop. White Amazon Logo

Hi guys,
I was in the final step (7) of this gude: http://www.aftvnews.com/start/
Which is installing the latest pre-rooted stock software, (version 51.1.4.1_514013920) After pushing the rom to /sdcard, I rebooted the device so that I could flash it via clockworkmod recovery, but I was not able to select the recovery option with my keyboard. So I decided to re-do the installation of Rbox's kernel boot menu. Now, I'm stuck at a boot loop with just the white Amazon logo showing up. Is my device bricked and is there a way to fix it?

FYI I cannot access clockworkmod recovery. I wish I could, as I would then be able to flash the latest pre-rooted ROM that's in /sdcard
Does anyone know how I can access recovery?

Newbie_from_NJ said:
FYI I cannot access clockworkmod recovery. I wish I could, as I would then be able to flash the latest pre-rooted ROM that's in /sdcard
Does anyone know how I can access recovery?
Click to expand...
Click to collapse
You need cwm 6.0.5.1.4 or higher AND unlocked boot loader or you will brick it. If this is your situation believe me I hope I'm not the bearer of bad news. Hopefully you'll be ok. Good luck!

KLit75 said:
You need cwm 6.0.5.1.4 or higher AND unlocked boot loader or you will brick it. If this is your situation believe me I hope I'm not the bearer of bad news. Hopefully you'll be ok. Good luck!
Click to expand...
Click to collapse
I have all that. Box came with 51.1.1.0_user_511070220. Here are the steps I did:
1. Rooted & install busybox and blocked updates
2. Downgraded to version 51.1.0.2_user_510058520
3. Rooted again
4. Unlocked Bootloader
5. Installed Clockworkmod recovery 6.0.5.1.4a
6. install Pre-Rooted Stock ROM version 51.1.4.0_514006420 updated via Clockworkmod recovery
7. Installed Busybox
8. Installed Kernel Boot menu
9. pushed to sdcard the latest pre-rooted stock software, version 51.1.4.1_514013920
10. Rebooted box, but here is when I realized I could not select recovery option from boot menu using my keyboard.
11. I decided to try and reinstall the boot menu. I followed the same steps I did in #8.
12. Stuck at boot loop with white Amazon Logo.

In hindsight, now that I've reviewed each step, what I should have done was flashed Pre-Rooted Stock ROM version 51.1.4.0_514006420 AGAIN via Clockworkmod recovery in order to properly uninstall the kernel boot menu. Then I should have tried re-installing the kernel boot loader again. Lesson learned.

Newbie_from_NJ said:
I have all that. Box came with 51.1.1.0_user_511070220. Here are the steps I did:
1. Rooted & install busybox and blocked updates
2. Downgraded to version 51.1.0.2_user_510058520
3. Rooted again
4. Unlocked Bootloader
5. Installed Clockworkmod recovery 6.0.5.1.4a
6. install Pre-Rooted Stock ROM version 51.1.4.0_514006420 updated via Clockworkmod recovery
7. Installed Busybox
8. Installed Kernel Boot menu
9. pushed to sdcard the latest pre-rooted stock software, version 51.1.4.1_514013920
10. Rebooted box, but here is when I realized I could not select recovery option from boot menu using my keyboard.
11. I decided to try and reinstall the boot menu. I followed the same steps I did in #8.
12. Stuck at boot loop with white Amazon Logo.
Click to expand...
Click to collapse
Then I don't know...I always double or triple check to make sure but your steps seem correct. Was this a new box? I only say that because I remember that super tedious process and at one point I think I needed to root again. At that point it maybe possible an update could sneak through but that would probably result in losing root--worst case. Not a brick.
It's concerning because you seem to know what you're doing and were cautious during the process.
Hopefully someone else can confirm where you went wrong. If you didn't go wrong then that might be a bigger problem. Everything went smoothly up until it hung at boot?

As they always say, if your in a jam and get "failed" messages when writing to boot or recovery or flashing, do not reboot. keep trying till you get no errors. that said, I thought I was stuck in a boot loop cause I insalled the llama and xbmc launcher and removed the launcher app. I was still able to get through adb but it took like 5 or 6 reboot tries. good luck.

SOLVED: Can't boot past bootloader/recovery after installing SuperSU (Moto G)

Hi, I have a Moto G (3rd gen.).
I successfully unlocked the bootloader and installed TWRP.
The OS booted and worked fine after this.
Then, to root, I installed SuperSU v2.65 via TWRP, and rebooted.
I used this file:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
After that the phone does not boot past the screen with "Warning, bootloader unlocked".
I can get into recovery and TWRP, and ADB/FastBoot connects to the phone.
What can I do to save/restore my phone from here?
Do I need to flash a clean stock image, or can I fix the current state somehow?
EDIT: solved, by flashing cyanogenMod on it.

Unable to boot after unlocking bootloader and installing TWRP

Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?

chinhodado said:
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
Click to expand...
Click to collapse
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.

I actually solved this myself before k23m's reply by flashing the stock rom (MOB30X), then completed the initial setup, then reflashed TWRP (twrp-3.0.2-0-flo.img, not the multirom version). After that I booted up then restarted into recovery but then realized that TWRP had been wiped (only the android with the red triangle showing). So I re-flashed TWRP again and this time rebooted directly into recovery, and renamed the file recovery-from-boot.p into recovery-from-boot.backup. Then I flashed su and all went well.

k23m said:
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
Click to expand...
Click to collapse
Thank you for the hint!

Help with TWRP please

Hello,
I have a nexus 7 2013 and have just flashed twrp 3.0.2-0 recovery and have a problem.
I used adb to go to bootloader, and then unlocked it
flashed recovery image then used fastboot reboot.
tablet starts, shows teamwin startup page, goes to screen "Running openrecovery script"
then after a few seconds reboots and then the whole process repeats.
any ideas?

ok, so here is how i fixed it.
extracted recovery.img from the stock image (MOB30X) and reflashed it to the device, restarted and set up as new.
reflashed TWRP and it restarted ok.
have since flashed Nougat rom and gapps (so far so good).

Lost root. How do I regain it?

Hi guys it's been a while since I've rooted any devices but decided to root my LG G PAD 8.3 (V500), since it is so outdated. I'm gonna go over exactly what I did on how I got here to better understand. Sorry in advance for the long winded post.
-Anyway, I had to downgrade to 4.2.2 by using the LG Flash Tool 2014.
-Then, I rooted my device by running root.bat Also, I had SuperSU when I rooted.
-After rooting, I installed TWRP via the play store, downloaded the most recent twrp.img and flashed it via the app. It took me forever to get to recovery by pressing power+volume down and then pressing power+volume down+volume up. But after what felt like 20+ tries, I got to TWRP recovery.
-I wiped my phone and flashed the most recent Lineage ROM. Unfortunately, after flashing the ROM, I could not flash GApps because it rebooted to the ROM after flashing. TWRP let me know that I had to update TWRP and since I did not have the play store and I was once again having trouble getting into recovery, I downloaded the most recent TWRP apk.
-When trying to open the apk, it gave me a "can't open file" message which I didn't understand why. After rebooting, for some reason, it then let me run the TWRP apk and installed the TWRP app. This is when I found out that I was no longer rooted because TWRP notified me. I double checked with root checker and indeed I was no longer rooted. I have no idea when or how that happened.
-Again, I couldn't get into TWRP recovery until I plugged in my phone to my PC and for whatever reason, it helped me get into recovery. I wiped the phone and proceeded to flash Lineage and GApps.
-I read that by flashing SuperSu I may regain root, so downloaded an updated SuperSu, went into recovery and flashed SuperSu. When rebooting, the LG screen came up with a message at the top left corner reading "secure booting error! Boot certification verify". At that point, I was in a bootloop and had to go into recovery, wipe and flash again minus supersu. So I am now on Lineage with GApps and no root.
How do I regain root? And anyone know how I was able to lose it? Back in the day when I was into flashing, I never had these problems and never lost root out of nowhere like this.
Also, if I wanted to get back to stock LG 4.2.2, how would I go about that? I know that currently, I can't use the LG Flash Tool 2014 because my current ROM does not have a USB Software option in order for the tool to recognize the tablet.
Any help would be greatly appreciated, thank you.