Related
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
kokorolove said:
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
Click to expand...
Click to collapse
You need to unlock to flash a custom kernel which would be needed by the cm12 to run. So first.
1.Backup drm keys
2.Unlock BL
3. Flash CM kernel via fastboot
4. Flash CM Rom via recovery.
Sent from my SGP621 using XDA Free mobile app
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Cyberratchet said:
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Click to expand...
Click to collapse
I guess you should just flash the kernel via fastboot after unlocking the bootloader, that would eliminate the need to flash a recovery. It's hitting 2 birds and one stone and besides CM uses a different kernel than stock so later you would really need to flash kernel.
Sent from my SGP621 using XDA Free mobile app
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
I'm also curious about this.
Right now, I'm trying to download the Flashtool program from Sony, but apparently, you need to "register" for it. Where did you guys download your Flashtool from?
Cyberratchet said:
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
Click to expand...
Click to collapse
Correct, make sure the kernel is compatible with CM
Sent from my SGP621 using XDA Free mobile app
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Cyberratchet said:
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Click to expand...
Click to collapse
I ran into the same problem usin the cm12 nightlies from 27th march 2015:
Sideloading would not work because the tablet is not recognized by the computer. I tried with Windows 7 and gentoo Linux.
Installing from the sd-card in recovery mode was also not possible due to a error of missing "/misc".
I solved the problem by manually choosing the driver in Windows 7. I booted the tablet into recovery. Choose update using adb as detailed in this post:
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534
Then I found the device in the windows device manager. Here I manually choose the adb driver that I installed earlier from the flashtool package. After that the device was correctly recognized by Windows and I could Sideloade the cm12 image.
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.
Recently I attempted to root my Nexus 9 (running 6.0.1, latest OTA update) using this guide: phandroid.com/2014/11/05/how-to-root-nexus-9
It didn't go so well and I ended up in a bootloop after completing the steps. I managed to resolve this by following the steps on the Google Developer Factory Images page using the latest Nexus 9 (Wi-Fi only) image (I did not re-lock the bootloader, however).
After this, the device booted fine, however it is not rooted (apps cannot get root access and rootchecker and supersu both state that it is not rooted). I would appreciate some help here, as I am not sure where I went wrong (for example does flashing the factory image de-root?) or how to gain root from here. Most of the guides I have seen are for android 5.0, and I am not sure if the software used/linked is still compatible. I am not planning on moving away from stock android on this device, so a custom recovery is not necessary for me, and most guides include installing CWM or TWRP (I'm not against this, I just figured it's not necessary.)
If anyone could link any guides that are still valid (or tell me what to do) it would be much appreciated!
That guide is way out of date and links you to wrong files. Flashing factory images will remove root.
Get latest TWRP image .
Boot your device to bootloader mode. Attach to PC issue this comand "fastboot boot <name of twrp.img>".
Have latest supersu.zip on your device before hand. Use the Temporarily booted TWRP to install that zip.
corkiejp said:
That guide is way out of date and links you to wrong files. Flashing factory images will remove root.
Get latest TWRP image .
Boot your device to bootloader mode. Attach to PC issue this comand "fastboot boot <name of twrp.img>".
Have latest supersu.zip on your device before hand. Use the Temporarily booted TWRP to install that zip.
Click to expand...
Click to collapse
Thanks! I've just gotten around to following your instructions, and that was totally painless. Much simpler and faster than anything I found elsewhere, too (Guess all the guides I found were hopelessly outdated).
Will this method work for all current devices (assuming I have the correct TWRP, of course)?
@Sithon
Should work with most nexus devices.
Other devices may have locked bootloaders and need different methods to root. Check the device forum.
i have a kindle hdx 7 3rd gen 4.5.5.2 rooted with kingroot, my goal is to install custom rom like lineage 14 or one with android 6.0 or higher, i did the root with kingroot, then i generated the unlock file, then i flashed with fastboot the aboot_vuln.mbn file then my mistake i flashed with fastboot thor-twrp-3.0.3-1.img (has to be unlocked first) the i tried to unlock the bootloader and there was no fastboot driver, i know that i should flashed this file twrp_cubed.img and then unlock, know i can boot to recovery and seems to be working fine, but how can i flash twrp_cubed.img, i can boot to fastboot but my pc doed not recognize the driver, can i install another rom that does not need bootloader unlocked and the flash with rom manager apk this file twrp_cubed.img and the unlock and continue with my goal help please
machigaeru1 said:
i have a kindle hdx 7 3rd gen 4.5.5.2 rooted with kingroot, my goal is to install custom rom like lineage 14 or one with android 6.0 or higher, i did the root with kingroot, then i generated the unlock file, then i flashed with fastboot the aboot_vuln.mbn file then my mistake i flashed with fastboot thor-twrp-3.0.3-1.img (has to be unlocked first) the i tried to unlock the bootloader and there was no fastboot driver, i know that i should flashed this file twrp_cubed.img and then unlock, know i can boot to recovery and seems to be working fine, but how can i flash twrp_cubed.img, i can boot to fastboot but my pc doed not recognize the driver, can i install another rom that does not need bootloader unlocked and the flash with rom manager apk this file twrp_cubed.img and the unlock and continue with my goal help please
Click to expand...
Click to collapse
There are several ways to skin this cat; two possibles solution are shown below; both assume you have access to a working build of TWRP (version is irrelevant)
Option #1
- boot into TWRP
- tether device and test if adb server responds
- if no proceed to option #2
- otherwise follow step #2 from this post to reflash aboot and twrp
Option #2
- boot into TWRP
- tether device and transfer Nexus ROM KTU84U (KitKat based) to internal storage
- wipe system, data, cache and dalvik partitions from advanced wipe menu
- install Nexus and reboot device
- once ROM boots follow step #2 from this post to reflash aboot and twrp
Davey126 said:
There are several ways to skin this cat; two possibles solution are shown below; both assume you have access to a working build of TWRP (version is irrelevant)
Option #1
- boot into TWRP
- tether device and test if adb server responds
- if no proceed to option #2
- otherwise follow step #2 from this post to reflash aboot and twrp
Option #2
- boot into TWRP
- tether device and transfer Nexus ROM KTU84U (KitKat based) to internal storage
- wipe system, data, cache and dalvik partitions from advanced wipe menu
- install Nexus and reboot device
- once ROM boots follow step #2 from this post to reflash aboot and twrp
Click to expand...
Click to collapse
i tried to flash the nexus rom using install option from twrp an i got this error no MD5 file found cant install this pacage (Mon 17 oct 13:32:45 BST 2016 over newer build (Tue 20 Dec 13:57:49 GMT 2016)
updater process ended with error 7
error installing zip file /sdcard/download/kk-fire-nexus-rom-thor-201617.zip
machigaeru1 said:
i tried to flash the nexus rom using install option from twrp an i got this error no MD5 file found cant install this pacage (Mon 17 oct 13:32:45 BST 2016 over newer build (Tue 20 Dec 13:57:49 GMT 2016)
updater process ended with error 7
error installing zip file /sdcard/download/kk-fire-nexus-rom-thor-201617.zip
Click to expand...
Click to collapse
Likely due to TWRP 3.0.3 which has issues flashing certain ROMs. Did you try option #1? ADB capabilities are integrated into TWRP v3. You could also try flashing CM 11 which seems to be more tolerant of TWRP 3.0.2/3.0.3 weirdness. You'll need to include a GAaps package and SuperSU (use this build) with CM 11; see OP for details.
If neither of these options work we can try a different ROM (albeit untested w/locked bootloader) or update the recovery partition from fastboot. The latter will require fiddling with drivers on the host machine which you previously indicated was problematic. Same with unlocking the bootloader assuming you saved the unlock file.
i cant access adb shell, i have the unlock file but with out adb functionality, the rom CM 11 needs a unlock bootloader, can i flash it with out the unlocked bootloader ?
machigaeru1 said:
i cant access adb shell, i have the unlock file but with out adb functionality, the rom CM 11 needs a unlock bootloader, can i flash it with out the unlocked bootloader ?
Click to expand...
Click to collapse
Linked CM 11 build does not require an unlocked bootloader.
Davey126 said:
Linked CM 11 build does not require an unlocked bootloader.
Click to expand...
Click to collapse
this is from the link
General Information
- This ROM is for all variants of the 3rd generation Kindle HDX tablets.
- This is primarily for users of Safestrap 4.0.1, however
- This will also work on devices with TWRP however you must also unlock your bootloader.
machigaeru1 said:
this is from the link
General Information
- This ROM is for all variants of the 3rd generation Kindle HDX tablets.
- This is primarily for users of Safestrap 4.0.1, however
- This will also work on devices with TWRP however you must also unlock your bootloader.
Click to expand...
Click to collapse
Dude - you're fine. If you want to challenge great. I'm trying to help you out of a pickle of your own doing - not justify the validity of my posts. If uncomfortable flashing CM 11 roll up your sleeves and get fastboot drivers installed/working on your host. Then unlock the bootloader and reflash TWRP.
machigaeru1 said:
this is from the link
General Information
- This ROM is for all variants of the 3rd generation Kindle HDX tablets.
- This is primarily for users of Safestrap 4.0.1, however
- This will also work on devices with TWRP however you must also unlock your bootloader.
Click to expand...
Click to collapse
i am going to flahsed to see what hapens
it worked, so know to flash the twrp_cubed.img can i use rom manager ?, thanxs for all of your help
machigaeru1 said:
it worked, so know to flash the twrp_cubed.img can i use rom manager ?, thanxs for all of your help
Click to expand...
Click to collapse
Two options:
#1 - follow instructions (step #2) in unlock thread (code block)
#2 - grab Flashify from here and use it to install the desired build of TWRP (no tether required)
Also suggest you issue the following adb commands in advance and record the results somewhere; these codes can be used to create an unlock sequence for your device in case the previously generated unlock file is invalid:
adb shell cat /sys/block/mmcblk0/device/manfid
adb shell cat /sys/block/mmcblk0/device/serial
we did it, thanks so much, my bootloader is unlocked thanks to you, now i am testing lineage 14, and i am very happy, tanks again for your time
machigaeru1 said:
we did it, thanks so much, my bootloader is unlocked thanks to you, now i am testing lineage 14, and i am very happy, tanks again for your time
Click to expand...
Click to collapse
Great! Glad it worked out. As for 'credits' I'm just a humble messenger. Kudos to @ONYXis, @draxie, @ggow, @Hashcode and several others who are the real brains behind the show.
Enjoy your liberated HDX!