Database Users

[How To] Root

TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43

Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?

adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome

Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.

Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer

point me to some functioning samsung drivers and I can do this!

If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.

Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?

Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine

For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)

NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"

OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse

Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.

Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks

rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!

Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again

Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.

Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks

Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.

For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related

The best NexusPlayer ROM - 7.1.2 from scratch, root and block OTA updates HOWTO

So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice and install it. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
First thing you need to do is ensure your player is unlocked. When in the fastboot screen it should show the lock state. If it's locked, you need to run this command twice from your computer: "fastboot oem unlock"
Okay, now you're ready to go, you need to extract the factory firmware and use adb to flash it. Extract the main firmware file. Inside is another large zip file with the broken out recovery and system images. Extract that file also.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the flashed bootloader: fastboot reboot-bootloader (If it doesn't reboot in the bootloader, unplug and use the hold button and plug in to get back to the bootloader screen)
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
TWRP Might ask if you want to keep system Read Only. Push the button that says Keep Read Only.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v17.3.zip (Or whatever version of Magisk you happened to download)
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe/factory reset of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip This will disallow updates to be applied.
Remount the system partition as readwrite
cd /
mount -o rw,remount /system
Disable otacerts.zip
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
exit
exit
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sdcard/disupdate.sh
You should then use adb shell again and move the script into place
adb shell
su (accept request on screen if it asks to become root)
mv /sdcard/disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots. If there is no directory /sbin/.core/img/.core/service.d then Magisk isn't likely properly installed. You might need to reboot or something to get it to load.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.

Thank you! My player started random reboots then lost wifi on android 8. This worked great and she seems to be running properly again.
The final step fails for me. I run adb push to move the script and it looks like it does it, no error message but the file doesn't copy. Not a big deal, I can watch netflix again.
---------- Post added at 12:32 PM ---------- Previous post was at 11:47 AM ----------
I worked around it. What I did was push the file to a location I had permission to write to on the nexus.
Then I copied the file using a root powered file manager, Solid Explorer in this case, to /sbin/.core/img/.core/service.d/
Hopefully this helps others to keep their nexus player alive. 7.1.2 runs very nice.

Update: After running great for the past week my nexus player how just sits at the black google screen.

You lost me at the "USB OTG adapter"
I wonder if your problem with Ver. 8 (which is Oreo?) has to do with unplugging or losing power to the device? - After I lost power for just a second (blink) the unit partially bricked and finding your post got me to a different page that showed how to sideload (via ADB) the ver. 8 OTA onto the device.
That worked OK until the unit lost power again (I unplugged it to move it). The problem returned and since I don't have the mouse adapter, I just tried to sideload a ver. 7.1.2 OTA but that refused to load with an error message that I didn't grok but probably meant that it was incompatible with stuff that Ver. 8 had on the filesystem.
So I restored again the latest Ver. 8 ota.zip and for now (until the next power off) it is working.
-----
Seems like they have a problem serious enough thought that another update will have to happen.
-----
Thanks!
snowzach said:
So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
Once you are in fastboot mode, you need to extract the factory firmware and use the minimal adb to flash it.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the old bootloader: fastboot reboot-bootloader
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v16.7.zip
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip
This will disallow updates to be applied
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
You may also need to use adb shell again and run:
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.
Click to expand...
Click to collapse

First off great starting point to get nougat back on nexus player but a few points...
a) I had to do "mount -o rw,remount /system" after SU to get write on /system
b) The method you outlined for running script on boot didn't work for me and i ended up having to use https://play.google.com/store/apps/details?id=com.k2.bootshellprokey with the script you provided
Other than those two points worked great and staying on 7.1.2

Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks

texasjmzmd said:
Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks
Click to expand...
Click to collapse
I answered these questions. However I get an error of failed to copy when I adb push the sh file.

Had to do this 4 times to get it to stick. The second to the last step preventing the update is what was difficult. It kept upgrading to Android 8. I couldn't get the script part to work. So far so good this has worked for me. Kibmcz's "a)" suggestion allowed me to stop the automatic upgrade. So far it's sticking and working really well. I did this to prevent the black screen of death that everyone's getting with Android 8.0 upgrade.

Got the OTG adapter - questions & comments
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
A couple of days later, the 4 balls animation returned. Brought up Restore, TWRP and attempted to revert to a backup made with it but it would not restore it. So... Flashed boot and Flashed system and it came back to life for another couple of days. TWRP doesn't load anymore though so the un-altered system without the script still doesn't want to load Oreo as there is a copy of Oreo still there that didn't pass verification.
Still busted every couple of days though.

ggregor said:
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
Click to expand...
Click to collapse
I couldn't get the script to work either.

Did this August 21st. Still working today [Sept 2].

For those of you still having trouble, it seems like you are having an issue with installing Magisk. When you have Magisk installed, it actually creates linked directories in the system partition. You aren't making changes to system. I am going to update the original post to push the script and then move it to a directory that Magisk manages. That hopefully fixes everyone else.

