Related
I found linuxct's guide (Link: https://forum.xda-developers.com/razer-phone/how-to/treble-install-generic-image-gsi-razer-t3770684) need to be modified to get 9.0 GSI working (at least in my circumstance). I haven't tried any Oreo Gsi but to my case, I can't properly booted to 9.0 Gsi by following exactly to this guide. That's why I want to write my own processes of getting it works. Hope it's useful to some of you.
0) I strongly recommend you to flash back to stock image from razer, if you have messed up with the partitions. !!THIS WIPES YOUR DATA, PLEASE BACKUP THE INTERNAL STORAGE!!
Code:
(Link: https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip)
After flashing to stock, it should automatically reboot into the system.
/*To your convenience, please put all the required file under the adb tool folder*/
1) Enable USB debugging, reboot to bootloader by command:
Code:
adb reboot bootloader
2) Flash the prebuild boot image in linuxct's guide by command:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
(Link is mentioned above)
This boot image has TWRP and Magisk built in.
3) Reboot into TWRP by command:
Code:
fastboot reboot
4) In TWRP, tap Wipe and do a factory wipe. DON'T CHANGE THE DEFAULT WIPE SETTINGS.
5) Flash the GSI you have, then reboot to bootloader.
6) Extract and copy the stock boot image from Razer to the adb tool folder, and flash the boot.img by command:
Code:
fastboot flash boot_a boot.img
7) Reboot to the stock recovery, and do factory wipe, then reboot to bootloader.
This will decrypt the /data. (I am not sure why if I do it under TWRP, I can never boot into system, but that's the case.)
8) Flash the prebuilt image from linuxct again by command:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
9) Reboot to the system by command:
Code:
fastboot reboot
And whola, you should be able to boot into system without any decryption message. And you will have a partially functional TWRP.
If you need to flash any other GSI next time, you should first copy the GSI image through MTP in system. Because the TWRP doesn't support adb command and can't be mounted as MTP.
Once you have copied the GSI image, you can reboot into TWRP and flash image as usual.
Here are the photos proving this works. I flashed Pixel Dust first through the command and booted. Then I reboot into TWRP and flashed PixelExperience through TWRP and get it booted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can't image I figured out to flash the second system_b so quickly lol.
0) In system_a, reboot to bootloader by command: adb reboot bootloader
1) Flash the GSI you have to system_b: fastboot flash system_b [The GSI you have]
2) Flash the stock boot image to boot_b: fastboot flash boot_b boot.img
3) Set active partition to B: fastboot --set-active=b
This is where I found linuxct's guide tricky because it should be 'b'.
'_b' doesn't work.
4) Reboot to stock recovery: fastboot reboot
5) Do a factory wipe, then go back to bootloader
6) Flash the prebuilt image to boot_b: fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
7) Reboot to the recovery: fastboot reboot
And it will brings you to TWRP on B partition, and you can reboot to system_b now.
And whola, and now you can have both AB system with different GSI. And you can switch to any partition by going to TWRP on either partition and switch as you like!
Here are the photos proving I have Pixel Experience and Pixel Dust working seperately on two partitions.
I also found that the prebuilt boot image from linuxct is breaking the wifi. Till now, you should have the TWRP patched boot image on both AB partition. So fixing that is pretty straightfoward.
1) Copy the stock boot image and TWRP installer zip to your phone in system.
Link: https://dl.twrp.me/cheryl/
I used the 3.2.1 version.
2) Boot into TWRP by command: adb reboot recovery
3) Flash stock boot.img on both A/B partition.
You can do this by first flash it to Slot A, and switch to B in TWRP. NO NEED TO REBOOT, SIMPLY SWITCH SLOT IN TWRP!!
4) Flash the twrp zip file.
This should fix your wifi.
DON'T FLASH MAGISK! I found flashing even the latest magisk v18.0 breaks wifi again.
So could you have stock on slot a and another GSI on slot b?
Magisk still breaking WiFi and 4g? I played around with 9.0 gsi's ages ago and that was the only thing stopping me from using it. Have anyone tried the latest canary builds of magisk also?
askylitangel said:
So could you have stock on slot a and another GSI on slot b?
Click to expand...
Click to collapse
Since A/B systems are using a common /data partition, I think you can at most flash an 8.1 Oreo on another slot because the stock image is 8.1. And this breaks the OTA of stock, so pretty meaningless.
It worked for me following the guide unfortunately had to go back to stock (no WiFi) shame was looking good too thanks for the guide though helped at least getting system up and booting
parky169 said:
It worked for me following the guide unfortunately had to go back to stock (no WiFi) shame was looking good too thanks for the guide though helped at least getting system up and booting
Click to expand...
Click to collapse
Follow the guide on #4, it will certainly fix Wi-Fi.
Followed must of the guide except just on partition a all worked nice
Thanks a lot.had no issues installing magisk either
Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.
BoostRoid said:
Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.
Click to expand...
Click to collapse
Pixel Experience, Pixel Dust, Aosp extended 6.1
BoostRoid said:
Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.
Click to expand...
Click to collapse
Reboot after first boot fixes it.
parky169 said:
Followed must of the guide except just on partition a all worked nice
Thanks a lot.had no issues installing magisk either
Click to expand...
Click to collapse
To clarify, you only installed on partition A, and installed magisk without breaking wifi?
Apologies for not clearing one thing up,I installed android 8.1 and it all
Worked I didn't realize at first it was android 9 that was having WiFi breaking,I haven't tried that one yet.sorry if I was misleading anyone
With my post.
All I had to do was flash the GSI image via fastboot and that seemed to work fine with no other flashing needed
What gsi ROM did you flash? And have you flashed magisk on it ?.
HO-COOH said:
I also found that the prebuilt boot image from linuxct is breaking the wifi.
Click to expand...
Click to collapse
Using an MR0 image on MR3 is not recommended, and using Magisk will break RIL (data connectivity) and WiFi.
If you want to run Pie GSIs, forget about using Magisk and run phh-su. Lastly, if you want your front camera and Bluetooth A2DP to work, use latest phh-gsi image v109. Using older versions than v108 is discouraged for breaking the mentioned.
Current status:
1. Cheryl specific overlays are not yet merged into phh source code because I'm a lazy assh*le. If you want your device to have Adaptive brightness, gestures, and fix the strong vibration, place the following apk inside /system/overlay or /vendor/overylay
2. Razer Power Service and NFC are faulty and will spam your logcat, which may, in the end, reduce your battery life. You need to extract [email protected] from both /system/lib and /system/lib64 from Razer's stock ROM and place them respectively into /vendor/lib and lib64. I've conveniently extracted them for you (Folder named 32's file should be extracted onto /vendor/lib and folder named 64's file should be extracted onto /vendor/lib64).
To kill NFC until we find a proper solution, go into your GSI's filesystem path /system/app/NfcNci and delete or change NfcNci.apk's filename into anything else, like NfcNci.bak.
3. Common to MSM8998, and I believe several other Qcomm based smartphones, Bluetooth In-Call audio is not working, and audio gets redirected to Earpiece.
4. Everything. Else. Works.
Please thank @phhusson for his amazing job in this project!
---------- Post added at 09:16 ---------- Previous post was at 09:13 ----------
As an extra, if you would like to erase your data/userdata partition without messing up with recoveries, you could just issue the following fastboot command:
Code:
fastboot format:ext4:0xc72dd3000 userdata
Where 0xc72dd3000 is the userdata partition size with FBE enabled.
If you are running a bootimage without FBE, the partition size might be 0xC72DD7000, so the command would be:
Code:
fastboot format:ext4:0xC72DD7000 userdata
--------------------
As a result, a summary of OP would be:
0. Flash latest cheryl fastboot image just like explained in OP.
1. Download the Android 9.0 GSI of your preference.
2. Reboot into fastboot.
3. Wipe your userdata partition with:
Code:
fastboot format:ext4:0xc72dd3000 userdata
4. Flash the system image you downloaded with:
Code:
fastboot flash system IMAGENAME.img
Where IMAGENAME goes your system image name. In our bootloader, you don't need to specify the partition you want to flash, and fastboot flashing into just "system" will flash the current slot.
5. Follow the steps from 1 and 2 from the Current status section above to get all the perks to work.
Tried multiple android 9 GSI roms and some boots but no wifi and data (some don't even boot).
Wifi fix (works on Arrow OS) on post #4 doesn't work. After flashing twrp 3.2.1.0, the phone does not boot on any android 9 GSI roms. Anyway thanks for your work trying to make GSI work on Razer phone.
Hello, I followed your instructions in post 4 to the letter, I've got 4g but no wifi. Any ideas what I'm doing wrong?
TWRP + MAGISK for our Motorola One Action
First of all, let me thank to @ilia3367 for his big effort bringing the joy of mod to our phones (One Vision and Action) and my fellow countryman @sfoot13 for his unvaluable help.
Original guide
Disclaimer
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Backup all your personal information, it'll be wiped.
* This process was performed on the XT2013-1 using PSBS29.-21-20-4 compilation.
Click to expand...
Click to collapse
Instructions
1- Unlock your Motorola One Action using Motorola's Official Guide.
2- Download this file to your PC.
2.1- Get the latest compilation of your firmware, according to your region, here.
2.2- Unzip the file downloaded on step 2 on c:\adb (you should already have installed ADB, Fastboot and Drivers at this point) and unzip the firmware in a place of your convenience.
3- Copy the files KANE_flash_stock.bat and vbmeta.img (remember, both files are from the file you've downloaded on the step 2) of c:\adb to the firmware folder you unzipped on step 2.2.
3.1- Some firmwares have one more system.img_sparsechunk than others, in case the firmware you've download has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
4- Copy this files (located at c:\adb) to your External SD (mandatory):
Disable_Dm-Verity_ForceEncrypt.zip
MagiskManager-v7.3.4.apk
Magisk-v19.4.zip
TWRP-3.3.1_Installer_One_Vision.zip
This is where the fun begins.
5- Reboot your phone to bootloader mode.
6- Once detected, execute the KANE_flash_stock.bat you've edited and copied to the firmware folder and wait until the phone reboots to bootloader again (around 2-3 minutes)
7- Open CMD on your computer and type
Code:
cd c:\adb
, then
Code:
fastboot -w
and when it's done
Code:
fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
8- TWRP will boot on your phone, surely in Russian, check the box and swipe to allow modifications on /system. I suggest you to set TWRP on your language (if not Russian of course ), the language setting is on the right column on the third button, and then, the globe icon (the last one), choose your language and set it up using the gray button.
*If you can't get to TWRP the first time, after the Android One Screen, keep pressing volume down and power buttons, when the phone shuts down, release the button power and get into fastboot again and try the command described above (fastboot boot TWRP...). Try until you can get into TWRP recovery, the first time took me around 4-5 times.
8.1- According to your language, go to Install > Select Storage > Micro SD card and flash TWRP-3.3.1_Installer_One_Vision.zip, once it's done, go to the home screen.
8.2- Now tap on Wipe > Format Data > Type Yes and go back to the home screen again.
8.3- Reboot to Recovery.
9- Install > Magisk-v19.4.zip and Disable_Dm-Verity_ForceEncrypt.zip, go to the home screen and tap on Reboot > Bootloader
9.1- On CMD type
Code:
fastboot flash vbmeta_a vbmeta_patch.img
and when it's done, press the power button to start.
10- The phone will show Android One Logo > Unlocked Bootloader warning screen > Android One Logo > It will reboot and will repeat the same process
10.1- After that scary but necessary reboot, it will reach the setup screen and... It will reboot and will repeat the process shown on step 10.
11- Once it reaches the setup screen again it will not reboot again (randoms reboot has been reported, nothing serious, let it reboot and keep it using).
12- Complete setup.
13- Uninstall Magisk Manager and install the APK you've copied to your External SD on step 4.
Now you're rooted.
Thanks for taking the time to read the whole guide and excuse my not-so-well (poor is threshed) english.
The original guide didn't work for me on the part when it says to boot TWRP using fastboot > Wipe Data > boot TWRP via fastboot again, it kept hanging on the Android One screen.
Greetings,
Charly.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I keep getting stuck on boot screen
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Root Moto One Action - Working on Android Pie (9) and Q (10) 23.01.2020
anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
There's another way to do it.
Download the files and install magisk on your phone.
1. Open magisk and patch your boot.ing
2. Save your patched boot to adb-fastboot folder.
3. Reboot to bootloader.
4. Flash vbmeta.img: fastboot flash vbmeta_a vbmeta.img
5. Flash your patched boot: fastboot flash boot_a PATCHEDBOOT.IMG
6. Flash vbmeta_patched: fastboot flash vbmeta_a vbmeta_patch.img
7. fastboot erase userdata and reboot.
8. Configure your phone and install magisk manager apk.
9. Here, you'll need and app... Franco kernel app, because that app allow you to flash zips without twrp (I don't know a similar app).
10. Open Franco kernel app and install twrp installer zip and reboot.
11. Reboot into FASTBOOT and type fastboot -w after that, select "Reboot Recovery".
12. Now, configure Twrp, change language and format Data (type YES), if you don't format data, you'll end in bootloop.
13. Flash magisk again because the phone was unrooted when twrp installer was flashed and flash Disable_Dm-Verity_ForceEncrypt.zip.
14. Reboot and if everything was successfully, you should be rooted with twrp working.
15. Be grateful
---------- Post added at 02:33 AM ---------- Previous post was at 02:27 AM ----------
@Tuandroidaldia
Thank you so much for the guide
If you want to UPGRADE or DOWNGRADE MAGISK, do this:
Download the Magisk version that you need and reboot into recovery.
1. Flash the downloaded Magisk version.
2. Now flash Disable_Dm-Verity_ForceEncrypt.zip
3. Reboot.
4. Check if everything is ok.
5. Hit or say "thanks".
anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
I rooted my device and then made this guide, so yes, I "followed" it If you're not able to boot into TWRP then you're missing some steps, like "fastboot -w"
Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.
binary**# said:
Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.
Click to expand...
Click to collapse
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.
Tuandroidaldia said:
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.
Click to expand...
Click to collapse
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.
binary**# said:
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.
Click to expand...
Click to collapse
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.
Tuandroidaldia said:
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.
Click to expand...
Click to collapse
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions
So here are my results
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.
binary**# said:
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions
Click to expand...
Click to collapse
I understood you. One of the steps for achieving root is to flash the Stock Firmware (with the patched vbmeta.img), so, If you want to go back to stock, you have to flash the entire firmware using the same commands as described above (with the stock vbmeta.img)
binary**# said:
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.
Click to expand...
Click to collapse
Thanks for the note, I'll change the guide ASAP. If you don't get to TWRP at the first try, you have to reboot into bootloader again (keep pressing the power button and volumen down button until it powers off, release the power button and it should reboot to bootloader), enter fastboot boot TWRP-3.3.1_Motorola_One_Vision.img and see if you can boot into TWRP, if not, try again until you can boot to TWRP (it took me around 3 or 4 times to get TWRP booted on my One Action the first time)
Hi Guys!
Got my Action One today (US User here!) and was pulling out my damn hair!!!
For those who can NOT boot into TWRP double check STEP 3!!! My issue was, even though I copied the extra zip file into the firmware folder, it did NOT overwrite the vbmeta.img so it was still loading the non patched version! Once I saw that the version it was flashing was from 9-16-2019 (For my firmware - RETAIL) and not the one from the zip from 9-26-2019! Once did that, on the second try TWRP booted and volia!
SO OP Please add to check the vbmeta.img is the correct version being flashed if they can not boot to TWRP and thanks for the instructions!
Ok so stupid me (This happened to me on my G5s+. I come from Quark so there was only one possible firmware for the phone since it was a verizon branded firmware) flashed the wrong firmware (RETAIL vs RETUS) but this guys doesn't see to work on the XT2013-4 though. The RETAIL firmware will let me have data but no voice on Verizon.
Any suggestions anyone?
My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.
thalesjans said:
My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.
Click to expand...
Click to collapse
During the original setup, where did it fail? Did it not boot TWRP?
Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!
thalesjans said:
Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!
Click to expand...
Click to collapse
So you first downloaded and flashed your firmware from the listed and did the sets to add in the extra line of code for it? Did that even complete? Then the fastboot -w? Also you copied over the vbmeta.img in the zip to the firmware folder? Twrp will not boot if that patched file is not there. Also you only boot from twrp not flash it. You don't flash it until later
---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------
Also what model of the XT2013 are you uaing? There is XT2013-1 thru XR2013-4.
Root success! Xt2013-2
So I finally rooted my Moto One Action (XT2013-2). I read on many forums that the method of flashing the patched boot.img file gave some kind of validation error for their boot files. But anyhow I went ahead with the very method and was able to successfully root my device. Here are the steps to be followed.
STEPS:
View attachment 4870223
NOTE: USERS HAVING XT 2013-2 (INDIAN VARIANT) MAY DIRECTLY TAKE MY PATCHED BOOT.IMG FILE. IT IS BASED ON THE FIRMWARE VERSION PSBS29.39-23-6
1. Extract the boot.img file from the stock firmware.
2. Patch it via Magisk Manager. The magisk_patched.img file will now be created under the Downloads folder. Move it to the platform-tools folder on your desktop.
3. Reboot to fastboot mode and flash the vbmeta file via fastboot flash vbmeta_a vbmeta.img
4. Now use the fastboot flash boot_a magisk_patched.img to flash the patched boot file.
5. Next, flash the vbmeta patched file using fastboot flash vbmeta_a vbmeta_patch.img
6. Then erase user data using fastboot erase userdata
7. Finally fastboot reboot
8 Now set up the device and install the Magisk Manager app.
9. Head over to the Magisk Manager app. It will ask for some additional configurations. Allow it. It will take a minute or two for the Magisk configuration to complete. Once done, your device will automatically reboot once. it's normal.
10. That's it. Your Moto One Action will now be successfully rooted (as already mentioned, the process was carried on the version XT 2013-2.)
I need WIFI calling enabled and non of the unlocked phones they sell at Best Buy or Amazon come with the feature activated. It is literally not listed in the settings I am looking at installing a custom ROM with WIFI calling activated like it is on my old Samsung A50. I honestly don't know the first thing about the root program that android runs on so I am looking for someone that has patience that can help a noob.
I have watched many youtube videos on this topic but I have found nothing on my specific phone.
Thanks in advance
Anubis2002 said:
I need WIFI calling enabled and non of the unlocked phones they sell at Best Buy or Amazon come with the feature activated. It is literally not listed in the settings I am looking at installing a custom ROM with WIFI calling activated like it is on my old Samsung A50. I honestly don't know the first thing about the root program that android runs on so I am looking for someone that has patience that can help a noob.
I have watched many youtube videos on this topic but I have found nothing on my specific phone.
Thanks in advance
Click to expand...
Click to collapse
About ROOT: https://forum.xda-developers.com/t/...attery-charge-limit-root-application.4251443/
About GSI: You not need TWRP. But if you want backup your userdata so need install that.
All depend about your decision: I'm install GSI and test. I chose the perfect GSI for me; so I don't need the backup => you not need custom recovery so use stock recovery.
I want GSI and need backup => need TWRP.
In the true both recoveries [stock & TWRP] has the fastbootd implemented!
So you need:
1- unlock bootloader;
2- stock or specific vbmeta file;
3- know how use fastboot commands for flash GSI;
4- Every time is more security flashing Custom ROMs if you have stock ROM!
Are you ready for flash GSI??!
Even if something goes wrong and you can't "revive" the device again?
Do you have everything it takes to feel relaxed if something goes wrong or successful?!!
I can put the instructions myself. But I will never be responsible for your actions and choices.So make up your mind!
lopestom said:
About ROOT: https://forum.xda-developers.com/t/...attery-charge-limit-root-application.4251443/
About GSI: You not need TWRP. But if you want backup your userdata so need install that.
All depend about your decision: I'm install GSI and test. I chose the perfect GSI for me; so I don't need the backup => you not need custom recovery so use stock recovery.
I want GSI and need backup => need TWRP.
In the true both recoveries [stock & TWRP] has the fastbootd implemented!
So you need:
1- unlock bootloader;
2- stock or specific vbmeta file;
3- know how use fastboot commands for flash GSI;
4- Every time is more security flashing Custom ROMs if you have stock ROM!
Are you ready for flash GSI??!
Even if something goes wrong and you can't "revive" the device again?
Do you have everything it takes to feel relaxed if something goes wrong or successful?!!
I can put the instructions myself. But I will never be responsible for your actions and choices.So make up your mind!
Click to expand...
Click to collapse
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EdsterX71 said:
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
Click to expand...
Click to collapse
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
EdsterX71 said:
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.imgView attachment 5337319
Click to expand...
Click to collapse
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
Flawless instructions , thank you so much! TRWP & Root!
i had to flash Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
then follow your instructions .
Because firmware BLU_G0370WW_V10.0.04.03_GENERIC the WIIFI and Bluetooth did not function when using older version boot.img .
lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
EdsterX71 said:
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
Unfortunately in the compiling TWRP time I haven't MicroSD to testing.
But now I know about and need fix so easy. The fix is not easy because my time and the issues about different adress/partition of MicroSD in G90 Pro. So I needed more knowledge and informations to fix that and need only write correct adress/partition. That's is to mount/start MicroSD automatically in the TWRP. But....
I not remember now because I not using MicroSD or OTG in the TWRP or ROMs. But maybe worked with the option in the TWRP - Wipe - FORMAT DATA; Reboot - Recovery. Test!
I have PBRP (other awesome Custom Recovery) if you want test too.
EdsterX71 said:
Flawless instructions , thank you so much! TRWP & Root!
i had to flash Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
then follow your instructions .
Because firmware BLU_G0370WW_V10.0.04.03_GENERIC the WIIFI and Bluetooth did not function when using older version boot.img .
Click to expand...
Click to collapse
It's a shame you didn't try to remove the boot.img file from version 10.0.04.03 because it would be interesting to know the kernel changes. But as far as I know it was a security update and the fix for call volume I think.
I not using Xposed a very time ago. Sorry. You need search/ask in the Xposed forun.
lopestom said:
Unfortunately in the compiling TWRP time I haven't MicroSD to testing.
But now I know about and need fix so easy. The fix is not easy because my time and the issues about different adress/partition of MicroSD in G90 Pro. So I needed more knowledge and informations to fix that and need only write correct adress/partition. That's is to mount/start MicroSD automatically in the TWRP. But....
I not remember now because I not using MicroSD or OTG in the TWRP or ROMs. But maybe worked with the option in the TWRP - Wipe - FORMAT DATA; Reboot - Recovery. Test!
I have PBRP (other awesome Custom Recovery) if you want test too.
It's a shame you didn't try to remove the boot.img file from version 10.0.04.03 because it would be interesting to know the kernel changes. But as far as I know it was a security update and the fix for call volume I think.
I not using Xposed a very time ago. Sorry. You need search/ask in the Xposed forun.
Click to expand...
Click to collapse
Yes I would like to try PBRP , Thanks, I really like the specs on the Blu G90 Pro... But to be honest the camera is crap.
EdsterX71 said:
EdsterX71 said:
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
n TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.
EdsterX71 said:
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.
Click to expand...
Click to collapse
EdsterX71 said:
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.imgView attachment 5337319
Click to expand...
Click to collapse
ANy error with 10.0.04.02?
As your message and picture had BLU_G0370WW_V10.0.04.03_GENERIC
Update: Yes the kernel was changed with more informations and need new Custom recovery with that to work with new stock ROM.
EdsterX71 said:
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.
Click to expand...
Click to collapse
Sent in PM to you.
I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team
lopestom said:
I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team
Need gsi link
Click to expand...
Click to collapse
Lopestom im having lags, overheat issues and system slow downs , why??
with or without gsi
my guess is hardware issue (emmc chip)
DarkeEmpire said:
I want a gsi link
Click to expand...
Click to collapse
Any GSI-Treble A10 arm64 ab - https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Can I use pixel experience
lopestom said:
I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team
Click to expand...
Click to collapse
Shorten Code for blu g90 pro GSI NOOBS edit
fastboot devices
fastboot --disable-verification flash vbmeta vbmeta_mod.img
fastboot -w
fastboot reboot fastboot
fastboot erase system
fastboot --disable-verity --disable-verification flash system GSI.img
fastboot reboot
GSI supports
Havocs, Corvus and others but not pixel experience image is too large with gapps
sometimes when transferring file from pc to the device it fails over 1mb files like what????
lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
Whenever I go into fastboot mode (with the text on the bottom left) no fastboot commands will work on my G90 Pro. Therefore I can't follow the rest of the instructions. Any possible solutions? Thanks.
While I was trying to install GApps for Lineage OS 18.1 on my Nokia 7.2, I always lost my wi-fi. This is apparently due to flashing TWRP as boot image, which replaces the stock boot messing with wi-fi as the boot image has thee kernel.
Although, I did figure it out, it took me three days to get a proper solution from multiple sources. Here, I will explain how to install Lineage OS 18.1 on Nokia 7.2 with Gapps and Magisk. This can be applied to other ROMs as well. I am assuming you are on stock firmware.
Requirements:
Any custom ROM without GApps
vbmeta file
vendor image
Gapps zip file of your choice
platform-tools
twrp image
magisk file
payload dumper tool
Preperation:
The wifi stops working because we change the boot image. To prevent this, we must flash the boot image of the rom after we are done with our work with TWRP
For this, we ,ust get the boot image for the ROM. As this is not available readily, we must extract it from the ROM zip
Install latest python on your pc
Get the payload dumper tool from the link given below. Extract the contents into the root directory of python. It should be in C:\Users\USER-NAME\AppData\Local\Programs\Python\Python <version number>
Extract the ROM zip into any folder. Copy the payload.bin file and paste it in the folder where you put the payload dumper tool
Open a command prompt in the python root folder and type
Code:
python -m pip install -r requirements.txt
Then type
Code:
python payload_dumper.py payload.bin
After it finishes, go to the folder named Output inside the python folder. Here there will be a file named boot.bin. Rename this as lineage_boot.bin and paste it into the platform tools folder
Installation:
Download the twrp image, rename it to twrp.img and place it in the platform-tools folder. Connect your phone to the computer, switch on usb debugging on your phone.
Open command shell in the platform-tools folder and type
Code:
adb reboot bootloader
. In the bootloader, type
Code:
fastboot flash boot_b twrp.img
.
Next, type
Code:
fastboot --set-active=b
and then reboot to recovery using volume buttons and selecting using power button
In TWRP swipe to allow modifications. Copy your ROM and vendor image files to your SD Card. Now, click wipe, format data and type yes. Go back to home screen and the press install. Select your ROM file and install it. Sometimes it is required to flash vendor image. In that case flash that too. This step is required for Lineage OS 18.1
Now on the twrp home screen, tap on reboot. At the bottom, the current slot should be B. Tap slot A. THis changes the active slot to A. Now go back and tap on bootloader, this should boot you to the bootloader.
Take your vbmeta.img file and place it in the platform tools folder. Now, while in the bootloader mode, type,
Code:
fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Next type
Code:
fastboot flash boot_a twrp.img
and boot to recovery using volume buttons
Now, press install in TWRP and select install and install the GApps file and reboot to bootloader
Next, in the bootloader type
Code:
fastboot flash boot_a lineage_boot.img
. Now start your phone. You should have lineage os with GApps
Installing Magisk:
Copy the lineage_boot.img into your phone. Download magisk.apk file from the link given below
Install the magisk app and open it. If it asks for additional setup select no. Beside the magisk option select install. Under options, if Recovery Mode is selected, deselect it and click next.
Now click on Select and patch a file under method. Select the lineage_boot.img
The patched image will be saved in downloads folder. Rename this file to lineage_magisk.img and copy it to the platform tools folder on your computer. Reboot your phone to bootloader mode
On your computer in the command window opened in the platform tools folder, type,
Code:
fastboot flash boot lineage_magisk.img
Reboot and you will have a rooted lineage os with GApps
Files:
Lineage OS 18.1 and vbmeta.img
TWRP
vendor
NikGApps
Payload Dumper tool
platform tools
Magisk
Guides that I Followed:
Extracting boot.img from ROM zip
Installing magisk using patched boot image
Credits:
Raghu varma for Lineage OS 18.1 port and twrp
Providers of the guides mentioned above
Hi @Ujwal2000 thanks for the guide.
I am using the stock android 10 rom and magisk patch method.
This also leads to non working wifi and magisk does not recognize that its installed.
Which steps of your guide apply to the stock rom?
i do not need gapps nor twrp I guess I only wanted to root the stock rom with magisk.
For stock, use this guide. They maintain a repository if patched boot images
Guide - How to root the Nokia 7.2 and Nokia 6.2 using Magisk
Nokia 7.2 and Nokia 6.2 come with an unlockable bootloader. The thing that compliments unlocked bootloader best is root access. So, this guide will help you in rooting the Nokia 7.2 or Nokia 6.2. You have a choice between Magisk patched boot images and TWRP recovery. I’d recommend going the...
www.techmesto.com
@Ujwal2000 , can you please look at my posting here? Thank you.
after fallowing the steps(except installing lineageOS with twrp flash everything was encrypted even tough i have the bootloader unlocked, managed to install it via adb sideload) the wifi doesnt work at all. When i try to turn it on is switches off on its own. Do anyone know a fix?
i had problem with latest version of python (3.10), version 3.7 was working for me
If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!