Database Users

[Q] Help rooting -- device offline after rageagainstthecage

I'm following instructions given by karnovaran "How to root the Droid 2"
I have a Droid 2 running 2.2 OS, latest SDK, latest Moto drivers. I'm new to Droid 2 but not to windows or linux. After running the instructions rageagainstthecage, waiting to be kicked out, and then issuing "adb kill-server". The following command "adb devices" lists my device as "offline" and not surprising "adb shell" give me the "error: device offline".
The similar threads didn't seem to help. Does anyone have an idea?

Just use z4root. It's no longer on the market but you can download it from its official thread. The Droid 2 works beautifully with it.

Thank You for the quick reply. I will take a look and see if a z4root is a better route to take. I will also watch for other replies. I am as curious as to way rageagainstthecage is not working as I am to complete the rooting process. Has Verison block this application? I'm even more curoius to know why providing something as simple as superuser to a linux OS is so shrouded in voodoo. It may just be something simple I missed but the device goes offline on the phone side and I can not reconnect until it is rebooted.

Well, rageagainstthecage is an exploit that tricks the adb daemon on the phone into running as root instead of setuid'ing to a non-root user. Once that's accomplished you can do pretty much anything through adb such as installing system level packages and changing some system configuration files. Basically all the existing root methods for the Droid 2 use rageagainstthecage to obtain root and then fix the system to allow any user to su to root.
Verizon can't block the exploit because the bug is in the adb daemon which a vendor really shouldn't touch. As for why it might not be working on your phone, rageagainstthecage really relies on what is called a race condition. The exploit has to kill the adb daemon and fork off another process before the adb daemon is restarted. Sometimes it fails to do so.
Really z4root has made most previous methods obsolete. It does the hard work for you.

Thank you for that very fine explaination. I guess I will proceed to z4root now.

Just a last followup.
Z4root worked prefect! I'm rooted, got the SDK connected to Netbeans and the latest moto drivers. Let the games begin.
Thank you again Spitemare

Hi there, I got a similar problem. I downloaded z4root as well but the thing simply quits halfway. No error message appears and the device remains unrooted. What else can I do?

elsenoire said:
Hi there, I got a similar problem. I downloaded z4root as well but the thing simply quits halfway. No error message appears and the device remains unrooted. What else can I do?
Click to expand...
Click to collapse
Try this
Reboot your device then try running the app again ....
It would quit half way on me too but a fresh reboot did the trick
Sent from my DROID2 using XDA Premium App

Kindle Fire lost root. Rooted with Burrito Root

Interesting issue I found today.
I have an Amazon Kindle Fire that I rooted using the Burrito Root method as described in the stickied thread above entitled: "Video guide to rooting etc..."
I followed the instructions as presented in the You Tube video, and achieved root.
I loaded the android market and downloaded the apps I had previously with no dramas. They all run fine.
Last night I downloaded Voodoo OTA Root Keeper as described in another thread.
I got to playing around with it today, and it said I did not have root access. Used the root checker utility as posted in the you tube video previously mentioned, and it too says no root. Attempted to use root explorer, and again no root. Power off and back on, same deal.
Weird to say the least. As far as I know, I have not had an update to the kindle firmware (current version: 6.2.1_user_3103920) which appears to be unchanged since I rooted. There were no issues when I rooted, and all functioned as it should have (rooted I mean)
The only thing I did do in the previous week was download an amazon movie to the device.
Any ideas on WTF happened?
I had been considering installing TWRP...now I am wondering if I should re-root using the same method, or uninstall the stuff I put on in the originl root, and just load TWRP, and do it that way?
Thanks for any input.

Burrito Root gives you root through ADB. In order to get permanent root that's usable by applications such as Root Explorer you need to push the su binary and install the superuser.apk. Not sure if that was covered in whatever video you watched, but there should be instructions and download links kicking around here and rootzwiki somewhere.

Easiest way is to use this http://forum.xda-developers.com/showthread.php?t=1399889 and use option 2 then 3. should be good to go after that.

