Related
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
Click to expand...
Click to collapse
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Click to expand...
Click to collapse
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
buhohitr said:
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
Click to expand...
Click to collapse
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
deV14nt said:
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
Click to expand...
Click to collapse
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
wha2do said:
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
Click to expand...
Click to collapse
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
wha2do said:
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
Click to expand...
Click to collapse
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
22sl22 said:
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks - that was the post had been reading through - appears after the kitkat OTA, latest posts mentioned problems with SU when running the original CF-AUTO Root method (flashing autorootp600mj4.tar.md5). Wondering if flashing the "newer" CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5
would be best. At this point feel confident either way!
deV14nt said:
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
Click to expand...
Click to collapse
Yep, will be downloading TWRP v2.6.3.3 and flash it and SuperSU after rooting. After rooting, will be curious to see where I sit with superuser (sorry, reading the latest posts kind of muddy whether a SU app is already installed or not, lol)...
Thanks everyone for all the great input & help!!
I bought a Fire TV from Staples and I'm hoping it will be rootable. Assuming it is, I was planning to do the following:
Block the updates at the router.
Plug in the Fire TV and follow the rooting procedure (using Towelroot) without upgrading the firmware
Install ClockworkMod
Install latest Prerooted Stock Image.
The rooting procedure has steps for getting the firmware to the latest rootable version prior to rooting, but rather than go through all that, I'd rather get root ASAP and then flash a pre-rooted firmware using ClockworkMod.
I've got lots of experience rooting and flashing phones and tablets, so I don't think installing a custom recovery will be an issue for me. Is this a good plan?
Once you are rooted and have su installed, you should follow this guide: http://www.aftvnews.com/how-to-block-ota-update-for-amazon-fire-tv-and-keep-root-access/.
If you haven't already done so, you can't go wrong browsing thru all of the aftvnews.com guides.
jmerrilljr2 said:
Once you are rooted and have su installed, you should follow this guide: http://www.aftvnews.com/how-to-block-ota-update-for-amazon-fire-tv-and-keep-root-access/.
If you haven't already done so, you can't go wrong browsing thru all of the aftvnews.com guides.
Click to expand...
Click to collapse
Yes, disabling the service is something to do, but I was assuming the Prerooted Stock Images that I would be flashing would already have that disabled.
ASFAIK, rbox recommends doing this.
jmerrilljr2 said:
ASFAIK, rbox recommends doing this.
Click to expand...
Click to collapse
depending on the version you get and hopefully its rootable. I would do this.
Enable adb, install towelroot, disable updates and if you are on the initial version of the firmware where the menu items fit in one screen, then you are good to go. else downgrade first.
for safety disable the amazon updates through su everytime you are on new firmware.
then go up to the last version before unlocked firmware of rbox
then unlock and go to the bootloader menu along with the latest firmware
block updates and you are golden. latest and perfectly rooted.
For anyone else reading this thread, rbox made a walkthrough guide: http://www.aftvnews.com/start/
Just follow that. It does what I was planning on doing.
Hi
I have a 2015 Shield (non pro) currently running rooted 5.2.0. I am looking to update it with the latest 8.0.1 dev image to keep root. Is there any precautions or extra steps I need to take over what is in the instructions in the download centre. From what I have read I will need to ADB sideload Magisk to get full root access after installing the dev image.
you'll need to patch the boot.img in magisk canary and then flash it
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
Do I need to unroot or factory reset the rooted 5.2.0 before flashing 8.0.1. Is there any benefit in flashing the dev image rather than the factory image before flashing the patched boot.img.
You should update the firmware OTA. Because you'll flash the OTA you'll need to patch then flash the dev image or this root boot image: https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
But do I need to unroot etc to do an OTA.
g1dtf said:
But do I need to unroot etc to do an OTA.
Click to expand...
Click to collapse
yes unroot will happen automatically when you install the OTA. if you know how to use adb and follow my steps it's not a big deal though you can get it back quickly
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
g1dtf said:
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
Click to expand...
Click to collapse
yes correct you need to do it incrementally--it's totally worth it Nvidia has done some great upgrades!
Got it up to 8.0.0 installing the OTA's. However the next OTA offered is 8.0.2 rather than 8.0.1 which as far as I know has no root options yet as the 8.0.2 images have not been released by NV.
yes but you don't need dev images to root, you can just patch this boot.img and it should give you root (as long as you install the latest Magisk canary and then upgrade through that)
https://forum.xda-developers.com/sh...l-2-22-ghz-t3943079/post81708169#post81708169
False double post please ignore.
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
g1dtf said:
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
Click to expand...
Click to collapse
Just boot into twrp using this https://drive.google.com/file/d/1934405D1S0lv52jZMqS-Zny62RIzGWSi/view
Then flash magisk canary in there, and you are done
Thanks! Flashed the latest canary and now rooted on 8.0.2.
I've done a search on the forum and can't find the exact answer I'm after. I have a Fire TV2 box that I would prefer to keep on Fire OS 5.0.5. TWRP Recovery is currently on 3.0.0-4 and I would like to update it to the latest version without installing the latest Fire OS pre-rooted ROM. There are many guides on the internet for updating TWRP on Android phone and I wonder if it is the same approach for Fire TV (and I can just follow one of those)? Thanks for all help.
Leedsgreen said:
IThere are many guides on the internet for updating TWRP on Android phone and I wonder if it is the same approach for Fire TV (and I can just follow one of those)? Thanks for all help.
Click to expand...
Click to collapse
Nope, since TWRP runs from a ram disk, not from the recovery partition..
OK. So other than installing latest pre-rooted ROM is there anyway to update TWRP recovery (& stay on the Fire OS I’m currently on)? Thanks.
Hello,
I rooted my FireTV Stick 4k (mantis) some time ago with fireISO 1.0, kamakiri-mantis 1.2 (I believe) and it worked just fine until recently. Now it often crashes, is slow or I have to reboot several times before I can use it.
The firmware version is 6.2.6.8, Magisk 20.1, Magisk Manager 7.4.0, TWRP 3.3.1-0. So everything seems a bit outdated and I hope that an update will solve the problems mentioned.
I found several threads on different websites but they are either referring to other devices, software versions or starting situations.
Can someone please show me where I can find a comprehensive guide or tell me how to do the updates, where to find the latest firmware and software versions and what to consider in general (e.g. I never had to use TWRP after the rooting and now, when I cancel the rebooting on the stick and start TWRP it asks me if I want to leave the system partition read only or allow changes. No idea.)?
Thanks for your help!
There are some threads, guides and youtube videos on how to install roms and how to interact with twrp...
but if you want to keep your device 'kamakiri vulnerable via shorting' then you want only install this prerooted rom to your stick:
Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might. First, you must be unlocked. You can follow the instructions...
forum.xda-developers.com
Make sure that you flash July 17, 2021 - 6.2.8.1.r2 first, then 6.2.8.1 r3 if you like. Don't forget to disable the OTA updates.
Sus_i said:
There are some threads, guides and youtube videos on how to install roms and how to interact with twrp...
but if you want to keep your device 'kamakiri vulnerable via shorting' then you want only install this prerooted rom to your stick:
Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might. First, you must be unlocked. You can follow the instructions...
forum.xda-developers.com
Make sure that you flash July 17, 2021 - 6.2.8.1.r2 first, then 6.2.8.1 r3 if you like. Don't forget to disable the OTA updates.
Click to expand...
Click to collapse
Thanks for the link. I've already found this thread but since I don't know what "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." means I was hoping that I can flash a stock rom instead of a pre-rooted so that I don't have to be careful about that blow efuse thingy.
Btw, what means keep your device "kamakiri vulnerable via shorting"?
Droidknot said:
Thanks for the link. I've already found this thread but since I don't know what "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." means I was hoping that I can flash a stock rom instead of a pre-rooted so that I don't have to be careful about that blow efuse thingy.
Click to expand...
Click to collapse
You can flash stock roms, easiest is to enable updates and the OTA app will install the latest...
But netflix and prime video etc won't play stuff, until you flash an updated trustzone (TZ image) to your stick (which the 6281r2 prerooted does for you).
Together with this updated TZ image, every stock rom above 6.2.8.0 burns an efuse in the SOC, which will prevent/patch the kamakiri shorting method, i.e. unbricking via short is gone forever.
Droidknot said:
Btw, what means keep your device "kamakiri vulnerable via shorting"?
Click to expand...
Click to collapse
You may know how you did the unlock in the first place, open and short a special point...!?
PS: The prerooted was put together because the blow efuse thingy, i.e. efuse burning is disabled in the prerooted...
Sus_i said:
You can flash stock roms, easiest is to enable updates and the OTA app will install the latest...
But netflix and prime video etc won't play stuff, until you flash an updated trustzone (TZ image) to your stick (which the 6281r2 prerooted does for you).
Together with this updated TZ image, every stock rom above 6.2.8.0 burns an efuse in the SOC, which will prevent/patch the kamakiri shorting method, i.e. unbricking via short is gone forever.
Click to expand...
Click to collapse
Thanks for the explainations, that makes it clearer. Isn't it possible to manually flash a specific firmware version (which doesn't patch the kamakiri shorting method) with TWRP? E.g. to download a stock rom zip file and then flash it with TWRP?
Sus_i said:
You may know how you did the unlock in the first place, open and short a special point...!?
PS: The prerooted was put together because the blow efuse thingy, i.e. efuse burning is disabled in the prerooted...
Click to expand...
Click to collapse
Yes, I know the shorting method but I didn't know that later firmware versions make this method impossible. The warning "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." made me believe that it is basically possible to (manually) flash a specific stock rom, e.g. 6.2.7.1.
After flashing the pre-rooted rom will it still be possible to OTA update to the latest version and bring the device back to stock mode?
If not, I would prefer to update Magisk, Magisk Manager and TWRP (if this can be updated separately) first and to check if this already solves the issues. If it's always possible to go back to stock mode, flashing the pre-rooted rom would maybe be the easier way.
Do I have to set up TWRP as read only or read write on system partition? I ask because some sources say this, other say that.
Droidknot said:
Thanks for the explainations, that makes it clearer. Isn't it possible to manually flash a specific firmware version (which doesn't patch the kamakiri shorting method) with TWRP? E.g. to download a stock rom zip file and then flash it with TWRP?
Click to expand...
Click to collapse
Ofc thats possible, but as I said DRM is broken because the new OS needs a new TZ
Droidknot said:
After flashing the pre-rooted rom will it still be possible to OTA update to the latest version and bring the device back to stock mode?
Click to expand...
Click to collapse
It's possible, but all new Stock will burn the efuse by default, if the new TZ is also there.
Easiest is if you just flash the prerooted 6281r2 (which updates the TZ so no DRM issues for you), then the 6281r3, done. Make sure that updates are disabled and thats it. Watch out if your issues are gone.
If you somehow/sometimes want the stick at a higher stock OS than 6281, @SweenWolf released a patch, which deletes the efuse burner for you... needs to be flashed just after the stock rom.