Related
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
OnePlus7TOxygen_14.I.05_OTA_fastboot
Code:
ro.vendor.build.date=Wed Sep 25 21:54:29 CST 2019
ro.vendor.build.date.utc=1569419669
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1909250940:user/release-keys
ro.vendor.build.id=QKQ1.190716.003
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=1909250940
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T
Fastboot Commands :
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
Credits :
jamflux
Regards,
acervenky
reserved
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
RohanAJoshi said:
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
Click to expand...
Click to collapse
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
acervenky said:
Download the attachment, and flash it using this command :
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
OK, I will try this and report you back soon.
acervenky said:
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
RohanAJoshi said:
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
Click to expand...
Click to collapse
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
acervenky said:
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
Click to expand...
Click to collapse
which file should i dowload ?
stock or mod ?
RohanAJoshi said:
which file should i dowload ?
stock or mod ?
Click to expand...
Click to collapse
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
acervenky said:
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
Click to expand...
Click to collapse
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
RohanAJoshi said:
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
Click to expand...
Click to collapse
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
How2Kritin said:
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
Click to expand...
Click to collapse
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
cultofluna said:
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
Click to expand...
Click to collapse
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
acervenky said:
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
Click to expand...
Click to collapse
I did, initially but it said that the /system, /vendor and /product partitions couldn’t be mounted. When I tried to restore I got stuck in the fastboot mode. After that, I’ve used your file and got stuck with the qualcomm crashdump mode.
FIXED
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
I wonder, if a T-Mobile 7T is unlocked can we use this method to install the international firmware on it?
Is this for EU Model?
Hot-Proton said:
Is this for EU Model?
Click to expand...
Click to collapse
No, Global!
Regards,
acervenky
Ok that is bad. Wait for EU Version.
for T-Mobile no, I messed up mine, it boots but no wifi and data. I did a remote session with oneplus but they can't fix it, they don't have the firmware for the tmobile version, unless if someone has already patched the MSM, but sadly nothing yet
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
How2Kritin said:
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
Click to expand...
Click to collapse
how did you reach out to him, just wanna know if there's a fix for my wifi and data no connections, T-Mobile unlock bootloader, tried flashing the modem from here but no effect and when I tried deleting it, sim card cannot be detected
Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.
Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !
tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.
Worked to my, Thnx
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk
Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !
sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse
Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.
Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.14 HD65AA (GLOBAL)
Only for OOS 10.0.14 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_14.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_14.img
When finished type
Code:
fastboot reboot
patched boot.img download: https://drive.google.com/file/d/1wZ2TyIi0uUfbRTxPYK_imURBVjHqaA_f/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1R90vvdJEe6NkL2FdqSvuxtk18SmWHYUc/view?usp=sharing
It's still telling me "Root access is not properly installed on this device". I have an unlocked bootloader and OOS 10.0.14 HD65AA (GLOBAL), is there something I'm missing?
EDIT: tried a different root checker and I'm fine. Please disregard.
daaper said:
"Root access is not properly installed on this device"
Click to expand...
Click to collapse
Install Magdisk Manager
Thanks and much appreciate for the patched file!
Hello. No internet after booting.
Hey everybody.
So I've recently got this Redmi Note 8 (2021) and figured I'd root it.
After the week of waiting to unlock the bootloader, I did the next step to install Magisk.
Due to the lack of custom recovery, I patch the bootimage, and flash it with fastboot.
However after this, the phone is stuck on fastboot, so I guess something is missing.
I also tried the canary versions, but no success yet.
Did anybody succesfully instal Magisk on this phone? Or some other type of root?
I'll just answer my own question here.
Android 11 MIUI devices need enabled verification in boot.img AVBv2 signature
This pull request will fix it (for me): https://github.com/topjohnwu/Magisk/pull/4975
Trying the vvb alpha worked for me.
You should flash first vbmeta.img with this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then flash the previously modified boot image with Magisk:
fastboot flash boot boot.img
pierzale said:
You should flash first vbmeta.img with this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then flash the previously modified boot image with Magisk:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I heard about this vbmeta at several occasions, but I haven't found a proper resource or download location for it.
How do I create or download a patched vbmeta?
Other than that, the solution I posted does work for rooting my device. But I think flashing vbmeta might open some options up for me like a custom recovery.
pierzale said:
You should flash first vbmeta.img with this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then flash the previously modified boot image with Magisk:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hi.
when ich put that command i became that error:
C:\adb\fastboot.exe: unknown option -- disable-verity
sorry, i made a mistake. got it now
hello can you help me to root
Sure.
Install the newest magisk.
First unlock the bootloader, then patch a boot image with magisk, and flash it to your boot partition with fastboot.
EU&Asia : https://rom.download.nubia.com/Europe&Asia/NX729J/V312/NX729J-update.zip
EU : https://rom.download.nubia.com/Europe/NX729J/V412/NX729J-update.zip
CN : https://ui.nubia.cn/rom/detail/76
CN <-> Global steps : https://forum.xda-developers.com/t/chinese-rom-to-global-rom-tutorial.4452887/
bestman1069 said:
https://rom.download.nubia.com/Europe%26Asia/NX729J/V312/NX729J-update.zip
Does anybody want to trans CN to Global ??
Click to expand...
Click to collapse
Red magic 8 pro plus can it be installed?
Red magic 8 pro plus can it be installed?
I dont know the model no
bestman1069 said:
EU&Asia : https://rom.download.nubia.com/Europe&Asia/NX729J/V312/NX729J-update.zip
EU : https://rom.download.nubia.com/Europe/NX729J/V412/NX729J-update.zip
ISSUE : fingerprint not work . secure not work
Does anybody want to trans CN to Global ??
Click to expand...
Click to collapse
could anybody extract boot and vendor from eu 4.12 image. i could extract payload.bin on my Smartphone , but the extraction of the images did not work. my pc is at the Moment ill :-(
others would also like to root - i think.
thx in hopefully advance.
i need boot patch for red magic 8 pro v3.12
how to root ???? any one root phone
I need root for red magic 8 pro
V3.12
Any one help me
bestman1069 said:
EU&Asia : https://rom.download.nubia.com/Europe&Asia/NX729J/V312/NX729J-update.zip
EU : https://rom.download.nubia.com/Europe/NX729J/V412/NX729J-update.zip
CN : https://ui.nubia.cn/rom/detail/76
CN <-> Global steps : https://forum.xda-developers.com/t/chinese-rom-to-global-rom-tutorial.4452887/
Click to expand...
Click to collapse
here are
boot.img + vbmeta.img from eu 4.12.
i patched with magisk canary 25.2.
Afterwards i flashed boot with the patched_boot_image.
root is not working.
flashed boot_a + boot_b with patched image - also not working.
i used newest adb on win11.
vbmeta flash + disable dmverity also not working.
any ideas?
berndv01 said:
here are
boot.img + vbmeta.img from eu 4.12.
i patched with magisk canary 25.2.
Afterwards i flashed boot with the patched_boot_image.
root is not working.
flashed boot_a + boot_b with patched image - also not working.
i used newest adb on win11.
vbmeta flash + disable dmverity also not working.
any ideas?
Click to expand...
Click to collapse
Same here with 3.12 global/us.
Patched boot.img, tried flashing both a and b, magisk does not show root.
What happens if you patch init_boot.img (if there is one)?
tlxxxsracer said:
What happens if you patch init_boot.img (if there is one)?
Click to expand...
Click to collapse
Have not tried. The stock boot.img is 98MB, the init_boot.img is 8MB. quite a big difference.
Another interesting fact, there is nothing in the boot_b. Tried booting to it, and the phone went blank. Had to hard shut off, boot into bootloader, then switch back to boot_a, then it booted no problem.
If i had to guess, magisk isn't working with android 13 on the magic 8 pro. I even tried the canary version, no luck.
patching init_boot and trying to flash returns with
Sending 'init_boot' (8192 KB) OKAY [ 0.024s]
Writing 'init_boot' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
BoJaXz said:
patching init_boot and trying to flash returns with
Sending 'init_boot' (8192 KB) OKAY [ 0.024s]
Writing 'init_boot' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
Click to expand...
Click to collapse
what is different with this phone?
i rooted all my phones in the last years without problems.
crawling the internet for a solution...
V3.12 global
Not working:
Magisk patched boot.img (Both regular and canary)
Magisk patched init_boot.img (remote flash failed, not allowed for critical partitions)
Working:
Nothing yet
BoJaXz said:
V3.12 global
Not working:
Magisk patched boot.img (Both regular and canary)
Magisk patched init_boot.img (remote flash failed, not allowed for critical partitions)
Working:
Nothing yet
Click to expand...
Click to collapse
V 4.12 global
magisk alpha 25206 no success
BoJaXz said:
V3.12 global
Not working:
Magisk patched boot.img (Both regular and canary)
Magisk patched init_boot.img (remote flash failed, not allowed for critical partitions)
Working:
Nothing yet
Click to expand...
Click to collapse
fastboot flashing unlock_critical
Then you can flash patched init_boot.img
edzchen said:
fastboot unlock_critical
Then you can flash patched init_boot.img
Click to expand...
Click to collapse
fastboot flashing unlock_critical
but....it wiped my phone. really really really not happy about that!!!
Acted like i just unlocked the bootloader!!!
Edit: tried to install magisk after flashing init_boot.img, only installs v1.0 of magisk, 101kb in size, doesn't open, root checker shows no root
lost all applications, all saved keys with authenticators. everything.
do not unlock critical
Bypass charging/charge separation does not work on EU rom v4.12
berndv01 said:
V 4.12 global
magisk alpha 25206 no success
Click to expand...
Click to collapse
ota eu 4.18 is out
Download failed at 50%
multiple tries
Maybe they withdrew it. I'm showing nothing available