Database Develop

Bricked phone.

Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.

Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224

Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV

Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.

Real appreciated, will keep you updated, if anything works ill post it here.

Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL

Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536

Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?

mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??

TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu

mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"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"
}

TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\

mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)

TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.

mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig

TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?

mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo

TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\

Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards

ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?

[ROM] Lenovo Z6 Pro L78051 QPST | Edl way |

Dear, Since I only support Arabic, I will present the necessary files with the pictures
This Files Only For: Lenovo Z6 Pro L78051
Settings > About phone > Technical details > Model > Lenovo L78051
You Can use | Tool All In One | to Force your Device go to Edl
{
"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"
}
Files:
Lenovo Z6 Pro L78051 ROM ZUI 11.0.483
Note:
No Need > Unlock the bootloader
https://www.zui.com/iunlock

Thanks. global rom ??

this is the chinese version with no google play but fixed bugs and real benchmark scores close to the top , for me it was easy to remove the bloatwares and install playstore and my apps
i ve already put negative review on the aliexpress seller who provided a hybrid rom claiming this to be a global release....

Guide for Lenovo Z6 Pro CH/ENG ROM flash (BIG PERFORMANCE BOOST COMPARED TO GLOBAL RO
First of all, some info
Okay guys, I’ve been struggling with this a few hours myself. I am by no means a professional. I think it’s safe to say I’m an amateur who had messed around with Android phones in the past.
As all of you may have noticed; the graphical performance and actually the general performance of the global ROM is really horrible for the Lenovo Z6 Pro. I couldn’t live with the fact that my benchmarks sucked and I felt like my phone wasn’t providing its full potential. After opening an official Lenovo forum some amazing people from the community pointed me in the right direction. Thanks Chaina and PcM_2019 for your amazing input!
The reason for this bad performance has to do with the Global ROM itself. It’s simply poorly optimized right now and receives barely any updates. I expect that in the future it will receive updates accordingly but as of right now it’s better to move over to the Chinese / English ROM.
Keep in mind there will be some Chinese apps and no Google Play in this ROM. You can add Google Play and delete most of the apps in case you’d like it better that way.
Time for the tutorial
MAKE SURE TO BACKUP ALL YOUR DATA, THIS IS A TUTORIAL FOR FLASHING DIFFERENT FIRMWARE FOR YOUR DEVICE AND IT WILL RESULT IN LOSING ALL YOUR DATA. Backup all data you wish to keep. Of course I cannot be held responsible for the loss of your data.
You will need a windows computer and a USB-C data cable.
1) Get all the required software for flashing your device to the preferred ROM.
a. First of all, the ROM itself. Because URL’s are not allowed, look on mirrors.lolinet under firmware for Lenovo L78051. It’s about a 3GB file.
b. Secondly; Qualcomm HS-USB driver.exe Boycracked has in his portfolio a a link to the Qualcomm usb driver. Google for it.
c. Lastly; the Qualcomm Flash Image Loader (QFil)
i. Androidbrick lists the latest Qualcomm flasher qfil gpst 2.7.460. Download this one!
2) We start off with the ROM. It’s a ZIP file, get 7zip or other archiving software to extract it.
3) Install the HS-USB driver – keep pressing next, don’t change anything.
4) Exctract and Install QFil. After the installation you can find the program in start by searching for “QFil”.
5) Place the extracted ROM folder in the following installation path of QFil for avoiding potential issues in the flashing process. The path should be: C:\Program Files (x86)\Qualcomm\QPST\bin. Just drop the entire folder in the bin.
6) You’re now ready for the real deal. Time to flash your device! Open QFil (search QFil in start) and follow these steps.
a. Open the configuration tab, click Firehose configuration and change device type from eMMC to UFS. Also “turn Reset After Download” on. Now press “OK”.
b. Now click “load content” Navigate to the path where you placed the new firmware, the path should be: C:\Program Files (x86)\Qualcomm\QPST\bin\L78051_CN_SECURE_USER_Q00745.01_P_ZUI_11.0.483_ST_190511_qpst and open the XML document “contents”. After this the Programmer path should be automatically filled in.
c. Now open developer options on your phone and turn on USB debugging and OEM unlocking. Change default USB configuration to File Transfer.
d. After this you can turn off your phone. When the phone is turned down completely we will now boot it into flash mode. Hold down the two volume buttons together and plug-in your USB-C data cable which is connected to your PC. QFil should now recognize your device as a COM port. The port should be automatically selected. If that’s not the case, then select port manually. You can now press the blue “Download Content” button.
e. That’s it. Your phone should now be flashed with your selected firmware.
Troubleshooting
If you were to run into problems, don’t worry you can always boot your phone normally again by holding down the power button for 10 seconds after having entered the flash mode. No damage will be done.
If QFIL gives Sahara error, go to device manager and update your COMM port drivers. Let Windows select the correct drivers automatically. Enter flash mode again and try the procedure again.
If it turns out the Sahara error is not fixed after a few attempts you could save a lot of time by using another computer, install everything on there again by following this tutorial and try it again.
If something is unclear, or you keep running into problems, let me know and I’ll try to help you to the best of my ability.
Special credits to Chaina
Additional sources that helped me put this tutorial together:
Boycracked
Mirrors.lolinet
Androidbrick

