Database Users

Updated to rooted OK4 keeping knox counter at 0

This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.

Thank ya for this post, it has actually been a while since I have updated my phone. I haven't had any issues with any of the apps thus far. It's been a little over 24 hours since I've updated. Also, I think my phone runs a lot smoother with the update than it use to. Also, I don't have any issues with the play store updating. I'll post issues if any occurs.

dave011182 said:
This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Click to expand...
Click to collapse
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?

IMBigWillie said:
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
Click to expand...
Click to collapse
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.

dave011182 said:
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
Click to expand...
Click to collapse
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!

IMBigWillie said:
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
Click to expand...
Click to collapse
You may also want to try using flashfire to create your own stock partitions tar to flash in this process to be sure my file on drive isn't somehow corrupted. If you used it in the first place. Use the flash firmware package option, wait for it to read the file partitions, then the download icon to create your partitions file. Use what's highlighted by default, create your file, and transfer it to your computer. Flash what is selected by default from the tar and reboot into download mode to flash the partitions file just created.
If all you want is stock root and your data works you shouldn't need to flash anything else at that point.

[Guide] New and Easiest method for root ALL Galaxy S5 Mini (G800) on Lollipop 5.1.1

BETA: All this is still in testing!
Jump to:
- ODIN flashable devices
- Fastboot flashable devices
REQUESTS AND DISCUSSION
The central CF-Auto-Root thread can be found here on XDA-Developers.com. Use that thread for requests for new roots and generic discussion. Most device models have their own dedicated threads on XDA, please keep discussion about those specific models in that dedicated thread, and don't litter the central thread with them.
NO REDISTRIBUTION
Please link directly to this page, or use the link you find in the table below.
NO WARRANTY
Use at your own risk, I'm not responsible for bricking your device.
GET THE RIGHT FILE
Make sure you get the correct file. Using the incorrect file may brick your device.
FLASH COUNTER
If your target device has a custom firmware flash counter, CF-Auto-Root will trigger it. If you're lucky, Triangle Away has support for your device and can be used to reset the counter.
KNOX WARRANTY
If you have a KNOX-enabled device, using CF-Auto-Root will trip the KNOX WARRANTY VOID status !
ENCRYPTION
Warning: If your device storage is encrypted, using CF-Auto-Root will wipe your data !
ANDROID VERSION
When newer firmwares are released for a certain device, sometimes that firmware includes new bootloaders that prevent kernels based on the old firmwares from booting. This usually coincides with a transition to a newer Android version. In that case, the CF-Auto-Root for download here may no longer work - flashing or booting might fail. It is too much work for me to keep track of all these firmwares, so if you encounter this issue, it is up to you to submit the recovery.img file from the latest firmware for your device to the CF-Auto-Root thread on XDA-Developers.com.
To be clear, just because you have a newer Android version than listed here, does NOT mean the CF-Auto-Root will not work - there's a good chance that it will!
How 2 falsh it?
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Files 4 rooting!
SM-G800H: https://download.chainfire.eu/524/CF-Root1/CF-Auto-Root-kmini3g-kmini3gxx-smg800h.zip?retrieve_file=1
SM-G800F: https://download.chainfire.eu/523/CF-Root1/CF-Auto-Root-kminilte-kminiltexx-smg800f.zip?retrieve_file=1
SM-G800R4: https://download.chainfire.eu/676/CF-Root1/CF-Auto-Root-kminilteusc-kminilteusc-smg800r4.zip?retrieve_file=1
SM-G800M: https://download.chainfire.eu/525/CF-Root1/CF-Auto-Root-kminilte-kminilteub-smg800m.zip?retrieve_file=1
SM-G800Y: https://download.chainfire.eu/526/CF-Root1/CF-Auto-Root-kminilte-kminiltedv-smg800y.zip?retrieve_file=1
If I helped Don't Forget click on thanks botton. :good: :good:
Source: autoroot.chainfire.eu

Reserved!

Reserved

