Related
Download the latest FW files from from http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8/
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
krystyuc said:
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
Click to expand...
Click to collapse
I'm coming from Motorola/Lenovo and I cannot imagine that it is so simple to unlock and relock the bootloader. When you unlock the bootloader on Moto phones you void your warranty. I am so scared from my experience with Motorola that I haven't tried it yet for my OP5.
Can someone please give me some reassurance?
lollyjay said:
I'm coming from Motorola/Lenovo and I cannot imagine that it is so simple to unlock and relock the bootloader. When you unlock the bootloader on Moto phones you void your warranty. I am so scared from my experience with Motorola that I haven't tried it yet for my OP5.
Can someone please give me some reassurance?
Click to expand...
Click to collapse
Yes it's that easy. Done it a few times.
lollyjay said:
I'm coming from Motorola/Lenovo and I cannot imagine that it is so simple to unlock and relock the bootloader. When you unlock the bootloader on Moto phones you void your warranty. I am so scared from my experience with Motorola that I haven't tried it yet for my OP5.
Can someone please give me some reassurance?
Click to expand...
Click to collapse
I can relate to that. I have personally owned two Moto E devices along with the OnePlus One and OnePlus 5, and I can assure that it's way too easy with the latter. I have had really bad experience with Moto, be it updates, unlocking, or downgrading. OnePlus is like a second-Nexus to me, when it comes to such stuff. :good:
deathst said:
Download the latest FW files from from http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8/
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
Click to expand...
Click to collapse
Thanks for sharing mate.
I`ve alredy rooted with SuperSu and TWRP installed. How do I flash Magisk over SuperSu ?
And I`ve tried to flash latest FW (OOS 4.5.10 Full Zip) with TWRP, but whenever I try to reboot it always says " No OS Installed .......".
I`ve tried several times, but every time it remains the same.
I totally new to OP devices. It would be very helpful, if you share how to revert back to stock OOS and lock the bootloader.
deathst said:
Download the latest FW files from from http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8/
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
Click to expand...
Click to collapse
It will be good if you can't post exact commands needed to flash stock recovery, relook, etc.
here in this video u can see in detail how to lock bootloader. hope this help
https://www.youtube.com/watch?v=CQYCSdDUdAU
adb sideload fails
deathst said:
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled" in developer settings (THIS IS IMPORTANT)
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock command
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
Click to expand...
Click to collapse
I have followed the instructions but the adb sideload command fails.
The process stops about 40% and the phone screen shows "failed".
Is there somebody have any guess about why it happens?
Hi!
I see the large number of requests concerning the roolback of a custom rom to a official and untouched EMUI 4, i decide to create this thread.
After follow that methode, you able to rest on official EMUI and get the new update automatically on OTA (directly on your phone) OR try to install custom rom with a clear and good base version.
1. You ave access on TWRP?
-If not, pleas unlock your bootloader (again) and flash TWRP recovery for you actual version (marshmallow or nougat).
-perform a full wipe and restore your partitions on "ext4" format, shutdown phone.
2. Get a "oem_info.zip" for your model phone (dont extract the .zip) and push it on your internal or external sd.
-This archive contain cust and oem info for patched your phone at the correct manufacture information.
-I have a link for VNS-L31 (c432, but is not very important) HERE LINK
-If you have other model (VNS-L31) pleas find a correct patch for you (VNS-L21, ...).
3. Find and download a EMUI marshmallow official full-ota update.
-for a VNS-L31 i advice choice a VNS-L31C432B160 full-ota update.
4. Unpack your update archive.
5. Create "dload" folder on your internal or external sd and put it UPDATE.APP
6. Reboot phone on TWRP recovery and flash "oem_info.zip"
7. Use dload methode for update (hold 3 buttons phone and dont release before "dload screen" appears)
8. Unlock your bootloader again (important!) And make a factory reset
9. Your phone reboot (please wait ) and done!
Ok now you are on official version, please update on setting menu >> update and choice, rest on official or flash a custom rom..
P9 lite brick precision:
In my personal experience the "p9 lite" is very easy to flash, mod or other tips and the risk of HARD brick is very very tiny.
If you see this page and your phone bootloop, relax, keep calm at 99,999% you have a little and ridiculous brick
Good luck and flash happy!
hi! i'm on 381, on my phone i have root, twrp and elite kernel...this guide is good for me???why after dload method i have to re-unlock my bootloader??
thank you and sorry for my english XD
macao1989 said:
hi! i'm on 381, on my phone i have root, twrp and elite kernel...this guide is good for me???why after dload method i have to re-unlock my bootloader??
thank you and sorry for my english XD
Click to expand...
Click to collapse
Yes, is good for you.
Not necessary to re-unlock bootloader.
Therand said:
Hi!
I see the large number of requests concerning the roolback of a custom rom to a official and untouched EMUI 4, i decide to create this thread.
After follow that methode, you able to rest on official EMUI and get the new update automatically on OTA (directly on your phone) OR try to install custom rom with a clear and good base version.
1. You ave access on TWRP?
-If not, pleas unlock your bootloader (again) and flash TWRP recovery for you actual version (marshmallow or nougat).
-perform a full wipe and restore your partitions on "ext4" format, shutdown phone.
2. Get a "oem_info.zip" for your model phone (dont extract the .zip) and push it on your internal or external sd.
-This archive contain cust and oem info for patched your phone at the correct manufacture information.
-I have a link for VNS-L31 (c432, but is not very important) HERE LINK
-If you have other model (VNS-L31) pleas find a correct patch for you (VNS-L21, ...).
3. Find and download a EMUI marshmallow official full-ota update.
-for a VNS-L31 i advice choice a VNS-L31C432B160 full-ota update.
4. Unpack your update archive.
5. Create "dload" folder on your internal or external sd and put it UPDATE.APP
6. Reboot phone on TWRP recovery and flash "oem_info.zip"
Click to expand...
Click to collapse
I can do everything up to point 6... won't enter to twrp... stays on Your device is now booting...
Update: I can now reach point 7 but now won't do dload (3 buttons) method... Huawei logo all the time. Can't even turn off the phone
In my other thread you post the same problem but is not entirely the same..
You succeeded to enter on fastboot mode? Flash recovery?
If you follow the steps 1-5 is impossible to fail the 6 point..
You have acces on fastboot mode or not?..
Therand said:
In my other thread you post the same problem but is not entirely the same..
You succeeded to enter on fastboot mode? Flash recovery?
If you follow the steps 1-5 is impossible to fail the 6 point..
You have acces on fastboot mode or not?..
Click to expand...
Click to collapse
I did update the post... 3 hours ago I wasn't able to enter TWRP, some way I did managed, now I can enter fastboot, I did flash custOEM (sorry I don't remember exactly the name but it's the one of your post) .zip file. Now I can't do dload method, stuck on huawei logo. If I try to go to recovery, I got red message "phone fail validation"...
I know, I post on both but I was trying to do everything...
just tried... validation red error message won't let me go to TWRP now...
You have a VNS-L31C432?
Your phone does not enter at dload mode?
Wipe all partitions an retry flash a oeminfo for your model phone (if not C432 you need right oeminfo).
Therand said:
You have a VNS-L31C432?
Your phone does not enter at dload mode?
Wipe all partitions an retry flash a oeminfo for your model phone (if not C432 you need right oeminfo).
Click to expand...
Click to collapse
How can I wipe all partitions if stuck in Huawei logo? Is there a way to do everything from adb command line? (I'm using Mac and cannot use all the tools I've found here XDA neither hiSuite which is basically a backup photo/video only the Mac version).
Thank for helping, really appreciate
To answer your question in the other thread, yes bootloader is unlocked and I am on C432.
What's your rom have before the bootloop?
You have the right version of TWRP for your rom?
If you have a MM version Don't flash a TWRP for N.
Send me a link to TWRP version used (thread forum)
Therand said:
What's your rom have before the bootloop?
You have the right version of TWRP for your rom?
If you have a MM version Don't flash a TWRP for N.
Send me a link to TWRP version used (thread forum)
Click to expand...
Click to collapse
Before the bootloop I was on L31C900 (on the phone) but I did actually flashed C432B160 because I did rollback. TWRP used I've found in the other post where there's a OEMfile to flash (but for this I need to double check because I did look so many pages which I am not 100% sure.
I not have experience on other model that C435.
But i suggest to find a oeminfo for your variant (C900?)
For TWRP you need flash a version for MarshMallow HERE
Flash it and pas return here (fastboot flash return and first enter to new recovery)
Hi, found Windows emulator for MacOs so I extract from update.app boot.img and flash.
I did format all partitions as told using a proper twrp this time.
What's next step, system says NO OS INSTALLED?
islandman75 said:
Hi, found Windows emulator for MacOs so I extract from update.app boot.img and flash.
I did format all partitions as told using a proper twrp this time.
What's next step, system says NO OS INSTALLED?
Click to expand...
Click to collapse
Flash partitions on .img files is not needed.
Just find a corect oeminfo for your model phone.
Flash it on TWRP recovery.
Use dload methode to update on basical version (MarshMallow b160).
After that, unlock bootloader again and make a factory reset.
Switch on your phone (the first boot make long time).
Update on last emui on OTA.
Done!
After that you able to install a custom rom.
Therand said:
Flash partitions on .img files is not needed.
Just find a corect oeminfo for your model phone.
Flash it on TWRP recovery.
Use dload methode to update on basical version (MarshMallow b160).
After that, unlock bootloader again and make a factory reset.
Switch on your phone (the first boot make long time).
Update on last emui on OTA.
Done!
After that you able to install a custom rom.
Click to expand...
Click to collapse
Done!
Thanks again you're saving my life!
IT won't turn off so been always on it won't keep the charge... Writing so because apparently it won't go to download mode (dload) if plugged in. On the other way if I unplugged from power it won't even start. Shall I force to download mode using console ADB or FASTBOOT? I had looked but can't find anything...
islandman75 said:
Done!
Thanks again you're saving my life!
IT won't turn off so been always on it won't keep the charge... Writing so because apparently it won't go to download mode (dload) if plugged in. On the other way if I unplugged from power it won't even start. Shall I force to download mode using console ADB or FASTBOOT? I had looked but can't find anything...
Click to expand...
Click to collapse
I not understand.
You not able to switch on your phone without connected charger?
Therand said:
I not understand.
You not able to switch on your phone without connected charger?
Click to expand...
Click to collapse
Correct. Because I'm not able to switch it off it won't keep the charge. When discharged, the minute I do plug on charge it wakes up... That's the loop...
My main question is: does a command exist to enter download mode using terminal?
islandman75 said:
Correct. Because I'm not able to switch it off it won't keep the charge. When discharged, the minute I do plug on charge it wakes up... That's the loop...
My main question is: does a command exist to enter download mode using terminal?
Click to expand...
Click to collapse
You have a hardware bug?
No abd command to enter dload mode..
Try flash a update.zip with twrp (not guaranted)
After that unlock bootloader again and make factory reset.
Therand said:
You have a hardware bug?
No abd command to enter dload mode..
Try flash a update.zip with twrp (not guaranted)
After that unlock bootloader again and make factory reset.
Click to expand...
Click to collapse
I'll try. Thank you
Hi, I followed this guide to go back to stock from elite rom. I flashed my oeminfo.img on twrp and then went to dload combination. Do I have to unlock the bootloader after the reboot? Thanks!
Hi,
I followed your guide and it works perfectly thanks!
This Guide Can Also Be Used For Unlocking & Relocking Bootloader, Installing TWRP & Rooting
If Any Ota Messes With The Implementation Then Whole Procedure Needs To Be Redone
To mitigate the problem requesting developers for making a hack for Relocking Bootloader Without Wiping Data PM me if Interested
Data Will Be Wiped So Make Backup First
What Will We Be Doing: Unlocking Bootloader, Installing TWRP,Flashing Camera2api Enabler, Installing Back Stock Recovery, Relocking Bootloader
Procedure:
1. Download this rar and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows
2. Install the drivers according to your OS (happens Automatically In Most Cases) and open the unlock folder
3. Reboot your phone to fastboot mode by pressing volume up + power on at the same time.
4. Connect it to pc and open unlock.bat in unlock folder
5. Long Press Power Button & Reboot. A wiping Data screen will appear followed by an encrypting sceen then the phone will reboot (A warning of unlocked bootloader will show up initially)& then the initial setup screen will show up don't add any thing & skip the setup(there will be another wipe).
6. Download Cam2Api & copy it to sd card or internal storage of phone. Then switch off the phone once again & reboot in fastboot mode once more.
7. Download TWRP from here & Install Minimal ADB to root of C drive.
8. Copy the twrp to the adb folder in your C drive.
9. Open the 'cmd-here.exe' the adb window will open
10. With the phone connected in fastboot mode type in adb "fastboot flash recovery twrpasus.img" & press enter then type "fastboot boot twrpasus.img" & hit enter.
11. Switch Off the phone & boot in twrp by pressing vol down+power, opening TWRP will take time
12. A decryption popup will open in twrp skip it.
13. Select Install Zip & slect the storage where you have kept the cam2api.zip & flash it, then select reboot system.
14. Download Gcam from here (Arnova v8 is best) & copy it to phone and install it, check if it works, dont configure it. Reboot your phone to fastboot mode
15. Download stock asus recovery from here & copy it to the adb folder.
16. Again open the adb & type "fastboot flash recovery recovery.img"
17. Download Zenfone_Max_M1_Pro_Relock.zip and extract it.
18. Open the directory where you extracted the file
19. In that directory, open a file named relock_bl.cmd
20. A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
21. It will then erase all the data on your phone once again (excluding Micro SD card).
23. Reboot
22. Now the phone won’t show the “bootloader unlocked” warning that was displayed after you unlocked the bootloader. Now setup the phone and install the Gcam downloaded earlier also all manual camera apps will work fine too.
Done! You Have Successfully Relocked Bootloader & Enabled Camera 2 api in stock rom. As the bootloader is locked & we have'nt rotted our phone you have your warranty and ota updates work well. If any kind of future ota breaks the camera2api then you have to redo the procedure once again.
Installing Magisk Or SuperSU while twrp is installed will root your phone (breaks ota updates though)
Credits to:
@Sudeep Duhoon : For Original Unofficial unlock & Camera2api Enabler script
@Shivam Kumar Jha For Unofficial TWRP
@style2345 For Providing ASUS Stock Recovery
@myapky For Relocking Script
Hit Thanks If This Helped You!
Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?
mehtasu said:
Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?
Click to expand...
Click to collapse
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)
AstroBiswas said:
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)
Click to expand...
Click to collapse
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?
mehtasu said:
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?
Click to expand...
Click to collapse
Swipe to allow modifications ofcourse how would we change anything without that permission
Thankyou, the guide works perfectly. Just to add when installing twrp, boot directly into recovery, otherwise twrp won't install. Just wanted to put it here so that people don't have to go through other threads.
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test May Security Patch arrived via ota & it installed fine, didnt break the api.
AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
The June Security Patch is arrived via OTA now?
Sent from my [device_name] using XDA-Developers Legacy app
The Wolf Dark said:
The June Security Patch is arrived via OTA now?
Click to expand...
Click to collapse
No actually my phone has just arrived I Did this procedure on the day itself
AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota
Aftab_khatri said:
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota
Click to expand...
Click to collapse
Oh my bad they provided may patch in june update.
We havent done any kind of detectable large system modification so ota's work
Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thankyou. I had to search for your thread to take care of some troubleshooting. Also, will surely have to follow the guide to go stock/relock to get furture OTA updates. Never the less a big thank you to you and the other developers for their contributions for this phone. Makes this divice so very worthwhile.
Well its working as mentioned by OP.......
Well done !!!
What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img
pranavsree00 said:
What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img
Click to expand...
Click to collapse
I had tried it. It didnt work
AstroBiswas said:
I had tried it. It didnt work
Click to expand...
Click to collapse
pranavsree00 said:
Click to expand...
Click to collapse
if you already have twrp installed then you just have to flash the cam2.zip thats all ...........
& if you don't have twrp then you have to first install twrp using the command by OP & then flash cam2.zip as mentioned it original thread .
Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...
Amal Prabhakaran said:
Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...
Click to expand...
Click to collapse
Well just follow the give procedure or steps one by one & relock the bootloader at last and you would be good to go .....
Well I didn't relocked the bootloader & I frequently change my ROMS & regarding updates well there is none after 309 so whenever there would be an update I will give it a try then but for now everything is working fine so you can give it a go .........
How to revert back to stock firmware
October 26, 2018
WARNING :do not try to downgrade your device.
For example, if you are on September security patch level (on stock firmware) and rooted your device or installed a custom ROM and if you want to revert back to stock firmware then flash the firmware which have September Or greater then September Security patch level.
As downgrading (flashing firmware of older versions or older security patches) can result in hard bricking of your device.
As in example, if you flash august security patch firmware your device may got bricked and believe me guys you don't want it!!).
If however you flashed downgraded firmware then it's recommended to do not update your device via OTA. Wait for latest stock firmware or update and flash it.
Fastboot adb files or platform tool links given below
Fastboot- https://androiddatahost.com/wp-conte...oot_v1.4.3.zip
Platform tools- https://developer.android.com/studio...ools#downloads
Motorola driver- http://www.motorola.com/getmdmwin
Stock fastboot firmware August security patch- https://mirrors.lolinet.com/firmware...d50_oem.tar.gz
Now sit back and follow these steps
1.install motorola USB driver, fastboot adb files or platform tools or you'll get adb files inside that firmware folder..
2. Extract tar.gz file through winrar in a folder,copy adb files in that same folder
3. Boot your phone to bootloader screen for that power off your device press volume down following by power button..
4. In that extracted folder press shift in your keyboard and right click on the mouse in a blank space you'll get a option called "open windows command here" type 'fastboot devices' to make sure your device is connected
Exit that cmd window and double click on 'flashall'.bat file(it'll available in the folder) sit back and relax it'll flash your stock firmware...
For more enquiries join telegram group of Motorola one power official
https://t.me/MotoOnePower
Now we can update monthly security patches after flashing this above firmware
1.download ota zip https://drive.google.com/file/d/1PUDntncjTNeqgCyzvqCjdCLpNF3ElxZx/view?usp=drivesdk
move or copy update.zip in SD card into root directory...
2.boot into bootloader scroll down to recovery through volume down button--hit power button to enter recovery mode,once you enter you'll see a "no command" massage,don't panic.hold power button and press once volume up.now a new menu will open.
3.navigate the option called update from sdcard(volume down,hit power button to enter)
4.find update.zip and hit power button..sit back and relax it'll take time to complete the update process...??
Hey,
You did a great job bro, but i want to give you a suggestion, plzz add a warning that flash latest stock firmware with latest security patch only, do not try to downgrade your device.
For example, if you are on September security patch level (on stock firmware) and rooted your device or installed a custom ROM and if you want to revert back to stock firmware then flash the firmware which have September Or greater then September Security patch level.
As downgrading (flashing firmware of older versions or older security patches) can result in hard bricking of your device.
As in example, if you flash august security patch firmware your device may got bricked and believe me guys you don't want it!!).
If however you flashed downgraded firmware then it's recommended to do not update your device via OTA. Wait for latest stock firmware or update and flash it.
ADITYA_KUMAR said:
Hey,
You did a great job bro, but i want to give you a suggestion, plzz add a warning that flash latest stock firmware with latest security patch only, do not try to downgrade your device.
For example, if you are on September security patch level (on stock firmware) and rooted your device or installed a custom ROM and if you want to revert back to stock firmware then flash the firmware which have September Or greater then September Security patch level.
As downgrading (flashing firmware of older versions or older security patches) can result in hard bricking of your device.
As in example, if you flash august security patch firmware your device may got bricked and believe me guys you don't want it!!).
If however you flashed downgraded firmware then it's recommended to do not update your device via OTA. Wait for latest stock firmware or update and flash it.
Click to expand...
Click to collapse
Thnx bro.. I'll add it
September security patch firmware available you can follow op's flashing method
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Happy flashing:fingers-crossed::fingers-crossed:
dayask said:
September security patch firmware available you can follow op's flashing method
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Happy flashing:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
can you attach flashing bat file which I can relock boot loader.
tnmsrkr said:
can you attach flashing bat file which I can relock boot loader.
Click to expand...
Click to collapse
Just type after flashing firmware
fastboot oem lock
dayask said:
just type after flashing firmware
fastboot oem lock
Click to expand...
Click to collapse
after the command bootloader hasbeen locked but ,
while sturtup it is showing different os. Error screen.(it looks like unlocked bootloader screen).
tnmsrkr said:
after the command bootloader hasbeen locked but ,
while sturtup it is showing different os. Error screen.(it looks like unlocked bootloader screen).
Click to expand...
Click to collapse
Go this link above as mentioned
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And unlock the bootloader first.
Then install it. After installing the rom, see if it boots. Let it boot the first time.
Then go back to fastboot mode and relock the bootloader.
Don't do both of these at the same time.
Worked for me.
Reference link here: https://www.getdroidtips.com/stock-firmware-moto-one-power/
Look at the 2nd method in this thread.
Good luck.
Time to upgrade PIE
WARNING: (DO NOT DOWNGRADE YOUR DEVICE)
(From Android pie to Oreo)you may face IMEI and RIL issues later..this process will erase all your internal memory..so do take a backup before proceeding...
You can follow earlier process for upgrading to Android pie..
Flashall.bat should be with in your pie firmware folder
Just double click on it and you good to go...
https://mirrors.lolinet.com/firmwar...PT29.74-25_64be_release-keys-cid50_oem.tar.gz
Happy flashing
Credits @erfanoabdi
Doesn't work even after applying OTA update
nitish2706 said:
Go this link above as mentioned
And unlock the bootloader first.
Then install it. After installing the rom, see if it boots. Let it boot the first time.
Then go back to fastboot mode and relock the bootloader.
Don't do both of these at the same time.
Worked for me.
Look at the 2nd method in this thread.
Good luck.
Click to expand...
Click to collapse
I flashed fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After booting, installed OTA update
then fastboot oem lock, Still shows different os error
rahulsharma0810 said:
I flashed fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After booting, installed OTA update
then fastboot oem lock, Still shows different os error
Click to expand...
Click to collapse
facing same problem
need solution for this
One_Hermit said:
facing same problem
need solution for this
Click to expand...
Click to collapse
We are working on it, it's something related with splash screen or boot img.
I already updated to January security update and messed up which caused a bootloop on my device. can anyone point me to a stock ROM which won't brick my phone? I don't care about my data, just want the phone in working condition again.
rahulsharma0810 said:
I flashed fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After booting, installed OTA update
then fastboot oem lock, Still shows different os error
Click to expand...
Click to collapse
Does your device working proper except this error getting update etc.?
Is it possible to downgrade to stock Oreo safely?
Edit: Nevermind. Got it .
JaggedPill said:
Is it possible to downgrade to stock Oreo safely?
Edit: Nevermind. Got it .
Click to expand...
Click to collapse
Not possible I tried it. You will stuck on logo or lost imei
I have stock pie with April security patch and want to revert to oreo. So, does this mean I should use oreo firmware file with April security patch or greater only?
Also should I unlock bootloader for this?
i rooted my phone after unlocking bootloader but i messed up in the process and my phone went to bootloop and then when i relock bootloader it said "your device is untrusted nd wont boot" but somehow i managed now to flash stock rom but when iam booting it is showing in booting screen "your device has downloaded different os" well after that it is booting fine and phone is running also fine .. is this any problem .. will it create any problem ? and how do i update ota updates which comes in future ???\
how to downgrade ?
I am new here can anyone tell me how can i downgrade my motorola one power from android pie to its original oreo 8.0 version.
Hi all,
After multiple issues with this phone, I finally opt out and pass to Pixel 7 Pro.
So, i would like to know how to relock bootloader avoiding the problems of bootloop.
I've uninstall Magisk with option "complete uninstall".
I saw it's better to flash stock image before relock bootloader but how ?
Simply by flashing boot.img on the two slot OR flashing full.zip generated by Oxygen Updater OR other method ?
Thanks a lot for your help !
fma388 said:
Hi all,
After multiple issues with this phone, I finally opt out and pass to Pixel 7 Pro.
So, i would like to know how to relock bootloader avoiding the problems of bootloop.
I've uninstall Magisk with option "complete uninstall".
I saw it's better to flash stock image before relock bootloader but how ?
Simply by flashing boot.img on the two slot OR flashing full.zip generated by Oxygen Updater OR other method ?
Thanks a lot for your help !
Click to expand...
Click to collapse
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
zopostyle said:
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
Click to expand...
Click to collapse
This phone was promising on paper but the user experience was much less so...
Thank you for the answer !!
For the full zip of Oxygen Updater, I flash it with "fastboot flash full.zip" or how? (I've never flashed a full zip )
fma388 said:
This phone was promising on paper but the user experience was much less so...
Thank you for the answer !!
For the full zip of Oxygen Updater, I flash it with "fastboot flash full.zip" or how? (I've never flashed a full zip )
Click to expand...
Click to collapse
You can use the Local installation system, from the update screen and it that does not support use the OPLocalUpgrade app that Oxygen Updater provides.
zopostyle said:
You can use the Local installation system, from the update screen and it that does not support use the OPLocalUpgrade app that Oxygen Updater provides.
Click to expand...
Click to collapse
Ok thanks !
zopostyle said:
+1 for leaving OnePlus lol
You need to do both, flash the boot.img, then flash the full zip from oxygen updater
And then after a full reset and full boot up you can relock the bootloader.
Click to expand...
Click to collapse
Dear sir, i'm using Ne2213_11_C.30 (Newest Rom). Can u give me the Instructions to relock the bootloader (step by step). I don't know how to flash the boot.img. Thank so much.
hoaianh1505 said:
Dear sir, i'm using Ne2213_11_C.30 (Newest Rom). Can u give me the Instructions to relock the bootloader (step by step). I don't know how to flash the boot.img. Thank so much.
Click to expand...
Click to collapse
If you're on the latest rom there is no need to relock the bootloader
But if you want to, download this https://gauss-componentotacostmanua...23/03/21/b6cfe6d4ec4f4cf7bcb316891f9f8db9.zip
It's the full NE2213 C30 zip file.
Than download https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Intall it on you phone, It will show a new app Local Upgrade, using this tool you will install the above zip file.
After the installation complete, it's recommended to full wipe your device.
Than using adb and fastboot that you can download from here https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
plug you device into your computer
reset it to fastboot mode (turn off, hold power, vol + and vol - until the device start than release power button, once the screen shows the options you can release all buttons and choose fastboot mode if its not there)
on the command prompt type:
Fastboot flashing lock
And that's it.
zopostyle said:
If you're on the latest rom there is no need to relock the bootloader
But if you want to, download this https://gauss-componentotacostmanua...23/03/21/b6cfe6d4ec4f4cf7bcb316891f9f8db9.zip
It's the full NE2213 C30 zip file.
Than download https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Intall it on you phone, It will show a new app Local Upgrade, using this tool you will install the above zip file.
After the installation complete, it's recommended to full wipe your device.
Than using adb and fastboot that you can download from here https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
plug you device into your computer
reset it to fastboot mode (turn off, hold power, vol + and vol - until the device start than release power button, once the screen shows the options you can release all buttons and choose fastboot mode if its not there)
on the command prompt type:
Fastboot flashing lock
And that's it.
Click to expand...
Click to collapse
Thank you so much. Your advice's no need to relock the bootloader, i just worry about the information security. Eg: Banking app can work normal?
After updated to oxygen 13, my phone appear the warning: "phone has been unlocked and cant be trusted ..." each time i boot my device. How can i turn off this warning?
hoaianh1505 said:
Thank you so much. Your advice's no need to relock the bootloader, i just worry about the information security. Eg: Banking app can work normal?
After updated to oxygen 13, my phone appear the warning: "phone has been unlocked and cant be trusted ..." each time i boot my device. How can i turn off this warning?
Click to expand...
Click to collapse
There is no reason to worry about that warning. As your bootloader is not locked the only breach is that a user can manually flash another firmware.
But as he will not have the device on hand there is no problem.
My advice is to not relock, many users bricked their devices doing that.
Also everything works just fine, so no need to relock.
zopostyle said:
There is no reason to worry about that warning. As your bootloader is not locked the only breach is that a user can manually flash another firmware.
But as he will not have the device on hand there is no problem.
My advice is to not relock, many users bricked their devices doing that.
Also everything works just fine, so no need to relock.
Click to expand...
Click to collapse
Thanks for your helpful advice.