Has anyone figured out, how to fix google assistant issue in chinese rom? (default assist app is switchnig to none after deepsleep or kill process button) Turning off battery optimization or giving more permissions for google home or google services did not help.

China Official

opened a dispute with seller on aliexpress claiming the sale version as global and here is their joke answer here is no actual comparability between the evaluation software and the actual use. It is subject to actual usage. and The global version refers to language packs and channels. if i win i will take back 30usd as this amount i asked back open up all of you the same dispute , we must not tolerate this attitude and lies....

hello to all , how about twrp for this z6 pro ???
i need it bad .
thanks

help please .
i have unlocked bootloader and the global rom provided by phone seller has crashed , i have installed cn rom but no google play and my job depends on playstore apk's.
so please help with global rom for qfill or twrp and a backup of the global rom

here is the latest , i think
L78051_CN_SECURE_USER_Q00745.01_P_ZUI_11.0.542_ST_190610_qpst
https://drive.google.com/open?id=1r2oqL0jrFWO9MDMGMA6J0D-Jxd5rWryx

Background Services Off
Hi all
Firstly thanks for your efforts above! Tut was good and info too.
Since upgrading I received 2x ZUI updates and am now on the newest version.
I'm having so many problems now, my phone is a borderline frisbee!
Managed to install Google apps via Aptoide easy enough and now have everything installed.
Problem I'm having is: when closing apps; they don't run in background which means, WhatsApp's emails, etc. don't come through unless you go into the app. Secondly the settings do not save, so as mentioned above, setting the assistant also changing keyboard etc.
Does anyone know a fix? Is it worth reverting back/updating to the newest global ROM?
Please help!
Thanks

dnick88 said:
Hi all
Firstly thanks for your efforts above! Tut was good and info too.
Since upgrading I received 2x ZUI updates and am now on the newest version.
I'm having so many problems now, my phone is a borderline frisbee!
Managed to install Google apps via Aptoide easy enough and now have everything installed.
Problem I'm having is: when closing apps; they don't run in background which means, WhatsApp's emails, etc. don't come through unless you go into the app. Secondly the settings do not save, so as mentioned above, setting the assistant also changing keyboard etc.
Does anyone know a fix? Is it worth reverting back/updating to the newest global ROM?
Please help!
Thanks
Click to expand...
Click to collapse
You Need to Lock the app
Multitask button box / Lock the app

nakarmkir69 said:
help please .
i have unlocked bootloader and the global rom provided by phone seller has crashed , i have installed cn rom but no google play and my job depends on playstore apk's.
so please help with global rom for qfill or twrp and a backup of the global rom
Click to expand...
Click to collapse
Lock The boot then use this rom or another one

