Related
hi,
my USB port on my phone is broken and I need to go back to stock ROM for warrenty. Currently I use the Paranoid ROM 4.2.2 JDQ39 (3.67) and TWPR recovery. I read a lot of posts but I didn´t find a complete guide. So I want to ask if I can do it this way?
1. Close Bootloader with "BootUnlocker for Nexus Devices" app from the playstore
2. Download Factory Image 4.2.2 from the google developers page
Extract everything. I need the files: System.IMG, Boot.IMG, Userdata.IMG, Recovery.IMG ? Or do I need other files?
3. Install Mobile Odin Pro on my phone
4. Load the IMG files in Mobile Odin Pro and start
Is this right? What is with the radio? I have XXLJ1 on my phone. I think it is the latest. Isn´t it?
It would be nice if someone can help me.
thanks
//Patrice// said:
hi,
my USB port on my phone is broken and I need to go back to stock ROM for warrenty. Currently I use the Paranoid ROM 4.2.2 JDQ39 (3.67) and TWPR recovery. I read a lot of posts but I didn´t find a complete guide. So I want to ask if I can do it this way?
1. Close Bootloader with "BootUnlocker for Nexus Devices" app from the playstore
2. Download Factory Image 4.2.2 from the google developers page
Extract everything. I need the files: System.IMG, Boot.IMG, Userdata.IMG, Recovery.IMG ? Or do I need other files?
3. Install Mobile Odin Pro on my phone
4. Load the IMG files in Mobile Odin Pro and start
Is this right? What is with the radio? I have XXLJ1 on my phone. I think it is the latest. Isn´t it?
It would be nice if someone can help me.
thanks
Click to expand...
Click to collapse
You'll have to close the bootloader last otherwise you won't be able to flash the imgs.
I don't know if you'll can, you'll have to keep root when you reset it because you'll have to lock the bootloader last, then you could factory reset.
Not sure though.
Beauenheim said:
You'll have to close the bootloader last otherwise you won't be able to flash the imgs.
I don't know if you'll can, you'll have to keep root when you reset it because you'll have to lock the bootloader last, then you could factory reset.
Not sure though.
Click to expand...
Click to collapse
I thought I don't need a open bootloader for Odin Mobile?
I just did this with the same problem about a month ago, and I relocked the bootloader first because you won't have root or a way to use fastboot to lock it afterward. Odin worked just fine with bootloader locked.
underwaterjr said:
I just did this with the same problem about a month ago, and I relocked the bootloader first because you won't have root or a way to use fastboot to lock it afterward. Odin worked just fine with bootloader locked.
Click to expand...
Click to collapse
You did it the same way as I described it in my first post?
Does nobody know if i can do it this way?
Sent from my Galaxy Nexus using xda app-developers app
i sent my gnex in for the same broken usb port issue, and all i did to the bad one was do a factory reset on cm10.whatever it was at the time, and locked the bootloader with that app, probably did that first i guess lol.
but they havent charged me for that, so i assume its all good, its been a few months so if they were going to charge me they would have i assume
un4givn85 said:
i sent my gnex in for the same broken usb port issue, and all i did to the bad one was do a factory reset on cm10.whatever it was at the time, and locked the bootloader with that app, probably did that first i guess lol.
but they havent charged me for that, so i assume its all good, its been a few months so if they were going to charge me they would have i assume
Click to expand...
Click to collapse
But I´m not sure if it works for me too, so I would like to try to go back to stock ROM. The problem is that I don´t know if it works with this guide and I don´t want to make a mistake.
can anyone tell me if it is possible to use the 4.2.2 factory image from the google developers site or do I have to use a special odin file?
If I have to use a odin file where can I find it? I only found old files with android 4.0.1
thanks in advance for any help.
Can anybody help me with my problem? I try to go back to stock to send it in.
Thanks
Sent from my Transformer TF101 using xda app-developers app
This may or may not be relevant but I used to have a T989 (TMO GSII) and the USB port when bad as well. Any connection that I attempted would last brief moments and in one of those, I took the chance and tried restoring. What ended up happening is the update did not complete and the phone remained in the ODIN screen even after reboots. I sent it in like so and they still honored the warranty. So what I'm trying to say, as a last resort you could intentionally brick your GN...
I have heard however, that warranty companies don't always check to see if you've messed with the software so there's another thought.
Just send it back as is. Your problem is hardware related, not software. They'll refurb the phone and re-image it anyway.
Thanks for your answers!
OK I understand. But is it that dangerous to go back to stock without USB, so I shouldn't do it or is it only that you think it is not necessary?
Sent from my Transformer TF101 using xda app-developers app
Hi,
I have still the same problem. Is nobody here who can help me?
I have the problem that I don´t know if I can use the guide from my first post, and which file I can use.
thanks for any help!
//Patrice// said:
Hi,
I have still the same problem. Is nobody here who can help me?
I have the problem that I don´t know if I can use the guide from my first post, and which file I can use.
thanks for any help!
Click to expand...
Click to collapse
Why dont you download this on your phone directly http://forum.xda-developers.com/showthread.php?t=1882248 and then flash it using Mobile Odin or Recovery. Dont flash SuperUser. Factory reset and then lock the bootloader.
Wouldnt that work?
rajuki said:
Why dont you download this on your phone directly http://forum.xda-developers.com/showthread.php?t=1882248 and then flash it using Mobile Odin or Recovery. Dont flash SuperUser. Factory reset and then lock the bootloader.
Wouldnt that work?
Click to expand...
Click to collapse
I think I could flash this with TWRP, if it´s no problem that I come from Paranoid 4.2.2 ? But it is not really stock. Is it? What happen than when I do the factory reset? Does it erase TWRP? And I think I need root to lock the bootloader...
//Patrice// said:
I think I could flash this with TWRP, if it´s no problem that I come from Paranoid 4.2.2 ? But it is not really stock. Is it? What happen than when I do the factory reset? Does it erase TWRP? And I think I need root to lock the bootloader...
Click to expand...
Click to collapse
So lets try this again, OK?
1. Download the stock rom from the link and copy to your phone
2. Boot into TWRP
3. Wipe data
4. Flash the stock 4.3 rom you downloaded
5. Reboot.
Now, you have stock 4.3 but you are still rooted. A factory reset from the OS doesnt unroot you or takes away your root.
6. Download this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en and lock yout bootloader. This will do a wipe again.Now reboot.
7. Remove /system/bin/su via adb shell or by using root explorer
8. Remove /system/app/Superuser.apk via adb shell on phone or by using root explorer
9. Factory reset.
Done. By now, you should be stock, unrooted and without any custom recoveries.
rajuki said:
So lets try this again, OK?
1. Download the stock rom from the link and copy to your phone
2. Boot into TWRP
3. Wipe data
4. Flash the stock 4.3 rom you downloaded
5. Reboot.
Now, you have stock 4.3 but you are still rooted. A factory reset from the OS doesnt unroot you or takes away your root.
6. Download this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en and lock yout bootloader. This will do a wipe again.Now reboot.
7. Remove /system/bin/su via adb shell or by using root explorer
8. Remove /system/app/Superuser.apk via adb shell on phone or by using root explorer
9. Factory reset.
Done. By now, you should be stock, unrooted and without any custom recoveries.
Click to expand...
Click to collapse
OK this sounds good. I will try it.
Thank you!!
rajuki said:
So lets try this again, OK?
1. Download the stock rom from the link and copy to your phone
2. Boot into TWRP
3. Wipe data
4. Flash the stock 4.3 rom you downloaded
5. Reboot.
Now, you have stock 4.3 but you are still rooted. A factory reset from the OS doesnt unroot you or takes away your root.
6. Download this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en and lock yout bootloader. This will do a wipe again.Now reboot.
7. Remove /system/bin/su via adb shell or by using root explorer
8. Remove /system/app/Superuser.apk via adb shell on phone or by using root explorer
9. Factory reset.
Done. By now, you should be stock, unrooted and without any custom recoveries.
Click to expand...
Click to collapse
I have one more question. In step 3 should I do a factory reset before I flash the rom? Because I usually do one when I install a new rom and I don't want to do a mistake because I can't use usb to fix it. And is it OK that I go from 4.2.2 Paranoid to this 4.3 stock rom?
//Patrice// said:
I have one more question. In step 3 should I do a factory reset before I flash the rom? Because I usually do one when I install a new rom and I don't want to do a mistake because I can't use usb to fix it. And is it OK that I go from 4.2.2 Paranoid to this 4.3 stock rom?
Click to expand...
Click to collapse
Before you flash the new ROM; you must wipe data.
And yes, its OK to come from 4.2.2 to 4.3 as long as you wipe data.
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
I'm going to be exchanging my pixel and getting another one. Just curious so I know for the future.. if I flash the full factory image via fastboot does that relock the bootloader? I'm gonna guess that it doesn't but just wanna make sure.
New to adb and fastboot so I've been reading around like crazy trying to learn. Is the only way to lock again to use the actual lock command in fastboot?
Edit: I'm referring to using the flash-all.bat script
Yes, you will have to re-lock the bootloader. Do it with fastboot in the bootloader.
Although, you don't have to re-lock the bootloader before sending your phone back... Especially since it will have the stock image flashed to it.
aholeinthewor1d said:
if I flash the full factory image via fastboot does that relock the bootloader?
Click to expand...
Click to collapse
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
cam30era said:
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
Click to expand...
Click to collapse
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
canemaxx said:
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
Click to expand...
Click to collapse
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
cam30era said:
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
Click to expand...
Click to collapse
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
canemaxx said:
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
Click to expand...
Click to collapse
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
cam30era said:
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Click to expand...
Click to collapse
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
canemaxx said:
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
Click to expand...
Click to collapse
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
cam30era said:
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
Click to expand...
Click to collapse
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
canemaxx said:
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
Click to expand...
Click to collapse
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
cam30era said:
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
Click to expand...
Click to collapse
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
In fact, on Windows I think you can just double click the flash-all.bat file (I'm on Linux, so I'm not 100% positive). Yes to your other questions. As long as nothing goes wrong.
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
Been here for about 4 minutes, is that normal?
canemaxx said:
Been here for about 4 minutes, is that normal?
Click to expand...
Click to collapse
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
cam30era said:
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
Click to expand...
Click to collapse
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
canemaxx said:
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
Click to expand...
Click to collapse
Very good.
You sure like living on the edge...
cam30era said:
Very good.
You sure like living on the edge...
Click to expand...
Click to collapse
Haha thanks again for all your help!! 7.1.1 installed and root is back!! This may be the last time I get to update my phone for a while lol
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer? ?
thank you!
Blooddrunked said:
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer?
thank you!
Click to expand...
Click to collapse
if you're returning it to Google they don't really care if it's locked or not. I've sent them back for an RMA both ways never had any problems
Agree, relocking shouldn't be needed for a RMA...
Just make sure your device is completely stock at the very least.
Personally, I'd flash the factory images to both slots and lock the bootloader. However, if others have suggested they don't have any issues sending it back with the bootloader unlocked, then just flash the factory images.
Although, it is just one command to lock it (just be absolutely sure you're completely stock before locking, if you go that route).
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ?
Click to expand...
Click to collapse
You can't, and don't worry about it.
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Click to expand...
Click to collapse
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Badger50 said:
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Click to expand...
Click to collapse
Thank you! it worked!
Blooddrunked said:
Thank you! it worked!
Click to expand...
Click to collapse
Well there ya go! Your welcome. :good::good:
how long does it take to get the replacement from google??
That's exactly why I never unlock the bootloader, root, install custom ROMs, etc. I don't want to be in the situation where I can't use my warranty or insurance.
kismetmookz said:
how long does it take to get the replacement from google??
Click to expand...
Click to collapse
My bootloader was unlocked and it was not an issue. I sent my phone back and got a new phone in 6 days. I guess it would also depend on where you live. I live on the east coast and sent my phone to Texas and they sent me a new one from Illinois.
want to put my p6p back to stock. currently rooted on stock firmware stock kernel etc. what's the best way to get it back to stock? do I need to flash back the stock boot image before I lock the bootloader?
Magisk has an option to unroot then you can lock the bootloader
Either as @spart0n proposed or flash the original factory image (for that I prefer to using the Android Flash Tool, using the fastboot method has so far always failed to work for me).... After that you are back on original stock and can proceed to relock the bootloader using "fastboot flashing lock" (detailed info on the above linked page)
whatsisnametake2 said:
want to put my p6p back to stock. currently rooted on stock firmware stock kernel etc. what's the best way to get it back to stock? do I need to flash back the stock boot image before I lock the bootloader?
Click to expand...
Click to collapse
Official Google Android Flash Tool, and then lock the bootloader after that.
Note that you should never lock the bootloader unless you're 100% stock, and flashing the full stock image is the only way of ensuring that, even if you choose to not let Official Google Android Flash Tool wipe your user data, as well.
ok thanks. so if I wasn't going to use the android flash tool, flash the full stock image, then lock bootloader?
whatsisnametake2 said:
ok thanks. so if I wasn't going to use the android flash tool, flash the full stock image, then lock bootloader?
Click to expand...
Click to collapse
Yes. I would leave the oem unlock slider at allow unlock for awhile in case it goes sideways. I would wait for the first OTA update before changing that.
TonikJDK said:
Yes. I would leave the oem unlock slider at allow unlock for awhile in case it goes sideways. I would wait for the first OTA update before changing that.
Click to expand...
Click to collapse
Great advice. Once it's stable you can flip the OEM switch and a reboot reenables all security features.
TonikJDK said:
Yes. I would leave the oem unlock slider at allow unlock for awhile in case it goes sideways. I would wait for the first OTA update before changing that.
Click to expand...
Click to collapse
you mean in developer options? I hadn't thought of that thanks. so a full factory flash with wipe doesn't set that back to off?
so,
full factory flash with wipe
lock bootloader
boot into phone and turn OEM unlocking off
factory reset from phone settings
I'm returning the phone to google so it needs to be completely stock.
whatsisnametake2 said:
you mean in developer options? I hadn't thought of that thanks. so a full factory flash with wipe doesn't set that back to off?
so,
full factory flash with wipe
lock bootloader
boot into phone and turn OEM unlocking off
factory reset from phone settings
I'm returning the phone to google so it needs to be completely stock.
Click to expand...
Click to collapse
If you are returning it them skip my advice and do your steps.
Don't worry about this too much. Google does not care if you unlocked it.
TonikJDK said:
If you are returning it them skip my advice and do your steps.
Don't worry about this too much. Google does not care if you unlocked it.
Click to expand...
Click to collapse
ok thanks. so if you flash factory image then lock bootloader, the oem unlock will still be set to on when you go into the phone?
whatsisnametake2 said:
ok thanks. so if you flash factory image then lock bootloader, the oem unlock will still be set to on when you go into the phone?
Click to expand...
Click to collapse
Correct
TonikJDK said:
Correct
Click to expand...
Click to collapse
ok cheers