http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
The new 7"Amazon tablet on Amazon OS 5 was just rooted today. Anyone want to give it a go on the Fire TV? I doubt it would work, but worth a shot...
Not sure why no one cares about this, maybe wrong section? But here's a reply from the developer regarding using it on the fire tv:
" technically, if you have access to the original boot.img of the other FireOS device 5, can get into fastboot, and do the boot.img repacking, theoretically you can use the same method.
but, you definitely can't use this as it is..."
So do we have the correct boot.img for the device? ?
This rooting method relies on using a modified boot image, loaded through fastboot, to mount the system partition as writable. This will not work for the 1st-gen Fire TV or Fire TV Stick because they are hardware locked to not allow fastboot to load a boot image. Oddly, the 2nd-gen Fire TV will allow fastboot to load a boot image, so it may be possible to root the 2nd-gen Fire TV using this method. The problem is, we do not have a complete original boot image for the 2nd-gen Fire TV to use as the base for the modified boot image. The boot image is normally extracted from the software update file, but since the 2nd-gen Fire TV switched to incremental updates, its updates do not contain a complete boot image. Only patches to the boot image.
I thought we had complete fastboot and bootloader access on the v1 tv...
Oh no! Its like "Yess, finally soon - Wait - NoooooO"
Are you shure about not beeing able to enter fastboot on First-Gen-AFTV? That Thread looks like it could somehow be possible: http://forum.xda-developers.com/fire-tv/help/fastboot-mode-usb-unbricking-t3146278
dafunkydan said:
Oh no! Its like "Are you shure about not beeing able to enter fastboot on First-Gen-AFTV? That Thread looks like it could somehow be possible:
Click to expand...
Click to collapse
You may be able to enter fastboot mode but the bootloader is still locked and read-only on the AFTV 1, hence rbox developing a bootloader unlock for those of us with root.
AFTVnews.com says the AFTV2 bootloader is unlocked, which is semi good news I suppose.
so could someone with image lets say 5.03 perform a hardware root on the emmc of the device and then extract the boot.img be possible route?
If the emmc hardware root still works on the AFTV2, you should be able to dump the bootloader.
roligov said:
You may be able to enter fastboot mode but the bootloader is still locked and read-only on the AFTV 1, hence rbox developing a bootloader unlock for those of us with root.
AFTVnews.com says the AFTV2 bootloader is unlocked, which is semi good news I suppose.
Click to expand...
Click to collapse
the bootloader is locked on the fire tablet too, but they still rooted it.
ldeveraux said:
the bootloader is locked on the fire tablet too, but they still rooted it.
Click to expand...
Click to collapse
So it looks like they are using fastboot boot to boot a modified kernel image. On Fire TV, it prevents you from running fastboot boot.
rbox said:
So it looks like they are using fastboot boot to boot a modified kernel image. On Fire TV, it prevents you from running fastboot boot.
Click to expand...
Click to collapse
Do you have an AFTV2 rbox? If not we need to get a fund going to buy you one so you can tinker.
Elias said "Oddly, the 2nd-gen Fire TV will allow fastboot to load a boot image" so it will be interesting to see if you can do anything with it.
roligov said:
Do you have an AFTV2 rbox? If not we need to get a fund going to buy you one so you can tinker.
Elias said "Oddly, the 2nd-gen Fire TV will allow fastboot to load a boot image" so it will be interesting to see if you can do anything with it.
Click to expand...
Click to collapse
I don't, and I wasn't really planning on getting one. It's still yet to be seen if it can actually load an unsigned kernel image.
Oh ok. Maybe Elias can setup a donation page on AFTVNews.com with an "Assist rbox in getting an AFTV2" with your donation link and a counter. You have done a lot for the community, I'm sure many people will donate, I would definitely donate again.
roligov said:
Oh ok. Maybe Elias can setup a donation page on AFTVNews.com with an "Assist rbox in getting an AFTV2" with your donation link and a counter. You have done a lot for the community, I'm sure many people will donate, I would definitely donate again.
Click to expand...
Click to collapse
I'm sure we can get enough donations, but I'll leave it up to @rbox if he wants it. I won't start a campaign and force it on him without his okay.
AFTVnews.com said:
I'm sure we can get enough donations, but I'll leave it up to @rbox if he wants it. I won't start a campaign and force it on him without his okay.
Click to expand...
Click to collapse
If it can be verified that unsigned kernels work, I guess I could probably work on it.
rbox said:
If it can be verified that unsigned kernels work, I guess I could probably work on it.
Click to expand...
Click to collapse
Then let's just assume it can and go ahead and get you a box If not unsigned kernels, I'm sure something will come around that the community will benefit from you having a 2nd-gen Fire TV to experiment on. I'll start up a campaign on Monday.
AFTVnews.com said:
Then let's just assume it can and go ahead and get you a box If not unsigned kernels, I'm sure something will come around that the community will benefit from you having a 2nd-gen Fire TV to experiment on. I'll start up a campaign on Monday.
Click to expand...
Click to collapse
OK. But everyone needs to be clear that I make no promises about anything.
rbox said:
OK. But everyone needs to be clear that I make no promises about anything.
Click to expand...
Click to collapse
You got it. I'll make sure that's clear.
rbox said:
OK. But everyone needs to be clear that I make no promises about anything.
Click to expand...
Click to collapse
Perfect! There are no expectations and no pressure Tinker when you can.
rbox said:
If it can be verified that unsigned kernels work, I guess I could probably work on it.
Click to expand...
Click to collapse
It's definitely locked. If you look at the UART output you can see it just doesn't setup the memory mapping correctly in fastboot mode vs lk mode. I even tried to recompute the hash and update the signature and of course that failed. This was with modifying the boot partition not even using fastboot so in lk mode. We'd need some sort of unlock code like you did for the first one. That's why I gave up and went to using the preloader to modify the flash. It was a ton more work because I had to write an MMC driver for PIO mode based on the kernel sources. Potentially if you can modify lk (which is also signed) or just understand how it works an unlock code might be generated. If we could find a way to dump the preloader that would be even more helpful to potentially extract keys because then SP Flash Tool could work. Then the device would be unbrickable pretty much. I'm guessiung the boot process is all protected and they keys are store in trustzone and unobtainable.
Related
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file. I will try rerooting my device using known methods as soon as I get home and keep you updated.
jonathanlyng said:
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file. I will try rerooting my device using known methods as soon as I get home and keep you updated.
Click to expand...
Click to collapse
Same here ... any luck with re-rooting?
Danged Amazon and their OTA
jonathanlyng said:
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file.
Click to expand...
Click to collapse
Same here. I suppose I'll patiently wait for the next iteration of rooting this one. And hopefully a good way to stop the OTA updates from Amazon. If anyone reads this and knows of anything I can do in the way of offering files from my now unrooted device (ADB still connects at user level), I'll be glad to help the cause.
On the bright side, most stuff I've done works fine without root. I didn't bother with Google Play because that hadn't been perfected and the 1 Mobile Market seems to work fine, as well as side loading.
If you feel like it you can downgrade your is now, there no utility to do it for you yet, but the images are there now so you can flash the older pre-rooted system and boot image from fastboot and it should do the trick, just figure out a way to keep it from updating as well.
Sent from my Amazon Kindle Fire HD using Tapatalk
Sorry about that
chalid said:
Same here ... any luck with re-rooting?
Click to expand...
Click to collapse
I didn't have spare time yet. I'm gonna try whenever, I get some gadget time.
Downgrading? It would be worthwhile if I knew the push server's IP; and it's clearly not any of those that have roamed the net. There is a stray IP that hasn't been identified yet. downgrading and keeping the system offline or under a low battery level is too anoying to be worthwhile IMHO.
But those who want may try to proxy their wifi connection through their computer, downgrade their device, leave it alone and check in their proxy logs to pinpoint which IP is uploading the update to their device. Re-downgrade, root, re-wall their device.I'll try this but I won't be able to do it within the next few days.
In the meantime, gotta go.
Couldn't you just leave an adb shell running on the PC while running a continuous netstat?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Couldn't you just leave an adb shell running on the PC while running a continuous netstat?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh... yes, obviously... *puts on dunce hat*
BTW: such a thing might not be necessary, as I read on the HDX forum this about said update:
"It now appears that renaming or removing com.amazon.dcp.apk stops Amazon ota updates. Ex. com.amazon.dcp.apk.old"
jonathanlyng said:
Oh... yes, obviously... *puts on dunce hat*
BTW: such a thing might not be necessary, as I read on the HDX forum this about said update:
"It now appears that renaming or removing com.amazon.dcp.apk stops Amazon ota updates. Ex. com.amazon.dcp.apk.old"
Click to expand...
Click to collapse
Yeah I've done something like that (on the 2012 model), but instead I used Android Firewall to block it from using Wi-Fi, no OTA updates now, been good for months
Seems the best way to prevent updates.
stunts513 said:
If you feel like it you can downgrade your is now, there no utility to do it for you yet, but the images are there now so you can flash the older pre-rooted system and boot image from fastboot and it should do the trick, just figure out a way to keep it from updating as well.
Click to expand...
Click to collapse
I presume the files you speak of are:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
But NOT the boot0block.zip img because that's specific to the individual's device. I thought about doing this, but admittedly, was a little uncertain. I don't want to brick it. Basically, if I fastboot, I can push those images over safely? I presume I'd want to have my wireless turned off in advance of this operation, lest I end up exactly where I began with the thing wanting to update right away again.
Thanks much for the feedback!
kfsowi 11.3.2.1
hello people,
this is my first post here love the site, anyways anything yet that can be done about kfsowi on 11.3.2.1 yet can it be rooted or downgraded so i could get my root back.
thanks
SOLUTION!
http://forum.xda-developers.com/showthread.php?t=2544736&page=30#post_message_50878798
Courtesy of GranPC
Fastboot cable
where is the best and fastest way to get a fastboot cable online or in a store.
thank you
louiep said:
where is the best and fastest way to get a fastboot cable online or in a store.
thank you
Click to expand...
Click to collapse
From Amazon.COM though they are quite easy to make
Sent from my KFSOWI using xda app-developers app
Any skilled dev here is able to make recovery for Razer Forge? I know it's nexus forums but these 2 are kinda similar both run android tv etc.. root can be achieved with kingroot then one can swap (if knows how) to SuperSU.
I would love to have some CM 12.1 on it.. and don't know where to ask.
Any help?
the only thing they seem to have in common is the fact that they run android tv, they are totally different when it comes down to hardware. but if your wanting it to happen you should post some dumps from the system so devs can take a look at them and possibly build a recovery. if the bootloader is locked that can be another issue also.
pbanj said:
the only thing they seem to have in common is the fact that they run android tv, they are totally different when it comes down to hardware. but if your wanting it to happen you should post some dumps from the system so devs can take a look at them and possibly build a recovery. if the bootloader is locked that can be another issue also.
Click to expand...
Click to collapse
How can I find out if bootloader is locked or not?
fastboot oem unlock ? I would need USB to USB cable to do adb first.
Would that be good way to find out?
pbanj said:
the only thing they seem to have in common is the fact that they run android tv, they are totally different when it comes down to hardware. but if your wanting it to happen you should post some dumps from the system so devs can take a look at them and possibly build a recovery. if the bootloader is locked that can be another issue also.
Click to expand...
Click to collapse
Hey a late update about 3 weeks ago razer provided tools with home image etc.. I'd like to post system dump when I get back to the states in couple days,bootloader is unlockable with fastboot oem unlock.
You think you could help me out ?
I recently updated to the developers preview of Fire OS 5.0 and I had TWRP installed and I was not able to downgrade using the ADB sideload method. So for people that have the same issue here is what you need to do to resolve this and get back to Fire OS 4.0
Summary:
Rolling back to Fire OS 4 is easy! Simply visit the page below and follow the instructions provided to complete the rollback form.
http://www.amazon.com/gp/html-forms-controller/wdp_gen_rb
Note: The rollback process requires you to provide both your email used to participate in the Developer Preview, as well as your device's DSN. Instructions on obtaining your DSN are included in the link provided.
What version of OS 4 does this roll you back to?
junglistknot said:
I recently updated to the developers preview of Fire OS 5.0 and I had TWRP installed and I was not able to downgrade using the ADB sideload method. So for people that have the same issue here is what you need to do to resolve this and get back to Fire OS 4.0
Summary:
Rolling back to Fire OS 4 is easy! Simply visit the page below and follow the instructions provided to complete the rollback form.
http://www.amazon.com/gp/html-forms-controller/wdp_gen_rb
Note: The rollback process requires you to provide both your email used to participate in the Developer Preview, as well as your device's DSN. Instructions on obtaining your DSN are included in the link provided.
Click to expand...
Click to collapse
You had TWRP with OS 5.0. So you had root and OS 5.0? how?
siegesoldier said:
You had TWRP with OS 5.0. So you had root and OS 5.0? how?
Click to expand...
Click to collapse
No I had root on 4.5.4 with twrp and I did not have my nav bar so I decided to try to upgrade to 5.2.0 thinking I would be able to downgrade. I was stuck at this OS because I can't get into the stock recovery or twrp. So basically I need to go back to 4.5.3 to gain root and upgrade back to 4.5.4.
DoLooper said:
What version of OS 4 does this roll you back to?
Click to expand...
Click to collapse
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
Lol, so just to be clear, this isn't something you've even actually done yet. Nice. So what, you're just working on theory and leading people to do it with you blindly? Awesome. Post back when you have something with substance for us.
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
I'm guessing it will be 4.5.4, but if it's lower that would make getting 4.5.3 (and root!) much easier. Hope you can keep an eye on it and block OTA as soon as it comes through. thx.
This is directly from Amazon and the zip is signed. There is no reason it shouldn't work. I am just trying to let anyone in the same boat as me this may help them. No need to be rude.
I apologize if that sounded rude. Wasn't my intent at all. I assumed downgrade would be OTA, and it would help everyone if we can get the developer preview and then downgrade in the way you suggest to 4.5.3 or less.
No not you I was referring to the post above yours
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
Have you gotten the rollback yet? If so has it fixed your ability to get to the recovery?
I finally received the update but I can install it because it still needs to boot to the recovery. Sorry for the misleading post. Just so everyone knows it also was 4.5.4 OTA. So I still need to flash the recovery.img through fastboot so if anyone has this img please share.
junglistknot said:
I finally received the update but I can install it because it still needs to boot to the recovery. Sorry for the misleading post. Just so everyone knows it also was 4.5.4 OTA. So I still need to flash the recovery.img through fastboot so if anyone has this img please share.
Click to expand...
Click to collapse
I have 4.5.3 recovery img somewhere, but I am not sure it'd help you since I doubt you could flash anything through the fastboot. I'll dig it up, and upload.
bibikalka said:
I have 4.5.3 recovery img somewhere, but I am not sure it'd help you since I doubt you could flash anything through the fastboot. I'll dig it up, and upload.
Click to expand...
Click to collapse
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
junglistknot said:
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
Click to expand...
Click to collapse
In the same boat anxiously awaiting for someone to find a stock recovery.img
junglistknot said:
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
Click to expand...
Click to collapse
wyldeice said:
In the same boat anxiously awaiting for someone to find a stock recovery.img
Click to expand...
Click to collapse
Well, this is 4.5.3. I dd'ed from my recovery when doing backups. See if it works!
so after messing with this so much bootloader is locked again and I am not able to flash recovery via fastboot. Looks like I will need to wait until someone can root 5.2.0 OS. Unless anyone else has any ideas because I feel like I have tried everything.
junglistknot said:
so after messing with this so much bootloader is locked again and I am not able to flash recovery via fastboot. Looks like I will need to wait until someone can root 5.2.0 OS. Unless anyone else has any ideas because I feel like I have tried everything.
Click to expand...
Click to collapse
5.2.0 can be rooted, but you'll have to start with a working TWRP, which means you already must have root. For independent 5.2.0 root, you may wait for a long time.
With fried recovery and no root, I don't think you are going anywhere, other than to Amazon customer service
bibikalka said:
5.2.0 can be rooted, but you'll have to start with a working TWRP, which means you already must have root. For independent 5.2.0 root, you may wait for a long time.
With fried recovery and no root, I don't think you are going anywhere, other than to Amazon customer service
Click to expand...
Click to collapse
Well I had TWRP and root beforehand. In fact SuperSU is still in the app drawer but it says the binary isn't installed. I can wait though I know I can bring this thing back to life at some point. I have a galaxy s5 rooted with CM12 on it so that will keep me busy while I wait.
Edit: Amazon is sending me a new Fire HD 7. Be here on Friday
junglistknot said:
Well I had TWRP and root beforehand. In fact SuperSU is still in the app drawer but it says the binary isn't installed. I can wait though I know I can bring this thing back to life at some point. I have a galaxy s5 rooted with CM12 on it so that will keep me busy while I wait.
Edit: Amazon is sending me a new Fire HD 7. Be here on Friday
Click to expand...
Click to collapse
Just curious what you told them? I am in the exact same place as you, but it was with my wife's brand new tablet from prime day.
Came out on July 14, 2016 10:30 PM. There is no bin file at this time.
Note: Don't try to downgrade from this. Might brick your FireOS. Need a report on it actually works or not first.
Cannot be rooted. Tested with NewKingrootV4.95_C149_B285_en_release_2016_07_15_105203.apk
Comment moved to different post. Sorry new to forum
Tip: If you log in on the Amazon it gonna try to update the system automatic. Don't log in then it gonna ask first after the download.
It wouldn't let me past the splash screen without logging in
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Venio2000 said:
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Click to expand...
Click to collapse
I don't recall that anyone posted anything about the new release. You should just wait until the resident experts chime in with some guidelines.
fmc000 said:
I don't recall that anyone posted anything about the new release. You should just wait until the resident experts chime in with some guidelines.
Click to expand...
Click to collapse
I will - I just wish I would have waited longer with the update, but it was brand new and said: update me now
Thx for any help/ Info
I used the 5.1.2 bin file and installed adb drivers on my windows computer. I used a program called minimal adb and fastboot. I opened minimal adb and fastboot, powered on fire by holding volume down and power until bootloader. Selected apply update from adb. Typed ' adb sideload' and dragged the bin file into the window of minimal adb and fastboot. Hit enter and watched it climb to100%. This was from 5.1.4 and 5.1.3. I do not know if it will work going down from 5.3.1.0. the fire is a piece of crap with the stock amazon installed imo
Venio2000 said:
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Click to expand...
Click to collapse
What is the date of your 5.3.1.0 FireOS ?
This thread is your friend :
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
You would try to sideload the 5.1.2 (the last version that's rootable at the moment). There is a chance the downgrade would brick (due to the possible higher version of the newer bootloaders ), so be prepared to send Fire back to Amazon if this fails.
One option is to write the entire new system, but that would take forever since those tools are slow ...
WARNING: Do not downgrade from 5.3.1.0. Brick the device if you do.
so now we're screwed and can't root a device? Has this ever happened before? What are the odds the first device I purposely buy to try my hand at rooting something and it turns out to be unrootable after I brick the first one....
The ROM image for FireOS 5.3.1.0 has now been published on the Fire (5th Generation) Software Updates page. The filename is update-kindle-global-37.5.5.2_user_552153420.bin
http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
Determine your software version
Determine the current software version on your Fire tablet before downloading and installing a software update.
Swipe down from the top of the screen and then tap Settings.
Tap Device Options, and then tap System Updates.
If you have the latest software update, it should look like this: Your device is running Fire OS 5.3.1.
Download Fire (5th Generation) software updates
Click the link below to download the software update to your computer:
Download Software Update 5.3.1
Click to expand...
Click to collapse
fusion01k said:
so now we're screwed and can't root a device? Has this ever happened before? What are the odds the first device I purposely buy to try my hand at rooting something and it turns out to be unrootable after I brick the first one....
Click to expand...
Click to collapse
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
beezar said:
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
Click to expand...
Click to collapse
Thanks for the advice. I will check it out when it arrives soon.
beezar said:
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
Click to expand...
Click to collapse
For those without a bricked device, just one on 5.3.1.0 and still want to root is it best to just sit tight then and wait on a work around?
jmorlin said:
For those without a bricked device, just one on 5.3.1.0 and still want to root is it best to just sit tight then and wait on a work around?
Click to expand...
Click to collapse
Well there doesn't seem to be another choice. A "work around" may come tomorrow or never. Seen both scenarios play out.
bibikalka said:
One option is to write the entire new system, but that would take forever since those tools are slow ...
Click to expand...
Click to collapse
@bibikalka what tools are you referencing here? And how to write entire new system?
beautiful3cellar said:
@bibikalka what tools are you referencing here? And how to write entire new system?
Click to expand...
Click to collapse
Sorry, that's not correct It looks like Amazon patched the hole that allowed AFTV2 tools to work. Since these tools don't work with FireOS 5.3.1, even the slow path is not available
bibikalka said:
Sorry, that's not correct It looks like Amazon patched the hole that allowed AFTV2 tools to work. Since these tools don't work with FireOS 5.3.1, even the slow path is not available
Click to expand...
Click to collapse
AFTV2 Tools works below OS 5.3.1 though?
beautiful3cellar said:
AFTV2 Tools works below OS 5.3.1 though?
Click to expand...
Click to collapse
I think the last version was 5.1.1. The tools don't work in 5.1.2 . Amazon replaces the preloader with each update, so they can fix it quite easily.
It has come to light that a new update has been released for the Prime version stock ROM. This update is called V6.6 (duh), and the update replaces the preloader. Some people have reported bootloops, one has gotten a brick, and I am all but certain that Amazon is trying to patch the preloader to remove any chance of rooting or converting to OEM ever again. It also replaces the boot image, which we believe is a way to re-lock the bootloader, or possibly even make fastboot ignore the unlocked status. This could also destroy your ability to root, run TWRP, or run any custom ROM ever again. If you are on the Prime stock ROM, DO NOT take the OTA to V6.6. It's really not worth it for the security patch. I also encourage all users of V6.1, V6.4, or V6.5 to go ahead and convert your phone to the non-Prime variant while you have the chance. Amazon is known for jamming updates down people's throats so I would not be surprised if they have a way of installing that update without your approval.
The conversion guide is here: http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
There is some discussion about the OTA in the last few pages of the general discussion thread here: http://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-t3418354/post68565531#post68565531
We can use this thread to further dissect and discuss the update.
The boot img can lock the Bootloader.
Thanks for the warning. I would have taken it as I think V6.5 was a good update and improved performance (at the expense of battery life).
DarkBlood. said:
The boot img can lock the Bootloader.
Click to expand...
Click to collapse
No, but some kernel/ramdisk shenanigans could lock it at boot.
We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.
With the fire tablet they disabled the preloader and changed the pid
ColtonDRG said:
We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.
Click to expand...
Click to collapse
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.
I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.
I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.
DarkBlood. said:
With the fire tablet they disabled the preloader and changed the pid
Click to expand...
Click to collapse
You cannot simply "disable" the preloader. We discussed what exactly Amazon did with the Fire a little bit in the private hangout the other day. The bottom line is that we still don't know exactly what shenanigans Amazon is up to, or what tricks they have up their sleeve. Knowing Amazon, it can't be good for us.
jacewt said:
I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.
Click to expand...
Click to collapse
It has the August security patch and some things that lock things down. Nothing else that I'm aware of.
bionictoothpick said:
I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.
Click to expand...
Click to collapse
If you unlocked your bootloader (fastboot style) via one of the methods before, you should still be able to gain root. If not, you are probably hosed, at least for now. Weather or not you will end up regretting that is up to you, but I certainly would.
kal250 said:
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.
Click to expand...
Click to collapse
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".
ColtonDRG said:
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".
Click to expand...
Click to collapse
Fortunately, I had OTA blocked and as I said the other day when i get downtime(hopefully Sunday), I'm back to OEM, to hell with security patches!!
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
The zip is available in https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
Go for it, but I'm not interested in taking any of Amazon's **** either way.
As @DarkBlood. said, the zip file is mirrored on https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/
I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....
ariesgodofwar said:
I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....
Click to expand...
Click to collapse
A handful of people around here actually got their phone bootlooped just after taking the upgrade straight from 6.5 to 6.6. At first I figured it was a fluke because their phones were altered, but at this point it's getting very suspicious (almost like it's a hit or miss thing for everyone, even those that haven't touched anything). I hope this doesn't damage the device's reputation too bad, and Amazon better get their **** together. Chopping off their nose in spite of their face. I guess I shouldn't be surprised at this point. This is Amazon we're talking about here.
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
If the zip can be modified, can we inject the 6.1 preloader and bootloader into the 6.6 OTA and modify it to run over current 6.6 installs allowing those who have been locked to at least unlock themselves?? I'm not savy enough to try....