No superSu Binary.
failed installation.
Brick on G-800M Lollipop.
---------- Post added at 12:32 PM ---------- Previous post was at 12:20 PM ----------
hekintools said:
No superSu Binary.
failed installation.
Brick on G-800M Lollipop.
Click to expand...
Click to collapse
thanks you.
I could already make root

hekintools said:
No superSu Binary.
failed installation.
Brick on G-800M Lollipop.
---------- Post added at 12:32 PM ---------- Previous post was at 12:20 PM ----------
thanks you.
I could already make root
Click to expand...
Click to collapse
It didn't Worked?
<<<<<<<<<Besure you uninstalled the security policy updates>>>>>>
Did you uninstall the security policy and security agent and the knox and knox II and reinstall the supersu to 2.65?
Did your phone soft bricked?

Works for G800H on Lillipop 5.1.1 100% tested
If U do the the ways correctlly.

Hi, all!
In my case, after flash all works fine, after open SuperSU and trying to update the binaries an error message appears. BUT when try to do something as root... works!

pouriasa said:
It didn't Worked?
<<<<<<<<<Besure you uninstalled the security policy updates>>>>>>
Did you uninstall the security policy and security agent and the knox and knox II and reinstall the supersu to 2.65?
Did your phone soft bricked?
Click to expand...
Click to collapse
100% work.
In G800m

pouriasa said:
It didn't Worked?
<<<<<<<<<Besure you uninstalled the security policy updates>>>>>>
Did you uninstall the security policy and security agent and the knox and knox II and reinstall the supersu to 2.65?
Click to expand...
Click to collapse
no, how i can do?

hi i have tested it on g800h and it works just fine.
Root is holding since 2 days and im doing a heavy testing with a lot of applications. I will keep u posted in case anything wrong will happen.
Thank as i was waiting for a new root method since a long time.
Best regards,

SeedViciouZ said:
no, how i can do?
Click to expand...
Click to collapse
Before you root you should factory reset your phone then go to the about phone and click on the system update to register your device.
OR
Go to the application manager and uninstall the security policy update if there is this option.
2-flash the file to your phone (CF-auto root) and (do not connect to the internet) download the uninstaller pro and uninstall knox and knox ll and security policy and security agent now the root is safe.
(If the supersu said: There is no supersu binary flash the cf auto again to uninstall those apps)

SeedViciouZ said:
Hi, all!
In my case, after flash all works fine, after open SuperSU and trying to update the binaries an error message appears. BUT when try to do something as root... works!
Click to expand...
Click to collapse
When it said update the binary click on cancel and go to the supersu setting and click on the reinstall now go and install the supersu 2.65 apk. That's done!

hekintools said:
100% work.
In G800m
Click to expand...
Click to collapse
Thanks for your feedback. :good:

zatrzask said:
hi i have tested it on g800h and it works just fine.
Root is holding since 2 days and im doing a heavy testing with a lot of applications. I will keep u posted in case anything wrong will happen.
Thank as i was waiting for a new root method since a long time.
Best regards,
Click to expand...
Click to collapse
Your Welcome man.
Thanks for your feedback.

I use unbranded Lollipop 5.1..1. on G800F. After flashing root I ended up at bootloop.
Could not get rid of it despite cache wipe/factory reset. Tried 3 times, same result.
Is there a way to get rif of bootloop to have root on G800F?

For g800h files is for 4.4.2 not for 5.1.1, do not flash this files with lollipop you brick phone

kowalwalcz said:
For g800h files is for 4.4.2 not for 5.1.1, do not flash this files with lollipop you brick phone
Click to expand...
Click to collapse
No it works on lp I tested it. And it's impossible to brick your phone.

AT-Mio said:
I use unbranded Lollipop 5.1..1. on G800F. After flashing root I ended up at bootloop.
Could not get rid of it despite cache wipe/factory reset. Tried 3 times, same result.
Is there a way to get rif of bootloop to have root on G800F?
Click to expand...
Click to collapse
U mean U use custome ROM?

