Root TWRP Bootloop fix after update/OTA

[HasH_BrowN]

I'm officially on android 5.02! At last! It took me some time and had to reset to factory, but that is a minor issue. Also I found out what caused the softbrick yesterday. Flashify was failing to install the stock recovery. It failed again today. You guys can imagine my shock when I saw fastboot menu again. Anyway, I manage to install the stock recovery with adb, following HasH_BrowN's instructions (see how many things you taught me?). The update took place smoothly.

I'd like to thank everyone again for your help and patience. Saved my bacon!

You are most welcome!!
Glad its up and running. Lets us know if you need help again.

 

[knghcm]

I have TWRP but don't know what a Terminal Emulator is or know how to start one up from TWRP. What should I do?

 

[HasH_BrowN]

@knghcm
Boot to recovery
Tap advanced
Tap terminal
If it shows a browser, tap select (bottom right corner
Type in commands
Wait for each one to finish
Reboot and enjoy.

 

[knghcm]

@knghcm
Boot to recovery
Tap advanced
Tap terminal
If it shows a browser, tap select (bottom right corner
Type in commands
Wait for each one to finish
Reboot and enjoy.

When I go to Advanced, there's an option/button called Terminal Command, and when I click on it, it just shows some kind of directory (maybe the root directory). The other buttons under Advanced are Copy Log to SD, Fix Permissions, File Manager, etc.

Is there supposed to be some file I have to flash in TWRP in order to install the Terminal Emulator? The directory that shows up suggests I have to choose a file in order to load the Terminal Command (not sure if this is the same as the Terminal Emulator).

Thank you so much for helping me.

 

[HasH_BrowN]

When I go to Advanced, there's an option/button called Terminal Command, and when I click on it, it just shows some kind of directory (maybe the root directory). The other buttons under Advanced are Copy Log to SD, Fix Permissions, File Manager, etc.

Is there supposed to be some file I have to flash in TWRP in order to install the Terminal Emulator? The directory that shows up suggests I have to choose a file in order to load the Terminal Command (not sure if this is the same as the Terminal Emulator).

Thank you so much for helping me.

Tap on terminal command
Next screen, tap the select button - in bottom right corner.

Exactly as I described before.

@knghcm
Boot to recovery
Tap advanced
Tap terminal
If it shows a browser, tap select (bottom right corner
Type in commands
Wait for each one to finish
Reboot and enjoy.

 

[knghcm]

Tap on terminal command
Next screen, tap the select button - in bottom right corner.

Exactly as I described before.

Aahhh it worked! You are a wonderful human being! I was so worried about my phone being bricked until I came across your tip.

I'm assuming with this disaster, there's no hope for future updates not bricking the phone i.e. I should not ever approve any update pushed to the phone from now on.

 

[HasH_BrowN]

Aahhh it worked! You are a wonderful human being! I was so worried about my phone being bricked until I came across your tip.

I'm assuming with this disaster, there's no hope for future updates not bricking the phone i.e. I should not ever approve any update pushed to the phone from now on.

Glad it worked!!

I don't know as far as updates, some are buggy. Like the radio.img in this update. When that happens, it doesn't mean that you shouldn't update. Try this. When an "official" update arrives, check the forum and read, read, read.

Things to look for:

• Does it work like intended?

• Did it break anything? ie. Connectivity

• If previous was yes, Can it be fixed easily?

• Does it remove user control over system? ie. Features

If you see negative comments, KEEP READING. There might be light at the end of the tunnel further in the thread. Sometimes though nothing has been posted about it yet. Don't sweat it though.

You can do 1 of 4 things:

1. Wait. Also safest, but heh we root...right?
2. Step 1 and post a question for others to respond to. Safe and shows your interest.
3. Update. Toss up between Good and Evil (bad). Shows your initiative. (disclaimer in red)
4. Step 3 and post your findings and recommendation. In the thread you create include answers to those questions I mentioned above to help others. Shows your initiative and your concern for the community.

Or you can do something else. It's really up to you. I do hope that this has helped, even in the smallest way.

Make a backup before updating or flashing files. I won't be responsible for any damages that occur to your device

 

[HasH_BrowN]

OP updated. I'm proud to announce that it now includes zips, which can be downloaded here. http://androidforums.com/resources/twrp-bootloop-fix-zip.214/
Please leave feedback, a review and also rate the resource directly at the resource page. I would greatly appreciate it.

 

[knghcm]

Glad it worked!!

I don't know as far as updates, some are buggy. Like the radio.img in this update. When that happens, it doesn't mean that you shouldn't update. Try this. When an "official" update arrives, check the forum and read, read, read.

Things to look for:

• Does it work like intended?

• Did it break anything? ie. Connectivity

• If previous was yes, Can it be fixed easily?

• Does it remove user control over system? ie. Features

If you see negative comments, KEEP READING. There might be light at the end of the tunnel further in the thread. Sometimes though nothing has been posted about it yet. Don't sweat it though.

You can do 1 of 4 things:

1. Wait. Also safest, but heh we root...right?
2. Step 1 and post a question for others to respond to. Safe and shows your interest.
3. Update. Toss up between Good and Evil (bad). Shows your initiative. (disclaimer in red)
4. Step 3 and post your findings and recommendation. In the thread you create include answers to those questions I mentioned above to help others. Shows your initiative and your concern for the community.

Or you can do something else. It's really up to you. I do hope that this has helped, even in the smallest way.

Make a backup before updating or flashing files. I won't be responsible for any damages that occur to your device

Thank you for the very insightful advice. I have a question: after I fixed the problem based on your suggestion, I don't seem to get the persistent update notification any more. Does this mean the update had been applied when I was trying to fix the problem?

I also used the instruction from this XDA post (http://forum.xda-developers.com/showpost.php?p=59566043&postcount=9) to avoid future update pushes. Do you think this is a good idea?

Thanks again for your help.

 

[HasH_BrowN]

Thank you for the very insightful advice. I have a question: after I fixed the problem based on your suggestion, I don't seem to get the persistent update notification any more. Does this mean the update had been applied when I was trying to fix the problem?

I also used the instruction from this XDA post (http://forum.xda-developers.com/showpost.php?p=59566043&postcount=9) to avoid future update pushes. Do you think this is a good idea?

Thanks again for your help.

Your welcome.

On the update notifications, easy cheesy.

Goto phone settings/apps/ then ALL tab, scroll down to Google Play Services and uncheck notifications.
Or
Wait for another update (which won't likely happen), then long press on notification, tap app info, then uncheck notifications.
Basically the same, one is just lazier.

If there is another update it most likely would be a fix for this last update.

 

[knghcm]

Your welcome.

On the update notifications, easy cheesy.

Goto phone settings/apps/ then ALL tab, scroll down to Google Play Services and uncheck notifications.
Or
Wait for another update (which won't likely happen), then long press on notification, tap app info, then uncheck notifications.
Basically the same, one is just lazier.

If there is another update it most likely would be a fix for this last update.

So should I uninstall those apps suggested in that post (Autorun Manager, DisableService) and follow what you suggested? Honestly I don't like having apps that I don't absolutely need (hence my hatred for bloatware).

PS. I went back and liked your OP, You have no idea how happy that post made me feel.

 

[HasH_BrowN]

I like MyAndroidTools Pro by Wanqi. Awesome app. It allows you to disable: services (@ boot), broadcast receivers (startups), activities (ads), content providers, and a number of other extremy useful things. You just can't go balls to the wall disabling everything. Major FC'ing. But under moderation, the app will tame your system. If you need help ask or check out the PlayStore and click on webpage towards bottom.

 

[HasH_BrowN]

PS. I went back and liked your OP, You have no idea how happy that post made me feel.

I'm glad you got that warm fuzzy feeling. I thought some humor would liven the OP up.

 

[CommandTheREAPER]

Found the solution for bootlooping to TWRP after OTA

It took all afternoon and evening to find the answer. :silly::highfive::victory:. I've got 2 simple commands to ease everyone's troubled minds. The overwhelming sense of accomplishment you'll get knowing you can use your device again. Take a step back and appreciate this moment. All joking aside, here you go.

You now have two choices. Follow the directions below or download the zip and flash in TWRP.
http://androidforums.com/resources/twrp-bootloop-fix-zip.214/ & please leave a review there.

Start up Terminal Emulator from TWRP.
*Since its showing a file browser, hit the select button - bottom right, now you can enter command lines.

*Enter commands EXACTLY as shown

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

Hit enter (return)...wait, takes a few seconds
Now input this

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc

Hit enter (return)...wait again.
When its complete, reboot.

_____
Tested and verified numerous times by myself before release.

Also as a note, you may have to reactivate your device before using data or the phone.

______
Disclaimer:
I will not be responsible for damages that occur to your device due to using the above TWRP commands.

_____
If this has helped please press LIKE, a pat on the back is always nice!

when I do this it says not enough space on device,but I have gigs of space.

 

[MTdude]

when I do this it says not enough space on device,but I have gigs of space.

Gigs.. plural? of internal space? I doubt it considering you are only allowed like 1.5 of user space on this phone. The update needs at least 500 mb of internal memory, not including any external micro sd you may have for the update.

 

[CommandTheREAPER]

O

Gigs.. plural? of internal space? I doubt it considering you are only allowed like 1.5 of user space on this phone. The update needs at least 500 mb of internal memory, not including any external micro sd you may have for the update.

Wow I thought I could just use my external.. I may have to delete some things. Feel like a noob now lol and I've been at this for a while. This is my first time having to use the emulator for anything.

 

[HasH_BrowN]

@CommandTheREAPER You shouldn't be getting space error from using the commands on terminal in TWRP. That would happen when flashing update without enough internal space like @MTdude replied.

 

[CommandTheREAPER]

A

@CommandTheREAPER You shouldn't be getting space error from using the commands on terminal in TWRP. That would happen when flashing update without enough internal space like @MTdude replied.

I had exactly 943 Mb of internal space. So I'm not really sure what's going on.

 

[CommandTheREAPER]

@CommandTheREAPER You shouldn't be getting space error from using the commands on terminal in TWRP. That would happen when flashing update without enough internal space like @MTdude replied.

thanks for the quick reply by the way every bit of info is helpful.

 

[HasH_BrowN]

thanks for the quick reply by the way every bit of info is helpful.

While in twrp, after binary error. Goto advanced tab, then tap log (top left), and then swipe to confirm. Upload the log file here, so I can try to help.
When error happens in TWRP, take screenshot. Vol- & power, its saved in Pictures/Screenshots. Upload that too.

 

[CommandTheREAPER]

While in twrp, after binary error. Goto advanced tab, then tap log (top left), and then swipe to confirm. Upload the log file here, so I can try to help.
When error happens in TWRP, take screenshot. Vol- & power, its saved in Pictures/Screenshots. Upload that too.

No need ha-ha I just fixed it. Your original method worked like a charm. I was seeing it from a device that wouldn't let me veiw all the content I was to put in the terminal emulator. It's up and working fine now the only thing is now I keep getting a notification saying system udate downloaded and it won't go away even when I hit ignore or later. This is the same udate that threw me in the boot loop to begin with. Can I get rid of it in the system files or is there a way I can update it? Which ever is easiest lol I'm on the lg tribute, but this isn't technically the stock ROM cause I lost it once and found a recovery of it from the internet with a root and some bloat missing from it.

 

[HasH_BrowN]

No need ha-ha I just fixed it. Your original method worked like a charm. I was seeing it from a device that wouldn't let me veiw all the content I was to put in the terminal emulator. It's up and working fine now the only thing is now I keep getting a notification saying system udate downloaded and it won't go away even when I hit ignore or later. This is the same udate that threw me in the boot loop to begin with. Can I get rid of it in the system files or is there a way I can update it? Which ever is easiest lol I'm on the lg tribute, but this isn't technically the stock ROM cause I lost it once and found a recovery of it from the internet with a root and some bloat missing from it.

Goto main settings>apps>all apps tab, scroll to Google Play Services. Uncheck notifications. Then you can delete the update if you want, /cache. Updating to zv6 will cause more headaches than you want. I'm still on zv5 and it is working fine. Just so you know its still 4.4.2

You can't flash the update over the "custom" rom, very unstable.

 

[CommandTheREAPER]

Thanks again man! So is there anyway I would be able to go back to out of the box again? Like I said earlier I lost all my original stock ROM data. I flashed cyanogenmod 12 unofficial and forgot to back everything up.. I thought I did but forgot to double check. Then I found this ROM (wich apparently can't receive updates lol) but its not complete like my stock one was. I had to make due with this one cause until recently there wasn't much about the ls660 on the web. Could I pehaps flash it form some provided sorce or is it more complicated than that? I really want to learn more about this. I would love to get into more detail, I just have a lot of ground to cover.

 

[HasH_BrowN]

Thanks again man! So is there anyway I would be able to go back to out of the box again? Like I said earlier I lost all my original stock ROM data. I flashed cyanogenmod 12 unofficial and forgot to back everything up.. I thought I did but forgot to double check. Then I found this ROM (wich apparently can't receive updates lol) but its not complete like my stock one was. I had to make due with this one cause until recently there wasn't much about the ls660 on the web. Could I pehaps flash it form some provided sorce or is it more complicated than that? I really want to learn more about this. I would love to get into more detail, I just have a lot of ground to cover.

IF THERE IS another update, it most likely will be a fix for this last update. We (LS660 devices) probably won't see Lollipop, unless its a custom rom. The only decent thing I saw in the update was the stagefright fix, the steps are posted somewhere on AF.
The included radio.img (the new boot img) corrupts data connectivity, which is a bunch of hooey.
It reinstalls all of the bloatware and unneeded carrier apps/software, after rebooting from installing the update the carrier update runs.

I don't have the link, but if you need the stock rom look at the rest of Tribute forum. There's a post on it.

 

[CommandTheREAPER]

IF THERE IS another update, it most likely will be a fix for this last update. We (LS660 devices) probably won't see Lollipop, unless its a custom rom. The only decent thing I saw in the update was the stagefright fix, the steps are posted somewhere on AF.
The included radio.img (the new boot img) corrupts data connectivity, which is a bunch of hooey.
It reinstalls all of the bloatware and unneeded carrier apps/software, after rebooting from installing the update the carrier update runs.

I don't have the link, but if you need the stock rom look at the rest of Tribute forum. There's a post on it.

Okay very helpful. Doesn't seem worth the trouble.. I'll just stick with what I have, its a great lay out and everything after its debloated. I have no problems with it the version its on. Kinda sucks we probably won't see lollipop though.