Device: Nexus 7 (Wi-Fi) (Old one)
Android: 4.3
When i go to flash cyanogenmod 10.2.0-grouper.zip i get this error
Updating partition details...
Installing 'usb-otg/cm-10.2.0-grouper.zip'...
Checking for MD5 file...
Skipping MD5 Check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" | | getprop("ro.build.pr
E:Error executing updater binary in zip '/usb-otg/cm-10.2.0-grouper.zip'
Error flashing zip 'usb-otg/cm-10.2.0-grouper.zip'
Updating partition details...
Can anyone please help this has been going on forever now and its getting super annoying.
What recovery are you using? Last I heard TWRP over 2.6.3.0 had issues. Try that certain version or use CWM
Sent from my Nexus 5
Pirateghost said:
What recovery are you using? Last I heard TWRP over 2.6.3.0 had issues. Try that certain version or use CWM
Sent from my Nexus 5
Click to expand...
Click to collapse
Lol ok ill try that. I'm on 2.6.3.1 ill try the other version of TWRP first.
How Did You Solve This?
HVC FOG3Y34 said:
Lol ok ill try that. I'm on 2.6.3.1 ill try the other version of TWRP first.
Click to expand...
Click to collapse
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?
StarSphere said:
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?
Click to expand...
Click to collapse
Hey im sorry. i don't really remember what i did, it was a very annoying time for me. All i remember is googling most of the stuff. Just google how to flash custom recovery on nexus 7 jelly bean or something. sorry...
StarSphere said:
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecoveryimage.img
It's that simple
Sent from my Nexus 5
Complete Instructions
I'm a newbie, and this is what I did. I can't take responsibility for anything that happens to anyone's device, nor answer any questions, because I only half understand it myself. I am sorry I can't include links. I am too new, and the website won't trust me to do that. So, you will have to search for these things on your own.
Download Stuff to your PC Note: Some antivirus software may trigger false positives on these kinds of files and block them from downloading, so you may have to temporarily disable the website shielding portion of your program.
1) The fastboot.exe file. If you want a big download, you can get it in the Android SDK. However, I got it from the CyanogenMod Installer. The installer failed to work with my device, but conveniently downloaded the fastboot.exe file for me. I'm not sure I would recommend this route if you don't want CyanogenMod.
2) TWRP 2.6.3.0. You can get it from androidfilehost.
Safety Stuff
1) Compare the MD5 code on the website to the one in your downloaded TWRP image.
A Windows utility to do that is called MD5 SHA Checksum Utility.
An Android utility to do that is called MD5 Checker.
2) Completely back up your current Android ROM. Nexus Root Toolkit is great for this and many other things. It can be downloaded from wugfresh.
The Custom Recovery Flash
1) Make sure USB debugging is still enabled on your Android device. The video links on wugfresh's page can show you how to do that.
2) Make sure your Android device is connected to your PC via USB cable.
3) Boot your Android device into the bootloader. I used Nexus Root Toolkit -> Advanced Utilities Launch -> Reboot Bootloader to do this, but I think you can also do it by turning your device off, then holding down the Power and Volume Down buttons simultaneously (don't quote me on that).
2) Search for the location of fastboot.exe on your PC. Mine was in my user directory, where CyanogenMod's installer left it: C:\Users\{Username}\cminstaller\bundle\win32
3) On your PC, open a command line. Go into the directory where you found fastboot.exe above.
4) Type fastboot flash recovery {Complete directory location and file name of TWRP image}. If you would rather not be using the complete directory location, you can always copy the TWRP image into the same directory as the fastboot.exe file, before doing this step.
5) The command window should soon say "finished". Mine took under 2 seconds.
6) On your Android device, the bootloader should currently have a big green arrow that says "Start". Press the volume down button until the arrow says "Recovery". Then press the power button. Your device should now start TWRP 2.6.3.0.
Best of all, using TWRP 2.6.3.0 for custom recovery, instead of the newest version, really did solve the original problem. Yeah!
Unfortunately, the next time I used Nexus Root Toolkit, it insisted on updating back to TWRP 2.6.3.1. So, hopefully I won't have to flash another ROM in the near future and the next TWRP version will fix the problem more permanently.
Related
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.
planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.
Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.
Going well so far...had an issue but figured it out.
Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.
Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?
Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.
Hi everyone!
I have come to a slight problem, trying to flash an android L preview port for my N4. I rooted properly, but when CWM asked me if I wanted to fix boot, I unfortunately replied with Yes. After I lost my root, I tried rerooting, when I accidently selected a wipe all function. So, now I have no rom Just a CWM recovery.
I have downloaded a tar.gz factory image file for N4 (4.4.4) and tried adb pushing to the device. The transfer is successful, but when I try to install it from the sdcard (cwm), it reports failure. I googled and read a lot, but not much seems to be helping.
I am using a Mac, btw.
Thanks in advance!!
You cant install a .tgz via recovery. Instead you should download a flashable .zip of your rom. Try this.
CCody said:
You cant install a .tgz via recovery. Instead you should download a flashable .zip of your rom. Try this.
Click to expand...
Click to collapse
Yes, I keep trying to do that but without success.
O tried factory kitkat zip and I tried an L android I downloaded.
Could you provide me witha link to a flashable zip?
Then tell me what you want. A factory image or a custom rom. I would recommand you cyanogenmod. Downloaf the zip for your device. http://www.cyanogenmod.org/
To install stock do this:
Extract .tar.gz (using 7Zip) until you come up with folder named "occam-xxxxx"
Copy the files within it to your fastboot.exe folder
Reboot into boot-loader
Hit flash-all.bat
But you may download latest CM from https://download.cyanogenmod.org/?device=mako and install it via flash .zip in CWM (however I recommend Philz Touch Recovery)
I'd like to flash Nexus 4 port for Android L. I had downloaded android l zip file but when I try to flash it, installation aborted keeps popping up.
And once again, people keep mentioning fastboot.EXE and run a batch file, but again... I am on a Mac. It would mean a great lot if the instructions given were for a mac.
Thanks!
Here's what I did:
1. Install Wugfresh's NRT (search online for it)
2. Download the factory image from the Google website
3. Connect your phone in Recovery mode
4. Open NRT and let it update if it has to
5. Hit "Flash stock + Unroot"
6. The usage is clearly explained at every stage. You should ideally have no problems restoring your phone to a working state. Your data however is most likely lost. Sorry.
(PS: I don't usually recommend toolkits because they take away the fun in messing with the phone manually, but sometimes it becomes necessary to use them. This is one of those times )
I tried flashing CM 11 snapshot M8 release, but it gave me status 7, install failed. I tried to fix it by removing asserts and rezipping, and failed again, without a status.
I am trying to revert back to stock now, nothing else works, and neither will this, so it seems.
EDIT:
I flashed new bootloader and new radio, but when I tried to flash a stock rom, it failed again.
I don't know what to do anymore, I feel like throwing a phone against the wall and just getting a Nexus 5.
to flash the n4 L port, download the zip in the port thread and flash it in recovery. that's all. wipe before you flash.
there was no official L preview for the n4, so you can't flash it from the factory IMG, that's for the nexus 5.
simms22 said:
to flash the n4 L port, download the zip in the port thread and flash it in recovery. that's all. wipe before you flash.
there was no official L preview for the n4, so you can't flash it from the factory IMG, that's for the nexus 5.
Click to expand...
Click to collapse
Cwm reports unable to mount... i updated to 6.0.5.0 cwm, changed to twrp even using fastboot... But nothing is helping.
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
Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker and I am now receiving a security notice about unauthorised actions.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:
ElronVonSexbot said:
Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:
Click to expand...
Click to collapse
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.
jaannnis said:
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.
Click to expand...
Click to collapse
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.
ElronVonSexbot said:
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.
Click to expand...
Click to collapse
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img
jaannnis said:
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img
Click to expand...
Click to collapse
Thanks, I was going to custom ROM eventually anyway so I may as well bite the bullet, and Renovate ICE seems to be the best out there, thanks for the advice.
I think you are right, it was my thought that because I used CF-Auto-ROOT no backup of the original/stock Boot.img was ever created giving me no point of return. god knows what actually went wrong with the root. I shouldn't have been lazy and avoided the TWRP step in the first place.
Again, thanks for the help, I am Downloading Renovate ICE now, only 1.5 hours to go, yay Australian internet.