Related
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.
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.
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.
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo
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 [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo. 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!
droiduzr2 said:
My device is "bricked". I screwed up safestrap install and my device just boots to the grey kindle screen.
Click to expand...
Click to collapse
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
draxie said:
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
Click to expand...
Click to collapse
my device boots up and stays at grey kindle screen
nothing happens after
That doesn't tell us anything.
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Bruder Torgen said:
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Click to expand...
Click to collapse
If you're not booting into TWRP, then it probably didn't install.
Try using Flashify.
Great, I had to sideload Flashify apk and install it via adb install, then it worked , I could see the difference
Till now all seems great although the way to reach it is not described perfectly (as I normally have only to do with windows systems, too many steps I had to find out by myself and I never knew if the tablet will be still alive after the next step )
Pretty Good Work , thanks a lot for all your effort !!!!
Factory Reset?
droiduzr2 said:
my device boots up and stays at grey kindle screen
nothing happens after
Click to expand...
Click to collapse
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
droiduzr2 said:
I can get into that weird looking recovery that does not allow fastboot.
Click to expand...
Click to collapse
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
draxie said:
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
Click to expand...
Click to collapse
Thank you for the detailed response.
Yes, I did install safestrap. I admit I did not fully understand what I was doing. I thought I would just wipe everything to have a clean system as we usually do for most devices. I wiped the system also which deleted the system rom.
Upon reboot it just sits at the grey kindle screen never booting past. I played around with the buttons and stumbled upon the power and vol+.
I got into Kindle system recovery and did the wipes but nothing boots up because I deleted the system os.
Would ADB work from the Kindle recovery screen?
Remember I have no OS on the device now.
Please let me know what to do now?
Where are the Kindle drivers for Win7 which has ADB driver for it. The problem is windows will not recognize the device I don't think.
14.3.2.4 can have twrp?
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
vandy_andy said:
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
Click to expand...
Click to collapse
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
EncryptedCurse said:
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
Click to expand...
Click to collapse
Thank you for the answer.
So , so far no easy way.
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
jimyv said:
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
Click to expand...
Click to collapse
Well, if you have adb access and root, you can try this
jeryll said:
Well, if you have adb access and root, you can try this
Click to expand...
Click to collapse
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
jimyv said:
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
Click to expand...
Click to collapse
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
jeryll said:
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
Click to expand...
Click to collapse
Apollo first release of TWRP started at (.0) flashed renamed files each increment up to and including( .2.4 )I know I can redo the downgrade and anything else I need to do once I get a usable ui
not unless the recovery is black screen also. What is strange is when it is booted and I tried adb shell I did get su prompt ,,, just no launcher or notification bar etc..this is what I'm thinking let me know if I am mistaken. I should grab and flash a stock recovery image via the same as flashing this recovery with PC. Push. 3.2 build prop file to system then try this. http://forum.xda-developers.com/show....php?t=2793253 with .2.4 WiFi was off before black screen and OTA had been re- enabled I believe.and this is probably important to I do actually have a lock screen. And poweroff menu I am going to try that command now..
access denied going to reboot everything and try again
this is double posted in main thread with @ggow
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Bruder Torgen said:
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Click to expand...
Click to collapse
It's as simple as flashing the new image.
This is no different than any other device.
I thought the root for 4.5.2 and there's no root for 4.5.3 this is why I didn't update and disabled OTA. How can this method is for 4.5.3 only and it requires root? I think I miss something here. Please, help me to get it
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.