XQ55 said:
Lock The boot then use this rom or another one
Click to expand...
Click to collapse
Thanks for the idea, i have allready installed the latest(the one that i have posted the gdrive link above) without locking the bootloader, all the commands to lock the bootloader do not work.
The phone is working but no google play that is mandatory to install apk's from store

nakarmkir69 said:
Thanks for the idea, i have allready installed the latest(the one that i have posted the gdrive link above) without locking the bootloader, all the commands to lock the bootloader do not work.
The phone is working but no google play that is mandatory to install apk's from store
Click to expand...
Click to collapse
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ

XQ55 said:
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
Click to expand...
Click to collapse
Thanks a lot , got all done .
Please help me to get rid of the China default apk's.
Those that are system apk's and maybe how to lock the bootloader.

On Chinese ROM, does everyone experience battery drain? Think I've gone from 35 hours to 12 now

dnick88 said:
On Chinese ROM, does everyone experience battery drain? Think I've gone from 35 hours to 12 now
Click to expand...
Click to collapse
No drain with zui i am looking for global rom "the fake one" as some people call him

Same, I went from global version 11.0.054 ST to the newest CN version 11.0.575 ST and am having so many issues:
No push notifications, unless apps left open
No location on most apps including Google maps
Battery drain
Settings do not save
On the up side, camera quality and performance is now what I paid for!
I'm hoping I can track down a global ROM newer than .054 but seems impossible at the moment..

XQ55 said:
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
Click to expand...
Click to collapse
I have found some problems on zui :
Whatsapp does not notify with sound , only with popup
System default phone apk does not initiate call when touch call from recents or contacts , just increase the number of calls made.if i insert the number manually it make the call just perfect
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
dnick88 said:
Same, I went from global version 11.0.054 ST to the newest CN version 11.0.575 ST and am having so many issues:
No push notifications, unless apps left open
No location on most apps including Google maps
Battery drain
Settings do not save
On the up side, camera quality and performance is now what I paid for!
I'm hoping I can track down a global ROM newer than .054 but seems impossible at the moment..
Click to expand...
Click to collapse
New phone new problems , i just hope that twrp and lineage or mokee will appear soon, for me is the best way allso was the stock global rom that the phone had installed when arrive but it seems that nobody have it.
Maybe someone will have it and posted here

Help needed, 'Your device has failed a routine safety check and will not boot.' after relocking BL

Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru LG developers site. Then I tried to get TWRP working and it might be the problem (more on that later). So, in order to get TWRP one of the steps was to fastboot boot TWRP-judypn-boot.img. I did that but didn't know that to do next (cause when I did it the phone booted normally and I didn't fully understood what now), so I abandoned the idea and just loaded the backup from LG Mobile Switch. But, then I realized that with having unlocked bootloader I won't be able to use google pay, so after some reading I found out that Magisk might be the answer (it wasn't) so I managed to get Magisk root on my device. When I found out that it didn't help with google pay i tried to do what others on forum warned me not to - RElock the bootloader using 'fastboot oem lock'. And now it has locked bootloader. But also now of course the phone is rather bricked in a way that: I can enter both fastboot mode and download mode but: trying fastboot something I get the info that it is not possible in Lock State, and when trying to just flash kdz of that stock android 10 that I started with, the LGUP says error 'error 0x6004 crossDL' and below that it mentions 'judypn_lao_eea>@judypn_lao_co' so probably that first fastbooted img now prevents it from beign flashed. So now I cannot fastboot or flash anything, and trying to boot the phone gives me error "Your device has failed a routine safety check and will not boot." and also sometimes, below 'All slots are unbootable'.
I know that I screw up multiple times, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?

