Database Info

Nexus 5 with "TeamWin" failed update - and won't start again

Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!

Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.

Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.

if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.

simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.

I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.

Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.

simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?

How to uninstall twrp?

It's an lg g3 on lollipop. Basically I want to remove all root and custom recovery from my phone.By I don t want to lose all settings and data and hours of configuring the phone the way I like it. So don't tell me how to flash stock Rom back on phone. I know that. I want to remove twrp without messing anything up on phone. Is this possible.

Are you not able to reflash a stock bootloader. You can then unroot by using SuperSU in its settings page.
Hope this helps a little.

Agent_Sm1th said:
Are you not able to reflash a stock bootloader. You can then unroot by using SuperSU in its settings page.
Hope this helps a little.
Click to expand...
Click to collapse
Does reflashing the boot loader reset and erase phone? If not how do I do it in detail please. I already unrooted super su. But still stuck with twrp.

Flashing a recovery doesn't wipe the phone. Just like if you flash cwm over twrp for example, your phone wouldn't wipe it'd just boot to cwm recovery instead of twrp. You'll need to search for your phones stock one.

On the Galaxy Note 4 I would flash a PDA file with the bootloader CSC etc that's all Stock. It would be a tar file and I would flash this using Odin. I believe this is only on Samsung though. Not sure how it is done for LG but I can imagine it's similar. You could attempt to flash everything stock using your computer I believe but I am not sure as this only applies to Samsung devices. But you get the idea, perhaps a Google search can further help you though! Hope this helped √
Sent from my SM-N910T using Tapatalk

Agent_Sm1th said:
Flashing a recovery doesn't wipe the phone. Just like if you flash cwm over twrp for example, your phone wouldn't wipe it'd just boot to cwm recovery instead of twrp. You'll need to search for your phones stock one.
Click to expand...
Click to collapse
I can't seem to find it. Could use some help. My phone is lg g3 d850 att. Running 5.0.1
I need the stock recovery to flash using flashify

AndrewG1299 said:
I can't seem to find it. Could use some help. My phone is lg g3 d850 att. Running 5.0.1
I need the stock recovery to flash using flashify
Click to expand...
Click to collapse
I'll have a look, but can't promise anything as I use an S4. I flash stock recovery via Odin on the PC or custom via cwm or twrp.
---------- Post added at 06:35 PM ---------- Previous post was at 06:29 PM ----------
I can only find stock firmware. Unfortunately this will wipe your phone if you flash it.
Is there no one who can advise you in the lg parts of these forums.
Here's the link to the stock firmware. Careful you pick the right one.
http://lgg3root.com/lg-g3-stock-factory-firmware/

I know about that but I need the recovery so I don't erase phone

Yeah I know it'll wipe it. Just thought in case you decided to fresh install. It doesn't take that long really to set back up even if you do go down that route.

After Custom Recovery OTA and Recovery-flashable Incrementals Don't work

I've had the OPO for over a year, and just now had the need to root it. An OTA happened to come in the next day, and the update process didn't work as I expected. So I'd like to know if I did something wrong, a random problem occurred, or this is the way it's supposed to work.
Until a couple days ago, the OPO was stock + all OTAs that had been released. I unlocked the bootloader, installed TWRP recovery, and installed SuperSU. All that went as expected. When the OTA notification arrived the next day, I tried to install it with "Update Cyanogen recovery" still unchecked (because original reports with CM 11S said you could keep your custom recovery with an OTA).
When I tried to install the update, the phone just rebooted to TWRP and the update was not stored anywhere on /sdcard. I then checked "Update Cyanogen recovery" and tried to install the OTA again. It did not install, and TWRP was still my recovery. Several repeats of this had no different result.
Then I flashed the stock CM recovery with fastboot. After verifying I had the CM recovery, I installed the OTA again, and it failed again, reboting to recovery and doing nothing else. Then I downloaded the incremental update and tried to flash that via CM recovery, and that failed too. I checked the file /System/build.opt, and line "ro.build.version.incremental" said 49d90510ef, which meant I should have been able to install the cm-bacon-49d90510ef-to-d91bf047f5-signed.zip file. But it failed and said the current build number was not as expected. The number it gave me was not anything that made sense looking at the list of recent incremental updates.
So at that point I bailed out and installed via recovery the full flashable zip file, and that worked.
If this is what I have to do each time, it's certainly doable, but I don't think this is how it's supposed to go. I'm surprised the OTA didn't work with the custom recovery installed, and I'm even more surprised that the incremental installation failed. Maybe trying to install the OTA without updating the CM recovery messed things up, but that doesn't seem likely either. When the next OTA comes out, I'll see if any of these troubles are repeated. But I'd like to know how the OTA was supposed to work after installing a custom recovery.

