just got C61 (via ota) and I am getting frustrating for custom roms for OP9Pro, so, i'd like to relock OEM, but...
once I run "fastboot flashing lock", it run into boot loop
back on bootload, "fastboot flashing unlock" system restarts
(i need unlock to flash c47 on 2.1010 via twrp)
i also tried "fastboot erase userdata" but this is undefined nowadays
what I am doind wrong?
thank you for helping
MSM relocks the bootloader
Psk.It said:
just got C61 (via ota) and I am getting frustrating for custom roms for OP9Pro, so, i'd like to relock OEM, but...
once I run "fastboot flashing lock", it run into boot loop
back on bootload, "fastboot flashing unlock" system restarts
(i need unlock to flash c47 on 2.1010 via twrp)
i also tried "fastboot erase userdata" but this is undefined nowadays
what I am doind wrong?
thank you for helping
Click to expand...
Click to collapse
Just flash the stock rom once, then factory reset the device and then fastboot OEM lock
Funk Wizard said:
Just flash the stock rom once, then factory reset the device and then fastboot OEM lock
Click to expand...
Click to collapse
It's what i did
but It goes into bootloop
habobababo said:
MSM relocks the bootloader
Click to expand...
Click to collapse
Yes, but, It comes with 2.2.2
first ota bring 2.10.10
second ota c47 does not apply installed from local, i need twrp ti flash It
and once flashed c47
It runs into bootloop if trying lock on c47 and also once update to c61 (fresh install and/or fresh formatted) It goes always in bootloop
Psk.It said:
It's what i did
but It goes into bootloop
Click to expand...
Click to collapse
The system has to be in stock condition for you to be able to lock it. Flash the stock from, no root no mods no nothing, restart > let the stock recovery overwrite twrp > reboot to stock recovery > factory reset once for the device to return to stock condition and then do fastboot OEM lock from fastboot. That should work.
Funk Wizard said:
The system has to be in stock condition for you to be able to lock it. Flash the stock from, no root no mods no nothing, restart > let the stock recovery overwrite twrp > reboot to stock recovery > factory reset once for the device to return to stock condition and then do fastboot OEM lock from fastboot. That should work.
Click to expand...
Click to collapse
It does not
I just EDL once again
I tried copying E13 (2.10.10) full ota, then trying update to C47 failed (from local update and re-downloading it, nothing to do)
EDL once more, thinking the problem could be related to E13 update i let update to run via ota, but once more updating to C47 failed
I had to unlock the bootloadet to move from 11.10.10 to C47
so via twrp I siloaded C47 on both slots
trying to "oem lock" with a fresh setup
on locking process i got the messagge "the corrent image boot/recovery has been destroied"
so, how to?
Psk.It said:
I just EDL once again
I tried copying E13 (2.10.10) full ota, then trying update to C47 failed (from local update and re-downloading it, nothing to do)
EDL once more, thinking the problem could be related to E13 update i let update to run via ota, but once more updating to C47 failed
I had to unlock the bootloadet to move from 11.10.10 to C47
so via twrp I siloaded C47 on both slots
trying to "oem lock" with a fresh setup
on locking process i got the messagge "the corrent image boot/recovery has been destroied"
so, how to?
Click to expand...
Click to collapse
Msm and then try oxygen updater from the playstore.when on oos 12 if you google search there is an apk updater app that allows you to upgrade on oos 12 locally.
gillim74 said:
Msm and then try oxygen updater from the playstore.when on oos 12 if you google search there is an apk updater app that allows you to upgrade on oos 12 locally.
Click to expand...
Click to collapse
OK, may be next time
but, with MSN it goes to 11.2.2, updating to 11.10.10 from full rom or incremental runs well
the problem is going from 11 to 12 , no kind of update works keeping loked bootloader, so i will noto ne abile to reach A12
Related
Hi,
I have the Find 7 with the new display panel.
I wanted to flash the latest version of TWRP but failed. I do not know what I did wrong.
I can use adb and fastboot without any problem. When trying to flash recovery, it says there that the flash was successful but when I reboot to recovery, TWRP was not installed and the original Oppo recovery is still there.
The bootloader is unlocked. And I tried relocking and unlocking again but to no avail. Whenever I use the command "fastboot oem unlock", nothing happens to the phone.
I am currently on spectrum. I want to try other roms such as the lite COS 2.15 and also maxwen roms since that only those supports the new panel.
I am also trying to get root for my phone and it is impossible without custom recovery.
Thanks for any help.
I had poop loads of issues with getting custom recovery on my Find 7a. Eventually I used these instructions:
http://community.oppo.com/my/forum.php?mod=viewthread&tid=996
They work. Don't know if it's the versions of ADB or Fastboot or something.
Give it a go
limbot said:
I had poop loads of issues with getting custom recovery on my Find 7a. Eventually I used these instructions:
http://community.oppo.com/my/forum.php?mod=viewthread&tid=996
They work. Don't know if it's the versions of ADB or Fastboot or something.
Give it a go
Click to expand...
Click to collapse
I will give it a go when I get back. Thanks!
This is what a forumer from the official forum said and it works:
After you had successfully flash recovery via fastboot, you MUST NOT reboot the device. AFAIK, if you reboot the device it will restore the recovery back to stock oppo recovery.
So instead, you need to immediately press vol down & power button on the fastboot screen. Keep holding the button until you see the TWRP recovery screen. Hope that helps. Cheers!""
faidz85 said:
Hi,
I have the Find 7 with the new display panel.
I wanted to flash the latest version of TWRP but failed. I do not know what I did wrong.
I can use adb and fastboot without any problem. When trying to flash recovery, it says there that the flash was successful but when I reboot to recovery, TWRP was not installed and the original Oppo recovery is still there.
The bootloader is unlocked. And I tried relocking and unlocking again but to no avail. Whenever I use the command "fastboot oem unlock", nothing happens to the phone.
I am currently on spectrum. I want to try other roms such as the lite COS 2.15 and also maxwen roms since that only those supports the new panel.
I am also trying to get root for my phone and it is impossible without custom recovery.
Thanks for any help.
Click to expand...
Click to collapse
Can u teach me how to unlock bootloader.. because when I flash twrp recovery img my fon stuck at fastboot menu, cannot enter the recovery menu.
Some say I get this problem becos I not unlock my bootloader..
Im trying to flash miui os..huhuhu
cikgutan said:
Can u teach me how to unlock bootloader.. because when I flash twrp recovery img my fon stuck at fastboot menu, cannot enter the recovery menu.
Some say I get this problem becos I not unlock my bootloader..
Im trying to flash miui os..huhuhu
Click to expand...
Click to collapse
fastboot oem unlock in bootloader mode.
azeem40 said:
fastboot oem unlock in bootloader mode.
Click to expand...
Click to collapse
Unlocking bootloader erases data?
Mine wouldn't flash recovery. It said successful but I still had oppo recovery 1.2 and it only worked when I found the latest official twrp over version 3. after flashing, I disconnected usb and then held down power button to shut the phone down. It then was able to boot to twrp ok.
I used the latest one.
https://dl.twrp.me/find7/
Hi.
- I flashed TWRP using ADP, flashed root to change fonts but used Stock OOS 3.2.4
Now i sold device.=, to buy black one or iPhone
- I done data reset in TWRP to unroot, after reboot SU App was gone.
- I flashed stock recovery via ADB
- I left the bootloader unlocked, i was not sure of comand, plus in case of mess up, i could fix it.
New user has no idea as well, he says now when he installs OTA 3.2.6 it fails to install.
What i am missing? how can i fix this?
Help will be much appreciated, thanks in advance.
EDIT: SOLVED
When i locked bootloader, it took me to bootloap, and when i try to sideload new OOS3.2.4 it gave ever, cannot read file.
- I flashed new official TWRP again.
- I flashed stock 3.2.4 with TWRP
- Set up OS
- Flashed stock recovery, in fastboot by doing USB debugging on
- Locked bootloader by "fastboot bootloader oem lock" right after stock recovery
- Set up OS 3.2.4 again, at this moment 3.2.6 fail to down over the air
- I downloaded stock 3.2.6 incremental update, successfully downloaded and install.
Now phone seem to be at stock. I bought it back from to save him from inconvenience, as he was scared as the phone was failing to install update initially.
Also interested on this, same thing happened with me and a friend, modded his phone, he didnt want it modded anymore, flashed a clean stock OOS, flashed stock recovery, and error on install of 3.2.6 OTA, if anyone have any idea how to recover the ability to OTA, appreciated.
What happens if you try to sideload it
https://forums.oneplus.net/threads/...root-non-root-users-without-data-loss.451853/
khaos64 said:
What happens if you try to sideload it
https://forums.oneplus.net/threads/...root-non-root-users-without-data-loss.451853/
Click to expand...
Click to collapse
When i sideload oos.zip which is 3.2.4, it says cannot read zip.
When i relock bootlaoder, it goes into bootloap, i go back to fastboot and unlock bootloader, it boots back into old stock OOS 3.2.4. This rom still has my changed fonts, which i had when i had root and TWRP.
I know there was a firmware change with 3.2.6, so if you flashed the 3.2.6 recovery with OOs 3.2.4, this could possibly be your issue.
Boot into Twrp, don't need to flash it. Clean flash 3.2.6, reboot. Try relocking bootloader see if you still get boot loops.
So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
DrUnknownEMC said:
So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
Click to expand...
Click to collapse
You need to have usb debugging enabled in your phone and adb tools installed in your pc before you do this.
For locking bootloader :
Connect the phone to computer,
Restart the phone in bootloader mode
Open command prompt window
Check connection by typing fastboot devices . You should see your device listed
Type fastboot oem lock
Reboot once the process completes. Be aware this will wipe your phone and ALL data will be lost.
It is advisable to keep boot loader unlocked.
For stock recovery :
Download stock recovery image from the forum
Save it in the same folder where your adb is installed in windows. The file name should be recovery.img
Reboot into bootloader mode
Open command prompt and
Type fastboot flash recovery recovery.img
Stock recovery to be installed before you lock bootloader
DrUnknownEMC said:
So I brought oneplus 3t for my father from china so it running hydrogen OS but now we moved back to Australia it would more sensible to change to google services for apps download and updates so i flashed Oxygen OS something stable but I was wondering how should re lock boot loader and maybe flash to stock recovery (Optional) to have boot up message and maybe encryption enabled.
Click to expand...
Click to collapse
a cautionary warning regarding the above reply to you, don't' relock the bootloader while you're on a custom recovery and/or kernel, and also while you have changes to the system (installed any mods or deleted any files form system folder)
so in theory it's possible,
1- you need to sideload a full stock rom (download from oneplus website) it's better to be stable not beta (you should have adb drivers installed and stock recovery, sideload will insure you have stock everything)
2- after you successfully sideloaded a full stock rom and make a full boot to system, you can follow the above re-lock instructions.
theduke7 said:
a cautionary warning regarding the above reply to you, don't' relock the bootloader while you're on a custom recovery and/or kernel, and also while you have changes to the system (installed any mods or deleted any files form system folder)
so in theory it's possible,
1- you need to sideload a full stock rom (download from oneplus website) it's better to be stable not beta (you should have adb drivers installed and stock recovery, sideload will insure you have stock everything)
2- after you successfully sideloaded a full stock rom and make a full boot to system, you can follow the above re-lock instructions.
Click to expand...
Click to collapse
Currently it running oxygen OS from their website like full rom.zip, i know when you flash new recovery you will factory wipe the phone which i don't really wants. Are they like patch to remove boot up warning? because last time i check there wasn't one.
DrUnknownEMC said:
Currently it running oxygen OS from their website like full rom.zip, i know when you flash new recovery you will factory wipe the phone which i don't really wants. Are they like patch to remove boot up warning? because last time i check there wasn't one.
Click to expand...
Click to collapse
A new recovery does not wipe your phone.
There is no patch to remove the boot warning. The only way is to lock boot loader <- this will wipe your phone and data.
If your phone runs well, it is better you keep it as it is. Why fix something that's not broken ?
After trying to install a custom ROM (PixelExperience for OnePlus 7T [hotdogb]) via fastboot, the installation flashing ended with errors with "no such partition" for odm, product and system I tried everything to get out of the fastboot screen loop. After finding a bat file with IMG files which got me on the Android 11 Beta 1. build (still no WiFi)
What can I do to fix the partition error to get on the Pixel Experience ROM or even get back to the stable build - I did try MSM but it isn't listing the phone even after pressing ENUM.
Please help...
Context (can skip): The latest stable build OOS for my 7T had issues with the microphone not working and so I decided to do a factory reset which resulted in having a clean install but now, WiFi doesn't connect for some reason. After trying some fixes I decided to install a custom ROM.
U need to flash stock recovery (fastboot flash recovery recovery.img) as twrp prevents fastbootD entry. Then type fastboot reboot fastboot to enter fastbootD. Then flash your rom. Personally, I just flash roms via Chinese twrp or 3.5.10 twrp
HueyT said:
U need to flash stock recovery (fastboot flash recovery recovery.img) as twrp prevents fastbootD entry. Then type fastboot reboot fastboot to enter fastbootD. Then flash your rom. Personally, I just flash roms via Chinese twrp or 3.5.10 twrp
Click to expand...
Click to collapse
that was my process for the first try - entered fastbootD for the flashing process which ended with the mentioned partition error and the fastboot loop. I realised that TWRP version I got from TOOL ALL IN ONE wasn't going to work as it couldn't access data no matter what.
No twrp can decrypt oos or a11 custom roms data. Chinese twrp can access data only on a10 custom roms if u remove screen lock before booting into twrp for backup
What do you reckon I try this time then?
itssata said:
What do you reckon I try this time then?
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
So I wanted to switch from OOS 11 to 13.
I was unl;ocked, rooted with magisk installed.
Updated to c47 and flashed magisk. all good.
Then flashed TWRP and tried flashing the full OOS c64 I downloaded.
The flashing failed and now I have no OS since I wiped before flashing as recommended.
At the past with previous devices I just flashed TWRP, flashed the ROM, reflashed TWRP and was done with it.
How can I recover my phone now? All of the data is backed up (contacts, apps, photos) so it's not a big deal if I lose all my data.
Currently I'm at TWRP
PLEASE HELP ME
Also when trying to activate sideload, TWRP is stuck on 'starting ADB sideload feature' and nothing happens, adb devices command doesn't recognize the phone and I have a red warning 'unable to decrypt FBE device'
Just use MSM TOOL and never unlock bootloader.
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Not sure but I think the problem was installing twrp, as far as I know it does not support installation, just start without installing like, (Fastboot boot twrp.img)
Why didn't you follow all the updates without inventing fashion?
Just download the complete package of the update and does the manual update, does not restart the phone, go in magisk, click install and mark the third option, which is to install after full Ota.
N1ldo said:
Not sure but I think the problem was installing twrp, as far as I know it does not support installation, just start without installing like, (Fastboot boot twrp.img)
Why didn't you follow all the updates without inventing fashion?
Just download the complete package of the update and does the manual update, does not restart the phone, go in magisk, click install and mark the third option, which is to install after full Ota.
Click to expand...
Click to collapse
I don't think TWRP even support flashing OOS.
@N1ldo cause I wanted Android 13 and the OTA failed to update from C47 to C61.
Also I thought that my past experience with flashing the Oneplus 6 will still be relevant, which obviously isn't apparently...
Gonna try to follow the MSM guide.
But for the future, assuming I will succeed in restoring via MSM, what should I do in order to gain root?
1. MSM
2. re-unlock the bootloaded
3. Flash magisk via fastboot
That's it? did I get this right?
Alonzzo2 said:
@N1ldo cause I wanted Android 13 and the OTA failed to update from C47 to C61.
Also I thought that my past experience with flashing the Oneplus 6 will still be relevant, which obviously isn't apparently...
Gonna try to follow the MSM guide.
But for the future, assuming I will succeed in restoring via MSM, what should I do in order to gain root?
1. MSM
2. re-unlock the bootloaded
3. Flash magisk via fastboot
That's it? did I get this right?
Click to expand...
Click to collapse
nope, you boot twrp-3.7.0-12.1 via fastboot (fastboot boot twrp.img) and there you can install magisk. if normal installation doesn't work, try using sideload. if you plan on flashing the twrp installer zip, do it before flashing magisk as it patches your current boot image.
Guest902379028 said:
I don't think TWRP even support flashing OOS.
Click to expand...
Click to collapse
worked fine for me
DirtryElectroOP3 said:
nope, you boot twrp-3.7.0-12.1 via fastboot (fastboot boot twrp.img) and there you can install magisk. if normal installation doesn't work, try using sideload. if you plan on flashing the twrp installer zip, do it before flashing magisk as it patches your current boot image.
Click to expand...
Click to collapse
great. and I can do it regardless of the oos I'm running right? I wouldn't ask that question under normal circumstances but after today, better safe than sorry
Alonzzo2 said:
great. and I can do it regardless of the oos I'm running right? I wouldn't ask that question under normal circumstances but after today, better safe than sorry
Click to expand...
Click to collapse
should work as I described. if you want to be 101% safe, just boot the twrp, but if I remember correctly, the installer should work on oos 13. if you want, you can extract the payload.bin of your current oos so you have the stock boot.img and vendor_boot.img in case anything goes wrong. you can find the exact description here.
Thanks, And one last question, if I'll unlock the bootloader now that I've installed all of the updates up to android 13, it will erase all the data but not the updates, right?
Alonzzo2 said:
Thanks, And one last question, if I'll unlock the bootloader now that I've installed all of the updates up to android 13, it will erase all the data but not the updates, right?
Click to expand...
Click to collapse
Never mind, it works, after the updates I unlocked the bootloader, patched the boot image, booted from it and installed magisk. I now have root.
Thanks all for helping me out!