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/
So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On the tablet, download the Stump app from http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Credit and thanks @jcase, IOMonster , @autoprime and @PlayfulGod. Credit and thanks azureflux for the music although personally I turn the volume down all the way.
2. Install the Stump app you downloaded. Android should prompt you that it's an app from an unknown source since you didn't download it from the Play Store. It should direct you to the Security Settings option "Unknown sources" which you should checkmark and then attempt again to install the Stump app.
3. Launch the Stump app.
4. Turn the volume all the way down if you want because the music can be annoying for the duration necessary to root the VK810.
5. Choose "Grind".
6. Choose "Brute Force".
7. On the VK810, it can take up to 20 minutes at which time the Stump app should say to reboot the device to implement the root.
8. Once the device is rebooted, go to the Play Store and install SuperSU from https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Alternatively you can download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053), extract the zip and install the SuperSU app, or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
You'll also need this SuperSU.zip for step 8 of the fourth post "Flash to the latest stock ROM so that you can have it with root".
Credit and much thanks to @Chainfire !!!
9. Launch SuperSU, confirm the prompt to update binaries.
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
1. On the tablet, download the "VK810_twrp_2.7.0.1.zip" from http://forum.xda-developers.com/showthread.php?t=2726707
Credit and thanks teamwin , @Drgravy , @djrbliss , @Dees_Troy , @id10terror and @traccdma !
The link is in the "DOWNLOAD" section below the "DISCLAIMER" towards the bottom of the first post.
Credit @Drgravy for the original instructions but I prefer to run the commands directly on the device instead of from a PC via USB Cable and ADB.
2. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
3. Install "X-plore File Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en
Credit and thanks Lonely Cat Games!
4. While you're in the Play Store, install "Terminal Emulator for Android" https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
5. Launch X-plore.
6. Enable root mode in X-plore:
6A. Click the three-dot menu button in X-plore's upper right corner.
6B. Choose "Configuration".
6C. In the "Root access" section, click the gray area below it and choose "Superuser + mount writable".
6D. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up. It might not open this prompt until a later step when you actually access root.
7. Find the "VK810_twrp_2.7.0.1.zip" file you downloaded in step 1 above. It should be on your internal storage in the Download folder.
8. Click once on the zip file - this will show you the files contained in it.
9. Navigate to the other file manager pane by choosing "SWITCH PANE" in the upper right corner.
10. Choose "Internal storage".
11. Navigate to the original pane by choosing "SWITCH PANE" again.
12. Select all the files inside the zip.
13. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
14. Now navigate to root. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up.
15. From root, navigate to data/local/tmp.
16. "SWITCH PANE" to where you extracted the files from the zip.
17. Select "loki_flash" and "twrp.lok".
18. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
19. Launch "Terminal Emulator" installed in step 4 above.
20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/twrp.lok
reboot recovery
Instead of "reboot recovery" you can use an app such as "Quick Reboot" from the Play Store at https://play.google.com/store/apps/details?id=phongit.quickreboot to reboot to recovery.
21. For getting to custom recovery with the tablet off, press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock-looking recovery and you can let go of both buttons). "Factory Reset" will no longer perform a Factory Reset. That's what you choose to get into custom recovery.
22. Update to to the latest TWRP v2.8.7.0 that you downloaded in step 2 above by (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.
You can put a different custom recovery on the same way.
23. You can reboot into the newer TWRP by choosing the reboot recovery option.
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
Flash to the latest stock ROM so that you can have it with root:
1. Download my ROM from my signature at the bottom of this post. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.
3. Optionally download one or more of my debloat zip files in the third post of my ROM thread in my signature below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. If you didn't already do so in step 8 of the second post "Rooting VK810 official stock release 11A", download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
Thanks to @JBurch/cry for the monetary motivation to finally put this all together in one place!
There are THREE variants of the G Pad 8.3: The Verizon VK810.4G which has LTE, and the V500 and V510 WIFI-only models. These instructions are ONLY for the VK810.4G.
Please don't quote the whole OP.
FAQ: If you use files meant for anything else other than the VK810, you'll brick your tablet. This will be exhibited by the tablet showing up in Windows' Device Manager under "Other devices" as "QHSUSB-BULK". You will have to Google for "QHSUSB-BULK" to find out how to fix that. I've read about some having success doing so and others not. I haven't ever had to fix that so I have no personal experience with it and can only lead you to Google about it.
This requires a Windows PC, preferably Windows 7 or newer, to first downgrade your VK810 variant of the G Pad 8.3 to LG build 11A / Jellybean 4.4.2, to make it easiest to root and to put a custom recovery on.
Disclaimer: I am not responsible for whatever you do to your device. This is my preferred method and what I recommend.
Note: These instructions are still working in order to downgrade from official stock release 36B on the VK810 (codename "altev"), Verizon LG G Pad 8.3 LTE, to official stock release 11A in order to make it easiest to both root and install TWRP. You can then install any ROM you like including my newest stock ROM in my signature at the bottom of this post.
Downgrading/resetting to 100% official stock unrooted release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On a Windows PC, preferably with Windows 7 or higher, download the latest Verizon-LG driver at http://www.lg.com/us/support-mobile/lg-LGVK810 (current version 4.0.3, direct download link if still working http://18d5a.wpc.azureedge.net/8018D5A/tool/dn/downloader.dev?fileKey=UW00520120427).
2. Install the driver.
3. Reboot the PC.
4. While you're continuing to follow the rest of the directions, might as well get the installed driver "loaded":
4A. Put the VK810 in Download mode:
4A1. Preferably using the original USB cable, or alternatively possibly a high-quality cable, connect the one end preferably to a USB 2.0 port on your Windows PC. Note: not all, but most USB 3.0 ports (to avoid for this process under normal circumstances) are blue in color whereas USB 2.0 ports are usually black.
4A2. Turn the VK810 off (within Android, long press the power button and choose "Power off").
4A3. The following is different from other G Pad 8.3 variants:
4A3a. Press and hold the Up Volume button.
4A3b. While continuing to hold it, insert the tablet end of the USB cable.
4A3c. You should feel the tablet vibrate and you can see a very dim, very faint graphic in the very center of the screen that says "Download Mode":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credit and thanks @sevoan for posting the screenshot at http://forum.xda-developers.com/showthread.php?t=2782066
4A3d. Let go of the Up Volume button.
4B. Windows may take up to 10 minutes to finish loading the driver you previously installed. Every time you connect any USB device to a new/different USB port on a PC, Windows will have to take a longer loading the driver process.
5. Download the official stock release 11A KDZ for the VK810: https://www.androidfilehost.com/?fid=23991606952610809 (file name "5. VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside - recommended for both ease of rooting and one less step to install the initial TWRP v2.7.0.1.7z")
If the previous link doesn't work, you can find it in my signature at the bottom of this post.
6. Download and install the free 7-Zip Windows program from ttp://www.7-zip.org"]http://www.7-zip.org[/URL]. Any version should work although you can only install the 64-bit version on 64-bit versions of Windows.
7. Use 7-Zip to extract the KDZ from the 7-Zip (7z) file downloaded in step 5 above. If you want to extract the 7-Zip on an Android device instead for some reason, use ZArchiver from the Play Store at https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver&hl=en
8. LG Flash Tool 2014:
8A. On the Windows PC, download "LG Flash Tool 2014" from http://forum.xda-developers.com/showthread.php?t=2797190
Credit and thanks @quangnhut123
The MediaFire link is in step "3. Tutorial"
8B. Run "LGFlashTool2014.exe" as Admin: Right-click on "LGFlashTool2014.exe" and choose "Run as administrator". Provide Administrator credentials if necessary. If you get a UAC (User Account Control) prompt, click "Yes".
8C. If the program doesn't run, install the Visual C++ Runtime Library, also available in step "3. Tutorial" at the link in step 8 above, then repeat step 9.
8D. Screenshots also available at the link in step 8.
8E. "Select Type" should already be at the correct default "CDMA". Same for "PhoneMode" is "DIAG" and "Reset time" is "33000".
8F. Click the yellow folder icon to the right of the "Select KDZ file" field and choose the 11A KDZ file extracted from the 7-Zip archive you downloaded in step 5 above.
For reference: "CSE Flash" is what you should normally always use. "CSE Flash" will wipe your user data including your internal storage so be sure to move/copy anything you want to keep that's currently on your internal storage. "Normal Flash" is like a dirty flash. Your device will be restored completely to stock but will keep all of your user data including your internal storage. If you're downgrading stock ROM versions, you can expect "Normal" to result in a device that'll crash. If you do so, you can attempt a "Factory Reset" from the stock recovery (with the device off - long press the power button for 10 or so seconds until the device shuts off - press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock recovery and you can let go of both buttons). "Factory Reset" will of course wipe all user data including Internal Storage.
8G. Click "CSE Flash".
8H. On the "Read Phone Information" dialog which appears, do NOT press the "Read Phone Information" button. This has always crashed for me.
8I. Click "Start".
8J. On the next dialog, you can change the Country and Language if you like - either way doesn't make a difference. Click "OK".
VERY IMPORTANT: Once you click "OK", ignore any error dialogs that pop up. I mean every single one. Don't click any buttons in them, just drag them out of your way if necessary. 99.9% of the time, given enough time the device will be flashed successfully anyway. On the VK810, usually within 20 minutes. For comparison, on the VS985 Verizon LG G3, usually within 10 minutes.
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=2
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
General thanks to, for my previous experience:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ. http://forum.xda-developers.com/showpost.php?p=60851710&postcount=108
@Revoe for letting us know the availability of the VK810 36B_00 OTA. http://forum.xda-developers.com/lg-g-pad-83/general/verizon-lg-g-pad-8-3-vk810-altev-ota-t3182449
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use. http://forum.xda-developers.com/showpost.php?p=56005236&postcount=1
@rant for giving a link to the official Verizon PDF detailing 35B. http://forum.xda-developers.com/showpost.php?p=60857092&postcount=1 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
@DeanGibson for giving a link to the official Verizon PDF detailing this release. http://forum.xda-developers.com/showpost.php?p=62413430&postcount=2 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-8-17-15.pdf
@Chainfire for SuperSU! http://forum.xda-developers.com/showthread.php?t=1538053
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading.
@xdabbeb for further knowledge about the partitions!
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip and any debloat zips too.
Reserved
Update
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
JBurch/cry said:
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
Click to expand...
Click to collapse
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
@JBurch/cry I wrote up directions for checking MD5 hashes on Android - they're in the section for flashing my ROM. I realized that this won't help you in your current situation unless you take the MicroSD card out and put it in another Android device and check the hash on there.
I'm debating whether I should write up directions for checking MD5 hashes on Windows too.
So uh ya
roirraW "edor" ehT said:
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
Click to expand...
Click to collapse
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
JBurch/cry said:
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
Click to expand...
Click to collapse
Cool! Glad at least it was something simple, even if a little bit painful to fix. You must at least be a fast learner.
Maybe I'll separate that into two steps to distinguish them.
Enjoy! I hope we get 5.1.1 someday because 5.1.1 on the G3 is so much better than 5.0.x was. You're welcome and thank you! I never even took donations until a few months back when one or two people wanted me to.
Most of the time I enjoy just seeing someone successfully do whatever they're trying to do.
Thank you, I felt so much better using this than some sketch chinese program.
FL4NKENSTEIN said:
Thank you, I felt so much better using this than some sketch chinese program.
Click to expand...
Click to collapse
You're welcome! I know what you mean.
Hey. Not sure if I am posting in the correct thread so apologises if warranted.
I recently rooted my vk810 with king root. Seemed to be the only thing to work. Only after I rooted did I realize that king root probably was not the wisest way to go.
So I'm about to attempt to unroot and hopefully get this thing rooted and a decent rom working. I like the tablet but all the verizon crap and associated bloatware are driving me nuts.
A little background, I've used linux distros for a while now, but not comfortable with command line stuff. I'm that copy and paste guy...
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Soundsofsublime said:
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Click to expand...
Click to collapse
Just follow all of the directions in the first through fifth posts and they'll get you there. You'll need a Windows PC.
Some people have told about an app called "SuperSU Me" (not by @Chainfire) to replace Kingroot with SuperSU. I have no experience with that or links to it, however.
Thanks and you're welcome!
Lost on step 3.20
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Slingb1ade said:
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Click to expand...
Click to collapse
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
How to unlock boot loader anyone suggest me
zaccheo said:
How to unlock boot loader anyone suggest me
Click to expand...
Click to collapse
No one has done it. Someone more knowledgeable than I would have to tackle it.
roirraW "edor" ehT said:
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
Click to expand...
Click to collapse
i didn't pay attention to the provided instructions "20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure)"
i was typing temp, needed to type tmp.
So basically, I got a new Mi Max helium 3 days ago, wanted root, and the most recent stock stable rom. Looked on the threads, guides are not up to date, or are for unlocked bootloaders, or are just plain unclear. SO HERE'S ONE THAT WORKS! (at least for me) I've essentially mashed together a few guides, and found really helpful posts. I'll go step by step for everyone to follow.
Your data will be wiped. proceed with backups (whatever you can do)
1. download MiFlash Beta
2. extract the installer from the downloaded zip
3. install MiFlash Beta (it should install drivers for you.)
I was met with a warning on unsigned drivers or similar. just make sure to select "install anyway"4. download and unzip this prepackaged zip for flashing in MiFlash TWRP 3.0.2.0 for helium.
5. download and unzip the fastboot version of MIUI v8.1.3.0 Global stable for Helium
6. download and unzip recovery flashable MIUI v8.2.1.0 from this thread.
7. download the newest TWRP .img from twrp's site .
I KNOW it says hydrogen, but this official post states it is for both. And if you try looking at the Helium link it doesn't have the latest TWRP. trust me on this one. it works fine. Only download the hydrogen 3.1.0 version.8. download "universal boot.img patcher.zip" from this thread.
9. download latest SuperSU recovery flashable zip.
we need to modify the ROM to be able to work with a locked bootloader as suggested by this post.
10. go to the folder you extracted the prepacked ROM you downloaded in step 6
11. zip up all the files except for the "firmware-update" folder
Now that you've got all the resources, we can go to a version of MIUI that does not have security patches and allows custom recoveries with a locked bootloader, then upgrade from there.
12. Run MiFlash Beta as administrator
13. Turn off your Mi Max Helium
14. hold down Vol + and Vol - on your phone then plug phone to computer via USB while holding the buttons down to enter EDL mode. you should feel a short vibration and then a black(blank) screen.
15. click on the "refresh" button in MiFlash
you should see a new entry for id: 1, device: COM**16. click on the "select" button and navigate to the folder which contains the extracted files of the fastboot MIUI v8.1.3 you downloaded in step 5.
17. click flash and wait for result to show "success"
now we need to re-enter EDL mode to refresh EDL18. hold down Vol + and Vol - and Power buttons on your phone with the USB cable still attached to the computer. again you should feel the vibration and then black screen.
19. refresh MiFlash
you should see a new entry for id: 1, device: COM** again20. click on the "select" button and navigate to the folder which contains the extracted files of TWRP 3.0.2.0 you downloaded in step 4.
21. click flash and wait for result to show "success"
additional info: if you have issues trying to flash, also perform the instructions from this forum post.
22. hold down Vol + and Power button to boot into TWRP recovery. you should feel a slightly longer vibration.
at this point you should see the MI logo and it will take a while before it changes to TWRP's logo. once you see the MI logo you can let go of buttons. if the MI logo only flashes quickly and disappears, then try flashing a older version of MIUI instead.23. when TWRP boots, it will ask, and you should keep system read-only at this point.
24. format the data partition. important
25. check if your preferred method of copying/pushing files can be done from the computer
26. copy/push the newest TWRP img you downloaded from step 7 to /sdcard
27. install the new recovery.img
28. reboot into recovery and keep system read-only
29. flash the prepackaged ROM you modified in step 11
30. flash the boot.img patcher you downloaded in step 8
31. flash latest SuperSU.
32. DO NOT REBOOT.
33. mount /system
34. delete /system/recovery-from-boot.p (or similar)
35. you may reboot now.
36. PROFIT!
Based on the fact that we used a boot.img patcher, theoretically I could use the official latest roms as long as we patch immediately after flashing the recovery version instead. I've not tried this, but you're welcome to.
If you get a softbrick (Mi logo flashes then black screen) just use MiFlash and flash any Fastboot version official rom. (or the v8.1.3 for convenience sake) that'll reset everything.
Thanks to these following guides and threads, and i implicitly hereby thank creators of the prepackages/tools they link to.
[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recovery by @DoomSlayer
source for boot.img patcher thanks to this post by @avi3230
[ROM] [HELIUM] MIUI 8 Global Rooted by @ajsmsg78
and @Chainfire for SuperSU
I confirm that this does work
Big Thanks
Many thanks for this guide. I followed just about every other guide written to the exact letter but no success at all. The Miflash tools written for the Max (1 click method) didn't work and showed "Specified cast not valid" despite the driver being okay the Mi logo would flash but TWRP would not load if I flashed myself with the newer flash tools beta . Xiaomi never sent me an unlock SMS either and even if they did I might have gotten stuck on 50% anyways
Your guide worked for me 100%. I followed it up to step 30 but then went for LineageOS https://forum.xda-developers.com/mi-max/development/rom-lineageos-14-1-t3529851/post70343167 ROM and Firmware instead of de-bloated MIUI (personal preference) and it worked for me great. A super thanks to all those credited in the OP but especially to shuckeru for making the instructions super clear!
Can i use this guide for my 3 / 32 GB Version ?
What about safety net pass?
Can I ask few noob questions.
1. From step 22 to 36 is the phone must connected to the computer?
2. From step 22 to 36 is it done in the phone and not in the computer?
3. If I restore my phone from MUIU account will this delete the whole process?
Thank you for anyone that answering and I really appreciate it if the answer is in simple language as I'm a noob in this. Thanks.
janmichaelis said:
Can i use this guide for my 3 / 32 GB Version ?
Click to expand...
Click to collapse
Unfortunately no, the resources I've linked are not compatible. If you can find the equivalent resources for your own model you can try it. Most you'll get is a soft brick which is easy to fix.
ankushkushal said:
What about safety net pass?
Click to expand...
Click to collapse
Never tried. Root is more important than safety net. There's no NFC for Android pay and only one dying game uses it, amongst the rest of the banking apps.
kornetbeef said:
Can I ask few noob questions.
1. From step 22 to 36 is the phone must connected to the computer?
2. From step 22 to 36 is it done in the phone and not in the computer?
3. If I restore my phone from MUIU account will this delete the whole process?
Thank you for anyone that answering and I really appreciate it if the answer is in simple language as I'm a noob in this. Thanks.
Click to expand...
Click to collapse
1. No, but you are required to connect the phone to the computer for step 26.
2. Yes, Recovery instructions are done in phone. Except step 26. That is done from your computer.
3. Yes
shuckeru said:
1. No, but you are required to connect the phone to the computer for step 26.
2. Yes, Recovery instructions are done in phone. Except step 26. That is done from your computer.
3. Yes
Click to expand...
Click to collapse
Thank you for answering. If u don't mind I still have a few question, sorry for being noob:
1. In step 16 did u mean fastboot version of MIUI v8.1.3.0? As u mention "download in step 5".
2. At step 26 the phone is still usable/detectable by the computer right? So I can transfer the file from computer to the phone.
3. Everything that I install from step 27 to 31 is it copied at step 26? Because all of the files is still in my computer not in my phone, or should i transfer it to my phone before?
4. So I should delete my back up in my MIUI account, if after twrp and root and then back up the phone in my MIUI account, will this new back up have twrp and root?
Sorry for asking so much and please pardon my English as its not my main language. And Thank You for answering.
kornetbeef said:
Thank you for answering. If u don't mind I still have a few question, sorry for being noob:
1. In step 16 did u mean fastboot version of MIUI v8.1.3.0? As u mention "download in step 5".
Click to expand...
Click to collapse
yes i did. i'll fix that typo
kornetbeef said:
2. At step 26 the phone is still usable/detectable by the computer right? So I can transfer the file from computer to the phone.
Click to expand...
Click to collapse
yes
kornetbeef said:
3. Everything that I install from step 27 to 31 is it copied at step 26? Because all of the files is still in my computer not in my phone, or should i transfer it to my phone before?
Click to expand...
Click to collapse
Yes
kornetbeef said:
4. So I should delete my back up in my MIUI account, if after twrp and root and then back up the phone in my MIUI account, will this new back up have twrp and root?
Click to expand...
Click to collapse
no. its not going to back up twrp and root. you should use nandroid backups.
@ shuckeru
After several hicup and error I finally succeed.
But I still want to ask several confirmation:
1. From step 27 until step 31, I never touch any check box. Is this OK/right?
2. To do step 34, I have to change the setting in recovery from "read only" into "allow modification" to delete the file. Is this right?
3. And in step 34 I delete it with file explorer function in the recovery, is this the right way?
4. When I'm rebooting, instead the normal MI start up loading animation, It was replaced by ring of light animation (like from horror movie). Is this OK.
Other than that everything is OK. Thanks a lot shuckeru. Hopefully will not find any problem.
Again Thank you.
kornetbeef said:
@ shuckeru
After several hicup and error I finally succeed.
But I still want to ask several confirmation:
1. From step 27 until step 31, I never touch any check box. Is this OK/right?
2. To do step 34, I have to change the setting in recovery from "read only" into "allow modification" to delete the file. Is this right?
3. And in step 34 I delete it with file explorer function in the recovery, is this the right way?
4. When I'm rebooting, instead the normal MI start up loading animation, It was replaced by ring of light animation (like from horror movie). Is this OK.
Other than that everything is OK. Thanks a lot shuckeru. Hopefully will not find any problem.
Again Thank you.
Click to expand...
Click to collapse
1. Have no idea what you are talking about.
2. Yes
3. Yes.
4. Yes
Glad I helped you enjoy!
Thank you man! :good:
shuckeru said:
1. Have no idea what you are talking about.
Click to expand...
Click to collapse
I was talking about TWRP interface menu. There is many checkbox and options that should be left alone or should be check when using TWRP menu. For example Don't touch anything else from step 27 until step 31. But in step 34 turn off "read only" checkbox. Maybe u can mention this in the guide to help more user so they can do it more easy than me.
shuckeru said:
Glad I helped you enjoy!
Click to expand...
Click to collapse
Yes Thank You!!!
If u don't mind I have two question:
1. What happen if in Step 7 I use the helium one? The one that is older? Will it give different result?
2. If there will be upgrade in the future like MIUI V8.2.2 do I have to do it from step 1 or from step 29 (that also need to be modify first)?
Again Thank you for making this guide.
jwa88 said:
Thank you man! :good:
Click to expand...
Click to collapse
no problem
kornetbeef said:
I was talking about TWRP interface menu. There is many checkbox and options that should be left alone or should be check when using TWRP menu. For example Don't touch anything else from step 27 until step 31. But in step 34 turn off "read only" checkbox. Maybe u can mention this in the guide to help more user so they can do it more easy than me.
Click to expand...
Click to collapse
really, if i didn't say do something in this guide, don't do it. its a step-by-step guide. if you managed then i've already got my message across. i'm not going to be using pictures for a 34 step guide unfortunately.
kornetbeef said:
If u don't mind I have two question:
1. What happen if in Step 7 I use the helium one? The one that is older? Will it give different result?
2. If there will be upgrade in the future like MIUI V8.2.2 do I have to do it from step 1 or from step 29 (that also need to be modify first)?
Again Thank you for making this guide.
Click to expand...
Click to collapse
1. yes it is older, I can't remember.
2. probably step 1.
i posted the steps that worked for me. i didn't go out of my and try every single combination. there is no need.
shuckeru said:
really, if i didn't say do something in this guide, don't do it. its a step-by-step guide. if you managed then i've already got my message across. i'm not going to be using pictures for a 34 step guide unfortunately.
Click to expand...
Click to collapse
Well its your guide.
shuckeru said:
2. probably step 1.
Click to expand...
Click to collapse
I actually have try once when I screw up the process to restart it from step 29 and its works. The crucial point of this process is the new ROM (and everything else) will need to be installed by TWRP, so in theory if u already have it (TWRP) u can just skip it to step 29. At least its work for me.
shuckeru said:
i posted the steps that worked for me. i didn't go out of my and try every single combination. there is no need.
Click to expand...
Click to collapse
Again is your guide.
Again thanks a LOT fro creating this guide.
I just get update notification for Miui v8.2.3.0. What should I do? If I automatic update it will I lost my ROOT and Twrp?
:good:
Hi,
I made the steps from 1 to 21 exactly as described, but my device won't enter TWRP, with Mi logo flashing and disapearing. I already flashing an older MIUI (8.0.3) as suggested, still with no success. My phone now not even boot in normal mode, only showing mi logo for one second and turning off (soft bricked). However, it still boots in fastboot and EDL modes. Any advices?
Some suggestions /improvements
Thank you friend for this great guide, great job!:good:
I could flash my device successfully after failing in the other ones i have tried.:victory:
I have some suggestions or improvements for your guide.
about the XiaoMiFlash:
1. The name of the flashed files and their path-names should be kept short; otherwise it wouldn't work. thus the names of the files should be renamed and shortened. that means the files "fastboot MIUI v8.1.3" and the " TWRP 3.0.2.0".
2. The flashing should be done quickly. " just seconds from entering EDL mode to hit flash"... that means that step #16 should be done before step #13 or 14. and step#20 should be done before step #18.
http://en.miui.com/thread-325513-1-1.html
3. 2 steps are missing:
to enable step #34. delete /system/recovery-from-boot.p, we first need to uncheck the box Mount> Mount system partition read-only
and after deletion to check it back.
Thanks a lot.....
mailm said:
Thank you friend for this great guide, great job!:good:
I could flash my device successfully after failing in the other ones i have tried.:victory:
I have some suggestions or improvements for your guide.
about the XiaoMiFlash:
1. The name of the flashed files and their path-names should be kept short; otherwise it wouldn't work. thus the names of the files should be renamed and shortened. that means the files "fastboot MIUI v8.1.3" and the " TWRP 3.0.2.0".
2. The flashing should be done quickly. " just seconds from entering EDL mode to hit flash"... that means that step #16 should be done before step #13 or 14. and step#20 should be done before step #18.
http://en.miui.com/thread-325513-1-1.html
3. 2 steps are missing:
to enable step #34. delete /system/recovery-from-boot.p, we first need to uncheck the box Mount> Mount system partition read-only
and after deletion to check it back.
Thanks a lot.....
Click to expand...
Click to collapse
Thanks for your feedback.
1. This isn't an issue unless your path is very very very long. In that case the onus is on you to clean up your environment. I've personally been guilty of that before.
2. I don't believe this is the case for everyone. I left my device in EDL mode for a very long time while I figured what I should flash before flashing and it is fine. I will make a reference to the link just in case. Thanks.
3. That's step 33. You also don't have to return it to read only. That's redundant
Do anyone know if there's already CWM recovery for Zenfone 3 ZE552KL?
I dont think many people use clockworkmod anymore, though I think I still have it on one of my backup phones.
Most people here use TWRP as a custom recovery on their ze552kl, myself included.
Procedure is the same to flash it as cwm.
Check the guides section
wang1chung said:
I dont think many people use clockworkmod anymore, though I think I still have it on one of my backup phones.
Most people here use TWRP as a custom recovery on their ze552kl, myself included.
Procedure is the same to flash it as cwm.
Check the guides section
Click to expand...
Click to collapse
but I want to try to update yo nougat using CWM cause I can't update using either stock or TWRP
I had tried all ways of updating to nougat posted here but with no luck
I'm on stock nougat with my ze552kl, and I flashed it with TWRP.
What is the issue you're having when you try to flash through TWRP?
wang1chung said:
I'm on stock nougat with my ze552kl, and I flashed it with TWRP.
What is the issue you're having when you try to flash through TWRP?
Click to expand...
Click to collapse
when i tried on stock recovery, signature verification error and on twrp, flashing just hangs up and i need to revert to stock MM rom
Sounds like you may have a corrupted download. Try downloading it again via your computer and then transfer it over.
I literally JUST updated to the the latest version of nougat off Asus' website (came out two days ago!), only error I got was Error 7 which I bypassed by deleting the first 7 lines of the updater script. No problems over here?
I am assuming you have an unlocked bootloader, TWRP v3.0.2+ and have read through the guide on how to flash, including the no-verity.zip.
wang1chung said:
Sounds like you may have a corrupted download. Try downloading it again via your computer and then transfer it over.
I literally JUST updated to the the latest version of nougat off Asus' website (came out two days ago!), only error I got was Error 7 which I bypassed by deleting the first 7 lines of the updater script. No problems over here?
I am assuming you have an unlocked bootloader, TWRP v3.0.2+ and have read through the guide on how to flash, including the no-verity.zip.
Click to expand...
Click to collapse
sorry for bothering, can you please list the steps you had done to update?
Tohan15 said:
sorry for bothering, can you please list the steps you had done to update?
Click to expand...
Click to collapse
I suppose it's best to start from scratch.
go here and unlock your bootloader.
go here, and perform Step 1 only for now, in case you have a corrupted recovery.
download the latest Nougat firmware from Asus' website here (in case your original one was corrupted). Open the archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard.
Boot into recovery with "volume up + power", select "wipe"-->factory reset. Then select "install", select the firmware, and let it do it's thing. When it's done, select "wipe Dalvik & cache", and then reboot and wait no longer than 10min.
Once she's up and running, go back to here and perform step 2.
click the "thanks" button for the two gents that wrote the above guides, without them we'd both be lost, lol.
wang1chung said:
I suppose it's best to start from scratch.
go here and unlock your bootloader.
go here, and perform Step 1 only for now, in case you have a corrupted recovery.
download the latest Nougat firmware from Asus' website here (in case your original one was corrupted). Open the archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard.
Boot into recovery with "volume up + power", select "wipe"-->factory reset. Then select "install", select the firmware, and let it do it's thing. When it's done, select "wipe Dalvik & cache", and then reboot and wait no longer than 10min.
Once she's up and running, go back to here and perform step 2.
click the "thanks" button for the two gents that wrote the above guides, without them we'd both be lost, lol.
Click to expand...
Click to collapse
okay, thank you for this. will let you know if this would work for me