Database Info

6.0.1 OTA for stock rooted system

Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.

Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.

Safest way.. ruu back to stock everything take ota and re root/download apps etc...

Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse

What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe

Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse

Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse

Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse

Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse

Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse

First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse

And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...

I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond

txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....

mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.

Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.

Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.

[ROM] SU4TL-49 100% Stock

SU4TL-49 Stock Image for XT1254: https://mega.nz/#!TwYShBCb!OFxwiUnUO2MiOHEVc8XluNP1uPSf5tTBaVdmyZ-mwSA
This package will flash every image in the SU4TL-49 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, download this: https://mega.nz/#!LwhxyCaZ!NZVi3pA77t7Qlxm1gFQr340SHurOAJEhDQsiR8QFbMc. Install it using the Install Image option in TWRP.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Deodexed version here for those who may want it: https://mega.nz/#!zxAEHJjS!hqNDjOGJoE3eI3rwL48h45Lovj764quxFsWP9IsN_Z4
If you need the full, non-TWRP version, here it is: https://mega.nz/#!ao4zmQQB!T2VClxKcTb-ePAhHotvlSR3NCxG0tRY1YEhMtti_H3k
If you get errors while flashing this, try using TWRP Mod 3 instead of Mod 4.

Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...

Nice! Thanks a lot!

rjansen110 said:
Used this today. Was coming from CM 13. Only notes I had are:
1. Make sure you use the Wipe from the main menu of TWRP and not just the available wipe after you install.
a. Caused my phone to boot but go black after this first half of the boot animation.
2. It asks to uninstall some Motorola services and that will persist. Not sure why but, I did uninstall them.
Overall, it works very well (only up and running 2.5 hours now so I'll have to wait and see if anything happens over the next day or so)
Thanks for this package and all your work...
Click to expand...
Click to collapse
1. Yeah, that's kind of what I meant by the last sentence of the OP.
2. That always happens whenever you go from CM to stock. It's harmless.

So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app

joeriv5692 said:
So when I try to install this, it keeps coming back to me saying no OS is installed. I'm using twrp and have followed the instructions. Should I redownload the zip?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.

TheSt33v said:
I've seen that message before. I just rebooted to system anyway, and it booted just fine. Not sure why it shows up.
Click to expand...
Click to collapse
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?

Glad to see the return of @TheSt33v !! Thank you for your work!!
joeriv5692 said:
Ok, Ill give it a try. I was just afraid of moving forward and soft bricking my phone. Thanks alot.
---------- Post added at 07:56 PM ---------- Previous post was at 07:11 PM ----------
One more thing, If i flash the stock recovery for this....will it take TWRP off my phone? I cracked the **** out of my screen and having a replacement come in from Asurion tomorrow. And would this relock my bootloader? Im trying to make this phone bare stock the day I bought it with out going through computer. Is this possible?
Click to expand...
Click to collapse
the answers to "one more thing":
1) yes, if you flash stock recovery it will take TWRP off. 2) it will not relock your bootloader.
edit: ****** 3) it will *not* take away all traces you have modded/hacked/rooted
Stock.
NEXT DAY EDIT: i just restored pretty much stock 5.1 su-44. after all the uninstall crud there, i booted to twrp, and flashed this. all went perfectly. Thank you @TheSt33v !!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[emoji92] [emoji95] [emoji95] [emoji95] [emoji95] [emoji109]
edit again: same line added to build.prop enables tethering on this build too.
net.tethering.noprovisioning=true

kitcostantino said:
Glad to see the return of @TheSt33v !! Thank you for your work!!
Click to expand...
Click to collapse
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.

TheSt33v said:
Haha the return? I didn't know I left. There just hasn't been all that much for me to do. Then again, the latest Witcher 3 expansion was running my life for the past few weeks, so maybe I did disappear.
Click to expand...
Click to collapse
TheSt33v said:
Now that we've got some Sunshine in our lives, sadly (not really) it is time for Turboid to be retired. We don't need it anymore.
I think that about covers it. Go forth and flash! Thanks for letting me play dev for a few months
Click to expand...
Click to collapse
Ha ha, brother. I guess i just took this post in the Turboid thread wrong.
-King of Unsolicited Advice