pouriasa said:
U mean U use custome ROM?
Click to expand...
Click to collapse
No, I have used original Cyprus ROM and flashed hidden.img following these instructions:
First of all install Samsung usb drivers http://developer.samsung.com/technic...000000117#none (probably dont need if you have kies installed)
Make sure you have SM-G800F, download http://www.sammobile.com/firmwares/d...FVFG1BOL1_CYV/
Extract (unzip) the firmware file
Download Odin v3.10.7 - http://dl.sammobile.com/Odin3_v3.10.7.zip
Extract Odin ZIP file
Open Odin v3.10.7
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
If you have problems with hidden.img during flash, then:
Remove usb cable and battery,
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Add PIT file: https://www.androidfilehost.com/?fid=24369303960685133 (re-partition option will tick automatically, is ok)
Click the start button, sit back and wait few minutes
Done.

pouriasa said:
Before you root you should factory reset your phone then go to the about phone and click on the system update to register your device.
OR
Go to the application manager and uninstall the security policy update if there is this option.
2-flash the file to your phone (CF-auto root) and (do not connect to the internet) download the uninstaller pro and uninstall knox and knox ll and security policy and security agent now the root is safe.
(If the supersu said: There is no supersu binary flash the cf auto again to uninstall those apps)
Click to expand...
Click to collapse
Excuse my delay, after uninstall de security updates, all works fine. :good:

N910TUVS2EPG2 - Caution & Info

Be cautious with the latest N910TUVS2EPG2.
You might not be able to downgrade the bootloader once its updated.
If you look back at the history of builds for the N910T you will see the following:
N910TUV U2 EPE3 = 6.0.1
N910TUV U2 DOK2 = 5.1.1
N910TUV U1 COG2 = 5.0.2
Pay attention to the U1 & U2 numbers.
Notice that you can upgrade and downgrade between 6.0.1 and 5.1.1 but cannot downgrade to 5.0.1
Both 6.0.1 and 5.1.1 have U2 in their build. In the past (at least on some devices) once these numbers change is when you cannot downgrade to a different number.
So whats my point? Look at the latest build. N910TUV S2 EPG2.
"S2" This very well could mean you can not downgrade to 5.1.1 and or PE3 6.0.1.
It also could mean that there have been some other bootloader changes.
There have been some reports that some on the latest N910TUVS2EPG2 have had trouble flashing TWRP.
Disclaimer: This info is not to be taken as golden fact. I'm just providing it so people can look out and be aware this has been the case in the past.
Since a lot of this information has not been confirmed and will not be confirmed by Samsung we can only go by past situations.
This has been indeed the case on both the Note 4 and the Galaxy Tab S2
To everyone that has indeed updated to this new Firmware version (N910TUVS2EPG2) please post any experiences from it.
Any problems? Any confirmed known changes. Anything.
Thanks!

I updated, and I was able to install twrp, root, and xposed. However, I have heard reports that twrp doesn't work for some people.

I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?

N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk

ayeitschris said:
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Chocu1a said:
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
Click to expand...
Click to collapse
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?

DeeXii said:
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
Click to expand...
Click to collapse
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:

wilsonmd said:
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
Click to expand...
Click to collapse
Any update to this?

DeeXii said:
Any update to this?
Click to expand...
Click to collapse
Odined stock EPG2 tar, SuperSu systemmode, Xposed alt 86 wanam, TWRP 3.0.2-0, no issues. Great battery, runs smoother, no hiccups. :good:

DeeXii said:
Any update to this?
Click to expand...
Click to collapse
via Odin and i could not let me try flashing the LP bootloader and flash any room ......