skourg3 said:
Burrito Root gives you root through ADB. In order to get permanent root that's usable by applications such as Root Explorer you need to push the su binary and install the superuser.apk. Not sure if that was covered in whatever video you watched, but there should be instructions and download links kicking around here and rootzwiki somewhere.
Click to expand...
Click to collapse
For clarification, as I failed to mention it in my original post.
Superuser.apk was installed, as were all commands done through ADB as prescribed...it appeared to have worked flawlessly. Until now. LOL
I am new to the fire, not new to android.
It is rather puzzling, as I have never experienced this type of issue before.

Re use ota root keeper and restore your root
Sent from my Kindle Fire using xda premium

silvertrd said:
For clarification, as I failed to mention it in my original post.
Superuser.apk was installed, as were all commands done through ADB as prescribed...it appeared to have worked flawlessly. Until now. LOL
I am new to the fire, not new to android.
It is rather puzzling, as I have never experienced this type of issue before.
Click to expand...
Click to collapse
Superuser.apk and the su binary are separate things. These are the original instructions. Not sure what the video you watched suggests.
The su binary goes into /system/xbin and you need to:
Code:
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
When Superuser.apk is installed it gets put into /data/app. If you've only done one, but not the other, that's most likely causing your issue.
*Edit* In your original post you mentioned messing around with OTA Rootkeeper. There's a checkbox that backs up the su binary. Maybe it was unchecked when you temporarily unrooted? There's also a button that deletes the su binary backup. Very possible one of these led to your issue.

phunky123 said:
Easiest way is to use this http://forum.xda-developers.com/showthread.php?t=1399889 and use option 2 then 3. should be good to go after that.
Click to expand...
Click to collapse
I had looked at that. My question doing it using that method:
Do I need to uninstall/delete anything from my previous root? or will that program overwrite superuser, etc?
ghost_og:
The video I watched was the same video you link to.
I copied and pasted all of the commands into the adb shell as nat3mil describes.
I wonder where I went wrong? Weird.
Can I just connect the kindle to my computer, run burrito root, and then re-push the commands via adb as described ? I just don't wanna bork it up and brick it.

Veritass said:
Re use ota root keeper and restore your root
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Great idea! Just now tried that after seeing your suggestion. No joy. FML.

silvertrd said:
Can I just connect the kindle to my computer, run burrito root, and then re-push the commands via adb as described ? I just don't wanna bork it up and brick it.
Click to expand...
Click to collapse
It should be fine. I remember having to run it twice and I never went through and deleted anything. Here's something interesting: I checked both /system/bin and /system/xbin when I was rooted and unrooted. Even though I originally installed su to /system/xbin, OTA Rootkeeper places it into /system/bin upon restoring root.
I'm not saying you should do that, but just thought I'd bring it up. Maybe that has to do with why you lost root privelages out of the blue.
Also, I know certain Superuser.apk's were not working properly. The one included in the zip file at Androidpolice is actually com.noshufou.android.su-1.apk. Perhaps try using that one instead?
*Edit2* I just looked at the official thread and noticed he updated the zip and it now uses Superuser.apk. Not sure if Androidpolice ever updated their zip as well.

ghost_og:
Thanks!
I will give it a shot, and report back later this evening.
Regards,
SilverTRD

install busybox from the market and try again

KFU will tell you if it is rooted or not. just connect KF to your pc and run no harm going that far.

I am in the same situation as you are, same steps. Rooted with BR, but didn't root all the way, yet was still able to put the market apps.

My kindle Fire (non-HD) just "lost" root too!!!
No idea how it happened.
I successfully rooted last summer with the KFU and have temp un-rooted/re-rooted MANY times with OTA Rootkeeper . I went in yesterday to root, but the buttons were gone in Rootkeeper and it shows that I'm NOT rooted.
I tried to update/reinstall Superuser but I probably just made things worse.
Is there any way for me to get root back without losing all of my data??
If not, I suspect that I have to go back to KFU and do the root process again, but will this brick my Kindle???
Thanks all!

