Develop Bugs

[request] Any method to re-rooting after update 6.2.1? (latest update link included)

here is the amazon latest update 6.2.1
https://t.co/BRUE4vHR
Any expert wants to help out those have updated their kindle fire to 6.2.1?

My coworker bought a Kindle Fire for his mother and want's me to prepare it for her as a Christmas gift (she wants Android so we decided to install the Android Market). I took it home the other day and noticed a message saying that it was updating itself. The system version says "6.2_user_3003020"
Is this 6.2.1? It's doesn't say 6.2.0, so I don't want to make any assumptions.

have u tried zergrush from this post? not sure if its the same exploit or not, but try it
http://forum.xda-developers.com/showthread.php?p=20288923
sent from my kindle fire

CZroe said:
My coworker bought a Kindle Fire for his mother and want's me to prepare it for her as a Christmas gift (she wants Android so we decided to install the Android Market). I took it home the other day and noticed a message saying that it was updating itself. The system version says "6.2_user_3003020"
Is this 6.2.1? It's doesn't say 6.2.0, so I don't want to make any assumptions.
Click to expand...
Click to collapse
That is version 6.2
You need to make sure that WiFi is OFF until you protect it from getting further updates. There are a number of theads on how to do that.
o Modified hosts file to block: 127.0.0.1 s3.amazonaws.com
o Installed TWRP 2.0, FIREFIREFIRE and u-boot (was done via a package)
o Renamed /system/app/OTASilentInstall.apk to /system/app/OTASilentInstall.apk.bak
Any of which will prevent further updates. You needed to be rooted to do any of these however. One method that people are using is:
http://forum.xda-developers.com/showthread.php?t=1399889

Still, an exploit needs to be found for stock KF that will be coming with 2.6.1 and higher. I'm pretty sure we are going to be able to download and patch future stock Roms for those that don't want to go to cm7 or cm9 when it is ready.

And for people like me who had root, and got the silent update, not thinking I would lose root!

ATM, my guess is that a factory cable is required to put it into fastboot to restore root.

Yes, I would think Vashypooh is right. If you can get fastboot access, one could possibly gainroot, or maybe flash an already rooted Rom.

Have anybody tried to remove the OTASilenInstaller.apk from the system/app?

Aw damnit, it just updated on me. So I can't reroot using the old methods?

kweng_ca said:
Aw damnit, it just updated on me. So I can't reroot using the old methods?
Click to expand...
Click to collapse
No, nothing works at this point, until someone figures out a new way to gain root. No telling how long that could take. I'll say one thing, I'm putting CM7 on mine as soon as I get it rerooted. I don't like having a surprise lockdown on my device.

kweng_ca said:
Aw damnit, it just updated on me. So I can't reroot using the old methods?
Click to expand...
Click to collapse
Had you bychance renamed the OTA file or redirected a3.amazonaws.com?
Sent from my Kindle Fire using xda premium

Ectoplasmic said:
No, nothing works at this point, until someone figures out a new way to gain root. No telling how long that could take. I'll say one thing, I'm putting CM7 on mine as soon as I get it rerooted. I don't like having a surprise lockdown on my device.
Click to expand...
Click to collapse
this is why i did this yesterday!
sent from my kindle fire

borborpa said:
Had you bychance renamed the OTA file or redirected a3.amazonaws.com?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
No sir, guess it's just a waiting game for me now

borborpa said:
Had you bychance renamed the OTA file or redirected a3.amazonaws.com?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I
I had the sneakyOTA.apk (or whatever it was called) UNINSTALLED!!! and still got updated to 6.2.1 Monday night. Many of those self-righteous folks who are sayin' 'ah, but I froze/renamed the .apk' will soon have a fancy e-reader. Just watch!

kweng_ca said:
No sir, guess it's just a waiting game for me now
Click to expand...
Click to collapse
I have faith in the brilliance of xda community members ... the rooting method will be available tomorrow

I had the same thing happened to me. Apparently renaming or freezing ota is not enough
Sent from my Kindle Fire using Tapatalk

charmainelooi said:
I have faith in the brilliance of xda community members The rooting method will be available tomorrow.
Click to expand...
Click to collapse
I agree with that 100%

charmainelooi said:
I have faith in the brilliance of xda community members ... the rooting method will be available tomorrow
Click to expand...
Click to collapse
Is it done yet? Why is it taking so long?