How Downgrade your T-Mobile Note 4 (N910t) from MM (any version) to DOK2 Lollipop!
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
IM NOT RESPONSABLE IF A HEART ATTACK OCCUR OR YOUR PHONE BLOW UP WITH ALL THE ROOF :silly:
IF YOU HAVE YOUR PHONE IN MM PG2 STOCK rooted with super SU systemless and last TWRP instaled (like me) YOU CAN DOWNGRADE TO D0K2 LOLLIPOP :
******REMEMBER Disable Reactivation lock (see picture below) and activate USB debuggin, Before DO this procedure!!*******
1-Download the DOK2 BOOTLOADER HERE https://www.androidfilehost.com/?fid=24269982087008410 and the D0K2 modem here: https://www.androidfilehost.com/?fid=24269982087008409 ( i did use 3.0.9 Odin) >>>>>>>>>thanks to @xoxo_xdagirl91 for post the links!
2- Download The 5.1.1 rom here: http://forum.xda-developers.com/note-4-tmobile/development/rom-maximum-ovrdrive-v15-1-1-t3196653 its an awsome rom by @OvrDriVE and so Thanks for that!
3-Put the ovrDrive 5.1.1 rom into the external sd card together with the upgrade. (because need erase all in the internal memory, remember, make a back up of your data in the phone or in the internal memory if you want).
4-now GO to your TWRP and wipe cache-dalvik-system-data-INTERNALmemory x3 ..........DONT TOUCH YOUR EXTERNAL SD, REMEMBER THE OVRDRIVE 5.1.1 ROM IS THERE!
******REMEMBER WHEN YOU ERASE YOUR INTERNAL MEMORY JUST REBOOT AGAIN IN RECOVERY, each time you erase yor internal memory, when reboot in TWRP you see the warning and said that you need to click in "never show this screen during boot again" just click there and swipe to allow Modifications or the stock recovery will rewrite again. TURN OF YOUR PHONE!
5-GO TO DOWNLOAD MODE TO USE Odin and flash the 5.1.1 bootloader FIRST, WHEN FINISH, Flash the modem ..... REMEMBER: put the bootloader in the BL section FIRST AND FLASH & FOLLOWING THE modem in the CP section of odin
6- When finish the step 5, go to your recovery TWRP>install>go to ext sd>flash the ROM first, when finish, wipe dalvik, cache and reboot again in TWRP
7- Just flash the othe part of the rom........the upgrade zip file, when finish just reboot the system aaaaaaaand
WALAAAAAHHHHHH!!!!!!
I DID IT EXACTLY AS DIRECTED AND I HAVE A CLEAN OVRdrive
rooted rom in 5.1.1. Now you can flash via ODIN the original firmware on 5.1.1:good::good:

Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.

mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.

xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.

xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!

mykos said:
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
Click to expand...
Click to collapse
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
kiikez said:
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
Click to expand...
Click to collapse
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:

xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Conflicting reports on here. I haven't tried this myself yet but THIS post states a successful downgrade. YMMV.

mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
how did you flashed the super su systemless?

Cannot root or odin twrp after latest (pg2) update. Odin to pe2 and everything is back to normal.

xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks

krishelnino said:
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
Click to expand...
Click to collapse
Sure bud.
1) Download the M6 ROM from Dev-Host or from MediaFire.
Put this file in your external SD card.
2) Download the BeastMode kernel.
Put this file in your external SD card.
3) Download the Data Fix - MM_DataFixs7rebootmenu.zip.
Put this file in your external SD card.
4) Boot into recovery. Make a backup of your current ROM just in case. :fingers-crossed:
5) Go into Advanced Wipe (if you're using TWRP) and wipe dalvik, system, data, cache, internal storage (or whichever options are available in the recovery you are using).
6) Flash M6 Rom from Step 1. Do not restart.
7) Flash kernel from Step 2. Do not restart.
8) Flash data fix from Step 3.
9) Now wipe cache and dalvik cahe. Restart.
Once you restart, it will look like your phone crashed or is stuck in a bootloop, it's not. Let it sit there for about 10-15 minutes and it will boot into the setup screen. Good luck. :good:

Question about rooting P8 Lite

Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite

TommyWhite said:
Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite
Click to expand...
Click to collapse
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?

You probably got stuck in boot animation because you flashed superSU in system mode. It should be installed in system-less mode. Magisk will install only in system-less mode and I think it's better at passing the safetynet.

