Related
I just got OTA notification, should I install it? I'm rooted and have custom recovery.
If you're running stock 4.2.2 (you didn't flash a custom ROM or applied other system changes), then yes go ahead and install the OTA.
Check this thread for more info.
4.2.2 OTA Failed
Hey
I have a rooted Nexus 4 also. Running mako kernel. I got the 4.3 OTA update. Proceeded to install the update. But the update failed, then directed me to the stock recovery screen with the red warning sign. I rebooted the phone, went to Settings -> System Update, the 4.3 OTA is no longer there, and the phone is still running 4.2.2. What should I do to get 4.3?
I'm a noob.
Thank you for your help.
By "mako kernel" do you mean the stock kernel?
Why did the update fail - did you see the error message?
Since you're rooted, you have the option of re-flashing the OTA update:
1. The update zip should be in system/cache. First copy the zip file into your sdcard (ie the root folder).
2. If you don't have a custom recovery already, I suggest you use one to flash the OTA update. Install GooManager from the Play Store and install recovery. The default recovery is TWRP. Google Youtube for the process if you're not clear.
3. Once you're ready, reboot into TWRP recovery and select the OTA update file which you copied over in step 1. This should update you to 4.3.
4. If flashing this is successful, select the option to wipe dalvik cache, then select reboot device.
5. The phone will boot up and you should now see that you're on 4.3. You can now delete the OTA zip from your root folder.
6. If you want to re-root your phone, here's where TWRP comes in handy again. Download SuperSU from here, and paste it in the same root folder you placed the OTA zip before.
7. Now boot into recovery again, then choose to flash the SuperSU zip file.
8. Reboot phone and check that you have root access.
Good luck.
Settings -> About Phone -> Kernel Version
3.4.0-faux123-mako-custom
[email protected] #141
Sun Jun 23 00:57:50 CDT 2013
Can you please expand on Step 1?
Im not so sure as to what you mean and how to complete that step
Sorry for the trouble
Thanks
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
I managed to get the 4.3 OTA again
It downloaded and I'm now in the process of installing.
The phone reboots, (bootloader is unlocked), I see Droid, with the stomach open, blue bar right underneath it.(The screen that shows up with all updates)
Now the progress stopped. The blue bar stopped moving. This is the message on screen
Install Untrusted Package?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
- Yes - install untrusted zip
-No
-No
*******Go Back *********
When I choose "Yes- install untrusted zip", the installation fails, with the red warning sign and the droid laying on the ground.
Now I'm at the ClockworkMod Recovery v6.0.3.1 screen, given the following options.
- reboot system now
- install zip from sdcard
-install zip from sideload
- wipe data/ factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
The error message below the droid reads:
ClockworkMod Recovery v6.0.3.1
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/thermald", "94e92fc68071c4f5b131d6b6a634a8e3ecca", "1f2323bbfa00ccb97c4f345e83f908ba61b830df")
E: Error in /cache/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-fromJDQ39.ebc8bad2.zip
(Status 7)
Installation aborted.
Any help would be great.
Thanks again. I appreciate it
That message is very similar to mine when I tried to apply the update using my cwm I have my baseband flashed to .33 so I can enable LTE idk if that's the problem causing it
Sent from my Nexus 4 using xda app-developers app
@cliew:
Signature verification check failures tend to happen on CWM, which is another reason why I recommend using TWRP instead.
You can try following step 2 of my initial post and see if that works.
If the update still fails when you use TWRP, that means you've altered some system files that conflict with the OTA. You'll get another error message when that happens, and it should point to whichever file is in conflict.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
@droidman89:
Yes, I believe if you've flashed different radios, that would most certainly stop the OTA taking. If you haven't already done so, you'll need to re-flash the stock ones in order to update.
I have the OTA file. Assuming that I'm on stock everything but rooted with a custom recovery, will the install still work, or should I reflash stock recovery as well?
@viewfindr
If only your recovery is custom - and no other system files have been modified - then yes, you should be able to take the OTA successfully.
Rooter? Lol just root or rooted. Sure it's a typo.
Sent from my Nexus 4 using xda app-developers app
mlj11 said:
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
Click to expand...
Click to collapse
Can't seem to locate this file anywhere in those folders. Any suggestions?
inc188 said:
Can't seem to locate this file anywhere in those folders. Any suggestions?
Click to expand...
Click to collapse
It should be in System root / cache. The other stuff in that folder (at least for me) are three folders named backup, lost+found and recovery.
If you can't find it there, it's probably because it's been some time since your OTA arrived. Which means it's now been cleared from cache.
If that's the case don't worry, because it'll come back again. Alternatively you can flash the update manually using the 4.3 image elsewhere in these forums.
------------------
Hit thanks if I helped
How to root Lenovo TAB A7-40 A3500-FL?
[Solved] See the guide below!
Device info:
Model number: Lenovo A3500-FL
Android version: 4.4.2
Kernel version: 3.4.67
Build number: A3500FL_A442_01_25_140823_SE
BB Chip: MT6582
MS Board. A3500FL
Bar code: this was my device's serial number
SW Ver.: ALPS.KK1.MP1.V2.10
Custom Build Verno.: 1408775889
Managed to get cwm and root with this guide: http://forum.xda-developers.com/and...vo-a3500-h-t2879208/post55491817#post55491817
Modified the guide for Lenovo A3500-FL!
EDIT: Also some users have reported that this guide doesn't do the trick or is out-dated, so copypasted the guide from this post here.
Guide
1. Download attachment cwmRecovery.zip and download latest Flash_tool (version 5.1352.0) can be downloaded from here)
1.1. Enable USB-debugging. (How to do this)
2. Manually install the drivers from the attachment a7_40_drivers.zip for the LenovoTablet before plugin it to computer (win7 dirvers work for win8 too).
2.1. To install unsigned/uncertified drivers on Windows 7: http://en.kioskea.net/faq/3914-windows-7-how-to-install-unsigned-drivers
2.2. To install unsigned/uncertified drivers on Windows 8: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2.3. After you have disabled the driver signature verification, you can install the drivers like this: Right click My computer, Manage, Device Manager, right click your computer at the top, Add Legacy hardware, next, Install plapla manually, next, Show all Devices, Have a Disk.., Browse to the driver folder where you unzip them, choose example windows7 and the 64 version (win7 drivers work for win8.x too), install every device. Then follow the guide.
(Note: Otherwise Windows only installs the normal automatic drivers and its more difficult to install the other drivers.)
2.4. Plug your device to PC.
3. Download the latest supersu zip file (version 2.46) from attachments or from https://download.chainfire.eu/696/SuperSU/
3.1. Move the zip.-file to the Sdcard.
4. Turn off your device.
5. Unpack cwmRecovery.zip
6. Run Flash_tool.exe with Admin Rights.
7. Chose Scatter-Loading and choose MT6582_Android_scatter.txt (in Recovery folder).
7.1. Now you will see checekd only one checkbox - recovery, if not click on it and choose recovery.img
7.2. Press Download.
7.3. Connect your device.
7.4. Wait few seconds.
8. Have CWM on your device .
9. Unplug your device.
10. . Boot to cmw recovery by turning off your device. Then press and hold VOL DOWN + VOL UP and then also press and hold POWER for about 7 seconds.
10.1. Choose " Install zip from sdcard." (To confrim always use the Power Button)
10.2. Choose "zip from sdcard".
10.3. Select SuperSU-v2.46.zip from sdcard and apply.
10.4. Have a rooted tablet.
It might be necessary to always flash the CWM with the Flashtool directly before you startup the device. Otherwise it will start the original AndroidRecovery again.
It might also be necessary to use different drivers from here.
If the supersu zip doesn't install, try toggling the signature verification to disabled from cwm->install zip from sdcard->toggle signature verification.
Tested and working on Levono A7-40 3500-FL with kitkat update, build number A3500FL_A442_01_25_140823_SE, from ota. Attached screenshot for proof. Also other people have reported that this works for later updates too, for example A3500FL_A442_01_27_141127_SE.
You can update to the latest OTA firmware by first going back to stock recovery. See the second post for the guide.
Thanks and credits go to: @Koli96 and @bobais
How to go back to stock rom/recovery and update to latest Lenovo OTA firmware update
So, it's pretty simple, you take the stock_recovery.zip from the first post, extract it, and replace recovery.img in the recovery folder with the stock one.
Then :
Quote:
4. Turn off your device.
6. Run Flash_tool.exe with Admin Rights
7. Chose Scatter-Loading and choose MT6582_Android_scatter.txt (in Recovery folder)
7.1. Now you will see checekd only one checkbox - recovery, if not click on it and choose recovery.img
7.2.. Press Download
7.3. Connect your device
7.4. Wait few seconds.
And that's it !
On a side note, if it seems stuck on a black screen with a loading circle after factory reset, you have to put the tablet in landscape mode and restart (the shutdown menu appears without any problem) - this issue doesn't seem related to recovery, but a bug within lenovo firmware and the first configuration screen.
Side note 2: The first boot after flashing new update might take 15mins.
Side note 3: After updating to the latest OTA you can go back to cwm recovery with the guide from the first post.
Credits @tenuis
I got the same tablet and I also am looking for a root. :/
Another waiting for rooting lenovo owner.
Same here, i was looking for a root guide and i couldn't find anything.
Does anyone else has a problem with long charging times?
Well it charges long and the charge stays long, so no issue here.
Seems that not that many lenovos root easily, but of course this is a pretty new device(?).
leripe said:
Well it charges long and the charge stays long, so no issue here.
Seems that not that many lenovos root easily, but of course this is a pretty new device(?).
Click to expand...
Click to collapse
OK let's try this
Install mtk drivers
Install USB and adb drivers
Install v root 1.7.8
Now tick adb debugging and connect your device to PC run v root and click root button after device get connected to v root
Let me know if you have any issues
All the best ?
Sent from my x604 using Tapatalk
The-Immortal said:
OK let's try this
Install mtk drivers
Install USB and adb drivers
Install v root 1.7.8
Now tick adb debugging and connect your device to PC run v root and click root button after device get connected to v root
Let me know if you have any issues
All the best ?
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
Can you link all the drivers?
Edit: Vroot link here: http://vrootdownload.info/vroot1.7.8/
leripe said:
Can you link all the drivers?
Edit: Vroot link here: http://vrootdownload.info/vroot1.7.8/
Click to expand...
Click to collapse
If you have win7 or win8/8.1 USB drivers will automatically installed when you connect device
Adb driver I hope this will work
http://adbdriver.com/downloads/
If it fails make a google search am sure you will find it
Sent from my x604 using Tapatalk
The-Immortal said:
If you have win7 or win8/8.1 USB drivers will automatically installed when you connect device
Adb driver I hope this will work
http://adbdriver.com/downloads/
If it fails make a google search am sure you will find it
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
Installed everything and tried vroot once again (I have tried it before).
Still not rooted. And btw that vroot at least tries to install bunch of bloatware crap on the pc.
Edit:
I would suggest for anyone who installed Vroot to your pc to scan the whole pc after you uninstall the vroot.
Here are the scanning tools:
Malwarebytes
adwcleaner
superantispyware
hitmanpro
leripe said:
Installed everything and tried vroot once again (I have tried it before).
Still not rooted. And btw that vroot at least tries to install bunch of bloatware crap on the pc.
Edit:
I would suggest for anyone who installed Vroot to your pc to scan the whole pc after you uninstall the vroot.
Here are the scanning tools:
Malwarebytes
adwcleaner
superantispyware
hitmanpro
Click to expand...
Click to collapse
I got a successful root by flashing Recovery.rar from lenovo-forums.ru, (it's easy to google, I'm not allowed to post links) with the included SPFlash Tool and afterwards flashing the needed SU binaryies and apk. However, this will mess up the OTA updates, and I can't find the stock recovery again.
Therefore, I really beg anyone having the stock recovery to post it, enabling us to switch between them, whenever we want to apply any OTAs.
Thanks a lot!
nkr said:
I got a successful root by flashing Recovery.rar from lenovo-forums.ru, (it's easy to google, I'm not allowed to post links) with the included SPFlash Tool and afterwards flashing the needed SU binaryies and apk. However, this will mess up the OTA updates, and I can't find the stock recovery again.
Therefore, I really beg anyone having the stock recovery to post it, enabling us to switch between them, whenever we want to apply any OTAs.
Thanks a lot!
Click to expand...
Click to collapse
Well I very highly doubt that there will be any more updates for a device with this price range. And since the next android version is the L version, which requires more work than before.
Edit2: http://forum.xda-developers.com/android/development/guide-lenovo-a3500-h-t2879208 found this. Tested and it works. Will edit it to the first post.
The same as me
i cant flash update.zip from cwm recovery and need to restore the stock recovery ...
I think flashing the stock rom can solve the problem..
.by using the sp flash tool we can select to flash recovery only ....unticking the others except recovery.img ....you just try to download the stock rom and flash the recovery
Same problem
Heya guys!
I have the same problem here.. I can't run the .zip file from the SD card, it get interrupted every time. Any ideas?
drabuaiad said:
The same as me
i cant flash update.zip from cwm recovery and need to restore the stock recovery ...
I think flashing the stock rom can solve the problem..
.by using the sp flash tool we can select to flash recovery only ....unticking the others except recovery.img ....you just try to download the stock rom and flash the recovery
Click to expand...
Click to collapse
I dont know what you two are trying to do but this thread is about rooting the lenovo A3500-FL not about lenovo stock rom.
Rooting..
Yes indeed, that's what I'm trying to do. Rooting the A3500-FL. According to the instructions you need to install the SuperSU from a zip on your SD card. When I try do that it gets interrupted every time. Installing recovery went well. So I'm not getting what I do wrong? Any ideas?
leripe said:
I dont know what you two are trying to do but this thread is about rooting the lenovo A3500-FL not about lenovo stock rom.
Click to expand...
Click to collapse
Mrosenho said:
Yes indeed, that's what I'm trying to do. Rooting the A3500-FL. According to the instructions you need to install the SuperSU from a zip on your SD card. When I try do that it gets interrupted every time. Installing recovery went well. So I'm not getting what I do wrong? Any ideas?
Click to expand...
Click to collapse
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip and y ou mean this when you talk about update.zip?
And I hope you are using the install zip from sdcard option and the choose zip from sdcard option?
Boot to cmw.
Install zip from sdcard.
Choose zip from sdcard.
browse to your supersu zip and apply.
Now I also update the first post's guide, so you can check that out too.
Thanks for the help so far. But now I'm starting to doubt that the CWM install went successfully. Let me show you a picture of my screen after a failed install of the UPDATE-SuperSU-v2.02.zip -file. (ht_tps://ww_w.dropb_ox.com/s/1wrnatzjk2gn42h/2014-10-09%2008.50.40.png?dl=0) (slightly modified link because of forum rules, just take out the _) I'm using the "apply update from sdcard" option, then I browse to the SuperSU.zip -file and apply it. Then it starts installation, but aborts it in a few seconds. So am I booting to just a normal recovery mode and not CWM? (Sorry if all this seems totally ignorant, I have only flashed roms before, never rooted a new device)
leripe said:
UPDATE-SuperSU-v2.02.zip and you mean this when you talk about update.zip?
And I hope you are using the install zip from sdcard option and the choose zip from sdcard option?
Boot to cmw.
Install zip from sdcard.
Choose zip from sdcard.
browse to your supersu zip and apply.
Now I also update the first post's guide, so you can check that out too.
Click to expand...
Click to collapse
Yup.. This is the problem. The recovery runs fine from Flash Tool and claims it installs it. (Download ok) But I still don't seem to have CWM on the device. It's just normal recovery mode. So any ideas about the CWM-installation? What could possibly go wrong? I get no error messages. Cheers.
//Mike
Mrosenho said:
Thanks for the help so far. But now I'm starting to doubt that the CWM install went successfully. Let me show you a picture of my screen after a failed install of the UPDATE-SuperSU-v2.02.zip -file. (ht_tps://ww_w.dropb_ox.com/s/1wrnatzjk2gn42h/2014-10-09%2008.50.40.png?dl=0) (slightly modified link because of forum rules, just take out the _) I'm using the "apply update from sdcard" option, then I browse to the SuperSU.zip -file and apply it. Then it starts installation, but aborts it in a few seconds. So am I booting to just a normal recovery mode and not CWM? (Sorry if all this seems totally ignorant, I have only flashed roms before, never rooted a new device)
Click to expand...
Click to collapse
thanks ...
It is work fine for me on a3500 fl with 4.4.2 ver a442_01_26_140911_se
Mrosenho said:
Yup.. This is the problem. The recovery runs fine from Flash Tool and claims it installs it. (Download ok) But I still don't seem to have CWM on the device. It's just normal recovery mode. So any ideas about the CWM-installation? What could possibly go wrong? I get no error messages. Cheers.
//Mike
Click to expand...
Click to collapse
Same for me, what about this @leripe ?
EDIT// Oh, It's working now, tried to flash it one more time, then I held a power button until Lenovo logo appeared and then I pressed Vol UP and Vol DOWN and the CWM came in, thank you! Now my tablet is finally rooted
By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.
Good work KidJoe :laugh::good:
I guess this will be more relevant as Soaks start heading out for the 2013 X...
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
there any way to make a dump the stock recovery in Lollipop, without the need root?
ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files
ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.
Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.
upload the stock recovery lollipop please!!!!
Good work, love your detailed explanations always .
Doesn't seem like there will be a US LTE version again... hoping there will be a RoW version that someone will eventually create a flashable zip...
Hey Guys -
Yeah, just saw this was available for my Original Shield Tablet (rooted) few minutes ago. Aside from wiping and installing OS all over again, what's the best method to upgrade and ensuring I still have root afterwards + retain installed apps & settings?
I use an SD card in Internal mode if that makes a difference. Thanks!
Just got the Notication for the wx-un-do upgrade.
Now looking for the full ota update.
Send from my .I. .I.
Don't worry, it doesn't seem to work. OTA downloads, boots and back into system again. Asks to download ota again, version number unchanged. I've tried it 3 times already.
Whatever Nividia can do wrong, they will do wrong. It's so frequent it's no longer funny.
When you are rooted and have a custom recovery installed you need the full Ota zip file.
The incremental ota update won't work.
Snah001 said:
When you are rooted you need the full Ota zip file.
The incremental ota update won't work.
Click to expand...
Click to collapse
If you're telling me, then my device is unrooted, stock everything. Not just me, got another guy on the Shield forums saying the same thing hehe.....
on a side note, mine is a ROW LTE. Maybe those with wifi sets have better luck. But the other guy I mentioned has a wifi set, and it didn't work for him.
You have a custom recovery installed?
I search the full WiFi EU ROM. Can anybody help me
Snah001 said:
You have a custom recovery installed?
Click to expand...
Click to collapse
Stock EVERYTHING.
Have no intention to root this one because the battery replaced old version is already rooted.
---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------
clawwulf said:
I search the full WiFi EU ROM. Can anybody help me
Click to expand...
Click to collapse
Be patient. It will come. many still asleep now.
When we have the full OTA zip then the link will be posted here immediately 4sure.
Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.
C'mon, RoW LTE version... can't wait
JohnK71 said:
Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.
Click to expand...
Click to collapse
You should be able to do a FULL OTA download, offload it - then TWRP it.
Once they post it on their site, we'll be able to flash it one way or another, just a matter of time. I'm disappointed it's only through the Mar update though...
Release notes here:
https://shield.nvidia.com/support/shield-tablet/release-notes/1
Incremental OTA works just fine on rooted tab + TWRP. Just keep in mind that it will replace your recovery for the stock one and you will loose root.
Worked fine for me. Completely stock.
Didn't work for me on stock row lte rom with multirom. Does go into mr twrp but fails install with an error 7.
Snah001's posting #24 of 2016.05.13.Fr.09:35 PM solved it all.
Before that, I ran into Failure as follows with "Upgrade" on my rooted RoW LTE.
< 1. > Hitting [[ Restart to install ]] made it into Team Win Recovery Project v3.0.0-0, where it logged the following :::
Running OpenRecoveryScript – Installing ZIP :::
Updating partition details » Done.
Full SE Linux support is present.
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file.
Skipping MD5 check : no MD5 file found.
:::
After that, I could reboot from TWRP, get another identical upgrade notification, and loop through as_many times as I'd like.
< 2. > Installing the upgrade manually from TWRP resulted in :::
Source : nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
Target : nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys
Verifying current system...
Package expects build fingerprint of :::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
or nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys;
this device has ::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_658.5732:user/release-keys
:::
Updater process ended with ERROR : 7
Error installing zip file '/data/data/com.nvidia.ota/app_download/PUBLIC92c9 4d59.zip'
Updating partition details » Done.
» Failed.
< 3. > Skipping all checks in OTA 4.1 LTE's "PUBLIC92c9fefb721b31eb2dc26fb6ac2b4d59.zip\META-INF\com\google\android\updater-script" seems no_good idea either, as I ended up without Notification Drawer and without Android Settings app. }} I had to restore a backup in TWRP to regain normal functionality.
Didn't manage to the OTA URL (somehow it's not showing in my logcat). But, I managed to grab it out and install manually with TWRP. Here it is:
Code:
https://mega.nz/#!XggijAhZ!Depd8u5nwMNt_wNcjbWmbT_6EGJB4OejmTv8eMSte9Y
EDIT: forgot to mention that this is the LTE ROW version.
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0. The new emoji aren't supported either. Back in Lollipop I also got an update that says Android 5.0.2 but the version stayed at 5.0 after the update. Anyways, this update is 15MB and takes around 20 minutes to install, contrary to what Motorola says.
Also, really Motorola? MAY?! I'd be expecting you to roll out the QuadRooter (August/September) patch by now.
Hi,
thnx for the info.
Any suggestions if anyone is making update zip for twrp installation?
Regards
LK82
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
YassGo said:
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
Click to expand...
Click to collapse
I think these official updates fail if you are rooted.... but if it succeeds i don't know if you retain root.
Again the RetGB variant being overlooked apparently. Spanish version got it and British version nothing...
Do anyone have some changelog for this security update? Does it fix Bluetooth issues (sometimes not routing audio via BT when connected to Nokia car kit)?
AB__CD said:
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0.
Click to expand...
Click to collapse
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Hello
This weekend I got a prompt on my phone (model XT1092) to upgrade to android 6.0.1.
I was happy about this upgrade because it solves a bug that prevented me from using bluetooth tracking devices [1].
However, after the upgrade the android version mentioned in the phone settings is still 6.0 and not "6.0.1" as expected. The only change I notice is that the "security patch" level is now May 1 2016.
Please confirm which version is actually is and/or if the specific bluetooth low-energy fix mentioned in link [1] is included.
Thanks
Click to expand...
Click to collapse
[1] URL can't link to in this forum, but search for "tileapp 6.0.1" in google
No OTA when rooted.
My MOTOX is rooted and has TWRP, so no OTA possible.
Any chance of this upgrade being downloadable somewhere alreadY?
bart.cerneels said:
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Click to expand...
Click to collapse
I can confirm that notification says "New version: 24.201.3.en.EU" and "Android 6.0.1, Marshmallow".
OK, in OP there is a screenshot with 6.0 still. So no go for BT patch I think...
Screenshot Android 6.0.1 promt
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
sgpieter said:
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
Click to expand...
Click to collapse
Yeah, Motorola might just as well be Chinese now.
maybe this helps someone
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
Click to expand...
Click to collapse
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
Hi, could you possibly upload the OTA file you downloaded? Could come in handy
Thnx in advance.
Cheers
Sent from my MOTO X using XDA Labs
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
JonesMuc said:
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
Click to expand...
Click to collapse
Thnx m8, really appreciated:good:
Cheers
Sent from my MOTO X using XDA Labs
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
May you tell the name of the post after searching "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1" ?
or some clues,
smthg plz ?
I suppose this is for rooting again
I'm looking for the stock recovery.img and the stock boot.img.
May you tell what to search to obtain them plz ?
Thx
You can find the recovery.img and boot.img in any stock firmware.
I used one from this site because it had the same version as mine:
androidsage.com/2016/02/09/install-official-marshmallow-ota-for-moto-x-android-6-0-ota-capture/
When you google for "blur_version.24.11.18" (or the version you need) you will find a lot of firmwares to download.
You are right, the other post is just for rooting again, after you updated
OK, thx :good:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
theoblackhawk said:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
Click to expand...
Click to collapse
One word: Lenovo
Actually four words: Lenovo being an ass