AnDevil said:
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru L<brevity>imes, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
Click to expand...
Click to collapse
Sounds kind of messy. Two things to know; 1) u most certainly can have google pay working on v40 w/10. I just added it on my (orig at&t) korean 10 30e / rooted / magisk / twrp. And 2) u should never ever try to relock the bootloader unless you just flashed a stock kdz to the device (completely unmodified, don't even choose language when it boots).
So the prob is what to do now. I'd first try to use fastboot to switch slots and see if the other side boots? And if that doesn't work / achieve what you want, then use lgup with dll version 1.14 to do the 'cross flash' (the 1.16 version doesn't work for that). Be sure to do a part DL (if u do the crossflash), then do a refurbish with the same kdz just after the part DL (of course you let the part DL complete, just shut it off after it boots all the way), then do refurb.
Ideally, what are u trying to accomplish?
cheers

Well, for now I would want to have bootloader locked, stock Android 10 on there. I'm probably going to leave the modding cause of the mess I've made - especially that I don't have much free time to tinker with phone when things go bad (and also as You can see I don't have enough experience to do so).
Right, so back to the point. How do you switch slots in fastboot? If by 'fastboot set_active a' (or b), then the result is 'not possible in lock state'. And for the other part (with LGUP and crossflashing), can You provide some kind of idiot-proof tutorial for that? Which files should I download and try to flash on the phone?

OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.

AnDevil said:
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
Click to expand...
Click to collapse
Okay, just so that it's clear, you do want to use 1.14 when going from 8 or 9 to 10. 1.16 won't recognize the older OS.
But, if you'd have done 1.16 Part DL from the beginning, it would have worked, as you've discovered. When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them).
Because you want to flash ebw 30b, there shouldn't be any reason to select all partitions. But I'd suggest (again), after doing the part DL, let the phone reboot of course, to complete. Then just shut it off and go back to LGUP and do a refurbish this time of the exact same kdz.
good luck

Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?