amageek said:
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?
Click to expand...
Click to collapse
Thanks for replying :good:
What do you mean with "Your can error every versions..."? .. Do you mean you can root every version?
I am very new to this. Half of the time I dont know what the H im doing, and all of the time I only have a slight idea of what is going on in the Phone. For example I dont even know what a root file is, could you tell me?
How did you root with Magisk if I may ask? And whats the difference with SuperSu?
I had all kinda errors and issues along the way from B605 to B170 and B123 Android 5 back to 6 and B609. (I could make a thread of it ... maybe it helps others???)
Because today I finaly rooted my Phone.
Weirdly enough root checker basic sais it isnt but other root checkers say it is (and my device itself said after reboot that it was) ... so what to make of that?
Can I update the Phone now its rooted without unrooting it?

@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)

TommyWhite said:
@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)
Click to expand...
Click to collapse
You can't update phone which is rooted(as far as I know).
Do you have TWRP recovery installed?
If you had TWRP installed and you rooted by flashing SuperSu(this is what other guy meant with "root file"). By default SuperSu installs in system mode(meaning it does it thing into system partition). You need to install other zip file first to make it install system-less mode(meaning it does it thing into boot partition).
Magisk is also flashable zip and similiar to SuperSU. If you use apps that need to pass safetynet(like netflix) you want to root with magisk.
Don't know did that helped at all. It's hard to explain when I only know how to use it but don't know why/how it works : D
And if you don't mind doing factory reset before updating, you can also install official updates in TWRP.

Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )

1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
TommyWhite said:
Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )
Click to expand...
Click to collapse

By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...

amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
Click to expand...
Click to collapse
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?

keikari said:
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?
Click to expand...
Click to collapse
Yes but I haven't uploaded the file in my Mega Cloud... He can update it ..

keikari said:
1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
Click to expand...
Click to collapse
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )

amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...
Click to expand...
Click to collapse
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?

TommyWhite said:
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?
Click to expand...
Click to collapse
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this

amageek said:
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this
Click to expand...
Click to collapse
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!

TommyWhite said:
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!
Click to expand...
Click to collapse
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again

TommyWhite said:
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )
Click to expand...
Click to collapse
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.

amageek said:
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again
Click to expand...
Click to collapse
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.

keikari said:
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.
Click to expand...
Click to collapse
Thanks again, I copied some bits to remember. I hope you were not tired of me not understanding things. You said I should just ask so here I go again
I understand most of what you wrote but:
TWPR can make a back up/an image of the device, right? But that image doesnt include apps and app data (or data at all?)? And Titanium doesnt back up firmware I guess.
So how do I make a backup of everything (except of the hardware) then?
Also Im in a dilemma about updating TWPR, because you said it will whipe data (what data actually?) and amageek said I need new TWPR for stock updates. So I need the "backup of everything first" I guess ... what to do? I have TWPR 3.0.2 now by the way.
Also cant I just download Magisk from Google Play now that my phone is rooted ... or is that being stupid?
7: Its strange, coz I remember I had my phone rooted (with the help of some old tutorial they should remove imo) but accidentally downgraded my phone with it to lollipop (one of the many failures I encountered ). But just with local updates B052 to B132 to B170 back to some 2KB B132 to marshmallow B609 ... something like that ... it was unrooted again.
Anyway, by update script you mean a script only TWPR can read?
And therefor TWPR does not check the version allready installed?
Is that correct?
But after this you say: "If you are doing this remember to reboot recovery when installation is done (it will go to stock recovery) and to factory reset.
Then you can flash TWRP and do rooting stuff."
I dont get that, coz that means you have to start all over again ... or do I miss something?
Im sorry, im doing the best I can.

TommyWhite said:
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.
Click to expand...
Click to collapse
Do you have have stock recovery or TWRP recovery? If you have TWRP recovery then fish stock recovery and then try updating again...

Fire TV 3 (needle/stark): TWRP

Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.

Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.

Confirmed, it works on the cube (stark) as well...

That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.

Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.

Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.

Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.

2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?

Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.

2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...

Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.

How may I get the "su". It said, I don't have permision.

eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.

2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?

eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.

This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.

eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work

Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.

moving it to the right place.

anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?