I am still yet to figure this one out also, my friend I'm sure with time someone will respond who had better experience with this; just be patient
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava

Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs

Check the CyanogenMod website, @distante

vince.lupe said:
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Click to expand...
Click to collapse
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.

distante said:
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Click to expand...
Click to collapse
This thread with Cyanogen mirrors and info has exactly what you need.

MidnightJava said:
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
Click to expand...
Click to collapse
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/

vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.

Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?

Cholerabob said:
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
Click to expand...
Click to collapse
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.

MidnightJava said:
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Click to expand...
Click to collapse
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Cholerabob said:
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Click to expand...
Click to collapse
I did do both :/

MidnightJava said:
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
Click to expand...
Click to collapse
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
vince.lupe said:
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
I did do both :/
Click to expand...
Click to collapse
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.

Cholerabob said:
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Click to expand...
Click to collapse
Yes, bootloader is unlocked and SuperSu was reinstalled :/

[G930F][Nougat] Installing TWRP or rooting resulting in eternal flashing Samsung logo

Hey,
So yesterday I decided to flash the BTU Nougat 7.0 firmware to my EE S7 and all went well and the device booted normally, after this I tried to install TWRP onto my device which also went well, I installed the no-verify zip (or whatever it's called) and tried to boot the phone and I was just greeted with the flashing Samsung logo for an hour, after this I used Odin to flash my phone back my phone to the BTU nougat ROM and everything was fine, later I tried to use CF-Auto-Root which once again resulted in the flashing Samsung logo, I also tried wiping my data with TWRP and booting but to no use, same error occurred. Can anyone help, really I only need TWRP as I just want Google assistant (Yes I know, probably not worth tripping the KNOX for but I want it) and for this I just need to install a zip file.
Thanks!
EDIT: Fully resolved, just installed the Superman ROM and all is well. Thanks for the help!

Using the latest version of ODIN?
Any older than 3.12.3 cause problems

*Detection* said:
Using the latest version of ODIN?
Any older than 3.12.3 cause problems
Click to expand...
Click to collapse
Yeah I'm using 3.12.3

tbh to make things less hassle download any custom roms avail and used it. i gave up when i had the same issues as yours or maybe slightly worse losing my IMEI and baseband too. did install twrp to the cm14.1 rom and now using superman rom's everything was fine root is there too.
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
but if you still insist on using the stock rom with just root what i can suggest u to do is turn off that oem lock in the settings and enable usb debugging. 1) Odin flash your twrp.zip files 2) Download supersu.zip or any rootable zip files 3) and extra modifications/tweaks you wanna add in such as the no-verify thingy 4) Always download your stock original firmware in case you messed it up.

MxFadzil92 said:
tbh to make things less hassle download any custom roms avail and used it. i gave up when i had the same issues as yours or maybe slightly worse losing my IMEI and baseband too. did install twrp to the cm14.1 rom and now using superman rom's everything was fine root is there too.
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
but if you still insist on using the stock rom with just root what i can suggest u to do is turn off that oem lock in the settings and enable usb debugging. 1) Odin flash your twrp.zip files 2) Download supersu.zip or any rootable zip files 3) and extra modifications/tweaks you wanna add in such as the no-verify thingy 4) Always download your stock original firmware in case you messed it up.
Click to expand...
Click to collapse
Thanks for the tip mate, I'll have a look at some custom ROMs for my phone tomorrow, I used to use CM14 on my s5 so CM shall be my first choice I think