AnDevil said:
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
Click to expand...
Click to collapse
Sorry yes, that should have been 'there shouldn't be any reason NOT to select all partitions' (I think that's what the 'context' of the whole comment implied').
Yes, those steps are correct.
I think the confusion about lgup is around this; 1.14 is used if u need to 'cross flash' (going to diff OS). If you're not cross flashing then 1.16 will work. I think most people are cross flashing due to desire to get rid of bloatware and / or wanting to move to A10 when their OS doesn't have it or the kdz is unavailable.
you are in a somewhat unusual circumstance, having the only version of v40 that lg actually allows legit unlocking. So you never cross flashed (had to re read to realize that, it's that uncommon).
good luck

OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
{
"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"
}
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.

AnDevil said:
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
View attachment 5190441
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
Click to expand...
Click to collapse
So here's what I'd suggest, because you have an ebw version, which I believe has dual sim, and many many have had issues with those and losing the dual sim capability (very frustrating and difficult to get back).
Go to the v40 rom forum and Markus (los developer), put in the first post of his lineage rom an invite to the lgv40 tele gram group. Use that and join tele group and there are a lot of international users there, they can guide you with this problem (they have and use that specific device, among others).
If you want to do more reading on this, follow this link. It's the lg firmware dl page and do a search from the top for 'judy'. You'll see others have had the same error you're getting, and used lgup 1.15 command line to get around it.
I don't think it's because of what u flashed with fastboot (twrp), judypn is the name of the device, not specific to twrp.
So join the tele group and also (here on xda) look in the thread about 'unlocking all devices - except t-mo'. Not to unlock it, but to learn to use qfil. You will probably need that.
cheers

Ok, definitely will do that. Thank You very much for Your help

Question [CLOSED] Pls help to fix: dm-verify corruption

For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
{
"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"
}
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?

fm663 said:
For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
View attachment 5458547
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?
Click to expand...
Click to collapse
Try with:
adb disable-verity
or flashing blank/null vbmeta:
fastboot --disable-verity flash vbmeta vbmeta.img or:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta vbmeta.img

@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?

fm663 said:
@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?
Click to expand...
Click to collapse
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?

SubwayChamp said:
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?
Click to expand...
Click to collapse
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?

fm663 said:
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?
Click to expand...
Click to collapse
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.

SubwayChamp said:
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.
Click to expand...
Click to collapse
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way

fm663 said:
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way
Click to expand...
Click to collapse
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.

SubwayChamp said:
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.
Click to expand...
Click to collapse
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching

simika said:
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching
Click to expand...
Click to collapse
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you

fm663 said:
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you
Click to expand...
Click to collapse
sure:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
here you'll find answers about root, dm-verity and much more, always related to poco m3 pro and redmi note

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
If you want to stay locked no way to disable this warning message but if you decide to unlock your device and root it, it is pretty easy to fix it, one of the methods available is what I indicated, flashing a blank/null vbmeta through specific fastboot commands, there are other methods though, but this is the most universal and easy to use.
In regard to the CTS issue, I don't use GPay, so I can't tell you, but no better place that the Magisk Discussion Thread, it is the appropriate thread where you can find all the info from all the members affected on that, in the meantime you also can take a read on this https://droidholic.com/fix-safetynet-failed-cts-profile-false/

1. Hello friends, there are two ways to fix this problem. First, you need Root, and after using Root, you need to download any file manager and give Root permission. You need to backup your baseband, nvram nvdata nvcfg after backup Save, you also need an MTK Bypass You can search for MTK Auth Bypass Tool through Google. To download, you also need to use SP Flash to flash the machine. You need to download the official firmware package. You can download it through xiaomirom.com, download the corresponding version, and use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for the completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, but you have backed up. Boot through fastboot to unlock the BL lock, and proceed fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. congratulations your baseband is back, i am a newbie and my instructions are very Not comprehensive, such as where is the baseband position, but I have too many characters, I will list the baseband position. 2. Replace a new motherboard, all mobile phone problems are solved.
Hope to help you.

THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://forum.xda-developers.com/t/how-to-get-rid-of-dm-verity-corruption-on-boot.4290677/
Regards,
shadowstep
Forum Moderator

Question Update OnePlus 10 Pro from HydrogenOS (CN) to OxygenOS (EU/GL/IN) without rooting

This process uses Oxygen Updater as I haven't found the full EU/GL/IN stock ROMs anywhere else.
Update OnePlus 10 Pro NE2210 (CN) from HydrogenOS (NE2210_11_A.12) to OxygenOS EU (NE2213_11_A.12)
Download [Play Store] apk and install
[Play Store] install [Oxygen Updater]
[Oxygen Updater] Device: One Plus 10 Pro EU
[Oxygen Updater] Update method: Stable (full)
[Oxygen Updater] Settings > Advanced Mode - activate
[Oxygen Updater] Update > Download the full stock ROM (4.15 GB)
Activate Developer Options
Update > Local install
CURRENT STATUS: Verification failed
I've done this process before for other OnePlus phones and it was very straightforward. For some reason is not working with this OnePlus 10 Pro. Any insight on how to continue?
Thanks!

Bump, redownloaded again the EU version, resetted phone, still fails. Whyyy! Anyone can advise how to go from Hydrogen to Oxygen? Thanks!

Short description for "How to switch from ColorOS (Chinese version) to OxygenOS (IND/EU) on OnePlus 10 Pro". I did the flash under Windows 10, even if I'm usually a Linux guy...
BEFORE DOING THIS MANUAL, MAKE A BACKUP OF THE DATA OF YOUR DEVICE! Your phone will be DELETED completely!
1.)
- Download the desired ROM (Oxygen OS 12.1 A11 (IND) or Oxygen OS 12.1 A12 (EU) (Auntie Google has the answer, effective April 2022) -> extract
- download OnePlus_USB_driver.zip:
https://oneplususbdrivers.com/download-oneplus-usb-driver/ -> extract
- download Android Platform SDK:
https://www.techspot.com/downloads/downloadnow/5425/?evp=de0a68064118855fcddcc3980a2143c4&file=6062 -> extract
- download "Fastboot Enhance Tool": https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ -> extract
2.) First of all, disable driver signature check for Windows 10, because the OnePlus drivers are not signed (yet).
3.) After restarting Windows, install the OnePlus drivers by executing the .exe file from the extracted folder.
4.) Copy the payload.bin file from the downloaded ROM into the folder where the fastbootenhance tool is located
5.) Enable Developer Options on your phone
6.) Enter the Developer Options, enable OEM unlock and USB debugging there
7.) Now connect your OnePlus 10 Pro to your computer by a USB cable. Make sure it's started, screen unlocked and charged over 60%
8.) On your computer, open File Explorer and switch to the Android SDK folder. Click in the address line above and type CMD [Enter]. A CMD window opens in the SDK folder.
9.) In CMD, type "adb devices". A new line should appear with the encrypted name of your device. When an empty line is returned, check the driver installation. If this line returns the name, but the suffix "not allowed", you must first allow this connection ON YOUR PHONE. Disconnect and reconnect your device and confirm the popup that appears on your phone! (Best is to enable "Always allow connections from this computer"!)
10.) Now type "adb reboot bootloader" in CMD. Your telephone restarts automatically to bootloader mode. In this mode your phone should tshow you it's name and beside of some other information you don't need, that the bootloader is LOCKED.
11.) Type in CMD "adb flashing unlock [Enter]". Now your phone should restart and ask you, if you want to unlock the bootloader or do not unlock the bootloader. With the volume buttons, switch to "UNLOCK BOOTLOADER" and confirm by pressing the Power Button.
12.) After doing so, restart your phone. After rebooting, go back to CMD and type "adb reboot fastboot". Your phone now should restart to "FASTBOOTD MODE". You are asked to choose a language (I recommend english after all... ;-) )
13.) Open the "Device Manager" on your computer.
14.) If device manager shows you some unknown device like "Android: ! 'ossi'" or similar, your device is not recognized in fastbootd mode. In that case continue with pt. 15. Otherwise continue with pt. 19
15.) Right-click on the unknown Android device and choose "Update driver..." -> "Search my computer for drivers" -> "Pick from a list of available drivers on my computer"
16.) When OnePlus drivers where installed correctly some steps above, Device Manager should suggest you 3 different possible drivers. Choose "OnePlus ADB Interface Manager" and confirm your choice. Windows will warn you that a wrong choice will crash Windows. Confirm also this warning.
17.) If everything went good, the before unknown device will change to an Android ADB Interface Device. When that happend, everything is good and you're good to go on.
18.) Just to be really sure: Type in CMD again "fastboot devices" and your computer should tell you the s/n of your phone with the suffix "fastboot". This will tell you your device is recognized in fastboot mode.
19.) Start "FASTBOOTENHANCE" tool from the respective folder (Folder name "release")
20.) Now you can follow the instructiions here at pt. 8.:
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
Puuuuuuh! That was enoying..! Maybe I have missed something... If so, please tell me by PN and I will complement this manual. But at this time, I guess it should work. I did it right like that this day - and it works fine! Finally I have my foremost chinese OP10Pro with a EU ROM in (swiss) german!
And if it works just like that (after my manual), please let me know as well!
Have fun! Oliver
Oh, there's something I forgot: I had after flashing still about a dozen of chinese apps I had to delete manually. Don't be surprised by that!