I did a system-only backup in TWRP after updating, so I don't think I need this, buuuut, never hurts to have a 2nd option! 44 did save my bacon so update was possible. ?

Thank you for the De-Odexed build!!!
-King of Unsolicited Advice

Has anyone had issues w this ROM or is it all good?

its all good.
-King of Unsolicited Advice

No luck with de-odexed version
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.

yeah, i can confirm. same issue. the fix was wiping data for the app via TiBup. i use a transparent google drive, though, and had presumed it was just me.

sgeek7 said:
De-odexed version seems to be causing Google Drive to fake load randomly. It'll be doing something, see it flash to Drive at the top with a blank page, then it goes back to what it was before. Was coming from a CM rom, but did do a factory reset via TWRP after installing the rom. Currently trying the non de-odexed version, just waiting for the install to finish.
Click to expand...
Click to collapse
Weird. I forget, is Drive a system app in the stock rom? If so, maybe try removing it altogether with TiBu and reinstalling it from the play store?

It might be. The non de-odexed version is having no issues on my phone. Thanks for the idea just in case.

Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?

Is anyone having issues with the play store crashing everything you start it up? I flashed the de-odexed and non-de-odexed but play store keeps crashing every time. Any ideas?
---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------
snugroho3 said:
Hi, is this include the new .49 bootloader and radio package? or should I install it manually after flashing this rom?
Click to expand...
Click to collapse
It's included

Can CF-Auto Root G930F really do no harm instead of G930W8

Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to Marshmallow 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?

isnull said:
Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to lollipop 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?
Click to expand...
Click to collapse
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F

MAX 404 said:
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F
Click to expand...
Click to collapse
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?

isnull said:
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?
Click to expand...
Click to collapse
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo

MAX 404 said:
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo
Click to expand...
Click to collapse
Oh, thanks, neat little app. And yeah, exynos indeed:
screenshot

isnull said:
Oh, thanks, neat little app. And yeah, exynos indeed:
Click to expand...
Click to collapse
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3

MAX 404 said:
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3
Click to expand...
Click to collapse
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought

isnull said:
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought
Click to expand...
Click to collapse
Hi
1 That is right
2 I thought so...
3 Yes 35MB is about right ....is not the whole rom is only patching some modifying

MAX 404 said:
Yes 35MB is about right ....is not the whole rom is only patching some modifying
Click to expand...
Click to collapse
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to

isnull said:
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to
Click to expand...
Click to collapse
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/

MAX 404 said:
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/
Click to expand...
Click to collapse
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?

