Just rerooted after 6.3 with the Kindle Fire Utility v0.9.5

[Hope]

It wasn't too bad. I had to run through the steps to get the Android Market back which was a pain.

Anybody else use the FireFireFire method to get rooted after the 6.3 update?

Here's the link to the new Kindle Fire Utility which works with 6.3:

http://forum.xda-developers.com/show....php?t=1399889

[beej231]

Originally Posted by Hope

It wasn't too bad. I had to run through the steps to get the Android Market back which was a pain.

Anybody else use the FireFireFire method to get rooted after the 6.3 update?

Here's the link to the new Kindle Fire Utility which works with 6.3:

http://forum.xda-developers.com/show....php?t=1399889

I decided not to root again.

[beej231]

Originally Posted by Hope

It wasn't too bad. I had to run through the steps to get the Android Market back which was a pain.

Anybody else use the FireFireFire method to get rooted after the 6.3 update?

Here's the link to the new Kindle Fire Utility which works with 6.3:

http://forum.xda-developers.com/show....php?t=1399889

I have a question. Say you were rooted then unrooted and went back to stock, then something general goes wrong and you had e send it in to Amazon. Will they be able to tell it was previously rooted or will they be unable to tell and honor the warranty?

[diba]

My Android Market survived update to 6.3 as well as the rooting process. But I know some KF owners, who lost apps, others the market as well. Seems every KF behaves in some other way ...

[Jessica Lares]

Originally Posted by beej231

I decided not to root again.

Aww, don't give up!

Oh and... If the app is not compatible, it'll remove itself when you apply a new update because the /system/build.prop would have been overwritten.

[beej231]

Originally Posted by Jessica Lares

Aww, don't give up!

Oh and... If the app is not compatible, it'll remove itself when you apply a new update because the /system/build.prop would have been overwritten.

I decided it just didn't do enough for me to bother. I don't need the android market as badly as I thought and there really wasn't any other reason for me to do it.

[Pushka]

My fire stayed rooted after the update.

[diba]

Originally Posted by Pushka

My fire stayed rooted after the update.

Sorry, just can't believe, would be the first behaving like this. They even implemented a file checking the root-status at each boot.

[Hope]

Originally Posted by Pushka

My fire stayed rooted after the update.

Any idea why?

[Ramer84015]

Originally Posted by Hope

Any idea why?

For me, I installed the unsecured rooted 6.3 rom from xda forums before the update was pushed to me, and it never got pushed to me, so I stayed rooted.

[beej231]

Originally Posted by Hope

Any idea why?

I'm wondering if dida only got a partial install or something.

[jduck]

Originally Posted by beej231

I have a question. Say you were rooted then unrooted and went back to stock, then something general goes wrong and you had e send it in to Amazon. Will they be able to tell it was previously rooted or will they be unable to tell and honor the warranty?

I'm pretty sure they won't even bother to check. Once they have it in their hands, it's more cost-effective for them to swap out the device with a refurb, then do some sort of certification process on the returns to validate the hardware is ok and re-flash from scratch. No point in doing ANY software troubleshooting when they can start anew in a couple minutes.

[jduck]

So at this point I'm still apparently successfully blocking the 6.3 update.

I'm hoping to not have to re-root from scratch after I bite the bullet and manually do the update. My plan is to stuff /system/xbin/su someplace that will preserve the permissions and not get blown away by the update. Then after the update I can merely run my preserved su to become root and put su back in /system/xbin (and remove the new root check). I can reinstall the superuser apk if needed, but I don't think it'll go anywhere. I THINK that will keep me "rooted". At the very least it will preserve what I need to put the GoogleCalendarSyncAdapter.apk back in place so my google calendar will work.

My Market survived 2 or 3 previous software updates. Not sure what the differentiating factor is there - maybe it depends on what apk you started out with and whether it had been updated in the past.

[Anabran]

Hi I am not, nor will I ever be, Rooted.

But strangely I turned on my Wifi in a very strong free public Wifi area in a local mall on sunday to "update" an Amazon app that inexplicably began demanding an internet connection to run ( Autodesk Sketch book mobile paid version)

Anyway I made the "Sketch book mobile" App happy to have "called home to mommy" I guess as it now runs fine with the wi fi off.

However I hit the synch to cloud button several times and got notices about updates to a few other apps from AMZN
But my system software still sits at 6.2 and the update button next to it it stays greyed out( inactive)

I know I can go to the amzn website and get the
250+megabyte "bin" file and manually update via USB side load but I dont plan to bother as I have zero need for the "enhancements" offered this time around any way.

Cheers

[dengar]

Well...I gave up and loaded the Cyanogen rom on my Fire. No more Amazon update, no more worries