Thank you! Can you relock the bootloader afterwards? What model shows in the phone info screen?

This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?

Lynxy0 said:
This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?
Click to expand...
Click to collapse
If you relock the bootloader and reset, does it behave like a normal non-rooted phone with EU firmware?

Ultimatum99 said:
If you relock the bootloader and reset, does it behave like a normal non-rooted phone with EU firmware?
Click to expand...
Click to collapse
Good shout - Let me try that and get back to you.

Yes, this worked

Lynxy0 said:
Yes, this worked
Click to expand...
Click to collapse
Did the Chinese apps disappear once you locked the bootloader and resetted? Which method did you use to relock? What model is being shown in the phone info page? Thanks!!!

No they did not. After the first flash, the OP Launcher was back (previously it was Google Phone Launcher) . I factory reset and Chinese apps were back.

Ultimatum99 said:
Thank you! Can you relock the bootloader afterwards? What model shows in the phone info screen?
Click to expand...
Click to collapse
Hi Ultimatum99
I didn't relock my bootloader yet, but I'll do it in the next days, I'll post the update here. (Speaking technically it's possible, yes, but I don't know yet what happens...) And my model shows "NE2213" after the update.

Lynxy0 said:
This worked for me! Thanks very much.
After installing EU firmware, I factory reset the phone but Google Pay wont work saying the phone is rooted but when I launch Root Checker, it says ' Sorry! Root access is not properly installed on this device'
Is the root broken? Do I need to root again? Any ideas how to fix?
Click to expand...
Click to collapse
Hi Lynxy0
No, your phone is not rooted, but the bootloader is still unlocked, even after the update. And that means your phone is vulnerable to attacks from outside. So Google Pay tells you your phone is rooted, just to keep you safe. Try to relock your bootloader, this should solve the problem. (I didn't do it yet, but I'll post the update when I've done it.)

Lynxy0 said:
Yes, this worked
Click to expand...
Click to collapse
Haha... I was too late then!(See my last replay...) But thanks for the feedback!

Lynxy0 said:
No they did not. After the first flash, the OP Launcher was back (previously it was Google Phone Launcher) . I factory reset and Chinese apps were back.
Click to expand...
Click to collapse
This is unfortunately a bad thing... Some chinese apps are really back, even after flashing and resetting the device. But I could delete them manually. Yeah, it took me a few minutes, but at least, I had (finally) my beloved OxygenOS back! (After I crashed my OP6T almost 2 years ago, I chose a Oppo FindX 2 Pro - and after almost 2 years I still regret to have paid for this phone... The hardware was really cool, but ColorOS is ... So I was really terrified when I learned my brand new [chinese] OP10Pro had ColorOS installed by default..!)

Loba74 said:
This is unfortunately a bad thing... Some chinese apps are really back, even after flashing and resetting the device. But I could delete them manually. Yeah, it took me a few minutes, but at least, I had (finally) my beloved OxygenOS back! (After I crashed my OP6T almost 2 years ago, I chose a Oppo FindX 2 Pro - and after almost 2 years I still regret to have paid for this phone... The hardware was really cool, but ColorOS is ... So I was really terrified when I learned my brand new [chinese] OP10Pro had ColorOS installed by default..!)
Click to expand...
Click to collapse
Let us know if you manage to relock the bootloader and share the full process please, I can update the guide with your findings. Thanks!

Loba74 said:
Hi Lynxy0
No, your phone is not rooted, but the bootloader is still unlocked, even after the update. And that means your phone is vulnerable to attacks from outside. So Google Pay tells you your phone is rooted, just to keep you safe. Try to relock your bootloader, this should solve the problem. (I didn't do it yet, but I'll post the update when I've done it.)
Click to expand...
Click to collapse
It was pretty straight forward, unroot by uninstalling Magisk. adb into the bootloader and send the adb bootloader lock command, then boom, its locked. It wipes your phone in doing so, so you will have to everything again.

Lynxy0 said:
It was pretty straight forward, unroot by uninstalling Magisk. adb into the bootloader and send the adb bootloader lock command, then boom, its locked. It wipes your phone in doing so, so you will have to everything again.
Click to expand...
Click to collapse
Thanks @Lynxy0
So, just to clarify, after relocking the bootloader (which causes a full wipe) Google Pay works again?
Also, do you know if Netflix installs after relocking the bootloader? (Because in most phones once the bootloader is unlocked the status changes from "L1" and doesn't change back again after locking. Netflix reads that status, and Netflix will only install if it is L1.)
Many thanks

Hi Guys
It seems like a straight forward process, It was all good until I try flash it. . When I loaded the downloaded zip file, I couldn't get the payload file in fastbootd and flash it those buttons are missing(after I load it to payloadDumper .) . I thought it might be file download has some issue. I tried different ones , the same thing.
any ideas?
{
"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"
}
C.

never mind , I figured it out . My case is the ADB driver problem , even u unlocked the bootloader , somehow the fastbootenhance wont work correctly , strange , ... but.
C

@Loba74 I think there is an error in your guide, in step 11 maybe it should say "fastboot flashing unlock" rather than "adb flashing unlock" ?