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 :/
Related
Ok, I looked , didn't see this problem.
In reading the posts this morning I see the ATT update is out. Did some reading and tried the zip in a post, didn't install
I read some more and found another post Originally Posted by ThrasherSC2K2
Yes S-OFF and Bootloader Unlock is still in place after JB OTA.
I wanted a clean install and also could not flash the OTA with TWRP installed, so here is how I did it:
- Re-locked Bootloader
- Applied 2.20 RUU
- Unlocked Bootloader (did it here in case the new hboot would not accept unlocktoken)
- Started Phone (disabled Fast Boot option);
- "Check for software update" (Had to do this a couple of times alternating with doing a "factory reset" because the server would not find an update)
- Downloaded and applied OTA
- Reboot into Bootloader and confirmed S-OFF+Unlock in place
- Flashed TWRP via fastboot
- Flashed Super SU via TWRP
- Reboot and have working JB on phone.
Before: Stock 2.20 RUU with Root , S-OFF , HBOOT: 1.14 and Radio: 0.19as.32.09.11_2
After OTA: 3.18.502.6 OTA with Root, S-OFF, HBOOT: 2.14 Radio: 0.24p.32.09.06_10.130.32.34
As confirmed in my previous post: HBOOT and Radio were upgraded.
I followed these directions and no install
This is what I have:
unlocked
S-OFF
RUU 2.20
I tried relocking and install from TWRP , no install, fails
I tried reunlockng and install from TWRP no install, fails
I tried flashing from ADB , fails
cleared cache
factory reset
all the same thing , no install, all fails
Every time I reboot to 2.20 it says I have a system updates and downloads to the SD card, its downloaded about 6 times and every time I try to install it fails.
what am I doing wrong ?
So what do you want to do? Why'd you even do the ota if you were going back to 2.20..man I don't get it
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
If you want to do the 2.20 you must have s off just relock than run the exe file from your comp
a box of kittens said:
So what do you want to do? Why'd you even do the ota if you were going back to 2.20..man I don't get it
Click to expand...
Click to collapse
If you are on a custom ROM, often you will not be able to download the OTA. Also, root (and possibly unlocked bootloader) can interfere with an OTA downloading or properly installing.
The method he mentions (originally posted here) is just a way to get back to stock, and allow the OTA to come through and install properly.
That said, I don't know what is causing the OP's issue.
Maybe my reading comprehension is on a all time low..but doesnt it say he ruud back to 2.20 then did the ota fine with s off and then he wants to go back?
leesumm said:
I tried relocking and install from TWRP , no install, fails
I tried reunlockng and install from TWRP no install, fails
Click to expand...
Click to collapse
What exactly are you trying to flash from TWRP?
---------- Post added at 12:19 PM ---------- Previous post was at 12:17 PM ----------
a box of kittens said:
Maybe my reading comprehension is on a all time low..but doesnt it say he ruud back to 2.20 then did the ota fine with s off and then he wants to go back?
Click to expand...
Click to collapse
Its not your comprehension, his description is confusing. Sounds like he RUU'ed and is back on 2.20. Now he is trying to flash something (not sure what) in TWRP. But the next step should be to check for the JB update.
a box of kittens said:
So what do you want to do? Why'd you even do the ota if you were going back to 2.20..man I don't get it
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
If you want to do the 2.20 you must have s off just relock than run the exe file from your comp
Click to expand...
Click to collapse
I was on Hatka XL rom. I read the posts thinking this was a dev and he knew what it was about, I went back to the RUU to get the download. I relocked tried it , it downloaded, wouldn't install. reunlocked, it downloaded, wouldn't install. I flashed it from adb , that failed. the update downloads but won't install. Its downloaded about 6 times now but wont install.
I wanted to see what the new JB was . Just curious. But can't figure out why it wont install and keeps failing.
leesumm said:
I was on Hatka XL rom. I read the posts thinking this was a dev and he knew what it was about, I went back to the RUU to get the download. I relocked tried it , it downloaded, wouldn't install. reunlocked, it downloaded, wouldn't install. I flashed it from adb , that failed. the update downloads but won't install. Its downloaded about 6 times now but wont install.
I wanted to see what the new JB was . Just curious. But can't figure out why it wont install and keeps failing.
Click to expand...
Click to collapse
Were you totally stock when you tried to first download and install the OTA? Then after it failed, you installed TWRP and tried to flash from there? Its not a zip you can flash from TWRP.
What adb command are you using? Again, its not a zip file like the kind flashed in recovery. You would need to do the method described here: http://forum.xda-developers.com/showthread.php?t=1701460
Which was mentioned in teh AT&T Jellybean rollout thread here: http://forum.xda-developers.com/showpost.php?p=38873165&postcount=31
For those trying to help and confused , here it is again
Sorry to be this way but I have trouble typeing the right words to explain in tech terms.I read the posts and see there is a OTA AT&T update
I read more posts to see how to do it
I found the one with directions on how to revert to 2.20 I was on HatkaXL rom
I did all that was directed. The OTA update downloaded to "downloads" on the SD card in TWRP
I tried to install from TWRP it failed
I relocked ,failed again
I reunlocked it failed again
Every time I reboot it says download available and downloads to TWRP "downloads" on the SD card
Everytime I try to install either with reunlocked or locked it fails.
I tried flashing from adb , still fails.
The phone has done about 6 downloads OTA but none will install .
I am at a loss
Sorry but why do you want to do the update so badly..why not just flash the stock rooted one? And you won't flash an ota through twrp
a box of kittens said:
Sorry but why do you want to do the update so badly..why not just flash the stock rooted one? And you won't flash an ota through twrp
Click to expand...
Click to collapse
Just CURIOUS
leesumm said:
Sorry to be this way but I have trouble typeing the right words to explain in tech terms.I read the posts and see there is a OTA AT&T update
I read more posts to see how to do it
I found the one with directions on how to revert to 2.20 I was on HatkaXL rom
I did all that was directed. The OTA update downloaded to "downloads" on the SD card in TWRP
I tried to install from TWRP it failed
I relocked ,failed again
I reunlocked it failed again
Every time I reboot it says download available and downloads to TWRP "downloads" on the SD card
Everytime I try to install either with reunlocked or locked it fails.
I tried flashing from adb , still fails.
The phone has done about 6 downloads OTA but none will install .
I am at a loss
Click to expand...
Click to collapse
You will see that the method you cut and paste into your original post (post #1) it does not say anything about installing TWRP before installing the update:
- Re-locked Bootloader
- Applied 2.20 RUU
- Unlocked Bootloader (did it here in case the new hboot would not accept unlocktoken)
- Started Phone (disabled Fast Boot option);
- "Check for software update" (Had to do this a couple of times alternating with doing a "factory reset" because the server would not find an update)
- Downloaded and applied OTA
- Reboot into Bootloader and confirmed S-OFF+Unlock in place
- Flashed TWRP via fastboot
- Flashed Super SU via TWRP
- Reboot and have working JB on phone.
OTAs will not install in TWRP, as I've already stated.
The method you quoted says to RUU back to stock. He says unlock the bootloader, but I don't think that's critical. Don't install TWRP. Just RUU back to stock (RUU will return you to stock recovery), then go into settings and check for the update.
The reason its failing is clear now. The OTA is looking for stock recovery to install. TWRP is 3rd party custom recovery, and OTA will not work with it.
redpoint73 said:
You will see that the method you cut and paste into your original post (post #1) it does not say anything about installing TWRP before installing the update:
- Re-locked Bootloader
- Applied 2.20 RUU
- Unlocked Bootloader (did it here in case the new hboot would not accept unlocktoken)
- Started Phone (disabled Fast Boot option);
- "Check for software update" (Had to do this a couple of times alternating with doing a "factory reset" because the server would not find an update)
- Downloaded and applied OTA
- Reboot into Bootloader and confirmed S-OFF+Unlock in place
- Flashed TWRP via fastboot
- Flashed Super SU via TWRP
- Reboot and have working JB on phone.
OTAs will not install in TWRP, as I've already stated.
The method you quoted says to RUU back to stock. He says unlock the bootloader, but I don't think that's critical. Don't install TWRP. Just RUU back to stock (RUU will return you to stock recovery), then go into settings and check for the update.
The reason its failing is clear now. The OTA is looking for stock recovery to install. TWRP is 3rd party custom recovery, and OTA will not work with it.
Click to expand...
Click to collapse
Ok, am I clear to this now, I restored back to a back up of 2.20 with TWRP installed I should , if I understand, RUU back to stock 2.20 which will uninstall TWRP , then look for the update. Then install and reinstall TWRP ?
leesumm said:
Ok, am I clear to this now, I restored back to a back up of 2.20 with TWRP installed I should , if I understand, RUU back to stock 2.20 which will uninstall TWRP , then look for the update. Then install and reinstall TWRP ?
Click to expand...
Click to collapse
Yes.
It should be like this:
1) RUU to stock 2.20
2) Download and install OTA
3) Unlock bootloader
4) Install TWRP
5) For root: using TWRP, flash SuperSU
Steps 2 and 3 might be interchangeable.
redpoint73 said:
Yes.
It should be like this:
1) RUU to stock 2.20
2) Download and install OTA
3) Unlock bootloader
4) Install TWRP
5) For root: using TWRP, flash SuperSU
Steps 2 and 3 might be interchangeable.
Click to expand...
Click to collapse
Ok, thank you for the time and consideration. Once a "noobie" thinks he knows what there is to know to do a few things , there is a new puddle to cross or sink in.
When I open up superSU, it says:
There is no SU binary installed, and super SU cannot install it.
If you just upgraded to android 4.3, you need to manually re-root.
If I turn the Nexus on in recovery mode, it still says it's unlocked.
So at this point, is there anything I can do to restore root status without factory resetting? I made a backup with titanium backup but it was a while ago so I would rather not use it if there is another way.
I've read somewhere that rooting it should mean OTA updates should no longer work but somehow, it still went through and I updated it without thinking too much.
Download the supersu zip file and flash it in recovery.
http://download.chainfire.eu/371/SuperSU/UPDATE-SuperSU-v1.85.zip
This will throw me back into rooted mode while keeping my phone as is?
BruceHsiang said:
This will throw me back into rooted mode while keeping my phone as is?
Click to expand...
Click to collapse
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.
xBeerdroiDx said:
this will update the binaries and restore root. no data will be lost or formatted. simply flash the zip in twrp or cwm.
Click to expand...
Click to collapse
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?
So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?
BruceHsiang said:
I don't have twrp or cwm installed yet. Which one is generally simpler/easier to install/use?
Click to expand...
Click to collapse
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
BruceHsiang said:
So I installed goomanager and tried to install twrp, but it all goes back to the same problem which was that I am now not in root mode anymore.
Also what do you mean by flashing the zip? Which options am I supposed to use?
Click to expand...
Click to collapse
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.
wantabe said:
I've been using TWRP with no problem and it's been awhile since I've used CWM. I've never used a toolkit or flashify but with adb it would probably take a couple minutes max to flash either one.
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
Choose "Install" in recovery, with either TWRP or CWM is flashing the zip.
Click to expand...
Click to collapse
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?
BruceHsiang said:
Problem is, I didn't install twrp when I had root access before, and now when I try to use it, it says I need root to use it.
Can I flash the zip using adb in the fastboot recovery menu?
What should I do from here?
Click to expand...
Click to collapse
Sorry I've never done that. I guess you could adb push superuser.apk to the system but you still need the binary wherever that goes. Honestly I would just flash TWRP using adb and use TWRP to flash the SuperSu zip.
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
Do you have adb already working?
Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.
BruceHsiang said:
Not yet, I just saw it as an option while reading around.
How would I install twrp with that image file?
All tutorials I've found said I needed root to install it in the first place.
Click to expand...
Click to collapse
No.You do not need root to install a custom recovery. You need an unlocked bootloader. How did you get root in the first place? You must have used a toolkit of some kind? Use it again? I've only every used adb so I can't help with any toolkits but lots of people use them, I guess!
Download the latest TWRP or CWM recovery. Put it in the same folder as your adb and fastboot files. Open a command prompt and type adb reboot bootloader(you have to make sure developer settings are enabled and USB debugging is checked). Then flash recovery using fastboot by typing fastboot flash recovery name_of_file.img and then you can flash the supersu zip file.
Sent from my Nexus 5 using Tapatalk
Exactly! I'm thinking he doesn't have adb setup yet.
---------- Post added at 11:36 PM ---------- Previous post was at 11:28 PM ----------
This is a pretty decent video on how to setup adb, not the newest video out there probably but it should work!
I used chainfires autocf root file from here
http://forum.xda-developers.com/showthread.php?t=2507211
and followed a youtube tutorial.
When I try adb devices it shows my serial number followed by sideload.
I've tried sideloading both twrp and the superSU.zip, and they fail to verify and the installation aborts =\
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Carousser said:
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Click to expand...
Click to collapse
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
ThePagel said:
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
Click to expand...
Click to collapse
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Carousser said:
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Click to expand...
Click to collapse
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
ThePagel said:
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
Click to expand...
Click to collapse
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Carousser said:
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Click to expand...
Click to collapse
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
ThePagel said:
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
Click to expand...
Click to collapse
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Carousser said:
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Click to expand...
Click to collapse
Oh your stuck on twrp can't boot up to usable state?
ThePagel said:
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Oh your stuck on twrp can't boot up to usable state?
Click to expand...
Click to collapse
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Carousser said:
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Click to expand...
Click to collapse
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
ThePagel said:
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
Click to expand...
Click to collapse
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Edit-----
I found the zip file while browsing TWRP. Can I just install it?
Carousser said:
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Click to expand...
Click to collapse
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of the 3 options I gave you are your only options.
ThePagel said:
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of thoughs 3 options are your only options.
Click to expand...
Click to collapse
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Carousser said:
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Click to expand...
Click to collapse
Sure you can try tell me if it works
ThePagel said:
Sure you can try tell me if it works
Click to expand...
Click to collapse
Is there a chance of me bricking my phone?
Carousser said:
Is there a chance of me bricking my phone?
Click to expand...
Click to collapse
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
ThePagel said:
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
Click to expand...
Click to collapse
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Carousser said:
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Click to expand...
Click to collapse
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
If you have backups of stuff on your internal sd it would be much faster to just Odin to 4.3 right now.
ThePagel said:
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
Click to expand...
Click to collapse
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Carousser said:
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Click to expand...
Click to collapse
Factory reset deals with the rom. So no it will stay twrp.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
Using Odin is a lot like SBF'ing on the droid x (that was my last phone also). So if you can remember installing cyanogen mod 6 or 7 you probably always did a factory reset before first boot. Custom recovery stays intact the only way to get rid of it was to flash stock recovery with terminal emulator or sbf back to pure stock. Luckily Odin let's us flash the recover by its self so we have more options with Samsung.
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?
I just received notification for OTA update. (134MB)
BLU_p0010UU_V11_GENERIC_5.1_20151123-0956
1. Stagefright patch
2. google security patches
3. Mcafee security 2015
4.Other bug fixes
Anyone tried it ?
i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!
you can remove mcafee after the update.
Can anyone upload ota?
Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
If only for the stage fright patch
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days
Rooting after the update
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
blacksmithjk said:
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
Click to expand...
Click to collapse
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
ArconHadron said:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
Click to expand...
Click to collapse
tbirdguy said:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Click to expand...
Click to collapse
tbirdguy said:
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
Click to expand...
Click to collapse
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
ArconHadron said:
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
Click to expand...
Click to collapse
Fastflash?
Manually search?
Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM