Database Users

[GUIDE] Port firefox OS to Nexus 4 + Galaxy 2 Dual Boot

How To Install Firefox OS on a nexus 4 and dual boot. ​
XDA-Developers member pureexe has created an Image that will help you to port Firefox OS to your Google Nexus 4. Here is the list of what works and what doesn’t works:
What Works:
– Wi-Fi
– Data
– Phone Calls
– Contact Import
– GPS
– SMS/MMS
-Some Sensors (Light+Gyroscope+Acceleration)
-ADB
Does NOT Work:
– Camera
-MTP/PTP
– A lot of other things
How To Flash
Step 1: First connect your device to PC (desktop/laptop) via USB and make sure that USB debugging enabled on your device.
Step 2: Now to be on safe side create a Nandroid backup from recovery its because if something goes wrong then you can easily backup all your data.
Step 3: After creating backup, now download the ROM (FFOS_mako_********.zip) file and place these files on the SD card of the phone.
Step 4: Now switch off the phone and boot the phone into Recovery mode.
Step 5: Assuming you are in the Recovery mode and now you have to wipe the full data on your device. To do this, you have to click on “Wipe Data/Factory Reset” option. As soon as you click on “Wipe Data/Factory Reset” option a new screen pop-up where you have to click on “Yes” option.
Step 6: After wiping out all the data on your device you have to wipe the cache & the dalvik cache also.
Step 7: Now go to “install zip from SD card” option and click on “select zip from SD card”. After selecting the option “select zip from SD card” you have to choose the ROM file.
Step 8: After performing all the correctly in step 7 you have to clear the cache and & dalvik cache again.
Step 9: Now, go to “Install zip from SD card” option and click on “Select zip from SD card”. After selecting the option “Select zip from SD card”, you have to choose the optional file like home app or server module
Step 10 : Assuming you have performed all the steps correctly, now simply reboot your device and it will boot into Firefox OS.
Click to expand...
Click to collapse
How to dual boot: ONLY FOR GALAXY S2
Warning: This procedure doesn't really work anymore. It only works with Android 4 (Ice Cream Sandwich) and Siyah Kernel v 5.0.1. Later versions of either won't work. Consider this guide archived, and use it at your own risk.
If you want to test B2G from time to time but continue using Android as your main OS and you have a Samsung Galaxy S2, you can choose to install B2G in a separate partition (which is already present on the phone) and choose where to boot into when your device starts.
Prerequisites
In order to dual boot Android and B2G, you have to meet these prerequisites:
You have to have built B2G for the Galaxy S2
You have to download the Siyah kernel v. 5.0.1 for the Galaxy S2
You need the tool simg2img, that you get automatically if you build B2G following the guide on MDN
You need the heimdall tool, best if version 1.3.1 as you may encounter problems with version 1.3.2
One-time operations
There are several operations to do in order to get a working dual boot. The following ones need to be done the first time only.
In order to use heimdall without requiring root access, you should create a file called android.rules (the portion of the name before the .rules extension is arbitrary) and place it in /etc/udev/rules.d. The file should contain a line line the following:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
In order to activate this rule, you should restart udev:
Code:
sudo service udev restart
and then unplug and replug in the phone. The above rule will also allow adb to access the SGS2 without requiring root privlidges.
Flashing the Siyah kernel
The Siyah kernel is mandatory for the dual boot, because it is this kernel that manages it. Once you have downloaded and decompressed the tar file, you'll be left with a file named zImage. In order to flash it on your phone you have to follow these steps:
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash the kernel with the following command (your phone needs to be connected to your PC):
heimdall flash --kernel /path/to/zImage
Once the kernel is flashed the phone will reboot.
Preparing the B2G rom environment
Once you've installed the Siyah kernel, it's time to use its functions to prepare the environment to install your B2G image in the secondary partition. Follow these steps:
Switch off your phone
Reboot in recovery mode (press together volume up + home + power buttons)
In the CWMR Touch interface, go to dual-boot options -> Wipe 2ndROM data/cache -> Yes - Wipe. This operation will take some time
Once the operation is finished, select Go Back and then reboot system now to reboot your phone. If you check, inside the internal SD card of your phone you'll now have a .secondrom directory with inside two files named cache.img and data.img.
B2G update operations
The following operations need to be done every time you build a new version of B2G.
In order to simplify command line instructions, it's advised to copy all needed files in a same folder of your choice. These are the files that need to be copied inside the folder:
Code:
simg2img, found in B2G/out/target/product/galaxys2/system/bin/
system.img, found in B2G/out/target/product/galaxys2/
userdata.img, found in B2G/out/target/product/galaxys2/
Once you have all the files in one place, do the following:
Create a data.img file out of the sparse file userdata.img. You can do it with the following command:
Code:
simg2img userdata.img data.img
Put the data.img file on your phone's .secondrom folder. You can do this either by enabling file storage mode on your phone and connecting it to your PC or, if you have USB Debug active, you can use adb:
adb push /path/to/data.img /sdcard/.secondrom/data.img
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash B2G firmware inside the second partition:
heimdall flash --hidden system.img
Once the flash is finished, your phone will reboot and at boot time you can boot into your second rom (the B2G one) by pressing the home button during the bootloader countdown. If everything has gone right, once you've finished booting B2G you'll have a black screen on your phone. You now have to install Gaia.
Note: Depending on how you want to test B2G, you may not want to put a new data.img file on the phone every time you update B2G, as it will wipe all of your preferences, installed applications and in general pretty much everything you've done while using B2G.
Boot operations
The following operations need to be done every time you boot inside B2G.
Unfortunately, there's no simple way to put Gaia inside the system.img B2G image, and it get lost when you switch off your phone, so you'll need to install Gaia again every time you boot inside B2G. To install Gaia, type the following on a console after you've booted your phone inside B2G (so you have a black screen) and have connected your phone to your PC:
cd B2G/gaia
GAIA_DOMAIN=foo.org make install-gaia
After the upload of Gaia is completed, on your phone's screen the B2G interface will appear.
Click to expand...
Click to collapse
Dual Boot With Nexus 4 :
Original Link Here
Text Steps :
-Download FFOS.zip file
-Go to TWRP recovery
-Go to advanced, MultiROM, add ROM
-Select android, and don't share kernel
-Select next, then select zip file
-Select the FFOS.zip file
-After that go to list ROMs, pick FFOS, select flash zip, and flash the addons you want
-Reboot to multiboot
-Select FFOS and boot it
-Wait about 2 minutes
-You're now booted to FFOS
BTW FFOS stands for firefox OS
Downloads :
FFOS image Here
Contributors + Complier
pureexefor image and steps
Mozilla (for Dual Boot 1)
Riro Zizo for dual boot 2
Me, for putting all this stuff together!

@Apph3x
I have two version of porting
- Base Jellybean 4.3
- Base Kitkat
i know Base Kitkat is bad but working fine on base Jellybean 4.3
on jellybean everything working except MTP
Please read this post http://forum.xda-developers.com/showpost.php?p=44451567&postcount=2

Thanks
@pureexe I know but I'm sparse on time will update soon. The image is your latest 1 tho ;D thanks for original guide

Updated
Removed by owner
vvvvvvvvvvvvvvvv

Updated
UPDATE BASE LAYER 4.3
What Works:
- Wi-Fi
- Data
- Phone Calls
- Bluetooth
- Camera (Rear Camera & Front Camera)
- Video Record
- GPS
- SMS/MMS
- MUSIC (Mp3 & ogg decoder working)
- USB tethering
- WIFI tethering
- Video HQ decoder
- Sensor (Light+Gyroscope+Acceleration)
- ADB
- A lot of thing
Does NOT Work:
-MTP/PTP
Download
http://forum.xda-developers.com/devd...ct/dl/?id=3793

A Complete Noob-Friendly Guide To Personalize Your Sony Xperia Z5 Premium Dual E6883

If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery. - Actually, there is no need for this step. The custom kernel provided above already included TWRP 3, so this is just to show you how to flash a custom recovery. Thanks, @YasuHamed
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:

Now that you have root access, the next part is to remove bloatware but I will post this later on because I need to do some more research just to confirm it won't have FCs in the future. Removing bloatware is rather self-explanatory and depends on your personal preferences. Like me, I would delete all of Google and Sony apps to bare minimum but some people prefer leaving Google Maps or Sony Smart Connect on their phone. I'll see you on the next episode, to be continued...
Reserved for battery management, tips and tricks.

cglegion said:
If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:
Click to expand...
Click to collapse
the customer kernals by @khab.bros already have recovery installed,

Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.

@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...

cglegion said:
Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.
Click to expand...
Click to collapse
the way sony is behind in specs, I think in upcoming days the development side of xperia will suffer the most as the sales goes down!
in 2016 we have mobiles reaching specs such as 2.2ghz with 6gb ram and the NEWEST xperia X series has 1.5gb ~ 2gb RAM ONLY~

-DM- said:
@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...
Click to expand...
Click to collapse
You're right @-DM-, the fact that I recommend using Android SDK was the ability to install packages automatically for example the Google USB Driver though the SDK manager and not solely for fastboot functionality. Some newbies might not even have appropriate drivers installed on their machine so their device won't be recognized hence a simple problem will lead to another problem. But of course, using minimal adb and fastboot is another noob-friendly way (which is also less in size) compared to the 100mb + Android SDK. Thanks, for the heads up too and making this thread a more noob-friendly one! :laugh:

Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!

cglegion said:
Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!
Click to expand...
Click to collapse
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...

Command Prompt
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.

shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
Make sure you have unlocked your bootloader before following this guide and just to inform you again this guide is for E6883.

Yeah I figured it out, the only problem was the fastboot drives weren't installed correctly for some reason windows 10 didn't allow it, also it was having trouble finding the boot.img so I just dragged the fastboot.exe and the boot.img into the command instead and it worked.
All in all great guide, thanks.

YasuHamed said:
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...
Click to expand...
Click to collapse
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.

shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
use flahstool
---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------
use flashtool
---------- Post added at 11:34 AM ---------- Previous post was at 11:15 AM ----------
cglegion said:
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.
Click to expand...
Click to collapse
although i never liked aroma and i won't usually recommend custom roms specially for xperia... but since you have came this far,
lets say under APK foler you removed many bloatware and also updated
you must repack you SYSTEM folder (only) back to ROOM.zip (originally extracted from ftf file using ext2explorer)
then you need to apply mods,
https://www.youtube.com/watch?v=FdhUK_Ds4Fo (part 2, deleting bloatware) / finding MODS and repacking
http://forum.xda-developers.com/showthread.php?t=1363460 (tutorial about updater script modification by notepad++ )
however just remember what ever studies i did, for android 6.0.1 the prf creator wont work,
but you can try (PRF creator)
http://forum.xda-developers.com/showthread.php?t=1363460
convert your boot.img to kernel.sin and recreate your PRF creator (as mentioned above)
OR keep the custom rom ftf and BOOT.img SAPERATE as many custom roms does that
1. cynogenmod 12+
3. Miui 5 onwards
have boot+recovery file saperate and Rom saperate to flash.
the only reason i could understand is because they flash their system via recovery. if your aroma stock has xd recovery you can keep the flashable zip to install as system ORRRR keep it as FTF file to be flash and then kernal to be flashed saperate

Thanks for this guide I just wish to have root on locked BL...

[GUIDE] Root and/or install a GSI on razer phone 2 and pass safety net (For Windows)

YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
ISSUE: FASTBOOT Might not work on windows 10 version 2004, a solution is to use a Linux virtual machine to use fastboot commands. Test it out first as you might be lucky and it could work for you.
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port, as USB 3.0 might give you issues with the fastboot commands)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day

Usyless said:
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Click to expand...
Click to collapse
Thank you excellent post just what I needed.

eedwin101 said:
Thank you excellent post just what I needed.
Click to expand...
Click to collapse
I'm glad it helped you

Usyless said:
I'm glad it helped you
Click to expand...
Click to collapse
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.

eedwin101 said:
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
Click to expand...
Click to collapse
I know that phhussons AOSP works on this phone with no issues aswell, you might have to use securize to get safety net to pass tho.
android 11 will boot on this phone however iirc you won't be able to hear and other people won't hear you in phone calls.
havoc gsis I believe works but I haven't tested it and I have only heard of one person using it.
BLISS/LOSQ/CAOS don't work on this phone at all.
and after that I don't think there really is many more GSIs that work as they just won't boot for bizarre reasons

How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.

_Sherrif said:
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
Click to expand...
Click to collapse
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.

Usyless said:
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Click to expand...
Click to collapse
No AT&T.

_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)

_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
or you could try this: https://t.me/razer_phone/12949
install instructions shown in the message

Usyless said:
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
Click to expand...
Click to collapse
Aight! Definitely worth a try. Tried everything else.
Thank you!

Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.

frannet said:
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
Click to expand...
Click to collapse
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.

Usyless said:
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Click to expand...
Click to collapse
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.

frannet said:
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
Click to expand...
Click to collapse
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.

Usyless said:
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Click to expand...
Click to collapse
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it

frannet said:
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
Click to expand...
Click to collapse
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)

Usyless said:
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Click to expand...
Click to collapse
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ??

frannet said:
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ?
Click to expand...
Click to collapse
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha

i
Usyless said:
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
Click to expand...
Click to collapse
Hahaha, yeah, If I'm honest, dark mode in iOS work fine, very fine, normally I use my iPhone 11 and I play with android devices for.. for play with the OS and develoment OS, and as second andriods phone for maybe.... I go to check the gsi mode, thanks guy!!

[11] [GSI] [OFFICIAL] AOSP Q Mod //CAOS

C A O S​(Note, I did not make this rom. This is a Generic System Image (GSI) made by Caos' devs. so it is not specifically built for the A51, but it's really stable and I am using it now. ALL CREDIT GOES TO CAOS' DEVS!)
Your warranty is now void!​We're not responsible for bricked devices, dead SD cards,​thermonuclear war, or you getting fired because the alarm app failed. Please​do some research if you have any concerns about features included in this ROM​before flashing it! YOU are choosing to make these modifications, and if​you point the finger at us for messing up your device, we will laugh at you​​
CAOS (Custom AOSP OS) is a project which is based on @phhusson's Treble GSI AOSP 10. CAOS' devs began it because ASOP has stability, speed and support but also some issues and limitations - pure AOSP's code has some bugs and it doesn't have much useful things and it's hard to pull it. So CAOS' devs did this fork. System can run with SELinux enforced state, as an original Phh AOSP GSI. Fully compatible with PHH-Treble patches exclude few low level changes: no root app, no "su" binary in system; by default exist file /system/phh/secure (for Google Certification PASS), so if you can boot AOSP GSI, but can't boot CAOS - try to removing that file
UPDATE VERSION
latest build: 2020.10.29
treble patches: v222+
SPL: 5 Oct 2020
File Downloads/Installation​THINGS THAT YOU NEED ON YOUR WINDOWS COMPUTER.​
Odin
Unzip the file. There is a EXE file in it. Double click it to launch. There will be a pop up, just press ok.
FILES THAT YOU NEED TO FLASH THE ROM.​The rom itself
Make sure you have 7-zip installed. Right click it and click extract files. Go into the unzipped folder and rename the file inside to "system.img"
TWRP Decrypter
Just leave this file as a zip. Don't unzip it.
ChonDoe Flasher
Just leave this file as a zip, Don't unzip it.
INSTALL RECOVERY AND UNLOCK BOOTLOADER (SKIP THIS PART IF YOU ALREADY HAVE TWRP.)​I have made a reddit post on twrp. DO NOT DO THE MAGISK PART.
FLASHING THE FILES​Go into TWRP. Press wipe and go into format data. Type in yes and wipe your data. Press the home button in your nav bar and go back into Wipe. Press advanced wipe, tick "data", "Dalvik / ART cache" and "Cache". Format it.
Press the home button in the nav bar again. Now, go into reboot and click recovery. Don't do anything. Once it's back into TWRP, plug your phone into the pc if you haven't already.
On your Windows PC, go into File Explorer, This PC, A515F and then internal storage. Take the "system.img" file and drag it into there. Do the same with "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" and "ChonDoe_Flasher.zip"
Once all of them are copied, go onto your phone. Click install and you should see your files. If you don't, go into /sdcard. Flash "ChonDoe_Flasher.zip". Once it's done, flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip". Press "Reboot System" once "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" is installed.
If this looks really confusing to you, there is a tutorial for this. However, it's for HavocOS. But everything is the same except the rom. But the steps are the same. Watch it here.​
Congrats! You have installed Caos!​
CONTACTS
> telegram group
> project page
KNOWN BUGS:
• excluding fixes, the same as on AOSP Quack (in some cases doesn't work: broadcasting on TV, calls via BT; offline charging does not work normally fingerprint doesnt work; problems with GPS etc etc)
NOTE: always test ROM first without Magisk (with clean boot ramdisk). and don't send me bug reports if you have:
a) Magisk installed​b) modified/custom vendor or kernel​c) dirty flashing rom without wiping data​
CREDITS
persons: @phhusson
projects: TrebleGSI • BlissROMs • crDroid • PixelExperience • ION • neon-OS • Havoc-OS • LineageOS • Evolution-X • LiquidRemix • ExtendedUI • GrapheneOS • abc rom

