I've exchanged several PMs with pokey9000 today. He has taken a look at the software update packages for both the 2nd generation KF and the 7" HD. The MLO (xloader, 1st stage bootloader) is signed and the boot header is the type used for HS (high security) OMAP devices with the M-Shield turned on. If the setup is comparable to the Nook Tablet, this is not good news for those hoping to modify these devices in one way or another. The Nook Tablet's exploit was to utilize the external sdcard as an alternate boot device and that doesn't really help with these 2nd generation KFs.
It's all subject to verification by someone who has a device in hand, but it doesn't look good. This is not to say that it's impossible, but it will be considerably more difficult to manipulate these devices than their 1st generation cousin.
So, let's all hope for the best, but be prepared for the worst. If you plan to buy one of these devices, buy them as an Amazon tablet to be used in the Kindle Fire ecosystem. Don't buy them expecting to run Jelly Bean the day after tomorrow.
Some clarification... and much left unanswered...
kinfauns said:
The Nook Tablet's exploit was to utilize the external sdcard as an alternate boot device and that doesn't really help with these 2nd generation KFs.
Click to expand...
Click to collapse
Not quite right. NT's exploit was far more complicated than that and has nothing to do with using the external SD card (or depending on one). It could have been done simply with root (or any other method for overwriting a partition, which was required to insert a 2nd unsigned bootloader into the boot sequence). If you're curious, you can look at the CyanoBoot 2nd bootloader for NT description or source to see what's going on.
I've taken a VERY quick look at the bootloader source for the HD7 as well, pushed here for anyone who wants it. There is in fact signature verification code in the uboot source (~line 140).
Also, looks like there are three configs-- bowser, jem, and tate. I have to look at it closer but it looks like tate is a subtype of bowser, and the HD7 I assume is tate. Hashcode also found a "radley" in the kernel code, but I haven't looked at that.
Anyway.. it is possible that bauwks' flaw or some other flaw exists in this signature verification code, but the code isn't identical to NT so who knows.
Incidentally, the new revision of the Kindle Fire (otter2) also has the same code, and there's a thread about the signature issue here as well.
It's all subject to verification by someone who has a device in hand, but it doesn't look good. This is not to say that it's impossible, but it will be considerably more difficult to manipulate these devices than their 1st generation cousin.
So, let's all hope for the best, but be prepared for the worst. If you plan to buy one of these devices, buy them as an Amazon tablet to be used in the Kindle Fire ecosystem. Don't buy them expecting to run Jelly Bean the day after tomorrow.
Click to expand...
Click to collapse
Yeah.. it all depends on whether there's a flaw as there was with the Nook Tablet... someone get bauwks on the line
Meanwhile, I'm enjoying my free (as in speech) Nexus 7...
fattire said:
Not quite right. NT's exploit was far more complicated than that and has nothing to do with using the external SD card (or depending on one). It could have been done simply with root (or any other method for overwriting a partition, which was required to insert a 2nd unsigned bootloader into the boot sequence).
Click to expand...
Click to collapse
Technically true, but altering the boot chain with a removable microSD makes it a reversible process. Overwriting the boot image on emmc without any other boot options is serious brown trousers time. Now if they left in fastboot, then its not so scary if a similar hack to the NT can be done. Still, with no possibility of USB boot there's no recourse if any exploits get patched.
Meanwhile, I'm enjoying my free (as in speech) Nexus 7...
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 7 using xda premium
fattire said:
Not quite right. NT's exploit was far more complicated than that and has nothing to do with using the external SD card (or depending on one). It could have been done simply with root (or any other method for overwriting a partition, which was required to insert a 2nd unsigned bootloader into the boot sequence). If you're curious, you can look at the CyanoBoot 2nd bootloader for NT description or source to see what's going on.
...
Click to expand...
Click to collapse
Thanks for the clarification and your input as well. I just wanted to get the discussions going on the possibilities of opening up this device to development, but also temper some expectations. There are many people waiting and some undoubtedly have ordered with the assumption that these 2nd generation devices will be getting the full range of development enjoyed by the original. I was mostly paraphrasing and summarizing, so I'll leave the details to those with the know-how.
I'm sure many people will be scouring the code and tinkering with their new devices in the coming days to figure something out.
Boring stuff...
pokey9000 said:
Technically true, but altering the boot chain with a removable microSD makes it a reversible process. Overwriting the boot image on emmc without any other boot options is serious brown trousers time
Click to expand...
Click to collapse
It's not THAT risky, I don't think. Even w/o SD card on NT, the safe(st) way to do it would be to replace the recovery partition with a 2ndboot/cyanoboot-enhanced recovery.img from a normal rooted boot. If recovery fails, you're still okay-- you can always just boot normally, gain root, and replace recovery again. If you're verified good, then use recovery to replace boot.img.
On NT, the normal secure boot sequence is unaffected when you replace recovery. That's because on the NT, you are never removing or touching the original uboot (ub1), so there's not much danger of a brick as long as you always have two means for booting (normal + recovery).
This is all academic as far as KFire HD goes, as I'm guessing from existence of the "crypto" partition that bauwks' bugfix won't work. I need to give a look at the signature verification stuff, as I haven't looked at it yet, but I'm not particularly optimistic.
pokey9000 said:
Now if they left in fastboot, then its not so scary if a similar hack to the NT can be done. Still, with no possibility of USB boot there's no recourse if any exploits get patched.
Click to expand...
Click to collapse
True, although w/NT, BN can only patch it by modifying the hardware, which would create massive support headaches for two versions of the boot. This is because w/unchanged hardware, the current, signed xloader->ub1->ub2 chain can always be used to load whatever. Again, I have more clarification on this-- if you're not already familiar with the details, find me on IRC.
speaking of fastboot, apparently if CONFIG_MACH_BOWSER_SUBTYPE_TATE is set, fastboot_idme is defined and fastboot and other debugging stuff seems to be turned on. I'm pretty sure "idme" is a uboot command. It's commented-out of drivers/fastboot.c as a shortcut to be enabled for TATE only.
FWIW, here are some various versions of the bowser board:
Bowser-Jem-PreEVT2-
Bowser-Jem-PreEVT2-
Bowser-Tate-PreEVT2.1-
Bowser-Tate-PostEVT2.1-
Bowser-Tate-PostEVT3HS2-
Bowser-Tate-DVT-
Bowser-Tate-PVT-
Bowser-Radley-
tate = product id 7
jem = product id 8
radley = product id 9
HS is High Security, I'm pretty sure.
Someone apparently is a fan of To Kill a Mockingbird (Boo Radley, Atticuls "Jem" Finch, Heck Tate, etc.). I don't know what the Bowser connection is... this guy? Or maybe just one of these.
Gotta go.
software RD of AMAZON said it was impossible to crack the NEW KF system, unless u know the key in the machine
This was probably done in response to all the bricked Kindle Fires that were returned with the original Fire. That and the fact that if they didn't, it probably would have meant a price increase due to increased warranty expense. However, it seems i would make sense to simply allow an owner to pay a small fee to unlock the boot loader and register a modified Fire as "no warranty" for software issues.
kinfauns said:
I've exchanged several PMs with pokey9000 today. He has taken a look at the software update packages for both the 2nd generation KF and the 7" HD. The MLO (xloader, 1st stage bootloader) is signed and the boot header is the type used for HS (high security) OMAP devices with the M-Shield turned on. If the setup is comparable to the Nook Tablet, this is not good news for those hoping to modify these devices in one way or another. The Nook Tablet's exploit was to utilize the external sdcard as an alternate boot device and that doesn't really help with these 2nd generation KFs.
It's all subject to verification by someone who has a device in hand, but it doesn't look good. This is not to say that it's impossible, but it will be considerably more difficult to manipulate these devices than their 1st generation cousin.
So, let's all hope for the best, but be prepared for the worst. If you plan to buy one of these devices, buy them as an Amazon tablet to be used in the Kindle Fire ecosystem. Don't buy them expecting to run Jelly Bean the day after tomorrow.
Click to expand...
Click to collapse
I got my 7" Fire HD in the mail yesterday and am in this 100% to see custom roms running on it.
While I have just under a year of Android tinkering under my belt and many more years of experience playing with pc's and various flavors of embedded systems, I dunno where it all begins for this new device, but I want to help the dev community in any way I can.
If anybody has specific requests about the device or needs to test out something on one, I don't mind being a guinea pig, as long as there isn't too much risk of bricking my cool new toy...
I will take a look at the u-boot sources of the new fires too and see how/what they have changed. Very possible that they fixed the funny flaw in the loading process for this iteration of their devices.
It would certainly be sad since a full HD android tab is tempting. At least for the 7inch category we have the nexus7 as an extremely good alternative.
Ifixit has a teardown of the device, and there is a big test point labeled "USB BOOT" on the main board, and two smaller ones labeled "RX" and "TX"....
http://guide-images.ifixit.net/igi/UapMeZFPXthjTrEn.huge
Returned
I have already hit the Return Item button on this. I could care less about the speakers and the screen! Gonna pick up the Nexus 7 instead.
pokey9000 said:
Technically true, but altering the boot chain with a removable microSD makes it a reversible process. Overwriting the boot image on emmc without any other boot options is serious brown trousers time. Now if they left in fastboot, then its not so scary if a similar hack to the NT can be done. Still, with no possibility of USB boot there's no recourse if any exploits get patched.
Yes.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
just wait for pokey9000 to answer ， wait for u have idea how to USB boot it
psomero said:
I got my 7" Fire HD in the mail yesterday and am in this 100% to see custom roms running on it.
While I have just under a year of Android tinkering under my belt and many more years of experience playing with pc's and various flavors of embedded systems, I dunno where it all begins for this new device, but I want to help the dev community in any way I can.
If anybody has specific requests about the device or needs to test out something on one, I don't mind being a guinea pig, as long as there isn't too much risk of bricking my cool new toy...
Click to expand...
Click to collapse
Well I for one will be quite happy if someone can get an alternate launcher to work without rooting. Didn't have to on the original KF for them to work.
---------- Post added at 12:50 PM ---------- Previous post was at 12:46 PM ----------
JaxDomino said:
I have already hit the Return Item button on this. I could care less about the speakers and the screen! Gonna pick up the Nexus 7 instead.
Click to expand...
Click to collapse
I hope not cause the Nexus 7 for those two things ain't as good as this Fire HD.
Worst case scenario, there's always the kexec option. As a last resort, it works even on devices where the bootloader was never cracked.
robertc88 said:
Well I for one will be quite happy if someone can get an alternate launcher to work without rooting..
Click to expand...
Click to collapse
Yes, that would do it for me too (along with some ability to sideload apps). I preordered the 8.9 HD so I'll keep close watch on the development. If no solution is found before end of November, I just might cancel, and look around for what's hot (and rootable) at that point.
bournezhang said:
just wait for pokey9000 to answer ， wait for u have idea how to USB boot it
Click to expand...
Click to collapse
USB boot needs a special boot loader (aboot in omap4boot used in Firekit) , and at least on the Nook Tablet it needs to be signed too. I doubt that TI's customers can or would opt for locking just flash boot so I'm going to assume that it won't work on the new Fires without a signed USB loader.
glad to see everyone brainstorming over here. sorry for the bad news. i'm gonna follow these closely as i want to get a kfire hd for the gf eventually, but only when this bootloader gets unlocked. til then, back over to my n7 (which i find boring at times, because everything just works... bummer) lol
fattire said:
It's not THAT risky, I don't think. Even w/o SD card on NT, the safe(st) way to do it would be to replace the recovery partition with a 2ndboot/cyanoboot-enhanced recovery.img from a normal rooted boot. If recovery fails, you're still okay-- you can always just boot normally, gain root, and replace recovery again. If you're verified good, then use recovery to replace boot.img.
On NT, the normal secure boot sequence is unaffected when you replace recovery. That's because on the NT, you are never removing or touching the original uboot (ub1), so there's not much danger of a brick as long as you always have two means for booting (normal + recovery).
This is all academic as far as KFire HD goes, as I'm guessing from existence of the "crypto" partition that bauwks' bugfix won't work. I need to give a look at the signature verification stuff, as I haven't looked at it yet, but I'm not particularly optimistic.
True, although w/NT, BN can only patch it by modifying the hardware, which would create massive support headaches for two versions of the boot. This is because w/unchanged hardware, the current, signed xloader->ub1->ub2 chain can always be used to load whatever. Again, I have more clarification on this-- if you're not already familiar with the details, find me on IRC.
speaking of fastboot, apparently if CONFIG_MACH_BOWSER_SUBTYPE_TATE is set, fastboot_idme is defined and fastboot and other debugging stuff seems to be turned on. I'm pretty sure "idme" is a uboot command. It's commented-out of drivers/fastboot.c as a shortcut to be enabled for TATE only.
FWIW, here are some various versions of the bowser board:
Bowser-Jem-PreEVT2-
Bowser-Jem-PreEVT2-
Bowser-Tate-PreEVT2.1-
Bowser-Tate-PostEVT2.1-
Bowser-Tate-PostEVT3HS2-
Bowser-Tate-DVT-
Bowser-Tate-PVT-
Bowser-Radley-
tate = product id 7
jem = product id 8
radley = product id 9
HS is High Security, I'm pretty sure.
Someone apparently is a fan of To Kill a Mockingbird (Boo Radley, Atticuls "Jem" Finch, Heck Tate, etc.). I don't know what the Bowser connection is... this guy? Or maybe just one of these.
Gotta go.
Click to expand...
Click to collapse
fattire is a beast for doing work on the Nooktablet with me, chm and all the other guys.... From what im reading, its actually kinda like booti from the Nook tablet. Very very interesting file at ./common/cmd_idme.c It seems as though theres a way to load a debugging kernel. Kinda curious if we can use that to smash a new boot into it. The following lines interest me:
./common/cmd_idme.c
Code:
#ifdef ENABLE_DIAG_KEY
if (!val_vol_up && val_vol_down) {
/* button up is pressed only */
printf("Tablet: Enter dkernel mode: ....\n");
*ptn = pdkernel;
}
Code:
case '2':
printf("Select Diagnostic image\n");
*ptn = pdkernel;
break;
and also this line in the ./include/config/tate.h
Code:
#define CONFIG_DIAGNOSTIC_BOOTCOMMAND "mmcinit 1;mmc 1 read 0x580 0x81000000 0x600000; bootm 0x81000000"
As for the boot hole that bauwks discovered on the nook tablet, it is not on this device, though it is highly possible that if this Diagnostic mode can be activated we can use the same exploit as we used with the fatload and the booti. This CONFIG_DIAGNOSTIC_BOOTCOMMAND can maybe do the same thing with something in the SAR memory, so its worth someone doing somemore research.
thebrave said:
Ifixit has a teardown of the device, and there is a big test point labeled "USB BOOT" on the main board, and two smaller ones labeled "RX" and "TX"....
http://guide-images.ifixit.net/igi/UapMeZFPXthjTrEn.huge
Click to expand...
Click to collapse
One way to make the device harder to alter is by making these test points the physical connections for a bootloader USB port. Perhaps the USB port accessible to the user is solely intended as a data transfer port for multimedia where the driver is initialised only after the anti-hacking measures are loaded?
pokey9000 said:
USB boot needs a special boot loader (aboot in omap4boot used in Firekit) , and at least on the Nook Tablet it needs to be signed too. I doubt that TI's customers can or would opt for locking just flash boot so I'm going to assume that it won't work on the new Fires without a signed USB loader.
Click to expand...
Click to collapse
This is standard operating practice. You can be assured that if flash boot is locked, USB boot will also be locked.
Interesting tidbit: While no Samsung Android device other than the Verizon GS3 (and rumor has it, upcoming Verizone Note 2) has a locked bootloader in terms of ability to boot a kernel, nearly ALL of them have the initial first stage of boot locked. It's just that Samsung usually drops the chain of trust early on. This is, for example, why Unbrickable Mod doesn't exist for any GS2 or GS3-family device - No one has access to a signed USB-bootable IBL/PBL/SBL setup. (Technically, one could likely USB-boot the existing IBL, but that IBL is hardcoded to go to flash for PBL/SBL.)
So far, no one I am aware of has ever compromised the low-level hardware enforcement of OMAP4 HS or Exynos4. In all cases of OMAP4, any compromise took advantage of holes in the chain of trust farther down the line - however nearly all attack vectors are known, so probably every compromise technique that is standard (kexec, second init, etc.) has a countermeasure in play with the KFHD if they're THAT confident in its unbreakability. In the case of Exynos4, in all current cases the chain of trust goes "insecure" so early that only people with clobbered bootloaders care.
I purchase a kindle fire hdx 7" with a cracked screen on ebay, prepared to order the necessary parts from china and restore it (somewhat) to working order. I did this, only to find that the device was blacklisted. Now I would like to install a custom operating system if any such thing exists. I am not a developer for this kind of thing, so pardon my post, but every single link to cyanogen and kindle hdx is a dead link (amazon legal dept?). Any suggestions, general or specific?
cambium0 said:
I purchase a kindle fire hdx 7" with a cracked screen on ebay, prepared to order the necessary parts from china and restore it (somewhat) to working order. I did this, only to find that the device was blacklisted. Now I would like to install a custom operating system if any such thing exists. I am not a developer for this kind of thing, so pardon my post, but every single link to cyanogen and kindle hdx is a dead link (amazon legal dept?). Any suggestions, general or specific?
Click to expand...
Click to collapse
Maybe u can find out why black listed...(probably stolen).. cause u will be hard pressed installing another Rom since none really exist yet. Those links are dead cause no roms exist. Once and if the device is rooted then more doors will open. No timeframe for that however. Might wanna wait on putting any money into this device. Good luck.
cambium0 said:
I purchase a kindle fire hdx 7" with a cracked screen on ebay, prepared to order the necessary parts from china and restore it (somewhat) to working order. I did this, only to find that the device was blacklisted. Now I would like to install a custom operating system if any such thing exists. I am not a developer for this kind of thing, so pardon my post, but every single link to cyanogen and kindle hdx is a dead link (amazon legal dept?). Any suggestions, general or specific?
Click to expand...
Click to collapse
Did the seller say it was blacklisted? If not, might be a buyer protection case there and you can return it.
Though seller might win if it was sold "for parts".
worked out
Tomen8r said:
Maybe u can find out why black listed...(probably stolen).. cause u will be hard pressed installing another Rom since none really exist yet. Those links are dead cause no roms exist. Once and if the device is rooted then more doors will open. No timeframe for that however. Might wanna wait on putting any money into this device. Good luck.
Click to expand...
Click to collapse
Well I messaged him asking where he'd bought it, he replied "Staples". It developed that he was in fact the original purchaser, but he went about unregistering his kindle the wrong way. He called Amazon and I've been able to register the Kindle so it worked out.
However there are a lot of blacklisted kindles on ebay that are catching my attention. I'd really be interested to know if it's possible to make use of that 2.2GHz snapdragon processor by installing some kind of android os on it to make a generic android tablet.
Despite my attempts to block the OTA update, my fire now has 5.3.2. It definitely lags compared to the previous firmware version. Does anyone known if it can be downgraded via ABD without bricking?
gbennett said:
Despite my attempts to block the OTA update, my fire now has 5.3.2. It definitely lags compared to the previous firmware version. Does anyone known if it can be downgraded via ABD without bricking?
Click to expand...
Click to collapse
I have read and was able to downgrade my 2015 Fire HD 7 from 5.3.2.0 to 5.3.1.0. Then I was able to install a CM Rom.
I also have the new HD 8 2016, but I am not sure if the downgrade will work.
Just bought a the HD 8 2016 since it is on sale (today) for $59 at Best Buy and THOUGHT I read it can be rooted, later learned it's only the older model that can be rooted. Really don't want an Android device that will remain unable to be rooted, so, might have to take it back even at that cheap price?
Would love to have a custom ROM on this tablet!
critofur said:
Just bought a the HD 8 2016 since it is on sale (today) for $59 at Best Buy and THOUGHT I read it can be rooted, later learned it's only the older model that can be rooted. Really don't want an Android device that will remain unable to be rooted, so, might have to take it back even at that cheap price?
Would love to have a custom ROM on this tablet!
Click to expand...
Click to collapse
I bought it knowing that it can't be rooted at the moment. But I'm going to block updates with openDNS and cross my fingers for a future root method. Still a pretty good tablet for the money and the Play Store works too. However, I still love my cheap, year-old Fire 7" with CM 12.1 the most despite the screen resolution.
What steps are required to block updates with openDNS? Would like to try it on Fire 8, 6th gen.
OscarDiggs said:
What steps are required to block updates with openDNS? Would like to try it on Fire 8, 6th gen.
Click to expand...
Click to collapse
I used this method for my Fire TVs, and it appears to work on the Fire tabs too.
http://www.aftvnews.com/how-to-bloc...-the-amazon-fire-tv-or-fire-tv-stick/#opendns
Thanks. Looks like this could work on devices that don't leave home network.
Hopefully this Fire HD 8 tablet 6th generation - 2016 can be rooted in near future. Better to block the OTA updates. By the way, can someone pin-point the codename for this device ? That is similar to KFFOWI_Ford for 7'' Fire-2015.
kesavan2000in said:
Hopefully this Fire HD 8 tablet 6th generation - 2016 can be rooted in near future. Better to block the OTA updates. By the way, can someone pin-point the codename for this device ? That is similar to KFFOWI_Ford for 7'' Fire-2015.
Click to expand...
Click to collapse
As I was trying KingRoot today it said the code for this one is "KFGIWI"
And I also saw another thread that stated KFGIWI_GI
I've never had an Android device, so I'm probably wording it completely wrong. But I AM in technology, so I can get around and understand pretty quick.
I just bought my son a Fire HD 10 (2017 version) for his birthday. I set it all up for him and put one of his favorite games on it - Vainglory. We noticed that any time there is a decent fight on the screen, it will lag out for 2-3 seconds, and then catch back up real quick. From their website, the Fire HD 10 exceeds all the requirements to run the game smoothly, so I'm wondering if it's all the Amazon bloatware that is causing the lag. First, do you think if I replaced the Fire OS with just stock Android, would it increase performance? Do you think I'll still have these lag issues even if I put stock Android on it? Second, if you think it will help, how do I wipe the Fire OS and install stock Android?
Nobody has any suggestions?
we cannot unlock Bootloader right now, so we cannot install custom ROM on Fire HD 10 right now, one thing you can do is root the device and disable amazon apps to make it runs better
https://forum.xda-developers.com/hd8-hd10/general/tut-fire-hd-10-7th-gen-2017-root-box-t3726443
convit161 said:
we cannot unlock Bootloader right now, so we cannot install custom ROM on Fire HD 10 right now, one thing you can do is root the device and disable amazon apps to make it runs better
https://forum.xda-developers.com/hd8-hd10/general/tut-fire-hd-10-7th-gen-2017-root-box-t3726443
Click to expand...
Click to collapse
Do you think that will help? Because I'm a button press away from posting this on craigslist. Amazon Fire products are so trash, I don't know why I bought this. An iPad 2 (7 years old) runs the game better than the newest Fire HD 10 (1 year old). Yes, I understand I only paid $150 for it, but I was optimistic about it.
I'll probably just end up spending more and get the newest iPad for $330.
jrossh21 said:
Do you think that will help? Because I'm a button press away from posting this on craigslist. Amazon Fire products are so trash, I don't know why I bought this. An iPad 2 (7 years old) runs the game better than the newest Fire HD 10 (1 year old). Yes, I understand I only paid $150 for it, but I was optimistic about it.
I'll probably just end up spending more and get the newest iPad for $330.
Click to expand...
Click to collapse
Hello jrossh21 --- I read your original post twice. I realized why nobody responded with the exact solution. Time has passed and you've probably bought your son the perfect tablet for gaming. BUT, I wonder if your wife or son can spot the reason nobody has responded. Ask wife and kid(s) and make sure they read your original post ..... maybe they will have to read your original post two or more times, but I know they just might notice the reason. Anyway, do your best and make sure they read this posting from me so they know this exercise is real. Take a few days and reply to let me know if they get it or not.....we are trying to find out if anyone in your family can spot the reason nobody has responded with the exact solution. Hint: it has to do with your original post...trust me on that.
@KingRoseNot Do you have friends in real life? Read your post and maybe you will understand why I ask. Please tell me what it's like to live a lonely existence without any human contact. I really want to know. You must be a master at alienating yourself from other people. Just read your post and you will see what I mean. No, read it slowly. Maybe then you might be able to possible grasp the subtle intricacies of my question. Probably not, but maybe.
convit161 said:
we cannot unlock Bootloader right now, so we cannot install custom ROM on Fire HD 10 right now, one thing you can do is root the device and disable amazon apps to make it runs better
https://forum.xda-developers.com/hd8-hd10/general/tut-fire-hd-10-7th-gen-2017-root-box-t3726443
Click to expand...
Click to collapse
Can you unlock and root your Fire HD 10 using the exploit package amonet-suez
This link: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
Same, I have a fire tablet 5th gen with fire os 5.6.8.0 and trying to root without pc but no luck in finding tutorials, please help me to downgrade fire os 5.6.8.0 to 5.3.0
I was following the root method for tablet 8" but it was an older version. Now I can no longer boot up the tablet since I flashed the wrong boot.img. I unlocked the bootloader but that's the furthest I can get.
Anyone have any luck rooting on these 100003561 Onn 8" Tablet Pro Android 10 devices? Maybe post a guide for beginners to show what is possible?
No luck here either
Andenthu said:
Anyone have any luck rooting on these 100003561 Onn 8" Tablet Pro Android 10 devices? Maybe post a guide for beginners to show what is possible?
Click to expand...
Click to collapse
I tried it last night, and got the code orange loop. I'm going to try to restore factory and go another route
I have that model, too. Doesn't come pre-loaded with junk, fortunately -- mostly I just want to remap the stupid dedicated Walmart app button. It's a present for an elderly relatively that lives without a car in a town nowhere near any Walmart business -- never used a smart phone before (and I'm guessing even though she's pushing 90 she's never been in a Walmart).
Kind of annoying they put the Walmart button in the very location you normally press to see which tasks are running.
PS: I've only had it for less than a day, haven't played with it much, but so far, it's much nicer than I was expecting, at least in terms of how the build quality "feels."
It's really not a bad cheapie choice if you prefer to avoid the Amazon ecosystem.