Database Develop

[Summary] Rooting the Z5

Hi there,
I think we should make a simple thread to sum up everything we know about root, since the main talking thread is long, here are the main informations:
Xperia Z5:
- No locked bootloader root yet
- AndroPlusKernel: http://forum.xda-developers.com/xperia-z5/development/kernel-andropluskernel-v1-t3246100
- TWRP here http://forum.xda-developers.com/xperia-z5/development/twrp-2-8-7-0-z5-rootable-kernel-t3240032
- CWM booting but not usable: http://forum.xda-developers.com/xperia-z5/development/recovery-clockworkmod-recovery-sony-t3249782
- Unlocked BL dirty rooting available and working as intended: http://forum.xda-developers.com/xperia-z5/development/dirty-root-solution-unlocked-bl-t3233274
- Dumped original firmware: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
- Xposed works but you need to let it bootloop a few times
Xperia Z5 Compact:
- No locked bootloader root yet
- Zombie Kernel testing release here: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
- Unlock bootloader root available (http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524)
- Prerooted firmware available for unlocked BL: http://forum.xda-developers.com/z5-...-rooted-32-0-5-32-firmware-one-click-t3231520
- Xposed doesn't work with prerooted firmware
Currently we need to:
- Compile Zombie Kernel for Z5
- Improve TWRP support
- Create prerooted-firmware
- Most obviously and most hardly, find exploit for Locked BL root
Ok I'm not an Xperia pro, just got my first one few days ago, but still a android and linux geek, so if there is mistakes in my post, or update I haven't seen, notify me

Knux14 said:
- Maybe dump the original firmware ?
Click to expand...
Click to collapse
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397

Need root for Z5, thx for efforts.

Uclydde said:
If I'm not mistaken, I think it already has: http://forum.xda-developers.com/xperia-z5/general/ftf-files-sony-xperia-z5z5-dual-t3214397
Click to expand...
Click to collapse
Updated

Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.

nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
You are the man, you saved me
my phone works now with root access

nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Huge thanks, But I can't get it working...
I open BL, I fastboot flashed the kernel, then I fastboot booted on the recovery (Which doesn't show a black screen as expected but a real non-fully-working twrp for me) and I tried to install Supersu but I write an error then...
EDIT: Kinda glitchy to do, but works.
If anyone has Xposed working, please make a tutorial

Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.

Most android devices have either already unlocked BL or you have to. For example, Nexus 5 needed to unlock the BL, as well as the OnePlus One, but those devices don't contain DRM so you don't loose anything when unlocking

nilezon said:
Test kernel for Z5:
https://mega.nz/#!15oSGLiA!N-lOlfn8RS9_gN_GcVJrFzXg21nzL1xDdt1xKujl9is
This is stock Z5 kernel modified to disable Sony RIC, dm verity, etc.
It should work together with the Z5C rooting solution:
http://forum.xda-developers.com/z5-compact/development/dirty-root-solution-unlocked-bl-t3230524
Please report back.
Click to expand...
Click to collapse
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)

harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did not had to :/

You guys work fast!
Unsure whether to root myself yet,
Kind of wouldn't mind being able to connect a ps3 pad instead of
Ps4 using the sixaxis app

I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.

Falenone said:
I'm still confused here. I don't see clear instructions for root process, probably because this is my first Xperia device. Neither do I know if using this modded stock kernel and doing this adb thing few posts back will break the DRM thingy and camera features or not.
Click to expand...
Click to collapse
There is nothing clear enough for beginner yet. Sooner or later there will be a TWRP fully working and it will be easy.
Try the dirty method, but don't do things that you are not sure that will work. Ask us if needed

I don't want to lose features because of unlocked bootloader. I guess I'm going to survive without root til there's TWRP and pretty much flash n go root

You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...

Knux14 said:
You will maybe never be able to root without loosing feature. Xperia devices work like this for ages..
The only way you could would be that we find a flaw in Android, which could either arrive soon, or never...
Click to expand...
Click to collapse
Ages means..? I know that the Z1 is not so fresh anymore but we were able to root 4.2/4.4.4/5.1 without losing anything with locked BL. (I know nothing except following tutorials)
Sent from my E6653

Yes because there were security holes in android. For now we havent found anything yet in this version

harfot said:
Worked in second attempt. First time reboot into recovery. New fastboot boot booted into black screen.
In following sequence it was necessary to add destination file name,
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/
failed to copy 'SuperSU-v2.51.zip' to '/data/media/0/': Is a directory
D:\DOWNLOADS\Sony\Xperia\Z5\Fastboot>adb push SuperSU-v2.51.zip /data/media/0/SuperSU-v2.51.zip
9055 KB/s (3989636 bytes in 0.430s)
Click to expand...
Click to collapse
I did boot into TWRP (it was like tablet mode) mounted all partitions to be sure, flashed SuperSU from external sd. It is working. Thank you all