[HOW TO] Install Android 13 Beta on Samsung S20 Series

Hello everyone !! I recently installed the latest android 13 beta 3.3 on my Samsung Galaxy S20. I wanted to make a guide to show you the installation process. This is a GSI of android 13 ported from the google pixel 5, therefore there are a few things that don't work properly (I will list them below). If you have any questions or issues with installation please don't hesitate to ask and I'll do my best to help you !! Hope you find this guide helpful !!
Issues / Bugs
- No biometrics (No face unlock or fingerprint scannner)
- No always on display (only screen saver available)
- No auto-brightnees
- No sound on notifications
Pre-requisites
- Unlocked bootloader
- TWRP Recovery
YouTube Step by Step Tutorial
Download Installation Files:
2.7 GB folder on MEGA
32 files and 5 subfolders
mega.nz
How to Install Android 13 Beta 3.3 on Samsung S20 Series
1. Turn your phone off
2. Connect your phone to your computer via USB cable
3. Press the "power" and "volume up" buttons at the same time until you see the TWRP logo
4. Once booted into TWRP, click on "Reboot", then click on "Fastboot"
5. Wait for your phone to boot into fastboot mode
6. Go to your computer and download the folder with the necessary installation files linked above.
7. Open the folder that you downloaded and look for the "Platform Tools (Name of your OS)" folder.
8. Look for the "fastboot" file and drag it into a new terminal window
9. Leave a space and type the word "devices"
10. Hit enter
11. If you see a bunch of random numbers followed by the word "fastboot" your computer has recognized your phone
12. Go back to the "Platform Tools (Name of your OS)" folder and once again, drag the "fastboot" file into the terminal
13. Leave a space and type the words "erase system"
14. Hit enter
15. When the process is finished you should see the words "finished" and "total time" in the terminal
16. One last time, drag the "fastboot" file to the terminal
17. Leave a space and type "flash system"
18. Go to the folder that you previously downloaded (the one linked above) and look for the "Pixel 13...Beta3.3.img" file
19. Drag the file over to the command window and hit enter
20. Wait for the file to be flashed (this might take a while)
21. When flashing is finished you will again see the message "finished" and "total time" in the terminal
22. Go back to your phone
23. Click on "Reboot"
24. Click on "System"
25. Wait for your phone to restart with the new ROM
ENJOY !!!!

Great Tutorial There, Did you ever fix the issues from the pixel to s20
also is there a way to find out if my bootloader is unlocked?
Thanks again

R0YB0Y said:
Great Tutorial There, Did you ever fix the issues from the pixel to s20
also is there a way to find out if my bootloader is unlocked?
Thanks again
Click to expand...
Click to collapse
Google or YouTube, cheers

@victoriam8a, this gsi image is installable by twrp, plus gapps and magisk (individual choice), I did it a few days ago my fp was working, bluetooth streaming not working and a few more things, I'm gonna give another try and also try all the work arounds to get things going on android 13, cheers