Related
Hi if we freeze the OTA Silent Install will it stop the ora did anyone try?
Sent from my Kindle Fire using xda premium
Proven to not work
krelvinaz said:
Proven to not work
Click to expand...
Click to collapse
How can it not work if it freezes or if we remove the file?
Sent from my Kindle Fire using xda premium
You can remove the file, change the file, Freeze it, remove it's permissions whatever you want, but it will NOT stop an OTA update because the process that does the update creates a new one when it it needs it.
Proven Fail!
ref:
http://forum.xda-developers.com/showthread.php?t=1401073
samomamo said:
How can it not work if it freezes or if we remove the file?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Because that app is only a tool used by the app in charge of the whole upgrade process and it appears to get reinstalled from scratch during that process if it has been moved or removed
Thank you guy's for the info.
Sent from my Kindle Fire using xda premium
What if we are not registered to Amazons account? Becouse wen I wanted to get the ota I registered ans clicked on sync to get the ota. Maybe the registration has something to do with it?
Sent from my Kindle Fire using xda premium
just root ur phone and install cm7 or try droid wall that may block it but we dont have a update to check
I bought mine when it was on 6.0.0 and installed Root Uninstaller, backed up otasilentupdate.apk and then deleted it. After that no more updates. I guess experience varies, just sharing my ways. (btw i didn't register cuz im not in the US).
because u didnt register is why u didnt get the update
We have found out that when ur registered and u try to freeze the the silent update or rename it, it still updates no matter what. I hear droid wall stops the update but not sure
samomamo said:
What if we are not registered to Amazons account? Becouse wen I wanted to get the ota I registered ans clicked on sync to get the ota. Maybe the registration has something to do with it?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Probably. I had de-registered my Kindle prior to the 6.2.1 update and I did not get the update, even though it was out for a few days and my wifi was on / tablet was being extensively used during those days.
I did get the 6.2 update before I de-registered. So almost certainly, the de-registration helped.
here is my experience:
kf was and is registered
removed /system/etc/security/otacerts.zip -> update downloaded but did not install -> was automatically deleted from cache folder after failed attempt to install
installed "nfx-update-kindle-6.2.1" -> http://forum.xda-developers.com/showthread.php?t=1407852
6.2.1 is much more responsive than older version
b.t.w. root method for 6.2.1 is available:
http://forum.xda-developers.com/showthread.php?t=1399889
It seems to me that when an individual registers amazon uses that mac address for sending the update.... I could be wrong so please do not think that I am saying this is entirely true but, if all of these methods are confirmed as not working such as freexzing,removing apps, etc... then there has to be somesort of way that amazon is still able to update to your fire...
After researching for many weeks on how to root my Kindle Fire, I finally became a noob and rooted my first device. Thanks to all the awesome devs on this site to make that possible.
The next thing I want to do is start flashing some different ROMs to see what my Fire can really do.
After I flash a ROM, do I install data from a previous backup or do I have to start from scratch each time I install a new ROM?
If someone could help shed some light on switching between ROMs (I will be using TWRP) or point me to a thread that might cover this topic I would appreciate it very much. Thanks for your help.
Sent from my DROIDX using XDA App (XDA app keeps FC on my Fire after I log in!)
Depends on what data you are talking about.
General when switching between roms I follow a procedure.
1.Back up current apps with titanium backup.
2.Back up launcher settings with whichever launcher I'm using.
3.Boot into recovery.
4.Factory wipe - dalvik,cache,data,batt,rotation.
5.Flash rom.
6.Boot rom.
7.Restore apps from titanium.
8.Restore launcher settings.
Hope this helps!
Thanks! I am backing up my apps and system data with TB right now.
So is the backup I do within TWRP a ROM backup that has nothing to do with apps or data?
Sent from my DROIDX using XDA App
I always backup in TWRP first. Wipe cache before and after installing rom.
Sent from my Amazon Kindle Fire using xda premium
KnappyRoot said:
So is the backup I do within TWRP a ROM backup that has nothing to do with apps or data?
Click to expand...
Click to collapse
Correct, that's why you need to backup with TB
Just trying to jump into this same world, what happens with all of your books and applications from Amazon when you switch. Does Amazon still push your books to your Kindle.
Sent from my Kindle Fire using Tapatalk
MikeGolfW said:
Just trying to jump into this same world, what happens with all of your books and applications from Amazon when you switch. Does Amazon still push your books to your Kindle.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
you can still access your books through the Kindle app and all apps I've downloaded when on stock ROM have worked on my CM7 build
BluesHawk said:
you can still access your books through the Kindle app and all apps I've downloaded when on stock ROM have worked on my CM7 build
Click to expand...
Click to collapse
Thank-you BluesHawk, I took the first step last night and installed TWRP along with Burritto. Now we'll see how long it takes me to be brave enough for the next step.
MikeGolfW said:
Thank-you BluesHawk, I took the first step last night and installed TWRP along with Burritto. Now we'll see how long it takes me to be brave enough for the next step.
Click to expand...
Click to collapse
You're welcome. When you install market make sure to expand it with this build.prop editing guide
BluesHawk said:
Correct, that's why you need to backup with TB
Click to expand...
Click to collapse
Actually TWRP has Ann option to backup data, and I have used it. Never needed TB myself
I just started using TB because it can reliably/easily move apps to SD - freed up LOTS of device memory. Though Apps2SD ran on my rooted stock Fire, it wouldn't give me the option to move them.. In fact, when installing and running Apps2SD, it never requested superuser rights.
I believe I have all the files in the right place to install CM7 barebones. I was wondering, if I wanted to go back to my stock rooted ROM if it was just as easy as installing the backup I created with TWRP. Guess I could unroot and remove TWRP and start from scratch but I am hoping not to go that route.
I think bob posted this same question in another thread but I thought I would ask here too to see if we could get more answers.
Thanks for all your help.
Sent from my DROIDX using XDA App
would never ever flash the original stock rom (besides if returning the kf) cause you loose fff,twrp and root
furthermore there is a higher risk to brick
would instead recommend to flash one of the prerooted stock roms if you want to go back to stock:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
I am still a little confused. What is the purpose of doing a backup within TWRP?
I just want to be prepared before I install my first ROM.
Sent from my DROIDX using XDA App
KnappyRoot said:
I am still a little confused. What is the purpose of doing a backup within TWRP?
I just want to be prepared before I install my first ROM.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
to get back to your previous state in case something goes wrong
I just rooted my new kindle that I just got today using the bin4ry method and I have the superuser app. Cool, but I have no clue where to go from here. No idea what a custom rom is or why I would even need one or any of that stuff.
Is there a starter package or some sort for first time kindle users?
The system version is 7.4.6
jman1234 said:
I just rooted my new kindle that I just got today using the bin4ry method and I have the superuser app. Cool, but I have no clue where to go from here. No idea what a custom rom is or why I would even need one or any of that stuff.
Is there a starter package or some sort for first time kindle users?
The system version is 7.4.6
Click to expand...
Click to collapse
What I did for my mom's KFHD was root it, disable the OTA, and install APEX launcher.
http://www.androidpolice.com/2010/05/01/custom-roms-for-android-explained-and-why-you-want-them/ This explains custom ROMs.
Personally, I didn't install a second recovery or a custom ROM on my mom's KFHD because 1) It's not mine 2) I don't have a factory cable 3) She doesn't live with me so I won't get much troubleshooting time if something goes wrong.
She really hated the carousel feature of the stock kindle.
I used Kindle Fire First Aide, found here - http://forum.xda-developers.com/showthread.php?t=2096888 ----- ((actually I used an older version from before June))
jman1234 said:
I just rooted my new kindle that I just got today using the bin4ry method and I have the superuser app. Cool, but I have no clue where to go from here. No idea what a custom rom is or why I would even need one or any of that stuff.
Is there a starter package or some sort for first time kindle users?
The system version is 7.4.6
Click to expand...
Click to collapse
I would read the beginner guide here:
http://forum.xda-developers.com/showthread.php?t=1552547
Then you can read about upgrading here:
http://forum.xda-developers.com/showthread.php?t=2271909
R1Mike said:
I would read the beginner guide here:
forum.xda-developers.com/showthread.php?t=1552547
Then you can read about upgrading here:
forum.xda-developers.com/showthread.php?t=2271909
Click to expand...
Click to collapse
Just what I was looking for, thanks
jman1234 said:
Just what I was looking for, thanks
Click to expand...
Click to collapse
You're welcome. There is a lot to read and learn.
R1Mike said:
You're welcome. There is a lot to read and learn.
Click to expand...
Click to collapse
Got another question. I'm currently reading this thread http://forum.xda-developers.com/showthread.php?t=2271909 and I got to the point where I'm using fireflash. I see the red lettered warning. Do I put a checkmark in the "flash kfhd7-u-boot-prod-7.2.3.bin"? and the "apply stack override" boxes?
Yes u must check that flash 7.2.3 or you will get a red screen brick and need a fastboot cable to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Yes u must check that flash 7.2.3 or you will get a red screen brick and need a fastboot cable to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Bad news.
I used fireflash (checked both boxes before installing the flash), but now my kindle always boots into the twrp menu and it won't let me install zip files. I keep getting a assert failed message. Is this something I can fix on my own, or do I need a special cable to fix it or is it screwed? I can get into fastboot (assuming it's the black screen with the fastboot text in the middle)
jman1234 said:
Bad news.
I used fireflash (checked both boxes before installing the flash), but now my kindle always boots into the twrp menu and it won't let me install zip files. I keep getting a assert failed message. Is this something I can fix on my own, or do I need a special cable to fix it or is it screwed? I can get into fastboot (assuming it's the black screen with the fastboot text in the middle)
Click to expand...
Click to collapse
I don't know enough to answer your questions with me being new to this also; however, being able to still get to fastboot is good and that you can use KFFA to put an older version 7.2.3 back onto you KFHD and then retry.
jman1234 said:
Bad news.
I used fireflash (checked both boxes before installing the flash), but now my kindle always boots into the twrp menu and it won't let me install zip files. I keep getting a assert failed message. Is this something I can fix on my own, or do I need a special cable to fix it or is it screwed? I can get into fastboot (assuming it's the black screen with the fastboot text in the middle)
Click to expand...
Click to collapse
Do you have verification enabled?, try to turn it off before flashing, by the way check the Mr5 of the file you downloaded....maybe it got corrupted.
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
R1Mike said:
I don't know enough to answer your questions with me being new to this also; however, being able to still get to fastboot is good and that you can use KFFA to put an older version 7.2.3 back onto you KFHD and then retry.
Click to expand...
Click to collapse
Would that be safe since the version I'm using is 7.4.6 and it's an HD 7"?
jman1234 said:
Would that be safe since the version I'm using is 7.4.6 and it's an HD 7"?
Click to expand...
Click to collapse
Yes, 7.2.3 is safe to use. If you are unsure, update to 7.2.3 and wait a while and Amazon will update your KFHD to 7.4.6, and then retry. I also believe I read somewhere on the forum that 7.2.3 is better to use.
R1Mike said:
Yes, 7.2.3 is safe to use. If you are unsure, update to 7.2.3 and wait a while and Amazon will update your KFHD to 7.4.6, and then retry. I also believe I read somewhere on the forum that 7.2.3 is better to use.
Click to expand...
Click to collapse
Alright. I picked option 3 (completely restore KFHD 7.2.3) and it's currently downloading some files.
jman1234 said:
Alright. I picked option 3 (completely restore KFHD 7.2.3) and it's currently downloading some files.
Click to expand...
Click to collapse
Let us know how it goes.
R1Mike said:
Let us know how it goes.
Click to expand...
Click to collapse
Seems to be fine again. Currently on the 7.2.3 system version. Apart from having 1% battery life now and no icons on the homescreen, it went pretty smoothly. Should I wait until it charges up some more before attempting to re-root it or is it fine being plugged in the pc?
jman1234 said:
Seems to be fine again. Currently on the 7.2.3 system version. Apart from having 1% battery life now and no icons on the homescreen, it went pretty smoothly. Should I wait until it charges up some more before attempting to re-root it or is it fine being plugged in the pc?
Click to expand...
Click to collapse
1) Definitely let it charge first.
2) The partition images you used to restore your device should already be rooted.
fort reutoyme
soupmagnet said:
1) Definitely let it charge first.
2) The partition images you used to restore your device should already be rooted.
Click to expand...
Click to collapse
I think it's rooted. the google play store app is there and there's another one called "SuperSU". Is that the same as SuperUser?
jman1234 said:
I think it's rooted. the google play store app is there and there's another one called "SuperSU". Is that the same as SuperUser?
Click to expand...
Click to collapse
Yes, SuperSU is superuser. If you don't want to lose being root and keep 7.2.3 for upgrading, turn over the air updates after your battery is charged back up.
R1Mike said:
Yes, SuperSU is superuser. If you don't want to lose being root and keep 7.2.3 for upgrading, turn over the air updates after your battery is charged back up.
Click to expand...
Click to collapse
Okay, cool. Will I run into the same problem with the twrp booting or is that fixed since I'm on 7.2.3 now?
jman1234 said:
Okay, cool. Will I run into the same problem with the twrp booting or is that fixed since I'm on 7.2.3 now?
Click to expand...
Click to collapse
You shouldn't have any problems. If you follow the instructions closely from http://forum.xda-developers.com/showthread.php?t=2271909
I was bored and decided to try to build a rom and see what happens, i don't know any c coding so its a bit of it it compiles and works great, if it doesnt work then i'll need a c compiler and both my friends that know c coding dont get online often.
Anyways about the details, i have sucessfully built a 7" and 8.9" Kindle Fire HD version of the rom, soupmaget is going to test the 8.9" rom, but i need a 7" tester prefereably with a fastboot cable incase things go south like the first time where it deleted the second bootloader from the system partition, though i think i fixed that. Anyways if you are interested in testing this pre-alpha build of the rom, plz reply back and il send you a link in a private message to the rom. On another note te tester should also be prepared to do a full backup of their sdcard of their device including the sdcard because i have not ever used this os so i have no idea how it handles the sdcard data, while it shouldnt wipe it i just think it would be a good idea in general.
I can test it.
I have a fastboot cable and the only files that I have are books anyway.
OK sweet I'll pm you the link with instructions.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I'm your Huckleberry.
---------- Post added at 04:58 PM ---------- Previous post was at 04:54 PM ----------
stunts513 said:
i need a 7" tester
Click to expand...
Click to collapse
I messed up the quote last time. Anywho, link me if you want.
Sweet I'll pm u too.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sweet I'll pm u too.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
First test:
Downloaded and flashed just fine. After wiping Dalvik/CACHE and rebooting into system it did show the Kindle Fire Animation followed by the TWRP animation and then displayed fastboot. Holding the power button down for 20 seconds powered it off and access to TWRP was still possible. Flashed a nandroid and all is fine. Let me know when the next update is available.
LinearEquation said:
First test:
Downloaded and flashed just fine. After wiping Dalvik/CACHE and rebooting into system it did show the Kindle Fire Animation followed by the TWRP animation and then displayed fastboot. Holding the power button down for 20 seconds powered it off and access to TWRP was still possible. Flashed a nandroid and all is fine. Let me know when the next update is available.
Click to expand...
Click to collapse
So ok im confused it just went into fastboot after trying to boot or something? If thats the case there must be something very wrong with the kernel i think.
stunts513 said:
So ok im confused it just went into fastboot after trying to boot or something? If thats the case there must be something very wrong with the kernel i think.
Click to expand...
Click to collapse
Correct. The flash was successful (in other words it did not fail.) I click reboot into system from TWRP. I saw the Kindle Fire animation followed by the TWRP animation and then, then stead of the ROM animation, it went strait to fastboot. Then I force powered it down, was able to access TWRP, wiped and then flashed my backup nandroid and the Kindle booted with no permanent issues. But yes, something is not right there.
Basically, rather than booting into the system, it booted into the bootloader.
LinearEquation said:
Correct. The flash was successful (in other words it did not fail.) I click reboot into system from TWRP. I saw the Kindle Fire animation followed by the TWRP animation and then, then stead of the ROM animation, it went strait to fastboot. Then I force powered it down, was able to access TWRP, wiped and then flashed my backup nandroid and the Kindle booted with no permanent issues. But yes, something is not right there.
Basically, rather than booting into the system, it booted into the bootloader.
Click to expand...
Click to collapse
*facepalm* i'm going to have to check the kernel image, this whole setup i used is kinda rigged because this os was designed to work with a specific version of jb aosp, and cm 10.2 is close to that revision but not exact so i used aosp as my source and had to modify some of hashcodes file sto get it to compile, but it finally did compile, seeing as there were problems here and there i'm going to take a wild guess the boot.img is using the standard header and not amazons, and thats just a wild guess at best, i don't know what a normal header would do on a kindle, but i will try to decompile the boot.img and see if it errors out like a usual kindle boot.img would if you dont shave off the header with dd.
Man i hate double posting but i thought i'd mention i think what i guessed at was right because it split immediately upon running the splitting script... so now i guess i need to ask hashcode wtf is going on and how to fix it since it's not compiling the boot.img with the correct header.
Sounds like a plan.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Well I talked to hashcode, I'm trying to get it fixed, but I'm a bit confused, makefile coding isn't my specialty, I am going to ask other RC's and see what I can dig up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
hi!!
stunts513 said:
I was bored and decided to try to build a rom and see what happens, i don't know any c coding so its a bit of it it compiles and works great, if it doesnt work then i'll need a c compiler and both my friends that know c coding dont get online often.
Anyways about the details, i have sucessfully built a 7" and 8.9" Kindle Fire HD version of the rom, soupmaget is going to test the 8.9" rom, but i need a 7" tester prefereably with a fastboot cable incase things go south like the first time where it deleted the second bootloader from the system partition, though i think i fixed that. Anyways if you are interested in testing this pre-alpha build of the rom, plz reply back and il send you a link in a private message to the rom. On another note te tester should also be prepared to do a full backup of their sdcard of their device including the sdcard because i have not ever used this os so i have no idea how it handles the sdcard data, while it shouldnt wipe it i just think it would be a good idea in general.
Click to expand...
Click to collapse
send me instructions for the test
I will next time I make a build after fixing this boot.IMG issue I have, I haven't seen hashcode in the IRC since Wednesday and I haven't been able to fix the makefile issue yet, I have to transfer some of the code from cm's /build/core/Makefile to mine, specifically the parts that let's board_custom_booting_mk work to generate the booting correctly. You would think there would be a patch for aosp that does this, but I guess most devices don't need a custom bootimg?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Test
stunts513 said:
I will next time I make a build after fixing this boot.IMG issue I have, I haven't seen hashcode in the IRC since Wednesday and I haven't been able to fix the makefile issue yet, I have to transfer some of the code from cm's /build/core/Makefile to mine, specifically the parts that let's board_custom_booting_mk work to generate the booting correctly. You would think there would be a patch for aosp that does this, but I guess most devices don't need a custom bootimg?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have understood that the boot.img should go hand in hand with the system you build,
so a custom boot.img should be mandatory
excuse my bad English, I use google translator
Any chance of a build compatible with the kf2?
I'm too broke to buy the newest fire hdx that's on sale for $180 today,so I'm holding on to my 2012 non-hd fire.
Sent from my Amazon Kindle Fire2 using XDA Premium HD app
agentfusion said:
Any chance of a build compatible with the kf2?
I'm too broke to buy the newest fire hdx that's on sale for $180 today,so I'm holding on to my 2012 non-hd fire.
Sent from my Amazon Kindle Fire2 using XDA Premium HD app
Click to expand...
Click to collapse
Keep an eye on Swappa. People are dumping their older models for cash for the newer models.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
I plan on building it for all supported kf's, right now I'm working out the build kinks and seeing if it will even boot. Just fixed the makefile issue but I may have introduced another issue by using a certain patch to disable recovery a while back, so I may need to grab a fresh copy of the make file and repatch it, I'll pm when it's more ready to test which will be soon.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Send me a PM once you get the boot.img thing fixed. I have a fastboot cable, too.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Hi,
Just for understanding right. Is this for the Kindle Fire HD KFSOWI (3rd gen)?
If yes then I absolutely want to try your Rom.
Thanks in advance.
I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed
stunts513 said:
I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed
Click to expand...
Click to collapse
If I can get my Kindle back up and running, I'll have a go at it for you. But that's a pretty big if right now.
Sent from my iPod touch using Tapatalk, somewhere in the time vortex
Ok thanks, kinda surprised no one has offered before you. This had over 100 views. I guess not too many people are using amazon os that are willing to risk a softbrick. Hopefully this will work I think it is a bit safer than the other methods for beginners that don't want to risk anything.
Tapatalk is annoying me to no end lately... Had to type this message again because quick reply is being glitchy.
Sent from my Amazon Tate using Tapatalk
I could also volunteer. I have an extra Kindle fire 7" Hd. It is rooted and running 7.4.8. I have my trusty fastboot cable and I already have system images for a quick restore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
The safest method is to "fastboot -i 0x1949 flash bootloader oldbootloader.bin" then "fastboot -i 0x1949 reboot" (assuming you're using the cable and it auto-kicks you into bootloader mode again) "fastboot -i 0x1949 flash recovery twrp.img" and finally "fastboot -i 0x1949 oem recovery"
Edit: This is a more complex version of Hashcode's method, posted on the cm11 installation instructions page.
Sent from my Nexus 7 using Tapatalk
Yea but the thing about that method is sometimes people have bad downloads and don't check for md5sums(not to mention tons of people always having driver issues). If everything is in a signed zip file then if the signature verification fails its about the same as a bad md5sum, not to mention I can add a md5sum comparison in the update-tools script. I was just wanting to make a one click bootloader install option that comes from an apk, kinda like fire flash but simpler.
Sent from my Amazon Tate using Tapatalk
So you're suggesting using an OpenRecoveryScript to flash twrp, the old bootloader, and apply the stack override file to allow for that "2nd boot loader" hack?
Theoretically, that should work, but Amazon might have put restrictions on the recovery to only allow Amazon-signed zip files so that something like this couldn't happen.
Sent from my Nexus 7 using Tapatalk
I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk
stunts513 said:
I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
If TWRP is required, doesn't that make this pointless, because you need the 2nd bootloader hack to make twrp work in the first place? Or perhaps I'm just misunderstanding...
EDIT: when I have the time, I'll see if I can manage to recover from my weird semi-brick and if so, I'll revert to stock and help you test.
Sent from my Nexus 7 using Tapatalk
Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.
stunts513 said:
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.
Click to expand...
Click to collapse
Kindle's back up and running, I'll test it.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ok I'll upload it tomorrow. I was just checking my notifications. On a side note I left my kindle in the car and woke and woke up and realized it, having to use my phone to check messages because I will cause a domino reaction if I open the front door... it starts with dogs waking up...
Sent from my LG-P769 using Tapatalk
Sorry I haven't uploaded it yet, i will upload it when I have a chance, my weekend has been chaotic because I've been having to prepare for the job I am starting training for tomorrow. I have been meaning to do it but I hit another snag when I finally got some time to myself I told Ubuntu to upgrade to 14.04 and then unity surprised me and now apparently can't set the window buttons to right so I feel like i'm using a mac which I do not like at all so I decided to use mate since its pretty much what mynfavorite Ubuntu distribution had 10.04lts) so I have been spending the better part of the day reconfiguring it so it was more so like Ubuntu 10.04's theme but I modernized it a bit. Still not done with the theme yet but it is much much better. I think I'm going to attempt to add transparency to the theme. Just realized how off topic i went. Anyways I will see about uploading it tomorrow after I get off of work.
Sent from my Amazon Tate using Tapatalk