ChrissehB said:
Okay so this is my first Xperia device and my second android device (used to have a Nexus 5 so rooting was simple). Can anyone ELI5 the root situation?
I understand that the TA partition contains DRM keys to make X-Reality etc work and that unlocking the bootloader will wipe this TA partition and the features will stop working. My main confusion comes from - if other lollipop devices have rooting methods for locked bootloaders, why don't these methods work on the Z5? Sorry if this is extremely obvious and I'm an idiot.
Click to expand...
Click to collapse
Google "Verified Boot Android" .. there is almost 100% probability that locked bootloader root will never be achieved, because of this security feature. Verified Boot was introduced in KitKat, but almost nobody used it in so strict mode implementation... Until now, no single firmware using Verified Boot was ever rooted without either custom kernel (must unlock bootloader) or leaked engineering bootloader (try ask Sony engineers for it).

Dm-verity again

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!

Honor 5C Fastboot Loop (image verification error)

I have been using my Huawei Honor 5C for 6 month. Week ago, I decided to try updating my firmware from android 6 to 7. I have bricked my phone at all, as FRP was locked. I bought a DC Phoenix license and flashed some files, which I recieved from DC Support.
Everything was OK, but two days ago I tried to root my phone and install TWRP. When I try to do that, it gives me:
Fastboot: FAILED (remote: image verification error)
Contacting with DC Support doesnt give any help, as they dont know why it happens.
Did smb has the same problem as mine? If so, how did you solve it? I dont wanna buy DC license for a second time

SonicAndreev said:
I have been using my Huawei Honor 5C for 6 month. Week ago, I decided to try updating my firmware from android 6 to 7. I have bricked my phone at all, as FRP was locked. I bought a DC Phoenix license and flashed some files, which I recieved from DC Support.
Everything was OK, but two days ago I tried to root my phone and install TWRP. When I try to do that, it gives me:
Fastboot: FAILED (remote: image verification error)
Contacting with DC Support doesnt give any help, as they dont know why it happens.
Did smb has the same problem as mine? If so, how did you solve it? I dont wanna buy DC license for a second time
Click to expand...
Click to collapse
Try installing the stock rom clean. It might help.

Shubho20 said:
Try installing the stock rom clean. It might help.
Click to expand...
Click to collapse
I have already tried. It doesnt help.

SonicAndreev said:
I have already tried. It doesnt help.
Click to expand...
Click to collapse
You probably messed up like me.
I think you should download full update of the 6.0 firmware and then ^take out^ boot.img recovery.img. And system.img. Then install it through adb. 1.boot 2.recovery 3.system. It should help.
Someone told me about it in Nem-L21 Nougat tread.
I left my in Huawei seewis centre. They exchanged motherboard - it Was easiet way for them.

ConradP said:
You probably messed up like me.
I think you should download full update of the 6.0 firmware and then ^take out^ boot.img recovery.img. And system.img. Then install it through adb. 1.boot 2.recovery 3.system. It should help.
Someone told me about it in Nem-L21 Nougat tread.
I left my in Huawei seewis centre. They exchanged motherboard - it Was easiet way for them.
Click to expand...
Click to collapse
I have already tried it. I downloaded NEM-L51C432B130 FullOTA, unzipped it using Huawei Extractor app and flashed boot, cust, system, recovery and recovery2. After that, i rebooted my phone and had a critical error screen, which said me that I need to flash system partition (but I have flashed it). I also tried flashing rollback first, but it gives the same error. Finally, I fully flashed beta rom of android 7 and the phone has booted. The problem is that one archive of Android 7 rom has extra "data" folder, which contains system apps such as Bluetooth, Finger Scanner, Update Utility, EMUI Explorer and some others. Without them I cant use my phone, cause I often use these options. This archive with "data" folder needs to be flashed through TWRP, but I cant install TWRP on my phone (see thread question). I dont know what to do...

