Related
Is it specific for each device? Or does it depend only on finding the correct partition/block to be extracted?
Could you point me to further readings about that?
Thanks.
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
DopeyTheOne said:
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
Click to expand...
Click to collapse
Well, that link is to proceed AFTER you have boot.img at hand. I want to find a way to extract it from my phone (assuming default.prop can be changed in there).
Thanks.
When you make a back up with CWM, you have a copy of your bootimage in the clockworkmod map, not?
That's the thing ... I am trying to figure out how to get that backup in hand at first.
Currently, following the method in http://droidcore.blogspot.com.br/2012/12/how-to-edit-initrc-in-android.html
It seems to use the same scripts as cited in your link.
Will post results afterwards.
Don't make things more complicated as they are. If you just install CMW recovery (or TWRP for that matter) for your device, you have your full backup in minutes, including one of your bootimage, then use the script from my first post.
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
MrCabana said:
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
Click to expand...
Click to collapse
I used a CWM image to root my device. Booted up with that image, and flashed SU....after that you can use su, and apparantly, with the changes you made with your bootimage...you'll be like God on your phone
Sent from my S500 using xda app-developers app
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Click to expand...
Click to collapse
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
bromeara said:
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
Click to expand...
Click to collapse
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Alright thank you. I'm fairly new to the android ecosystem and to boot I'm working on a Fire tablet so its running fireos and amazon doesn't really make it easy to touch their code
think he is facing the same situation as mine, for hk version of htc u12+, its hard to find the proper RUU or firmware from internet. Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Vita.T said:
Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
dano.556 said:
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
Click to expand...
Click to collapse
Ok....
I am assuming that the op has a samsung device....
Same Problem
Loku_kika said:
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Click to expand...
Click to collapse
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Lloydster said:
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Click to expand...
Click to collapse
just google "Latest Software Version for OPPO OPPO AX7" and go to the Software Updates page on oppo-uk.custhelp.com. Download 2.4GB ozip file (like CPH1903EX_11_OTA_0210_all_oStq7F7jxqfF.ozip) and unpackit with 7zip program. You'll find boot.img inside .ozip file.
I do not have root, there is no recovery or rom for my phone, Can I extract the boot.img from my phone storage, to patch it with Magisk?
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
Click to expand...
Click to collapse
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
I will upload it, i downloaded the new firmware with june security patch and extracted the boot.img from it, you can do the same or wait when i go home to upload it for you
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
enjoy
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
Click to expand...
Click to collapse
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
https://mega.nz/#!6nJhQKba!XylZfJqVyRCXdIzZnVbhwhQFs5arpPf6Cg36mR0L9_Q
Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
Small update on this, there was an Android update recently, and it fixes everything ??* so if someone else here has the same issues somehow, updating to July update fixes it
I've some questions:
-does Nokia release his kernel source and which version use? on their website there is only for 3.1 I don't know if are same thing.
-Does support treble?
hello, now there is a august update for nokia 3.2 Do u have the boot file for that.. or how can I find it??
I add this phone to the list of my amazon.it account to make some stuff like twrp and roms but didn't buy yet, I'm afraid that Nokia will not release kernel source soon so in case of taking one I can make a twrp with stock kernel extracted from boot.img see ya.
Edit: buying this phone has been cancelled after reading unlocking bootloader seems to be "impossible" shame on you dear Nokia
disy
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img 8LSD2fhKkw6nCvdOKcU1j0w"]https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w[/URL]
Click to expand...
Click to collapse
Good afternoon, I HAVE BY THIS METHOD THE PHONE IN THE LOADER HANGED, HELP TO RETURN TO THE OPERATIONAL CONDITION.
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb
Click to expand...
Click to collapse
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.
JFDee said:
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.
Click to expand...
Click to collapse
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode
bouyhy01 said:
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode
Click to expand...
Click to collapse
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.
JFDee said:
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.
Click to expand...
Click to collapse
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed
bouyhy01 said:
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed
Click to expand...
Click to collapse
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).
JFDee said:
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).
Click to expand...
Click to collapse
i found it but its a .bin
bouyhy01 said:
i found it but its a .bin
Click to expand...
Click to collapse
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.
Hello JFDee,
is it possible that you upload your original or modified boot image also?
Because i flashed the boot image that was given here and now i have the same problem, like said before.
WLAN is not working anymore and the Boot time is very long. Updating also don't work.
I also saw the differences in the build numbers.
My is like yours 00EEA....
This would be really nice, because i don'T find the stock image for this number.
Best regards!!!!
JFDee said:
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.
Click to expand...
Click to collapse
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
That device can't install TWRP yet, so only method that OPN users have to root his phones is that:
https://forum.xda-developers.com/oneplus-nord/how-to/guide-how-to-root-oneplus-nord-t4139411
I think to simplyfy that method in two scripts, one to extract payload.bin and root your phone, and another to convert that extracted payload.bin to fastboot installable ROM.
Make sure that you have python installed in your computer before use it.
Here is the steps to use it:
1. Download any OxygenOS update from Some_Random_Username's Repo:
https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085
2. Download the script:
English v1 version for Windows: https://www.androidfilehost.com/?fid=8889791610682922150
Spanish v1 version for Windows: https://www.androidfilehost.com/?fid=8889791610682922151
3. Extract the script on any folder
4. Extract "payload.bin" file from OxygenOS update, downloaded previously on step 1
5. Execute "payload.bat" and follow the steps on the script
OPTIONAL: After root your phone or extract "payload.bin" file, you can use "flash-all.bat" file from scripts file to flash whole OxygenOS update from fastboot mode!
TIPS:
- As Some_Random_Username said, you should backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, because this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
This step will be include to the script in the future
Credits:
@topjohnwu for making Magisk
@Some_Random_Username for original guide and updated repo build of Oxygen OS
@mauronofrio for original fastboot script
Reserved
You can fastboot boot twrp.img and then flash magisk, so flashing a boot image is not the only way to root.
Yup:good:
The fastboot roms are already available in the dedicated thread and with the twrp i made you can flash magisk and also stock roms, i really don't know at what this is needed
mauronofrio said:
The fastboot roms are already available in the dedicated thread and with the twrp i made you can flash magisk and also stock roms, i really don't know at what this is needed
Click to expand...
Click to collapse
goRt said:
You can fastboot boot twrp.img and then flash magisk, so flashing a boot image is not the only way to root.
Click to expand...
Click to collapse
I know that fastboot roms is already in the dedicated thread, but maybe isn't updated or any people want to extract himself (for example, now you don't have latest 10.5.5 version uploaded!)
Also with TWRP, you can't install it as normal recovery yet, so maybe people want to do and try it with fastboot method, and can use my script for help himselves.
That is another and automated method to help people only
dimusa said:
I know that fastboot roms is already in the dedicated thread, but maybe isn't updated or any people want to extract himself (for example, now you don't have latest 10.5.5 version uploaded!)
Also with TWRP, you can't install it as normal recovery yet, so maybe people want to do and try it with fastboot method, and can use my script for help himselves.
That is another and automated method to help people only
Click to expand...
Click to collapse
Twrp can also be flashed if needed
I have spent 2 days trying to figure out how to root my g90 pro. I can't find twerp for it and every possible guide I find destroys my sanity when I find out it won't work. I have magisk as a zip file on my phone right now, is there an alternate apk I could use to finish this?
I am bootloaded and it is android 10.
Have you tried using the magisk manager app and pull the stock boot from your rom. Go into magisk manager app and select install then select patch boot image. Let it do it thing. After it's done there will be a patched boot image in your download folder. Copy that img to your fastboot tools directory on your computer. Boot your phone to fastboot and connect to your computer. In adb tools cmd promt type "fastboot flash boot (name of patched boot image).img"
Reboot phone..
Success
Link to magisk manager app https://github.com/topjohnwu/Magisk/releases
If you don't have your stock boot img you will need to download your current firmware and use payload dumper to extract the boot image. Just open the firmware in 7zip or eat and extract payload.bin the place that file in the input in the payload dumper then click on the exe. Will take a min and all you system partions will be extracted in the output folder. Grab your stock boot.img from there.
Link to payload dumper https://androidfilehost.com/?fid=818070582850510260
Will try in the morning, expect update.
I have no Idea how to download directly from my firmware. I don't know if I'm misunderstanding, but I tried googling it and still am stumped. I can't find the folder or whatever, I have read so many tutorials I'm mixing everything up.
I installed two wrong boot imgs, if anyones reading this thread https://www.mediafire.com/file/7502...WW_V10.0.03.03_GENERIC_20200710_1437.zip/file
this is current firmware for g90 pro, found by using info app, and ctrl-f on this page https://forum.xda-developers.com/t/blu-stock-firmware-repository-mediafire.3853065/
I_like_root_pls said:
I have spent 2 days trying to figure out how to root my g90 pro. I can't find twerp for it and every possible guide I find destroys my sanity when I find out it won't work. I have magisk as a zip file on my phone right now, is there an alternate apk I could use to finish this?
I am bootloaded and it is android 10.
Click to expand...
Click to collapse
BLU G90 Pro TWRP Image
Does anyone know if there's a version of TWRP out there for the BLU G90 Pro? The closest I've come is the G9, and I've tried that one already. Please help. I need to root my phone so I can enable Google Play Services for AR.
forum.xda-developers.com
Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO
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...
forum.xda-developers.com