If you used KFU the first time it should work again as long as you can get good communication and the driver is still installed correctly. Do you still have twrp and fff? if so just flash modaco if you`re on stock no wipes needed and you will never have to worry about loosing root again http://forum.xda-developers.com/showthread.php?t=1439916

Thepooch said:
If you used KFU the first time it should work again as long as you can get good communication and the driver is still installed correctly. Do you still have twrp and fff? if so just flash modaco if you`re on stock no wipes needed and you will never have to worry about loosing root again http://forum.xda-developers.com/showthread.php?t=1439916
Click to expand...
Click to collapse
Thanks Thepooch! I'm at work now, so I'll have to wait until I get home to my laptop to try.
I had no problems with the driver or communication, so that "shouldn't" be an issue.
The root process with KFU actually went painfully smoothly when I did it over the summer so hopefully second time will be the same.
I still have twrp and fff, but I'm not sure what you mean by "just flash modaco if you`re on stock", but I'll come back if i brick.
While losing my data would suck, I won't lose much sleep if I have to wipe it.

Thanks again Thepooch.
Took less than 5 minutes to get the root back with KFU.

2nd kindle root attempt

when I rooted my first kindle hd, I started as if I were gonna do the manual root, making sure that I was able to read the device using windows command prompts, had some problems with the usb error and also the device manager error (which has already been covered here)
Once I got that straightened out I used the auto quemo root, and was able to root and do all the other cool stuff I wanted
Picked up a 2nd kindle hd for my mom, trying to root it and failing
I'm able to detect the device using command prompts and I can get it to show up in device manager as "android composite adb interface"
but when I do auto root, I get stuck on step 2 "cannot create/data/local.prop: permission denied"
I've tried rollingback and uninstalling then re-installing adb drivers, can't get it to work
any suggestions?
Is it because I'm trying to root a 2nd kindle on the same laptop? Do I need to delete any directory regarding adb or kindle and start from scratch?
I'm either gonna try deleting everything and starting from scratch or try the manual root, any help?

ksound said:
when I rooted my first kindle hd, I started as if I were gonna do the manual root, making sure that I was able to read the device using windows command prompts, had some problems with the usb error and also the device manager error (which has already been covered here)
Once I got that straightened out I used the auto quemo root, and was able to root and do all the other cool stuff I wanted
Picked up a 2nd kindle hd for my mom, trying to root it and failing
I'm able to detect the device using command prompts and I can get it to show up in device manager as "android composite adb interface"
but when I do auto root, I get stuck on step 2 "cannot create/data/local.prop: permission denied"
I've tried rollingback and uninstalling then re-installing adb drivers, can't get it to work
any suggestions?
Is it because I'm trying to root a 2nd kindle on the same laptop? Do I need to delete any directory regarding adb or kindle and start from scratch?
I'm either gonna try deleting everything and starting from scratch or try the manual root, any help?
Click to expand...
Click to collapse
i noticed today I recieved a system upgrade to 7.2.2 on my formerly rooted Kindle Fire HD, which removed root access. Running autoroot gives me exactly the same error as yourself. Looks like amazon has shut off that route?

wrexhamafc said:
i noticed today I recieved a system upgrade to 7.2.2 on my formerly rooted Kindle Fire HD, which removed root access. Running autoroot gives me exactly the same error as yourself. Looks like amazon has shut off that route?
Click to expand...
Click to collapse
yeah I had meant to mention that, my other one is running 7.2.1
gonna try resetting to factory defaults on the new one and see if I can root it that way
eta- nope restes to 7.2.2 and still no root

never mind I figured it out

Kingo Root, not kingroot, has Amazon devices listed in compatible devices.

I have been watching Kingo Root for awhile and I just noticed they added Amazon devices to their list of compatible devices. Its a PC root so you would need to attach the fire TV to your PC. I do not have a cord to do so, but its worth a try.
Also, I know windows notices the Fire TV, but not sure what driver is needed. If anyone has any details on an Amazon device driver for windows, please let us know.
If anyone tries Kingo Root, please report back.
Please do not talk about how to get Kingo Root to work if does not work, cause if it doesn't work it just doesn't work. Please no getting mad about anyone else's comments, cause everyone has a voice.
There is also Root Genius that roots a lot of devices, but I do not know if it has worked on any Amazon devices.

OK here's a quote from Amazon.com about installing the USB drivers for the Fire TV
"The USB driver for the Fire tablets also works with Fire TV."
So I guess all you have to do is install the Fire tablet driver.