I bought two KFs for my kids, rooted, adw, happened, twrm. Froze otainstall.apk and one updated.
At least market still works and adw is still default.
Bummer is that I helplessly watched twrm flash the update.
Sent from my SCH-I510 using Tapatalk

[root] KF2 has updated to 10.2.3 - there goes root and gapps [edit: rooted again!]

So, all my work to get mine set up is undone, play store is gone, ads are back, etc..the voodoo root protector app failed completely.
Worse, the qemu exploits are not working.
On the plus side, Swype was recoverable with the nook advanced settings tool..
I eagerly await the next method.
Edit: And we're back, Baby! I had success getting root back via the MANY ANDROID method mentioned by bodi524 below..I had to run it twice, but then it was all good. Didn't even have to rerun the qemu bits!

Same story. I hope that someone can find solution. This device is useless without root

Did the device auto update or you updated hoping for the best? I was reading up that they are going to release an update any day now that will break it pulling the stuff that allows us to exploit root. Mine still has not come in the mail yet. I'm expecting it will be here by Wednesday of next week soo long. I'll give it till then for something to be done or it will be shipped back.

I noticed mine auto-updated last night. I looked over and saw "Kindle is upgrading..." on the screen.

Jirv311 said:
I noticed mine auto-updated last night. I looked over and saw "Kindle is upgrading..." on the screen.
Click to expand...
Click to collapse
anyone try Voodoo OTA Rootkeeper yet? I just installed on my yet to be updated KF2

esatchel said:
anyone try Voodoo OTA Rootkeeper yet? I just installed on my yet to be updated KF2
Click to expand...
Click to collapse
That app does not work. No app that is out there works. You have to change a system app that controls that function. Don't know what it is off hand bud the is a thread in q&a or general that discusses it

Try this method to root 10.2.3
It worked for me.
http://forum.xda-developers.com/showthread.php?p=35156970
Sent from my Galaxy Nexus using xda app-developers app

bodi524 said:
Try this method to root 10.2.3
It worked for me.
http://forum.xda-developers.com/showthread.php?p=35156970
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This Root Method works for the 10.2.3 Update.
This was my 1st try after failing the qemu root

Hey there!
I've tried the different Methods to gain root acces aganin after the Update to Version 10.2.3 but without success.
The Problem (while using qemu-method) is the step with build.prop -> "Permission denied".
Ca anybody give a hint how to gain root access again?
Also ca anybody give me a hint, if the original Kindle fire ROMS would work on kindle fire v2?
Im new to Kindle fire, only worked with different HTC-Phones till now, so maybe there is some help? =)
Thanks in advance!

Check post above yours for root. I had to use both methods in that thread. Do not be afraid if the phone is hanging after the first method, the second method brings it through.
Sent from my KFOT

help root
What page number is it on there's a lot going on there please help....i really want to root this device and put google apps store on it ....thanks
wildgunman said:
This Root Method works for the 10.2.3 Update.
This was my 1st try after failing the qemu root
Click to expand...
Click to collapse

root
I clicked on the link and it took me to Sony Xperia S, Acro S, Ion > Xperia S Android Development > Root MANY ANDROID! [Upd: 22.11.2012]
im not sure what to do..please help..what steps do i take i dont want to brick the device..thanks in advance
bodi524 said:
Try this method to root 10.2.3
It worked for me.
http://forum.xda-developers.com/showthread.php?p=35156970
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse

with your help i've managed to root on 10.2.3
is there a way to stop the kindle from auto updating?
because without gplay store i can't use it (german kindle in austria-> amazon appstore won't "buy" things)

bodi524 said:
Try this method to root 10.2.3
It worked for me.
http://forum.xda-developers.com/showthread.php?p=35156970
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So this is basically the replacement for the KFC atm?

Uh oh. 10.2.4 just hit my kindle. I'm going to try to re-root, but it even nailed OTA rootkeeper. Amazon keeps getting smarter. I kinda wish they would just let us enjoy our awesome 7" tablet with gorgeous ips display and leave it alone.
It's bad enough there's no KFU or FFF for the Fire 2 so we're stuck on rooted stock instead of being able to install ICS proper, or jellybean.
Sent from my KFOT using xda app-developers app

Just hit mine too, laptops playing up so going to try again tomorrow, let me know how you get on please agent.

Rix said:
Just hit mine too, laptops playing up so going to try again tomorrow, let me know how you get on please agent.
Click to expand...
Click to collapse
It worked. It took a couple tries, but it worked. Now it's kinda weird though, rather than saying "<app> has been granted root permission" it says now "<app> has been granted root permission for an interactive shell", but it still works.

