Even without a custom recovery like TWRP you can get Magisk on your phone.
To do this you need to manually patch the stock boot image and flash that to your boot partition.
However, I've done all of this and with a few steps you'll be rooted.
There's a more detailed guide below.
1) Get bootloader unlock code here
2) Enable "OEM Unlocking", boot into fastboot and type: "fastboot oem unlock your-unlock-code"
3) Download patched ramdisk image here and put it in fastboot directory.
4) Reboot into fastboot and type: "fastboot flash ramdisk patched_ramdisk.img"
(Optional) 5) Flash this to go back to stock ramdisk
[Detailed Guide]
First off, you need an unlocked bootloader. To do this, you need a special code from Huawei, you can request this here:
https://emui.huawei.com/en/plugin.php?id=unlock
With this code, and having "OEM unlocking" enabled in debugger settings, boot in fastboot mode.
Afterwards, open fastboot console and type: "fastboot oem unlock your-unlock-code"
Your device will now reboot.
Now reboot your device back into fastboot mode and open a fastboot console once more.
Download this patched ramdisk partition and place it in the same folder as your fastboot executable.
http://www.mediafire.com/file/9yfz6w9e8q7j5u2/patched_ramdisk.img
Now simply type in the console: "fastboot flash ramdisk patched_ramdisk.img".
Reboot your phone and it is rooted!
Download Magisk Manager to update/configure Magisk.
[REMOVE ROOT]
To remove the root, simply flash this original ramdisk partition, the same way as above. You can also relock the bootloader if wanted.
http://www.mediafire.com/file/4d6w2labc6cmh2o/original_ramdisk.img
WORKS IN ANE-AL00 china model??
When I'm trying to install the patched ramdisk with "fastboot flash ramdisk patched_ramdisk.img" it says "cannot load patched_ramdisk.img".
What's the exactly directory?
@RogerXIII, from which build did you patched ramdisk?
Nick said:
WORKS IN ANE-AL00 china model??
Click to expand...
Click to collapse
Only tested on ANE-LX1, you're welcome to try it though.
r00terb3y said:
When I'm trying to install the patched ramdisk with "fastboot flash ramdisk patched_ramdisk.img" it says "cannot load patched_ramdisk.img".
What's the exactly directory?
Click to expand...
Click to collapse
It has to be in the directory of your fastboot executable.
kilroystyx said:
@RogerXIII, from which build did you patched ramdisk?
Click to expand...
Click to collapse
Version 8.0.0.104 (C185)
Just a clarification. So lite version come with 8.0 ? Not 8.1 ?
otonieru said:
Just a clarification. So lite version come with 8.0 ? Not 8.1 ?
Click to expand...
Click to collapse
Correct
RogerXIII said:
Only tested on ANE-LX1, you're welcome to try it though.
It has to be in the directory of your fastboot executable.
Version 8.0.0.104 (C185)
Click to expand...
Click to collapse
And how do I find out?
r00terb3y said:
And how do I find out?
Click to expand...
Click to collapse
Find out what ? The directory ? Or the compatibilty ?
If the conpatibility, simply try it. And you will know
r00terb3y said:
And how do I find out?
Click to expand...
Click to collapse
I think you mean the directory:
On your computer you have the file "fastboot" that you use for sending fastboot commands to your phone, put the .img file in yhe same folder as that program. If you don't know where it is located, you can download the platform-tools files separately and use those.
Thank you worked very well. I need twrp but i cant find or Build compatibility with p20 do you find any way to get it work?
1) Get bootloader unlock code here
this is giving me a 404 error...
In which compilation (build) did you use this root?
Just got root on ANE-LX1 successfully. Tell me please, should this metod pass SafetyNet or not?
Rooted my ANE-XL3 just fine.
Hi. Huawei P20 lite ANE-LX1 8.0.0.111(C432).
Asking for some advice. Having read several how to guide to root, installed adb on Linux, connected, backup ok, patched ram disk, original ram disk and so on and so on, Running in circles about UNLOCK CODE: OR getting a 404 eng/Chinese, Or logging at Huawei and getting a US page for honor 7/10. Cannot get the unlock page to fill the formulary, although having all necessary info, IMEI, Product ID etc. My region is PT. Request advice, considering returning the phone wich is not so bad at benchmarks... Thank you. Congrats
I payed 5 usd at dc-unlocker and unlocked my bootloader in about 20 minutes. I followed this guide:
https://forum.xda-developers.com/honor-7/general/bl-unlock-dc-unlocker-t3318738
Just got an OTA: ANE-LX1 8.0.0.105(C10). My device OS ver.: ANE-LX1 8.0.0.102(C10). Please tell me, should I apply it? What will happen with root? Will I need to reflash ramdisk after update?
Can someone tell me where to unlock the bootloader? The link gives me only a 404 page
Alucard1238 said:
Can someone tell me where to unlock the bootloader? The link gives me only a 404 page
Click to expand...
Click to collapse
If the link is down you have a paid service, google by DC-unlocker
Related
Upon booting the 2nd RC build of Dirty Unicorns, I am faced with the dialog saying that the vendor image is out of date,
I have downloaded one from developer.google.com, I just need to know what I have to do to get it onto my Pixel.
fastboot flash vendor vendor.img
Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?
pTeronaut said:
Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?
Click to expand...
Click to collapse
If you download the full image from Google there is a second compressed file in the full image that has a vendor.img file. Also the just below the download link on the forum for the du ROM there is a link for the vendor image .
The third ROM release from DU does not require vendor image flash if you're already on the latest image.
Otherwise, reboot to bootloader.
Open your command prompt.
Use the command "fastboot flash vendor vendor.img".
I go the extra mile and do two commands.
"fastboot flash vendor_a vendor.img"
"fastboot flash vendor_b vendor.img"
Though it's probably not necessary.
As mentioned above, download the full Google image.
https://developers.google.com/android/images
Then extract it, and keep extracting it again and again until you find the vendor.img.
You can use TWRP to flash the vendor image. No need for fastboot.
spaceman860 said:
You can use TWRP to flash the vendor image. No need for fastboot.
Click to expand...
Click to collapse
Does that work with twrp on pixel?
toknitup420 said:
Does that work with twrp on pixel?
Click to expand...
Click to collapse
Yes
spaceman860 said:
Yes
Click to expand...
Click to collapse
Sweet deal. I didn't know that was working on pixel yet. Good looks for the info.
Flashing
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there
mac796 said:
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there
Click to expand...
Click to collapse
I exstract it to a ADB folder and I opened the command prop there.
Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Hello... Is your bootloader unlocked?
Good luck...
5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.
Vestell said:
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.
Click to expand...
Click to collapse
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...
5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
5.1 said:
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...
Click to expand...
Click to collapse
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum
Vestell said:
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum
Click to expand...
Click to collapse
Sorry... Since i don't own the device, it's unlikely I can help you. Maybe flashing g P9 lite requires a different process, I don't know. Again, i guess you won't find much help in this forum.
Good luck...
where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?
ken2736 said:
where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?
Click to expand...
Click to collapse
U need extracted vendor img from stock Google zip then flash image in twrp. Yes click image button. Then click on vendor then flash.
hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?
I had trouble finding this information, and since we have no working TWRP yet, here is a way to get low-level access to al lot of files.
Full credits go to: @s3axel, Source
So you flashed a module that is now causing a bootloop?
Follow these steps:
0. check if you can boot using stock boot.img, if that does not work, then you have a bigger problem then I had and this guide may not work for you.
1. Get the stock recovery.img by extracting it from the same OTA file as your current build, using payload_dumper
2. Follow s3axel's guide to get adb to work in recovery mode (after you unlock the drive)
s3axel said:
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Click to expand...
Click to collapse
3. rename the image_new.img to unsecure_adb_recovery.img
4. flash usecure recovery
Code:
fastboot flash recovery unsecure_adb_recovery.img
5. get into the adb shell
Code:
adb shell
then find the magisk module folder
Code:
cd /data/adb/modules
6. remove the module
Code:
rm -rf name_of_module
7. exit shell
8. reboot back to fastboot (See notes below)
9. flash stock recovery
Code:
fastboot flash recovery recovery.img
10. boot patched boot image to try if magisk worked
Code:
fastboot boot patched_magisk.img
Hopefully, if it boots again with root and Magisk
This worked very well and was very easy to do.
11. Use Magisk apk to install magisk to boot img. Or flash your patched magisk.
Notes:
DO NOT try adb reboot fastboot, I was hoping this would work (I was tired, ok...)
I got stuck in a bootloop (it kept asking me to unlock my device)
to break out of this loop, I used the forced off method: hold power + volume up & down until screen blacks out
From power off to bootloader:
press & hold volume down and power
and hold down until you get back to recovery, reboot to fastboot then flash stock recovery back to secure your ADB and return to as much stock as possible :good:
Here is my patched prop.default
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
grandpajiver said:
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Click to expand...
Click to collapse
The Recovery.img is from stock, so not a per-device thing.
I was just too lazy to find a place to upload large files.
I am currently on 10.0.4 but with 10.0.5 showing up, it would need updating later on.
I am not sure if you can flashboot boot recovery, certainly worth a try? Not sure how all this works, so I just flashed recovery and then flashed stock after I was done.
I also tested the TWRP build by not flashing it but booting it directly, but that was not very productive given it's current state.
hafiz.hasan said:
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
Click to expand...
Click to collapse
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
If only I didn't have tons of crap at work. This may be the gateway to v4a.
I have the images but not the extractor. Hmmmmm.
FreezyExp said:
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
Click to expand...
Click to collapse
Nice.. So are you gonna help building core only boot img for our device.?
hafiz.hasan said:
Nice.. So are you gonna help building core only boot img for our device.?
Click to expand...
Click to collapse
Nope sorry, not at this time.
There is a pull request on the magisk github that allows us to build Core-Only, so I will be waiting for that.
This guide contains the information that solved my immediate issue with not being in possesion of core-only.
Without having to deal with a lot of unknowns, just download some tools, extract some files, edit a few lines then patch it back up.
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
grandpajiver said:
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
Click to expand...
Click to collapse
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
This isn't fun to work on through a locked down Windows 10 pc. gonna try again on my chromebook after I get the 1.0.0.6 build.
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
grandpajiver said:
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
Click to expand...
Click to collapse
I got updated to 1.0.0.6.. I went from the '0' version to 'I'. Shrug.
fastboot boot recovery.img nor fastboot boot recovery recovery.img works... sigh.
I do have the full OTA. OnePlus7TOxygen_14.I.08_OTA_008_all_1911061912_10a180d3.zip. Dunno if anyone needs it.
I am on Linux. I used mktool to unpack and repack. I set all the flags properly between entered fastboot and Flash the new image to recovery as specified. device immediately hangs. I hold the keys to enter fastboot mode again and of course I can't run shell as ADB is not available in fastboot.
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
morback said:
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
Click to expand...
Click to collapse
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
morback said:
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
Click to expand...
Click to collapse
I have not fiddled around with fastboot ROMs. But you should be able to download your OOS rom with Oxygen Updater.
If someone else haven't uploaded the stock recovery, you'll need to use a tool like this to extract the payload bin inside the zip. The recovery is named recovery.img
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
On the screen I get: your device is corrupted and cannot be trusted and cannot reboot
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
blackhawk said:
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
Click to expand...
Click to collapse
Thanks for answering
The device may boot into a bootloader or an error on the screen
EranG90 said:
Thanks for answering
The device may boot into a bootloader or an error on the screen
Click to expand...
Click to collapse
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
craznazn said:
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you
I have now done that and the screens are in the same condition as in the pictures
It is good? Should I keep waiting? (I don't know really what to do, I am new at this. I don't know even if the device got the commend from the pc)
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
djsubterrain said:
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
Click to expand...
Click to collapse
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
EranG90 said:
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
Click to expand...
Click to collapse
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
You need to have previously allowed bootloader unlocking in your developer options (see below)
djsubterrain said:
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
Click to expand...
Click to collapse
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
EranG90 said:
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
Click to expand...
Click to collapse
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
EranG90 said:
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
Click to expand...
Click to collapse
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
djsubterrain said:
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
Click to expand...
Click to collapse
Really really thank you
I have tried all 4 commands (-w, --setactive=a/b and reboot)
all of them after I turn off and back on my phone show me the bootloader
can you send me a link to how I use the MSM tool to restore the phone to factory settings?
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
craznazn said:
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
Click to expand...
Click to collapse
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
EranG90 said:
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
Click to expand...
Click to collapse
try
Code:
fastboot reboot fastboot
and what shows up?
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
craznazn said:
try
Code:
fastboot reboot fastboot
and what shows up?
Click to expand...
Click to collapse
thank you for answring
that what show up:
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Shooter7889 said:
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
Click to expand...
Click to collapse
Thank you
I will try anything to fix that but I am new in all this
Where I am download the flashall.bat? where I save it? How to run it?
I have download the global version for onplus9pro. What I need to do with it?
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Shooter7889 said:
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Click to expand...
Click to collapse
And honestly, you could prob just download the zip I mentioned, the first one just to get the flashall.bat, and just extract it, plug ur phone in(in bootloader mode) and click the flashall.bat. It would put the EU version of OS on your phone. Use cld then use the loavl update in system settings to switch to ur variant after. Much easier.
Trying to root my phone but can't find a boot.img for the following- BD: 11.0.2.BE82CF MODEL:BE2015-METRO by T-Mobile. Thanks in advance for the help.
yuhh_chris said:
Trying to root my phone but can't find a boot.img for the following- BD: 11.0.2.BE82CF MODEL:BE2015-METRO by T-Mobile. Thanks in advance for the help.
Click to expand...
Click to collapse
Dude I been looking for this one for a while now bro... You brick your phone?
yuhh_chris said:
Trying to root my phone but can't find a boot.img for the following- BD: 11.0.2.BE82CF MODEL:BE2015-METRO by T-Mobile. Thanks in advance for the help.
Click to expand...
Click to collapse
If I had that version I'd do it myself. I was on the Metro by T-Mobile version but changed the firmware to the Global version to install a GSI Rom but I can still help you. The easy way is to use the Android 10 twrp.img for this device. Of course oem unlock should be enabled in developer options. You can either use ADB to reboot to bootloader or power off your device then hold the power + volume up and down together and it'll reboot into bootloader. Assuming you have adb and fastboot installed correctly on your PC and have added the binaries to path, just go into the folder where the twrp.img is, hold down shift then right click and choose open PowerShell here. Enter the command fastboot boot twrp.img. Once you boot into twrp you'll either need the Magisk zip on your SD card or you'll have to use adb sideload to flash the zip. You can't use the Magisk zip if it's stored somewhere in your internal storage because the data is encrypted. Honestly everything is much easier and better if you flash the Global firmware to the Metro by T-Mobile device. Here's the link to an already modified msm download tool. Msm download tool
sdflowers32 said:
If I had that version I'd do it myself. I was on the Metro by T-Mobile version but changed the firmware to the Global version to install a GSI Rom but I can still help you. The easy way is to use the Android 10 twrp.img for this device. Of course oem unlock should be enabled in developer options. You can either use ADB to reboot to bootloader or power off your device then hold the power + volume up and down together and it'll reboot into bootloader. Assuming you have adb and fastboot installed correctly on your PC and have added the binaries to path, just go into the folder where the twrp.img is, hold down shift then right click and choose open PowerShell here. Enter the command fastboot boot twrp.img. Once you boot into twrp you'll either need the Magisk zip on your SD card or you'll have to use adb sideload to flash the zip. You can't use the Magisk zip if it's stored somewhere in your internal storage because the data is encrypted. Honestly everything is much easier and better if you flash the Global firmware to the Metro by T-Mobile device. Here's the link to an already modified msm download tool. Msm download tool
Click to expand...
Click to collapse
I did get the global since i had bricked my phone but then updated it to android 11 seeming as i couldnt find a boot img, I can go back and flash it to that one if that link you sent to me is already rooted.
yuhh_chris said:
I did get the global since i had bricked my phone but then updated it to android 11 seeming as i couldnt find a boot img, I can go back and flash it to that one if that link you sent to me is already rooted.
Click to expand...
Click to collapse
No, it's not already rooted. It's just the stock firmware for the global version 10.5.5. I do have the boot.img for it as well as 11.0.4 global. Here they are if you need them.OnePlus boot.img
hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
afer download frimware copy to your phone then update via ota local update
topadstore said:
afer download frimware copy to your phone then update via ota local update
Click to expand...
Click to collapse
Have u tried recalibrate fingerprint?
kaiwayne said:
Have u tried recalibrate fingerprint?
Click to expand...
Click to collapse
The fingerprint will not work. Root the device. There are other ways to fix this problem
topadstore said:
The fingerprint will not work. Root the device. There are other ways to fix this problem
Click to expand...
Click to collapse
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
topadstore said:
hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
Click to expand...
Click to collapse
You do not need to patch boot.img and flash it, only patching init_boot.img is needed.
kaiwayne said:
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
Click to expand...
Click to collapse
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
ugene1980 said:
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
Click to expand...
Click to collapse
Yes but grayed out
kaiwayne said:
Yes but grayed out
Click to expand...
Click to collapse
Did you lock the bootloader again?
Lossani said:
Did you lock the bootloader again?
Click to expand...
Click to collapse
Dont need to ask the same thing everywhere,
Locking bootloader after you rooted = Brick....
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
VladimiroCampus said:
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
Click to expand...
Click to collapse
The other thing that bothers me is that if you have Google Assistant enabled, it breaks voice dictation. So you can't voice text if you want Google Assistant enabled. So sad!
May be interesting testing this phone with custom roms, like CRdroid or similar... a monster of power but with an operating system with some bugs it's a real shame....
topadstore said:
after finished all setting install magisk apk and patch
init_boot.img and boot.img
Click to expand...
Click to collapse
Thanks for the detailed guide.
But I came across this guide from Mr.PvT https://forum.xda-developers.com/t/root-red-magic-8-pro-v3-18.4556901/
He mentioned "Note: Absolutely do not patch the boot file, you will have a continuous boot error"
I am no expert in this, but will patching the boot.img by Magisk causing the situation Mr.PvT mentioned above?
thanks in advance!
i only patched the init_boot and that is all that is needed
Hi
Fingerprint not work with root? Any solution?
Then which is the command to relock the phone? Uninstalled root and.....
It's pretty easy to root the phone, but it's a more finicky to keep lock screen and finger print functionality. This root guide is more comprehensive and if you read the whole thread you will have success.
What worked for me: Working lockscreen after unlocking + rooting
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin) Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first...
forum.xda-developers.com
Took me a few tries to do it
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Dont_touch7 said:
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Click to expand...
Click to collapse
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
DarkestSpawn said:
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
Click to expand...
Click to collapse
Based on experience, you just have to run the command:
fastboot flash init_boot <patched_file>.img
It will automatically be flashed on the current active slot.