porkenhimer said:
OK here's a quote from Amazon.com about installing the USB drivers for the Fire TV
"The USB driver for the Fire tablets also works with Fire TV."
So I guess all you have to do is install the Fire tablet driver.
Click to expand...
Click to collapse
Not sure I'm much help here. I have rooted aftvs and don't really want to mess with them. However, I did try it once with my aftv stick with no usb drivers installed.
At first it said to enable usb debugging (which pretty sure isn't an option on stick)
Then it recognized the device as aftm
It started checking root status and downloading scripts but it just repeated that loop for about 10 minutes.
I'm willing to try again later. In the mean time if anyone has a link for drivers please post. It'll save time hunting them down. I actually have them on my Mac.
But this does seem more likely to work on the box since you can enable usb debug there.

KLit75 said:
Not sure I'm much help here. I have rooted aftvs and don't really want to mess with them. However, I did try it once with my aftv stick with no usb drivers installed.
At first it said to enable usb debugging (which pretty sure isn't an option on stick)
Then it recognized the device as aftm
It started checking root status and downloading scripts but it just repeated that loop for about 10 minutes.
I'm willing to try again later. In the mean time if anyone has a link for drivers please post. It'll save time hunting them down. I actually have them on my Mac.
But this does seem more likely to work on the box since you can enable usb debug there.
Click to expand...
Click to collapse
Just google "Fire HD USB Driver". Download and install it. If your computer notices your device then USB debugging should be working or it wouldn't notice your devices.

Tried again same result except this time I put the stick back in the tv. It actually installed kingo root on it. So I launched it. There's nothing to click and it says usb not connected. So I plugged the usb into my computer. In the kingo app on tv it says "rooting..." but on the pc it just repeats the same loop as last time.
There's no fastboot on stick. The box would at least have a chance of working. I think that's why it can't reboot which it needs to do during the process.

KLit75 said:
Tried again same result except this time I put the stick back in the tv. It actually installed kingo root on it. So I launched it. There's nothing to click and it says usb not connected. So I plugged the usb into my computer. In the kingo app on tv it says "rooting..." but on the pc it just repeats the same loop as last time.
There's no fastboot on stick. The box would at least have a chance of working. I think that's why it can't reboot which it needs to do during the process.
Click to expand...
Click to collapse
Well we now know it doesn't work on the stick. Hopefully someone tries it on the Fire TV. I noticed with Kingroot, it would say that your device may need to reboot during rooting, but I also noticed a couple times, not every time though, Kingroot would say it couldn't reboot the device. So I am guessing maybe we stumbled upon something. Maybe part of the process for some devices Is a need to be rebooted during the root process. I have seen videos where some devices would actually reboot during Kingroot and be rooted after the reboot. Maybe a dev with more knowledge on why a device would need to reboot during the root process can give us some info. Maybe the problem with the Fire TV is that Kingroot and other apps like Kingo Root cannot reboot the Fire TV, but that just an idea. It does not sound likely, but anything is possible.

I have another idea that I am not sure anyone would be willing to try. Maybe someone can run Kingroot or Kingo Root on a rooted device and see what happens. It would have to be someone that has more than one Fire TV incase they messed their device up, but I am sure it could be easily fixed by flashing a pre rooted ROM. Maybe it could give us a better idea of what Kingroot is doing and what it might take to root, if it actually worked on a rooted device.

Maybe this will help with drivers etc
https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-over-usb
It says the stick can connect to adb via USB. Perhaps installing the correct drivers will help.

KLit75 said:
Tried again same result except this time I put the stick back in the tv. It actually installed kingo root on it. So I launched it. There's nothing to click and it says usb not connected. So I plugged the usb into my computer. In the kingo app on tv it says "rooting..." but on the pc it just repeats the same loop as last time.
There's no fastboot on stick. The box would at least have a chance of working. I think that's why it can't reboot which it needs to do during the process.
Click to expand...
Click to collapse
Back up the Kingo Root app and uplod the apk and I'll try installing it on the Fire TV box. If you don't know how to backup apps, you can do it with ES File Explorer. It says "app" under the library tab, click it and it will let you backup apps.

porkenhimer said:
Back up the Kingo Root app and uplod the apk and I'll try installing it on the Fire TV box. If you don't know how to backup apps, you can do it with ES File Explorer. It says "app" under the library tab, click it and it will let you backup apps.
Click to expand...
Click to collapse
Just got your post. This is really just the UI for your phone/tablet so you can see the progress and if it works it'll probably warn you not to disconnect the device. But here you go.

I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.

AFTVnews.com said:
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.
Click to expand...
Click to collapse
I guess its case closed for unrooted Fire TVs and Fire TV Sticks. I am still wondering what kingroot or Kingo Root would do on an already rooted device. I know it sounds kinda risky, but it may actually be able to commplete its process if the device is already rooted.

KLit75 said:
Just got your post. This is really just the UI for your phone/tablet so you can see the progress and if it works it'll probably warn you not to disconnect the device. But here you go.
Click to expand...
Click to collapse
Thanks. Didn't work for me either, but it was worth a try.

AFTVnews.com said:
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.
Click to expand...
Click to collapse
I had basically the same results except I let mine continue to run. It eventually said "root failed". Connected fine. One note: it did install the correct usb drivers for the Fire TV. I used version 1.3

porkenhimer said:
I guess its case closed for unrooted Fire TVs and Fire TV Sticks. I am still wondering what kingroot or Kingo Root would do on an already rooted device. I know it sounds kinda risky, but it may actually be able to commplete its process if the device is already rooted.
Click to expand...
Click to collapse
I'm not gonna have time for a little while. Both my aftvs get used a lot so I'm not willing to risk (even if its slight) losing one of them for an undetermined amount of time. If that changes and no one steps up I might reconsider. However, surely there are better eyes than mine when it comes to diagnosing what might be needed.
Here's a thought. You could email AFTVNews. He's got many aftvs, some of which he probably just uses for testing purposes. He'd also be a good resource since he has tons of experience with this device. Actually its possible he already tried this root method.
dk1keith said:
I had basically the same results except I let mine continue to run. It eventually said "root failed". Connected fine. One note: it did install the correct usb drivers for the Fire TV. I used version 1.3
Click to expand...
Click to collapse

KLit75 said:
Here's a thought. You could email AFTVNews. He's got many aftvs, some of which he probably just uses for testing purposes. He'd also be a good resource since he has tons of experience with this device. Actually its possible he already tried this root method.
Click to expand...
Click to collapse
AFTVNews is responding to this thread.
Verified it doesn't work. /thread

jpeg42 said:
AFTVNews is responding to this thread.
Verified it doesn't work. /thread
Click to expand...
Click to collapse
He may not have been paying attention to who was posting on the thread, but he was actually talking about asking him to run Kingroot or Kingo Root on an already rooted device, to see what haapens so that maybe we can figure out what they do during the root process. My thinking is that you can write to the system if you are already rooted so maybe Kingroot or Kingo Root can complete the process if the device you run it on is already rooted. Who knows, it may be hugely helpful towards achieving root if someone runs these apps on rooted devices and reports their findings, that is if it completes the process on the rooted device.

LOL! Yes it looks like he has indeed. And I'm looking pretty stupid. Am I imagining this or wasn't there a thread started by @porkenhimer last night? I must've somehow responded to a different thread thinking it was the one from last night. Anyway if he tried it on a rooted device and it doesn't bring about any new info then I guess this topic is dead.
Edit--oh I see. Aftvnews chimed in a few posts back. I was just responding to those who quoted me & didn't keep up with the thread.

AFTVnews.com said:
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.
Click to expand...
Click to collapse
I know doing a factory reset was tried on the Fire Stick but I didn't see where it was tried on the Fire TV (i may have just missed it) so I tried it. Did factory reset and tried Kingroot 4.0 and 4.1 with no success. Also tried the PC version of Kingroot and Kingoroot with no success. Just wanted to make sure I tried everything I could to get it to work before giving up on it. Only have one rooted Fire TV so I can't mess with that one.
Just wanted to pass on my results.

[How To] Downgrade to 4.5.3 so you can root device

Step by step instructional video
Help setting up adb for windows: https://www.youtube.com/watch?v=CyJlmTtLsIg
If you are already running Fire OS 4.5.3 and below, all you need to do is follow this video to root: https://youtu.be/KcQ30qcImJc
Steps:
1. Install the Fire OS 5.0 developer preview. EDIT: Do not do this. If you already have a lollypop ROM installed, use that instead of installing dev preview (You could cause a brick)
2. Enable ADB on your device and set up ADB on your computer
3. Download 4.5.3 firmware: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin (Mirror coming soon. This download works for the Fire HD7 and HD6)
4. connect device to computer and run "adb reboot recovery"
5. use volume keys and power button to navigate to "Apply update from ADB"
6. from computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
7. from tablet select "wipe data/factory reset"
8. from tablet select "reboot system"
9. Complete setup (do not connect to a wifi network yet)
10. Download KingRoot: http://www.kingroot.net/
11. Download JmzFireHDTool: http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
12. install both apps. "adb install KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk" and "adb install JmzFireHDTool_v4.apk"
13. Temporarily disable otaverify via adb "adb shell pm block com.amazon.otaverifier" (spelled wrong in video)
14. Connect to wifi so that KingRoot can work
15. Open KingRoot on your device
16. press "try to root"
17. re-enable otaverifier "adb shell pm unblock com.amazon.otaverifier" (spelled wrong in video)
18. Open JMZ Fire Tools and press "Disable OTA's"
Note: If you ever need to upgrade back to lollypop, you should follow these steps so you do not brick device: http://forum.xda-developers.com/fire-hd/general/tools-fire-hd-67-rooting-gapps-t3371242/page4

Awesome find !!! Here is a direct link to the 5.2.0 update file:
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
After the downgrade, install TWRP, and upgrade to 4.5.4 but this time with root and fully working GAPPS:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.

bibikalka said:
Awesome find !!! Now, can you install TWRP, and try to upgrade to 4.5.4 while keeping root as per this post:
http://forum.xda-developers.com/showpost.php?p=61329063&postcount=4
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.
Click to expand...
Click to collapse
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Click to expand...
Click to collapse
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.

bibikalka said:
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.
Click to expand...
Click to collapse
Hashcode has gotten around this issue multiple times with something called a bootstrap but I'm not too sure how it works
Sent from my LG-V480 using Tapatalk

Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...

i just signed in with my amazon account, you will need to unroot your fire and reset it as 5.0 is a OTA.

bibikalka said:
Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...
Click to expand...
Click to collapse
I wish I could find that bin file link... I looked for it but could not find a link to the actual bin file.. If ota's download to the sdcard then It could still be accessed but I don't know where it downloads to. If it downloads to the data dir of the app it would be inaccesable since you need to be on the latest update in order to download the 5.0 version and on the latest version we have no root which means no access to data dir
Sent from my LG-V480 using Tapatalk

this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..

edgar.vrgs said:
this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..
Click to expand...
Click to collapse
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk
Click to expand...
Click to collapse
i have tried but i cant figure it out

It worked perfectly. Thanks

Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.

devicer said:
It worked perfectly. Thanks
Click to expand...
Click to collapse
great to hear it!
Sent from my LG-V480 using Tapatalk

bpeery84 said:
Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.
Click to expand...
Click to collapse
I hear ya
Sent from my LG-V480 using Tapatalk

so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?

edgar.vrgs said:
so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?
Click to expand...
Click to collapse
does adb devices list your device. Maybe try re-downloading the update in case of corruption
Sent from my LG-V480 using Tapatalk

Perfect timing! Lost root last week and hoped for a way to get back. You the man

I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
This would help to re-pack the update in a way that does not re-write key partitions, then one can have TWRP and root on 5.0
It does sound like 5.0 is a nice update, since it provides stock Android. That's what custom ROMs are usually for, but Amazon will give it away !

bibikalka said:
I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
Click to expand...
Click to collapse
I was wondering the same. Seems like you could rename the otaverifier apk back to (plain) .apk and get the download but by keeping com...otaverifier blocked it wouldn't install. I'm just not sure these developer updates are handled like any other.