These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Loustsoul said:
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Click to expand...
Click to collapse
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
jeffsga88 said:
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
Click to expand...
Click to collapse
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Grin59 said:
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Click to expand...
Click to collapse
For root? Just use the global patched boot.img and boot into OS, go to Magisk and perform a direct install. No issues at all with root on T-Mobile firmware. I've been rooted ever since they allowed us to unlock the bootloader and get our tokens.
Removed
EtherealRemnant said:
Really all you should need to do to convert to global is unlock the bootloader, take the NA downgrade package, and flash it with Fastboot Enhance. Make sure you go to the partitions screen and search for cow and delete every one of them so there is room for the image and if you get any other errors, don't continue. Once the flash is successful (the bar will seem to stop, just let it sit for a bit and it will continue), choose English on the phone screen and go through the menus to find where to wipe the phone and then reboot.
There is a risk of a brick if something goes wrong so without the MSM Tool, this is at your own risk, but Fastboot Enhance doesn't tend to brick phones like fastboot scripts do as long as you stop if it gives you an error.
Here is the NA downgrade package.
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
Click to expand...
Click to collapse
Yeah, technically should work. Unfortunately the risk is too high without having the MSM in case something goes wrong. Especially if it's your daily phone, like it is mine. But if anyone wants to give it a go, let us know how it goes, just know it could brick your phone and there's no current way to restore it without sending it to OnePlus or paying a scam artist to restore it.
Removed
Can I get my boot.img off of my phone or do I need to download it? Also the 10 pro is not listed in the software on the oneplus website. Where can I get the official stuff I need? Im happy with just root for now, I just want to use Magisk and do the updates......
EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
Im willing to try but I am too unsure of what to use as far as the correct boot and rom.... You seem to have way more knowledge than I and I would greatly appreciate your help.
Removed
EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
The only downside I could see then it's that we don't even have the full T-Mobile firmware to flash back to in case it starts to flash global but then failed. I'm tempted to take the plunge and try (would be nice to be on Android 13 now instead of waiting months for T-Mobile to get the update) but just don't want to end up bricking with no way to recover. Also, in the past I know people were using the MSM to convert to global or EU, does using the global downgrade script alone work for converting? I might take a look at your guide for the 9 series and try with the 10 pro. I guess I can always send it in if it does brick, still have my 9 pro I can use in case something goes wrong.
Removed
EtherealRemnant said:
It is a legitimate concern that you can't get back to T-Mobile firmware if something goes wrong and that is definitely something to think about.
I can tell you that the downgrade package is as close as you can get to the MSM Tool in terms of a restore without an MSM. I have used the downgrade packages to convert between regions on my 9 and never had any issues except for when I used the India MSM Tool for the 9 Pro on my 9 and kept losing touchscreen in OOS12. That was only fixed with an MSM Tool modded to get me back on regular global 9 firmware.
Click to expand...
Click to collapse
Well I'm taking the plunge so I'll update after if it's successful or not. Was able to delete all the COW partitions and start the flash no issue, so just have to wait for it to finish.
Removed
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
tman23 said:
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
Click to expand...
Click to collapse
Yeah, don't think it's going to work. Can't fully get out of the setup screen (or if you do it just stays at black screen only able to pull down quick settings and not enter options or anything). Wiped after flashing and won't work. I guess I could try using Fastboot Enhance to flash some of the global update zips and see if that does anything.
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. EDIT: I was wrong. There is no true full T-Mobile NE2217 ZiP available.. really sad.
But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success. That being said, as said above, root is very easily achievable by just BOOTing a patched global boot.img if you just want to root and maintain your original software.
Prant said:
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success.
Click to expand...
Click to collapse
I haven't really heard of anyone converting the 10 due to lack of MSM. Also, haven't seen any full zips for the 2217 (T-Mobile version), so if you have a link to it that would be very useful. Also on 2217, you can't flash from in system as it's disabled in firmware (unless the separate apk works).
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
EDIT: As mentioned later in the thread even these are not full images for NE2217.
Prant said:
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
Click to expand...
Click to collapse
Thank you, not sure how I missed those. If my attempt to restore the device doesn't work I'll try restoring it by flashing T-Mobile firmware again.
Related
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips
Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.
If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.
Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy
Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!
full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.
Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.
moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from
irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip
So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?
How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.
Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this
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 ...
This might be completely unnecessary (mods feel free to remove if it is), but I see a LOT of misinformation regarding GSI ROMs and the G8. So. Here's a guide/FAQ for those wondering if/what is possible:
***I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, LOSE YOUR DATA, OR OTHERWISE DAMAGE YOUR DEVICE. IF YOU CHOOSE TO FOLLOW THIS GUIDE, THE FATE OF YOUR DEVICE IS IN YOUR HANDS, NOT MINE, NOT YOUR MOTHER'S, NOT ANYONE OTHER THAN YOUR OWN***
Prerequisites (yes, these are all NECESSARY. If you don't know how to unlock your bootloader or use fastboot, there are other guides here. Go find one.)
Unlocked bootloader (and the V50 engineering abl files as well as stock, plenty of guides here with download links)
QFIL/QPST
Basic Fastboot, ADB knowledge
BACKUP. I mean ALL YOUR DATA kinda backup. This WILL wipe your phone, do NOT come crying to me if you lose the last picture of your favorite sock. Not my fault.
GSI for Treble device (ab)
GApps (optional, but recommended)
Instructions to Flash via Fastboot
WIPE YOUR PHONE
Yeah, completely factory reset that sucker. Doesn't matter if it's through recovery, settings, or adb, just bite the bullet and restore factory settings. You can technicially flash without doing this first, but you'll still have to wipe it before any flashed ROM will run. Sorry.
Boot to EDL (NOT download, your screen should be black, dev manager should show QD Loader 9008 COMx)
Use QFIL to flash engineering abl file to both a and b slots - yes, all this work just for fastboot.
Reboot to fastboot!
I just unplug my phone, use power + vol- to shut phone off and then reconnect while holding vol-, but you do you.
In case you don't remember, your touch screen WILL NOT WORK during this time, even if you fully boot to system! Completely fine and normal, means you're on the right track!
Fastboot Devices should yield "LG850UM", also good!
Open cmd prompt from platform_tools, copy path to desired GSI while you're in there
Run these commands line-by-line:
fastboot format system
fastboot flash system *Path_To_GSI.img*
This is where I usually repeat the 2 commands and attempt reboot while I still have fastboot, whether or not it changes anything I have no idea, but it's never given me problems so why fix it if it ain't broke?
fastboot flash abl_a abl_STOCK.bin
fastboot flash abl_b abl_STOCK.bin
fastboot reboot
Ta-Da! Your shiny new ROM should be up and running. Use TWRP or any kernel manager (I like SmartPak) to flash TWRP, GApps, blah blah blah.
FAQ/Troubleshooting
Touchscreen still not working? Go back to EDL and load the stock abl bin files through QFIL, then reboot as normal.
You will likely be asked to input a password upon successful reboot, just enter your PIN/password, whatever you used to unlock your phone pre-flash
The cool things like QuadDAC and LG-specific tweaks will probably not work. Weigh your options before flashing.
Magisk comes pre-installed with most GSI's, just follow the prompts and you'll be just fine.
Don't want GApps? Just sideload desired apk's via ADB, or use the browser to search for them.
Can't I just use TWRP and make this whole process a lot simpler? Yep. But some of us don't have working TWRP or prefer using fastboot commands. This is for those people, don't hate.
Which ROMs work?? Not sure, haven't tried them all. Currently running HavocOS found in Treble GSI forum on here.
Help! I broke my phone! No, you probably didn't. It's advisable that you know how to emergency restore via LGUP prior to starting this process though. Please be specific as to what part of this "broke" your phone and why exactly your phone is "broken" if you're going to ask for help- "bricked device" has never helped anyone.
Rebooting is your best friend in this process, especially during the first boot. If anything starts to hang up or act funny, just give the phone a minute to catch its breath and, worst case, turn it off and back on again
As previously stated, this is probably pointless, but given all I see on the G8 forum is "no custom ROM" or "why bother trying to *insert idea here*", I figured it might help some folks out. I'm sure I left a few things out, feel free to correct or provide input as necessary.
Works on LM-G820QM5?, I have bootloader unlocked
Elihu_GmG said:
Works on LM-G820QM5?, I have bootloader unlocked
Click to expand...
Click to collapse
Yep, it's basically the unlocking/root process only you're formatting/flashing the "system" partition instead of "boot_a/b"
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
AsItLies said:
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
Click to expand...
Click to collapse
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
SirOlive said:
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
Click to expand...
Click to collapse
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
AsItLies said:
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
Click to expand...
Click to collapse
Sorry for being short, but a simple Google search would back up everything I've written. I wouldn't have written this up if it didn't work, or if it was just a theory... I wouldn't have said that my Verizon G8 is running Havoc if it didn't work. I was able to flash with zero problems. With the Treble Project, Google has mandated that Android devices boxed with 11+ (possibly 10?) be capable of not only recognizing, but running GSIs as to assist developers in testing apps and builds in varying versions of Android as quickly, easily, and simply as possible. This means that not only can one download and flash Android releases downloaded directly from Google, but devs can use the source code to create versions of their ROMs that will apply to a wide array of models that would never have seen development otherwise. Because these are "generic" images and are based upon system architecture type alone- not a particular make/model- there are sometimes things overlooked. For instance, in our case, the audio processing and LG's camera software are not present. These are decently made up for by the presence of flashable mods, though, and the phone remains fully functional, Google Play Certified (if desired), and as reliable as the ROM you choose to flash.
Basically, Google>LG. LG wants to use the Android platform, they must abide by Google's rules. They need not go into great detail, nor allow their devices to be changed to something fundamentally non-LG, nor divulge any potentially propitiatory subject matter (once again, "generic"), but they must allow the device to be open to a certain level of customization as designated by Google.
Is it ideal? Not if you're lucky enough to have ROMs tailored for your specific phone. But for those left behind- like the G8- it's a fantastic workaround that does, in fact, work. As I'm sure you're still skeptical, I will add screenshots tomorrow to prove the validity of this seemingly ludicrous claim. In the meantime, please do some research on the topic- or better yet, give it a shot- there's gotta be a guide around here somewhere.
It works
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
hooutoo said:
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
Click to expand...
Click to collapse
Where did you get V50 engineering abl files as well as stock?, I just want to make sure to get the correct files
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
hooutoo said:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
Click to expand...
Click to collapse
Ok,ok
Hello, I followed your instructions as written but when I reboot my phone I am stuck at a boot logo cycle, but my comment doesnt have to do with that, I want to ask if maybe you know what could've gone wrong.
I also own a g8 from verizon, I do have bootloader unlock, and tried to install Havoc OS, I wanted to mention this in case it is useful
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
hooutoo said:
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
Click to expand...
Click to collapse
Yeah, I know, like I said in my previous comment my phone got stuck in a boot loop, I fix it just by loading system_a partition in qfil, so I am gonna give it another shot and see if it works, already backed up every partition just in case anything goes wrong
If you're goona play around, this is secondary bs. My real phone is a FLIP3 and I'm not allowed to play unlesss to make/awnswer call.
Does somebody tried tp flash GSI with LineAge (A11) or Arrow(A12) vendor to g8?
I`m interesting about dt2w .. I flashed GSI`s to my G820UM on the past (A10 stock vendor) and it have no dt2w.. ((
i ended zeroing my imei from sprint G8 but thats okay i dont care for it much but what i do care is getting some LOS 17.1 on the sprint G8
where do we have any links to these so called GSI images?
blaze2051 said:
where do we have any links to these so called GSI images?
Click to expand...
Click to collapse
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
From what I remember when I tested multiple Android 11 GSIs such as Pixel Experience, I couldn't get vibration to work on my G8.
Have never needed to install a GSI before but as we're kind of stuck here without a single custom ROM, I thought I'd have a look.
AFAIK installing one of these would still leave the door open for stock recovery to be used should something go wrong, so as long as you've made a back up it should be fine.
I'm just curious as to the method of installation?
Has anyone had any experience with GSI ROMs before.
How was it? Did it work?
Would DSU image loader be an option?
I've attached what treble version we have and the relevant info required from the treble info app.
Apparently we have VNDK compatibility, not sure what that is but we have it.
Hi @dladz, I ran into a similar question three years ago when I bought a Xiaomi Mi 8 Pro. I was so used to using custom ROMs that I didn't even check before I bought it whether any custom ROMs would be available.
I was honestly shocked to see that that wasn't the case - there was absolutely NOTHING available - and that I had ended up with a device that couldn't even be unlocked right away, you had to wait and open a Mi account to be allowed to unlock it. I couldn't believe it at the time, I had come from a OnePlus X and had helped others root and install custom ROMs on other OnePlus phones without any problems, so I felt like I had just thrown quite some money out the window to run around with a mobile Chinese Spyware gadget I didn't want to use.
That was the first time I ever came across the term GSI ROM and it took me several weeks to figure out how to flash a ROM that I could also use afterwards. I knew I wouldn't want to have a stock ROM by a company that has very loose data privacy standards and even clearly states they collect your data (Lesson learned, I thought, I just had to buy a "proper" phone again and no more phones from budget manufacturers).
Several weeks later, after I had finally managed to get a custom GSI ROM working on my device I posted a lengthy how-to here on XDA.
Again, it took me weeks to get everything to work that I could not go without. And even then, I had to resign to the fact that many features of the phone would not be working (The fingerprint sensor, for example. Also, the Xiaomi Mi stock rom apparently had excellent GPS support (dual GPS support) but GPS positioning is just alright on the GSI ROM I'm using, also there were many cool Xiaomi apps like a compass app that wouldn't work outside MIUI). But I was more than happy I had gotten different GSI ROMs to work in the end and settled on one that I could live with, knowing my phone wouldn't be sending data to some Chinese servers constantly.
Now that the Mi 8 Pro has become a bit slower over time with all the latest apps, I took the plunge and spent a ton of money on the OnePlus 10 Pro 256 GB version only to be disappointed again, but this time by a company that used to be the epitome of openness when it came to custom development.
I got my OnePlus 10 Pro on release in my region in April, together with the 50W wireless charger and both have been sitting here since April, I'm not touching that phone until I can remove all the Spyware it comes installed with. At this stage, I'm not yet willing to go through the weeklong trial-and-error again that it took to get the Mi 8 Pro running a custom GSI ROM (also considering that some of its features never worked...), but if OnePlus doesn't get its **** together soon with the MSM tool and some openness towards developers, I will seriously just consider selling it on eBay again (It is brandnew after all) and will never buy another phone from OnePlus again. This has been an extreme disappointment and I'm still struggling to understand why they wouldn't support custom development any more. I had checked the OnePlus 9 Pro threads on XDA just to see if there's still custom development going on for OnePlus and it seemed everything was still OK, but now... .
On a more positive note: The Mi 8 Pro did eventually get some custom ROM love and there are now several ROMS to choose from, so to answer your original question - If you ask me, don't bother with GSI ROMs until we can be sure there won't be any custom ROMs for our phone. I'm still hoping that will be the case.
Gsi will work but no fingerprint or faceunlock.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
MrScarl3t said:
Gsi will work but no fingerprint or faceunlock. And many more visual glitches.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
Click to expand...
Click to collapse
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
MrScarl3t said:
Gsi will work but no fingerprint or faceunlock.
Click to expand...
Click to collapse
Unless someone posts a step-by-step guide with screenshots of a successful flash, I wouldn't believe anything.
This sounds more like it:
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
yo-less said:
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
Click to expand...
Click to collapse
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Twiggy000b said:
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Click to expand...
Click to collapse
Did you try sending it in?
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
nah i reached out and oneplus never got back to me.
sorry to hear that :/
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
What phone was you on mate??
MrScarl3t said:
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
Click to expand...
Click to collapse
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
dladz said:
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
Click to expand...
Click to collapse
Yeah camera is gcam but the main sensor is fine with it.
Every OnePlus 10 pro works with gsi, and general boot images as well. I will start tomorrow making the guide.
Will test if you can use rollback zip to get back to stock
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
MrScarl3t said:
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
Click to expand...
Click to collapse
Legend
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.