Credit to @user_ScoTTT for providing the files and instructions.
So @user_ScoTTT has unlocked his bootloader for his Chinese version via official methods and was kind enough to share with us the files and instructions.
The instructions he provided are as below as are the files if anyone wishes to play around.
Disclaimer: I have not tested this.
1. Download and Unpack the latest ozip full update package of the Chinese version of oppo find x2 pro by dragging the Ozip onto the ozip2zip.exe. (You can use the boot.img file i have provided if you prefer)
2. extract the boot.img from it (be sure to back it up), (after unlocking the bootloader) you only need to transfer the boot.img file to your phone.
3. Install magisk manager on the phone, click "install", click "fix a file", select the boot.img you extracted from the ozip image.
4. Turn off the phone, press and hold the volume-& power button to restart to bootloader, connect to the data Connect to the PC, use
fastboot flash boot magisk_patched.img
5. flash vbmeta.img with "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable Verified Boot otherwise you will face the problem of not being able to boot.
6. "fastboot reboot" (reboot)
After that, your phone will reboot and enter the system, open magisk manager, it will show that magisk has been successfully installed. (Before this, you will be prompted that you need to repair it, click OK, and it will automatically restart once)
Enjoy Root!
Files can be found here:
https://drive.google.com/drive/folders/1cqKwrOSX_0fAdgZSRqG1_Lk3AQ5-COZs?usp=sharing
Hope this helps kick off some more development on these great devices.
Thanks all.
Any word on the global / EU versions with root?
Sent from my CPH2025 using Tapatalk
kevinireland11 said:
Any word on the global / EU versions with root?
Sent from my CPH2025 using Tapatalk
Click to expand...
Click to collapse
Before that, you need to unlock your phone
user_ScoTTT said:
Before that, you need to unlock your phone
Click to expand...
Click to collapse
How do we unlock bootloader with non Chinese versions?
Sent from my CPH2025 using Tapatalk
kevinireland11 said:
How do we unlock bootloader with non Chinese versions?
Sent from my CPH2025 using Tapatalk
Click to expand...
Click to collapse
We have to wait for the latest official news.
user_ScoTTT said:
We have to wait for the latest official news.
Click to expand...
Click to collapse
Keep us up to date please lol
Sent from my CPH2025 using Tapatalk
Nice .
Waiting for global version
user_ScoTTT said:
We have to wait for the latest official news.
Click to expand...
Click to collapse
Can I flash global rom after I unlockbootloader ? And what if I can flash, do I need to keep bootloader unlocked ? Because maybe OTA will be affected if I doesn't lock the bootloader again, but is it the same method as pixel phones ? Fastboot oem lock ' will work like this ? I forget also to ask do I need to be registered in depth testing program so that I can unlockbootloader ?
when I adb reboot bootloader the phone just reboots into the OS, have i done something wrong?
Mohamadshuwaiee said:
Can I flash global rom after I unlockbootloader ? And what if I can flash, do I need to keep bootloader unlocked ? Because maybe OTA will be affected if I doesn't lock the bootloader again, but is it the same method as pixel phones ? Fastboot oem lock ' will work like this ? I forget also to ask do I need to be registered in depth testing program so that I can unlockbootloader ?
Click to expand...
Click to collapse
Yes, the method is the same as the pixel phone. At present, the depth testing is not open to the international version of ROM.
---------- Post added at 04:12 PM ---------- Previous post was at 04:10 PM ----------
gb155 said:
when I adb reboot bootloader the phone just reboots into the OS, have i done something wrong?
Click to expand...
Click to collapse
Just press and hold the vol - and power key to start the machine.
Sage said:
Credit to @user_ScoTTT for providing the files and instructions.
So @user_ScoTTT has unlocked his bootloader for his Chinese version via official methods and was kind enough to share with us the files and instructions.
The instructions he provided are as below as are the files if anyone wishes to play around.
Disclaimer: I have not tested this.
1. Download and Unpack the latest ozip full update package of the Chinese version of oppo find x2 pro by dragging the Ozip onto the ozip2zip.exe. (You can use the boot.img file i have provided if you prefer)
2. extract the boot.img from it (be sure to back it up), (after unlocking the bootloader) you only need to transfer the boot.img file to your phone.
3. Install magisk manager on the phone, click "install", click "fix a file", select the boot.img you extracted from the ozip image.
4. Turn off the phone, press and hold the volume-& power button to restart to bootloader, connect to the data Connect to the PC, use
fastboot flash boot magisk_patched.img
5. flash vbmeta.img with "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable Verified Boot otherwise you will face the problem of not being able to boot.
6. "fastboot reboot" (reboot)
After that, your phone will reboot and enter the system, open magisk manager, it will show that magisk has been successfully installed. (Before this, you will be prompted that you need to repair it, click OK, and it will automatically restart once)
Enjoy Root!
Files can be found here:
https://drive.google.com/drive/folders/1cqKwrOSX_0fAdgZSRqG1_Lk3AQ5-COZs?usp=sharing
Hope this helps kick off some more development on these great devices.
Thanks all.
Click to expand...
Click to collapse
I have the Chinese version I need to register in depth testing and wait for approval to unlock bootloader first ?
Mohamadshuwaiee said:
I have the Chinese version I need to register in depth testing and wait for approval to unlock bootloader first ?
Click to expand...
Click to collapse
yup thats right. you need official unlock of the bootloader first.
Sage said:
yup thats right. you need official unlock of the bootloader first.
Click to expand...
Click to collapse
So does this apply to the models bought in the UK? Don't tell me this is another Huawei situation all over again? They're notorious for not allowing bootloader unlocking!
Sent from my [device_name] using XDA-Developers Legacy app
"So does this apply to the models bought in the UK? Don't tell me this is another Huawei situation all over again? They're notorious for not allowing bootloader unlocking!"
Yep! EE Model here, the App says "Customised Carrier Device" so it wont let me Unlock, so yes. UK for the most part / carrier phones are not allowed..
Stan464 said:
"So does this apply to the models bought in the UK? Don't tell me this is another Huawei situation all over again? They're notorious for not allowing bootloader unlocking!"
Yep! EE Model here, the App says "Customised Carrier Device" so it wont let me Unlock, so yes. UK for the most part / carrier phones are not allowed..
Click to expand...
Click to collapse
What app bud?
Sent from my [device_name] using XDA-Developers Legacy app
speedyjay said:
What app bud?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Oppo has Released an App (works very well in China) and allows you to setup "in Depth Testing". Check the "Root Guide" Threat out in relation to this phone...
Hope this helps.
Hello,
My find X2 pro and unlocked but I can't rotate it, it doesn't start, there is a red triangular at startup indicating a problem with the recovery.
I think the vbmeta.img file doesn't want to install.
Anyone have an idea? thank you.
They're never be root, to get rid of these carriers oppos ****e
kevinireland11 said:
They're never be root, to get rid of these carriers oppos ****e
Click to expand...
Click to collapse
i have a pure global version. no carrier ****e on mine
Sage said:
i have a pure global version. no carrier ****e on mine
Click to expand...
Click to collapse
Wish we could flash unbranded...
Related
can i fastboot my kiwl22 (honor 5x) which is in b370 without any problems (bootloop) and flash in lineage or RR N?
if yes, please let me know hiw to fastboot, and any suggestions for the best ROM availabke to be put on kiw l22 without major problems?
Here's the guide to unlock bootloader: https://forum.xda-developers.com/honor-5x/how-to/how-to-bootloader-unlock-honor-5x-t3328600
For the ROM, I recommend you LineageOS or Resurrection Remix, which is very customizable
Potato997 said:
Here's the guide to unlock bootloader: https://forum.xda-developers.com/honor-5x/how-to/how-to-bootloader-unlock-honor-5x-t3328600
For the ROM, I recommend you LineageOS or Resurrection Remix, which is very customizable
Click to expand...
Click to collapse
i have my phone in b370 right now. and i don't find any saying ENABLE OEM UNLOCK.
can you go me with this?
hemanth.k said:
i have my phone in b370 right now. and i don't find any saying ENABLE OEM UNLOCK.
can you go me with this?
Click to expand...
Click to collapse
Did you enabled developer settings? It should be one of the first options
Potato997 said:
Did you enabled developer settings? It should be one of the first options
Click to expand...
Click to collapse
this one
hemanth.k said:
this one
Click to expand...
Click to collapse
Maybe you could try to unlock bootloader to see it's already allowed ?
Potato997 said:
Maybe you could try to unlock bootloader to see it's already allowed ?
Click to expand...
Click to collapse
won't the be any problem? please don't mind me asking these many things. i am a person with nill knowledge over these things. just that I'm bored with this emui. i want to change the ROM
and my phone kiwl22 is right now in b370
hemanth.k said:
won't the be any problem? please don't mind me asking these many things. i am a person with nill knowledge over these things. just that I'm bored with this emui. i want to change the ROM
and my phone kiwl22 is right now in b370
Click to expand...
Click to collapse
No, if it's not allowed you will just get a message like "command not allowed" and nothing will happen
Potato997 said:
No, if it's not allowed you will just get a message like "command not allowed" and nothing will happen
Click to expand...
Click to collapse
so this says my phone is already unlocked?
and i can flash any rom like lineage or rrn directly via Fastboot ?
hemanth.k said:
so this says my phone is already unlocked?
and i can flash any rom like lineage or rrn directly via Fastboot ?
Click to expand...
Click to collapse
Boot to fastboot and try to unlock bootloader, it will either says it's not allowed if OEM unlock is not allowed or unlock the bootloader. After that if you manage to unlock it, you have to flash TWRP
hemanth.k said:
so this says my phone is already unlocked?
and i can flash any rom like lineage or rrn directly via Fastboot ?
Click to expand...
Click to collapse
Bootloader is locked by default ? do you have unlock code? You may check my threads for getting unlock code. In order to flash TWRP, you have to downgrade from B370 to B320/B340 ? otherwise you will get endless boot loops. Download B320 firmware package, extract it, copy "update.app", create a folder "dload" on External SD card and paste "update.app". Turn off your phone, hold vol up+vol down+power button simultaneously and release all the three buttons when Honor logo shows up. Wait until stock rom flashing finishes. I recommend you to do a factory reset. Done! You may proceed to unlock bootloader and flash twrp.
I have ALP-L29 (c185) Running emui 9.1.0.32 and unlocked bootloder. Is there any way to relock bootloader. I have tried DC unlocker (says chipset is not competible), Multi-tool, and fastboot command but none of them worked. Also tried to restore an factory reset with Erecovery but still unlocked. I am planning to sell my phone but probably buyer won't want root or unlocked bootloder
draqkin said:
I have ALP-L29 (c185) Running emui 9.1.0.32 and unlocked bootloder. Is there any way to relock bootloader. I have tried DC unlocker (says chipset is not competible), Multi-tool, and fastboot command but none of them worked. Also tried to restore an factory reset with Erecovery but still unlocked. I am planning to sell my phone but probably buyer won't want root or unlocked bootloder
Click to expand...
Click to collapse
Update using a dload firmware. It will lock it.
However, there seem to be no free one for ALP C185 9.1 :/
ante0 said:
Update using a dload firmware. It will lock it.
However, there seem to be no free one for ALP C185 9.1 :/
Click to expand...
Click to collapse
Sorry but what is "a dload firmware"?? I am familiar with dload folder methode ( force Update) but is there a special kind of firmware for this methode?
draqkin said:
Sorry but what is "a dload firmware"?? I am familiar with dload folder methode ( force Update) but is there a special kind of firmware for this methode?
Click to expand...
Click to collapse
Service firmware. And yes, it's special. Firmware from Huaweis own server (hicloud) is Online only, and can't be used to lock bl.
Service firmware is Offline, so you can flash it using an OTG cable and a memory stick.
Or, since you're rooted, you can place it directly in /data/update/dload/ and skip the OTG cable part.
You'd then reboot and hold VOL UP + VOL DOWN (OTG plugged in to phone if not /data/update/dload is used) and phone will start in force update mode and start update.
ante0 said:
Service firmware. And yes, it's special. Firmware from Huaweis own server (hicloud) is Online only, and can't be used to lock bl.
Service firmware is Offline, so you can flash it using an OTG cable and a memory stick.
Or, since you're rooted, you can place it directly in /data/update/dload/ and skip the OTG cable part.
You'd then reboot and hold VOL UP + VOL DOWN (OTG plugged in to phone if not /data/update/dload is used) and phone will start in force update mode and start update.
Click to expand...
Click to collapse
Hmm then i assume Team MT firmwares are not dload firmwares. So is there any way to get this special firmwares for my phone?
draqkin said:
Hmm then i assume Team MT firmwares are not dload firmwares. So is there any way to get this special firmwares for my phone?
Click to expand...
Click to collapse
Found one on AH.ru that should work: https://androidhost.ru/1MH5
I downloaded and confirmed it's a service firmware anyway
ante0 said:
Found one on AH.ru that should work: https://androidhost.ru/1MH5
I downloaded and confirmed it's a service firmware anyway
Click to expand...
Click to collapse
Thanks much ? i will give it a try. One last question if i restore and relock bootloader with this firmware, can i unlock bootloder again with my old unlock code? ( in case i need to root again) ?
draqkin said:
Thanks much ? i will give it a try. One last question if i restore and relock bootloader with this firmware, can i unlock bootloder again with my old unlock code? ( in case i need to root again) ?
Click to expand...
Click to collapse
Yes, as long as you don't modify oeminfo too much. But update will not change unlock code.
Oh yeah, I noticed the dload came without instructions. If you use otg and memory card you just copy the 'dload' folder (after extracting from zip) and paste on a memory stick. Then plug in otg cable in phone and reboot while holding vol up + down. If you use /data/update/ you'd have to transfer files using adb push to /sdcard/ and from a command prompt:
adb push update_sd.zip /sdcard/
adb push update_sd_ALP-L29_hw_meafnaf.zip /sdcard/
adb shell
su
mkdir -p /data/update/dload/ALP-L29_hw_meafnaf/
mv /sdcard/update_sd.zip /data/update/dload/
mv /sdcard/update_sd_ALP-L29_hw_meafnaf.zip /data/update/dload/ALP-L29_hw_meafnaf/
meafnaf zip might be named differently, I turned off computer so can't check.
After this, still in adb shell:
echo --factory_sd_update > /cache/recovery/command
reboot
Phone will reboot to update mode and flash firmware.
After this you should be locked
Thanks again
ante0 said:
Found one on AH.ru that should work: https://androidhost.ru/1MH5
I downloaded and confirmed it's a service firmware anyway
Click to expand...
Click to collapse
Look like zip file has a password. Do you have it by any chance?
draqkin said:
Look like zip file has a password. Do you have it by any chance?
Click to expand...
Click to collapse
It's 'ministryofsolutions.com'
Try disabling find my device
I've had this problem before as well with adb, first set the phone up and disable find my device, then try to relock the bootloader again with adb.
Hi
My model is ALP-L29
software version : 9.1.0.321(C636E5R1P13)
I unlocked my bootloader long time ago with the code from huawei.
Now i would like to relock it using dload format method.
Where do i download the fw to perfrom this method? and what version should i download?
carnby24 said:
Hi
My model is ALP-L29
software version : 9.1.0.321(C636E5R1P13)
I unlocked my bootloader long time ago with the code from huawei.
Now i would like to relock it using dload format method.
Where do i download the fw to perfrom this method? and what version should i download?
Click to expand...
Click to collapse
Try restore it from eRecovery ,, or there's rom in androidhost site but you need @ante0 for confirming if this service firmware or not you can download it then extract it and see if there's dload service or not .
https://androidhost.ru/1MoI
hamadazh said:
Try restore it from eRecovery ,, or there's rom in androidhost site but you need @ante0 for confirming if this service firmware or not you can download it then extract it and see if there's dload service or not .
https://androidhost.ru/1MoI
Click to expand...
Click to collapse
If it contains a dload folder it should work.
So if im having the current fw 9.1.0.321(C636E5R1P13), what should the service firmware be?
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
ante0 said:
If it contains a dload folder it should work.
Click to expand...
Click to collapse
hamadazh said:
Try restore it from eRecovery ,, or there's rom in androidhost site but you need @ante0 for confirming if this service firmware or not you can download it then extract it and see if there's dload service or not .
https://androidhost.ru/1MoI
Click to expand...
Click to collapse
Are you sure Erecovery will lock back my bootloader?
carnby24 said:
So if im having the current fw 9.1.0.321(C636E5R1P13), what should the service firmware be?
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
Are you sure Erecovery will lock back my bootloader?
Click to expand...
Click to collapse
Erecovery will not lock bootloader.
Generally you'd want a service firmware for the current build you're on, but that's now always possible. Any 9.1 C636 should work though.
hamadazh said:
Try restore it from eRecovery ,, or there's rom in androidhost site but you need @ante0 for confirming if this service firmware or not you can download it then extract it and see if there's dload service or not .
https://androidhost.ru/1MoI
Click to expand...
Click to collapse
Its asking for a password when i unzip it? Anyone know what is the password?
Oh okay Never mind, found out the password of some googling.
ministryofsolutions.com
i try the version of Magisk 23.0 but this is not worked.
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Nevermind figured it out
Kylewolf said:
Nevermind figured it out
Click to expand...
Click to collapse
Before you do anything, a unlocked bootloader is must required.
JaneValley said:
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Click to expand...
Click to collapse
good job my friend.
JaneValley said:
Before you do anything, a unlocked bootloader is must required.
Click to expand...
Click to collapse
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Where the hell do i find the official firmware, thats where im stuck
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
jporter396 said:
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
Click to expand...
Click to collapse
same am stuck at bootloader unlock rn. Cannot flash
olavbson said:
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Click to expand...
Click to collapse
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
What about DRM keys? how do u deal with that.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
rom4ster said:
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
Click to expand...
Click to collapse
I haven't noticed anything that's not working buddy
AJHutchinson said:
I haven't noticed anything that's not working buddy
Click to expand...
Click to collapse
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
rom4ster said:
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
AJHutchinson said:
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
Click to expand...
Click to collapse
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
rom4ster said:
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
Click to expand...
Click to collapse
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
AJHutchinson said:
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
Click to expand...
Click to collapse
Also is
Code:
Fastboot devices
showing a device? Maybe it's not installed properly?
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
jporter396 said:
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
Click to expand...
Click to collapse
Annoying aye, my issue was with the IMEI I must have been putting a wrong digit in but it worked eventually
I have an ANE-LX2 build number C636E4R1P5 (I live in Europe), latest security patch installed is from July 2020 and the OTA updater can't find any new update. It seems like on European firmware C432 the updates are released regularly. Is it possible to switch to this region and keep receiving updates?
I've read may threads but don't know where to start. Thanks in advance
ImFrengo said:
I have an ANE-LX2 build number C636E4R1P5 (I live in Europe), latest security patch installed is from July 2020 and the OTA updater can't find any new update. It seems like on European firmware C432 the updates are released regularly. Is it possible to switch to this region and keep receiving updates?
I've read may threads but don't know where to start. Thanks in advance
Click to expand...
Click to collapse
You have to unlock the bootloader first , for free or using paid service ,
info .
If you choose paid service , you have to download to EMUI 8 via HiSuite. If the rollback option is not available with your HiSuite ("switch to the older version" or "Earlier version"), you must downgrade to the lower EMUI 9.1 build number doing the dload method flashing Service ROM.
I can't give you a link because of forum rules, but you can google it, search for 'ANE-LX2 9.1.0.209(C636E4R1P5T8) FULL STOCK' (password: ministryofsolutions.com ).
Note: This process will erase your phone!
Then try again downgrade with HiSuite.
After successfully downgrading to Oreo you need downgrade to 8.0.140 , download here .
Running 8.0.140 you should be able to use HCU-Clent etc., get code and unlock your bootloader.
Only then will the difficult part of debranding come .
The question is whether it is worth doing...
-Alf- said:
You have to unlock the bootloader first , for free or using paid service ,
info .
If you choose paid service , you have to download to EMUI 8 via HiSuite. If the rollback option is not available with your HiSuite ("switch to the older version" or "Earlier version"), you must downgrade to the lower EMUI 9.1 build number doing the dload method flashing Service ROM.
I can't give you a link because of forum rules, but you can google it, search for 'ANE-LX2 9.1.0.209(C636E4R1P5T8) FULL STOCK' (password: ministryofsolutions.com ).
Note: This process will erase your phone!
Then try again downgrade with HiSuite.
After successfully downgrading to Oreo you need downgrade to 8.0.140 , download here .
Running 8.0.140 you should be able to use HCU-Clent etc., get code and unlock your bootloader.
Only then will the difficult part of debranding come .
The question is whether it is worth doing...
Click to expand...
Click to collapse
Thank you, HiSuite allows me to downgrade to 8.0.0.192.
After downgrading to 8.0.0.140 as well and unlocking the bootloader, is the debranding part particularly difficult?
ImFrengo said:
Thank you, HiSuite allows me to downgrade to 8.0.0.192.
After downgrading to 8.0.0.140 as well and unlocking the bootloader, is the debranding part particularly difficult?
Click to expand...
Click to collapse
Read the instructions carefully and completely, check unfamiliar terminology by google or xda.
Here you go
Ok, just one doubt: the files in the procedure are for ANE-LX1 while mine is ANE-LX2, does it make any difference?
ImFrengo said:
does it make any difference?
Click to expand...
Click to collapse
Of course.
Are all those 4 files (oeminfo, TWRP, stock recovery, service ROM) model-dependent? If yes, do you know where I can find the files for ANE-LX2?
Thank you
ImFrengo said:
Are all those 4 files (oeminfo, TWRP, stock recovery, service ROM) model-dependent?
Click to expand...
Click to collapse
Oeminfo and Service ROM only.
ImFrengo said:
If yes, do you know where I can find the files for ANE-LX2?
Click to expand...
Click to collapse
I thought you wanted to do a rebrand to ANE-LX1 C432 ...
P.S.: You might be better off staying on the C636
-Alf- said:
I thought you wanted to do a rebrand to ANE-LX1 C432 ...
Click to expand...
Click to collapse
Sorry about the confusion, I thought there was a specific C432 for ANE-LX2... I'm still new to this.
Does this mean my ANE-LX2 would "become" an ANE-LX1 C432?
ImFrengo said:
Does this mean my ANE-LX2 would "become" an ANE-LX1 C432?
Click to expand...
Click to collapse
Exactly.
-Alf- said:
Exactly.
Click to expand...
Click to collapse
Ok here's what I've done so far:
downgraded to 8.0.0.192 from HiSuite
downgraded to 8.0.0.140 following this
unlocked bootloader using HCU client (attached photo of phone in fastboot mode).
So now all I need to do is follow these steps?
Just double-checking before I do any damage to the phone
ImFrengo said:
So now all I need to do is follow these steps?
Click to expand...
Click to collapse
Yes, or these steps: Chapter 2.
"Chapter 2." is maybe simpler...
(I recommend reading the whole post!).
First flash oeminfo in TWRP, then continue with Chapter 2. !
These steps seem quite clear:
- In fastboot install TWRP, run
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot .
- Boot into TWRP and flash it over eRecovery :
-- select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe. Go back, find RECOVERY_RAMDISK-ANE-OREO file , mark Recovery, swipe. Reboot system, when yellow warning appears press and hold Volume Up.
- In TWRP select Install image and flash oeminfo.img file (mark oeminfo, swipe). Go back to main TWRP's menu, select Reboot > Power Off.
- Flash Service ROM using three buttons combo.
THE PROCESS WILL LOCK THE BOOTLOADER AGAIN!
Only thing is, what do you mean by "Flash Service ROM using three buttons combo."?
----
Edit: I guess it's standard dload method?
Also, should I add the ".img" at the end of the oeminfo file?
ImFrengo said:
Only thing is, what do you mean by "Flash Service ROM using three buttons combo."?
----
Edit: I guess it's standard dload method?
Click to expand...
Click to collapse
Power + both volume; standard.
ImFrengo said:
Also, should I add the ".img" at the end of the oeminfo file?
Click to expand...
Click to collapse
Yes.
Followed all the steps, bootloop after trying to install service rom
Is there a way to just take it back to the original state?
-Alf- said:
Power + both volume; standard.
Yes.
Click to expand...
Click to collapse
Either restoring the original or fixing the C432, either one is fine.. I'm still able to access TWRP, I don't know if that's useful
ImFrengo said:
Followed all the steps, bootloop after trying to install service rom
Click to expand...
Click to collapse
Your bootloader is locke or unlocked ? In fastboot run command
fastboot oem get-build-number
fastboot getvar vendorcountry
and post results.
ImFrengo said:
Is there a way to just take it back to the original state?
Click to expand...
Click to collapse
Only using the same procedure - oeminfo for C636 and service ROM 8.0.0.xxx C636 etc.
-Alf- said:
Your bootloader is locke or unlocked ? In fastboot run command
fastboot oem get-build-number
fastboot getvar vendorcountry
and post results.
Click to expand...
Click to collapse
C:\platform-tools>fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0CXB)
OKAY [ 0.006s]
Finished. Total time: 0.008s
C:\platform-tools>fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.005s
Fastboot screen on the phone shows "phone locked"
I flashed OxygenOS 12 Open Beta 1 and updated to 2 when it released. I'm desperate for a custom ROM so I tried going to fastboot mode. Instantly going back to OxygenOS.
I tried the rollback package but it wouldnt work. I tried mtkclient on Windows 11. Detecting but taking too much to connect. It says waiting for some VCOM thing.
ok, as long as I can understand tou should try to go on fastboot by using the tool with cmd (I don't know if it has compatibility issues with windows11).
other than that in a week the phone will arrive at my place and the first thing I will do is unlock bootloader and probably flash AncientOS because of OOS12's lack of problems.
Nezus3301 said:
ok, as long as I can understand tou should try to go on fastboot by using the tool with cmd (I don't know if it has compatibility issues with windows11).
other than that in a week the phone will arrive at my place and the first thing I will do is unlock bootloader and probably flash AncientOS because of OOS12's lack of problems.
Click to expand...
Click to collapse
The problem is that if I do 'adb reboot sideload' it gives me a fastboot_unlock_check fail or somethingand then reboots
mrcxlinux said:
The problem is that if I do 'adb reboot sideload' it gives me a fastboot_unlock_check fail or somethingand then reboots
Click to expand...
Click to collapse
adb sideload isn't that reccomended if you have to flash stock, you should do 'adb reboot fastboot' or 'adb reboot bootloader' and then follow this thread to flash the version you prefer:
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
I'm suspecting Windows 11 is interfering with UsbDK? It didnt exist when the last usbdk update released
Nezus3301 said:
adb sideload isn't that reccomended if you have to flash stock, you should do 'adb reboot fastboot' or 'adb reboot bootloader' and then follow this thread to flash the version you prefer:
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
Click to expand...
Click to collapse
Let me try it
mrcxlinux said:
I'm suspecting Windows 11 is interfering with UsbDK? It didnt exist when the last usbdk update released
Click to expand...
Click to collapse
maybe it could be the problem, windows 11 is the best os for unsupporting every driver exixting in the internet
Nezus3301 said:
adb sideload isn't that reccomended if you have to flash stock, you should do 'adb reboot fastboot' or 'adb reboot bootloader' and then follow this thread to flash the version you prefer:
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
Click to expand...
Click to collapse
I meant 'bootloader'. it gives me a fastboot_unlock_check fail or something and then reboots
mrcxlinux said:
I meant 'bootloader'. it gives me a fastboot_unlock_check fail or something and then reboots
Click to expand...
Click to collapse
when you flashed oos, did you unlocked again bootloader? I know it's a common thing when you flash stock roms you should unlock again bootloader
Nezus3301 said:
maybe it could be the problem, windows 11 is the best os for unsupporting every driver exixting in the internet
Click to expand...
Click to collapse
I think I cant get to fastboot because of.. oppo? They are really anti-bootloader unlock
Nezus3301 said:
when you flashed oos, did you unlocked again bootloader? I know it's a common thing when you flash stock roms you should unlock again bootloader
Click to expand...
Click to collapse
"flashed". Just did 'install update' from recovery.
mrcxlinux said:
I think I cant get to fastboot because of.. oppo? They are really anti-bootloader unlock
Click to expand...
Click to collapse
but it's strange, if you unlocked already the bootloader, "oppo's roms" shouldn't block you to flash anything else, the bootloader relock could be a thing (you should tell me if when you reboot your phone it gives you a 3/5 seconds splash that tells you the bootloader is unlocked) if not you should try to do again the same steps you did to unlock bootloader as ex novo
Nezus3301 said:
but it's strange, if you unlocked already the bootloader, "oppo's roms" shouldn't block you to flash anything else, the bootloader relock could be a thing (you should tell me if when you reboot your phone it gives you a 3/5 seconds splash that tells you the bootloader is unlocked) if not you should try to do again the same steps you did to unlock bootloader as ex novo
Click to expand...
Click to collapse
I didnt unlock it.
last thing I can tell you is to try to follow this
sorry mate but I can't help you as much as i would
mrcxlinux said:
The problem is that if I do 'adb reboot sideload' it gives me a fastboot_unlock_check fail or somethingand then reboots
Click to expand...
Click to collapse
I'm having the same issue this is really messed up I was gonna keep this device but this makes it hard to want to keep it is a freaking what else do you get a OnePlus for but to try costum roms smh..
Nezus3301 said:
ok, as long as I can understand tou should try to go on fastboot by using the tool with cmd (I don't know if it has compatibility issues with windows11).
other than that in a week the phone will arrive at my place and the first thing I will do is unlock bootloader and probably flash AncientOS because of OOS12's lack of problems.
Click to expand...
Click to collapse
You don't know fastbootmode is broken on oos 12 so you can't go back to oos 11
Till OnePlus gives us downgrade package or update with fastbootmode fixed.
So stop l discussions about that has no clue
pankspoo said:
You don't know fastbootmode is broken on oos 12 so you can't go back to oos 11
Till OnePlus gives us downgrade package or update with fastbootmode fixed.
So stop l discussions about that has no clue
Click to expand...
Click to collapse
Honestly, the OS is good but the way it is created and managed is just.. unspeakable.
pankspoo said:
You don't know fastbootmode is broken on oos 12 so you can't go back to oos 11
Till OnePlus gives us downgrade package or update with fastbootmode fixed.
So stop l discussions about that has no clue
Click to expand...
Click to collapse
There might still be hope! MTKClient Live DVD with:
recovery.img
seccfg.img
boot.img
vbmeta.img
Here's a question for ya. Why the **** did you install the INDIAN ONLY beta on your EU device? It clearly tells you that you'll **** up your phone if you do it and won't be able to roll back. And here you are complaining that you can't roll back. You should have waited for the EU beta or stable which ISN'T AVAILABLE YET.
xphyle1971 said:
Here's a question for ya. Why the **** did you install the INDIAN ONLY beta on your EU device? It clearly tells you that you'll **** up your phone if you do it and won't be able to roll back. And here you are complaining that you can't roll back. You should have waited for the EU beta or stable which ISN'T AVAILABLE YET.
Click to expand...
Click to collapse
What do you have to be rude for? Android 11 wasn't working good for me and I thought it will work better. + that fastboot is disabled for everyone and if I manage to go back then I can share everything because I'm not the only one.