isnull said:
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?
Click to expand...
Click to collapse
Up to you mate......mine is in unlock position

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
Oh cool, thanks. Think I'm ready now, will post a screenshot when I'm done, after re-reading a couple of things (Samsung Pay (which I don't use anyway), etc). You've been a huge help!

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

isnull said:
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
Click to expand...
Click to collapse
Yeah he deserve it !!!
Cool mate glad for you.

@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.

Just in case someone was going to reply to this here, I moved the "Software update" question here since it's a whole other story.

isnull said:
@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.
Click to expand...
Click to collapse
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA

MAX 404 said:
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA
Click to expand...
Click to collapse
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!

isnull said:
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!
Click to expand...
Click to collapse
Hi mate
If your only modification to the system is just root and you do not notice any thing strange let it be do not flash dm verity zip , that error is caused by a "flag" set by the kernel as far as i know it should not be a problem , actually latest SuperSu should take care of it also

FIXED - Android 10 - Sensors Bug

EDIT 5
In addition to the two methods highlighted below, I'm sharing a third method which was brought up in the thread. This one is much easier, however, root is required. This method works for many, however, it is not confirmed by me. Again, no one takes responsibility for this or the previous method.
Ask someone with working sensors to share the following folder with you: root/mnt/vendor/persist/sensors. Please ensure the device they have is the same as yours (Pixel 3 (blueline) and Pixel 3 XL (crosshatch) are NOT the same devices). They should, ideally, share it as a *.tar file to keep the permissions of subfiles intact.
Instructions to generate this tar file are here: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904/post80833171
On your rooted phone running Android 10, navigate to: root/mnt/vendor/persist/ and first of all, backup your /sensors/ folder. Then, paste the contents of the tar file in there so you have the sensors folder from the working device that was shared with you.
Reboot and report. You should have working sensors now.
EDIT 4
TWRP Developers are working on fixing the root cause of this issue. More details here: https://forum.xda-developers.com/showpost.php?p=80248406&postcount=1218
EDIT 3
We now have an update from Google: Here is the email we received (posting it verbatim after redacting any personal or confidential information).
We now have a root cause for this issue and a fix will rollout in October.
The short summary is that in Q qualcomm added some checks that prevented sensors from starting when it found corrupted calibration files. In Pi it was more forgiving and continue to function even though the calibration files may have been corrupted. The fix will revert back similar to what Pi was doing. The upside is sensors will continue to work. The downside is, some of the sensors may not function as effectively if the calibration files are corrupted due to external reasons. Regular users who do not touch persist partition would not hit this issue.
Thanks all for your support. Please do let us know if you are seeing any other issues post Android 10 rollout that need attention. We will start ramping up the rollouts next week.
Click to expand...
Click to collapse
EDIT 2
Thanks to many members of this thread, I am sharing a second method which does not involve flashing a new /persist/ partition that was shared before. This method works for many, however, it is not confirmed by me. Again, no one takes responsibility for this or the previous method.
Steps below (not my work; thanks to others on this thread):
We assume you are on Android 10 for these steps.
Backup your current persist partition since you will be changing it. On a rooted adb shell, run dd if=/dev/block/by-name/persist of=/sdcard/persist.img (this will backup your persist to your sdcard)
Navigate to root/mnt/vendor/persist and delete the cache folder completely. This stores TWRP's cache and log files and is the root cause of the problem in the first place.
Flash Android 9 (PIE) from bootloader. YOU DO NOT NEED TO WIPE your data so you can remove the "-w" flag
Let the phone boot (it will bootloop; that is normal) for 2-3 minutes. This step will "fix your broken persist files" according to users
Reboot to bootloader and flash Android 10. Again, YOU DO NOT NEED TO WIPE your data, so you may remove the "-w" flag.
Reboot and report if this works.
EDIT 1
This issue was fixed. The problem is with the persist partition getting corrupted on some devices. The reasons are not clear, but we have strong reasons to believe this is due to TWRP's implementation of leaving logs and cache files on the /persist partition, which is limited in size. The log files often exceed 20MB in size and cause the sensor config and calibration files to become corrupted on that partition.
Steps to get this fixed:
Obtain a working persist.img from someone (it is device specific. You can find the ones for crosshatch and blueline on this thread, but will have to ask someone else for other devices)
Replace your persist partition with the persist.img you obtained. This needs to be done using an advanced command (dd) and you need to be on Android 9 in TWRP (rooted) to do this. Read the thread (around page 19) for more details.
Flash Android 10 (does not need to be a clean install, but clean install is always recommended).
WARNING: replacing your persist partition with someone else's (even the same device) WILL replace your original, unique factory calibration data with someone else's. This includes audio config files, camera calibration files, sensor calibration files. Backup your original /partition image before doing this and only do this if it is absolutely necessary. You have been warned!
No one on this thread assumes responsibility for anything bad happening to your device. It worked for all of us, but is not guaranteed to work for you. Still no news from Google, who are still investigating.
ORIGINAL THREAD
Starting a new thread here from the old one: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-final-version-release-t3963794/page7
What is the problem?
Many users of Pixel 3 XL, Pixel 3, Pixel 2 XL and even the OG Pixel are reporting a major bug after upgrading to Android 10. All the sensors seem to be disabled.
This includes Active Edge, Proximity Sensor, Ambient Light Sensor, Auto-brightness, Accelerometer (Auto-rotation, flip to shhh, double tap to wake and lift to wake). All of these are dead on Android 10.
What we know:
Whether we upgrade directly from Android Pie or do a clean install using the factory images does not seem to matter. The issue only affects a certain set of users and only goes away if we revert to Pie. The phone works perfectly then.
Manually erasing all partitions and installing from the image does not work either.
Installing Android 10 individually on partitions A and B does not help either.
Re-locking the bootloader and returning completely to stock does not work either.
The only thing in common for all of us is that we were all rooted and/ or using a custom kernel in the past. However, some others who had been rooted and using custom kernels/ ROMs report they do not face this issue.
Interestingly, for users on the beta program, they started noticing this issue around Beta 6. Post-that, even if they reverted to an older Beta 3,4 or 5 which did not have this problem, they would face this problem after Beta 6. And this is continues with the public version now.
Some users suspect this could be happening due to "something left-over somewhere hidden on the phone." (not verified, but makes sense, in theory)
Coverage
This issue is widely covered now:
https://bgr.com/2019/09/05/android-10-update-for-pixel-phones-sensors-bug-explained/
https://www.androidauthority.com/pixel-sensors-android-10-1026027/
https://9to5google.com/2019/09/05/pixel-active-edge-sensors-android-10/
https://mobilesyrup.com/2019/09/05/pixel-users-experience-dead-sensors-post-android-10-update/
... and many more
Next steps:
If you face this issue, please add your comments and what you have tried here and update the bug on Google's issue tracker that we have filed here:
https://issuetracker.google.com/issues/140476661​
There is also a help center article on Google's support forum that you can upvote here: https://support.google.com/pixelphone/thread/13511202?hl=en

So the 3A and 3A XL aren't affected? I have 10 on mine now after sideloading the OTA last night and aside from the 20 minute reboot cycle, I've seen no problems as of yet.

BigOkie said:
So the 3A and 3A XL aren't affected? I have 10 on mine now after sideloading the OTA last night and aside from the 20 minute reboot cycle, I've seen no problems as of yet.
Click to expand...
Click to collapse
No idea about the other models. I've just posted the ones that I could find on forums, including mind (3XL).
There is something in common here for everyone that we seem to be missing. In the interest of getting to the root of it, I am posting my pre-android 10 update configuration:
Pixel 3XL, hardware model MP1.0
Rooted with magisk 19.3
Recovery: TWRP
Kernel: Kirisakura Kernel v3.4.5
Magisk modules installed: youtube vanced, busybox, energized, systemless hosts, zRAM/ SWAP manager to enable zram
Apart from this, I had naptime installed working in root mode
And tweaked a few kernel settings: color settings, changed scheduler for graphics, zram compression algorithm and I/O scheduler.
Anyone else facing this problem see something in common?

That is sooooo weird... I've never seen that on my phone

nikhilnangia said:
Interestingly, for users on the beta program, they started noticing this issue around Beta 6. Post-that, even if they reverted to an older Beta 3,4 or 5 which did not have this problem, they would face this problem after Beta 6. And this is continues with the public version now.
Click to expand...
Click to collapse
I would rather say this is related to the bootloader that after flashing beta 6 doesn't get downgraded when returning to an older beta version or even Pie. Since only a part of the users is affected I would guess that a specific hardware revision doesn't play nice with Android 10. As I am not affected I can't do further testing and you should take what I wrote above as an educated guess .

alpinista82 said:
I would rather say this is related to the bootloader that after flashing beta 6 doesn't get downgraded when returning to an older beta version or even Pie. Since only a part of the users is affected I would guess that a specific hardware revision doesn't play nice with Android 10. As I am not affected I can't do further testing and you should take what I wrote above as an educated guess .
Click to expand...
Click to collapse
Thanks for the ideas! I can confirm that the hardware version is not the problem since some others with the same hardware version as myself (MP1.0 - which can be checked on About Phone->Hardware) do NOT face this issue.
As far as the bootloader goes, that's certainly plausible. @ultimatepichu and @FcukBloat has any of you tried this? i.e change the bootloader version to an older version and flash 10?

nikhilnangia said:
As far as the bootloader goes, that's certainly plausible. @ultimatepichu and @FcukBloat has any of you tried this? i.e change the bootloader version to an older version and flash 10?
Click to expand...
Click to collapse
the first thing in flash-all is to send the bootloader to the phone . But even if the bootloader is not downgraded, then I should get sensor problem in Pie as well right?
But no, I didn't try what you said.

After majorly screwing up my first attempt to jump from Pie to 10, I finally made it, and sure enough, I am a victim of this bug as well.
On an unrelated note, for the Magisk users out there, attached is the patched boot.img across 4 RAR archives for the Pixel 3 XL 10.0.0 (QP1A.190711.020, Sep 2019) image to save you some time making one yourself.
The SHA-256 hash for the image contained across the archives is:
Code:
dbdc828777fd8b734986998d0732c1c4e3e565fc66499c310f3a23c85abe383b

Just listening... can't figure this one out too...in the GSI build I found a Qualcomm driver for sensors for Crosshatch, but I don't know how to flash it, downloaded the bin and Qualcomm installer but afraid to go thru it might kill my phone. I do an average a day of flashing, my phone might get crazy???
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
Me and FCUCKBloat has been discussing this since beta 6 came out. All my sensors used to work on beta 5, with kernels and TWRP installed, but after I tried flashing custom ROM and eventually beta6 came out flashed it thru fastboot, regular update and so on, sensors won't worked anymore. So, I decided to go back to beta 5 but sadly sensors don't worked anymore, when it used to worked before.:crying:

This happened to me since Pie. And Google seem doesn't do anything about it.
httpss://support.google.com/pixelphone/thread/3086868?hl=en

installed the GSI BUILD 10 from google and all sensors are working, flash it came from Bootleggers ROM. The only thing I can't find is the gesture Nav, maybe someone can help me activate it, so far all the sensors, dark mode are working.

imna357 said:
installed the GSI BUILD 10 from google and all sensors are working, flash it came from Bootleggers ROM. The only thing I can't find is the gesture Nav, maybe someone can help me activate it, so far all the sensors, dark mode are working.
Click to expand...
Click to collapse
please can you provide a step by step guide to flash GSI and fix this problem so other guys can also try this and eventually report the results in the bug tracker site to inform Google specialists? please!
tia

FcukBloat said:
please can you provide a step by step guide to flash GSI and fix this problem so other guys can also try this and eventually report the results in the bug tracker site to inform Google specialists? please!
I just downloaded it from the android 10 from here: https://developer.android.com/topic/generic-system-image/releases
then downloaded this version ARM64+GMS, problem only is the gesture navigation and phone apk, gestures is not present, while phone I can't here anything, I can call but nothing on the earpiece, and no voice output from the other side
---------- Post added at 01:20 AM ---------- Previous post was at 01:12 AM ----------
this thing is smooth, but I am not sure is a daily driver, good thing is sensors are working, maybe will just have to wait for a custom 10 ROM or I will try the TREBLE ROM : https://t.me/androidqgsi
Click to expand...
Click to collapse

imna357 said:
FcukBloat said:
please can you provide a step by step guide to flash GSI and fix this problem so other guys can also try this and eventually report the results in the bug tracker site to inform Google specialists? please!
I just downloaded it from the android 10 from here: https://developer.android.com/topic/generic-system-image/releases
then downloaded this version ARM64+GMS, problem only is the gesture navigation and phone apk, gestures is not present, while phone I can't here anything, I can call but nothing on the earpiece, and no voice output from the other side
---------- Post added at 01:20 AM ---------- Previous post was at 01:12 AM ----------
this thing is smooth, but I am not sure is a daily driver, good thing is sensors are working, maybe will just have to wait for a custom 10 ROM or I will try the TREBLE ROM : https://t.me/androidqgsi
Click to expand...
Click to collapse
thanks my friend, but how flashed system.img and vbmeta.img? i mean all steps coming from bootleggers please. so I can replicate and also inform google people so they maybe understand what is wrong in the official Q image.
about phone, in the google site I see:
Phone Audio - When using the integrated dialer, you may not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
did you try any other dialer? maybe that will fix the phone voice issue?
Click to expand...
Click to collapse

FcukBloat said:
imna357 said:
thanks my friend, but how flashed system.img and vbmeta.img? i mean all steps coming from bootleggers please. so I can replicate and also inform google people so they maybe understand what is wrong in the official Q image.
about phone, in the google site I see:
Phone Audio - When using the integrated dialer, you may not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
did you try any other dialer? maybe that will fix the phone voice issue?
Click to expand...
Click to collapse
I am trying it right now, looking for dialer that will work.
I flashed it this way, from Bootleggers ROM did not wipe anything just boot to fastboot then:
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot -w
fastboot reboot
---------- Post added at 01:52 AM ---------- Previous post was at 01:43 AM ----------
I went on flashing the official 10, not sure what will happen=)
---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------
will update in a few
Click to expand...
Click to collapse

imna357 said:
FcukBloat said:
I am trying it right now, looking for dialer that will work.
I flashed it this way, from Bootleggers ROM did not wipe anything just boot to fastboot then:
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot -w
fastboot reboot
---------- Post added at 01:52 AM ---------- Previous post was at 01:43 AM ----------
I went on flashing the official 10, not sure what will happen=)
Click to expand...
Click to collapse
thanks sir! let us know! I am doing some tests here too soon.
ps. fastboot -w erase all user data btw, correct? also internal storage I think
Click to expand...
Click to collapse

