Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
well
reconminicon said:
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
Click to expand...
Click to collapse
you could have accomplished most of that by one of the utilities in the development section and use same. 95 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
from what I read, after you have been rolled back BY Amazon you no longer need to OTA updates ?
jimyv said:
you could have accomplished most of that by one of the utilities in the development section and use same. 94 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
Click to expand...
Click to collapse
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
Edit: Just received a reply in another thread, it isn't currently possible to rollback 13.3.2.7. Hopefully it's not too far away though. =( If you did find a way too do it with 13.3.2.7 be sure to tell us how you did it then.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
jimyv said:
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
Click to expand...
Click to collapse
I bought it for my mother for Christmas and thought would be better with Andriod.
Got it out the box connected to the internet and it automatically updated to 4.5.1. I contacted Amazon using the SOS app and told them what I wanted to do and they rolled it back. They told me I would not get any future updates and customer service might be hard in the future as it would be running different software version. They requested TS to do it and said it would take two days. The update automatically came through and updated/backdated.
The SafeStrap version would of been the most recent as I think I downloaded it from their site.
The 2.0.2 Thor Rom I mentioned worked fine. The other one would not install. Cannot remember the message I was given but when going onto the Play Store Iand trying to download the daily newspaper it was saying designed for mobile. So I guess it was based on a mobile Rom. This was no good for me and thought my mother was getting along with the Amazon OS quite good. (As she is 67 and its her first device) so I ended up installing the Amazon OS from SafeStrap.
I ended up taking it back to Argos for an exchange, said it was switching itself of as I didnt know how to get rid of SafeStrap on boot and wanted the updates back. My mother loves it.
Amazon also removed the adverts free of charge but after the emplacement they are back. Need to SOS them again.
Hope this helps as I am no pro.
Sorry. Ignore it. Was 13.3.2.6 not 13.3.2.7
kindle fire hdx 14.3.2.8 (apollo 8.9)
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
dont try to rollback you will brick your device
undulus said:
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
Click to expand...
Click to collapse
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
jeryll said:
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
Click to expand...
Click to collapse
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Well
undulus said:
But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
I am glad you have working Nexus...
For downgrading using known method you must be on firmware xx.3.2.6, xx.3.2.5, xx.3.2.4. Several peoples reported that they bricked their device trying downgrade from xx.3.2.7! You can check here, but you have been warned, dont try that on your device!!! If you brick your device I cant help you, dont know how...
Default size for system partition is fine, I think...
undulus said:
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
Hi,
which version of Safetrap you installed? All links I see are for Apollo (in the thread linked above), and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
johim said:
Hi,
which version of Safetrap you installed? All links I see are for Apollo, and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
Click to expand...
Click to collapse
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
EncryptedCurse said:
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
Click to expand...
Click to collapse
I understand. Its all working now. Its more slow than usual thou.
Another question, once installed Nexus 2.0.2, do I need to root it? Any recommended method? I'm guessing I only need to flash supersu from safetrap, tried searchin in the safetrap topic, but its huge.
Related
hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
kasem71 said:
hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
Click to expand...
Click to collapse
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Arashkage said:
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Click to expand...
Click to collapse
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
if
kasem71 said:
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
Click to expand...
Click to collapse
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
jimyv said:
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
Click to expand...
Click to collapse
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
sorry
kasem71 said:
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
Click to expand...
Click to collapse
You dont already have the toolkit from development?it has adb drivers try that first .does your device show at all? Maybe with like an explanation point on it and the yellow triangle? If it does open that device in your device manager in and uninstall the drivers. Then run the driver install part of the utility toolkit .94. I'm sorry but no I cannot give you step-by-step or I will not considering it is in these forums at least a dozon times but I'll give you a link to a thread that explains it over and over again but you must be able to comprehend what you are reading and follow directions explicitly it does work it has worked for people but sometimes it takes several attempts . http://forum.xda-developers.com/showthread.php?t=2588608 remember but not just the first post has good information this is discussed all the way through these threads . And often pertain to different subjects . And if you don't think that you find what you need in this thread there are several several other threads in the general section and the troubleshooting section titled brick! Or please help! Or yada yada yada etc. and most will have to do with trying to get ADB back on a device.. For whatever reason. What ever you do do not go to factory recovery attempt a factory reset it will totally screw you. As long as you still have safestrap booting you have hope now you need to do what you did not do to begin with,and educate yourself thoroughly before moving forward with anything . All it will take is one more mistake on your part of the inability to completely read everything and understand everything and you will be calling Amazon for a replacement.. good luck why can't you restore a backup?
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
kasem71 said:
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
Click to expand...
Click to collapse
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
jimyv said:
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
Click to expand...
Click to collapse
when i do this, can i install updates from amazon ?
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
No!
kasem71 said:
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
Click to expand...
Click to collapse
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file BUT safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device AND YES IT will overwrite any system modifications and root access that's why you must flash the super SU after you flash the firmware zip if you want root right away..that is
jimyv said:
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file that safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device
Click to expand...
Click to collapse
ok thanks
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
It doesn't matter
lekofraggle said:
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
Click to expand...
Click to collapse
He didn't listen he chose to do in ADB sideload through safestrap and completely screwed it up now. As far as I know he still has not recovered this device
Q&A for [ROM] cm-11-20141216-UNOFFICIAL-thor
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] cm-11-20141216-UNOFFICIAL-thor. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
This is great news!! Hope somebody will release the 4.5.2 bootloader unlock or the right rooting method so that we can test this rom!.. I'ts nice to see people working on this kindle fire! Keep up the good work!:good:
xiloraptor said:
This is great news!! Hope somebody will release the 4.5.2 bootloader unlock or the right rooting method so that we can test this rom!.. I'ts nice to see people working on this kindle fire! Keep up the good work!:good:
Click to expand...
Click to collapse
Thanks ! The sooner should be a root method, crossing fingers
Is it possible to flash this from fully a rooted & safestrapped HDX Nexus 2.0.2. firmware?
Going Postal said:
Is it possible to flash this from fully a rooted & safestrapped HDX Nexus 2.0.2. firmware?
Click to expand...
Click to collapse
No.
i ve read this rom: cm-11-20141217-UNOFFICIAL-thor.zip on this topic: http://forum.xda-developers.com/kindle-fire-hdx/development/cm-11-20141216-unofficial-thor-t2974818
Cause my HDX have update automatically to FireOs 4.5.2 via wifi, then i have to wait for so long time, for any root version can apply for Fire OS 4.5.2, then use that rom, hopefully you guys can release that soon, thanks Cpasjuste, many thanks for your hardwork :good::good::good:
Dont try this ROM
Hi, I tried this ROM.
I am not on a late version of fire OS so I thought it would work - in actual fact I was on 13.3.2.4 with root access.
I now have a semi bricked kindle which just shows Amazon Kindle in white. As I have only owned the thing for a day this is somewhat gutting.
Any help anyone could offer would be appreciated.
I am getting a factory cable so will try to fix with that - if not a return is in order...
Avoid this mod like the plague...
Rob
buyaodanxin said:
Hi, I tried this ROM.
I am not on a late version of fire OS so I thought it would work - in actual fact I was on 13.3.2.4 with root access.
I now have a semi bricked kindle which just shows Amazon Kindle in white. As I have only owned the thing for a day this is somewhat gutting.
Any help anyone could offer would be appreciated.
I am getting a factory cable so will try to fix with that - if not a return is in order...
Avoid this mod like the plague...
Rob
Click to expand...
Click to collapse
Well the thread made it pretty clear...
Cpasjuste said:
There is currently a very few user which will be able to use it as you either need an unlocked bootloader or a root exploit for amazon firmware 4.5.2 (which will come someday...).
Click to expand...
Click to collapse
I am new to this - so didnt appreciate that I didnt have what the image said do you think a factory cable allow me to repair this or is it toast ?
EncryptedCurse said:
Well the thread made it pretty clear...
Click to expand...
Click to collapse
buyaodanxin said:
I am new to this - so didnt appreciate that I didnt have what the image said do you think a factory cable allow me to repair this or is it toast ?
Click to expand...
Click to collapse
How did you flash it?
D0ubl3_X said:
How did you flash it?
Click to expand...
Click to collapse
With Safestrap from Zip.
What I am guessing happened is safestrap was launched from initial bootloader - overflashed bits it shouldnt have now initial bootloader doesnt like what it sees so no booting...
Any suggestions appreciated.
That's strange. I didn't used safestrap since a while so I'm not 100% sure what happened but you probably flashed the ROM on your STOCK slot which probably erased safestrap... (Like said before you shouldn't have used this ROM in first place and you shouldn't flash to stock ROM).
The problem now is to get adb working so you can restore something but I guess it won't be enabled for you since your device do not boot the flashed kernel. I'm not sure if it will be possible to use fastboot for flashing a signed kernel made by @vortox , this is maybe your only solution.
Cpasjuste said:
That's strange. I didn't used safestrap since a while so I'm not 100% sure what happened but you probably flashed the ROM on your STOCK slot which probably erased safestrap... (Like said before you shouldn't have used this ROM in first place and you shouldn't flash to stock ROM).
The problem now is to get adb working so you can restore something but I guess it won't be enabled for you since your device do not boot the flashed kernel. I'm not sure if it will be possible to use fastboot for flashing a signed kernel made by @vortox , this is maybe your only solution.
Click to expand...
Click to collapse
I'm fairly certain that the boot image didn't flash, it's just the system that's not booting. I was reading through the bootloader source today and it *seems* that if the signature is invalid on a flashed partition, then the device will boot into fastboot mode. Had the boot image actually flashed, he would get a picture for about 2 seconds then a reboot. It wouldn't just hang if this was a sfv (signature verification failure, I decided to abbreviate because it's hell to type out).
r3pwn said:
I'm fairly certain that the boot image didn't flash, it's just the system that's not booting. I was reading through the bootloader source today and it *seems* that if the signature is invalid on a flashed partition, then the device will boot into fastboot mode. Had the boot image actually flashed, he would get a picture for about 2 seconds then a reboot. It wouldn't just hang if this was a sfv (signature verification failure, I decided to abbreviate because it's hell to type out).
Click to expand...
Click to collapse
Your right, the problem is now his system partition. With a few luck he still have adb enabled, I think its his last chance isn't it.
Can someone tell me what I need to do to move from the HDX ROM (Kernel .3.2.4) to this one?
Apollo Hartigan said:
Can someone tell me what I need to do to move from the HDX ROM (Kernel .3.2.4) to this one?
Click to expand...
Click to collapse
If I am not wrong:
Download the upload 13.3.1.0 update file from here: http://forum.xda-developers.com/showthread.php?t=2782159
Make a back-up of your data using Safestrap and copy it to your pc.
Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device. That would install a stock version with root enabled (if not u would need to do the whole root process)
Do a factory reset of your system
Copy the 13.3.1.0 downloaded before into the root and reboot to get the update installed.
Once the system is in 13.3.1.0 u would be able to install the TRWP and later the cm.
Maybe i am missing something, can anybody confirm?
qkp said:
If I am not wrong:
Download the upload 13.3.1.0 update file from here: http://forum.xda-developers.com/showthread.php?t=2782159
Make a back-up of your data using Safestrap and copy it to your pc.
Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device. That would install a stock version with root enabled (if not u would need to do the whole root process)
Do a factory reset of your system
Copy the 13.3.1.0 downloaded before into the root and reboot to get the update installed.
Once the system is in 13.3.1.0 u would be able to install the TRWP and later the cm.
Maybe i am missing something, can anybody confirm?
Click to expand...
Click to collapse
I can reply to myself. cm-11-20150101-UNOFFICIAL-thor.zip installed and running
I was in 13.3.2.4 with Safestrap, OTA updates disabled, root....
My steps:
1-Back up your data using Safestrap and copy it to your personal computer.
2-Select Stock rom.
3-Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device (Thor in my case). That would install a stock version pointing to 13.3.0.9. In my case root was not found so I needed to use again [TOOL:FROZEN] Faznx's HDX ToolKit v0.95 to disable OTA and put root.
3-Put the http://forum.xda-developers.com/showthread.php?t=2782159 at root level. Reboot the device, that would help the system to recognize the update, sometimes it takes a while. Put also TRWP and the cyanogenmod, I put them into download folder, but it doesn't matter.
4-Update the system, it would require a reboot.
5-Once in 13.3.1.0, check OTA updates are disabled and root is enabled, using Faznx again.
6-With OTA updates disabled, switch on wifi and install a file manager.
7-Install Rashr, download it from http://forum.xda-developers.com/showthread.php?t=2334554
8-Install TRWP image using Rashr.
9-Reboot on TRWP. Swip to factory reset and install the CM build.
10-Install CM Gapps for CM11.
I have found an issue with wifi, it required a reboot to get it working. Testing the other features right now.
I would like to use the google now launcher but CM doesn't detect the launcher as launcher. Maybe it is an issue of my device. Can someone try to set the google now launcher as default launcher?
At first, thanks a lot to all involved people to making a great device gets its full potential. Great work.
As it works fine for me so far, I was wondering if it is necessary to keep all the partitions, I got an emulateed ( legacy and 0) as well as two others. I suppose, these are two from the other rom slots I created. Im not sure if they take space at all?
Again, thanks for your effort and cheers.
disTractoR said:
At first, thanks a lot to all involved people to making a great device gets its full potential. Great work.
As it works fine for me so far, I was wondering if it is necessary to keep all the partitions, I got an emulateed ( legacy and 0) as well as two others. I suppose, these are two from the other rom slots I created. Im not sure if they take space at all?
Again, thanks for your effort and cheers.
Click to expand...
Click to collapse
No you don't need to delete them they are symlink used by the system and do not use space.
Hello i am currently running 13.3.2.1 on my HDX, i already root it and everything the only problem is that on that version recoveries dont work.
I tried them already.
So I downloaded the 13.3.2.3.2 to test on that one, this would be an upgrade for me but i already disable the OTA's. How do i upgrade to use recovery?
and question will this lose root?
what are the steps dont find anything.
Thank you
masterchop said:
Hello i am currently running 13.3.2.1 on my HDX, i already root it and everything the only problem is that on that version recoveries dont work.
I tried them already.
So I downloaded the 13.3.2.3.2 to test on that one, this would be an upgrade for me but i already disable the OTA's. How do i upgrade to use recovery?
and question will this lose root?
what are the steps dont find anything.
Thank you
Click to expand...
Click to collapse
TWRP should work fine on your current firmware level (13.3.2.1). However, since it is advisable to upgrade the bootloader to 13.3.2.3 do the following:
- install Flashify (free download from your favorite app store)
- use Flashify to install bootloader upgrade (here)
- use Flashify to install TWRP (here)
Davey126 said:
TWRP should work fine on your current firmware level (13.3.2.1). However, since it is advisable to upgrade the bootloader to 13.3.2.3 do the following:
- install Flashify (free download from your favorite app store)
- use Flashify to install bootloader upgrade (here)
- use Flashify to install TWRP (here)
Click to expand...
Click to collapse
Thank you bro!! i just got a boner!! ajajaj ill test that at home today . thank you!!:good:
masterchop said:
Thank you bro!! i just got a boner!! ajajaj ill test that at home today . thank you!!:good:
Click to expand...
Click to collapse
Err...glad I could help. Hope the Kindle part goes ok too.
Flashify is a powerful tool. Make sure you know what your are doing and flash the right components into the proper partitions. Flashify offers some protections but you can easily brick your device if done wrong. Assuming everything else is ok with your device; if stock recovery is borked you should probably fix that first.
Davey126 said:
Err...glad I could help. Hope the Kindle part goes ok too.
Flashify is a powerful tool. Make sure you know what your are doing and flash the right components into the proper partitions. Flashify offers some protections but you can easily brick your device if done wrong. Assuming everything else is ok with your device; if stock recovery is borked you should probably fix that first.
Click to expand...
Click to collapse
I was about to install flashify but my Google store is force closing multiple times.
I think i have stock recovery broken, do when i go to recovery i get blank screen.
I manage to install it thank you it was super easy with it. I have the SIM card version have test any roms
masterchop said:
I manage to install it thank you it was super easy with it. I have the SIM card version have test any roms
Click to expand...
Click to collapse
Glad it worked out. You can now flash CM11 or Nexus 2.0.5. CM12 requires an unlocked bootloader.
Hey guys ive got a hdx 7' RUNNING FIRE OS 3.2.4 everything i have been reading is saying that this version is somewhat unique in that there are a few roms availible mostly from safestrapp but most are not, twrp requires 3.2.3 and earlier as well as the bootloader unlock procedure. Can anyone point me in the direction on how to downgrade to one of the earlier versions. Currently i am rooted, ota disabled via: hdxtookit, i had safestrapp and a asop rom installed but was getting google play services stopped working error messages and restored to factory because i havent used the kindle in a year. Anyways i'm looking to get back into it and got cm 12.1 on my sgs3 and wanted to get something similar but keep runninginto problems with my version fire os. So just need a quick link to a roll back procedure in english and i should be able to do the rest from unlock - twrp - roms etc. I've been searching off and on the past few weeks but do not find anything definitive so i decided to finally ask to get an answer thanks for any and all help.
131 views no replies can anyone guide me to a solution?
rbkelley89 said:
131 views no replies can anyone guide me to a solution?
Click to expand...
Click to collapse
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
jeryll said:
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
Click to expand...
Click to collapse
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Davey126 said:
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Click to expand...
Click to collapse
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
rbkelley89 said:
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
Click to expand...
Click to collapse
Locate HDX toolkit in the Android Development thread and try to remove the OTA block that way. Keep WiFi off or you might receive an unwanted update.
Although not recommended twrp can be installed with a locked bootloader.
Travelling this week so can't get into more detail. Suggest you keep reading. Don't do stuff unless you are absolutely confident in your skills, knowledge, risks and expected outcome(s). Post questions. Many folks willing to help if you have done your homework. Sorry for brevity ...
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
XxD34THxX said:
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
Click to expand...
Click to collapse
The path I am suggesting does not involve modifying build.prop.
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice finding, I absolutely forgot that this existed, of course he can use that thread with rollback images to downgrade to x.3.1.0! Then he can install TWRP etc... (as I did in the past - proof below )
jeryll said:
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP
Click to expand...
Click to collapse
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Davey126 said:
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
Click to expand...
Click to collapse
pquan2009 said:
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Click to expand...
Click to collapse
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
jeryll said:
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
Click to expand...
Click to collapse
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
rbkelley89 said:
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
Click to expand...
Click to collapse
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Davey126 said:
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Click to expand...
Click to collapse
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
rbkelley89 said:
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
Click to expand...
Click to collapse
You can grab stock images here. Be absolutely certain you snag the correct one for your device. Verify md5=c49c0363de4d8dfa5c87c1bdb88aa2ba with ES FIle Explorer (long click the file and select 'properties' from the 'more' menu). Note you will loose root and OTA blocking. Be sure to stay off wifi. Use HDX Toolkit (requires usb tether to Windows PC) to root 3.1.0 and reblock OTA if needed.
I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.