SonicAndreev said:
I have already tried it. I downloaded NEM-L51C432B130 FullOTA, unzipped it using Huawei Extractor app and flashed boot, cust, system, recovery and recovery2. After that, i rebooted my phone and had a critical error screen, which said me that I need to flash system partition (but I have flashed it). I also tried flashing rollback first, but it gives the same error. Finally, I fully flashed beta rom of android 7 and the phone has booted. The problem is that one archive of Android 7 rom has extra "data" folder, which contains system apps such as Bluetooth, Finger Scanner, Update Utility, EMUI Explorer and some others. Without them I cant use my phone, cause I often use these options. This archive with "data" folder needs to be flashed through TWRP, but I cant install TWRP on my phone (see thread question). I dont know what to do...
Click to expand...
Click to collapse
This phone is harder to master with custom roms then my previous LG G2.

ConradP said:
This phone is harder to master with custom roms then my previous LG G2.
Click to expand...
Click to collapse
I know. I has Nexus 7 and it has the easiest way for flashing firmware. I dont understand why Google (or Huawei for EMUI) didnt preinstalled a small extended board with stock ROM for rescue purpose. So that, if somebody bricked his phone, he could be able to fastly rescue his phone and make it work. The worst problem of fastboot is that fastboot partition can be damaged, while you flash something. Anyway, android devs are better made FRP lock, which is useless and can be easily removed... Or they are better made some new androids every 3-6 month, wow, thats cool (no)
This problem had no solution yet. There is only one way, how I could make my phone fully-workable - wait for a stable ROM of Android 7 abd flash it through fastboot.

SonicAndreev said:
I know. I has Nexus 7 and it has the easiest way for flashing firmware. I dont understand why Google (or Huawei for EMUI) didnt preinstalled a small extended board with stock ROM for rescue purpose. So that, if somebody bricked his phone, he could be able to fastly rescue his phone and make it work. The worst problem of fastboot is that fastboot partition can be damaged, while you flash something. Anyway, android devs are better made FRP lock, which is useless and can be easily removed... Or they are better made some new androids every 3-6 month, wow, thats cool (no)
This problem had no solution yet. There is only one way, how I could make my phone fully-workable - wait for a stable ROM of Android 7 abd flash it through fastboot.
Click to expand...
Click to collapse
Yes, I totally agree.
And I am waiting for the Nougat release - after the beta I am missing some options - like dualscreen.

hey bro just unlock bootloader....(because this error for only bootloader lovked)

sahildutt said:
hey bro just unlock bootloader....(because this error for only bootloader lovked)
Click to expand...
Click to collapse
What? Explain your problem more.

Magisk and Bootloader

Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You

Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.

Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?

inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.

1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.

Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.

Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again

I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.

Ok.Thank you very much.I will learn more ...

Question [NE2215] QUALCOMM crashdump mode

Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps

I did the same mistake thinking it would work like it would on A12 and ended up sending it in to oneplus to reflash.

In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?

unsafe8989 said:
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
Click to expand...
Click to collapse
yes full ne2215. quite sad knowing we don't even have proper access to the tools to recover our own phones yet. luckily i kept my op8 for a situation like this.

ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
you are sol. i already told you guys that you'll brick your phone if you use magisk method when updating os versions.

ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
If you did unroot completely you can try to boot into EDL mode, in doing so I managed to flip the boot slot and get mine to boot when I was stuck in crashdump mode.
I updated to C.20 yesterday. The process is to unroot completely with image restore, reboot, then let the the update fully install and reboot. You will update fine but be unrooted. Then you boot a patched boot from bootloader and root directly from Magisk.
Do not forget the reboot after uninstalling Magisk before updating.

I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?

ltw5ki said:
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
Click to expand...
Click to collapse
I'm genuinely not sure how to flip the slot on purpose, it happened to me while I was trying the button combination for EDL mode. I believe you have hold all three buttons (Power, Vol Up&Down) until it restarts, it should vibrate but be a black screen and you can plug the USB in from there to see a port 9008 on the PC. This is very generalized but there are more details all around the forum here.
I will say I believe when it flipped, it booted and I saw the oneplus screen for a split second, the screen sort of glitched, and it immediately rebooted from black screen back to bootloader. I think the switch occurred then.

Also is that from a powered off state or is it possible to do with the phone being on?

Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.

Quantumrabbit said:
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Click to expand...
Click to collapse
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?

Prant said:
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Click to expand...
Click to collapse
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now

Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.

Prant said:
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Click to expand...
Click to collapse
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!

unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
your jumping around probably screwed up some partition size. I did not restart for the c20 ota and have no issues.

unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.

Appreciate your guys input, I'll make sure to be extra cautious! Phone comes in today, fingers crossed I successfully update to C20 and root! Lol.

Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
One last question, do you remove all your modules first reboot then unroot and reboot?

Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
Technically that's on you. I gave a warning that you will brick if you don't fully unroot for c19.

Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
I posted the c20 boots and how to flip the boot so go try it out.