yup
---------- Post added at 01:55 AM ---------- Previous post was at 01:54 AM ----------
copy your storage first on a computer
---------- Post added at 02:07 AM ---------- Previous post was at 01:55 AM ----------
well flashing to official 10, sensors stop working again...what the, i will try to factory reset

would like to try to replace the system and vbmeta images in stock Q with the ones in the
GSI package, but in GSI we have a single system.img file while in stock Q there are two (system.img and system_other.img) so don't know how I could do
alternatively I could try just fastboot flashing system and vbmeta images from stock Q, but again I wouldn't know how to manage the two system images... :silly:
---------- Post added at 08:30 AM ---------- Previous post was at 08:11 AM ----------
@imna357 I can't erase system and install GSI system image, I go in bootloader (fastboot mode) and i can flash vbmeta image, but when I try to erase or flash system image, it says this must be done in fastbootD...
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/9 (261528 KB) OKAY [ 6.370s]
Writing 'system_a' FAILED (remote: 'Partition should be flashed in fastbootd')
fastboot: error: Command failed
:silly:

FcukBloat said:
would like to try to replace the system and vbmeta images in stock Q with the ones in the
GSI package, but in GSI we have a single system.img file while in stock Q there are two (system.img and system_other.img) so don't know how I could do
alternatively I could try just fastboot flashing system and vbmeta images from stock Q, but again I wouldn't know how to manage the two system images... :silly:
---------- Post added at 08:30 AM ---------- Previous post was at 08:11 AM ----------
@imna357 I can't erase system and install GSI system image, I go in bootloader (fastboot mode) and i can flash vbmeta image, but when I try to erase or flash system image, it says this must be done in fastbootD...
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/9 (261528 KB) OKAY [ 6.370s]
Writing 'system_a' FAILED (remote: 'Partition should be flashed in fastbootd')
fastboot: error: Command failed
:silly:
Click to expand...
Click to collapse
this thing happened to me last night, if you can't erase the system it will not go thru, but after flashing bootleggers then let it settle with magisk, reboot to bootloader, it worked
---------- Post added at 02:55 AM ---------- Previous post was at 02:51 AM ----------
were you on pie rooted?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
ok, your on Q, will not work, last night I was on Q it did not work, need to be on PIE...sorry busy flashing my phone back to bootleggers, will try the TREBLE ROM tomorrow