Thanks for posting and updating your instructions. I used my own workaround for keeping my 3 Nexus Players alive and locked on Nougat 7.12...
Do you have a theory on how to make the LED light work again on those NPs that have gone dark and unresponsive to the OTG connection from a laptop or PC?

Instead of rooting or using Magisk, just use TWRP and its file manager to rename the ota certs file. You can also use it to put in the script if you want, or use it to remove gms and gsf to stop GPS from updating which actually is more the problem - people on lineage 15.1 are still bricking.

Did this August 21st. Still working today [Sept 20].

Mine is dead now.... No light on powerup, quickboot screen or any other sign of life. Forced to move on to a non-branded Android box. Boot loop even started after using LineageOS 15.1 (which required starting with 8.0 Oreo)

thanks for the guide, I did this and it worked great. Used the script as well and all 3 of my players are still working 2+ weeks after doing this.
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?

Triumph said:
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?
Click to expand...
Click to collapse
Which specific streaming apps are you referring to and what do the error msgs say?

growsonwalls said:
Which specific streaming apps are you referring to and what do the error msgs say?
Click to expand...
Click to collapse
They are HGTV, Travel Channel, Cooking Network, and ABC.
When I open them up they show a "Live Channel" option, and I enter in my online information for the channel (That has always worked in the past, and works on my Nvidia Shield device that isn't rooted.)
If I choose the Live Channel quick enough it tries to play then times out and says "There was an error playing this content."
If I open the app, and stay at the main screen for a minute or so, the Live Channel option disappears from the header, and I don't see it again, until I reboot the player.
I can play previous show episodes, just not the live stuff.

Triumph said:
They are HGTV, Travel Channel, Cooking Network, and ABC.
I can play previous show episodes, just not the live stuff.
Click to expand...
Click to collapse
In order to recreate this, I am still missing vital information.
Is this happening inside of Kodi or did you download these 4 apps (channels) through the Google Play Store?
In Kodi, I've never seen a "Live Channel" option for these channels, just several old episodes listed.
As for the 4 channels from the Play Store, they each have a stream live option where you sign in to your tv provider. My tv provider isn't on that 'sign in' list so can't watch it live.
If in Kodi, were they installed from the Kodi repo or did you install a 'build' that came with them already installed?
Or is there a different streaming app that is hosting these apps?

Fire hd 8 7th gen root

I tried all rooting methods for fire hd 8 7th gen but didnt succeed... the apply update in the recovery is also not there... can anyone help me?
im new...

Darklord071 said:
I tried all rooting methods for fire hd 8 7th gen but didnt succeed... the apply update in the recovery is also not there... can anyone help me?
im new...
Click to expand...
Click to collapse
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?

Letitride said:
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?
Click to expand...
Click to collapse
Thanks for the welcome.. i tried using linux and windows... the fire tab is running fire os 5.6.6.0..
i know adb commands..and i disabled ads using fire toolkit.
and i use debian linux.
Thanks in advance!!

Letitride said:
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?
Click to expand...
Click to collapse
btw do u have the drivers for 32bit arch linux?
thx

Darklord071 said:
btw do u have the drivers for 32bit arch linux?
thx
Click to expand...
Click to collapse
Fire OS 5.6.6.0 is the newest one and my understanding is that version/release is a PITA as the "exploit" to unlock & inject the Fastboot mod is a problem .... sorry about that, maybe another XDA'er familiar with that can help walk you thru on their efforts & success (or not) i.e. whether they managed to roll it back.
I used LMDE-4 Cinnamon 64bit (d/l via Linux Mint) and it works fine on my good old Dell 380 desktop on USB stick ... don't believe one can get anything done if I stay on Windows 10 Pro. Copy or download all the possible files you need to the USB/thumb drive ahead or while connected in LInux ... go slow & a nice cup of coffee is always good to watch & sip. If you have even older hardware (just retired my 15 years old Dell Optiplex 620 MT which has been a home server) - LMDE-3 Cinnaman 32 or 64 bits (LTS) should do. Sorry, I don't have a link to any 32 bits ... just go search for it while connected.
If and when you managed to modify the HD8 and get back into Bootloader & Recovery, do not restart the device until you are certain that TWRP is up & running (whether you install & run Magisk or not, doesn't matter) Then, sideload & flash either LIneage 12 OS or the "stock" HD8 rom in this XDA thread/link - https://forum.xda-developers.com/hd...rmware-amazon-fire-hd-8-2017-douglas-t3972921
Even if you cannot do some/all of the above, the latest V8.2 Toolbox itself is pretty good - ads blocked & OTA stopped/disabled, able to install Google Apps & Play Store, etc. and Nova Laucher (I recommend & use it myself on the FD8) ... it is more responsive than Lineage (being in "beta" status) - install some apps & run it, let it update & settle down for a day or two.
Be sure to read & follow all the steps, disable WiFi & turn on Developer's Mode, enabled USB debug, etc. - then resume & do the setup after using the Toolbox.
Not bad for a $60 device that's 3+ years old, I got Youtube Vance running, Adaway installed & FB/Messenger/IG "Lite" working - use it to watch videos on a 64 GB mSD card offline, and check email & run news app ... when not using it as a security cam monitor linked to our Xiaomi & Wyze wifi cams.
Just don't feel like trading up for a $10 Amazon gift card & get the newest HD8 with 20% discount - if and it's on sale on 2020 Prime Day, I might just grab another one to play.
What do you wish, hope & expect the HD8 to do by rooting it ??

Letitride said:
Fire OS 5.6.6.0 is the newest one and my understanding is that version/release is a PITA as the "exploit" to unlock & inject the Fastboot mod is a problem .... sorry about that, maybe another XDA'er familiar with that can help walk you thru on their efforts & success (or not) i.e. whether they managed to roll it back.
I used LMDE-4 Cinnamon 64bit (d/l via Linux Mint) and it works fine on my good old Dell 380 desktop on USB stick ... don't believe one can get anything done if I stay on Windows 10 Pro. Copy or download all the possible files you need to the USB/thumb drive ahead or while connected in LInux ... go slow & a nice cup of coffee is always good to watch & sip. If you have even older hardware (just retired my 15 years old Dell Optiplex 620 MT which has been a home server) - LMDE-3 Cinnaman 32 or 64 bits (LTS) should do. Sorry, I don't have a link to any 32 bits ... just go search for it while connected.
If and when you managed to modify the HD8 and get back into Bootloader & Recovery, do not restart the device until you are certain that TWRP is up & running (whether you install & run Magisk or not, doesn't matter) Then, sideload & flash either LIneage 12 OS or the "stock" HD8 rom in this XDA thread/link - https://forum.xda-developers.com/hd...rmware-amazon-fire-hd-8-2017-douglas-t3972921
Even if you cannot do some/all of the above, the latest V8.2 Toolbox itself is pretty good - ads blocked & OTA stopped/disabled, able to install Google Apps & Play Store, etc. and Nova Laucher (I recommend & use it myself on the FD8) ... it is more responsive than Lineage (being in "beta" status) - install some apps & run it, let it update & settle down for a day or two.
Be sure to read & follow all the steps, disable WiFi & turn on Developer's Mode, enabled USB debug, etc. - then resume & do the setup after using the Toolbox.
Not bad for a $60 device that's 3+ years old, I got Youtube Vance running, Adaway installed & FB/Messenger/IG "Lite" working - use it to watch videos on a 64 GB mSD card offline, and check email & run news app ... when not using it as a security cam monitor linked to our Xiaomi & Wyze wifi cams.
Just don't feel like trading up for a $10 Amazon gift card & get the newest HD8 with 20% discount - if and it's on sale on 2020 Prime Day, I might just grab another one to play.
What do you wish, hope & expect the HD8 to do by rooting it ??
Click to expand...
Click to collapse
I wanna install custom roms to get a better experience... Thanks a lot ??.

Darklord071 said:
I wanna install custom roms to get a better experience... Thanks a lot .
Click to expand...
Click to collapse
There isn't much custom rom development going on with a years old Fire HD tablet, unless you are prepared to work on LOS's V12 beta (newest release) - which I tried briefly, which I am hoping to go back to when status is "stable". I am perfectly happy to go back to use the tablet as an always-on mini monitor for our home security cams.
Have you managed to root yours yet ??
Just FYI and as a sideload, I've been watching prices for the newest HD8 2020 (Gen 10) priced at $89.99 - with Prime Day around the corner. Well, I hit the Enter key today upon getting an alert that it's on sale at QVC for $59.99 with free standard shipping. Wiki codes & whatever - able to use a "New" code to get an additional $15 off, hence - ordered it, just a click over $50 shipped, taxes included - AND, it's bundled with a coupon for free case redemption (that's anywhere from $15 to $25) and other goodies. I should get mine by next weekend - going to have fun with the Toolbars Kit & see how far I can run with it, and see if the smart XDA'ers will find a way to root it - got another inexpensive tablet to play & watch YouTube Vanced, etc.

This post was a Mistake

Letitride said:
There isn't much custom rom development going on with a years old Fire HD tablet, unless you are prepared to work on LOS's V12 beta (newest release) - which I tried briefly, which I am hoping to go back to when status is "stable". I am perfectly happy to go back to use the tablet as an always-on mini monitor for our home security cams.
Have you managed to root yours yet ??
Just FYI and as a sideload, I've been watching prices for the newest HD8 2020 (Gen 10) priced at $89.99 - with Prime Day around the corner. Well, I hit the Enter key today upon getting an alert that it's on sale at QVC for $59.99 with free standard shipping. Wiki codes & whatever - able to use a "New" code to get an additional $15 off, hence - ordered it, just a click over $50 shipped, taxes included - AND, it's bundled with a coupon for free case redemption (that's anywhere from $15 to $25) and other goodies. I should get mine by next weekend - going to have fun with the Toolbars Kit & see how far I can run with it, and see if the smart XDA'ers will find a way to root it - got another inexpensive tablet to play & watch YouTube Vanced, etc.
Click to expand...
Click to collapse
I haven't rooted mine yet... I used the raspberry pi before??.. so I am gonna use a laptop soon... I'm only 14 yrs old???. I wanna also be a software developer when I grow up.. and my laptop is in the us and can't be delivered to me cuz of the pandemic.... Thanks a lot and I posted this question in reddit and some nice guy gave me the link for directions.. these are the instructions posted by a fellow xda'er..
Yesterday i managed to root updated FireOS and install Lineage 12.1, so, here's my story
Version 5.6.6.0 build 654620620,
on Linux KDE Neon.
Installed python3, PySerial, adb, fastboot dos2unix as described in this and other posts.
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Downloaded the following attachments from the first post : amonet-douglas-v1.2.zip and brick-douglas.zip
Extract both files to the same folder
Enable Developer options and enable ADB (inside debugging options) on Amazon tablet
Plug in the tablet (has to be turned on)
Now comes the commands execution part. So, open the terminal in Linux (lines that start with // are comments and should not be run from command line - if you copy paste)
Code:
sudo systemctl stop ModemManager && sudo systemctl disable ModemManager
Code:
adb devices
// there should be an item listed
// to be sure, you can unplug and run it again, if it's empty,
// ou know tablet can connect, so plug in the tablet back
Code:
adb reboot bootloader
// reboots the tablet and awaits commands
Code:
sudo ./brick.sh
// type YES, hit enter
// it will take a couple of minutes (around 3-5min in my case)
// watch the tablet for success message, it should be displayed there if everything works
// but also, watch your terminal...if it gives you error message similiar to:
// ==> [I][U]failed with error message that it can't write somewhere[/U][/I]
// you have to try with brick-9820 script
Code:
sudo ./brick-9820.sh
// it will take a couple of minutes, similar to above step
NOTE : after either of the above commands (which one succeeds) POWER OFF THE TABLET and DO NOT try to turn it back on. It should stay powered off!!
Code:
sudo ./bootrom-step.sh
// this will take some time (in my case around 5-10 minutes)
// will give you message similar to "awaiting device connection" and nothing else...
// although nothing seems to happen, just wait a bit and watch the terminal, it will soon start displaying the process
// it should then reboot the tablet, but in my case, that did not happen, so i had to do it manually...
// NOTE that althought tablet seems to be "off", it isn't, so press power btn and hold for 5 sec to turn it off
// after that click and hold volume up button (when in portrait mode it is the right one, the one closest to power btn)
// and immediately after that press and hold the power btn until amazon logo shows itself
// it should then show in bottom left corner HACKED FASTBOOT after a few seconds
Code:
sudo fastboot devices
// there should be a device listed
// if not, you should run (in the extracted directory that you are in):
./bin/fastboot devices
// if sudo fastboot devices does not show your device but ./bin/fastboot works, you have to edit the fastboot-step.sh file and change the fastboot commands to ./bin/fastboot
Code:
sudo ./fastboot-step.sh
// takes a couple of minutes (1-3 min in my case)
// reboots the device
after that you should be in TWRP
NOTE when in TWRP:
DO NOT RESTART tablet before the following
(or amazon fire os will overwrite TWRP and you will be reset to factory default with fireOS, losing everything you've done and starting from scratch...
when it happened to me, the brick-9820.sh didn't work anymore and had to use brick.sh script)
-allow modifications
-format data,system,cache partitions, go to wipe->advanced wipe-> repair/format (something like that), select each of the 3 partitions aformentioned and format to ext4
-if you've done it correctly, there should not be any red warnings
-after that go to wipe, select all partitions and wipe them (just to be sure)
-tablet should be connected and TWRP should be left on
on PC
-download Lineage 12.1 ROM from https://forum.xda-developers.com/hd8-hd10/general/discussion-root-progress-fire-hd-8-t3743024
-download opengapps from https://opengapps.org/
- put them inside amonet-douglas-v1.2 folder where you've extracted the prior ZIP files (just to be clear, you can put them anywhere, but i like to keep it all inside the working directory)
-go to terminal
Code:
adb push lineage-12.1-20200614-UNOFFICIAL-douglas.zip /sdcard
adb push open_gapps-arm64-5.1-nano-20200624.zip /sdcard
now the files are on the tablet
- in TWRP go to INSTALL, go to /sdcard folder if not in it
- first install Lineage ROM from zip
- then install GApps from zip
hope it works!
I'm glad i've finally rooted it, thank you all for the great content here!

Darklord071 said:
I haven't rooted mine yet... I used the raspberry pi before.. so I am gonna use a laptop soon... I'm only 14 yrs old. I wanna also be a software developer when I grow up.. and my laptop is in the us and can't be delivered to me cuz of the pandemic.... Thanks a lot and I posted this question in reddit and some nice guy gave me the link for directions.. these are the instructions posted by a fellow xda'er..
Yesterday i managed to root updated FireOS and install Lineage 12.1, so, here's my story
Version 5.6.6.0 build 654620620,
on Linux KDE Neon.
Installed python3, PySerial, adb, fastboot dos2unix as described in this and other posts.
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Downloaded the following attachments from the first post : amonet-douglas-v1.2.zip and brick-douglas.zip
Extract both files to the same folder
Enable Developer options and enable ADB (inside debugging options) on Amazon tablet
Plug in the tablet (has to be turned on)
Now comes the commands execution part. So, open the terminal in Linux (lines that start with // are comments and should not be run from command line - if you copy paste)
Code:
sudo systemctl stop ModemManager && sudo systemctl disable ModemManager
Code:
adb devices
// there should be an item listed
// to be sure, you can unplug and run it again, if it's empty,
// ou know tablet can connect, so plug in the tablet back
Code:
adb reboot bootloader
// reboots the tablet and awaits commands
Code:
sudo ./brick.sh
// type YES, hit enter
// it will take a couple of minutes (around 3-5min in my case)
// watch the tablet for success message, it should be displayed there if everything works
// but also, watch your terminal...if it gives you error message similiar to:
// ==> [I][U]failed with error message that it can't write somewhere[/U][/I]
// you have to try with brick-9820 script
Code:
sudo ./brick-9820.sh
// it will take a couple of minutes, similar to above step
NOTE : after either of the above commands (which one succeeds) POWER OFF THE TABLET and DO NOT try to turn it back on. It should stay powered off!!
Code:
sudo ./bootrom-step.sh
// this will take some time (in my case around 5-10 minutes)
// will give you message similar to "awaiting device connection" and nothing else...
// although nothing seems to happen, just wait a bit and watch the terminal, it will soon start displaying the process
// it should then reboot the tablet, but in my case, that did not happen, so i had to do it manually...
// NOTE that althought tablet seems to be "off", it isn't, so press power btn and hold for 5 sec to turn it off
// after that click and hold volume up button (when in portrait mode it is the right one, the one closest to power btn)
// and immediately after that press and hold the power btn until amazon logo shows itself
// it should then show in bottom left corner HACKED FASTBOOT after a few seconds
Code:
sudo fastboot devices
// there should be a device listed
// if not, you should run (in the extracted directory that you are in):
./bin/fastboot devices
// if sudo fastboot devices does not show your device but ./bin/fastboot works, you have to edit the fastboot-step.sh file and change the fastboot commands to ./bin/fastboot
Code:
sudo ./fastboot-step.sh
// takes a couple of minutes (1-3 min in my case)
// reboots the device
after that you should be in TWRP
NOTE when in TWRP:
DO NOT RESTART tablet before the following
(or amazon fire os will overwrite TWRP and you will be reset to factory default with fireOS, losing everything you've done and starting from scratch...
when it happened to me, the brick-9820.sh didn't work anymore and had to use brick.sh script)
-allow modifications
-format data,system,cache partitions, go to wipe->advanced wipe-> repair/format (something like that), select each of the 3 partitions aformentioned and format to ext4
-if you've done it correctly, there should not be any red warnings
-after that go to wipe, select all partitions and wipe them (just to be sure)
-tablet should be connected and TWRP should be left on
on PC
-download Lineage 12.1 ROM from https://forum.xda-developers.com/hd8-hd10/general/discussion-root-progress-fire-hd-8-t3743024
-download opengapps from https://opengapps.org/
- put them inside amonet-douglas-v1.2 folder where you've extracted the prior ZIP files (just to be clear, you can put them anywhere, but i like to keep it all inside the working directory)
-go to terminal
Code:
adb push lineage-12.1-20200614-UNOFFICIAL-douglas.zip /sdcard
adb push open_gapps-arm64-5.1-nano-20200624.zip /sdcard
now the files are on the tablet
- in TWRP go to INSTALL, go to /sdcard folder if not in it
- first install Lineage ROM from zip
- then install GApps from zip
hope it works!
I'm glad i've finally rooted it, thank you all for the great content here!
Click to expand...
Click to collapse
Dude! Thank you so much for sharing this, I've spent hours looking for a solution and I'll certainly give this a go when I next get the opportunity. Literally I exhausted all my efforts to the point where I posted a question a couple of days ago (https://forum.xda-developers.com/showpost.php?p=83638279&postcount=584). Fingers crossed your very helpful reply will help me see an end to this painful process!

lmao
andyboot said:
Dude! Thank you so much for sharing this, I've spent hours looking for a solution and I'll certainly give this a go when I next get the opportunity. Literally I exhausted all my efforts to the point where I posted a question a couple of days ago (https://forum.xda-developers.com/showpost.php?p=83638279&postcount=584). Fingers crossed your very helpful reply will help me see an end to this painful process!
Click to expand...
Click to collapse
LMAO. No problem
btw it worked for other ppl so, it will definitely work for you!

Darklord071 said:
LMAO. No problem
btw it worked for other ppl so, it will definitely work for you!
Click to expand...
Click to collapse
Quick update, worked like a charm! Thanks once again!

WORKED!!
andyboot said:
Quick update, worked like a charm! Thanks once again!
Click to expand...
Click to collapse
tried it yesterday.. IT WORKED!!!

Just wanted to add another confirmation that these steps worked. Its hard finding the correct info for such an old device and so much out of date guides, but this worked like a charm.

thetakerfan said:
Just wanted to add another confirmation that these steps worked. Its hard finding the correct info for such an old device and so much out of date guides, but this worked like a charm.
Click to expand...
Click to collapse
Hit the thanks button if you want to!

Thanks Darklord071. Worked like a charm.
I guess LineageOS 12.1 is the best we can get huh? it's showing Android 5.1.1.
Some apps are not compatible with those old Android versions. Oh well.

[GUIDE] Android 11 GSI With GApps and Root (magisk)

DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2!
This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something moderately more cohesive and understandable. Here's my moderately usable guide!
-----------------------------------------------------------------
VIDEO!
-----------------------------------------------------------------
-----------------------------------------------------------------
Things that work and don't work:
-----------------------------------------------------------------
This section will update periodically as issues arise or fixes arise for said issues.
Note: Things that work: Bluetooth*, all sensors, audio, LTE/SIM/phone stuff, 120hz (you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected])
Things that probably work: N/A
Things that don't work for some reason: SafteyNet with Magisk. All modules that I've used work tho...??! Verizon.
Remember, you can always flash back to stock if something doesn't work properly.
-----------------------------------------------------------------
FIXES!!!
-----------------------------------------------------------------
AUDIO FIX!!! GO TO Phh Treble Settings > Qualcomm features > Use alternate audio policy.
Bluetooth audio stops working with this enabled. Disable it for Bluetooth audio. The audio fix doesn't apply to Bluetooth audio ether way.
BLUETOOTH FIX!!! Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Important notes
-----------------------------------------------------------------
THIS IS ASSUMING YOU HAVE ALREADY UNLOCKED THE BOOTLOADER OF YOUR DEVICE AND HAVE GOTTEN A SERIAL NUMBER OUTPUT FROM CMD AFTER TYPING IN "fastboot devices" AND MAKE SURE YOU HAVE TYPED IN "fastboot flashing unlock" AND "fastboot flashing unlock-critical".
***NOTE: I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES OR ANGRY PARENTS. PLEASE DO NOT COME BACK AT ME SAYING I AM STUPID AND BRICKED YOUR PHONE. YOU DECIDED TO DO THIS. PLEASE PROCEED WITH CAUTION AND DON'T SKIM***
ANOTHER IMPORTANT NOTE: The stock firmware is actually really good for unbricking devices. Razer made it easy to fix your bricked device. So basically, if you can get in to fastboot mode, (which you basically always can do) you can unbrick your device super easily.
AGAIN JUST PLEASE, MAKE SURE TO FOLLOW ALL THESE INSTRUCTIONS CAREFULLY AND DONT SKIM OR ELSE YOU MIGHT BREAK SOMETHING!!!
-----------------------------------------------------------------
Introduction
-----------------------------------------------------------------
This is a quick and easy guide for how to install Android 11 on the Razer Phone 2. I'm kind of a noob here myself but I did this and it worked flawlessly. (also if you do run into any issues PLEASE don't count on me for troubleshooting tips (I'm not that great at that))
-----------------------------------------------------------------
Pre-requisites/Downloads
-----------------------------------------------------------------
Get the factory firmware for your phone. It's a good failsafe in case of a bootloop or a bad case of the phone not booting up. Download it here: P-SMR6-RC001-RZR-201022 (latest build at the time of writing)
Extract this with 7zip or WinRar (or windows. You will need 7zip or WinRar for the rest of this)
First you need the actual GSI. Get the latest version. (Make sure its not a pre-release). system-roar-arm64-ab-vndklite-gapps.img.xz is the version that you should get. The vndklite release will allow you to modify the system partition making it possible to get magisk. Note: If you want magisk, MAKE SURE TO COMPLETELY follow the magisk section of this guide aswell or else magisk will NOT install correctly and will NOT work.
This version also has GApps. It will give you Gmail, the google play store, google play services, etc.
Use 7zip or WinRar to extract this.
Your also gonna need the Trinity Kernel (v2). This gives you TWRP and I'm pretty sure you also need this to have the ability to boot up the phone (I may be wrong but it's required.)
use 7zip or WinRar to extract this.
You will also need this zip file made by arter97 I don't really know what it does but you need it. here is the download: Download.
Don't extract this.
Put all these in a known folder that you can access later.
Alright. Now that we're done with the downloads, time to test to make sure your ready to put this on your phone.
-----------------------------------------------------------------
Making sure your computer is ready
-----------------------------------------------------------------
First things first. Go open your platform tools folder, shift-right click and open a PowerShell, or command prompt window there. Shut down your Razer phone 2 and turn it back on with the power and volume down buttons.
Plug it into your PC and type in
Code:
fastboot devices
you should end up with the serial number of the device. if you don't, follow Razer's instructions on how to install USB drivers and then come back here. Link to PDF.
If you get a serial number, close that and flash stock firmware by going into the aura-p-release-etc. folder, then opening flash_all.bat.
When it finishes and the screen goes black, hold the power and volume down buttons again to get back in to fastboot mode.
open back up the CMD/PowerShell platform tools window thing again.
-----------------------------------------------------------------
Installing/Flashing
-----------------------------------------------------------------
In your CMD or PowerShell window, (while in fastboot mode on the phone) type
Code:
fastboot flash system <file name>
in the <file name> area, just drag and drop the system-roar-arm64-etc.img file into your command line. your command will look a little something like this:
Code:
fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
Wait until it says complete or something similar like done or something and has no errors.
Then, time to flash the kernel. it should just be called boot.img.
We will be typing in:
Code:
fastboot flash boot <file name>
Do the same thing that you did for the last command which is drag and drop the boot.img file for the file name.
Again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select reboot bootloader with your power button on your phone.
Go to recovery mode and swipe where it says to swipe.
Go to the wipe menu and then tap on format data. Type yes and then press enter/ok.
Go back to your computer and open file explorer.
Put the last zip file that I was talking about earlier (the f2fs thing) on the razer phone 2's internal storage. Head back to your phone, and press install.
Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that, go back to the TWRP home screen (with the 8 options)
Go to the reboot menu, then reboot into recovery
Tap on format data and type in "yes" and tap ok. click on "don't install" because you don't need the TWRP app on your phone.
The phone will shut down. Turn it on normally and everything will work!
----------------------------------------------------------------------------------------------------------------------------------
GET THESE THINGS IF YOU WANT 120Hz, GCam, and a SNAZZY RAZER LOGO.
----------------------------------------------------------------------------------------------------------------------------------
To get 120Hz, you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected].
If you want your Razer logo to light up again, use Logo+. here is a download: Logo+ APK
The default camera app sucks. Make sure to get GCam 7.4 from Cyanogen Mods (v8.0 is broken). you can get it here.
Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Magisk
-----------------------------------------------------------------
So this part was pretty long-awaited. It half-passes SafteyNet and modules work! (at least all the modules that I've used.)
Make sure you have the vndklite variant. That is the only way that this will work.
1. Open up an adb/fastboot powershell/cmd/windows terminal window.
2. Type adb root and hit enter.
3. Type adb shell and hit enter.
4. Type mount -o remount,rw / and hit enter.
5. Type mv /bin/resetprop_phh /bin/phh-resetprop and hit enter.
6. Type phh-securize.sh and hit enter.
The phone should reboot after you approve the request (if there is one) and you are now able to install magisk!
MAKE SURE THAT THE SUPERUSER APP IS NOT THERE AFTER RUNNING phh-securize.sh.
Get specifically this version of Magisk. Download the zip file.
Boot into TWRP and tap on mount, and select everything (usb storage doesn't matter in this case. it never mounts either way.)
Transfer over your zip file via file explorer, and go back to your phone.
Tap install, then scroll down until you find the zip file and tap it. Swipe to flash and wait. After it is done, you can reboot!
You should see Magisk manager in your app drawer. Open that. It might ask you to install it, if so, install it. Allow apps from this source then install. Open it up. You should see that Magisk is installed. Update it and turn on Magisk hide.
If it passes SafteyNet, it's a miracle.
-----------------------------------------------------------------
In case of failure
-----------------------------------------------------------------
If it starts bootlooping or is perpetually stuck at the razer logo, powered by android screen, go back into fastboot mode and run the flash_all.bat stock firmware thing. it will unbrick your phone automatically. Really make sure you don't skim if you try it again. If it did work (which it probably did), then have a good time with android 11!

There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!

Reznor7 said:
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Click to expand...
Click to collapse
Just curious, what games have that issue?

Marcos8760 said:
Just curious, what games have that issue?
Click to expand...
Click to collapse
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.

Reznor7 said:
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Click to expand...
Click to collapse
Thanks for the info. I added that to the top of the thread.
EDIT: Fix at the top of the thread

Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR

rrusek said:
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
Click to expand...
Click to collapse
I got the Razer logo working flawlessly with logo+. I didn't really see the appeal for Dolby Atmos as all it did was made it louder and made the audio clip more.

I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module

Reznor7 said:
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Click to expand...
Click to collapse
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.

Marcos8760 said:
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Click to expand...
Click to collapse
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.

Reznor7 said:
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Click to expand...
Click to collapse
Alright good to know. like the other info I've gathered, ill put that at the top of the thread until further notice.

The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.

Reznor7 said:
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Click to expand...
Click to collapse
Nope, Magisk doesn't work.

Thank you. I got it all set up and mostly working well. I was wondering if you could try Minecraft and let me know if it will let you get to the actual login screen.

I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.

AgentXGhost said:
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
Click to expand...
Click to collapse
You forgot to extract it with winrar or 7zip. make sure it is a .img file and not a .xz file.

Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Thanks very much. It works perfectly.

AgentXGhost said:
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Click to expand...
Click to collapse
oh noes!

When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?

Gurcharan5 said:
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Click to expand...
Click to collapse
Try going to wipe, then format data. That might fix the problem. If not, try everything again.

[Guide] Building a TWRP Fire TV Stick Rom [WIP]

Since @burcbuluklu did such a nice job of creating this for mantis (4k), I've decided to copy that concept for sheldon.
I've created a couple different images, which I'll post in the next few days hopefully.
Sorry for the delay. I've actually managed to get further with this then I expected. The wait will be worth it. I've managed to bring back the OOBE (the welcome setup you have to run through when the stick is brand new). There's one last piece I would like to figure out before I post the image.
I'm looking for help on creating a script that will trigger after the OOBE is complete. There is a flag that gets set after successful completion of the OOBE so that value could be read on boot for example and then trigger the script. Would also want to ensure the script only runs once. It will just be a basic debloating script. This is the last piece of the puzzle. This is a bit out of my skill set. If you can give me a hand with this I'll be able to post a really nice complete image.
--------------------------------------
I've now managed to get around the following problem, though not as cleanly as I would like.
Unfortunately, I'm stuck at a critical part. I need to remove my amazon account before I can share it.
I've approached it in two ways but neither have been successful. First is to remove my account after everything has been setup and done, this would be a bit preferable as I've already done all the work to create this. Second is to not have to sign in with amazon to begin with. Basically disable the OOBE, build up the ROM and then re-enable OOBE so when it gets flashed it's easy to run through that part of the setup. If OOBE can't be re-enabled, then the setup to connect your remote will be the same as in the 4K thread, hopefully.
I had played with various ways to get around OOBE, getting ADB enabled out of the box etc, all with various levels of success on mantis but for whatever reason I can't get ADB enabled on sheldon. For clarification, the intent is to get ADB enabled via recovery so it's accessible before having to run through OOBE.
EDIT:
The only plausible way I've figured out is to use "deregister". Not sure how much "personal info" is left as it says it won't remove all personal info but I used a dummy account anyway. The other factor that is different from mantis/6.2.7.6, is to complete OOBE after the stick has been deregistered, the stock amazon launcher must still be enabled. When trying with another launcher set via launch manager, OOBE won't complete as it gets into a loop during the registration stage. Definitely unfortunate as I would have liked the user to end up on the customer launcher (wolf in this case) rather then having to enable it after getting through the OOBE. If anyone has a better way please let me know.

Can't you just enable ADB through IDME?

Finnzz said:
Can't you just enable ADB through IDME?
Click to expand...
Click to collapse
I'm not familiar with IDME. I couldn't find a whole lot on it. Mind pointing me in the right direction?

bnevets27 said:
I'm not familiar with IDME. I couldn't find a whole lot on it. Mind pointing me in the right direction?
Click to expand...
Click to collapse
IDME is part of the Amazon feature layer added to all their bootloaders. It includes flags to enable ADB, enable ADB with root, and enable ADB without authorization.
You can check it out if you boot up FireOS and use the command 'ADB shell IDME print'. Fos_flags is the value you are interested in in this case.
The fos_flag value can be set from within FireOS using ADB, or from fastboot. These values are written to the end of the bootloader partition, or backup bootloader. It's magic is "beefdeed", and you could edit it directly.
For more information go to Amazon's FireTV open source page, download the source for Sheldon and search the bootloader source for IDME.h

reserved

reserved

@Finnzz thanks for the suggestion but I wasn't able to figure out IDME. Looks pretty interesting though. End result is was easier to just run through the OOBE. Now that I have an image it doesn't matter too much anymore. And I think I've managed to remove all account traces. Though I still want to figure out how to get adb access and bypass the OOBE. I've seen @SweenWolf do it for mantis. Of course I can do it with an image restore but that's not really the same thing. It's not really need but interesting anyhow.
Getting close to a release, just need help making a script that triggers after the OOBE is complete. More info on that in the OP.