Related
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
dccxviii said:
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
Click to expand...
Click to collapse
You cannot get root back without a custom recovery. OTA will not relock the bootloader, you'll just lose root and custom recovery.
You need to flash custom recovery using fastboot, then flash superuser to get root back. There are plenty of guides in the stickies describing the process.
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
The superuser app checks to see if you have the latest superuser binary and will download and instalk it. Or download superuser from within rom manager.
Sent from my Nexus S 4G using xda premium
Ok..the binary update fails (because i don't have root) so it's chicken and egg as far as I can tell.
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
dccxviii said:
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
Click to expand...
Click to collapse
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
albundy2010 said:
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
Click to expand...
Click to collapse
You've misunderstood what i'm after. Thanks for trying to help tho
irishrally said:
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
Click to expand...
Click to collapse
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
dccxviii said:
You've misunderstood what i'm after. Thanks for trying to help tho
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
Click to expand...
Click to collapse
Turn off signature verification in CWM and try again.
irishrally said:
Turn off signature verification in CWM and try again.
Click to expand...
Click to collapse
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
dccxviii said:
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
Click to expand...
Click to collapse
You're welcome.
If you stick with a stock ROM then recovery will reflash every time you reboot. To prevent this you can go to system>etc, and change the file install-recovery.init to something else like install-recovery.init.bak.
So I've searched and read for about the last 4 hours, and I'm only more confused than before.
Using a Verizon VS980:
1.Took the OTA (to VS96012B) when I first got the phone
2. Rooted using ioroot script
3. installed latest twrp (2.6.3.3) using Freegee
4. Downloaded CM10.2 stable directly from Get.cm as well as appropriate GAPPS
5. Rebooted into TWRP
6. Wiped (but did not backup since I didn't care about keeping user data...did this wipe the factory OS too then?)
7. Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
8. Attempted to reboot into stock since CM flash had failed and got "secure booting unsuccessful" error message
Why would the CM10.2 install be failing under the above messages? And did I blow away my factory ROM? I just used the generic TWRP 2.6.3.3 "factory reset option"??
Dear lord help me. I've read so many threads, but I've ended up much more confused.
In theory, the stock ROM should still be installed since the CM10.2 flash failed, what do I need to do to A.)Be able to successfully flash the CM10.2 without getting the "error executing updater binary in zip" problem, or B.) Be able to at least boost back into stock LG image?
Thanks,
-A
Planning on using this to go back to how it shipped stock, and then re-rooting, and re-installing TWRP and taking another shot at a ROM. Can someone please tell me if this is the right direction?
http://forum.xda-developers.com/showthread.php?t=2449670
After going back to stock I would go this route if u take 12b OTA.
http://forum.xda-developers.com/showthread.php?t=2587296
Sent from Verizon logo plastered G2 bastard
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
amazonparrot said:
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
Click to expand...
Click to collapse
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
truckroot said:
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
Click to expand...
Click to collapse
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
amazonparrot said:
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
Click to expand...
Click to collapse
Yeah. I would try pushing the patched Loki img via adb, then try flashing the cm10.2 ROM. Otherwise u can sideload a stock ROM and flash that.
Sent from Verizon logo plastered G2 bastard
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
amazonparrot said:
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
Click to expand...
Click to collapse
Read that some are having issues using Freegee/Flashify to install a working loki'd recovery with 12b OTA. ADB seems to work best. Glad to hear u were able to get back to stock though.
Sent from Verizon logo plastered G2 bastard
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
amazonparrot said:
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
Click to expand...
Click to collapse
The unofficial cm 4.4.2 is a good one. OP has good directions on getting ROM to run perfectly with kernel settings.
If ur on 11a u should have zero issues flashing, def try a different ROM.
Sent from Verizon logo plastered G2 bastard
Same error... kinda freaking out now #FML
I am so lost and confused. Definately in over my head right now. I usually depend on the one click methods to flash, and this time I'm bricked. Same problem as post #1 on the thread. Not very familiar with adb. Is anyone with experience in this area able/willing to remote into my mac or even over the phone to help a brother out? I'm willing to compensate you for your time.
Thanks,
Vinnie
Ok so currently running a rooted VS980 on 12B with CWM 6.0.x.x non touch. I have attempted to flash both CM10.2 and a 4.4 kitkat absed rom (pa_g2-4.0-ALPHA-20131205-vs980). In both cases I get the same error,
asset failed: run_program("/system/bin/loki.sh") == 0
E: Error in /data/media/o/ (filename of rom in zip format)
(status 7)
installation aborted
My current steps are a backup of rooted 12B,
wipe/factory reset
wipe cache partition
wipe dalvik
format system.
I also attempted to install a GAPPS .zip to see if it was happening with all zip files, the GAPPS installed with no issues.
phone also will take a restore from CWM so at least im not bricked in the meantime
Now that that is all out of the way can anyone tell me what is happening here? Only my second rooted phone first being a droid 4 and by the time I rooted it there was a lot out in the form of auto runs and apps to take care of all the steps to root/flash roms. So my knowledge level is pretty novice on this.
UPDATE: so after my reading im coming across random issues with CWM on the LG G2. going to attempt to push ASOPA 4.4 with GAPPS after I switch to TWRP.
Get same thing on trwp
Sent from my VS980 4G using XDA Premium 4 mobile app
Make sure you are on the latest versions. Darker ones will not install kitkat. Roms
Sent from my LG-D800 using Tapatalk
UPDATE 2:
Ok, so after following the guide below and face palming myself about a thousand times through the process, I've come to another snag..... I get all the way to the end in both options 1 and 2, then get the error below. Option 3 (GooManager) states that there is no recovery for my phone.
http://forum.xda-developers.com/showthread.php?t=2449670
[+] loki_flash 2.1
[-] loki aboot version does not match device
looked around through the thread and cannot find a definitive answer on what im doing wrong or what I may have done wrong in rooting or with already running CWM.
I want to attempt to go back to stock. Completely unrooted and start from scratch but not sure the path to take on this. I've factory reset via CWM but the phone is still rooted and the apps i removed via titanium backup are missing as well.
Is there a way to pull a stock firmware and somehow push it to the phone so that everything i have done thus far is erased? ( excuse the terminology here) like erasing and reformatting a computer's hdd and re installing windows.
update:
http://forum.xda-developers.com/showthread.php?t=2432476
Hopefully this stock firmware guide works...
Goo doesn't work either lol. Use freegee to install recovery. Will take you about 2 minutes to complete and you will be rooted and have a custom recovery installed
Sent from my LG-D800 using Tapatalk
Thats how I got CWM onto the phone after I rooted. After all my reading though, I want to go back to stock and start all over again. I still haven't got a chance to start the proccess yet, been pouring through the thread about reverting back to stock firmware to see what issues have come up. From mwhat I can tell the issues were all related to people not fully reading the directions provided by the OP. Will update once I have attempted. FreeGee worked like a charm for getting CWM on though
Ok, so using the thread listed above i was able to revert back to 11a!!!!!!! now, onto IORoot and see if i can loki twrp 2.6.3.2 and then flash 2.6.3.3.
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
corrsea said:
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks for clarifying that!!!!!
So as of now I have re flash stock 11A per the guide (showed unrooted once done), Rerooted via IORoot 22 and then adb flashed twrp 2.6.3.2, Now I am going to flash the 2.6.3.3 .zip via TWRP and then try to flash A ROM and Kernel.
Back up and running!!!!
IORoot22
TWRP 2.6.3.3
ASOPA 4.4 BETA (updating as daily releases come out)
Slim GAPPS (might switch to regular due to the speech to text function being missing from keyboard but need to do some reading to figure out if running the full GAPPS will fix that or if it is something with the ROM ) EDIT: as i typed this i got a text and as i replied I noticed the icon is there now on the keyboard.... FACEPALM....
Thanks for all the information that was provided guys. Probably could have cleared this all up without the thread and just reading, Thanks for not flaming me and turning me away with a statement to use the search function.
To anyone reading this to find a fix for an issue they are having here are the links in order of what I did to get back up and functioning.
1. Went back to stock
http://forum.xda-developers.com/showthread.php?t=2448960 ( how to go back to stock )
http://forum.xda-developers.com/showthread.php?t=2141817 ( how to set up SDK )
2. ReRooted
http://forum.xda-developers.com/showthread.php?t=2448887 ( IOROOT how to )
3. TWRP
http://forum.xda-developers.com/showthread.php?t=2449670 ( TWRP how to )
All these guides worked the first time through for me, make sure you take the time and read all the directions in them.
Just got a notification for OTA to 5.0.1. Anyone know if this will break root? And if it will install with CWM custom recovery?
Hello, I tried to install in my WiFi model and rooted and I got and error during the installation, so I'm waiting for the opinion of other users. ?
Sent from my SHIELD Tablet using XDA Free mobile app
I kiddy got it too, I'll wait for the zip file lol.
Ya think it is really better to install from the zip file?
Sent from my SHIELD Tablet using XDA Free mobile app
I'll be the guinea pig
I downloaded the OTA but can't find where is the ota file. Any idea where is it?
Sent from my SHIELD Tablet using XDA Free mobile app
Get an error in cwm . shucks
Does someone can post change log please?
Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
Same. My bootloader is locked and tried flashing via cwm and got error. Pls teach me how to update?
Sent from my SHIELD Tablet using XDA Free mobile app
Judge584 said:
Does someone can post change log please?
Click to expand...
Click to collapse
Android Central has the log change. It's bug fixes really.
Also, in this thread a user states that apparently only with the full 5.0.1 can you install it with CWM.
http://forum.xda-developers.com/shi...p-nvidia-shield-tablet-ota-android-5-t2982677
You will lose root and CWM after the reboot but those took about 3 minutes to get back .. easy peasy. I'm now at 5.0.1 on my shield with root and CWM.
Cheers.
Hello aegern,
deletes the full update all the data? can you give me the recovery and root attach files?
Thanks
Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
d4m45cuz said:
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
Click to expand...
Click to collapse
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
l0ud_sil3nc3 said:
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
Click to expand...
Click to collapse
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
GMrMadrigal said:
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
Click to expand...
Click to collapse
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
l0ud_sil3nc3 said:
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
Click to expand...
Click to collapse
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
GMrMadrigal said:
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
Click to expand...
Click to collapse
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
dgjenkins said:
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
Click to expand...
Click to collapse
Hi dgjenkins, sorry answer so late. So, answering you first, not, it did not work for me. I actually did give up, the bad was that I tried so many ways to do it that I freezed the tablet and did not start again. Well, looking out there, I found this amazing video who saved my tablet of bust it again the wall and start from the original firmware.
https://www.youtube.com/watch?v=GsMo1tPlIFU
I did intal the Minimal ADB and Fastboot
Copy the image files in to the Minimal ADB and Fasboot directory c:\Programs Files (x86)\Minimal ADB and Fastboot
Ope Minimal ADB and Fastboot
-Type: fastboot flash recovery recovery.img
-Type: fastboot flash boot boot.img
-Type: fastboot flash system system.img
-Type: fastboot flash userdata userdata.img
-Type: fastboot flash staging blob
-Type: fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
And done . I can now install the updates from the stock firmware. Maybe I will root it again once a stable way to root the shield tablet appear out there. :cyclops:
Happy Holidays and Thanks for the interest! :good:
Nvidia updates definitely trump Android ones. These days, Google is in the habit of pretending that a nexus 5 camera bug is worthy of a new Android version (that was KitKat) or that an update is a great place to break functionality (App Ops, also with KitKat). Anything that's not a minor version with updates you know you want... Avoid on a non Nexus unless you have a great reason for it.
Manufacturers besides Google, see, they do this thing I like to call quality control. They generally release an OS that is ready for the hardware and software*. Crazy, right?
* unless that hardware is, say, the pen
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Can you add what variant and build you are using before the update? Also the build afterwards?
KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.
I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?
bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.
rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.
That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.