I came from pie rooted avb and encryption disabled an took the ota when booting it said it was corrupted had to factory reset booted and worked fine all sensors any way except the mobile data sucks worse but I'm on Google Fi in East Tennessee. Also there's 2 builds for Android 10 on the dev site maybe try both builds and worst case scenario go back to pie and disable avb and encryption then set phone up then try taking the ota.
To disable avb and encryption boot to twrp then advance wipe,format data then sideload this zip and flash then reboot.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/

How To Guide [CLOSED] Bypass the region check in Lenovo p12 pro 12.6(CN version)

Having had a long research after I bricked my lenovo p12 pro 12.6(the CN version) ,I thought I finally figured out what is happening when boot ROW firmware on my tablet and a method to bypass such region check. Here is detail procedure:
First of all ,you DO NOT need to return your bricked tablet back to the seller or manufactures, any of which costs time and patience.
1、Download the super partition image file Mod edit: Links removed ,and extract super.img from it using 7z x ... command.
2、You can choose to use my bash shell script (flash_stock_firmware.sh)or your manual instructions: to flash the stock firmware
Bash:
bash 'flash_stock_firmware.sh' 'PATH/TO/THE/STOCK/FIRMWARE/FOLDER'
,it takes about 5 minutes to end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After it booted to framework ,the init process will play a bootanimation ,in my case it shows :
This is exactly what we should to remove.And now you could reboot the tablet into fastboot mode
Code:
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
In my case ,my tablet successfully launches the SetupWizard for registering device to google:

Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?

