Related
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
Hello
I have seen many of you have had problems with ROOT and Recovery for altev (Vk810) G PAD Lte Verizon only. So I have decided to help everyone who is having troubles with either of the two. Another reason to write this guide is that we are gearing up for some serious development in next weeks and months so I think many of you would find it useful. I shall update this guide if necessary. I recommend you read the second post of FAQ before proceeding with this guide.
I woudl not be responsible for any damage nor would be any developer or contributor at XDA. You understand the risks before proceeding on your own. All credits to the developers for their work and I am merely arranging everything in one place.
UPDATE Root 5.02 35A
I have successfully rooted lollipop 5.02 with SuperSU. Proof is given in the postHERE IS THE PROOF
Many thanks to my friend @roirraW "edor" ehT for his help, suggestions and his constant motivation that led me to keep trying!
All instructions are given here ROOT VK810 LOLLIPOP 35A WITHOUT DOWNGRADING
Root 4.4.2
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
3.If you unable to root it via brute force, repair your VK81024A firmware using Verizon tool because there's something wrong with your firmware.(modifications mostly)
4.Repairing would ensure it works. Brute force roots your device in first attempt so if it doesn't, you'll need to repair your firmware and do not waste time to retry.
Instructions :
1.Download stump root and install apk in your device. You can get it from HERE
You will need unknown sources checked in settings for installation.
2.Once installed. Select bruteforce. It'd say device is not supported but brute force works perfectly.
3.Once you run brute force, it'd ask you to restart your device. Do it manually.
4.After restarting your device, install SuperSU from market and run it. It'd ask to upgrade the binary, do it.
5.Uninstall stump tool.
Done.
Recovery :
It is a bit tricky to install it. Recovery requires aboot 4.2.2. Thus if you are on 4.4.2, you'll need to downgrade your aboot first.
FAQs
1.You'll need platform tools and a PC with Usb debugging on.
2.You must unlock developer options in settings by tapping build number 9 times in about device and then turn usb debugging on in developers tool.
3.Make sure you have platform tools(see attachment) and you have opened command prompt and cd to directory. (You can alternatively use ctrl+shift+right click in the directory of platform tool and select open command prompt here)
4.Paste aboot and twrp contents into platform tools folder.
Instructions :
How to downgrade and flash aboot4.2.2
If you are on 4.2.2, skip this step.
1.Download aboot 4.2.2 FROM HERE
2.Rename aboot4.2.2 to aboot. (recomove 4.2.2 from it only)
3.Place it in your internal memory/sd card/platform tools folder.
4.Run the commands.
HTML:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit
Installing TWRP
You will need to install twrp 2.7.0.1 first using loki support. After you are done, you can flash CWM or TWRP (2.7.0.2) zips from recovery.
Refer to last line for TWRP download links.
1.Open command prompt from PC in platform tools folder.
2.Paste contents of twrp 2.7.0.1.zip into the folder.
3.Type these commands
HTML:
adb push loki_flash /data/local/tmp/loki_flash
adb push twrp.lok /data/local/tmp/twrp.lok
adb shell
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/twrp.lok
exit
exit
adb reboot recovery
You would boot into recovery now
How to boot into recovery
To boot into recovery, you will need to first turn off your device.
Hold volume down+power key and switch it on.
Using volume keys, select factory reset data. (I know I know but this isn't a troll)
You will boot into recovery.
How to boot into download mode
To boot into download mode, you will need to first turn off your device.
Hold volume up+ connect it to the PC using a USB.
Change recovery to CWM
1.Download vk810 CWM recovery from the development forum. See Link Below for CWM
2.Flash it using twrp recovery.
To flash twrp.zip from cwm, you might need to toggle loki support in advanced in CWM menu
HOW TO FLASH KDZ FILES
1- Make sure you have installed the proper drivers in Post#2
2- Download LG Flash Tool 2014 from the attachment and extract them.
3- Paste the KDZ file in the LG Flash tool folder that you want to flash for best results.
4- Run the tool and select the file you want to flash.
5- Do not change any other value. (keep the TYPE as CDMA, Phone Mode as DIAG and Reset Time as 33000 )
6- Choose CSE flash (It wipes all the data as well. Normal mode is used for repairing the same firmware that you have installed and it might stuck on boot screen, just hold down power+ down key and do a factory reset. )
7- A new screen would appear. Just choose start
8- It might ask for administrator permissions, Allow
9- A new screen would that would ask for country and language. Completely ignore the language and country. You do not need to change it.
10- It might give you warning like " connection to server failed. Do you wish to cancel S/W Update. Complete IGNORE THIS. Do not even press OK on this screen. Just drag the window and you will see S/W progress.
11- Wait patiently. Do not disconnect the cable until done.
Special Thanks to @paperWastage for the following guide
ALL FLASHING GUIDE
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Click to expand...
Click to collapse
Please refer to this guide for all other problems.
CLICK HERE
The guide includes amongst many others
*non-booting device
*JB4.2.2 Issues
*KK4.4.2
*LTE not working
Some Useful Links
TWRP RECOVERY
CWM RECOVERY
Some Considerations /Frequent Issues:
1.To connect into usb debugging mode or your device to be detected by Verizon tool.
You must select PC connection as Internet connect>Ethernet. It took me a long time to realise that actually.
2.You can not boot into recovery via abd commands or key combination. See recovery post above how to boot into recovery once you have flashed it.
3. For me, old version of drivers which are included in verizon tools worked. I have also attached the latest drivers from verizon website as well.
Download Official Verizon Tools
http://d-h.st/g7UC with XP support (30 MB)
Download Latest Drivers
See attachment
The new lg root kit works for 24a
Sent from my vk810 using XDA Free mobile app
Can you provide me the link and proof?
juggamonkey said:
The new lg root kit works for 24a
Sent from my vk810 using XDA Free mobile app
Click to expand...
Click to collapse
@jparasita @roirraW "edor" ehT
I think you would be interested to see this
juggamonkey said:
The new lg root kit works for 24a
Click to expand...
Click to collapse
Hnk1 said:
Can you provide me the link and proof?
@jparasita @roirraW "edor" ehT
I think you would be interested to see this
Click to expand...
Click to collapse
@juggamonkey, I believe it if you tell me that you have been able to get the new one click root method (via GUI or script) to work on 24A, however like some people that no matter what even after a fresh flash of the 24A KDZ couldn't get Stump to work for them, Stump works for me on 24A but I've tried two or three times after two or three fresh flashes of the 24A KDZ in CSE mode to wipe everything and couldn't get the new root method to work with my VK810. It works just fine with my VS985 G3, however.
I would have to see proof to list it as a viable alternative for others, however. I know that before I had tried it, I and others mentioned it as a possible new way to root the VK810, however it just always hangs on "rooting...." for me (again, only on the G Pad 8.3 VK810 variant, works fine on my G3 VS985).
I'm not really willing to try it again on mine as two-three times is enough to eliminate it as a possibility for me when Stump works for me every time.
@Hnk1, thanks for this thread. I had seriously considered posting a comprehensive all-in-one thread with all the important info needed by VK810 owners but I'm so "AR" (read: perfectionist) that I I was overwhelmed providing all the links and proper credits. I'm an all or none kind of person and in my case it just had to be none.
Let's rate this thread 5/5 and call for it to be stickied (didn't notice if it is already).
roirraW "edor" ehT said:
Let's rate this thread 5/5 and call for it to be stickied (didn't notice if it is already).
Click to expand...
Click to collapse
I have asked the moderator of this thread to pin it, he hasn't however have read my message till yet. I hope it happens soon enough. Cheers for your feedback
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
There's the link what's the best possible way of of me showing proof that I rooted 24a with this tool?I'm currently on cm11 ....I had 24A ..brute force wouldn't work for stump root.. Hooked my tab up to the laptop ran this tool . it stuck at the download screen while rooting I held power down until it rebooted and I was rooted.. Downgraded aboot to 4.2.2 installed twrp and now I'm running cm11
Sent from my Nexus 6 using XDA Free mobile app
juggamonkey said:
There's the link what's the best possible way of of me showing proof that I rooted 24a with this tool?I'm currently on cm11 ....I had 24A ..brute force wouldn't work for stump root.. Hooked my tab up to the laptop ran this tool . it stuck at the download screen while rooting I held power down until it rebooted and I was rooted.. Downgraded aboot to 4.2.2 installed twrp and now I'm running cm11
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, that's the one I tried as well, both script and GUI versions. I totally believe you, though so no worries. I don't have time right now (I'm at work!) to think about how to prove it other than videorecording doing the whole process from start to finish, but I really don't expect that from you. I don't require the proof to believe you, though. I'm just saying I wouldn't tell someone to try that to root their VK810 unless I heard of it working for more than one person, or as a last ditch effort, of course.
Interesting, you say it was stuck at the download screen, did the script itself indicate it was done or was it stuck on "rooting..." just like it showed for me? If the script was stuck on "rooting..." for you too then I'll have to try again. Maybe I assumed that since the script never went beyond that point that it wasn't actually rooted, and I don't remember at this point if I did actually reboot and see if it was.
Thanks for the info.
I know it didnt finish in the GUI of the tool .can't remember exactly what it said but I believe it got stuck at rooting after rebooting into download .I just held power after I realized it was stuck in download mode and all was well
Sent from my vk810 using XDA Free mobile app
roirraW "edor" ehT said:
Yep, that's the one I tried as well, both script and GUI versions. I totally believe you, though so no worries. I don't have time right now (I'm at work!) to think about how to prove it other than videorecording doing the whole process from start to finish, but I really don't expect that from you. I don't require the proof to believe you, though. I'm just saying I wouldn't tell someone to try that to root their VK810 unless I heard of it working for more than one person, or as a last ditch effort, of course.
Interesting, you say it was stuck at the download screen, did the script itself indicate it was done or was it stuck on "rooting..." just like it showed for me? If the script was stuck on "rooting..." for you too then I'll have to try again. Maybe I assumed that since the script never went beyond that point that it wasn't actually rooted, and I don't remember at this point if I did actually reboot and see if it was.
Thanks for the info.
Click to expand...
Click to collapse
juggamonkey said:
I know it didnt finish in the GUI of the tool .can't remember exactly what it said but I believe it got stuck at rooting after rebooting into download .I just held power after I realized it was stuck in download mode and all was well
Sent from my vk810 using XDA Free mobile app
Click to expand...
Click to collapse
I can add a poll for the method. If it works for more than 5 people, I can add it in the guide.
What do you reckon?
Hnk1 said:
I can add a poll for the method. If it works for more than 5 people, I can add it in the guide.
What do you reckon?
Click to expand...
Click to collapse
That sounds like a good idea. Quote Todd Snider "64 percent of all the world's statistics are made up right there on the spot"...
Todd Snider:Statistician's Blues Lyrics
But really, yes, can't hurt!
OK, so the guide is not very n00b friendly...
I get to the part where I run from CMD from PC, and nothing happens. Just 'device not found' errors.
I've tried everything from copying everything in platform-tools to C:/ drive and TWRP in that folder, as well as C:/ drive.
I cannot get TWRP on this device. All that I have gotten so far from this guide is where I started which is that I cannot get custom recovery on my device.
I did however get ONE step further as the Terminal commands FINALLY WORKED on the aboot part. So now I am rooted, ran aboot commands, got supersu, etc.
Now I just need help with the TWRP part.
Please help !!!
---------- Post added at 02:11 AM ---------- Previous post was at 02:07 AM ----------
{
"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"
}
---------- Post added at 03:03 AM ---------- Previous post was at 02:11 AM ----------
Firs the guide tells me to upgrade from 4.2.2 to 'make sure I am on the latest firmware'.
Root
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
Then, the guide tells me if I was already on 4.2.2 (which I was, because after bricking the device, the LG tool auto put me there) to skip this whole section. Really? So first I should be on the latest firmware, and 2 seconds later find out, I should not be on the latest firmware?
How to downgrade and flash aboot4.2.2
If you are on 4.4.2.if you are already on 4.2.2, skip this step.
:/
I'm not being an ass, I am laughing, and I am extremely pleased with the guide, but it isn't n00b friendly. n00b friendly would mean a n00b could do it.
Thank you again!!!
Do u have correct lg drivers for your PC also do you have usb debugging turned on and when connected there will be a RSA box pop up on your tab to trust the PC select always trust PC and it should read your phone from the cmd prop type in adb devices and see if your device shows then
Sent from my Nexus 6 using XDA Free mobile app
SidedX said:
OK, so the guide is not very n00b friendly...
I get to the part where I run from CMD from PC, and nothing happens. Just 'device not found' errors.
I've tried everything from copying everything in platform-tools to C:/ drive and TWRP in that folder, as well as C:/ drive.
I cannot get TWRP on this device. All that I have gotten so far from this guide is where I started which is that I cannot get custom recovery on my device.
I did however get ONE step further as the Terminal commands FINALLY WORKED on the aboot part. So now I am rooted, ran aboot commands, got supersu, etc.
Now I just need help with the TWRP part.
Please help !!!
---------- Post added at 02:11 AM ---------- Previous post was at 02:07 AM ----------
---------- Post added at 03:03 AM ---------- Previous post was at 02:11 AM ----------
Firs the guide tells me to upgrade from 4.2.2 to 'make sure I am on the latest firmware'.
Root
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
Then, the guide tells me if I was already on 4.2.2 (which I was, because after bricking the device, the LG tool auto put me there) to skip this whole section. Really? So first I should be on the latest firmware, and 2 seconds later find out, I should not be on the latest firmware?
How to downgrade and flash aboot4.2.2
If you are on 4.4.2.if you are already on 4.2.2, skip this step.
:/
I'm not being an ass, I am laughing, and I am extremely pleased with the guide, but it isn't n00b friendly. n00b friendly would mean a n00b could do it.
Thank you again!!!
Click to expand...
Click to collapse
thank you for pointing out the mistake. Changes have been made. Now what just follow the recovery instructions.
If you are 4.4.2, then you need to have aboot4.2.2 and then carry on with recovery instructions.
Why do not you send me the screenshot of the errors you have faced.
Secondly , are you connecting your device in modem>ethernet mode else PC wouldnot be able to recognise it.
Have you enabled USB debugging in developer tools ?
What is your driver status ?
Hnk1 said:
thank you for pointing out the mistake. Changes have been made. Now what just follow the recovery instructions.
If you are 4.4.2, then you need to have aboot4.2.2 and then carry on with recovery instructions.
Why do not you send me the screenshot of the errors you have faced.
Secondly , are you connecting your device in modem>ethernet mode else PC wouldnot be able to recognise it.
Have you enabled USB debugging in developer tools ?
What is your driver status ?
Click to expand...
Click to collapse
I did include a screenshot in previous post.
After all steps have been completed, I open a CMD prompt from within Platform tools, and it just says 'device not found'.
If I install the ADB drivers it says ADB Daemon running on port 5087, and then says Device not found.
I have USB debugging enabled, I have tried every driver possible from default ADB to Verizon official, the computer can see the device, the RHA fingerprint key pops up and I agree, but no matter what when I type
adb push loki_flash /data/local/tmp/loki_flash
Nothing happens. Device not found.
SidedX said:
I did include a screenshot in previous post.
After all steps have been completed, I open a CMD prompt from within Platform tools, and it just says 'device not found'.
If I install the ADB drivers it says ADB Daemon running on port 5087, and then says Device not found.
I have USB debugging enabled, I have tried every driver possible from default ADB to Verizon official, the computer can see the device, the RHA fingerprint key pops up and I agree, but no matter what when I type
adb push loki_flash /data/local/tmp/loki_flash
Nothing happens. Device not found.
Click to expand...
Click to collapse
Try rebooting the PC. You can also try another USB port. If you're trying a USB 3.0 port, try a USB 2.0 port instead. Are you using the original cable?
Rooted 35A from Verizon. Instructions and details coming soon
Congratulations for rooting 35A_08 without downgrading to 24A or earlier first!
Hnk1 said:
Hello
I have seen many of you have had problems with ROOT and Recovery for altev (Vk810) G PAD Lte Verizon only. So I have decided to help everyone who is having troubles with either of the two. Another reason to write this guide is that we are gearing up for some serious development in next weeks and months so I think many of you would find it useful. I shall update this guide if necessary. I recommend you read the second post of FAQ before proceeding with this guide.
I woudl not be responsible for any damage nor would be any developer or contributor at XDA. You understand the risks before proceeding on your own. All credits to the developers for their work and I am merely arranging everything in one place.
UPDATE Root 5.02 35A
I have successfully rooted lollipop 5.02 with SuperSU. Proof is given in the postHERE IS THE PROOF
Many thanks to my friend @roirraW "edor" ehT for his help, suggestions and his constant motivation that led me to keep trying!
All instructions are given here ROOT VK810 LOLLIPOP 35A WITHOUT DOWNGRADING
Root 4.4.2
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
3.If you unable to root it via brute force, repair your VK81024A firmware using Verizon tool because there's something wrong with your firmware.(modifications mostly)
4.Repairing would ensure it works. Brute force roots your device in first attempt so if it doesn't, you'll need to repair your firmware and do not waste time to retry.
Instructions :
1.Download stump root and install apk in your device. You can get it from HERE
You will need unknown sources checked in settings for installation.
2.Once installed. Select bruteforce. It'd say device is not supported but brute force works perfectly.
3.Once you run brute force, it'd ask you to restart your device. Do it manually.
4.After restarting your device, install SuperSU from market and run it. It'd ask to upgrade the binary, do it.
5.Uninstall stump tool.
Done.
Recovery :
It is a bit tricky to install it. Recovery requires aboot 4.2.2. Thus if you are on 4.4.2, you'll need to downgrade your aboot first.
FAQs
1.You'll need platform tools and a PC with Usb debugging on.
2.You must unlock developer options in settings by tapping build number 9 times in about device and then turn usb debugging on in developers tool.
3.Make sure you have platform tools(see attachment) and you have opened command prompt and cd to directory. (You can alternatively use ctrl+shift+right click in the directory of platform tool and select open command prompt here)
4.Paste aboot and twrp contents into platform tools folder.
Instructions :
How to downgrade and flash aboot4.2.2
If you are on 4.2.2, skip this step.
1.Download aboot 4.2.2 FROM HERE
2.Rename aboot4.2.2 to aboot. (recomove 4.2.2 from it only)
3.Place it in your internal memory/sd card/platform tools folder.
4.Run the commands.
HTML:
adb shellsudd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/abootexitexit
Installing TWRP
You will need to install twrp 2.7.0.1 first using loki support. After you are done, you can flash CWM or TWRP (2.7.0.2) zips from recovery.
Refer to last line for TWRP download links.
1.Open command prompt from PC in platform tools folder.
2.Paste contents of twrp 2.7.0.1.zip into the folder.
3.Type these commands
HTML:
adb push loki_flash /data/local/tmp/loki_flashadb push twrp.lok /data/local/tmp/twrp.lokadb shellsucd /data/local/tmpchmod 777 loki_flash./loki_flash recovery /data/local/tmp/twrp.lokexitexitadb reboot recovery
You would boot into recovery now
How to boot into recovery
To boot into recovery, you will need to first turn off your device.
Hold volume down+power key and switch it on.
Using volume keys, select factory reset data. (I know I know but this isn't a troll)
You will boot into recovery.
How to boot into download mode
To boot into download mode, you will need to first turn off your device.
Hold volume up+ connect it to the PC using a USB.
Change recovery to CWM
1.Download vk810 CWM recovery from the development forum. See Link Below for CWM
2.Flash it using twrp recovery.
To flash twrp.zip from cwm, you might need to toggle loki support in advanced in CWM menu
Special Thanks to @paperWastage for the following guide
ALL FLASHING GUIDE
Please refer to this guide for all other problems.
CLICK HERE
The guide includes amongst many others
*non-booting device
*JB4.2.2 Issues
*KK4.4.2
*LTE not working
Some Useful Links
TWRP RECOVERY
CWM RECOVERY
Click to expand...
Click to collapse
That 4.2.2 DL send me to a Chinese page?
---------- Post added at 10:18 PM ---------- Previous post was at 10:12 PM ----------
Its really not difficult. Just not as easy as ive become a custom too. Dang Verizon and they're bootloaders
TWRP for 5.02
So, if I am already on 5.0.2 and rooted, am I able to install TWRP using stated instructions for 4.4.2?
Hey all,
Today I present you with Rerun Root for the ZTE Majesty!
Disclaimer
The usual. I am not responsible for any damage done by YOU to YOUR device. As always, anything can brick your phone! Be careful!
What is the ZTE Majesty?
It is an extremely cheap, low end 2013 phone that, honestly, very few people probably have.
Why are you making this?
ReRun isn't about this device in specific, the Majesty was just the only ZTE phone I had in hand. The vulnerability that ReRun relies on (Thanks to Justin Case & Beaups! Without them this wouldn't be possible) is present in nearly all ZTE devices! This allows you to reboot to a mode where Write Protection will be disabled, and it can be re-enabled with a simple reboot (Or not! Your choice!)
Does this work on a Locked Bootloader?
I can't speak for every device, but on most, yes. I.e. ZTE Max, ZTE Blade, ZTE Majesty
I want to port this to x ZTE device?
Read the readme in the attached .zip. It honestly isn't too complicated. If you have a device that you have tested it on that works, send me a PM with your Boot.img, Recovery.img, and their corresponding blocks on the eMMC, and I will add support to ReRun.
What Black Magic is this?
We are taking the boot partition (kernel, ramdisk, etc.) and writing it to the recovery partition, then rebooting to recovery. The reason this works is:
1. The Boot& Recovery images are signed in the same way by ZTE, meaning that the phones don't known the difference, they just see that the signature is valid.
2. When the recovery kernel is booted, it is booted with permission to re-mount system RW, side-stepping Write Protection.
How do I use this?
Open rerun.bat and follow the instructions, you will need to have temp-root (i.e. TowelRoot), and SuperSU installed before running the tool, though, it will walk you through all that.
Supported Phones:
As of now, only the Majesty, but like I stated above, PM your device's Boot.img, Recovery.img, and their corresponding blocks on the eMMC, and I will add support to ReRun.
NOTE:
On several Straight Talk ZTE Phones, there are no Factory Restore Images, and FastBoot is disabled, meaning that if you boot loop, you have close to a 0% chance of recovery. BE CAREFUL!
Downloads:
v1.0: https://drive.google.com/file/d/0B1rm1VFiz_2FN1BXZWFBYzc2ZFU/view?usp=sharing
XDA:DevDB Information
ReRun Root/Write Protection Removal, Tool/Utility for all devices (see above for details)
Contributors
npjohnson, npjohnson
Version Information
Status: Stable
Current Stable Version: v1.0
Stable Release Date: 2015-05-25
Created 2015-05-25
Last Updated 2015-05-25
Reserved
Reserved
Thank you
Thanks @npjohnson
I downloaded this, read the read me, decided to try the script, a number of times. It kept copying to external sd, then internal when I removed external. I then tried the adb steps, went well until step 2.e. Guessed the partition for recovery, it seemed to be mmcblk0p16. Pasted that in for the next step and continued steps as listed in read-me. Finally seemed to work, so if this may help anyone. Thanks again.
Also, I believe to be able to write to system after these steps, you need to boot to pretend recovery, i.e. power off, volume up + power.
Update: Yes root is retained after shutdown/reboot. Busybox installs as does viper4android.
staypuft1652 said:
Thanks @npjohnson
I downloaded this, read the read me, decided to try the script, a number of times. It kept copying to external sd, then internal when I removed external. I then tried the adb steps, went well until step 2.e. Guessed the partition for recovery, it seemed to be mmcblk0p16. Pasted that in for the next step and continued steps as listed in read-me. Finally seemed to work, so if this may help anyone. Thanks again.
Also, I believe to be able to write to system after these steps, you need to boot to pretend recovery, i.e. power off, volume up + power.
Update: Yes root is retained after shutdown/reboot. Busybox installs as does viper4android.
Click to expand...
Click to collapse
Good to hear. What phone?
Sorry, it is the z796c zte majesty. Also forgot to mention copied the contents of payload folder to root of internal sd, other than script file.
Great job!
Doesn't work with ZTE's more tightly locked down phones though, such as Zinger, Whirl 2, Quartz, etc.
The recovery is write protected on these phones.... I'm working on the Quartz now, released in June of 2014.
ZTE saw this coming.
Good job though
Help.
npjohnson said:
Hey all,
Today I present you with Rerun Root for the ZTE Majesty!
Disclaimer
The usual. I am not responsible for any damage done by YOU to YOUR device. As always, anything can brick your phone! Be careful!
What is the ZTE Majesty?
It is an extremely cheap, low end 2013 phone that, honestly, very few people probably have.
Why are you making this?
ReRun isn't about this device in specific, the Majesty was just the only ZTE phone I had in hand. The vulnerability that ReRun relies on (Thanks to Justin Case & Beaups! Without them this wouldn't be possible) is present in nearly all ZTE devices! This allows you to reboot to a mode where Write Protection will be disabled, and it can be re-enabled with a simple reboot (Or not! Your choice!)
Does this work on a Locked Bootloader?
I can't speak for every device, but on most, yes. I.e. ZTE Max, ZTE Blade, ZTE Majesty
I want to port this to x ZTE device?
Read the readme in the attached .zip. It honestly isn't too complicated. If you have a device that you have tested it on that works, send me a PM with your Boot.img, Recovery.img, and their corresponding blocks on the eMMC, and I will add support to ReRun.
What Black Magic is this?
We are taking the boot partition (kernel, ramdisk, etc.) and writing it to the recovery partition, then rebooting to recovery. The reason this works is:
1. The Boot& Recovery images are signed in the same way by ZTE, meaning that the phones don't known the difference, they just see that the signature is valid.
2. When the recovery kernel is booted, it is booted with permission to re-mount system RW, side-stepping Write Protection.
How do I use this?
Open rerun.bat and follow the instructions, you will need to have temp-root (i.e. TowelRoot), and SuperSU installed before running the tool, though, it will walk you through all that.
Supported Phones:
As of now, only the Majesty, but like I stated above, PM your device's Boot.img, Recovery.img, and their corresponding blocks on the eMMC, and I will add support to ReRun.
NOTE:
On several Straight Talk ZTE Phones, there are no Factory Restore Images, and FastBoot is disabled, meaning that if you boot loop, you have close to a 0% chance of recovery. BE CAREFUL!
Downloads:
v1.0: https://drive.google.com/file/d/0B1rm1VFiz_2FN1BXZWFBYzc2ZFU/view?usp=sharing
XDA:DevDB Information
ReRun Root/Write Protection Removal, Tool/Utility for all devices (see above for details)
Contributors
npjohnson, npjohnson
Version Information
Status: Stable
Current Stable Version: v1.0
Stable Release Date: 2015-05-25
Created 2015-05-25
Last Updated 2015-05-25
Click to expand...
Click to collapse
I have been trying for mo the now and no luck still kinda new at this and wondering if someone can help me out and explain this to me step by step. Anyone please.
Convictking2 said:
I have been trying for mo the now and no luck still kinda new at this and wondering if someone can help me out and explain this to me step by step. Anyone please.
Click to expand...
Click to collapse
Are on a ZTE Majesty? If so, just run rerun.bat. If you aren't read the README in the .zip
npjohnson said:
Are on a ZTE Majesty? If so, just run rerun.bat. If you aren't read the README in the .zip
Click to expand...
Click to collapse
Yea I'm on the Majesty this phone has became so laggy it needs to be rooted to free it up
How do I get temp root I tried towelroot but it didn't work
So when someone gets the partitions and images from the Axxon Phone this exploit will work?!
XxAmyJo87xX said:
How do I get temp root I tried towelroot but it didn't work
Click to expand...
Click to collapse
What phone, what firmware, what android version?
ANDR01DN00B said:
So when someone gets the partitions and images from the Axxon Phone this exploit will work?!
Click to expand...
Click to collapse
Any ZTE phone made after October 2014 is likely not vulnerable
Sent from my Nexus 6 using Tapatalk
root Z796C ZTE Majesty
i have a ZTE Majesty Z796C, Android 4.1.2, Build # TF_US_Z796CV1.0.0B06, Hardware Version Z796CHWV1.0
is this the info you wanted i included a screen shot from my settings menu to help
XxAmyJo87xX said:
i have a ZTE Majesty Z796C, Android 4.1.2, Build # TF_US_Z796CV1.0.0B06, Hardware Version Z796CHWV1.0
is this the info you wanted i included a screen shot from my settings menu to help
Click to expand...
Click to collapse
Towelroot works. All firmwares shipped from the factory are the same. Are you suing the newest one from towelroot.com?
If yes, and its still happenening, uninstall your current TR, and try this one: https://www.androidfilehost.com/?fid=23681161096070831
If that version works, it isn't towelroots fault, its you Internet's fault.
Sent from my Nexus 6 using Tapatalk
Nope it didn't work ....root checker says no root (pic attached) ....superuser failed to install
Any chance that this could be supported for the ZTE Whirl 2 (Z667T or Z667G)?
Does this method work for the ZTE Prestige? Any help or info would me appreciated.
Got it to work! A few notes:
-After running towelroot and the .bat script, it will reboot. Pull the plug BEFORE it's able to reboot or you'll have to run towelroot/root checker and then proceed to the readme. Then go to your adb folder and type "adb shell", open the read me and start from there.
y= mmcblk0p16 and x= mmcblk0p8 (thanks to the other post who identified) (you'll know this step when you get to it).
I think the instruction manual was written wrong in the .bat file and OP. I've done this with three devices. Here's what it should really say:
(0. Enable usb debugging and allow install from all sources from developer options and security.)
1. Install towelroot, root checker, and supersu from apk/google play.
2. Run towelroot, gain temporary root, make sure it worked in root checker.
3. Open supersu, ignore whatever pops up. Go to settings and check default = enable, that way it wont bug you with prompts during the .bat file.
4. Open rerun.bat. Keep pressing enter, twice, you already did the prerequisites. If a message says write-disabled, you need to restart the phone and run towelroot again. Happened to me, too.
5. When the message comes up in the bat file that you're done, pull the usb cable or it'll reboot the phone.
6. If your phone rebooted: Wait for the phone to restart, plug the phone back in to the computer. Re-run towelroot and rootchecker to confirm.
7. If it didn't reboot, just plug it back into the usb port because you're fine.
7. Open the readme.txt.
8. Install mfastboot-v2 (with the two .dll files in the same package) to C:
9. Open a command prompt, go to C:/mfastboot-v2.
10. type 'adb devices' (without quotes) to make sure it shows up.
11. type 'adb shell' and you'll see a dollar sign.
12. Start by reading step #2 in the readme, type 'su', enter, and go from there...
(the X variable is 'mmcblk0p8' and Y variable is mmcblk0p16)
13. Reboot the phone 'reboot recovery'. If all went well, you'll be back to your start up screen within a minute.
14. Read step #5 in the readme. Run towelroot and rootchecker again. Then run supersu and update as normal. You should get a success message, and that's it.
I still can not gain temp. Root as is step 2. Run towelroot, gain temp. Root, check with root checker.
Well towelroot says I should have root but root checker still says the same as before no root. Per my earlier posts.
Any advice??
This guide is for never-rooted 2014 Fire HDs. Don't use it on any 2015 (5th gen) Fire. If your Fire has an sd card slot, go here.
Mar 3 Update: This guide is out of date. It could brick you! Don't use it!
Instead, follow one of these guides:
http://forum.xda-developers.com/fire-hd/general/root-os-5-1-2-kingroot-tools-play-store-t3371824
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Ignore these hidden text boxes
Feb. 5, 2016 Update: Don't use this to root OS 5.1.1 yet. It needs to be updated!!
Jan. 18, 2016 Update: Don't use this guide if you are running OS 4.5.5.1.
Look at Settings->Device->System Updates. If it says 4.5.5.1, installing the Developer Preview will brick your device.
Before You Begin:
OS 4.5.4, 4.5.5 (NOT 4.5.5.1) - Follow these steps to install the Developers Preview (OS 5):
Here are 2 methods. If you request it from Amazon it could take 24 hours, but if it causes problems you have proof that it downloaded to device. If you don't care about that and want it right now, use method 2.
1/23/16 UPDATE: Developers Preview is no longer available from Amazon. Method 2 is the only option.
Keep in mind, this is your choice. We can no longer blame Amazon for downloading "bad" firmware to device.
1/22/16 UPDATE: Use only method 2 until the risk of OTA updating to 4.5.5.1 is over.
METHOD 1 - From Amazon
Go here and request the developers preview: https://developer.amazon.com/public...campaign=FireOSPreview&sc_ detail=GetPreview]
It could take 24 hours but usually doesn't.
Goto Settings->Device->System Updates and press "Update Now"
If it doesn't download, wait an hour and try again.
METHOD 2 - From device
Turn OFF wifi.
Get update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin from here.
Copy/move the update file to device
Goto Settings->Device->System Updates and press "Update Now"
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go! Be sure to keep wifi off.
Note: If it hasn't booted after 20 minutes--it's stuck at "Fire" logo--hold down Power and Volume-up buttons to get to recovery menu. In recovery, factory reset, wipe cache and then boot to system.
OS 4.5.3 - Keep wifi OFF. Put the tablet into airplane mode immediately.
.
OS below 4.5.3 - Follow these steps to install OS 4.5.3:
Turn OFF wifi.
Download the 4.5.3 update to pc and copy/move it to device.
Go to Settings->Device->System Updates and press "Update Now."
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go!
Install adb device drivers. Here's an illustrated guide for Windows.
* OS 5.0.n: Install driver for both OS mode and sideload mode.
* OS 4.5.3: Install driver for OS mode only.)
.
If you don't know how to drag & drop or copy/paste into the terminal/CMD window, read this.
This guide simply pulls together existing material, almost none of which is original to me. All thanks go to Powerpoint45, who discovered how to downgrade to rootable OS 4.5.3; bibikalka for the ingenious recovery-swap update method that preserves root; seigesoldier, hawkazn and hariiiii for file captures and fearless testing.
A - Root!
Make sure ADB drivers are installed and adb is enabled in Developer Options.
Turn OFF wifi (airplane mode)
OS 4.5.3 - Download Kingroot (link below), open a terminal/CMD window from the folder you put it in, and go to step 6.
OS 5.0.n - Download to computer:
- 4.5.3 update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
- Kingroot: http://www.kingroot.net/
Downgrade to 4.5.3 (thanks to @powerpoint45):a. Connect to computer and open terminal/CMD window from folder containing bin file and kingroot.
b. Enter: adb reboot recovery
c. On tablet, use volume buttons to select “apply update from ADB” and then press power.
d. If you KNOW you have working adb driver for sideload mode, go to step e. Otherwise, see here:
To see if sideload-mode driver is installed, open Device Manager and see if your adb driver is listed under Android Device.
- If it is, close this text box and continue the steps.
- If it IS NOT and you're on Windows, do the following:
(1) Find KFARWI under "Other devices." NOTE: If you don't see KFARWI under "Other," disconnect/reconnect and look again.
(2) Right-click KFARWI and select "Update Driver Software." [see Update Driver Software screen].
(3) Click "Browse my computer" and then "Let me pick from a list . . ." [see Select your device type . . ."]
(4) Click Android Device. [see "Select the device driver you want . . .]
(5) Select your usual adb driver from the list, press Next, and say yes at warning screen. [see "Windows has successfully updated your driver software"]
(6) In CMD window, run adb devices and confirm you see your device ID and "sideload," like this:List of devices attached
SERIALNUMBER sideloadIf you don't see serial number, reboot tablet and computer and repeat "adb reboot recovery" and "Apply update from ADB" steps. Device should now be recognized.
e. From computer, enter: adb sideload update-kindle-20.4.5.3_user_453011120.bin
f. On tablet select "wipe data/factory reset" and then "reboot system" [long startup]
Enter language in Amazon setup, but skip registration and keep wifi OFF.
On computer, enter commands to block OTA:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Install Kingroot from computer: adb install app_filename.apk
Turn on wifi, run Kingroot on Fire and press "root." If you don't get success (100%), keep trying.Kingroot works over wifi, so do this where signal strength is best.
If the latest Kingroot from the link just won't work, try version 4.0.0 or 4.0.1 downloaded from any safe site.
On computer, give commands to confirm su access, granting root access on tablet when prompted:
adb shell
su
(In Windows, a # prompt indicates root.)
Type exit two times to get out of su.
B - Install TWRP and Get Files for the Upgrade
Download JMZ's ariel TWRP image to the Fire's download folder (or to computer and move to tablet).
Download Flashify v 1.9.1 to computer folder where you opened CMD window.
Install Flashify from computer: adb install app_filename.apk
Run Flashify on Fire and install the ariel TWRP.
If you have any question, follow the steps here. You must select Recovery image and Choose a File, and navigate to the ariel image.
Boot to recovery and confirm you're in TWRP:
adb command = adb reboot recovery; manual = power off, hold power & volume-up buttons until Amazon logo appears and then let go.
Tap Reboot, then System to boot back to OS.
Delete anything in tablet Download folder and get files for the upgrade.
.
Files for the Upgrade
Please hit Thanks when you pick up a file from an XDA site
Download apks to computer for later install.
- SuperSU: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
- ES File Explorer: http://www.apkmirror.com/apk/es-glo...file-explorer-4-0-2-3-3-android-apk-download/
Download to tablet (or to computer and move to tablet Download folder):
➜ Take care here: Be sure to get the right files and that they all download completely.
- 5.2.2u2 UPDATE BIN (linked in the post) This is update-kindle-full_ariel-20.5.2.2_user_522053520.bin
Confirm downloaded filename matches the above and then rename the extension from .bin to .zip.
- 5.2.0 STOCK RECOVERY ONLY (5.2.0_stock_recovery_only.zip - attached to post) AND . . .
- MAKE_SPACE (make_space_v01.zip - attached to post)
- Latest PICO-uni GAPPS: Get "tk_gapps-modular-pico-5.1.1(uni)-5.1.1-*-signed.zip"
C - Upgrade to OS 5.0.1 and Install Gapps
Bibikalka's Lollipop guide has info about the upgrade (and a Thanks button we all ought to hit!)
The boots into recovery and the OS can take a long time; don't interrupt them (by trying to manually reboot, e.g.)
Turn OFF wifi and connect to computer.
Boot to recovery. (Manually or "adb reboot recovery" from pc).
[TWRP screen displayed on tablet.]
In TWRP, do following exactly and if you have any problem, post immediately and wait for reply :
a. Factory reset (Tap Wipe and swipe "Swipe to Factory Reset." At "Successful," tap TWRP home icon at bottom-left)
b. Install the update-kindle-full_ariel-20.5.2.2 UPDATE zip
. . (Tap Install button, navigate to Downloads folder and tap the UPDATE zip. Repeat for the following zips.)
c. Install the 5.2.0 STOCK RECOVERY ONLY zip
d. Install the MAKE_SPACE zip
e. Install the GAPPS zip
f. Tap Reboot > Recovery and when prompted (top of screen) "install SuperSU?," swipe the slider to install it!
[long startup]
➜ You're now running rooted OS 5.0.1 and TWRP is gone. If you need it again, see here. Do not try to reinstall TWRP with Flashify. (Brick!)
Confirm you see stock 5.2.0 recovery.
If tablet doesn't boot to recovery or is still booting after 30 minutes, post in bibikalka's Lollipop thread
Reboot to system [takes at least 10 minutes] and when prompted on tablet to allow USB debugging, say "yes"
- If you miss "Allow USB debugging" prompt, unplug/replug to see it
- If tablet bootloops or is still booting after 40 minutes, see step 4 in bibikalka's Lollipop thread
At Setup screen, press Exit (or choose language if required). Do not connect to wifi; tap COMPLETE SETUP LATER.
D - Install the Apps, Block OTA and Open Play Store
On computer, open terminal/CMD window from folder containing ES File Explorer and SuperSU apks and install each with this command:
adb install -r app_filename.apk
On tablet:
a. Enable apps from unknown sources in Settings > Security.
b. Run File Explorer and enable Root Explorer (in menu under Tools), granting root access when prompted.
c. Run SuperSU to update binaries and reboot when prompted.
. . [If SuperSU gives choice of "CWM/TWRP" or "Normal," choose Normal]
Block OTA:
a. In the terminal/CMD window, enter these commands granting root access on tablet after the su command:adb shell
su
pm disable com.amazon.otaverifier
pm enable com.amazon.dcp <--(renables dcp from Section A. This block is not needed after you do the next step.)b. Use File Explorer on tablet to navigate to /system/priv-app/DeviceSoftwareOTA and rename extension of DeviceSoftwareOTA.apk to .apk_
Turn on wifi, open Play Store and sign in.
Register the Fire HD with Amazon.
Whew! Yay! :victory:
Some brave soul still needs to try to flash GAPPS during the 5.2.0 install in TWRP
If that fails, one will have to downgrade to 4.5.3, root, and get back to 5.2.0. So 20 minutes tops, not the end of the world ...
Yes, purposefully didn't put it in cuz untested. I'm thinking about it per your post at other thread. Just need to gird my loins
In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?
ROMAddiction said:
In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?
Click to expand...
Click to collapse
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."
DoLooper said:
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."
Click to expand...
Click to collapse
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root. I did say yes at step 3f and TWRP then installed a SuperSu Installer App. When you tap on the app it says it will install SuperSU but either from the Google Play Store or through TWRP. This is where I'm stuck because I can't install it from the Play Store or from TWRP, nor can I use ADB and install it from there because it says that SuperSu is already on my Fire.
Sent from my LG-H811 using XDA Forums Pro.
ROMAddiction said:
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root.
Click to expand...
Click to collapse
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
DoLooper said:
. . . Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk."
Click to expand...
Click to collapse
DoLooper said:
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
Click to expand...
Click to collapse
Ah, no I had been updated to 4.5.5 the other day and was wanting to roll back and root my Fire to make it much more useful to me. Signed up as a Developer to get it to update me to the 5.2 update and then followed the steps here to get me rooted and back to 4.5.3, etc.
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!
Sent from my LG-H811 using XDA Forums Pro.
ROMAddiction said:
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!.
Click to expand...
Click to collapse
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
Alright! When I get home tonight I'll complete the rest of the steps as best as possible.
Sent from my LG-H811 using XDA Forums Pro.
Hint: You can also flash tk gapps in twrp
meganoahj said:
Hint: You can also flash tk gapps in twrp
Click to expand...
Click to collapse
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.
DoLooper said:
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.
Click to expand...
Click to collapse
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)
meganoahj said:
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)
Click to expand...
Click to collapse
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
@bibikalka will also be glad to hear this! Thanks!
DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
When I perform: option: adb shell
su
It returns 1|[email protected]:/ $
I'm going to try "option: adb install -r name_of_your_supersu.apk" here and see if that makes a difference.
Edit: That did it! SuperSu installed, Google Play Store/Services installed, and I'm good to go.
DoLooper said:
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
@bibikalka will also be glad to hear this! Thanks!
Click to expand...
Click to collapse
Yes i got gapps from There
Gapps: Pico Modular Package (Proper DPI Play Services)
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!
Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long
meganoahj said:
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!
Click to expand...
Click to collapse
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
meganoahj said:
Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long
Click to expand...
Click to collapse
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)
Other than Kingroot taking forever and Xposed refusing to flash in TWRP everything went great and I was finally able to install all my apps from the Play Store on my wife's tablet following this guide.
Many thanks!
DoLooper said:
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)
Click to expand...
Click to collapse
With gapps + xposed is 49.8 mb free in /system
I had the upgrading screen also without an Module
Hello, guys this is my first post but i am quite sure that my methods work.If there any problems then u can surely ask in the section below. This thread will be a GUIDE TO ROOT AND INSTALL CUSTOM RECOVERY FOR MOTO G 1st Gen users.
Some prerequisites are:
1. Motorola drives (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481)
2.Fastboot and recovery files (https://www.dropbox.com/sh/9jf2va51ffg0pzq/AAAxDT-ETf7AESIcHGnfEgv7a?dl=0)
[ Let these files be downloaded and kept in Cdrive of ur pc and and place them on the desktop.. Please name this folder MOTO FILES]
3. SuperSu files https://download.chainfire.eu/696/supersu/ and[/url] paste it in ur phones internal memory and please do this after unlocking the bootloader cause bootloader unlocking will delete everything so its better to do it after unlocking bootloader
Download these files and ur done... Now lets continue to the fun part
This process involves three very simple steps :
1. Unlocking the Bootloader:-
This process is infact very easy to do. There are several guides on the internet regarding this process but the one that i suggest is by High On Android/ Max Lee . Follow his method and u can very easily unlock ur bootlader. Copy this url and see it for urself fellow guys...http://highonandroid.com/android-smartphones/how-to-unlock-bootloader-on-motorola-android-smartphone
2. Erasing ur previous recovery and installing a new one and rooting ur phone all in one process
Some users have been reporting that even after installing custom recovery , whenever they go into recovery they enter into stock recovery. The actual problem is that the stock rom of the Moto G rewrites over the new custom recovery installed.
So we have to install the recovery actually twice but it only takes a few minutes
i) Firstly be sure to have lots of juice in your phone
ii) Boot ur phone into the bootloader by power offing ur device and then pressing the volume down and power button together for 10 seconds and then leaving both of them together.
iii) Now connect ur device to ur pc/laptop
iv) Now open a cmd and enter the following commands(press enter after every command)
- cd Desktop
-cd MOTO FILES
-fastboot flash recovery Recovery2.img
-fastboot reboot-bootloader
[MAKE SURE NOT TO REBOOT UR DEVICE ]
v) Now ur phone has custom recovery installed in it and u shud now enter into recovery mode by choosing the option from the bootloader, by pressing volume down and then volume up while in bootloader mode.
vi) This will open the Philz recovery that i have provided with. I prefer the philz recovery over the cwm one. Now go on and install the SuperSu update zip file. And BOOM ur Device is now rooted !!!!.
vii) Now reboot ur phone and u must install
-ROOT CHECKER (to check root)
- and most importantly ROOT EXPLORER
viii) After following step (vii), now if u try to go into recovery, u will be booted to stock recovery. So to prevent that use the ROOT EXPLORER app and go to the root \system\etc and delete the file named install-recovery.sh .
ix) After deleting the file u will once again have to follow step (iv) and install custom recovery this will ensure u having custom recovery even after rebooting ur device and u will have ROOT access as well
On which android version , were you on before rooting . 5.01 or 5.1 .
This method works for both 5.1 and 5.01
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Is the first post too heavy for you?!
Follow the steps and be happy.
Gesendet von meinem Moto G mit Tapatalk
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Andus1988 said:
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Click to expand...
Click to collapse
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Ajay P said:
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Click to expand...
Click to collapse
whats the problem u facing ?
sanilch99 said:
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Click to expand...
Click to collapse
It could cumber the inbuilt root!
sanilch99 said:
whats the problem u facing ?
Click to expand...
Click to collapse
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Ajay P said:
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Click to expand...
Click to collapse
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
sanilch99 said:
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
Click to expand...
Click to collapse
Thank you
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
notuger said:
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
Click to expand...
Click to collapse
I will recheck that super su. file and make sure its perfect... Thanks for the response:good:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Works but could be simplified
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
issam029 said:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
i have edited the previous link and given the new one. You can use this SU file. It will solve ur prob.
pcgardner said:
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
Click to expand...
Click to collapse
Reinstallation of custom recovery is not must its just for safety precautions and I have finally updated the SuperSu link. As far as Busybox u will have to install it customly only.
issam029 said:
once i finished steps all, when i open supersu, popup window says, "there is no su binary installed, and supersu cannot install in it. This is the problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
If i check with root checker,
sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
use the new su files i updated the link
facing problem after unlock bootloader mood for moto g 1st gen
Thanks a lot for your information...:good:
Bro!! I have already unlock bootloader mood.. Before rooting is it necessary to clear all data & app...??