agentfusion said:
It worked. It took a couple tries, but it worked. Now it's kinda weird though, rather than saying "<app> has been granted root permission" it says now "<app> has been granted root permission for an interactive shell", but it still works.
Click to expand...
Click to collapse
Thanks agentfusion. Can you mention which technique you used to get it rooted again?

agentfusion said:
It worked. It took a couple tries, but it worked. Now it's kinda weird though, rather than saying "<app> has been granted root permission" it says now "<app> has been granted root permission for an interactive shell", but it still works.
Click to expand...
Click to collapse
How did you get root on 10.24.
---------- Post added at 02:48 PM ---------- Previous post was at 02:23 PM ----------
jutley said:
How did you get root on 10.24.
Click to expand...
Click to collapse
Ok just rerunf both exploits in order it will work eventually now rooted on 10.24 now to delete that ota.certs

bodi524 said:
Try this method to root 10.2.3
It worked for me.
http://forum.xda-developers.com/showthread.php?p=35156970
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This worked for 10.2.4 also,.
---------- Post added at 09:31 PM ---------- Previous post was at 09:26 PM ----------
jutley said:
How did you get root on 10.24.
---------- Post added at 02:48 PM ---------- Previous post was at 02:23 PM ----------
Ok just rerunf both exploits in order it will work eventually now rooted on 10.24 now to delete that ota.certs
Click to expand...
Click to collapse
I'm on that hunt myself. I've installed Droidwall until I find it, but I'd rather just disable the updates.

KFHD 8.3.0 update broke root! Now what?

I turned on my kids KFHD today and saw a lock screen ad, which I had eliminated when I rooted the device. I went to titanium backup and, sure enough, no root anymore. Voodoo didnt keep it. I used a method on XDA to root in the first place but IDK if it will still work on 8.3.0 (doubt it) and I dont feel like doing a data wipe right now to find out. Does anyone know to regain root on this version? Its only a few hours old and I havent seen anything about it yet.

ecopunk said:
I turned on my kids KFHD today and saw a lock screen ad, which I had eliminated when I rooted the device. I went to titanium backup and, sure enough, no root anymore. Voodoo didnt keep it. I used a method on XDA to root in the first place but IDK if it will still work on 8.3.0 (doubt it) and I dont feel like doing a data wipe right now to find out. Does anyone know to regain root on this version? Its only a few hours old and I havent seen anything about it yet.
Click to expand...
Click to collapse
I was able to get it re-rooted, but it took two tries before it finally worked.

You can reflash 8.1.4, and then run Chris/Prokennexusa's OTA-Update-Defeat script to kill the update services. My 8.9 survived Amazon's OTA update and remained on 8.1.4, rooted, with Hashcode's bootloader intact. Chris's defeat script works!
Hashcode reviewed the update the and major change was to plug the security hole that allows us to use an alternate bootloader and flash new operating systems.

Nestaron said:
I was able to get it re-rooted, but it took two tries before it finally worked.
Click to expand...
Click to collapse
Using what method? Same as 8.1.4 or something else?
Slimepuppy said:
You can reflash 8.1.4, and then run Chris/Prokennexusa's OTA-Update-Defeat script to kill the update services. My 8.9 survived Amazon's OTA update and remained on 8.1.4, rooted, with Hashcode's bootloader intact. Chris's defeat script works!
Hashcode reviewed the update the and major change was to plug the security hole that allows us to use an alternate bootloader and flash new operating systems.
Click to expand...
Click to collapse
Thanks, might have to do that.

I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.

Just saw this. I didn't check the version on mine until now. It's on 8.3, and has been rooted since I brought it home on Wednesday. I did it Wednesday night and if it updates overnight it kept root.
If not, it was on 8.3 the whole time.

gunnyman said:
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Click to expand...
Click to collapse
gsu_golfer said:
Just saw this. I didn't check the version on mine until now. It's on 8.3, and has been rooted since I brought it home on Wednesday. I did it Wednesday night and if it updates overnight it kept root.
If not, it was on 8.3 the whole time.
Click to expand...
Click to collapse
Thank you all! I will backup and go again tomorrow or the next dayand post the results

gunnyman said:
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Click to expand...
Click to collapse
+1 same here

bighead2k said:
+1 same here
Click to expand...
Click to collapse
Mine has not worked - I am using bin4ry tool v26. What did you use?

