[Query] OPO Complete Factory Reset - How to? - ONE Q&A, Help & Troubleshooting

Hi All,
I have unlocked the bootloader and have been using sultanxda CM13.0 rom for quite some time. Due to some personal requirements (Airwatch compliance issues at office!), I want to reset my OPO back to original factory settings, return to stock and reset/lock the bootloader.
Can anyone help me with this?
Thanks in advance!

3lok said:
Hi All,
I have unlocked the bootloader and have been using sultanxda CM13.0 rom for quite some time. Due to some personal requirements (Airwatch compliance issues at office!), I want to reset my OPO back to original factory settings, return to stock and reset/lock the bootloader.
Can anyone help me with this?
Thanks in advance!
Click to expand...
Click to collapse
Follow this guide
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

Related

[Q] Please help a noob...

Hi guys, sorry in advance for my silly question, I have just installed a factory ROM on my LG E900 (optimus 7) and have the version 7.0.7004.0... after that I have unlocked the phone usind the phones registry editor (not chevron) and I think everything went well (no errors)... but after all that I made a factory reset on the phone, now my question is: do I need to unlock it again after factory reset or it remained unlock anyway? Thanks in advance for any assistance and for your pacience as well.
What do you mean by factory reset?
Also there is one easy way to test - try sideload an application.
I would imagine that a reset would set your phone back to the way it was when you got it / after flashing it.
PsyCLown89 said:
What do you mean by factory reset?
Also there is one easy way to test - try sideload an application.
I would imagine that a reset would set your phone back to the way it was when you got it / after flashing it.
Click to expand...
Click to collapse
Hi, thx for your reply, factory reset from settings - about - reset your phone, yes I just tryed now and it's not working so I presume must unlock again... thank you very much, regards

Return to Factory state

Hi all!
I need a advice (help) from someone,please...
I'm on CROMi v5 RC1 Custom Rom.Now i need go back to stock (without root and custom Recovery-for garantie purpose).
Can anyone suggest me (short step by step) how i get rid of root and custom recovery and put a orig.FW from Asus as simple as possible?
Many thanks for any advice!
ValVK said:
Hi all!
I need a advice (help) from someone,please...
I'm on CROMi v5 RC1 Custom Rom.Now i need go back to stock (without root and custom Recovery-for garantie purpose).
Can anyone suggest me (short step by step) how i get rid of root and custom recovery and put a orig.FW from Asus as simple as possible?
Many thanks for any advice!
Click to expand...
Click to collapse
I don't think that this can be done. It has been asked a few times and that was the answer i believe.
Jeff
ValVK said:
Hi all!
I need a advice (help) from someone,please...
I'm on CROMi v5 RC1 Custom Rom.Now i need go back to stock (without root and custom Recovery-for garantie purpose).
Can anyone suggest me (short step by step) how i get rid of root and custom recovery and put a orig.FW from Asus as simple as possible?
Many thanks for any advice!
Click to expand...
Click to collapse
Check my All in One thread in General Forum, you will find the guide for doing a factory restore. But keep in mind that you won't be able to relock the bootloader and honestly even if it would be possible, Asus would still be able to check if your device was unlocked.
Pretoriano80 said:
Check my All in One thread in General Forum, you will find the guide for doing a factory restore. But keep in mind that you won't be able to relock the bootloader and honestly even if it would be possible, Asus would still be able to check if your device was unlocked.
Click to expand...
Click to collapse
Other than the warranty, what does it matter if you can't re-lock the bootloader? Will it still operate as a factory device i.e. receive system updates etc.?
davidbecht02 said:
Other than the warranty, what does it matter if you can't re-lock the bootloader? Will it still operate as a factory device i.e. receive system updates etc.?
Click to expand...
Click to collapse
Nope, after unlock you will no longer receive OTA updates.

Factory reset phone with root and twrp