did you try formating data in twrp?
you will loose your data but that should fix it.

munchy_cool said:
did you try formating data in twrp?
you will loose your data but that should fix it.
Click to expand...
Click to collapse
Yeah I've already tired that

Pixel rooted with Supersu, TWRPd and using EX kernel.

Was wondering if FlashFire will Auto install OTA updates?

Auto update dont work on unlocked bootloader phone

Can I download update and flash it with FlashFire? I read XDA post someone did it with Nexus and FlashFire restored stock boot and recovery installed OTA zip then restored TWRP and boot.

ayeros said:
Auto update dont work on unlocked bootloader phone
Click to expand...
Click to collapse
Unlocked bootloader by itself won't stop the OTA.
---------- Post added at 04:41 PM ---------- Previous post was at 04:38 PM ----------
Bulauski2005 said:
Can I download update and flash it with FlashFire? I read XDA post someone did it with Nexus and FlashFire restored stock boot and recovery installed OTA zip then restored TWRP and boot.
Click to expand...
Click to collapse
You can install it via TWRP or FlashFire. You will have to probably redo EX and root afterwards. But I dont bother trying to shortcut it anymore. I use flashall with the -w removed, then reapply my mods. Its clean and easy.

It appears there is a timing issue with the pixel when entering TWRP. Also with restoring backup. I'm using RC1 on stock NOF26V Supersu and have Weta audio mod with EX kernel. My device is running smooth as butter. I have a backup with RC1 and would like to try other Roms but I'm afraid to test the restore function at this time in fear of messing it up. Any advice?

Bulauski2005 said:
It appears there is a timing issue with the pixel when entering TWRP. Also with restoring backup. I'm using RC1 on stock NOF26V Supersu and have Weta audio mod with EX kernel. My device is running smooth as butter. I have a backup with RC1 and would like to try other Roms but I'm afraid to test the restore function at this time in fear of messing it up. Any advice?
Click to expand...
Click to collapse
I've backed up and restored many times without any issues other than the first time when I backed up system, data and vendor. It all restored ok but it lead to huge battery drain once the phone was booted up. I'd get a bit more than 6 hours and the battery would be dead. To avoid that, backup system image, data image and vendor image. I've never had a problem with restores backing up those three.

Did you use RC1 or alpha?

Bulauski2005 said:
Did you use RC1 or alpha?
Click to expand...
Click to collapse
RC1

OK because I watched a video on androidexplained and he said to backup and restore all partitions?

Thanks alot I'll try the image backup.

When restoring a backup with TWRP do I need to switch slots? Backup A and restore to B?

Bulauski2005 said:
When restoring a backup with TWRP do I need to switch slots? Backup A and restore to B?
Click to expand...
Click to collapse
No. Just boot to TWRP and restore the backup.

Just to make sure I'm on the same page. Restore system image, vendor image and data? That's it Right?

Bulauski2005 said:
Just to make sure I'm on the same page. Restore system image, vendor image and data? That's it Right?
Click to expand...
Click to collapse
Yes.

Am I able to relock pixel bootloader and unlock it after mods? I'm using the skipsoft tool.

Is there any way to remove or replace the pixel bootloader warning screen?

Bulauski2005 said:
Am I able to relock pixel bootloader and unlock it after mods? I'm using the skipsoft tool.
Click to expand...
Click to collapse
Only if it is 100 percent stock, but don't. Lots of folks have bricked themselves trying. Don't do it unless it is the last thing you are doing before sending it back for warranty.
---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------
Bulauski2005 said:
Is there any way to remove or replace the pixel bootloader warning screen?
Click to expand...
Click to collapse
No, not possible.

Bulauski2005 said:
Is there any way to remove or replace the pixel bootloader warning screen?
Click to expand...
Click to collapse
Not now. Possibly not ever but we'll see.

Does anyone know if I can activate the skipsoft toolkit from multiple computers with the pro ultimate activation code?

I just bought a new computer but the toolkit will not activate.