Related
All attempts that I have made to root this Kindle Fire on 6.3.3 have failed. KFU fails. Towelroot fails. Nothin.
Ok so I was at least able to use a factory cable to put the kindle into fastboot mode. After that I was able to flash FFF and TWRP and then flash a stock 6.3.2 Rom which is rootable.
Also you can install custom rom from this point. Not exactly succeeding and rooting stock 6.3.3 but its a start.
Kafluke said:
Ok so I was at least able to use a factory cable to put the kindle into fastboot mode. After that I was able to flash FFF and TWRP and then flash a stock 6.3.2 Rom which is rootable.
Also you can install custom rom from this point. Not exactly succeeding and rooting stock 4.3.3 but its a start.
Click to expand...
Click to collapse
Please post steps in flashing firmware 6.3.2. I'm not sure if I'll be able to go back though, because I reset to factory settings before I realized that the firmware had updated.
Kafluke said:
Ok so I was at least able to use a factory cable to put the kindle into fastboot mode. After that I was able to flash FFF and TWRP and then flash a stock 6.3.2 Rom which is rootable.
Also you can install custom rom from this point. Not exactly succeeding and rooting stock 4.3.3 but its a start.
Click to expand...
Click to collapse
So how are you preventing it from taking another OTA of 6.3.3?
has anyone figured out the root for kindle fire on 6.3.3
jblindy said:
Please post steps in flashing firmware 6.3.2. I'm not sure if I'll be able to go back though, because I reset to factory settings before I realized that the firmware had updated.
Click to expand...
Click to collapse
Here's what I did:
1. Download stock firmware 6.3.2 (latest KFU will get it for you)
2. Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)
3. Download TWRP 2.2.2.1 from here. (thanks sd_shadow).
4. Download latest FFF using KFU
5. Put TWRP and FFF into a folder on your computer that contains fastboot.exe
6. Make a factory cable (google "make Motorola factory usb cable") or you can buy a premade one or an adapter. Here's an example.
7. Turn off your Kindle fire and unplug it from your computer.
8. Plug one end or your factory cable into your computer.
9. Open a windows command prompt from the folder with fastboot.exe in it.
10. While the Kindle Fire is turned off, plug in the other end of your factory cable into the Kindle fire. This should throw the KF into fastboot mode.
If you have created the factory cable correctly you should see the red Kindle screen but it should stay there and you should get a new driver install notification in Windows. Install the driver for the Kindle Fire bootloader.
11. From your Windows command prompt run these commands (substituting the names for whatever your TWRP and FFF files are called)
Code:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 flash bootloader fff.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Now you should see the FireFireFire blue screen and you can push the power button to boot into TWRP. From TWRP you can wipe everything and install the 6.3.2 file you placed on the Kindle Fire earlier (if you want to flash a KitKat ROM like CM11 or others then you must re flash recovery with latest TWRP from here). After you are using 6.3.2 you can run latest KFU and it will work just fine.
So how are you preventing it from taking another OTA of 6.3.3?
Click to expand...
Click to collapse
I don't know how to prevent it. Maybe its best to just flash CM11 on it.
Cool.....thanks!
Kafluke said:
From TWRP you can wipe everything and install the 6.3.2 file you placed on the Kindle Fire earlier.
Click to expand...
Click to collapse
Unless newest Twrp is different, only Twrp 2.2.2.1 or lower can install stock kindle firmware. Other TWRP versions will bootloop the Kindle Fire, and Twrp will need to be flashed in bootloader
sd_shadow said:
Unless newest Twrp is different, only Twrp 2.2.2.1 or lower can install stock kindle firmware. Other TWRP versions will bootloop the Kindle Fire, and Twrp will need to be flashed in bootloader
Click to expand...
Click to collapse
Correct or cannibal open touch recovery but it won`t flash Kit Kat.
sd_shadow said:
Unless newest Twrp is different, only Twrp 2.2.2.1 or lower can install stock kindle firmware. Other TWRP versions will bootloop the Kindle Fire, and Twrp will need to be flashed in bootloader
Click to expand...
Click to collapse
Well, whatever KFU .99 downloaded, that's what I flashed. And it worked. I don't have the Kindle anymore to check TWRP version .
I don't want anyone bricking their fire because of my steps though. I'll edit the post. Thanks sd_shadow!
KFU will download latest twrp the first time you select install twrp, after that will install same version, and will not check for update, unless you remove twrp.IMG from folder.
Sent from my Amazon OtterX using Tapatalk
Has OTA root keeper been tried? Voodoo or Superuser option. It needs to be backed up before update is installed
need help with a stock 6.3.3
Ever since my wife asked me to try to root her stock 1st generation Kindle Fire (currently running 6.3.3), I have had a hell of a time trying to get this thing rooted. I will also admit that I am a relative newbie when it comes to rooting devices. I am perfectly comfortable doing a few tweaks here and there, even through using command-line tools, but this is my first attempt at trying to root a device. I have both my MacBook Pro OSX (Mavericks) laptop and my Windows 7 desktop at my disposal, but I have only been able to make limited progress in rooting the KF.
I have used a number of tools (which I realize are mostly variants of one another): Kindle Fire Utility 0.9.9, RootKindleFire631 (from RootKindleFire.com), Breakdroid, and KindleFireRootMacLinux (which basically uses the ZergRush method). All to no avail. The most common error that I get is "Couldn't write bp1, panic". Hope this helps some developers out there to finally find a feasible rooting method for this one.
Curse you, Amazon, you may have won this round, but the war is far from over!
I created a prerooted 6.3.3 update that can be installed in twrp.
I have Installed with 2.2.2.1 and 2.7.1.0 versions of Twrp
Didn't change much,
I replaced stock install script with tobiascuypers' install script from [Rom] Stock 6.3.2 [Mods] [04.22.13] [Primary/Alt]
Added Root files (busybox, su, SuperSU)
Added Google Apps (Framwork, Play Store, Calendar, Google Voice, Google +)
Added other apps (Root Browser, Go Launcher, Facebook)
Instructions
Download update-kindle-prerooted.6.3.3.v1.zip, place on sd card, wipe data (may be optional), install with TWRP
wipe cache, reboot, may take a few mins to boot first time.
Tested Google play (signed in, downloaded apps)
Didn't test amazon sign in.
Edit; see my [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only thread
sd_shadow said:
I created a prerooted 6.3.3 update that can be installed in twrp.
I have Installed with 2.2.2.1 and 2.7.1.0 versions of Twrp
Didn't change much,
I replaced stock install script with tobiascuypers' install script from [Rom] Stock 6.3.2 [Mods] [04.22.13] [Primary/Alt]
Added Root files (busybox, su, SuperSU)
Added Google Apps (Framwork, Play Store, Calendar, Google Voice, Google +)
Added other apps (Root Browser, Go Launcher, Facebook)
Instructions
Download update-kindle-prerooted.6.3.3.v1.zip, place on sd card, wipe data (may be optional), install with TWRP
wipe cache, reboot, may take a few mins to boot first time.
Tested Google play (signed in, downloaded apps)
Didn't test amazon sign in.
Click to expand...
Click to collapse
Does this require a factory cable?
Xeddicus said:
Does this require a factory cable?
Click to expand...
Click to collapse
if 6.3.3 is installed already yes a fastboot cable is needed to install fff bootloader and twrp.
If 6.3.2. Is installed, use kindle fire utility, to install bootloader and twrp.
Sent from my XT894 using Tapatalk
@sd_shadow - Installed fine with only dalvik / cache wipe over existing 6.3.3 (I removed most of the 3rd party apps prior to install).
Probably deserves it's own thread in development.
First thing I did was freeze OTASilentInstall.apk in /system/app/. I may consider removing it completely in the future.
Thanks for this. :good:
overground said:
@sd_shadow - Installed fine with only dalvik / cache wipe over existing 6.3.3 (I removed most of the 3rd party apps prior to install).
Click to expand...
Click to collapse
If I make a new version I will remove updater, and maybe all the extra apps other than play store, and ones need for root (supersu, binary, and busybox),
Probably deserves it's own thread in development.
Click to expand...
Click to collapse
Yes thought I would start a thread in Dev, but wasn't sure about the new General Public License rules (posting sources like the kernel), most of the devices I follow have it stickied in the dev section, but I see it is not in Kindle dev section?
First thing I did was freeze OTASilentInstall.apk in /system/app/. I may consider removing it completely in the future.
Thanks for this. :good:
Click to expand...
Click to collapse
I hadn't really looked for the updater apk, so that will help.
Thanks for the feedback
sd_shadow said:
Yes thought I would start a thread in Dev, but wasn't sure about the new General Public License rules (posting sources like the kernel), most of the devices I follow have it stickied in the dev section, but I see it is not in Kindle dev section?
Click to expand...
Click to collapse
You're not modifying the kernel, therefore there is no source (or changes) to post. GPL does not apply in this case.
Just specify in your thread that the ROM contains the stock, unmodified Amazon kernel.
If anyone beefs you on it, you can point them to this post.
overground said:
You're not modifying the kernel, therefore there is no source (or changes) to post. GPL does not apply in this case.
Just specify in your thread that the ROM contains the stock, unmodified Amazon kernel.
If anyone beefs you on it, you can point them to this post.
Click to expand...
Click to collapse
Thanks Posted here [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
This is merely a guide, I do not take credit for any methods or apps listed below. I am not a developer. The great people working on these apps and methods deserve all the credit and your donations, so please disparse accordingly.
BIG THANKS to @iKrYpToNiTe, @jcase, @geohot who worked on these apps. Also thanks to @mschumacher69 for some constructive discussions.
YOU AGREE BY PERFORMING ANY OF THE ACTIONS BELOW THAT I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE. EVERY DISCLAIMER STATED ON THE LINKS PROVIDED IS STILL 100% VALID.
A RECAP OF THOSE DISCLAIMERS IS THAT YOU WILL VOID YOUR PHONE'S WARRANTY AND NOONE ELSE BUT YOURSELF ARE RESPONSIBLE IF YOU DAMAGE YOUR PHONE!!!
I decided to compile a root guide for the Cricket variant of the Moto G falcon xt1032 running 4.4.2 (may work on other variants as well, not sure). I obtained full, permanent root with philz touch recovery (but it would work for any other recovery you may choose to use).
THIS METHOD DOES NOT REQUIRE A COMPUTER/PC/MAC/LINUX USB CONNECTION
1. Enable USB debugging
2. From the setting tab "security". Check the " unknown sources" box, so you can install apk outside of play store
3. In addition to all things below, you will need a file explorer. I find es file explorer to be the golden standard, but your preferred file manager will do
4. This Link below is for you to install towelpieroot.apk
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059.
The version 1.2 supports the xt1032 falcon. Big thanks to @iKrYpToNiTe for adding support for the Moto G! You will need this temporary or "tethered" root before you go to the next step, which is unlocking the bootloader with this app called Sunshine (link to thread given below). Towelpieroot is buggy at times, but if it doesn't work the first time, try a few more. It WILL work.
5. http://theroot.ninja/
Note that running Sunshine is not free, but the $25 is well spent! Just so you know, Sunshine will NOT charge you if the process fails.
6. After the bootloader is unlocked, UNINSTALL towelpieroot. This is important in order for you to proceed to the next step.
7. Once you unlock the bootloader, you need to run towelroot (link below)
https://towelroot.com/
This step will grant you full, permanent root. Tap on the "welcome to towel root V3" three times, then you should see a box where you can modify the modstring. By experimentation and trial, I found the modstring 1337 0 0 0 4 0 to be the one. Click "Make it ra1n" and you should have permanent, full root privileges!!!
8. Download your favorite root checker to verify root access!
9. Go to play store and install SuperSU, and do any necessary updates.
10. Go to play store and install busybox and do all necessary binary updates.
11. Go to play store and download a terminal emulator. This will aid you in flashing your recovery.
12. My personal preference is Philz Touch recovery, but I think it it fair to assume that any compatible recovery of your choice is appropriate to flash with this method (link below)
http://forum.xda-developers.com/showthread.php?t=2639583
Download the latest .IMG from the OP
13. Before you flash you may want to back up your stock recovery.
Open the terminal emulator.
(do not include quote marks, only what's inside them, including spaces)
Type "su" and hit the ENTER key
This will get you superuser access
Type "dd=if/dev/block/mmcblk0p32 of=/sdcard/stock-recovery-backup.img"
This will create a backup of your current STOCK recovery.
14. Now ,using your file manager, go to the philz touch recovery .img file you just downloaded and rename it into "recovery.img", then move it to the sdcard folder (storage root folder)
Note: there you should also see the backup recovery file "stock-recovery-backup.img" you just created
15. Open the terminal emulator
Type "su" to gain superuser access
Type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32
16. THAT'S IT!!!
Verify by powering off your phone, hold volume down and power button for 5 seconds, select recovery and you should have Philz touch recovery in your phone.
NEXT LOGICAL STEP WOULD BE TO BACKUP YOUR STOCK FIRMWARE IMMEDIATELY!
BE MINDFUL WHEN YOU HOP BETWEEN ROMS THIS PHONE HAS ONLY AN INTERNAL STORAGE, SO BE CAREFUL WHAT YOU FORMAT
Other than that, whoohoo!!!!
NOTE: ACCORDING TO SOME DEVS I HAVE COME ACROSS ARE TELLING ME STEP 7 IS NOT NECESSARY. YOU CAN TRY SKIPPING IT. UNFORTUNATELY MY BOOTLOADER AND ROOT ARE IN EFFECT, THEREFORE I CANNOT VERIFY THIS. YOU COULD TRY[emoji3]
Please, when you need app-specific support, you may get better answers in the respective forums, but don't be discouraged posting questions here. It took me great effort finding a way to root without a PC, and although i am not a developer, I have stumbled in enough obstacles to be of some assistance
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
mschumacher69 said:
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
Click to expand...
Click to collapse
Yes that is true if you wanna fastboot via USB, which means connecting the phone to a PC. I was under the impression that I could not flash a custom recovery from the stock one. I have been struggling to gain root because of non-access to a computer. It is a little more lengthy but I find this to be the only no PC guide around, since I've been looking for one for 4 months now. And most certainly I would not be able to flash a recovery from the terminal emulator if I did not have su.
Towelpieroot only gives a tethered, temp root with no r/w privileges to system. It would make it impossible to flash a recovery from the terminal without gaining full root. This is why you need to run the original towelroot with the modified modstring.
REMINDER: THIS METHOD DOES NOT REQUIRE A USB CONNECTION WITH A COMPUTET. ITS ALL DONE ON THE PHONE.
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
lmf said:
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
Click to expand...
Click to collapse
Towelpieroot is buggy (the dev states in his post). I had to try the process numerous times. What i think may work (or may have worked). Is you have to make sure that before running towelpieroot again youbhave to clear it from the recents. What i have done was clear it from recents, uninstall. Reboot phone. Install and run again. Once you get temp root you can continue the process.
On towelroot v3. It will say your device is not supported. Tap on "welcome to towelroot v3" twxt three times and a modstring modification box will appear showing numbers. Input the modstring posted above in the OP "1337 0 0 0 4 0" (with the spaces). Then it will give you root
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
BBobby said:
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
Click to expand...
Click to collapse
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
mschumacher69 said:
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
Click to expand...
Click to collapse
Would it be OK to download super su from play store directly?
BBobby said:
Would it be OK to download super su from play store directly?
Click to expand...
Click to collapse
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
mschumacher69 said:
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
Click to expand...
Click to collapse
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
Click to expand...
Click to collapse
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
mschumacher69 said:
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
Click to expand...
Click to collapse
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
BBobby said:
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Click to expand...
Click to collapse
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
mschumacher69 said:
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
Click to expand...
Click to collapse
Do you even read the posts? I have not had a PC or access to one (yes, people like me exist). I have looked for months on end and once I came across towelpieroot it all became possible. Then jcase released sunshine and that all put it together in a working method. This is the collection of hour of searching. If anyone like me does not have PC access it is still possible. But I wouldn't want others to have to go through that frustration
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Thanks for the useful guide.
Once you do all of this what can be done . Does this mean the device is carrier free or just allows to install any variant of android on it.
Also even after doing all of these things how one can activate it on a different network than it is bought to be used on.
Sorry i am newbie to flashing software.
Thanks
Mars
This is a guide to root this device. That means you have access to the operating system files. By getting this access it allows you to modify the system in many ways. It also allows you to install custom ROMs. Gaining root has so many uses I cannot list here.
But no, this is not a carrier/SIM unlock.
How about the 4.4.4 cricket XT1046 seems to be impossible at this point?
When I get to the step on gaining temporary root it just keeps loading and loading and it never gives me root.. Like I went on and off multiple times and it still won't work
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
Click to expand...
Click to collapse
Rashr needs root to flash images and zips
Edit: I didn't saw that you already have been answered
Recently released is the ONE-CLICK root and temporary custom CWM recovery for Asus Zenfone 2 ZE551ML & ZE550ML & ZE500CL
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
and to the maker of the original Intel temporary CWM: @social-design-concepts Thread
Method 1: ONE-CLICK root
Download the Asus Zenfone quick one-click root package
Unzip the package
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to download and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'Root_zenfone.bat'
To unroot, use 'xoa_root' or unroot through SuperSU in Android
Bam, done.
------------------------------
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
Download the Asus Zenfone temporary CWM package
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to download and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Easy, thanks!!!! :laugh:
with it, is possible run Asus update without bootloop?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
Working
working perfectly.
Getting more than 3GB RAM after removing preinstalled bloatware on the latest 2.17.40.12 ROM.
jaganathsamal said:
working perfectly.
Getting more than 3GB RAM after removing preinstalled bloatware on the latest 2.17.40.12 ROM.
Click to expand...
Click to collapse
great:good:! what is your software for uninstall that?
Used system app remover for removing preinstalled apps
Sent from my ASUS_Z00AD using XDA Free mobile app
Back in business.
Note, if you root and do OTA update after the root, you may end up in a boot loop/soft bricked. Unroot prior to OTA and reroot again after OTA may avoid this issue, but haven't tested yet.
Is this method working for ze500cl also ?
Hi, i have a zenofone 2 ze500cl, will this method work also on my device ?
Neemia86 said:
Hi, i have a zenofone 2 ze500cl, will this method work also on my device ?
Click to expand...
Click to collapse
Hello man. I'd read through this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and see if anyone's ran into any serious complications. If it were me, I'd try it. But be prepared for it to not work out.
Chinaphonearena said:
Note, if you root and do OTA update after the root, you may end up in a boot loop/soft bricked. Unroot prior to OTA and reroot again after OTA may avoid this issue, but haven't tested yet.
Click to expand...
Click to collapse
If you update SuperSU binaries, yes you will bootloop on OTA.
You have two options to update:
1: Unroot > Take OTA > Root
2: Flash Pre-Rooted system.img > Keep root with no unroot needed
Harfainx said:
If you update SuperSU binaries, yes you will bootloop on OTA.
You have two options to update:
1: Unroot > Take OTA > Root
2: Flash Pre-Rooted system.img > Keep root with no unroot needed
Click to expand...
Click to collapse
Even if using the latest SU binaries via this method and then OTA, will end up soft-bricked. The 2nd method can't update binaries. Need to stick with the binaries in the pre-rooted ROM. Either way (1. Unroot, OTA, reroot or 2. Pre-rooted ROM and never update SU) are both solid methods.
Chinaphonearena said:
Even if using the latest SU binaries via this method and then OTA, will end up soft-bricked. The 2nd method can't update binaries. Need to stick with the binaries in the pre-rooted ROM. Either way (1. Unroot, OTA, reroot or 2. Pre-rooted ROM and never update SU) are both solid methods.
Click to expand...
Click to collapse
I have updated my SuperSU and flashed the Pre-Rooted over my current without any problem. No bootloop at all.
The simple method is just like all other devices. If you're rooted, don't take an OTA. Wait for a rooted build.
Harfainx said:
I have updated my SuperSU and flashed the Pre-Rooted over my current without any problem. No bootloop at all.
The simple method is just like all other devices. If you're rooted, don't take an OTA. Wait for a rooted build.
Click to expand...
Click to collapse
You misunderstood, yes if you flash the entire pre-rooted system over it, you will be fine. I was referring to OTA.
Whats simple for some may be a chore for others. You download and flash 1gb to update. If that works best for you, by all means it's a fine way to go.
This one didn't work for me, nor did the other one. The same thing happened as with the other, I get to where I type "T4" and it won't take it. I have already done all the OTAs if that makes a difference.
Anyone know if this method will also work on Asus Memo Pad 7?
kanagawaben said:
Anyone know if this method will also work on Asus Memo Pad 7?
Click to expand...
Click to collapse
I would suggest searching/asking that here: http://forum.xda-developers.com/android/help/qa-intel-android-devices-root-temp-cwm-t2975462
That's the QA thread for the CWM stuff.
Trotter516 said:
This one didn't work for me, nor did the other one. The same thing happened as with the other, I get to where I type "T4" and it won't take it. I have already done all the OTAs if that makes a difference.
Click to expand...
Click to collapse
User error. My bad. I am good now.
This root worked for me!
this method, temporary CWM, can it be used to flash other zip file? such as viper4android-lollipop or gapps flashable zip file?
Hello everyone. I have successfully rooted Lollipop 5.0.2 for VERIZON LG PAD 8.3 VK810 without downgrading.
PREREQUISITES
-Updated drivers installed
-turned on usb debugging
- Supersu installed from playstore
STEPS
More specifically HERE
Now the English version stands at 2.2.1 while Chinese is still at 1.85
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user.
IF ABOVE FAILS
1.Install KingoRoot as well
http://www.kingoapp.com/
2.After running iRoot, run KingoRoot. Wait about 5-8 minutes as it would go on forever. Close it afterwards.
3. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser
3. Download supersu from here and install its apk. Upgrade binaries and uninstall kinguser.SUPERSU BETA 2.49
The apk file is located in the zip
If binary upgrade fails, try2.48 version. Link given below.
You should be rooted with Supersu.
If it fails to upgrade binaries.
.Flash aboot 4.2.2 to flash twrp 2.7.0.1. Instructions given Here on my guide
.Update Twrp to 2.7.1.0. FROM HERE
.Reboot into recovery via twrp menu
. Flashed SuperSu 2.48beta via twrp.
https://download.chainfire.eu/735/SuperSU
. Flash aboot 5.0.2 via twrp from HERE
Clear cache and wipe dalvik via recovery (twrp)
Reboot.
Done!
CHECK HERE FOR OTHER INSTRUCTIONS AND PROOF
UPDATE
LATELY I HAVE SUCCESS WITH KINGROOT APK for rooting devices.
Download apk from here and report back
http://www.kingroot.net/
XDA LINK TO KING ROOT
@imilleson
KingoRoot 4.62 worked on my Verizon LG GPad 8.3 (vk810) with sim card running Android 5.02 - at first it said failed but proceed after that point and it succeeds.
Click to expand...
Click to collapse
Credits
@roirraW "edor" ehT for his aboot 5.0.2 and innumerous suggestions
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSu! [MENTION=2282431]
twrp team
@Drgravy for bringing tarp to this device
@KyPbP for providing the kdz file in a jiffy.
@DeanGibson for his valuable feedback and testing my guide @imilleson for confirmation that kingroot works on lollipop!
Anyone else I forgot?
FAQs
1.I flashed 2.48beta via twrp. Did not try version 2.48 or 2.49 apk to update supersu binaries.
2. Supersu 2.46 from play store failed. Even flashing 2.46 failed via twrp
Hnk1 said:
Credits
@roirraW "edor" ehT for his aboot 5.0.2 and innumerous suggestions
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSu! [MENTION=2282431]
twrp team
@Drgravy for bringing tarp to this device
Anyone else I forgot?
Click to expand...
Click to collapse
Maybe the guy who made us aware the KDZ was available. Without that I couldn't have gotten the ROM out so quickly.
RE: Step 12 - Does TWRP survive the updated aboot flash?
w0rdie said:
RE: Step 12 - Does TWRP survive the updated aboot flash?
Click to expand...
Click to collapse
No it doesnot survive it as TWRP is not compatible with aboot 5.0.2. I am sure developers are looking into it
roirraW "edor" ehT said:
Maybe the guy who made us aware the KDZ was available. Without that I couldn't have gotten the ROM out so quickly.
Click to expand...
Click to collapse
Added him as well to credits post
Even simpler!
Hnk1 said:
Hello everyone. I have successfully rooted Lollipop 5.0.2 for VERIZON LG PAD 8.3 VK810 without downgrading.
PREREQUISITES
-Updated drivers installed
-turned on usb debugging
STEPS
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2. [Install KingoRoot -- not needed]
3.Run iRoot app from PC. Wait till it is complete. You will have partial root but some system cleaner app with King user. Do not do anything
4. [Run KingoRoot -- not needed]
5. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser.
...
Click to expand...
Click to collapse
The above is all I needed to do, to root my two VK810 tablets. I had SuperSU already installed on both tablets, but it didn't want to successfully update its binary ("su"), so I uninstalled SuperSU and kept "KingUser", the equivalent tool that comes with iRoot.
w0rdie said:
RE: Step 12 - Does TWRP survive the updated aboot flash?
Click to expand...
Click to collapse
Just to be clear, TWRP itself is still there when you have the 35A_08 aboot flashed, the new bootloader just won't let you boot into recovery. To get back into it temporarily you just have to flash the 4.2.2 aboot, then when you're done in TWRP and want to boot the ROM again, you can flash the 35A_08 aboot that I provide in zip flashable format in my ROM thread in Development. I also provide a mirror of the 4.2.2 aboot and instructions for everything.
If you forget to re-flash the 35A_08 aboot before leaving TWRP, the only symptom is the ROM won't boot. Just use the hardware keys (volume down and power buttons held in) long enough (about 10 seconds) to manually boot back into recovery (choose Factory Reset from the regular recovery menu, which takes you into TWRP).
Hnk1 said:
No it doesnot survive it as TWRP is not compatible with aboot 5.0.2. I am sure developers are looking into it
Click to expand...
Click to collapse
DeanGibson said:
The above is all I needed to do, to root my two VK810 tablets. I had SuperSU already installed on both tablets, but it didn't want to successfully update its binary ("su"), so I uninstalled SuperSU and kept "KingUser", the equivalent tool that comes with iRoot.
Click to expand...
Click to collapse
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much. I'll update the guide , thanks for your feedback. If you wish to try, uninstall supersu from Google play, install supersu from links I provided (not available in market yet)using apk and then try upgrading your binaries. See what happens.
@roirraW "edor" ehT
Many thanks for clarification.
Hnk1 said:
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much. I'll update the guide , thanks for your feedback. If you wish to try, uninstall supersu from Google play, install supersu from links I provided (not available in market yet)using apk and then try upgrading your binaries. See what happens.
@roirraW "edor" ehT
Many thanks for clarification.
Click to expand...
Click to collapse
You're welcome!
Re: SuperUser, I agree with you. Hesitant to trust anything but SuperSU until I do more research.
roirraW "edor" ehT said:
Just to be clear, TWRP itself is still there when you have the 35A_08 aboot flashed, the new bootloader just won't let you boot into recovery. To get back into it temporarily you just have to flash the 4.2.2 aboot, then when you're done in TWRP and want to boot the ROM again, you can flash the 35A_08 aboot that I provide in zip flashable format in my ROM thread in Development. I also provide a mirror of the 4.2.2 aboot and instructions for everything.
If you forget to re-flash the 35A_08 aboot before leaving TWRP, the only symptom is the ROM won't boot. Just use the hardware keys (volume down and power buttons held in) long enough (about 10 seconds) to manually boot back into recovery (choose Factory Reset from the regular recovery menu, which takes you into TWRP).
Click to expand...
Click to collapse
I appreciate the clarity. :good:
I agree with the sentiment
roirraW "edor" ehT said:
...
Re: SuperUser, I agree with you. Hesitant to trust anything but SuperSU until I do more research.
Click to expand...
Click to collapse
I agree with the sentiment. I did uninstall SuperSU 2.46 and then sideload SuperSU 2.49, and it still had problems updating its binary. SuperSU even detected that there was another "root management" (my term) app installed, and offered to uninstall it. I let it try, and that failed as well. So, I will wait for a report of a successful conversion to SuperSU.
I did originally try Kingo Root (per the OP's instructions) on the 1st tablet, and that got me another "root management" app installed, so now I had three (before I uninstalled SuperSU)! It also installed something on the 1st tablet that Google warned me was a security risk, so after the 2nd tablet rooted with just iRoot, I did a factory reset on the 1st tablet and just used iRoot.
Both iRoot and its "root management" app KingUser seem well-written, surprising (at least to me) from a region not known for well-written, easy to use software.
---------- Post added at 09:42 AM ---------- Previous post was at 09:25 AM ----------
Hnk1 said:
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much....
Click to expand...
Click to collapse
Unfortunately, once you install anything with root privileges, who knows what it left behind. KingoRoot in particular left around several apps with no app icon, that KingUser listed and I was able to uninstall. However, that left me with an uneasy feeling, which is why I did a factory reset on the 1st tablet and started over.
I'd rather trust what one Chinese/Korean app left around (which I have to, if I use iRoot), rather than two.
iRoot does install two other apps, one is the "Cleaner", and another is part of the download process, but I very promptly uninstalled them.
w0rdie said:
I appreciate the clarity. :good:
Click to expand...
Click to collapse
You're welcome!
DeanGibson said:
I did originally try Kingo Root (per the OP's instructions) on the 1st tablet, and that got me another "root management" app installed, so now I had three (before I uninstalled SuperSU)! It also installed something on the 1st tablet that Google warned me was a security risk, so after the 2nd tablet rooted with just iRoot, I did a factory reset on the 1st tablet and just used iRoot.
Both iRoot and its "root management" app KingUser seem well-written, surprising (at least to me) from a region not known for well-written, easy to use software.
Unfortunately, once you install anything with root privileges, who knows what it left behind. KingoRoot in particular left around several apps with no app icon, that KingUser listed and I was able to uninstall. However, that left me with an uneasy feeling, which is why I did a factory reset on the 1st tablet and started over.
I'd rather trust what one Chinese/Korean app left around (which I have to, if I use iRoot), rather than two.
iRoot does install two other apps, one is the "Cleaner", and another is part of the download process, but I very promptly uninstalled them.
Click to expand...
Click to collapse
I thought the same thing, once something has root it could already have done whatever hidden "damage" it wanted to. I had the same experience regarding what iRoot left behind, the one time early during @Hnk1 's experimenting that I tried it.
Hnk1 said:
STEPS
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user.
Click to expand...
Click to collapse
Well I sort of achieved root with this method.
The vroot program said I had root and root checker did too.
However adaway and titanium backup could not perform their functions. They are allowed in the king user app and tibu even said it had root access.
Anyone else run into this issue?
_Boondock_ said:
Well I sort of achieved root with this method.
The vroot program said I had root and root checker did too.
However adaway and titanium backup could not perform their functions. They are allowed in the king user app and tibu even said it had root access.
Anyone else run into this issue?
Click to expand...
Click to collapse
I was also partially rooted with the above method and thus I performed IF ABOVE FAILS in my guide, that is using another app and then running both apps simultaneously. However, another user said, he only needed to use IROOT so I edited it a bit.
Try restarting your device, and then try IF ABOVE FAILS.
See if that helps ?
@Hnk1 I really appreciate all your work but I have tried this method 100 ways and can not get it to work. Iroot says yea but root check says na and Kingo root never takes. If you have any ideas I will try again. Does it matter if I am on the ota or kdz?
mopartonyg said:
@Hnk1 I really appreciate all your work but I have tried this method 100 ways and can not get it to work. Iroot says yea but root check says na and Kingo root never takes. If you have any ideas I will try again. Does it matter if I am on the ota or kdz?
Click to expand...
Click to collapse
Although it shouldn't matter, I would try with a fresh CSE mode flash of the 35A KDZ.
roirraW "edor" ehT said:
Although it shouldn't matter, I would try with a fresh CSE mode flash of the 35A KDZ.
Click to expand...
Click to collapse
Yep tried that also, I will keep playing til I get it
mopartonyg said:
Yep tried that also, I will keep playing til I get it
Click to expand...
Click to collapse
It's tedious work, but satisfying once we figure it out. I had to reflash so many times in order to find out what two things I was debloating was causing the initial setup to FC. Google Webview and Google TTS.
Good luck!
I am not responsible for any bricked devices or any other damage do your Kindle Fire, SD Cards, or yourself.
Steps:
1. Using RootJunky's SuperTool, root your Fire then install FlashFire
2. Download CM12.1 from here.
3. Follow the instructions listed.
4. Profit
To re-root your tablet or enable ADB:
1. Go to settings
2. Scroll to the bottom, tap on About Tablet.
3. Tap on build number until it says "You have enabled developer settings."
4. Go back and open Developer Options.
5. You now have the options for rooting and ADB.
llamasking said:
I am not responsible for any bricked devices or any other damage do your Kindle Fire, SD Cards, or yourself.
Steps:
1. Using RootJunky's SuperTool, root your Fire then install FlashFire
2. Download CM12.1 from here.
3. Follow the instructions listed.
4. Profit
Click to expand...
Click to collapse
Just tried it out. Worked perfectly! Went from Fire 5.3.1 to CM12.1 successfully.
Thanks for the simplified tutorial!
ChronicAlbert said:
Just tried it out. Worked perfectly! Went from Fire 5.3.1 to CM12.1 successfully.
Thanks for the simplified tutorial!
Click to expand...
Click to collapse
Thank you!
Kingroot from the Super tool keeps failing for my Fire on 5.3.1.0. Frustrating. Can't even get passed that step.
fuelvolts said:
Kingroot from the Super tool keeps failing for my Fire on 5.3.1.0. Frustrating. Can't even get passed that step.
Click to expand...
Click to collapse
Try doing factory reset, then use the supertool without loging into your amazon account
Sorry for the noob question, but is this gonna work on a 6th gen HD 8" running 5.3.1.1?
usererror404 said:
Sorry for the noob question, but is this gonna work on a 6th gen HD 8" running 5.3.1.1?
Click to expand...
Click to collapse
Wrong forum; ask here. Hint: nope.
Worked perfect!
Edit: Just a short question after installing CM12.1, my device isn't rooted anymore? How to root it again in order to get Flashfire working? Or ist TWRP automatically installed?
SwitzXXL said:
Worked perfect!
Edit: Just a short question after installing CM12.1, my device isn't rooted anymore? How to root it again in order to get Flashfire working? Or ist TWRP automatically installed?
Click to expand...
Click to collapse
- enable developer options (Google for procedure)
- locate/enable root toggle under developer options
- no twrp; must use FlashFire as needed
I wanted to do this but IDK how to find my firmware version. My kindle has had updated disabled ads removed and all that for a while now.
Davey126 said:
- enable developer options (Google for procedure)
- locate/enable root toggle under developer options
- no twrp; must use FlashFire as needed
Click to expand...
Click to collapse
Tried that and gave root to apps & adb but I still can't install SuperSU nore use FlashFire (no root)?
SwitzXXL said:
Tried that and gave root to apps & adb but I still can't install SuperSU nore use FlashFire (no root)?
Click to expand...
Click to collapse
Have you rebooted after enabling root? Sometimes required. Verify root status with a checker app; I linked one below for convenience (both source and app are well regarded). There are many others including dozens in the Play Store if you have access.
http://www.apkmirror.com/apk/jrummy-apps-inc/root-check/
Sorry guys for asking a question that been asked many time but i just wanna be sure
my fire is on 5.3.1.0 installed on jully 29,2016.... CAN I ROOT IT? cause i heard i could brick it
Thanks
caymera said:
Sorry guys for asking a question that been asked many time but i just wanna be sure
my fire is on 5.3.1.0 installed on jully 29,2016.... CAN I ROOT IT? cause i heard i could brick it
Thanks
Click to expand...
Click to collapse
Yes - use the SuperTool linked in the OP (first post in this thread). Don't get all knotted up following some other guide that will lead you down a rabbit hole.
was able to install CM12.1 - but no Google stuff was installed, now enabled root again and can't get access to SuperSU, any tips, says it failed, rebooted, did factory reset, no luck.
fventura03 said:
was able to install CM12.1 - but no Google stuff was installed, now enabled root again and can't get access to SuperSU, any tips, says it failed, rebooted, did factory reset, no luck.
Click to expand...
Click to collapse
This commonly happens when (one of more):
- full system wipe does not proceed rom flash
- FlashFire zip options are twiddled (defaults are fine)
- wrong version of GAaps or GAaps not included w/rom
You'll likely need to restore FireOS via stock recovery and start over.
fventura03 said:
was able to install CM12.1 - but no Google stuff was installed, now enabled root again and can't get access to SuperSU, any tips, says it failed, rebooted, did factory reset, no luck.
Click to expand...
Click to collapse
Did you flash gapps?
ldeveraux said:
Did you flash gapps?
Click to expand...
Click to collapse
Which version of GAPPS do we need in this case?
jonathanmoneill said:
Which version of GAPPS do we need in this case?
Click to expand...
Click to collapse
Recommend Open GAaps arm/5.1/nano (here). You will likely need to reflash CM 12.1 along with the GAaps. Flashing a stand-alone GAaps package after CMxx has initialized often doesn't work. You will need to reinstall FlashFire (here) to accomplish the above. You do NOT need to reload FireOS provided the system partition is wiped before flashing CM+GAaps. Ask further questions as needed.
hi guys, i just used rootjunkys tool to root a new Fire 5.3.1 ,i put in kingroot and them
then supersu , chexked to see if i got root app sys yes, now i put in flasfire it says invalid file, so please what do i do now, and when i do get it to work plz explain how i put on cm.12,,thankyou