mardon85 said:
Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?
Click to expand...
Click to collapse
Edited

ZTE AXON 7 said:
otloader
2、fastboot boot rec/recovery.img(Here you should wait for about thirty seconds before initialization completed)
3、adb push systemrw_1.32_flashable.zip /sdcard
4、Go to Install->/sdcard/ and choo
Click to expand...
Click to collapse
ZTE AXON 7 said:
Edited
Click to expand...
Click to collapse
Thanks for this. Its the info I think a lot of us have been waiting for.
Did you find the following issues with your global ROM the same as the video below @ 27:14

That is some really good news, great work!

Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?

Thanks!

ZTE AXON 7 said:
h costs time and patience.
1、Download the super partition image file Mod edit: Link removed ,and extract super.img from it using 7z x ... command.
Click to expand...
Click to collapse
famaTV said:
Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?
Click to expand...
Click to collapse
Download link was updated

Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?

ZTE AXON 7 said:
Download link was updated
Click to expand...
Click to collapse
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.

ZTE AXON 7 said:
EXTRAC
Click to expand...
Click to collapse
mardon85 said:
Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?
Click to expand...
Click to collapse
So far so good, all works fine ,120hz refresh rate,precision 3 pencil ,precisicion keyboard,fast charging,etc...

There is a brand new ROM out today. Are you able to flash that now? Have you tried changing the region code via a hex editor?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

