Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Leafen said:
Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Click to expand...
Click to collapse
Renaming OTA contracts is a problem! Given device is rooted it may be fixable via ADB. Also possible you can go further and unlock bootloader which yields complete control to repair/replace FireOS. I am travelling today and can not immediately help with details. Will check back later (24 hours) to see if help is still needed.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Leafen said:
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Click to expand...
Click to collapse
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Davey126 said:
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Click to expand...
Click to collapse
Oi. Uh. It's normal procedure up to the colored Kindle logo. Goes off the same amount of time as usual. And it never makes it to the put in your password screen. Not yet anyways.
Scratch that I'm in. Changing Ota contracts back
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Leafen said:
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Click to expand...
Click to collapse
Great! Assuming a factory reset did the trick (I didn't immediately suggest that course of action as it can sometimes make things worse; other things to try first).
If you install Safestrap v4 choice of ROMs is limited to Fire Nexus and CM11 - both KitKat based. Unlocking the bootloader opens the door to a wider selection of Lollipop and Marshmallow based ROMs. Unlocking is not risky but does require a bit of technical knowledge and some patience. An unlocked device is also easier to recover in the event of a ROM crash or bootloop.
Assuming you want to proceed with Safestrap download the app from here. Make sure you get the build appropriate for your device. Install/launch the app and then select the option that installs Safestrap recovery. Please note this is not a true recovery environment and has none of the special powers associated with TWRP. Its singular purpose it to support the two custom ROMs noted above on a locked device. Unlocked devices do not need to use Safestrap.
Once Safestrap recovery is installed reboot your device. After the grey Amazon logo you will be presented with a 'robot' screen where you can choose to continue booting into FireOS or enter Safestrap recovery mode. Choose the latter. After a few moments device will enter Safestrap recovery which emulates TWRP.
Do you know what to do from here?
Warning: Once Safestrap v4 recovery is installed you should NEVER perform a factory reset via the stock recovery menu. Doing so will brick the device.
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Leafen said:
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Click to expand...
Click to collapse
Well you got "jammed" into a FireOS update because Safestrap was improperly configured. Details matter. Suggest proceeding with reinstalling Safestrap and forget about unlocking the bootloader thingy. Do not create or attempt to use a secondary slot. Custom ROM overwrites FireOS in the stock slot. Lots of posts outlining Safestrap best practices that apparently were not read or ignored.
Bootloader unlock thread: http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
No the reason I was booted out was because i was having to be stuck on the FireOS because I have to have it for well.. Showing reasons. Don't worry about that. But Safestrap was done perfect, I had it going on for A long while. I successfully used two or more ROMs with perfect functionality.
Leafen said:
I successfully used two or more ROMs with perfect functionality.
Click to expand...
Click to collapse
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Davey126 said:
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Click to expand...
Click to collapse
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Leafen said:
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Click to expand...
Click to collapse
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Davey126 said:
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Click to expand...
Click to collapse
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Leafen said:
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Click to expand...
Click to collapse
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Davey126 said:
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Click to expand...
Click to collapse
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Leafen said:
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Click to expand...
Click to collapse
Must be on FireOS 4.5.2.0 or 4.5.5.1 to run Safestrap v4. Rollback/upgrade options are available but ugly. Pretty sure Safestrap won't be receiving any further updates now that the HDX bootloader can be unlocked on any rooted 3rd gen device.
Related
I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
cnall09 said:
I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
Click to expand...
Click to collapse
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You and me both buddy. But hopefully someone with the know how will see this and give it a try. Who knows it could be the answer we have all been waiting for.
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
You can't just revert to the original Google-supplied Android files as that operating system shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
k1mu said:
You can't just revert to the original Google-supplied Android files as that operating sysm shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
Click to expand...
Click to collapse
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Short answer - no, you can't do that...it doesn't work that way. Depending on the bootloader your phone came with you cannot downgrade. You can try erasing everything and starting over but that's one thing you cannot change.....your stuck.
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
You can totally do this, you can replace the kernel and everything. The phone won't boot, and you'd have a hard brick though. The problem isn't replacing the kernel, the problem is getting the phone to boot after doing so. Download mode operates through aboot, aboot has protections and conditions set that regulate what kernel and recovery partitions you can boot. If these are replaced with a "non-allowed" version the phone simply won't boot, in other words it would be hard-bricked at this point.
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
decaturbob said:
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
k1mu said:
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
Click to expand...
Click to collapse
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
cnall09 said:
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
Click to expand...
Click to collapse
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
joshm.1219 said:
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i know how to permanently unlock it without bricking it. Hit it with a hammer smoke a whole lot n watch in amazement as the bootloader flies out of this phone, able to be replaced of course. Just kidding dont do that, although ive been tempted
cnall09 said:
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
Click to expand...
Click to collapse
reading helps too my friend....also I wouldn't jump to the conclusion that geek squad warranty coverage applies to the the misuse or negligent use of a product....you best read the fine print again.
any way good luck
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
Okay, I managed to get root, supersu, and whatnot up and running (thanks to people in these forums). I then went for the safestrap route.
My new issue is this - I click on "install recovery" - and that seems to work fine. I get notification that it's been installed, and the "State: Installed" status updates. It appears the next step would be to reboot so I have a boot menu, or at least another set of options. The only choice available in safestrap itself is "reboot to recovery". If I choose this, the device reboots to the grey logo, then the screen goes mostly black (powered up, back lit, but dark), and stays that way. I can hold power to turn off and then re-power up to reset (I assume to reboot into the stock rom slot).
Obviously I'm missing something, but I'm not sure what step I might have skipped. To anticipate some questions, I'm on 14.3.2.5, and I used HDX Toolkit v0.95 to root and install safestrap. I did have some difficulty in getting my system to recognize the device as an android adb one, but eventually I got a driver installed that worked.
begalund said:
Okay, I managed to get root, supersu, and whatnot up and running (thanks to people in these forums). I then went for the safestrap route.
My new issue is this - I click on "install recovery" - and that seems to work fine. I get notification that it's been installed, and the "State: Installed" status updates. It appears the next step would be to reboot so I have a boot menu, or at least another set of options. The only choice available in safestrap itself is "reboot to recovery". If I choose this, the device reboots to the grey logo, then the screen goes mostly black (powered up, back lit, but dark), and stays that way. I can hold power to turn off and then re-power up to reset (I assume to reboot into the stock rom slot).
Obviously I'm missing something, but I'm not sure what step I might have skipped. To anticipate some questions, I'm on 14.3.2.5, and I used HDX Toolkit v0.95 to root and install safestrap. I did have some difficulty in getting my system to recognize the device as an android adb one, but eventually I got a driver installed that worked.
Click to expand...
Click to collapse
Thanks documenting so clearly. Unfortunately, having never used Safestrap (know just enough to be dangerous ...) I can't confidently answer your question but I'm sure someone with more experience will jump in.
Question: Why did you opt for Safestrap instead of twrp? It is a simple matter to downgrade to 14.3.1.0, reroot and then install twrp. From there you can stick with stock or install several different roms including nexus and CM11/12. Now, if you prefer rooted stock Fire OS then 3.2.5 and safestrap makes sense (although safestrap isn't necessary it does offer a more robust recovery...albeit not as rich/powerful as twrp). Thanks for taking time to respond; just trying to better understand people's choices as it may help others in similar circumstances.
Davey126 said:
Question: Why did you opt for Safestrap instead of twrp? It is a simple matter to downgrade to 14.3.1.0, reroot and then install twrp. From there you can stick with stock or install several different roms including nexus and CM11/12. Now, if you prefer rooted stock Fire OS then 3.2.5 and safestrap makes sense (although safestrap isn't necessary it does offer a more robust recovery...albeit not as rich/powerful as twrp). Thanks for taking time to respond; just trying to better understand people's choices as it may help others in similar circumstances.
Click to expand...
Click to collapse
Well, since I'm just learning, the SS route seemed easier to not screw up - I had less to do, so I had far fewer chances of ending up with a shiny paperweight. It also seemed to be reversible, so I could learn and then maybe go with the option you quoted above.
However, if I can't seem to make this part work, maybe I'll just skip the in-between step.
begalund said:
Well, since I'm just learning, the SS route seemed easier to not screw up - I had less to do, so I had far fewer chances of ending up with a shiny paperweight. It also seemed to be reversible, so I could learn and then maybe go with the option you quoted above.
However, if I can't seem to make this part work, maybe I'll just skip the in-between step.
Click to expand...
Click to collapse
Yep - makes a ton of sense. Wish everyone acted with your restraint. You'll do fine. Keep reading, watch for gotchas, post questions. Sorry for your Safestrap troubles. It works well for many/most so it sounds like a unique problem with (hopefully) an easy fix.
While I awaited a further reply, I decided to at least see about starting the next steps towards your approach. I downloaded the apollo gapps apks, got them installed, got my account loaded, but the app just keeps stopping immediately after start up. Makes it difficult to grab the prop editor to do a rollback unless there is another way to install that.
I'm currently looking into fixes for gapps, but not finding what I need yet. And yes, this is just the apks and not the rom - since I haven't gotten safestrap fixed, and haven't (obviously) moved on to the alt version, I haven't attempted flashing roms yet.
Update:
So, nevermind. I figured that part out. I was dumb and installed the apks as r/o and not r/w. live and learn (and don't brick I guess).
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Timmetjuh said:
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Click to expand...
Click to collapse
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Davey126 said:
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Click to expand...
Click to collapse
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Timmetjuh said:
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Click to expand...
Click to collapse
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Davey126 said:
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Click to expand...
Click to collapse
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Timmetjuh said:
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
Click to expand...
Click to collapse
Timmetjuh said:
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Click to expand...
Click to collapse
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Davey126 said:
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Click to expand...
Click to collapse
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Timmetjuh said:
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Click to expand...
Click to collapse
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It's not that I don't like the Nexus ROM, I just like to experiment with these things..
So I just installed TWRP with Flashify (started Flashify from NEXUS) and now I seem stuck at the grey Kindle fire logo. I'm just going to leave it alone for a few hours, hopefully it boots later today.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Timmetjuh said:
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Click to expand...
Click to collapse
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Davey126 said:
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Click to expand...
Click to collapse
I'm stuck at the grey Kindle logo..
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Timmetjuh said:
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Click to expand...
Click to collapse
Congrats! Had a bad feeling after your earlier post; glad that was misplaced. Enjoy CM11 and all the goodness that comes from a liberated HDX.
At some point you should consider unlocking the bootloader. That will provide an important fail safe should things go wrong and opens the door to newer roms. Unlike previous flashes there is little/no risk in unlocking. It will either work or not with no adverse consequences. Unlocking can be a frustrating ride as the process involves multiple steps in unfamiliar territory but ultimately the benefits outweigh the effort IMO. Nothing that needs to be tackled right away but keep it on your radar ... especially if you plan to experiment with other roms.
Unlock bootloader
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
No. You can NOT unlock the bootloader! You can NOT downgrade to 3.2.4 and then further to 3.1.0/3.2.3.2! DON'T attempt to do so, you will brick your HDX!
Your only available option is to stay on 4.5.2 and use Safestrap v4 with either Nexus and/or CM11.
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Davey126 said:
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Click to expand...
Click to collapse
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
slothdabski said:
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
Click to expand...
Click to collapse
I actually just got it working by running the following as SU in terminal emaulator
# ip route add default dev tun0 scope link
Not sure yet if I have to do this every time I tether, but if so, i think i can just make a script to execute automatically?
Background: My kindle hdx 8.9 3rd gen was running FireOS 4.5.1 , then installed the kingroot, after that safestrap v4. Having the SS recovery installed, i make attempt to replace kingroot with supersu by flasing supersu v2. 46. It got stuck at logo white-yellow. I do a manufactory reset but still no hope.
Stupid me for not backing up the stock rom since i was confidence in the past was able to do it flawlessly.
Right now:
SS Recovery is accessible
ADB/Fastboot is accessible
Locked bootloader.
Any help would be appriciated.
firebird21 said:
Background: My kindle hdx 8.9 3rd gen was running FireOS 4.5.1 , then installed the kingroot, after that safestrap v4. Having the SS recovery installed, i make attempt to replace kingroot with supersu by flasing supersu v2. 46. It got stuck at logo white-yellow. I do a manufactory reset but still no hope.
Stupid me for not backing up the stock rom since i was confidence in the past was able to do it flawlessly.
Right now:
SS Recovery is accessible
ADB/Fastboot is accessible
Locked bootloader.
Any help would be appriciated.
Click to expand...
Click to collapse
- boot into Safestrap recovery
- use 'adb push' to copy the Fire Nexus install zip (here) to your device
- flash/install Nexus to the STOCK slot (includes GAaps and SuperSU)
You can switch to CM11 later if desired (overwrite Nexus in the STOCK slot) or move forward with unlocking the bootloader for access to the full suite of HDX roms.
Davey126 said:
- boot into Safestrap recovery
- use 'adb push' to copy the Fire Nexus install zip (here) to your device
- flash/install Nexus to the STOCK slot (includes GAaps and SuperSU)
You can switch to CM11 later if desired (overwrite Nexus in the STOCK slot) or move forward with unlocking the bootloader for access to the full suite of HDX roms.
Click to expand...
Click to collapse
Thank you for the quick answer.
Would install original stock OS be possible? in case i want to return it to amazon? Just bought it a week ago.
firebird21 said:
Thank you for the quick answer.
Would install original stock OS be possible? in case i want to return it to amazon? Just bought it a week ago.
Click to expand...
Click to collapse
Yes - but start with Nexus to get the device up and running with minimal risk. Reinstalling FireOS presents a few challenges given your previous actions. Post back if/when ready. Guessing you will want to stay on Nexus or go further and unlock the bootloader.
Davey126 said:
Yes - but start with Nexus to get the device up and running with minimal risk. Reinstalling FireOS presents a few challenges given your previous actions. Post back if/when ready. Guessing you will want to stay on Nexus or go further and unlock the bootloader.
Click to expand...
Click to collapse
It seems like the nexus has the same symptom. It's stucked at the loading logo.
firebird21 said:
It seems like the nexus has the same symptom. It's stucked at the loading logo.
Click to expand...
Click to collapse
Return to Safestrap recovery and perform a factory reset from the wipe menu (slider at bottom). Then reflash Nexus ROM.
Davey126 said:
Return to Safestrap recovery and perform a factory reset from the wipe menu (slider at bottom). Then reflash Nexus ROM.
Click to expand...
Click to collapse
Yes, this time it works.
firebird21 said:
Yes, this time it works.
Click to expand...
Click to collapse
Great. Enjoy your liberated HDX!
Davey126 said:
Great. Enjoy your liberated HDX!
Click to expand...
Click to collapse
Since the ROM was installed in Stock slot, should i be precautious of doing anything in future? I read the safestrap v4 thread that wifi will not work in second slot right, any update on this?
firebird21 said:
Since the ROM was installed in Stock slot, should i be precautious of doing anything in future? I read the safestrap v4 thread that wifi will not work in second slot right, any update on this?
Click to expand...
Click to collapse
No special precautions as some earlier limitations have been lifted. Avoid performing a factory reset from the native (not Safestrap) recovery menu as it can yield an unresponsive device that occasionally can not be recovered. Also try to keep a rom zip on the device at all times for emergency recovery.
Safestrap v4 is a special build for HDX with primary emphasis on allowing custom ROMs to run on a locked device running the native FireOS v4 kernel. There was never a need or intent to leverage secondary slots as was the case with Safestrap v3; in hindsight the developer probably should have disabled them. Aside from WiFi/BT radio issues processor management is also whacked. Only 2 of 4 processors will go online and both operate at maximum frequency. As a result the device never sleeps, performs poorly and has lousy battery life. None of these problems arise in the STOCK slot.
Keep in mind all 3rd gen devices can now be unlocked eliminating the need for Safestrap and opening the door to the full suite of custom ROMs including KitKat, Lollipop and Marshmallow variants. Unfortunately, the process is a bit involved as most steps are manual and require some technical experience.
Enjoy Nexus for now; it's a fine ROM that is fast, lean and energy efficient. Not to mention full access to Google Play Store/Services/apps and the ideal platform for Xposed extensions if you want even greater control over the hardware and user interface.
Davey126 said:
No special precautions as some earlier limitations have been lifted. Avoid performing a factory reset from the native (not Safestrap) recovery menu as it can yield an unresponsive device that occasionally can not be recovered. Also try to keep a rom zip on the device at all times for emergency recovery.
Safestrap v4 is a special build for HDX with primary emphasis on allowing custom ROMs to run on a locked device running the native FireOS v4 kernel. There was never a need or intent to leverage secondary slots as was the case with Safestrap v3; in hindsight the developer probably should have disabled them. Aside from WiFi/BT radio issues processor management is also whacked. Only 2 of 4 processors will go online and both operate at maximum frequency. As a result the device never sleeps, performs poorly and has lousy battery life. None of these problems arise in the STOCK slot.
Keep in mind all 3rd gen devices can now be unlocked eliminating the need for Safestrap and opening the door to the full suite of custom ROMs including KitKat, Lollipop and Marshmallow variants. Unfortunately, the process is a bit involved as most steps are manual and require some technical experience.
Enjoy Nexus for now; it's a fine ROM that is fast, lean and energy efficient. Not to mention full access to Google Play Store/Services/apps and the ideal platform for Xposed extensions if you want even greater control over the hardware and user interface.
Click to expand...
Click to collapse
That sounds good. You have been a great help to me.