Related
Hi all,
I normally live over on the Xperia Arc forum but I have been trying to root my mums Kindle.
Last time I looked it was on 10.2.4 which, as far as I have read, is rootable.
However last night I checked the version again just before I commenced rooting and it was on 10.2.5!
I cant seem to find any reference of .5 anywhere.
Even on amazons website the latest update says 10.2.4
I tried the root methods but it didnt work unfortunately...
Any ideas? Anyone else been updated to .5 and successfully rooted?
yo-meister said:
Hi all,
I normally live over on the Xperia Arc forum but I have been trying to root my mums Kindle.
Last time I looked it was on 10.2.4 which, as far as I have read, is rootable.
However last night I checked the version again just before I commenced rooting and it was on 10.2.5!
I cant seem to find any reference of .5 anywhere.
Even on amazons website the latest update says 10.2.4
I tried the root methods but it didnt work unfortunately...
Any ideas? Anyone else been updated to .5 and successfully rooted?
Click to expand...
Click to collapse
Unlucky mate. Ur the first I've heard having .5 kf. Did u try over HD forum. More devas over there or the general chat forum
Sent from my Amazon Kindle Fire2 using xda app-developers app
willieboya said:
Unlucky mate. Ur the first I've heard having .5 kf. Did u try over HD forum. More devas over there or the general chat forum
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
Really annoying ha
I literally cannot find a reference to it, and dont understand why the amazon website hasnt even documented it!
I would moan about the horrible launcher...but that seems to have been done many times lol
I will check back in a few days maybe, to see if others have been cursed with this.
yo-meister said:
Really annoying ha
I literally cannot find a reference to it, and dont understand why the amazon website hasnt even documented it!
I would moan about the horrible launcher...but that seems to have been done many times lol
I will check back in a few days maybe, to see if others have been cursed with this.
Click to expand...
Click to collapse
Does the root with restore method for 10.2.4 work for this?
fmkilo said:
Does the root with restore method for 10.2.4 work for this?
Click to expand...
Click to collapse
Already tried binarys root with restore and qemu
Both failed unfortunately
Going to have to wait i suppose!
yo-meister said:
Already tried binarys root with restore and qemu
Both failed unfortunately
Going to have to wait i suppose!
Click to expand...
Click to collapse
You could definitely restore to a rooted 10.2.4 if you had a fastboot cable...
This works for 10.2.4
I found the solution! If you try and install superuser.apk directly by copying over to downloads and clicking on it, it works. Then simply grant ES File Explorer su permissions and click to mount the file system.
Idk why it worked, but if it doesn't, try using Root_with_Restore_by_Bin4ry_v1**8 & QemuRoot combination. When you get permission denied, make sure you run it again and press 3 to jump steps, but make sure you run step 4 or your device will remain sluggish
If that doesn't work try this: Rooted 10.2.4
Hopefully after running the tf101 file and qemu you can manually install superuser.apk from the sdcard. If it worked make sure you mount the filesystem with ES, because tthe shell wont work. Next, make sure to rename /system/etc/security/otacerts.****(zip) so that the next software update wont deroot you.
Last week my kindle fire 2 randomly update to 10.2.5 after I had rooted it with root many android, by bin4ry and qemu root.
I decided I would try the root many android method again last night to try and re-root the device and it worked perfectly, installed rootchecker, definitely had root access. Left the kindle on overnight to charge using a wall socket.
Woke up this morning and somehow my kindle is now 10.2.6.. I even renamed otacerts.zip to something else and it still managed to update itself to a version which doesn't even exist as far as I am aware.
Am I missing something here? Does anyone have any input?
Wilkinsss said:
Last week my kindle fire 2 randomly update to 10.2.5 after I had rooted it with root many android, by bin4ry and qemu root.
I decided I would try the root many android method again last night to try and re-root the device and it worked perfectly, installed rootchecker, definitely had root access. Left the kindle on overnight to charge using a wall socket.
Woke up this morning and somehow my kindle is now 10.2.6.. I even renamed otacerts.zip to something else and it still managed to update itself to a version which doesn't even exist as far as I am aware.
Am I missing something here? Does anyone have any input?
Click to expand...
Click to collapse
Amazon will update a select few device with the newest version before they actually release to everyone. You should REALLY thank amazon for making you one of the new guinea pigs haha. Also renaming otacerts.zip doesn't seem to work with the newer software versions. I've disabled all ota portions of silk using Rom Tollbox, I'll let you know on the next update. Though I'm using the 8.9 but should be the same
onemeila said:
Amazon will update a select few device with the newest version before they actually release to everyone. You should REALLY thank amazon for making you one of the new guinea pigs haha. Also renaming otacerts.zip doesn't seem to work with the newer software versions. I've disabled all ota portions of silk using Rom Tollbox, I'll let you know on the next update. Though I'm using the 8.9 but should be the same
Click to expand...
Click to collapse
I find it hard to believe I've been a guinea pig twice in two weeks haha but I'll take your word for it. Should it be safe to try reroot using the 10.2.4 method on 10.2.6? I assume so but I'm skeptical
Wilkinsss said:
I find it hard to believe I've been a guinea pig twice in two weeks haha but I'll take your word for it. Should it be safe to try reroot using the 10.2.4 method on 10.2.6? I assume so but I'm skeptical
Click to expand...
Click to collapse
I would think its ok. Do you have a backup and factory cable incase?
onemeila said:
I would think its ok. Do you have a backup and factory cable incase?
Click to expand...
Click to collapse
Factory cable is in the post on its way to me now, the root worked fine in 10.2.5 so my assumption would be the same for 10.2.6.
Edit: Since I am a risk-taker, see:foolish, I just decided to go ahead and root again with bin4ry's root. All is well and I have root again. I'd very much like it if I didn't have to go through this procedure once again, is there any way I can foolproof my system not to update, since otacerts didn't work last time?
I turned on my kids KFHD today and saw a lock screen ad, which I had eliminated when I rooted the device. I went to titanium backup and, sure enough, no root anymore. Voodoo didnt keep it. I used a method on XDA to root in the first place but IDK if it will still work on 8.3.0 (doubt it) and I dont feel like doing a data wipe right now to find out. Does anyone know to regain root on this version? Its only a few hours old and I havent seen anything about it yet.
ecopunk said:
I turned on my kids KFHD today and saw a lock screen ad, which I had eliminated when I rooted the device. I went to titanium backup and, sure enough, no root anymore. Voodoo didnt keep it. I used a method on XDA to root in the first place but IDK if it will still work on 8.3.0 (doubt it) and I dont feel like doing a data wipe right now to find out. Does anyone know to regain root on this version? Its only a few hours old and I havent seen anything about it yet.
Click to expand...
Click to collapse
I was able to get it re-rooted, but it took two tries before it finally worked.
You can reflash 8.1.4, and then run Chris/Prokennexusa's OTA-Update-Defeat script to kill the update services. My 8.9 survived Amazon's OTA update and remained on 8.1.4, rooted, with Hashcode's bootloader intact. Chris's defeat script works!
Hashcode reviewed the update the and major change was to plug the security hole that allows us to use an alternate bootloader and flash new operating systems.
Nestaron said:
I was able to get it re-rooted, but it took two tries before it finally worked.
Click to expand...
Click to collapse
Using what method? Same as 8.1.4 or something else?
Slimepuppy said:
You can reflash 8.1.4, and then run Chris/Prokennexusa's OTA-Update-Defeat script to kill the update services. My 8.9 survived Amazon's OTA update and remained on 8.1.4, rooted, with Hashcode's bootloader intact. Chris's defeat script works!
Hashcode reviewed the update the and major change was to plug the security hole that allows us to use an alternate bootloader and flash new operating systems.
Click to expand...
Click to collapse
Thanks, might have to do that.
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Just saw this. I didn't check the version on mine until now. It's on 8.3, and has been rooted since I brought it home on Wednesday. I did it Wednesday night and if it updates overnight it kept root.
If not, it was on 8.3 the whole time.
gunnyman said:
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Click to expand...
Click to collapse
gsu_golfer said:
Just saw this. I didn't check the version on mine until now. It's on 8.3, and has been rooted since I brought it home on Wednesday. I did it Wednesday night and if it updates overnight it kept root.
If not, it was on 8.3 the whole time.
Click to expand...
Click to collapse
Thank you all! I will backup and go again tomorrow or the next dayand post the results
gunnyman said:
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Click to expand...
Click to collapse
+1 same here
bighead2k said:
+1 same here
Click to expand...
Click to collapse
Mine has not worked - I am using bin4ry tool v26. What did you use?
gooseacre said:
Mine has not worked - I am using bin4ry tool v26. What did you use?
Click to expand...
Click to collapse
I used bin4ry tool v25, It wasn't rooted, but I can install playstore, go laucher!
Went out of town and forgot to post back here. I did re-root with the original method and it DID work! I backed it up but I was surprised to find that all my data, apps, even passwords, etc were all still there after re-rooting (even after the supposed data restore) and were all working but I had regained root! The only thing missing were the kindle Books selections. Not a bad tradeoff!
gooseacre said:
Mine has not worked - I am using bin4ry tool v26. What did you use?
Click to expand...
Click to collapse
haovpi said:
I used bin4ry tool v25, It wasn't rooted, but I can install playstore, go laucher!
Click to expand...
Click to collapse
This is what I used on both firmware versions
http://forum.xda-developers.com/showthread.php?t=1886460
no such thing as a root keeper
Not f'realz anyways. I'm on 8.3.1; gotten used to rooting the same way, THAT is nice. I initially had to fiddle w/ADB, windows 8 doesn't initially allow unsigned drivers. There's a proceedure for that. After that was fixed, the b1nary root works like a boss ...
The kindle fire first aid works well for market installation (make sure to install busy box first, b1nary root didn't, and that's easy). OTA blocking works well, I forget what I used. My update to 8.3.1 was intentional
Seems a more stable update. In fact, all the updates seem worth-while: google maps didn't gps track w/1st version, with silk installed couldn't watch amazon vod. A lot of quirks seem to be fixed, google play store and amazon app store seem to be playing well together.
---------- Post added at 08:57 AM ---------- Previous post was at 08:47 AM ----------
ecopunk said:
Went out of town and forgot to post back here. I did re-root with the original method and it DID work! I backed it up but I was surprised to find that all my data, apps, even passwords, etc were all still there after re-rooting (even after the supposed data restore) and were all working but I had regained root! The only thing missing were the kindle Books selections. Not a bad tradeoff!
Click to expand...
Click to collapse
Hey, fyi when you reroot, go into app settings after and clear data on the Amazon apps like Kindle, Silk, or VOD. My stuff doesn't show up even on the "cloud" if I don't do that. You'll have to redownload media, so that might stink. Not really, imo.
So, we all just got the fresh root. Now that I'm rooted and I want to install CWM, do we have the ability to downgrade like the older updates?
lowridincrew said:
So, we all just got the fresh root. Now that I'm rooted and I want to install CWM, do we have the ability to downgrade like the older updates?
Click to expand...
Click to collapse
No. You can not not use CWM if you are on FireOS5 and I would strongly recommend not attempting to downgrade.
rbox said:
No. You can not not use CWM if you are on FireOS5 and I would strongly recommend not attempting to downgrade.
Click to expand...
Click to collapse
Thanks for the reply. What could I do from here? Playstore? Leanback Launcher?
lowridincrew said:
Thanks for the reply. What could I do from here? Playstore? Leanback Launcher?
Click to expand...
Click to collapse
Wait for me to release TWRP and prerooted roms.
rbox said:
Wait for me to release TWRP and prerooted roms.
Click to expand...
Click to collapse
Oooh ok. Waiting lol
rbox said:
Wait for me to release TWRP and prerooted roms.
Click to expand...
Click to collapse
Hi rbox,
would you be supporting 1st gen FireStick as well? - if TWRP is even possible to be install on these units. Thank you
bula1ca said:
Hi rbox,
would you be supporting 1st gen FireStick as well? - if TWRP is even possible to be install on these units. Thank you
Click to expand...
Click to collapse
That is the plan. Thanks to @AFTVnews.com and some wonderful people on the website, I picked up a stick last night. After some preliminary examination, I'm pretty sure it will work. I am still waiting on the update url for 3.x to 5.0.5 or beta to 5.0.5 though.
rbox said:
That is the plan. Thanks to @AFTVnews.com and some wonderful people on the website, I picked up a stick last night. After some preliminary examination, I'm pretty sure it will work. I am still waiting on the update url for 3.x to 5.0.5 or beta to 5.0.5 though.
Click to expand...
Click to collapse
I know I ask a lot (so feel free to not awnser), but do you have any idea how long until release? my actual install is partially broken and I'd like to know if it's worth resetting now or just wait for your releases
EDIT : I mean for the Fire TV 1 box, not the stick.
rbox said:
That is the plan. Thanks to @AFTVnews.com and some wonderful people on the website, I picked up a stick last night. After some preliminary examination, I'm pretty sure it will work. I am still waiting on the update url for 3.x to 5.0.5 or beta to 5.0.5 though.
Click to expand...
Click to collapse
has your stick already come with the update to 5.0.5?
if not, you can capture it via adb logcat?
El_Nino9 said:
has your stick already come with the update to 5.0.5?
if not, you can capture it via adb logcat?
Click to expand...
Click to collapse
Mine update 4 hours after I un-blocked router. Unfortunately I did not think about it at the moment
desmopro said:
I know I ask a lot (so feel free to not awnser), but do you have any idea how long until release? my actual install is partially broken and I'd like to know if it's worth resetting now or just wait for your releases
EDIT : I mean for the Fire TV 1 box, not the stick.
Click to expand...
Click to collapse
I was doing some testing on Sunday and it all looked good, but that was for unlocked boxes only. I need to fix some things to work with the locked bootloader. I plan on releasing both at the same time.
El_Nino9 said:
has your stick already come with the update to 5.0.5?
if not, you can capture it via adb logcat?
Click to expand...
Click to collapse
I got the newer one that already had 5.0.3 or something on it. I have all the 5 to 5 URLs. I need 3 to 5 or beta to 5.
bula1ca said:
Mine update 4 hours after I un-blocked router. Unfortunately I did not think about it at the moment
Click to expand...
Click to collapse
similar situation as you, it came to mind afterwards that too when i was already rooted.
to be honest i like the new UI better than the old. especially seeing my apps that i've side loaded there on the main page
I do as well however unfortunately broke some apps as well....hopefully these will be fixed sooner or later.
desmopro said:
I know I ask a lot (so feel free to not awnser), but do you have any idea how long until release? my actual install is partially broken and I'd like to know if it's worth resetting now or just wait for your releases
EDIT : I mean for the Fire TV 1 box, not the stick.
Click to expand...
Click to collapse
Dude, faux pas
rbox said:
I was doing some testing on Sunday and it all looked good, but that was for unlocked boxes only. I need to fix some things to work with the locked bootloader. I plan on releasing both at the same time.
I got the newer one that already had 5.0.3 or something on it. I have all the 5 to 5 URLs. I need 3 to 5 or beta to 5.
Click to expand...
Click to collapse
1) firetv 1, what will the consequences be if you were to dd the bootloader and other partitions of an unlocked system to one of a locked device fire tv1
2)firetv stick, if i do a system dump using dd, would that be useful? i have kingroot and busybox from playstore only installed on system partition.
El_Nino9 said:
1) firetv 1, what will the consequences be if you were to dd the bootloader and other partitions of an unlocked system to one of a locked device fire tv1
2)firetv stick, if i do a system dump using dd, would that be useful? i have kingroot and busybox from playstore only installed on system partition.
Click to expand...
Click to collapse
1) you'll brick it hard
2) I actually have gotten all the URLs I need. Thanks though.
my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:
I do not want to give you a hard time but why you guys do not read before doing it. There are few post here mentioning that boxes get bricked if you use supersu-me. Can you connect to it through adb? The only way to get it back if somehow rbox will release an unbrick image as he did for firetv 2
sardiswolf said:
my first gen fire tv box, I root it by kingroot, everything works fine. but after I use super me to get super su, resatart. then the box stacks at amazon splash start screen. Anybody can give any idea how to hardware reset? help :crying:
Click to expand...
Click to collapse
Same thing happened to me with fire stick but not stuck on amazon logo but fire TV stick logo.
Sent from my iPhone using Tapatalk
READ ME!
If you read the Kingroot thread on this forum, located here. You will find that the authors of Kingroot have taken exception to the author of SuperSu and anyone else who uses it in their programs to replace Kinguser, because of the claims of conflicting programs and/or malicious coding. Kingroot authors counter claim that programs like Super-Sume improperly remove Kingroot leaving orphaned files which may cause problems. But the author of Super-Sume says his program will not brick your device.
Most people have had no luck installing SuperSu on their devices after being rooted by Kingroot even though Kingroot authors claim they could co-exist on the same device, because Kingroot has added a restriction regarding SuperSu. So consequently those who have gotten SuperSu installed on their Kingroot rooted devices have ended up with problems.
Don't install random stuff via root without custom recovery! Its just as effective as a pull and pray people. You need some protection.
Just be patient!!
hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.
sardiswolf said:
hope rbox will bring out some unbrick rom. is any other way to do the hardware reset. open the box and short somewhere? Please give me a hint.
Click to expand...
Click to collapse
There's really nothing you can do if you have a locked firetv1 box that is bricked.
rbox said:
There's really nothing you can do if you have a locked firetv1 box that is bricked.
Click to expand...
Click to collapse
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.
sardiswolf said:
even it was rooted and I put super su there. I remenber can short the the chip somewhere to get the recovery mode.
Click to expand...
Click to collapse
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.
rbox said:
There's many ways to force it into recovery, but there's not much you can do from there.
You could follow the hardware rooting instructions to get access to the flash chip, and then rewrite the system.img... but that's about it.
Click to expand...
Click to collapse
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.
sardiswolf said:
do you have thr 5.0.5 system.img ? since it is bricked, may try, otherwise throw in the garbage.
Click to expand...
Click to collapse
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.
rbox said:
@AFTVnews.com has posted the update url for 5.0.5 for firetv1. You just need to run sdat2img on it to get the full system.img.
Click to expand...
Click to collapse
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks
sardiswolf said:
good to hear that, but where is the link, and after I get that img file, what do I need to do. Thanks
Click to expand...
Click to collapse
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.
rbox said:
Can't really walk you through this. But you could wait until I post the prerooted rom for firetv1. And extract the system.img from that.
Click to expand...
Click to collapse
Thanks, I will wait for your rom and use aftvnew post the unbrick way to do factory reset.
looks like the usb keyboard could not make it get into factory reset area.
Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?
mrchrister said:
Same problem here. used SuperSU me and now the box is stuck on Firetv logo.. It looks like emmc soldering is the only way which is pretty scary and possibly not worth the hassle... Did you get any further with recovering?
Click to expand...
Click to collapse
no way to solve it. bought another brand tv box.
I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk
mrchrister said:
I will try a emmc hardware root to revive the box. I hope rbox will release a bootloader for firetv gen 1 soon
Sent from my X98 Air III(M5C5) using Tapatalk
Click to expand...
Click to collapse
If your bootloader isn't already unlocked and you bricked a FireTV 1, there isn't anything that can be done from a software perspective.
i was hoping to dd system.img through hardware emmc soldering. do you think this could work to revive it?
Sent from my iPhone using Tapatalk
I just bought this tablet on black Friday recently and I was wondering if the rapid root method noted on this other thread would work? I don't like amazon's bloatware on it.
Rapid Temporary Root for HD 8 & HD 10
Software root method for Mediatek MT816x, MT817x and MT67xx! A tool that gives you a temporary root shell with Selinux permissive to do with as you please STATUS Confirmed Working Fire HD 8 8th gen (2018) (thanks xyz`) -- up to Fire OS 6.3.0.1...
forum.xda-developers.com
dizzymon said:
I just bought this tablet on black Friday recently and I was wondering if the rapid root method noted on this other thread would work? I don't like amazon's bloatware on it.
Rapid Temporary Root for HD 8 & HD 10
Software root method for Mediatek MT816x, MT817x and MT67xx! A tool that gives you a temporary root shell with Selinux permissive to do with as you please STATUS Confirmed Working Fire HD 8 8th gen (2018) (thanks xyz`) -- up to Fire OS 6.3.0.1...
forum.xda-developers.com
Click to expand...
Click to collapse
Your own post says "up to ... 6.3.0.1". Any recentl tablet is going to be above that, so, no it won't work. The best way to debloat is with the "Toolbox"
I used toolbox but I can't seem to get other web browsers to install. Any ideas?
I got one when amazon was doing there amazon day for cheap, too bad it comes with newestest firmware. I haven't used it yet since it can't be rooted or roms yet. I hope someone comes up with something soon
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
dizzymon said:
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
Click to expand...
Click to collapse
I don't have an issue. Chrome is working fine on my HD 10 2019. OS ver 7.3.1.6
dizzymon said:
Toolbox got rid of all the amazon things from the UI but the browser remains an issue.
Click to expand...
Click to collapse
I was able to install Vivaldi, from the Google Play Store.
Droid4200 said:
I got one when amazon was doing there amazon day for cheap, too bad it comes with newestest firmware. I haven't used it yet since it can't be rooted or roms yet. I hope someone comes up with something soon
Click to expand...
Click to collapse
I was just thinking , has anyone tried to open one of these and serial/UART flash to downgrade firmware to a rootable firmware?
Droid4200 said:
I was just thinking , has anyone tried to open one of these and serial/UART flash to downgrade firmware to a rootable firmware?
Click to expand...
Click to collapse
I am able to boot into the bootrom through the other exploits on fire devices, the bootrom is how every fire device has been unlocked in the last 2years. No one really has put much effort into unlocking it though. Running the exploit and plugging in to PC during the "waiting for bootrom" would boot it right into the bootrom (lsusb detects mediatek phone), but that is as far as i got as the exploit would have to be set up i believe similar to the firestick4k exploit. I have 2 rooted and one that is not rooted. The mtk-su exploit was blocked on first update. But the mtk-su is a temp root and you can not change the system folder. i havent checked any device higher than 6.3.1.2, I am not sure if you can still boot into it. Either way, it seems that the bootrom for this device was not blocked on the firmware. I believe there is a unlock option here, but i am not the one to figure it out...
Michajin said:
... i havent checked any device higher than 6.3.1.2, I am not sure if you can still boot into it. Either way, it seems that the bootrom for this device was not blocked on the firmware. I believe there is a unlock option here, but i am not the one to figure it out...
Click to expand...
Click to collapse
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
i dont know if anyone has tried to check to see if the bootrom is available on newer OS. But no one has written code to unlock if there is a bootrom exploit. I will update one this week and see if it will still boot into the bootrom. The mtk-su was just a temp root. The bootrom exploit has potential for full unlock, root, and TWRP... Has anyone try to access it on 7.3.1.6?
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
Looks like they killed the bootrom access since.. i don't know what version killed it.. I am on 6.3.1.7 now. I can only see the preloader now...
lewmur said:
That says it all. The current OS version are all higher than that and that no longer works. So far, no one has succeeded in rooting the current OS and you can't downgrade.
Click to expand...
Click to collapse
@k4y0z has done it again! come join the party @ https://forum.xda-developers.com/t/...k-brainstorming.3979343/page-28#post-84499719
Michajin said:
Looks like they killed the bootrom access since.. i don't know what version killed it.. I am on 6.3.1.7 now. I can only see the preloader now...
Click to expand...
Click to collapse
7.3.1.1 -> 7.3.1.0 confirmed. need more ppl 2 test out other fw rev.
newnewcomputer said:
@k4y0z has done it again! come join the party @ https://forum.xda-developers.com/t/...k-brainstorming.3979343/page-28#post-84499719
7.3.1.1 -> 7.3.1.0 confirmed. need more ppl 2 test out other fw rev.
Click to expand...
Click to collapse
i can give it a shot this weekend if i have a device that is on 7.3.1.1. But so few people got access to root or 7.3.1.1, unlocking may be moot if no developers have a want to make a rom. On that note, there should be a shorting method to access the bootrom. Amazon disabled the volume/power on trick somewhere between 7.3.1.2 and 7.3.1.7, not sure what version disabled the easy way. so what all does this do? just downgrade for accessibility to root? What do i need to do this, do i need access to bootrom to downgrade? Trying to read through the posts i got a little lost. I have 3 Mavericks and one is rooted. What would you like me to try, can you give me a step by step. Guess i am asking what rom are you looking for to attempt a downgrade from ? Let me know i will give it a shot, i just have my mavericks in a drawer right now...
Michajin said:
... so what all does this do? just downgrade for accessibility to root? What do i need to do this, do i need access to bootrom to downgrade? Trying to read through the posts i got a little lost. I have 3 Mavericks and one is rooted. What would you like me to try, can you give me a step by step. Guess i am asking what rom are you looking for to attempt a downgrade from ? Let me know i will give it a shot, i just have my mavericks in a drawer right now...
Click to expand...
Click to collapse
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
newnewcomputer said:
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
Click to expand...
Click to collapse
Do you need access to the bootrom to use this? If someone can find access to the bootrom on a updated rom this exploit has a further chance to develop into a custom rom. I suspect the old shorting method should be possible, but i have no idea where to look on the board. I have had it apart before but didn't see anything standing out... but anyways i am charging up my mavericks to see what i have, i know i have a 7.3.1.0, a 7.3.1.1 and a 7.3.1.7. So to be clear, boot into bootrom (volume down and plug in) then run the bypass and rollback? I will test the 7.3.1.1 since i know this one is more likely to succeed
Michajin said:
Do you need access to the bootrom to use this? If someone can find access to the bootrom on a updated rom this exploit has a further chance to develop into a custom rom. I suspect the old shorting method should be possible, but i have no idea where to look on the board. I have had it apart before but didn't see anything standing out... but anyways i am charging up my mavericks to see what i have, i know i have a 7.3.1.0, a 7.3.1.1 and a 7.3.1.7. So to be clear, boot into bootrom (volume down and plug in) then run the bypass and rollback? I will test the 7.3.1.1 since i know this one is more likely to succeed
Click to expand...
Click to collapse
Yeah there was a successful downgrade from 7.3.1.1 already, it has the same lk/pl as 7.3.1.0 but I haven't been able to get into the bootrom on 7.3.1.2, might need to look into shorting a pin.
I think bootrom through the volume button was killed before 7.3.1.7 though
I can confirm bootrom through the volume button on v7.3.1.7 is not working.
newnewcomputer said:
all mine are on 7.3.1.0 so i havent gone thro' the procedure myself. its early n only got 1 confirmed successful case so far (the hack was just put together n tested last few days).
@k4y0z thinks it should work on fw rev. newer than 7.3.1.1. first is to run the bypass utility; then the rollback. if it works out, ur tab will now be running 7.3.1.0 which allows the mtk-su root.
looks like someone has just tried n run into a problem...will need to see how it works out in that thread. good luck!
Click to expand...
Click to collapse
Do i need to run the bypass utility in linux? I am not familiar with this tool... Have any step by step instructions? i will do my 7311 then i will open my other on 7317 and start looking for a short option (i dont care if i destroy one of these testing, lol). I am going to go deep into it in the morning...
Michajin said:
Do i need to run the bypass utility in linux? I am not familiar with this tool... Have any step by step instructions? i will do my 7311 then i will open my other on 7317 and start looking for a short option (i dont care if i destroy one of these testing, lol). I am going to go deep into it in the morning...
Click to expand...
Click to collapse
@Michajin The bypass-utility will run fine on windows, check the README how to set up python and libusb on windows.
I'm not sure if the kamakiri-RPMB Downgrade will work on windows though.
You can use FireISO for both, it should have everything included.
Steps would be:
Run bypass-utility to disable authentication.
Use SP Flash Tool to flash 7.3.1.0
If it doesn't boot due to anti-rollback, run the kamakiri RPMB-downgrade
As for the shorting, there are some options on the back of the board.
Compare with suez (Fire HD 10 - 2017)