Hello guys, yesterday I sold my phone. Now im trying to factory reset my Oneplus one in the menu. But when I do that it reboots and gets in a TWRP bootloop. I already backedup my data on my new phone, so I just want to get rid of everything. When I reboot the phone nothing has changed and all my apps and data are still there. Anyone have an idea what I should do? Thanks in advance.
Iniesta89 said:
Hello guys, yesterday I sold my phone. Now im trying to factory reset my Oneplus one in the menu. But when I do that it reboots and gets in a TWRP bootloop. I already backedup my data on my new phone, so I just want to get rid of everything. When I reboot the phone nothing has changed and all my apps and data are still there. Anyone have an idea what I should do? Thanks in advance.
Click to expand...
Click to collapse
Simply boot into Recovery, tap Wipe and swipe to begin the process. Doing so will perform a regular Factory Reset.
Sent from my Nexus 4 using XDA Free mobile app
Iniesta89 said:
Hello guys, yesterday I sold my phone. Now im trying to factory reset my Oneplus one in the menu. But when I do that it reboots and gets in a TWRP bootloop. I already backedup my data on my new phone, so I just want to get rid of everything. When I reboot the phone nothing has changed and all my apps and data are still there. Anyone have an idea what I should do? Thanks in advance.
Click to expand...
Click to collapse
The best way to ensure that the device is ready for sale is by flashing the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
The best way to ensure that the device is ready for sale is by flashing the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Guys thanks for the tips . Whats the actual difference with sitins method? Cause that seem tot have worked.
Iniesta89 said:
Guys thanks for the tips . Whats the actual difference with sitins method? Cause that seem tot have worked.
Click to expand...
Click to collapse
Well the method that I suggested will ensure that the phone is back to a 100% stock state, exactly as it came out of the box.

The cellular network won't start after root.

