tim on 1309 now wth rollback but no way to copy .310 file to root lol with amazon. Ive tried to copy thru safe strap but upon reboot its not there..i turned on wifi and downloaded es explorer and mounted rw and now just get copy failed not enough space.. Im on stock with 32 gig left oi vey
What's the problem here? Your system will not boot? If you have the file on your PC boot up your tablet plug it in and copy it. I don't guess I understand what the issue is here . You're not trying to push it to system or to move it to cache even, you just need it on your Sdcard and not with in any files or foldersi know im talking to myself i forgot adb so im trying it now just want to understand the cant copy not enough room error in es explorer
opps heres what i got
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>adb push C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\update-kindle-188.8.131.52_user_310079820.bin /
failed to copy 'C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\update-kindle-184.108.40.206_user_310079820.bin' to '//update-kindle-220.127.116.11_user_310079820.bin': Read-only file system
Not sure what the problem is. Possible the 13.3.1 update file is bad. Did you verify MD5? Once the file is on sdcard you initiate from within FireOS (check for updates). You may have to enable wifi for the update to be processed correctly. Put your device in 'airplane mode' first to avoid an unwanted gift from Amazon. It's possible Safestrap is getting in the way but you obviously don't want to remove it as it is your only means of recovery if something should go wrong...like it did.when it says initiate update from device options does that just mean to go into sd card with a file explorer and open the file as an image file? i have successfully rolled back from 3.2.4 to 3.0.9 xx and put the 3.1 on the sd card. now i am wondering what to do now. do i open it from safestrap and flash it there? Because when i got to system updates under device it says to activate the internet before i can update anything?? I was thinking that if i did that it would update to the latest version of fire
So i went to devise software update and checked for the update iand it found the 13.3.1 rollback update so i went through with the update and it got stuck on the grey screen, i let it sit for an hour then rebooted using power volume button and it rebooted with ss and got me back to 13.0.9 so im back to the question of what do i do to update should i just wait a few hours at the grey screen and see if it'll finally boot.
Not sure what the problem is. Possible the 13.3.1 update file is bad. Did you verify MD5? Once the file is on sdcard you initiate from within FireOS (check for updates). You may have to enable wifi for the update to be processed correctly. Put your device in 'airplane mode' first to avoid an unwanted gift from Amazon. It's possible Safestrap is getting in the way but you obviously don't want to remove it as it is your only means of recovery if something should go wrong...like it did.
Give it another whirl using the above suggestions. If still stuck might try to root and flash twrp on 13.0.9 which I believe is possible (don't do this just yet...thinking out loud).
Do you have ES File Explorer installed? If not, get it. Then hold the file you want to check for about two seconds, so it is marked, then select "More" in the lower right corner, in the menu select "Properties", then click "Show checksum", it'll give you md5 & sha-1.okay the md5 file is something i was trying to check out, i know its easy to do form my samsung phone by just going into the settings, how is it done on the kindle?
I did try it again and let it sit for about 3-4 hours and still nothing so i rebooted still on 3.0.9 xx
Do you have ES File Explorer installed? If not, get it. Then hold the file you want to check for about two seconds, so it is marked, then select "More" in the lower right corner, in the menu select "Properties", then click "Show checksum", it'll give you md5 & sha-1.
Regarding the update you must use the FireOS update function as mentioned by Davey126.
That is the correct md5. Going to try a different approach. I'll post back shortly with thoughts; need to verify something first. Hang tight ...okay ive got my md5 and what not from the downlaod file where do i find the currrent os that it needs to match up with. what directory is that under?
here is the md5 and sha-1 from the file 13.3.1 not comlete sha-1
md5 - c49c0363de4d8dfa5c87c1db88aa2ba
I captured the md5 from a known good 3.1.0 update file.
I captured the md5 from a known good 3.1.0 update file.
Here's where I believe you stand. It appears something was amiss with your prior 3.2.4 install. If you've had it for awhile corruption can occur over time - especially on a rooted device where anything is possible and nothing is protected. I'm not going to dive into speculation as to the source. On the surface it many seem the 3.2.4 'rollback' introduced the problem but I would submit it simply exposed it as you likely had OTA blocked before.
There are a couple paths to pursue; both are risky. First I need some info from you. Can you access Amazon's stock recovery? Typically this is done by powering off your device (not just sleeping) and then pressing power + vol-up at the same time. Release the power button when the grey logo appears followed by the volume button. After a few seconds a recovery screen should appear hopefully with only two options:
Choose reboot (NOT reset) and post your findings.
Appears your stock recovery partition is borked and probably has been for some time. You would not necessarily notice unless trying to access stock recovery (rare) or perform a rollback/upgrade which requires a working recovery. Normally I would lean towards repairing recovery but given the presence of Safestrap and now a soft bootloop I think moving to a stable rom takes priority. I'm assuming to can still boot into Safestrap recovery.
Thanks ggow, but this is a warning to all apollo (HDX 8.9) users - do not use this file to rollback attempt!
@ggow you forgot to edit build.prop file, so after anyone boot from this file (md5 hash: 0f9f3b084500b888fc66415a8539a341), kindle will not continue with downgrade to 18.104.22.168 :crying:
No harm done for me, as I backuped everything I can, but beware, if you dont want problems (I found extremely difficult install anything through adb on this installed/running rollback ... you can try edit build.prop file to correct values for downgrade by yourself, but messing with build.prop is highly risky and small mistake and brick is for sure, so you have been warned) WAIT for ggow to upload correct rollback image, or correct edited build.prop for downgrade