Hi all,
I'd been using my rooted Nexus 6P on stock ROM+kernel. Unfortunately, I locked the bootloader after installing TWRP and installing SuperSU. I know, it was a huge mistake but it happened.
Yesterday I wanted to unroot and factory reset the phone. I forgot that my bootloader was locked so I didn't flick that "enable oem unlocking" button. I tried "flash-all" directly on bootloader. Obviously it didn't work and after reboot it got stuck on Google screen. I waited for a while but nothing happened. I wiped system, vendor, cache... etc on TWRP upon a tutorial in this forum with the intention to flash stock ROM but again : my bootloader was locked.
Now, I can still use TWRP and push files through adb but cannot use any fastboot commands. I get this error:
Code:
FAILED (remote: device is locked. Cannot flash images)
I tried installing the whole "image-angler-mdb08l" on TWRP but I get this error:
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/image-angler-mdb08l.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error flashing zip image-angler-mdb08l.zip'
Updating partition details...
...done
Is there any way to flash stock ROM with TWRP or should I try flashing a custom ROM and hoping to boot so I can enable that troublesome OEM unlock switch?
Compared to similar situations in 6P forum, I have the advantage of working adb and TWRP but I don't know if they even make a difference. Thanks for sparing time to read and your help.
You cannot flash factory image with TWRP. Download any custom ROM, flash it with TWRP. Let it boot and enable unlock in Developer Options.
Witek_M said:
You cannot flash factory image with TWRP. Download any custom ROM, flash it with TWRP. Let it boot and enable unlock in Developer Options.
Click to expand...
Click to collapse
You restored my faith in saving this phone. Is there any custom ROM in particular that won't mess with the recovery partition? It seems that if I loose TWRP, I have nothing to hold on to.
afaruky said:
You restored my faith in saving this phone. Is there any custom ROM in particular that won't mess with the recovery partition? It seems that if I loose TWRP, I have nothing to hold on to.
Click to expand...
Click to collapse
I believe that CyanogenMod wouldn't corrupt TWRP recovery. I've flashed official CM on my Galaxy S4 so many times, and CM never replace TWRP with something else. ????
LeoYL said:
I believe that CyanogenMod wouldn't corrupt TWRP recovery. I've flashed official CM on my Galaxy S4 so many times, and CM never replace TWRP with something else. ????
Click to expand...
Click to collapse
:victory: It worked like a charm. Thanks a lot. :victory:
afaruky said:
:victory: It worked like a charm. Thanks a lot. :victory:
Click to expand...
Click to collapse
Now unlock the bootloader, and leave it unlocked.
afaruky said:
:victory: It worked like a charm. Thanks a lot. :victory:
Click to expand...
Click to collapse
metaphz said:
Now unlock the bootloader, and leave it unlocked.
Click to expand...
Click to collapse
And maybe bookmark my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
A bit of research and knowledge would have avoided this issue in the first place.
Heisenberg said:
And maybe bookmark my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
A bit of research and knowledge would have avoided this issue in the first place.
Click to expand...
Click to collapse
Your guide is amazing and helped a lot.
I had been using N5 with locked bootloader and never encountered any problem but when I switched to 6P I read some articles explaining how dangerous leaving the bootloader unlocked is, so I locked it. Obviously, it was a mistake. I'm glad I didn't have to RMA.
afaruky said:
Your guide is amazing and helped a lot.
I had been using N5 with locked bootloader and never encountered any problem but when I switched to 6P I read some articles explaining how dangerous leaving the bootloader unlocked is, so I locked it. Obviously, it was a mistake. I'm glad I didn't have to RMA.
Click to expand...
Click to collapse
There is risk in involved in having an unlocked bootloader, but as long as you take care of your phone and don't let it fall into the wrong hands you'll be perfectly fine. To say it's dangerous would be a pretty big overstatement.
I'm in the same situation, need some help
Sent from my GT-I9500 using Tapatalk
---------- Post added at 02:30 PM ---------- Previous post was at 02:29 PM ----------
I have twrp working fine with no os
Sent from my GT-I9500 using Tapatalk
So why not do exactly what the OP did? Download a custom ROM, flash it with TWRP then unlock your bootloader?
Pain-N-Panic said:
So why not do exactly what the OP did? Download a custom ROM, flash it with TWRP then unlock your bootloader?
Click to expand...
Click to collapse
Its not connecting to bootloader to transfer custom rom.
Sent from my GT-I9500 using Tapatalk
Related
Hello, after two weeks with my OPT I've decided to sell it, I don't like it.
My OPT has Unlocked Bootloader, root and TWRP. I would like to know how can I restore it like it comes from factory (Locked bootloader, unroot and stock recovery)
Thanks everyone.
There are quite a few tutorials on this, i think there is one here also (sorry cant post links), otherwise there is on the official forum on Oneplus website. IF you need video tutorial search for TheUnlockr on YT they posted a tutorial yesterday. Best of luck.
Ok thank you. It's done.
nathebest said:
Ok thank you. It's done.
Click to expand...
Click to collapse
can you say how you did it? i know i can flash the stock Oxygen file but i am having no luck finding the stock recovery so i can replace TWRP.
Rattles said:
can you say how you did it? i know i can flash the stock Oxygen file but i am having no luck finding the stock recovery so i can replace TWRP.
Click to expand...
Click to collapse
This vvv
iterva said:
There are quite a few tutorials on this, i think there is one here also (sorry cant post links), otherwise there is on the official forum on Oneplus website. IF you need video tutorial search for TheUnlockr on YT they posted a tutorial yesterday. Best of luck.
Click to expand...
Click to collapse
Of course, after you have flashed stock OxygenOS in TWRP, you wipe data/cache and click reboot system. TWRP ask you to swipe to keep TWRP or you click on Not Disable. Just click on it and the stock recovery is back.
For the bootloader, start the phone on fastboot mode (VOL UP+POWER) and type "fastboot oem lock" in a terminal window.
nathebest said:
Of course, after you have flashed stock OxygenOS in TWRP, you wipe data/cache and click reboot system. TWRP ask you to swipe to keep TWRP or you click on Not Disable. Just click on it and the stock recovery is back..
Click to expand...
Click to collapse
that's the problem, it never asked me to swipe to keep twrp. it just flashed OxygenOS but kept the recovery. oh well, all good now!
nathebest said:
TWRP ask you to swipe to keep TWRP or you click on Not Disable. Just click on it and the stock recovery is back.
Click to expand...
Click to collapse
This is available only on the unofficial TWRP.There's no such choice in the official one.
Tapped from my ❶+❷
vaisakh7 said:
This is available only on the unofficial TWRP.There's no such choice in the official one.
Tapped from my ❶+❷
Click to expand...
Click to collapse
Ok, I didn't know that.
v7 said:
This is available only on the unofficial TWRP.There's no such choice in the official one.
Tapped from my ❶+❷
Click to expand...
Click to collapse
I have Official TWRP how do i go back to stock recovery ?
nathebest said:
Ok thank you. It's done.
Click to expand...
Click to collapse
Hi. Are you able to successfully relock your bootloader? Because I've read some people who relocked the bootloader just bricked the device.
Same situation, though in my case, Im returning the device. Does anybody know if I even have to relock the bootloader before I return it? Its unlocked and rooted with official twrp recovery.
From what I have read so far, relocking the bootloader will brick the device if one does not restore the stock recovery first. But am not 100% sure this is right. Also, I saw a few people posting the stock recovery, but its unclear what version of the device the recovery is for. If Im not mistaken, there are three versions of the hardware, Chinese, Europe (and India) and US. Is it okay to flash a stock recovery from a different region? If not, is there any other way to go back to stock recovery before bootloader relock?
UPDATE: Scratch that, I just had a chat with OnePlus Support and was told that when returning a device to seller, there is no need to unroot and relock the bootloader. If anything, trying to do so might brick the device and kill the warranty, but unlocked and rooted, warranty still applies, and its perfectly fine to return as is.
DISCLAIMER
I'm not responsible for any damage, bootloop, bricked or broken handsets.
Notice
The recovery can't be flashed to the handset with locked bootloader! Unlock it first!
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom and stock (with some remarks) ROMs to your device, repair broken file systems, and root your device.
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Update 29.03.2016
It's alive! First experimental working build published at internal 4pda Russian board.
Download
TWRP 3.0 M86 fastboot flashable image
TWRP 3.0 M86 flashable zip
Stock Recovery flashable zip
Unlocked BL flashable zip
Install
With BL unlocked reboot into fastboot mode and flash:
Code:
fastboot flash recovery TWRP_3.0_m86.img
Cautions
Before flashing stock rom with TWRP replace bootloader file with unlocked one inside rom archive!!!!
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)
JUST IN CASE this is an April fools.... I'll wait ?
Great mate, u've stolen my idea in the end, right ?!
Gooooood work, thank u very much ! Testing wip :highfive:
---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------
Nein, first step doesn't work
Flashing unlocked BL through stock recovery, I get always the same result :
FIRMWARE CORRUPT
Click to expand...
Click to collapse
faust93 said:
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Click to expand...
Click to collapse
*Working fine
PYCON said:
Nein, first step doesn't work
Click to expand...
Click to collapse
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
toms157 said:
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
Click to expand...
Click to collapse
Ahahah yes yes but the purpose of BL_UNLOCKED.ZIP is to unlock bootloader. But in order to flash it correctly... we've to have the bootloader already unlocked
Damn it, it's really stupid, right ?
PYCON said:
Damn it, it's really stupid, right ?
Click to expand...
Click to collapse
Filename could lead to confusion, sure... It's needed for this :
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)"
Click to expand...
Click to collapse
Meanning flash 3 files from custom recovery without rebooting
Anyway this is not a catch-22, leaked beta from tutorial is the entry point
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
showofdeth said:
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
Click to expand...
Click to collapse
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
naboleo said:
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
Click to expand...
Click to collapse
Oh man that's great to hear! Thanks. Bought myself a laptop specifically to get my PRO 5 all TWRP'd up.
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
showofdeth said:
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
Click to expand...
Click to collapse
Never had troubles to downgrade to leaked beta
naboleo said:
Never had troubles to downgrade to leaked beta
Click to expand...
Click to collapse
Brilliant. Thanks a lot. Can't wait to hear people's experiences with this.
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
That TWRP works perfectly for me, backup nandroid, restore it, flash ZIP rom and ZIP other ( Xposed, etc ), no problem at all :highfive:
Good job !!! Great, thx !!!
Thank you so much for this!!! could i ask you how you managed to create a recovery for the pro5?
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
I assume youare still on 5.6.1.19: Thats an error with this version.... put the updatefile manually (in the PC) on the external sd and flash via TWRP... you should later update your modified Pro 5 to 5.1.3.0, the error ist gone then...
Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
Copy UPDATE.ZIP from PC to phone BUT CONNECTING THE PHONE WHEN IT'S OPENED TWRP
MTP mode works great, even u'r on 5.6.1.19 :highfive:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
PYCON said:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
Click to expand...
Click to collapse
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
cedric3 said:
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
Click to expand...
Click to collapse
Uh I didn't know that a new version was released... Maybe, I could be. I download it again and try... Thx man ! :highfive:
The last version can't read the micro sd.
i am very frustrated, I get into TWRP again and again no matter what i do. Bootloader unlocked, I can finish the dirtycow rooting, flash SU, and a ROM. And then.
I am greeted by TWRP.
There is this one time I booted up the WETA rom, i didn't like something so I reflashed the room, thus beginning my TWRP bootloop nightmare...
Are you saying that after flashing rom your device is rebooting constantly into twrp?
Team DevDigitel said:
Are you saying that after flashing rom your device is rebooting constantly into twrp?
Click to expand...
Click to collapse
yes
dangercl0se said:
yes
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Its a common issue on the ls997
Related to having been on older softwear and
Your phone dl the update.zip and is causing this
Need to delete fota and misc directories
I have walkthrough in above link.
thanks so much. i really appreciate that
i did dive into the directories and can't find most of them, i will try again with the fastboot method. when do i do that? after i completed root and flashed super su?
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.
While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs Before doing this make sure EVERYTHING is stock! This includes custom recoveries. I do not claim any responsibility if anything goes wrong!
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.
Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)
Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs
OsiBasi said:
Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)
Click to expand...
Click to collapse
I didn't use any drm content while it was unlocked, so I can't tell. Sorry
steadfasterX said:
Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail
alex2000robert said:
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail
Click to expand...
Click to collapse
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.
steadfasterX said:
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.
Click to expand...
Click to collapse
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.
alex2000robert said:
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.
Click to expand...
Click to collapse
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
btw you should consider to add a [N only] or similar in the thread title
.
steadfasterX said:
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
.
Click to expand...
Click to collapse
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.
alex2000robert said:
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.
Click to expand...
Click to collapse
lol yes true so true :highfive: :victory:
title is perfect now
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol
pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
Click to expand...
Click to collapse
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Edit: Oh I just saw your added post about not being able to boot into the Download mode, I can't help you at the moment. Haven't figured out why some devices refuse to boot into the Download mode...
Mr.FREE_Bird said:
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Click to expand...
Click to collapse
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working
alex2000robert said:
While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.
Click to expand...
Click to collapse
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.
steadfasterX said:
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.
Click to expand...
Click to collapse
Thanks, just added that.
pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol
Click to expand...
Click to collapse
Sorry, don't know how to help you here. I read about this error snd supposedly after 10 seconds this message should go away by its own... Try to boot it and wait a little. Then unlock back the bootloader with the unlock.bin and flash the stock recovery from the ZIP file of V29a (which should've flashed by itself, did you remove it?) and only then lock the bootloader. Make sure everything is stock.
pedrogcsb said:
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working
Click to expand...
Click to collapse
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Hello,
Is it still possible to unlock the boot loader of an LG G4? Their site is not working.
Minto107 said:
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853 I think I will try this next in the morning
Did anyone try unlocking the bootloader as well?
Sent from my iPhone using Tapatalk