If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
veroby said:
If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
Click to expand...
Click to collapse
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
k.s.deviate said:
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
Click to expand...
Click to collapse
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
veroby said:
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
Click to expand...
Click to collapse
I did do this last night as I was greeted with the same Verity error after flashing the beta.
k.s.deviate said:
I did do this last night as I was greeted with the same Verity error after flashing the beta.
Click to expand...
Click to collapse
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Seems a little weird as the fastboot oem disable_dm_verity commands have only just come onto xda this morning. Seems weird because its working for most which would assume most are on 4.0.2 firmware. Meaning they havent update for a long time.
Updated - I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither. Thankyou..:good:
veroby said:
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Click to expand...
Click to collapse
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
k.s.deviate said:
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
Click to expand...
Click to collapse
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
veroby said:
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
Click to expand...
Click to collapse
Glad my explanation helped.
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
xtacb4 said:
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
Click to expand...
Click to collapse
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
veroby said:
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
Click to expand...
Click to collapse
Hi, last message mine in this thread talking about this here, don't want to be offtopic, I purchased it yesterday, came home installed the usual (twrp[i love how fast the backups are made], CM14.1) and delivered the Nexus 6 to a friend (he bought it from me).
Thanks!
Related
This is a weird one... for me at least.
I'm running on a two month old nightly because flashing a zip in either recovery or fastboot has been failing since then. I thought that maybe I was getting bad downloads, or my recovery needed to be updated. Then I got lazy and let it sit for a while because things have been working well enough that my weekly/bi-weekly nightly updates weren't all that pressing.
Then I heard 4.4.4 was a thing and decided to give it a go again. Well, updates still fail in TWRP without any specific error. Weird. Let's try fastboot! Nothing like the good-old brute-force method: Sending... FAILED: Remote not allowed. The hell...?
*does research*
This literally shouldn't be happening. Bootloader is unlocked. I have root. I'm 1.54 hboot S-ON (factory default from a swap, I got screwed). I'm also not having any issues with drivers or OS problems either. And yes, I'm running CMD as admin, USB debugging is enabled and linked to the PC I'm doing the work on.
By all accounts, I should NOT be having this problem. What gives? Halp? I'll provide anything you need. I'm not even going to bother wasting my time with ADB/Sideload because I'm likely going to get the same errors/failures.
ansuzThurisaz said:
This is a weird one... for me at least.
I'm running on a two month old nightly because flashing a zip in either recovery or fastboot has been failing since then. I thought that maybe I was getting bad downloads, or my recovery needed to be updated. Then I got lazy and let it sit for a while because things have been working well enough that my weekly/bi-weekly nightly updates weren't all that pressing.
Then I heard 4.4.4 was a thing and decided to give it a go again. Well, updates still fail in TWRP without any specific error. Weird. Let's try fastboot! Nothing like the good-old brute-force method: Sending... FAILED: Remote not allowed. The hell...?
*does research*
This literally shouldn't be happening. Bootloader is unlocked. I have root. I'm 1.54 hboot S-ON (factory default from a swap, I got screwed). I'm also not having any issues with drivers or OS problems either. And yes, I'm running CMD as admin, USB debugging is enabled and linked to the PC I'm doing the work on.
By all accounts, I should NOT be having this problem. What gives? Halp? I'll provide anything you need. I'm not even going to bother wasting my time with ADB/Sideload because I'm likely going to get the same errors/failures.
Click to expand...
Click to collapse
what rom are you talking about
what version of this rom is currently installed on your phone
what version of twrp is on your phone
don't know what you are trying to do from fastboot, custom rom MUST be flashed from custom recovery.
alray said:
what rom are you talking about
what version of this rom is currently installed on your phone
what version of twrp is on your phone
don't know what you are trying to do from fastboot, custom rom MUST be flashed from custom recovery.
Click to expand...
Click to collapse
Oh my god. I'm such a dolt. Totally forgot that fastboot only flashes official zips and smaller .bin and .zip packages.
I updated TWRP to 2.7.1.1 and flashed the newest nightly and gapps package without issue.
I think it was all because my TWRP was outdated. Thanks for the reminders, fixed things right up and honestly, 99% of my problem was over-thinking things. Derp.
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.
Same thing here, always installation failed
Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables
Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???
@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...
Same problem and I didn't find any solution yet.
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli
It worked for me mate! Thank you
k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...
jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?
Worked for me too, thanks!
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader
wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.
Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse
whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.
Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
I followed this:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
with this option:
https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
I went with the G8441_47.1.A.8.49_CE1.rar firmware, as it seems most compatible. THANK YOU j4nn! Marvelous and relatively simple procedure . Flashed with newflasher (Flashtool doesn't work with XZ1 Compact?).
Rooting worked, but when the phone is on battery it never goes above 20%. It was 100% before and 20% immediately after flashing. Red warning light is on, unless the phone is off and plugged in.
So. I missed the part about omitting persist* and Qnovo*. Somehow my attest keys didn't break (PROVISIONED in service test).
It looks like what happened is I replaced the battery config? Info:
https://forum.xda-developers.com/xperia-x/help/flashed-xperia-x-low-battery-t3441158
https://forum.xda-developers.com/xperia-xa/help/strange-battery-issue-jumping-33-3-0-t3688178
Can't repair with Xperia Companion because unlocked bootloader (no way it could be re-locked, is there? My DRM keys are backed up).
Someone wrote about wiping the Qnovo partition. Any advice on how to do this? fastboot format Qnovo didn't work (looks like it doesn't find that partition)
Unrelated, and sorry if this is a total n00b question, but where on earth is TWRP compatible with this device/FW? j4nn's rooted kernel doesn't play well with TWRP install, so I'm hoping to just fastboot boot recovery.img. I can't find any recovery.img that works - I tried several of these:
https://androidfilehost.com/?w=files&flid=232371
But it just gets stuck on SONY logo, needing soft reset.
ben_pcc said:
Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
Click to expand...
Click to collapse
Try this - https://developer.sony.com/develop/open-devices/get-started/flash-tool and report back.
WORKED. Flashed the US firmware with "Software Update Content Erase", battery now seems to be working normal again. Thank you so much!
Another question: I'd love to set this phone up to work with fastbooting TWRP (so, not a TWRP install on the phone). Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods? Preferably compatible with https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
ben_pcc said:
Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods?[/url]
Click to expand...
Click to collapse
Why use such old FW? If you're sticking with Oreo then you want the FW ending .20 for the latest. An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Because I didn't know better. Emma gave me 47.1.A.16.20, I'll stick to that
Would you mind sharing what *img file exactly would work with fastboot that way? I had no trouble finding it for the Z5 compact, but one that would work here is eluding me. For example, if I run:
fastboot boot twrp-3.2.3-0-lilac-1.img
The phone boots up to SONY logo (black on white background) and stays there, unresponsive. Got the file from https://androidfilehost.com/?w=files&flid=286271
ben_pcc said:
Would you mind sharing what *img file exactly would work with fastboot that way?
Click to expand...
Click to collapse
Have you missed this post, which is linked to in the threads you've posted links to? - https://forum.xda-developers.com/showpost.php?p=79880858&postcount=1029
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
ben_pcc said:
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
Click to expand...
Click to collapse
From the last page - https://forum.xda-developers.com/showpost.php?p=83844543&postcount=1657
Although I would simply install the latest and use one of the unrooted kernels then root it with Magisk.
Hmm. I was aware of that. I tried several of the twrp*.img files, they all get stuck booting on the SONY logo.
Are you sure this is true:
An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Click to expand...
Click to collapse
I'm wondering if a FW update would solve the TWRP booting problem.
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
ben_pcc said:
Are you sure this is true:
Click to expand...
Click to collapse
I know it used to be. Done a bit more searching for you https://forum.xda-developers.com/search/thread/3706704?query=fastboot twrp, and found this command...
Code:
fastboot reboot bootloader
fastboot boot twrp-3.3.1-0-lilac-pie-5.img
...I've just tried it, in fastboot mode and it booted TWRP.
ben_pcc said:
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
Click to expand...
Click to collapse
Starting over is always painful but sometimes it's the best option. I have a rooted stock ROM and TWRP installed with no issues, on Oreo or PIE so if you do, then I suggest backing up the essentials and starting again.
YES. Thanks so much SXUsr! You were right after all, I tried a few different TWRP images and they work now. What I was missing was fastboot reboot bootloader. My Z5 Compact doesn't require it.
There was one more thing I had to figure out: data partition is encrypted, and for my (Android 8.0.0) device the TWRP you mentioned fails.
twrp-3.2.3-0-lilac-1.img on the other hand asks for my unlock pattern when it boots up, and backs up fine.
Now that I have a complete backup I'll consider my next steps (possibly flashing a new ROM. Honestly 8.0.0 seems fine, we'll see). Thanks again!!
ben_pcc said:
YES. Thanks so much SXUsr!
Click to expand...
Click to collapse
You're welcome. I've always installed it on this phone so wasn't aware of that command myself either, so we've both learnt something.
Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links):
EU NE2213_11_A.12
Stock boot.img - link
EU NE2213_11_A.10
Stock boot.img - link
Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come.
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.