famaTV said:
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.
Click to expand...
Click to collapse
I updated to S212017 with this super image ,no problem:

ZTE AXON 7 said:
I updated to S212017 with this super image ,no problem:
View attachment 5506983
Click to expand...
Click to collapse
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.

mardon85 said:
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.
Click to expand...
Click to collapse
OTA,I changed the original ota update logic from aosp.

ZTE AXON 7 said:
OTA,I changed the original ota update logic from aosp.
Click to expand...
Click to collapse
Wow it seems you've cracked it even better than the Ali Express sellers. Most of the reports are that it can't OTA and the issue with the Settings search bar.
If mine ever clears Chinese customs (been stick there for 12days now) I'll get mine back and be able to play.

Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?

mardon85 said:
Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
View attachment 5507019
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
View attachment 5507027
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?
Click to expand...
Click to collapse
UPDATE... Fast boot commands do actually work. Even though it wont list devices commands like reboot work fine.
Did you have to unlock your bootloader for this? Have you kept widevine L1?

@ZTE AXON 7 you seem to be using Linux like me, mostly. I've used QFIL to flash the ROW ROMs but never did it from Linux. Do you have instructions on how to do that?
Oh wait, I reread your post. That script is for flashing the stock ROM, just like you said. Sorry about that.

Thank you for your work
I don't understand this very well. Do you have detailed operation steps?