gooseacre said:
Mine has not worked - I am using bin4ry tool v26. What did you use?
Click to expand...
Click to collapse
I used bin4ry tool v25, It wasn't rooted, but I can install playstore, go laucher!

Went out of town and forgot to post back here. I did re-root with the original method and it DID work! I backed it up but I was surprised to find that all my data, apps, even passwords, etc were all still there after re-rooting (even after the supposed data restore) and were all working but I had regained root! The only thing missing were the kindle Books selections. Not a bad tradeoff!

gooseacre said:
Mine has not worked - I am using bin4ry tool v26. What did you use?
Click to expand...
Click to collapse
haovpi said:
I used bin4ry tool v25, It wasn't rooted, but I can install playstore, go laucher!
Click to expand...
Click to collapse
This is what I used on both firmware versions
http://forum.xda-developers.com/showthread.php?t=1886460

no such thing as a root keeper
Not f'realz anyways. I'm on 8.3.1; gotten used to rooting the same way, THAT is nice. I initially had to fiddle w/ADB, windows 8 doesn't initially allow unsigned drivers. There's a proceedure for that. After that was fixed, the b1nary root works like a boss ...
The kindle fire first aid works well for market installation (make sure to install busy box first, b1nary root didn't, and that's easy). OTA blocking works well, I forget what I used. My update to 8.3.1 was intentional
Seems a more stable update. In fact, all the updates seem worth-while: google maps didn't gps track w/1st version, with silk installed couldn't watch amazon vod. A lot of quirks seem to be fixed, google play store and amazon app store seem to be playing well together.
---------- Post added at 08:57 AM ---------- Previous post was at 08:47 AM ----------
ecopunk said:
Went out of town and forgot to post back here. I did re-root with the original method and it DID work! I backed it up but I was surprised to find that all my data, apps, even passwords, etc were all still there after re-rooting (even after the supposed data restore) and were all working but I had regained root! The only thing missing were the kindle Books selections. Not a bad tradeoff!
Click to expand...
Click to collapse
Hey, fyi when you reroot, go into app settings after and clear data on the Amazon apps like Kindle, Silk, or VOD. My stuff doesn't show up even on the "cloud" if I don't do that. You'll have to redownload media, so that might stink. Not really, imo.

after super me,box bricked

my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:

I do not want to give you a hard time but why you guys do not read before doing it. There are few post here mentioning that boxes get bricked if you use supersu-me. Can you connect to it through adb? The only way to get it back if somehow rbox will release an unbrick image as he did for firetv 2

sardiswolf said:
my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:
Click to expand...
Click to collapse
Same thing happened to me with fire stick but not stuck on amazon logo but fire TV stick logo.
Sent from my iPhone using Tapatalk

READ ME!
If you read the Kingroot thread on this forum, located here. You will find that the authors of Kingroot have taken exception to the author of SuperSu and anyone else who uses it in their programs to replace Kinguser, because of the claims of conflicting programs and/or malicious coding. Kingroot authors counter claim that programs like Super-Sume improperly remove Kingroot leaving orphaned files which may cause problems. But the author of Super-Sume says his program will not brick your device.
Most people have had no luck installing SuperSu on their devices after being rooted by Kingroot even though Kingroot authors claim they could co-exist on the same device, because Kingroot has added a restriction regarding SuperSu. So consequently those who have gotten SuperSu installed on their Kingroot rooted devices have ended up with problems.

Don't install random stuff via root without custom recovery! Its just as effective as a pull and pray people. You need some protection.
Just be patient!!

hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.

sardiswolf said:
hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.
Click to expand...
Click to collapse
There's really nothing you can do if you have a locked firetv1 box that is bricked.

rbox said:
There's really nothing you can do if you have a locked firetv1 box that is bricked.
Click to expand...
Click to collapse
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.

sardiswolf said:
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.
Click to expand...
Click to collapse
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.

rbox said:
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.
Click to expand...
Click to collapse
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.

sardiswolf said:
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.
Click to expand...
Click to collapse
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.

rbox said:
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.
Click to expand...
Click to collapse
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks

sardiswolf said:
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks
Click to expand...
Click to collapse
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.

rbox said:
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.
Click to expand...
Click to collapse
Thanks, I will wait for your rom and use aftvnew post the unbrick way to do factory reset.

looks like the usb keyboard could not make it get into factory reset area.

Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?

mrchrister said:
Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?
Click to expand...
Click to collapse
no way to solve it. bought another brand tv box.

I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk

mrchrister said:
I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk
Click to expand...
Click to collapse
If your bootloader isn't already unlocked and you bricked a FireTV 1, there isn't anything that can be done from a software perspective.

i was hoping to dd system.img through hardware emmc soldering. do you think this could work to revive it?
Sent from my iPhone using Tapatalk

Kingroot Won't Root - Kingo says root but no root

BY mistake I made a thread in general note4 section.
http://forum.xda-developers.com/note-4/help/kingroot-fails-kingo-rooted-root-t3501476
Anyone willing to help out?
EDIT: was able to root once but then everytime it just reboots the phone - at first cause was I didn't accept the "installation of the application" battery is low so maybe that could be the the reason..

patt2k said:
BY mistake I made a thread in general note4 section.
http://forum.xda-developers.com/note-4/help/kingroot-fails-kingo-rooted-root-t3501476
Anyone willing to help out?
EDIT: was able to root once but then everytime it just reboots the phone - at first cause was I didn't accept the "installation of the application" battery is low so maybe that could be the the reason..
Click to expand...
Click to collapse
I had the same problem a few hours ago. Kingo Root refused to work at all, so I had to use the Kingroot app. It made my phone lag like crazy after it rooted it, but it eventually worked. When you use either Kingo Root or Kingroot, what's the exact error that you get? Are you using Root Checker to see if you achieved root?

I always did a factory reset before starting the root process, it just seemed to make things go smoother. At least it would stay stable long enough to get all the adb stuff done. (Barely though )

quinciebee said:
I had the same problem a few hours ago. Kingo Root refused to work at all, so I had to use the Kingroot app. It made my phone lag like crazy after it rooted it, but it eventually worked. When you use either Kingo Root or Kingroot, what's the exact error that you get? Are you using Root Checker to see if you achieved root?
Click to expand...
Click to collapse
I was able to root once and run the script and it changed the CID or whatever it was. Now I simply cannot get temp root at all to finish the bootloader unlock process. Tried PC version and Android version so many times now it just reboots and reboots.
kevintm78 said:
I always did a factory reset before starting the root process, it just seemed to make things go smoother. At least it would stay stable long enough to get all the adb stuff done. (Barely though )
Click to expand...
Click to collapse
did a factory reset actually :/

patt2k said:
I was able to root once and run the script and it changed the CID or whatever it was. Now I simply cannot get temp root at all to finish the bootloader unlock process. Tried PC version and Android version so many times now it just reboots and reboots.
did a factory reset actually :/
Click to expand...
Click to collapse
That sucks, to be honest it's been awhile since I did the unlock process. Maybe something changed with the way that app roots. Have you already tried an older version of kingroot? I know you've probably tried all this stuff but sometimes things get overlooked.

kevintm78 said:
That sucks, to be honest it's been awhile since I did the unlock process. Maybe something changed with the way that app roots. Have you already tried an older version of kingroot? I know you've probably tried all this stuff but sometimes things get overlooked.
Click to expand...
Click to collapse
Rooted once with the newest one and it didn't reset even once. But then it just resets everytime. I did another factory reset so we shall see. I'll keep on trying.
Sent from my iPhone using Tapatalk

quinciebee said:
I had the same problem a few hours ago. Kingo Root refused to work at all, so I had to use the Kingroot app. It made my phone lag like crazy after it rooted it, but it eventually worked. When you use either Kingo Root or Kingroot, what's the exact error that you get? Are you using Root Checker to see if you achieved root?
Click to expand...
Click to collapse
It worked once for me was able to use the unlock script but it was the part #1 of the process, so far I am unable to root again to fully unlock it. Been trying since yesterday the phone reboots when trying to root.

kevintm78 said:
That sucks, to be honest it's been awhile since I did the unlock process. Maybe something changed with the way that app roots. Have you already tried an older version of kingroot? I know you've probably tried all this stuff but sometimes things get overlooked.
Click to expand...
Click to collapse
Good news! Kingroot 5.0 worked on second try. Status: Developer

patt2k said:
Good news! Kingroot 5.0 worked on second try. Status: Developer
Click to expand...
Click to collapse
That's great! Did you have to do anything different or did kingroot just finally work long enough to get the job done?

kevintm78 said:
That's great! Did you have to do anything different or did kingroot just finally work long enough to get the job done?
Click to expand...
Click to collapse
The kingroot 5.0 worked on second try.. so no idea why the older ones didn't work.
Would you happen to know which rom supports more languages other then default ones? shipping this phone to Europe tomorrow, don't know how stable CM roms are.