Hello guys, i have an oneplus one for a month or two and yesterday i rooted it using Kingroot *i haven't unlocked the bootloader or something like this, just pressed root and waited* , i have busybox , lucky patcher things like this nothing special. Since then my cellular network won't start. Is the only solution to unroot or even maybe reset the phone to the factory settings? I would preffer not to.
Kachada said:
Hello guys, i have an oneplus one for a month or two and yesterday i rooted it using Kingroot *i haven't unlocked the bootloader or something like this, just pressed root and waited* , i have busybox , lucky patcher things like this nothing special. Since then my cellular network won't start. Is the only solution to unroot or even maybe reset the phone to the factory settings? I would preffer not to.
Click to expand...
Click to collapse
root does not affect network generally .check apn settings and
unlocking bootloader does not void warranty and do not use one click root if not urgently needed
#sychrome# said:
root does not affect network generally .check apn settings and
for bootloader does not void warranty using cheese app
Click to expand...
Click to collapse
I spoke with a pro from my network provider and he made do some steps and it didn't help me, he said to me to check the sim and the sim works perfect on a non rooted android. So i guess its from the root.
Edit: he asked me if i re-softed my phone and told me to do a factory reboot if the sim is good.
Kachada said:
I spoke with a pro from my network provider and he made do some steps and it didn't help me, he said to me to check the sim and the sim works perfect on a non rooted android. So i guess its from the root.
Edit: he asked me if i re-softed my phone and told me to do a factory reboot if the sim is good.
Click to expand...
Click to collapse
reset data is setback try using custom recovery for new modems or new ROM and use titanium backup for safety it would not help in future if it is because of root.
#sychrome# said:
reset data is setback try using custom recovery for new modems or new ROM and use titanium backup for safety it would not help in future if it is because of root.
Click to expand...
Click to collapse
I don't want to change my cyanogen rom, it's great, i'll unroot it and maybe even reset it. I need the data more than the root.
Thanks!
Kachada said:
I don't want to change my cyanogen rom, it's great, i'll unroot it and maybe even reset it. I need the data more than the root.
Thanks!
Click to expand...
Click to collapse
Your best bet is to unlock bootloader, wipe system and reflash your ROM (with custom recovery) , there are COS signed flashable zips in General Section. Unlocking bootloader if you've never done it before wipes the phone so backup your data to a PC and keep it unlocked, it doesn't void your warranty and it makes troubleshooting issues much easier. Factory reset of the phone WILL NOT remove root.
Sent from my A0001 using Tapatalk
Well i already unrooted it and deleted everything.I'm afraid to unlock the bootloader because i have never done something like this, my biggest experience with androids software is to root them with android apps . Would you recommend me to re-soft it to cm 13 official build or to factory reset it? I'll look for a tutorial for the bootloader and do my best.
Oh, and by the way, if i clear it unlock the bootloader etc and i can't fix the problem what should i do?
I'm a newbie so probably what i'm asking is stupid, but isn't there any chance that the bootloader is unlocked? I can enter it idk..
Check you APN settings , erase them and rewrite them. Root does not affect network. And i don't see how you would be able to switch ROMs if you don't unlock your bootloader...
thats why i said that i will unlock the bootloader. and i did the apn checking with a pro from the orange *my provider* and nothing, he even changed my settings from their system. It has too be from the root , i used the cellular to download the apps for the root, then rooted it rebooted and no more cellular.
Oh and i have another reason to think its from the root because after i rooted the phone some apps started to fall down. Apex launcher for example.
Renosh said:
Your best bet is to unlock bootloader, wipe system and reflash your ROM (with custom recovery) , there
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
u can use bootloader unlock without data loss just search here for <zip file> at xda 1+1
#sychrome# said:
u can use bootloader unlock without data loss just search here for <zip file> at xda 1+1
Click to expand...
Click to collapse
I unlocked bootloader when I bought the phone so its not relevant to me. It's a one time operation
Sent from my A0001 using Tapatalk
Renosh said:
I unlocked bootloader when I bought the phone so its not relevant to me. It's a one time operation
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
same here but it would help others out
and i thinks that 1clickroot ripped his phone and services to this state.
moreover when <theguy> u use custom recovery do not modify system partition if u want ota
a q to <expert> is he able to flash systemless root without modifying system partition?
i tried to flash cm13 from twrp and it gave me error 7 , so ya i'm resetting it to the factory settings.
Kachada said:
i tried to flash cm13 from twrp and it gave me error 7 , so ya i'm resetting it to the factory settings.
Click to expand...
Click to collapse
So you've been on CM13 and you're flashing kingroot? #facepalm
Sent from my A0001 using Tapatalk
No, I used kingroot on 12.1 yogd7, I unrooted it and tried to flash it to 13. I'll resoft it to the stock that's my only option. Does the resoft to the stock *with a PC* void my warranty?
Kachada said:
No, I used kingroot on 12.1 yogd7, I unrooted it and tried to flash it to 13. I'll resoft it to the stock that's my only option. Does the resoft to the stock *with a PC* void my warranty?
Click to expand...
Click to collapse
Seriously go do some major reading cause you seem to know nothing and despite having issues with your phone since recently have made zero effort to use the stickies and guides in General section as well as this section where you posted this question. The information you need to learn is all over. Flashing the factory image needs an unlocked bootloader last I checked (might be wrong) and you have to do it via fastboot. There are stickies for OPO you just have to click and read or even go to YouTube lots of people have provided step by step guides.
It will not void your warranty, neither will unlocking your bootloader void your warranty on this phone.
Sent from my A0001 using Tapatalk
First you have to unlock your bootloader
Then flash firmware , now you can get your network working, if you want flash twrp recovery and root with SuperSU. Or just flash twrp recovery and flash cm13 ROM.
DON'T USE KINGROOT LIKE ONE CLICK ROOTS , AS THEY WERE WORKING UPTO KITKAT ONLY. SINCE LOLLIPOP YOU HAVE TO UNLOCK BOOT LOADER AND FLASH RECOVERY AND SUPERSU FOR ROOT.READ WHATEVER YOU NEED IN OPO XDA FORUM . IF YOU DON'T WANT TO LOSS YOUR DATA COPY YOUR INTERNAL STORAGE TO PC AND BACKUP CONTACTS ETC TO YOUR EMAIL ID, THEN YOU WILL NEVER LOSS ANYTHING. ME TOO AFRAID OF ROOTING BUT I ROOTED 6 DEVICES IN PAST 8 MONTHS , NEVER LOOSE MY DATA EVERYTHING. STICK WITH XDA AND.....
WELCOME TO THE REAL WORLD.
OK guys, thanks.
I have solved the problem with manudroid19's toolkit, thanks for your help guys.
Off-topic: Do you know what is the error 2 on twrp? i didn't find it on google, i get it when i try to flash gapps on cm13.*i try to do this because not even 1 google apps work and i gave them all the permissions.I deleted cache data etc,rebooted a few times*

Don't Re-Lock Your Bootloader

As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .

Categories

Resources