I thought I would just casually go through my installed apps and clean some up. I disabled the following...
1. Accessibility Suite
2. Gmail
3. Google TV
4. Google Music
5. Chroma
6. Razor Store
7. Logo+ (Uninstalled)
I then thought to myself that I would probably need the Accessibility Suite for apps that needed that as a permission to work. So I re-enabled it and it updated. I then rebooted and now the phone hangs at the Razor logo. I do have TWRP installed so I can get to that. I also have a complete backup from about a year ago using TWRP which I would like to use as my last resort. I am thinking that by disabling one of the above apps caused this issue. So, can I fastboot and re-enable them using adb? If so what is the command and the name for each app above? I am not an adb guru so the exact commands and names would help. Or if someone can think of another way to get my phone working besides a complete wipe I would greatly appreciate it! I am running MR1 stock with Magisk/art97. I do remember back in the day having a similar problem and I ended up re-flashing the ROM or something and it kept all my data but I think it just repaired the OS or something and that fixed a not booting issue. That was a long time ago so I cannot remember all the specifics but if that rings any bells for anyone as to another way I can approach this I am all ears. Thank you!
Logo+ - you uninstalled it. I dont think any others will prevent booting. If there is no logo, it will sit till it gets one. Reflash logo+ if at all possible. (I have a logo.img in my firmware, but different fone.
Pachacouti said:
Logo+ - you uninstalled it. I dont think any others will prevent booting. If there is no logo, it will sit till it gets one. Reflash logo+ if at all possible. (I have a logo.img in my firmware, but different fone.
Click to expand...
Click to collapse
Thanks for your reply. Logo+ is not a system app and shouldn't have anything to do with the Razor logo when booting up. Logo+ is a 3rd party app that allows to manipulate the colored logo on the back of the phone. For example when a notification comes in Logo+ can light up the colored logo on the back of the phone or make it flash. The app is from here. I've actually uninstalled and reinstalled Logo+ in the past when updating and such with no adverse effects. I can't imagine Logo+ would be the culprit here. What do you think?
I think only logo+ is capable of preventing boot, because your bootlooping. all other apps should NOT cause ANY bootloop, because they do not access anything previous to logo+, your first step in your problem.
Try this...
Logo+ if incorrect in any way will not show. This CAN cause bootloops. No other app you mention can. Perhaps your fone took a silent update, maybe it checked for the Logo+ and 'kicked' you for messing with it. Maybe google decided not to like it, so silently ordered your fone to delete the logo you installed leaving you with no logo+, and until you can see a logo+ your fone will stay there, so try my suggestion, seems your only choice. I have been flashing chips for years so can help, just go with my suggestion, reflash ONLY stock system.img/.bin using your stock flashing application, you'll be glad you did.
Pachacouti said:
I think only logo+ is capable of preventing boot, because your bootlooping. all other apps should NOT cause ANY bootloop, because they do not access anything previous to logo+, your first step in your problem.
Try this...
Logo+ if incorrect in any way will not show. This CAN cause bootloops. No other app you mention can. Perhaps your fone took a silent update, maybe it checked for the Logo+ and 'kicked' you for messing with it. Maybe google decided not to like it, so silently ordered your fone to delete the logo you installed leaving you with no logo+, and until you can see a logo+ your fone will stay there, so try my suggestion, seems your only choice. I have been flashing chips for years so can help, just go with my suggestion, reflash ONLY stock system.img/.bin using your stock flashing application, you'll be glad you did.
Click to expand...
Click to collapse
I will follow your instructions but I am needing some clarification please.
The app Logo+ never came with the stock OS or the Razor Phone 2. It is a separate app made by a 3rd party. So flashing the system.img will not bring back Logo+. So should I first attempt to flash the Logo+ app using TWRP?
If you want me to reflash the stock system.img, I don't believe I have that. How can I obtain this? And could you please provide me with the steps to reflash? Should I use TWRP or fastboot and use Windows adb?
So the Logo+ is only an app. Not a zip. So I don't believe I can flash that. Should I attempt to sideload it? Can I install an app on the phone when the phone cannot boot?
So logo+ IS your prob. Personally I would never use an app to do such work, I'd edit and flash it myself, but hey, you prob know this by now.
Go to (motorola?) Razor support, look for your firmware, it may help if you have phone plugged in while doing so in case they have a detector script to detect firmware for your fone.
Regardless, grab stock offered for your fone. This should also point you in the direction of the correct flashing frmware. once you have them, get back to me.
Or look at what I found using startpage/google:
Need help in flashing stock rom on Razer Phone 2 ! (Stuck in Bootloop)
Hello Everyone , I have ran into a very bad problem and would appreciate some help. I tried rooting my phone (Razer Phone 2 Atnt varient) with the following method...
forum.xda-developers.com
Take your pick, so many stock firmares online here:
Startpage Search Results
www.startpage.com
(I use startpage for these results)
Choose what you believe is for your fone, then read the XDA razor thread I linked to above, I will guide you once you have your files if you still need it, but read the razor thread first
Pachacouti said:
So logo+ IS your prob. Personally I would never use an app to do such work, I'd edit and flash it myself, but hey, you prob know this by now.
Go to (motorola?) Razor support, look for your firmware, it may help if you have phone plugged in while doing so in case they have a detector script to detect firmware for your fone.
Regardless, grab stock offered for your fone. This should also point you in the direction of the correct flashing frmware. once you have them, get back to me.
Or look at what I found using startpage/google:
Need help in flashing stock rom on Razer Phone 2 ! (Stuck in Bootloop)
Hello Everyone , I have ran into a very bad problem and would appreciate some help. I tried rooting my phone (Razer Phone 2 Atnt varient) with the following method...
forum.xda-developers.com
Take your pick, so many stock firmares online here:
Startpage Search Results
www.startpage.com
(I use startpage for these results)
Choose what you believe is for your fone, then read the XDA razor thread I linked to above, I will guide you once you have your files if you still need it, but read the razor thread first
Click to expand...
Click to collapse
The Razer Phone 2 is made by Razer https://www.razer.com/mobile. Motorola makes the Razr which can be confusing.
I don't know how to edit and flash the Logo+ app. Can you do this for me and I'll test? The app is located here https://github.com/CurtisMJ/LogoPlus/releases.
As I understand it as soon as I flash the stock rom it'll put me back to factory settings right? So I'll have to re-personlize my entire phone from scratch. I'd like to leave this as my last resort if possible. So if we can I'd like to flash the Logo+ if you can make that zip for me.
Hi, developer of Logo+ here
I think there's maybe some misunderstanding as to what the app does. It doesn't work on the bootloader splash in any way (this can actually cause failed boots). It's for controlling the RGB on the Razer logo on the back of the device. I named it "Logo+" to avoid any legal issues with caling it "Chroma" since thats a trademark of Razer. The app is entirely user space and is not active during boot. It modifies the lights via sysfs values (with root) that are entirely in RAM so they're cleared on boot.
You can typically just put the .apk in /data/app in recovery mode to install it. I think this may have changed slightly with newer android versions.
Ultimately I don't think Logo+ is needed for or can interfere with boot. I would suggest flashing the system image as suggested for a clean slate.
EDIT: You may end up having to use your last resort backup if you're not keen to loose *too* much data. Not booting is a difficult thing to troubleshoot because there's no feedback as to what went wrong on Android. If its a data thing and not a system thing that is. You could try fastboot flash each system image part to maybe fix any corruption
EDIT2: Take another backup before you do anything though. Titanium back can extract app data from TWRP backups so you can restore your user data at least
CurtisMJ said:
Hi, developer of Logo+ here
I think there's maybe some misunderstanding as to what the app does. It doesn't work on the bootloader splash in any way (this can actually cause failed boots). It's for controlling the RGB on the Razer logo on the back of the device. I named it "Logo+" to avoid any legal issues with caling it "Chroma" since thats a trademark of Razer. The app is entirely user space and is not active during boot. It modifies the lights via sysfs values (with root) that are entirely in RAM so they're cleared on boot.
You can typically just put the .apk in /data/app in recovery mode to install it. I think this may have changed slightly with newer android versions.
Ultimately I don't think Logo+ is needed for or can interfere with boot. I would suggest flashing the system image as suggested for a clean slate.
EDIT: You may end up having to use your last resort backup if you're not keen to loose *too* much data. Not booting is a difficult thing to troubleshoot because there's no feedback as to what went wrong on Android. If its a data thing and not a system thing that is. You could try fastboot flash each system image part to maybe fix any corruption
EDIT2: Take another backup before you do anything though. Titanium back can extract app data from TWRP backups so you can restore your user data at least
Click to expand...
Click to collapse
Thank you for taking the time to chime in here @CurtisMJ. I did end up gettijg it to boot now in partition a. I went into TWRP and switched to partition a and phone boots but no longer has root or magisk. I'm not sure how the partitions work but it looks like there are two that the Razer uses. A and b. And I guess I've been using b since the beginning and since b won't boot now I tried booting off partition a and the phone seems to work as it did. All apps and widgets are in the same place except magisk and phone isn't rooted. I could reflash the system image but the amount of time to re-personalize everything will be extensive. So I just wanted to make sure I did everything I could before that. I'll try copying the apk as suggested and see if that works.
Do you know if there is a way to enable system apps when they've been disabled like I did when phone won't boot? I am in partition a right now and booted and I reinstalled logo+ and saw that all the apps I disabled in OP are back to being enabled. So I am not sure if partition a and b share the same system and user data but everything is exactly what it looks like from partition b. So it is a good chance they share everything except magisk which I guess is flashed at the partition level. Just trying to make sense. Thanks for everyone's time.
So the A-B partition layout is a thing that was introduced by google for more reliable system updates. Effectively the phone has 2 copies of the OS, including system partition,kernel,vendor etc and the phone flip-flops between them on every update, updating the "other" partition to the one its running so if it fails it can boot to the still good one. So you effectively went a system update backwards, but using the same user data partition (or Magisk kept an old copy of the system around). System apps disabled status is stored in /data/system/users/0/package-restrictions.xml which can edited in TWRP with some effort. Magisk is likely flashed to kernel B so you're correct in that its a partition level thing.
CurtisMJ said:
So the A-B partition layout is a thing that was introduced by google for more reliable system updates. Effectively the phone has 2 copies of the OS, including system partition,kernel,vendor etc and the phone flip-flops between them on every update, updating the "other" partition to the one its running so if it fails it can boot to the still good one. So you effectively went a system update backwards, but using the same user data partition (or Magisk kept an old copy of the system around). System apps disabled status is stored in /data/system/users/0/package-restrictions.xml which can edited in TWRP with some effort. Magisk is likely flashed to kernel B so you're correct in that its a partition level thing.
Click to expand...
Click to collapse
Thank you so much for that explanation. That makes a lot of sense. My OS has been MR1 for a long time and OTA has been turned off so I guess there hasn't been any OS updates so there's been no reason to switch between partition a and b I guess. So I guess there's technically been a backup of my OS all this time with the double partition thing which is cool. And I guess I could magisk and root partition a. If I reflash the system image to partition b will that effect partition a?
I think he's talking bootloaders re: a/b partitioning, The point of A/B being if your using 'A' to boot, and you update, the updated BOOTLOADER is flashed to 'B' and when you reboot the f'n, 'B' becomes your main bootloader until next update where that update will use 'A' having been 'emptied' after the previous update sort of thing, I dont have a/b, but this is my understanding of the a/b partitioning,,,?
Opens up the options for dual booting fone with or without magisk, If I had a/b, i'd flash magisk to one and stock to the other...
Pachacouti said:
I think he's talking bootloaders re: a/b partitioning, The point of A/B being if your using 'A' to boot, and you update, the updated BOOTLOADER is flashed to 'B' and when you reboot the f'n, 'B' becomes your main bootloader until next update where that update will use 'A' having been 'emptied' after the previous update sort of thing, I dont have a/b, but this is my understanding of the a/b partitioning,,,?
Opens up the options for dual booting fone with or without magisk, If I had a/b, i'd flash magisk to one and stock to the other...
Click to expand...
Click to collapse
I was thinking the same. I believe I have the opportunity to stick with the working partition which is a, and magisk that. And then for the partition b I could put the official lineage OS on there. My only concern is if lineage had an update does it update both a and b partitions which I would lose my original OS then. I guess I'll have to research.
I think it's safe to assume that when an update takes place, upon reboot, whichever bootloader you WERE using, a OR b, is now empty... it's staring you in the face
Just remember what we agreed on. Once you magisk your current bootloader, make a backup of said bootloader, store it on main computer, because when you flash lineage, your magisk in your current slot will be wiped. Once you have installed Lineage, you will need to boot into fastboot to re-flash magisk, and then use fastboot boot a or b for dual booting until you get an app or sumat to choose in gui what you choose to boot into
What I am thinking I will do for the time being is stick with booting into partition a which is currently not rooted and I am fine with that. At least it works unlike partition b. This is my main phone, my only phone, and I need it to work right now so would rather not risk causing issues flashing stuff. I know enough about flashing to be dangerous.
Currently the official release of lineage for the Razer Phone 2 is still not stable yet according to the forum here. So camera still doesn't work and I need the camera to work. So I'll wait until the camera is fixed which hopefully will be soon.
You stated in your previous post "sumat to choose in gui what you choose to boot into" can you clarify? Are you saying there is a GUI that helps choose what to boot into? Currently I am using TWRP to select partition a or b to boot into. It takes about a minute to load into TWRP but I wouldn't be doing it often. I don't think I really have a use for dual booting.
I appreciate the help. As soon as I am ready to proceed I'll update this post and If you're still around I'll receive your assistance. Thank you for your time.
Related
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Strephon Alkhalikoi said:
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Click to expand...
Click to collapse
First thanks for your answer!
Oh yes for the 1 and the 4, my precedent phone is a Nexus 4, I know these phones and the steps to root/unroot/flash custom rom/recovery etc.. ^^ (I have made that a looooooot of times on my N4 without any problem, with and without NRT)
And this is for that I am surprised by the bad reaction of my Nexus 6 to this simple actions I request to it. (flashing image files)
I don't make anything I don't know, I am scared to brick my phone because I have made something that I master.
Yes I have forgot this point about userdata.img... But this is not a problem, I have resized my partition after flashing my phone with TWRP =)
The point that are interesting for me is the third point. I want to flash a stock image from Google. It's my goal. (I will flash custom ROM when Google will have stopped the update support)
In fact, my principal big problem is why the OTAs have been failed whereas I just start my phone, out of the box, with no modification and no root.
I'm not a specialist but for me, this is not normal when the phone is out of factory.
I will retry to flash another factory image from Google. This time with the flash-all script.
Thanks =)
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
Click to expand...
Click to collapse
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Kermi78 said:
...
But, if a new system update is available, do you think I will get the same problems?
Click to expand...
Click to collapse
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
I have tried this. Thank you for this tip. I did not know Bootloader and OTAs fail depends of /system state. (I have never modified official google image. If I modify a device, it's with a custom rom like CM for example. Without my problem at the first start I would not have modify anything on my phone)
First, I don't have the bootloader message, that's a half good news
I download actually the MRA58N OTA update. Crossing fingers! =)
NLBeev said:
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
Click to expand...
Click to collapse
My goal is to use the official Google Nexus Factory Images with official bootloader, etc.... Exactly the state of a normal Nexus out of the box.
But thank you. In last resort I will think of your tip.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
So after my last try of OTA, 2 times, the update has been succeded!
Just thanks a lot! :good:
I notify this thread resolved
Kermi78 said:
My goal is to use the official Google Nexus Factory Images with official bootloader, etc....
Click to expand...
Click to collapse
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
NLBeev said:
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
Click to expand...
Click to collapse
Oh no that's good for me, I love Android Stock and I hate layers
For the battery... You see, my last phone was a Nexus 4. So the battery life of Nexus 6 is so wonderful for me!
In all cases, my phone is now stock and functionnal. Just that I want for the moment... I will see later for install other roms on it
I want to be simple things.
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
Click to expand...
Click to collapse
DON'T INSTALL THE userdata.img file and this won't happen.
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 ...
Anyone else having a problem with the OTA update failing to install?
It'll keep trying over and over and a notification of failure occurs.
I have to "FORCE STOP" for the "Motorola Update Service" in order for it to stop trying.
The filesize is 150815511.
Looking at https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/ it would seem *1-6 isn't listed, but rather it jumps to *2-3.
I ended up manually doing the "step"s in "flashfile.xml" from "BECKHAM_PPWS29.183_29_1_2_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml.zip" I took from LMSA to Slot-A.
I'm thinking the whole magisk thing was the culprit, but I'm still going to reinstall it.
Again, like last time, at some point Magisk seems to lose it's SU abilities. The thing is, there was NO version change for my device (not magisk) this time, so there was no reason for the "boot" partition to be overwritten.
This time, after rewriting boot, I updated the Manager and Magisk itself.
Next time, I might just copy out the boot partition and diff it with the patch to see if the patch that was written into boot was overwritten.
Hmm, for some reason I wasn't getting the update failure notification, but I'm guessing my system HAD been trying to update, because when I would wake up, my battery would be much lower than usual.
Looking at the logcat, it would appear that an update to PPWS29.183-29-1-9 exists and is trying to be installed.
Back to doing what I did before to make it happen <sigh...>.
vindicatorr said:
Hmm, for some reason I wasn't getting the update failure notification, but I'm guessing my system HAD been trying to update, because when I would wake up, my battery would be much lower than usual.
Looking at the logcat, it would appear that an update to PPWS29.183-29-1-9 exists and is trying to be installed.
Back to doing what I did before to make it happen <sigh...>.
Click to expand...
Click to collapse
What did you have to do before? This update that keeps failing to install seems to have broken my Google Pay.
gullzway said:
What did you have to do before? This update that keeps failing to install seems to have broken my Google Pay.
Click to expand...
Click to collapse
Sadly, what I did before does not make the other boot slot boot.
Essentially, I manually used fastboot to flash the partition images for version *1-6 following the steps in the xml file zipped up.
You can find recovery images from links in other threads dedicated to them or use LMSA (there was no *1-9 version when I last checked) to download it and find the file(s) in the ProgramData folder.
My understanding is that if you see the steps flashing some images specifically to the one dedicated to slot_b, then you want everything else flashed to slot_a (fastboot --set-active=a).
After that, I "think" the incremental upgrade process is supposed to download the diff (~100MB) between the 2 versions, then unpack the payload to slot_b and then set the active slot to "b".
But even when I used twrp to erase ALL partitions listed in the xml, then manually flashed *1-6 to slot a, it should have done a complete copy of slot_a and the upgrade diff to slot_b, but for whatever reason, even though it DOES seem to happen (looking at the logcat output), the boot fails to occur and it tells me something along the lines of trying again or wiping everything. So then I just set the active slot back to "a" (*1-6).
I didn't want to bother wiping out all of my programs and stuff, so I'm just going to wait for the *1-9 recovery and manually flash that.
I saw NO reason for the boot to fail given I wiped everything but userdata (wiped cache as well).
In the meantime I just disabled the motorola update service.
As for Google Pay, I don't know if you got it working before using the "dg.db" method (https://medium.com/@raphnguyen/andr...-work-with-magisk-through-tasker-2468e720b566).
That's what I used to get my card scanned into it.
So, I found the 1-9 version now registers as existing in LMSA.
But again, sadly, for some reason, it still doesn't want to boot that version. I went back to 1-6 for now and posted a reply to a thread on the Lenovo forum regarding this. I'm not sure if their issue is like mine or not.
I really don't want to delete my userdata partition and can't think of why an update would require it.
If you haven't already, you should be receiving a notification that the Stable Android 12 or "S" Build is lurking in the shadows of your Pixel 5a handset. If you're currently on the (only) beta version we received OTA, your update won't inconvenience you for too long, as it weighs in at <4 mb, all in.
Safe Journey's...evnStevn
The factory images are up on Google's developer site, and when I tickled the system update found the 12 upgrade. I'm downloading the factory image now (for rooting with Magisk) then will upgrade to 12. Then more to learn...
CarinaPDX said:
The factory images are up on Google's developer site, and when I tickled the system update found the 12 upgrade. I'm downloading the factory image now (for rooting with Magisk) then will upgrade to 12. Then more to learn...
Click to expand...
Click to collapse
Right-On, I'm not ready for that, the Big League's (yet) as I'm still down here playing T-ball !
CarinaPDX said:
The factory images are up on Google's developer site, and when I tickled the system update found the 12 upgrade. I'm downloading the factory image now (for rooting with Magisk) then will upgrade to 12. Then more to learn...
Click to expand...
Click to collapse
Attempted the upgrade last night, seems there's some new things required if you want to flash the modified boot image and successfully boot. I believe you need to wipe the data partition and also pass along a few flags during install. However, temp root is an option if you want to avoid that for now (I did) by simply booting the image in fastboot vs flashing it. Just FYI!
Edit. Sounds like SafetyNet won't pass yet if you do end up going the permanent route? I could be wrong but I believe that's what's I've read. I just checked on mine and the temporary boot image does seem to so that's good.
If you read this thread you will see how to do it, as done on beta releases. https://forum.xda-developers.com/t/guide-flash-magisk-on-android-12.4242959/ It is possible to achieve permanent root on 12 without wiping the personal data but it is a delicate dance. I have not tried it yet but as I understand it the process is to unroot 11 and at least remove Magisk modules, take the 12 update, boot into bootloader and use fastboot to remove boot verification and replace vbmeta.img, then flash patched boot.img, reboot and reinstall magisk. It seems there is a problem with just flashing the new factory image with the wipe option (-w) removed. Instead of fastboot flashing the patched boot.img it is also possible to directly patch the boot.img from Magisk while temporarily booted from the patched boot.img (via fastboot), again after removing the verification checks. It may be critical as to when the 5a is rebooted or not; it needs to have a normal reboot after the OTA upgrade in order to complete the upgrade, then boot to bootloader for fastboot operations. I am going to go back and make instructions for myself before proceeding, and will do a Titanium backup before doing anything else.
Edit: it appears that some have achieved permanent root and still passed the SafetyNet check. IIRC it was done through the OTA upgrade path but I need to check that. If you are willing to wipe your data then just installing the factory image and then doing the fastboot commands it might work but that is not clear. Too many attempts at root and SafetyNet failed while flailing so hard to know right now if there are good alternatives to OTA.
CarinaPDX said:
If you read this thread you will see how to do it, as done on beta releases. https://forum.xda-developers.com/t/guide-flash-magisk-on-android-12.4242959/ It is possible to achieve permanent root on 12 without wiping the personal data but it is a delicate dance. I have not tried it yet but as I understand it the process is to unroot 11 and at least remove Magisk modules, take the 12 update, boot into bootloader and use fastboot to remove boot verification and replace vbmeta.img, then flash patched boot.img, reboot and reinstall magisk. It seems there is a problem with just flashing the new factory image with the wipe option (-w) removed. Instead of fastboot flashing the patched boot.img it is also possible to directly patch the boot.img from Magisk while temporarily booted from the patched boot.img (via fastboot), again after removing the verification checks. It may be critical as to when the 5a is rebooted or not; it needs to have a normal reboot after the OTA upgrade in order to complete the upgrade, then boot to bootloader for fastboot operations. I am going to go back and make instructions for myself before proceeding, and will do a Titanium backup before doing anything else.
Edit: it appears that some have achieved permanent root and still passed the SafetyNet check. IIRC it was done through the OTA upgrade path but I need to check that. If you are willing to wipe your data then just installing the factory image and then doing the fastboot commands it might work but that is not clear. Too many attempts at root and SafetyNet failed while flailing so hard to know right now if there are good alternatives to OTA.
Click to expand...
Click to collapse
Thanks for the link. I downloaded the full Android 12 image, installed it, disabled verity and wiped my data via fastboot, then flashed the magisk-patched boot. Worked like a charm and safetynet passed after hiding Magisk and installing Riru and the universal-safetynet-fix.
michaelc5047 said:
Thanks for the link. I downloaded the full Android 12 image, installed it, disabled verity and wiped my data via fastboot, then flashed the magisk-patched boot. Worked like a charm and safetynet passed after hiding Magisk and installing Riru and the universal-safetynet-fix.
Click to expand...
Click to collapse
I am hoping to avoid wiping data by taking the OTA and then rooting - I just need to find the time to backup and write down the process first. I knew that the update could be done directly with the factory image, then rooted, but that requires the data wipe. If I encounter a problem that is the fallback approach - then restore data with Titanium.
I don't mind wiping data once. But if I have to wipe data for each update just to root, I'll stay on 11 for now until there's a better way to root
Exactly.... I'll wait for a better way to upgrade and keep my root on 12
You don't "keep your root" on 11 updates; you unroot, take the OTA, then root again with a newly patched boot.img. And the data isn't wiped when moving to 12 if done through the OTA, just like 11 updates. If flashing a factory image the data is always wiped. What is different with 12 is that there is a verification of the boot.img and this has to be turned off (because the boot.img is patched), with a single fastboot command. It does appear to be sensitive to some details, so best to have a detailed procedure written down before starting the process. But those that have done it do not report a long or difficult process - just a finicky one.
CarinaPDX said:
You don't "keep your root" on 11 updates; you unroot, take the OTA, then root again with a newly patched boot.img. And the data isn't wiped when moving to 12 if done through the OTA, just like 11 updates. If flashing a factory image the data is always wiped. What is different with 12 is that there is a verification of the boot.img and this has to be turned off (because the boot.img is patched), with a single fastboot command. It does appear to be sensitive to some details, so best to have a detailed procedure written down before starting the process. But those that have done it do not report a long or difficult process - just a finicky one.
Click to expand...
Click to collapse
Ok ...have you done it yet?....can you tell me your process or elaborate more to my understanding
CarinaPDX said:
You don't "keep your root" on 11 updates; you unroot, take the OTA, then root again with a newly patched boot.img. And the data isn't wiped when moving to 12 if done through the OTA, just like 11 updates. If flashing a factory image the data is always wiped. What is different with 12 is that there is a verification of the boot.img and this has to be turned off (because the boot.img is patched), with a single fastboot command. It does appear to be sensitive to some details, so best to have a detailed procedure written down before starting the process. But those that have done it do not report a long or difficult process - just a finicky one.
Click to expand...
Click to collapse
I want to upgrade ota....but what do i have to do to achieve root without loosing files, setup, etc
No, I have not done it yet - oddly enough I have other things needing doing. The information needed to do it is in this thread: https://forum.xda-developers.com/t/guide-flash-magisk-on-android-12.4242959/ Unfortunately since it started during the 12 beta program, and there was a lot of trial and error, it is necessary to work through the long thread and sort out the process - which appears to be fairly simple (if inflexible).
When updating or upgrading there are always two paths to take: 1) take the OTA that is offered (after unrooting), or 2) flashing the full factory image. Generally speaking, OTAs are designed to keep the user data untouched [edit: not untouched but just converted where needed for the new system] and the factory image is intended to put the phone to factory condition (i.e. no user data present - starts from scratch). Updates (i.e. not upgrades between Android major versions) over-the-air (OTA) are replacing blocks of the stored image, which is very efficient, but requires a pristine stored image (hence the need to unroot to pass the check). Upgrades (new Android versions) seem to download the entire image, IIUC, and then clean up any data (like config files) that are not compatible with the new system. Sometimes the result has been less than perfect, although it is mostly reliable. Ultimately a factory image is the guarantee of getting a known good system, which can then be set up to the user's taste. Backing up user data (e.g. with Titanium Backup) and restoring can make this easier but again, config files from the previous system if restored on the new system can cause problems. Some people prefer to flash the factory image and reinstall the apps as new to get the highest confidence in the result. Most of us just take the OTA and trust the process, prepared to wipe config files or even flash the full factory image if there is a problem. Your choice.
After I write a procedure for myself, and successfully upgrade, I will post it.
So those of us that never rooted can just skip the unroot process and do the rest I assume?
CarinaPDX said:
No, I have not done it yet - oddly enough I have other things needing doing. The information needed to do it is in this thread: https://forum.xda-developers.com/t/guide-flash-magisk-on-android-12.4242959/ Unfortunately since it started during the 12 beta program, and there was a lot of trial and error, it is necessary to work through the long thread and sort out the process - which appears to be fairly simple (if inflexible).
When updating or upgrading there are always two paths to take: 1) take the OTA that is offered (after unrooting), or 2) flashing the full factory image. Generally speaking, OTAs are designed to keep the user data untouched [edit: not untouched but just converted where needed for the new system] and the factory image is intended to put the phone to factory condition (i.e. no user data present - starts from scratch). Updates (i.e. not upgrades between Android major versions) over-the-air (OTA) are replacing blocks of the stored image, which is very efficient, but requires a pristine stored image (hence the need to unroot to pass the check). Upgrades (new Android versions) seem to download the entire image, IIUC, and then clean up any data (like config files) that are not compatible with the new system. Sometimes the result has been less than perfect, although it is mostly reliable. Ultimately a factory image is the guarantee of getting a known good system, which can then be set up to the user's taste. Backing up user data (e.g. with Titanium Backup) and restoring can make this easier but again, config files from the previous system if restored on the new system can cause problems. Some people prefer to flash the factory image and reinstall the apps as new to get the highest confidence in the result. Most of us just take the OTA and trust the process, prepared to wipe config files or even flash the full factory image if there is a problem. Your choice.
After I write a procedure for myself, and successfully upgrade, I will post it.
Click to expand...
Click to collapse
Ok cool and thanks....that was awesome info
anubis2k3 said:
So those of us that never rooted can just skip the unroot process and do the rest I assume?
Click to expand...
Click to collapse
That is the case. It seems that some with 12 beta got tripped up by not getting unrooting/removing Magisk and/or its modules right so that is one less thing to worry about. If you have never rooted then the OTA should work as expected. Rooting can be done in two ways, either by achieving a temporary root and using magisk to directly patch the boot.img, or by patching the boot.img and flashing it, right after removing verification and flashing the new vbmeta.img (in both cases). Of course you first have to unlock the bootloader and enable USB debug, install the Android tools on your computer (minimum version: you only need ADB and fastboot), and connect your computer to the phone with a USB cable. Again, refer to that thread or wait until I can write something up.
CarinaPDX said:
That is the case. It seems that some with 12 beta got tripped up by not getting unrooting/removing Magisk and/or its modules right so that is one less thing to worry about. If you have never rooted then the OTA should work as expected. Rooting can be done in two ways, either by achieving a temporary root and using magisk to directly patch the boot.img, or by patching the boot.img and flashing it, right after removing verification and flashing the new vbmeta.img (in both cases). Of course you first have to unlock the bootloader and enable USB debug, install the Android tools on your computer (minimum version: you only need ADB and fastboot), and connect your computer to the phone with a USB cable. Again, refer to that thread or wait until I can write something up.
Click to expand...
Click to collapse
How do one remove verification?
I haven't been able to permanently root android 12 without wiping my data. I'm not talking about upgrading from 11 to 12. I'm talking about after installing 12, I still have my data. Any attempt to permanently root 12 causes errors unless I wipe my data. This was detailed quite a bit in the link you posted. Have you tried permanently rooting 12 and keeping your data?
As I said before, I have not had time to try the upgrade. Also, that thread has multiple conflicting posts which is why I know it will take time to go through and parse out what works and what doesn't. There are posts IIRC where root was achieved with data retained - but exactly how that was accomplished is not clear (or even if that really did happen). Since we have not had our phones for long there shouldn't be too much in data to lose, and there is always Titanium, so I will give it a go when I have time.
One of the things that I would like cleared up is if the way to 12 and root is to stop the OTA upgrade process at some point and remove verification and/or root before continuing, or possibly root fails because it is attempted before the upgrade is complete. IIRC the OTA has at least one reboot involved, with some processing after the reboot (probably fixing the data to be 12-compatible). Clearly if the upgrade can be done while retaining data and then successfully rooted then it must be done in a precise way; the lack of precise explanations of successful roots is very disappointing.
Edit: If it does turn out that data must be wiped every time 12 is rooted then that means backing up and restoring will be needed for each update, as well as unroot/root, and possibly removing verification each time. That would be a huge PITA. Let's hope that isn't so.
BlvckSensei816 said:
How do one remove verification?
Click to expand...
Click to collapse
It is explained in the thread I linked. But at this point unless you are willing to wade through 14 [make that 16 and counting...] pages of posts it is better to wait until someone posts a good procedure. Anyone not familiar with flashing is liable to get into trouble and needing a factory flash. However good 12 is, it is not so good that we can't wait a bit.
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.