Related
Feel free to haze me for what I'm sure is a stupid question.
After flashing the factory 5.1.1 image, is the Chainfire root method still the correct way to root? The 'fastboot flash boot' part made me wonder if it needs to be updated for the bootloader that shipped with the 5.1.1 image.
funkybside said:
Feel free to haze me for what I'm sure is a stupid question.
After flashing the factory 5.1.1 image, is the Chainfire root method still the correct way to root? The 'fastboot flash boot' part made me wonder if it needs to be updated for the bootloader that shipped with the 5.1.1 image.
Click to expand...
Click to collapse
Wrong question.
There is no "correct" or "incorrect" method. FWIW, it's a Nexus device. You don't need these automated tools. Just fastboot flash the TWRP image, boot to recovery and flash the latest SuperSU zip from recovery. Done.
cam30era said:
Wrong question.
There is no "correct" or "incorrect" method. FWIW, it's a Nexus device. You don't need these automated tools. Just fastboot flash the TWRP image, boot to recovery and flash the latest SuperSU zip from recovery. Done.
Click to expand...
Click to collapse
Thanks but that wasn't really my question and I hadn't planned to use the auto-root CF version. To clarify what I'm confused about: The manual CF Root process involves a step "fastboot flash boot {img}", and when checking the CF repository I see that this boot image was based on 5.0.x. From other threads I had understood the 5.1.1 factory image includes a new bootloader image, and this made me wonder if flashing the bootloader that ships with the chainfire root package would be a potential problem. I'm still curious about this, but now also:
Your response suggests I could avoid CF altogether if I'm willing to flash a non-stock recovery. Is that correct?
yeah I would skip CF and just do it the manual way. copy SuperSU to your device first.
@funkybside,
No. Flash all of the stock .img files except recovery. Fastboot flash TWRP.img instead. Then boot to recovery from fastboot on your device and flash the SuperSU.zip.
Alternatively, if you want to keep the stock recovery, you can
fastboot boot recovery "name of TWRP.img". Then flash the SuperSU.zip.
y2whisper said:
yeah I would skip CF and just do it the manual way. copy SuperSU to your device first.
Click to expand...
Click to collapse
That's the part that generated my question. Inside the SuperSU.zip are inject.img and patched.img. The readme states patched.img needs flashed with 'fastboot flash boot patched.img', and the package was made before the 5.1.1 drop. For all I know it's fine to do this, but since it's flashing a boot image I figured better safe than sorry and decided to post. I have searched here and all root threads/links seem pointed to videos using toolkits/CF-AutoRoot so I wasn't comfortable with following them. FWIW - At the moment I'm stock factory 5.1.1 image, stock recover, unlocked BL, not rooted.
Trying to be a self sufficient as I can...quickly becoming 'that guy'. ugh. The core question is does the patched.img inside SuperSU.zip cause any problems with a factory 5.1.1 unlocked device, due to potential differences between the factory 5.1.1 boot image and the one included in SuperSU.zip.
No you're just learning. I rooted my after without problems but I wonder if a new version will be done now that 5.1.1 is done for the N9
funkybside said:
That's the part that generated my question. Inside the SuperSU.zip are inject.img and patched.img. The readme states patched.img needs flashed with 'fastboot flash boot patched.img', and the package was made before the 5.1.1 drop. For all I know it's fine to do this, but since it's flashing a boot image I figured better safe than sorry and decided to post. I have searched here and all root threads/links seem pointed to videos using toolkits/CF-AutoRoot so I wasn't comfortable with following them. FWIW - At the moment I'm stock factory 5.1.1 image, stock recover, unlocked BL, not rooted.
Trying to be a self sufficient as I can...quickly becoming 'that guy'. ugh. The core question is does the patched.img inside SuperSU.zip cause any problems with a factory 5.1.1 unlocked device, due to potential differences between the factory 5.1.1 boot image and the one included in SuperSU.zip.
Click to expand...
Click to collapse
SuperSU is not device specific. 2.46 works fine on 5.1 on Nexus 6. I doubt the changes between 5.1 and 5.1.1 are significant enough to require a new version.
i use CF SuperSU Root Tool
1. Extract the earlier downloaded CF Auto zip folder on your computer.
2. Enable Developer Options on Nexus 9: in the About Device > tap Build Number multiple times until you see the new tab Developer Options. In here, check Enable OEM Unlock and USB Debugging.
3. Enter the Bootloader mode from your computer by running this command (open command prompt with Shift + Right Click > Open the command window here), adb reboot bootloader
4. Execute the root file,
Windows: run root-windows-bat
OS X: chmod +x root-mac.sh
run root-mac.sh
Linux: chmod +x root-linux.sh
run root-linux.sh
Once the command window finishes executing, your Nexus 9 will reboot.
Thanks to all of you. I guess I stop worrying and just give it a go. It seems like anyone who's had experience rooting 5.1.1 has not had any concerns or problems related to SuperSU.zip's patched.img being listed with a 5.0.x version on the CF site.
/me crosses fingers.
Edit: IT'S ALIVE! Thanks again folks.
In case anybody stumbles onto this thread, you might as well go with the "autoroot" method. Autoroot is smart enough to adapt to new boot images, and does not require installation of a custom recovery. What it is essentially, IS a custom recovery bundled with the root bits.
You "fastboot boot autoroot.img" the device. It loads the autoroot.img to memory, and executes it, and installs the internal root bits to the /system partition.
Also note: With a Nexus device, it is NEVER necessary to INSTALL a custom recovery image, since you can RUN a custom recovery image without actually installing it.
fastboot boot bootable.img
doitright said:
In case anybody stumbles onto this thread, you might as well go with the "autoroot" method. Autoroot is smart enough to adapt to new boot images, and does not require installation of a custom recovery. What it is essentially, IS a custom recovery bundled with the root bits.
You "fastboot boot autoroot.img" the device. It loads the autoroot.img to memory, and executes it, and installs the internal root bits to the /system partition.
Also note: With a Nexus device, it is NEVER necessary to INSTALL a custom recovery image, since you can RUN a custom recovery image without actually installing it.
fastboot boot bootable.img
Click to expand...
Click to collapse
I would only disagree on one point. This is fine as long as the user understands how to use ADB and fastboot, and how to get out of trouble if something goes wrong. We've seen too many inexperienced users get into trouble with automated tools who don't have the SDK installed on their PC and don't understand how to install drivers.
I have a Fire HDX 7 on 13.3.2.5_user_325001120, Rooted, Safestrap 3.75 with Fire OS on Stock slot and ggow's HDX Nexus 2.0.2 on Slot-1. OTA updates are not disabled but no Wifi networks are added and Wifi is off within Fire OS.
I'm basically looking for clarification on the steps I need to take in order to unlock the Bootloader (for peace of mind and so that I can try out other ROMs freely).
To the best of my understanding I can Unlock with the following instructions:
Downgrade from 13.3.2.5 to 13.3.1.0
Download 13.3.1.0 .bin and script linked by kaeru00
Originally Posted by kaeru00
USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
How to use it.
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.
4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.
This batch file works "kindle fire hdx 7" ONLY
This is tested on version 13.3.2.5 and 13.3.2.6.
Click to expand...
Click to collapse
If successful with the above I then proceed with the following to actually unlock:
Originally Posted by ceyo14
complete as follows. tested on HDX 7 (Thor) Rooted 13.3.1.0
get Python 2.7 for windows and install it
get GMPY2 for Python 2.7
open command prompt to your ADB directory:
Code:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
from these 2 results you get your the code we need, insert the last 2 digits of the manfID with your serial
following
like this: mmssssssss
download the attachment on the following post: http://forum.xda-developers.com/show...2&postcount=46
Then place the file inside the attachement to C:\Python27 should be C:\Python\cuberHDX.py
open command prompt in: C:\Python27
replace "mmssssssss" with yours below:
Code:
python.exe cuberHDX.py 0xmmssssssss
that will put a new 0xmmssssssss.UNLOCK file in the Python27 directory
copy that file to your fastboot directory.
on an ADB prompt type
Code:
adb reboot-bootloader
then on a fastboot prompt type
Code:
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
thats it.
Click to expand...
Click to collapse
All going well, I'm then unlocked and can proceed to install TWRP and ROMs, correct?
Yes, but actually you can install TWRP after downgrading to 3.1.0 already.
And it's recommended (i.e. not mandatory) to update to 3.2.3.2 (can be done from TWRP, it's also possible to update the 3.2.3.2 bootloader only). Be sure to re-root if you update to 3.2.3.2! And keep WLAN off/flight mode active at all times. Stock firmwares are available here - ensure you get the correct for your device!
If you haven't done yet, install Minimal ADB and Fastboot, and grab these drivers for the unlock procedure in order to get the HDX recognized.
Then unlock the bootloader to be in the wonderland of HDX ROMs (=TWRP & unlocked bootloader), you can use Nexus, CM11 or CM12 then - read the installation notes and requirements carefully! Additional info for the unlock procedure after installation of the required software can be found here.
Disable OTA in Fire OS, make a backup in TWRP, and copy the backup to your PC before you flash any ROM!
Thank alot Cl4ncy.
Having now re-read the instructions I've posted, I'm abit unsure of the rollback process as below:
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.
4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.
Steps 4 & 5, am I doing this on the HDX or on PC. Do I need the HDX connected to my PC, and if so what mode should it be in?
Could someone possibly expand the above steps to to be abit more clear?
316894 said:
Thank alot Cl4ncy.
Having now re-read the instructions I've posted, I'm abit unsure of the rollback process as below:
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.
4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.
Steps 4 & 5, am I doing this on the HDX or on PC. Do I need the HDX connected to my PC, and if so what mode should it be in?
Could someone possibly expand the above steps to to be abit more clear?
Click to expand...
Click to collapse
After you downloaded the rollback.zip from that thread un-zip it to a folder on your PC, copy the update.bin into that folder, and execute the install.bat. Your HDX must be connected by USB, USB debugging must be active on the HDX, the install.bat will move (push) some files to the HDX.
Reboot the HDX then, copy the update.bin to your HDX and execute the downgrade.
Again: ensure you have WLAN off/flight mode active as you need OTA to be enabled in Fire OS! You do NOT want to get updated to 4.5.5 by Amazon.
Thanks again, that is as I suspected, having now opened the .bat in notepad.
Why is it generally recommended that we update to 3.2.3.2? Can this also be done the old fashioned way through the Fire OS update option or is it easier/safer through TWRP after taking a backup.
After that then I would re-root with Towelroot.
316894 said:
Thanks again, that is as I suspected, having now opened the .bat in notepad.
Why is it generally recommended that we update to 3.2.3.2? Can this also be done the old fashioned way through the Fire OS update option or is it easier/safer through TWRP after taking a backup.
After that then I would re-root with Towelroot.
Click to expand...
Click to collapse
There have been some screen issues with Nexus, thus it's recommended to use the 3.2.3.2 bootloader, which can be flashed itself in TWRP - check this thread.
So it's your choice, to update to 3.2.3.2 using the official update in TWRP or Fire OS, or just flash the 3.2.3.2 bootloader in TWRP. If you want to dump Fire OS anyway, just disable OTA in Fire OS via HDX Toolkit, backup Fire OS in TWRP, move it to your PC, update 3.2.3.2 bootloader from the thread mentioned above, unlock it, then flash Nexus, CM11 or CM12.
You can also check for the backup of the original Amazon recovery, should be somewhere on the HDX, after you installed TWRP (AFAIR TWRP creates a backup of the original recovery), and move that recovery backup to your PC as well.
Good stuff, this will give me something to do tonight when I get in from work.
I will report back with my results! Cheers. :good:
316894 said:
Good stuff, this will give me something to do tonight when I get in from work.
I will report back with my results! Cheers. :good:
Click to expand...
Click to collapse
One more thing:
You should remove the secondary slot with Nexus 2.0.2 before you un-install Safestrap. Otherwise the storage used by that slot could be still in use.
Success! 13.3.2.3.2 bootloader, unlocked and now running KitKat 4.4.4
Cheers for the help Cl4ncy. :good:
316894 said:
Success! 13.3.2.3.2 bootloader, unlocked and now running KitKat 4.4.4
Cheers for the help Cl4ncy. :good:
Click to expand...
Click to collapse
Great you got it working! Enjoy your "free" HDX.
Just to go for sure...
Hi there,
thanks for your great thread, I am in nearly the same position.
I am currently on: Safestrap 3.75, Nexus 2.0.2 from ggow on ROM-Slot-1 and Stock ROM has version: 13.3.2.4_user_324002120 (build on 20.th June, 2014, 23:58 GMT)
Some questions however remain:
How did you uninstall Safestrap? Boot to Stock ROM, start the Safestrap app there and hit uninstall? Or somewhere else?
I just want to go 100% sure before removing my "fallback" software, which Safestrap was until now.
The link in your post does no longer point to cuberHDX, I used this one: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
I have adb and "KFHDX ToolKit v0.95" running to do things via my PC.
Do I need to use fastboot (it does not list my device yet, but I also have not changed the driver as Cl4ancy suggested)? If it is not needed, I will stick to my working adb.
The things I downloaded right now are:
13.3.2.4_rollback (from here: http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 ), to go back to .3.1.0 .
thor-bootloader-13.3.2.3.2_upgrade.zip (from here: http://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-3-2-3-bootloader-upgrade-t3025504 ), to update 3.1.0 to .3.2.3.2
cuberHDX from here: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
I have retrieved the needed serials and are nearly ready to go. Just want to double check whether I have misunderstood something.
If not, I think this is the procedure, right:
1. Downgrade to .3.1.0 (how is this done? the zip contains folders, not a binary. The instruction say: 2. Flash the appropriate file for you device . Shall I do this by copying the zip to the device and install it via the still present Safestrap?) Can you please clarify on that?)
1.5 Delete Safestrap? (If this is still possible after downgrading? )
2. Upgrade to .3.2.3.2 by placing the .bin in the root folder ? ( I have no install.bat batch file supplied here).
3. Unlook bootloader as described here: http://forum.xda-developers.com/showpost.php?p=62253081&postcount=6
4. Flash twrp (as described here ) ?
As you see, I am a bit puzzled about Safestrap... appreciate your help!
Thanks in advance,
syk
You are in a slightly better situation, you can use the rollback images.
The downgrade is done by following the instructions in the rollback image thread. Basically you backup your current stock slot, delete secondary slots (if you created any) so the space isn't in use, copy the rollback image to the HDX, access Safestrap and flash the rollback image to the stock slot - Safestrap (like TWRP) flashes .zip files directly to the required partition(s). Then do a factory reset (i.e. wipe - do NOT go into advanced wipe! DO NOT wipe System!!). Keep WLAN off/flight mode active, so you won't get updated by Amazon! Follow the instructions 100% correctly! Copy the 3.1.0 stock update to the HDX, then update Fire OS.
Un-installation of Safestrap is simple: Just open the Safestrap app and select "Uninstall Recovery". But following the downgrade procedure incl. the factory reset, Safestrap will be gone anyway, so no need to worry about its removal (note that this applies to the usage of the rollback Image procedure only!).
After the downgrade to 3.1.0 and the removal of Safestrap you can install TWRP, then backup your Fire OS in TWRP and move the backup to your PC (if the HDX is powered off, you can access TWRP this way: press and hold Volume up, then press and hold the Power botton, release both buttons when the grey Kindle logo appears on Screen.
TWRP Installation can be done via ADB (recommended) or apps like e.g. Flashify. If you haven't installed ADB already, see the link below. The TWRP.bin must be in the root of your HDX, i.e. if you open the HDX in a file explorer, don't open any other directory, just paste it right there.
Then flash the 3.2.3.2 bootloader from the link you mentioned, it's a .zip file to be flashed in TWRP (the install.bat is required for 3.2.5 and 3.2.6 only, you have 3.2.4 and don't need it anyway).
You can unlock the bootloader then, but you should install Minimal ADB and Fastboot and grab these Drivers. You also need to install the software mentioned here (i.e Python 2.7 and GMPY2 for Python 2.7).
Hi Cl4ncy,
all worked well so far, less hassle than feared.
As expected, I could not uninstall Safestrap after I applied the rollback (since the app was gone).
I flashed original stock rom 3.1.0 ( from here, just in case anyone also needs these files reading this thread), and upgraded the bootloader to 3.2.3 (but can't really check whether this worked, or is there any possibility to check that?).
I already prepared the unlock file beforehand, but the final step is still missing: unlocking the bootloader.
I can set my device into fastboot mode with adb, but fastboot on my PC can't find my device (adb, in contrast, found it..), and the driver linked here can't be downloaded because the board is over capacity.
I hope the driver solves my problem soon.
Do you have an other location to download the file?
And in the meantime: Why do I need to unlock the bootloader? The installation of the old Nexus 2.0.2 ROM seemed to work without that via Safetrap (or it just did not say that it unlocked the bootloader?)
What are the benefits of doing that?
Thanks again,
syk
I uploaded the drivers here.
Unlocking the bootloader is required for e.g. CM12 - Nexus or CM11 for Safestrap v4 either require to update to 4.5.2, root, and install Safestrap v4, or an unlocked bootloader. TWRP also enables far better recovery options, so TWRP & unlocked bootloader open the wonderland of HDX ROMs for you.
Thanks a lot, the drivers worked. I am now trying out the latest SlimROM already. Seems to be the most stable Lollipop ROM as of now...
So I am in the process of attempting to unlock my bootloader and basically following the steps done by sykarian as we were in similar boats(my original situation described here) and I have a few questions.
So far I have used the rollback image and updated using the 3.1.0 stock firmware without any problems. According to the posts in this thread, my next steps would be to uninstall safestrap, install TWRP, and flash the 3.2.3 bootloader. My issue is uninstalling safestrap. As far as I can tell, it's already gone as I can no longer boot into recovery and there is no safestrap app present. I see sykarian mentioning a similar issue but it's not exactly clear what he did from that point.
Am I ok to just go ahead and install TWRP at this point or is there something specific I need to do to ensure safestrap is removed? Also, I notice in the TWRP thread, it says to ensure that I am running stock firmware 3.2.3.2 before installation but that is not mentioned anywhere in the posts here. Is it ok to install it on the 3.1.0 firmware I am currently running? I do see in the first reply in this thread Cl4ncy says TWRP can be installed after rollback to 3.1.0 but I just want to make sure that also applies to my situation and not just the OP.
If anyone could clear this up for me I'd really appreciate it
muunkin said:
So I am in the process of attempting to unlock my bootloader and basically following the steps done by sykarian as we were in similar boats(my original situation described here) and I have a few questions.
So far I have used the rollback image and updated using the 3.1.0 stock firmware without any problems. According to the posts in this thread, my next steps would be to uninstall safestrap, install TWRP, and flash the 3.2.3 bootloader. My issue is uninstalling safestrap. As far as I can tell, it's already gone as I can no longer boot into recovery and there is no safestrap app present. I see sykarian mentioning a similar issue but it's not exactly clear what he did from that point.
Am I ok to just go ahead and install TWRP at this point or is there something specific I need to do to ensure safestrap is removed? Also, I notice in the TWRP thread, it says to ensure that I am running stock firmware 3.2.3.2 before installation but that is not mentioned anywhere in the posts here. Is it ok to install it on the 3.1.0 firmware I am currently running? I do see in the first reply in this thread Cl4ncy says TWRP can be installed after rollback to 3.1.0 but I just want to make sure that also applies to my situation and not just the OP.
If anyone could clear this up for me I'd really appreciate it
Click to expand...
Click to collapse
Indeed Safestrap will be gone after the usage of the rollback image, and the 3.1.0 stock firmware along with the factory reset during the whole downgrade procedure, so no need to worry about Safestrap anymore. It's important to note the difference between using the downgrade images available for 3.2.4, and the different procedure for 3.2.5/3.2.6!
The requirements for TWRP are firmwares 3.1.0 to 3.2.3.2 IIRC, at least 3.2.3.2 or below - 3.2.3.2 is just recommended due to some graphic glitches with Nexus. You can flash the 3.2.3.2 bootloader upgrade (or even upgrade Fire OS 3.2.3.2) via TWRP without any problems (updated Fire OS would just require to re-root).
Cl4ncy said:
Indeed Safestrap will be gone after the usage of the rollback image, and the 3.1.0 stock firmware along with the factory reset during the whole downgrade procedure, so no need to worry about Safestrap anymore. It's important to note the difference between using the downgrade images available for 3.2.4, and the different procedure for 3.2.5/3.2.6!
The requirements for TWRP are firmwares 3.1.0 to 3.2.3.2 IIRC, at least 3.2.3.2 or below - 3.2.3.2 is just recommended due to some graphic glitches with Nexus. You can flash the 3.2.3.2 bootloader upgrade (or even upgrade Fire OS 3.2.3.2) via TWRP without any problems (updated Fire OS would just require to re-root).
Click to expand...
Click to collapse
Thanks for the quick reply. So I completed all that, got my unlock code good to go and put my kindle into fastboot mode no problem. Now I see that in order to get fastboot on my pc to find my device I need use to drivers linked in this thread. I downloaded those but I'm not sure exactly what to do with them. Looks like this is my last hurdle here. Really appreciate all the help
Edit: Just noticed one of the links in this thread is to a post explaining how to use them haha. Reading through that now.
---------- Post added at 09:12 PM ---------- Previous post was at 08:56 PM ----------
Ok after following the instructions from that post I get an error that says "The third party INF does not contain digital signature information" and it won't install the drivers. I don't see any option to bypass the warning. I am on windows 10 if that makes a difference.
muunkin said:
Thanks for the quick reply. So I completed all that, got my unlock code good to go and put my kindle into fastboot mode no problem. Now I see that in order to get fastboot on my pc to find my device I need use to drivers linked in this thread. I downloaded those but I'm not sure exactly what to do with them. Looks like this is my last hurdle here. Really appreciate all the help
Edit: Just noticed one of the links in this thread is to a post explaining how to use them haha. Reading through that now.
---------- Post added at 09:12 PM ---------- Previous post was at 08:56 PM ----------
Ok after following the instructions from that post I get an error that says "The third party INF does not contain digital signature information" and it won't install the drivers. I don't see any option to bypass the warning. I am on windows 10 if that makes a difference.
Click to expand...
Click to collapse
Do you use Win 10 x64? Unfortunately the installation of unsigned drivers in 64 bit Windows is a pain in the ass. It'd help if you'd access to a 32 bit system, preferable Win 7. Win 10 also seems to have signed driver enforcement active if secure boot is enabled, disabling secure boot helps on 32 bit Win 10.
Cl4ncy said:
Do you use Win 10 x64? Unfortunately the installation of unsigned drivers in 64 bit Windows is a pain in the ass. It'd help if you'd access to a 32 bit system, preferable Win 7.
Click to expand...
Click to collapse
No problem! Already figured it out with a quick google search. Looks I'm unlocked and ready to go!
Really appreciate your help and quick responses man. Cheers.
I would like to install Marshmallow on my Kindle Fire HDX 7.
My current issue is figuring out how to update the boot loader from 13.3.1.0 to 13.2.3.2. I read a post that indicated I could use TWRP to update my boot-loader version without updating my whole firmware, prior to unlocking the boot-loader.
This leads me to a bunch of questions about TWRP:
Do I need to have an unlocked boot-loader before installing TWRP?
Is there a TWRP version for kindle HDX 7 (I can only find one for Kindle 1st gen)?
Do I install TWRP through TWRP Manager app, or do I need a TWRP APK file?
Is this the correct file path for TWRP recovery “/dev/block/platform/mmci-omap-hs.1/by-name/recovery”?
I admit that this is all a bit above my head, so any help is very appreciated.
need root (no need to be unlocked if fw < 13.3.2.3)
Use an application from the market to flash the recovery image like Rashr or Flashify
OR
Use dd application from a root shell : "dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/twrp_thor.img"
https://drive.google.com/file/d/0B2twXJIOgv-URTJLS2JjRzVKcWs/view?usp=sharing
Thanks for your reply ONYXis; just to make sure I understand you correctly, I use Rashr to flash the twrp_thor.img file which installs TWRP on my device, is that correct?
For clarification, I'm rooted running 13.3.1.0. As I understand it, the next steps would be:
Update boot loader to 13.2.3.2
Unlock boot-loader
Backup 13.3.1.0 ROM
Flash CM-13 Marshmallow ROM
I think I understand overall what needs to happen, but not the specifics of how to perform each step.
imamacuser said:
Thanks for your reply ONYXis; just to make sure I understand you correctly, I use Rashr to flash the twrp_thor.img file which installs TWRP on my device, is that correct?
For clarification, I'm rooted running 13.3.1.0. As I understand it, the next steps would be:
Update boot loader to 13.2.3.2
Unlock boot-loader
Backup 13.3.1.0 ROM
Flash CM-13 Marshmallow ROM
I think I understand overall what needs to happen, but not the specifics of how to perform each step.
Click to expand...
Click to collapse
That sounds right.
imamacuser said:
Thanks for your reply ONYXis; just to make sure I understand you correctly, I use Rashr to flash the twrp_thor.img file which installs TWRP on my device, is that correct?
For clarification, I'm rooted running 13.3.1.0. As I understand it, the next steps would be:
Update boot loader to 13.2.3.2
Unlock boot-loader
Backup 13.3.1.0 ROM
Flash CM-13 Marshmallow ROM
I think I understand overall what needs to happen, but not the specifics of how to perform each step.
Click to expand...
Click to collapse
Yes. You'll need to do some reading to understand the specifics of each step. While there are no videos or end-to-end how-to articles all of the information you need is contained within the HDX forum. Make sure you use the posted files which have been adapted and tested for your device. Understand what is suppose to happen in each step and double check your work before committing. I also recommend verifying the MD5 of critical files (like bootloader updates) as a bad file can render your device unbootable. Ask questions as needed; best if each post focuses on a single topic. Links to a few threads to get you started:
- TWRP for HDX
- Bootloader upgrade
- Bootloader unlock
- CM13 ROM for HDX
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com