Related
Hi there,
I think I may have messed up my tablet. I recently was trying to update it through the fastboot commands but after wiping the internal storage and data, I went back to the bootloader and found out that the device was locked now. I can't fastboot flash anything since I don't have permission to do anything. I have TWRP flashed to the recovery though but when I go into there it asks for a password. I checked to see and it's because the device is locked, so I needed to unlock it. Well unfortunately there isn't an OS on the tablet to go into the settings and unlock it from. I was trying to flash Dirty Unicorns to see if I could just change it there but it fails during flash saying '/umount system failed: no volume exsists' if I try to reboot after that it just goes to the Google screen and does nothing.
So Bootloader Locked, TWRP installed, can't unlock bootloader since no OS installed.
Help!
Edit: I put this in the wrong forum. My bad.
@Verttex,
Let me see if I have understood your situation:
- bootloader is locked
- No ROM (deleted?)
-TWRP recovery installed, but you can't get into it because it requests a password?
---------- Post added at 08:07 PM ---------- Previous post was at 07:37 PM ----------
[/COLOR @Verttex
I think there is a solution for you on the Nexus 6 forum. See post #40 here >http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539/page4
Well I did the third command with the unlock.IMG that they provided, but now the screen doesn't work. It seems I can still get it to go to the bootloader since my computer detects it.
I might be able to get it to TWRP and then run the adb command again but right now, the screen is just blank.
Maybe I accidentally flashed the n6 unlock image instead of the n9 one?
Verttex said:
Well I did the third command with the unlock.IMG that they provided, but now the screen doesn't work. It seems I can still get it to go to the bootloader since my computer detects it.
I might be able to get it to TWRP and then run the adb command again but right now, the screen is just blank.
Maybe I accidentally flashed the n6 unlock image instead of the n9 one?
Click to expand...
Click to collapse
Go to that thread and post your question. They are the experts, and VERY helpful. The OP is actually looking for someone like you to try this.
Discussion moved to http://forum.xda-developers.com/nex...enable-oem-unlock-t3113539/page6#post61042231
Thread closed as per OP request.
Is there any way to get a full image for "adb sideload", which doesn't depend on current system contents? I'm still locked, so I assume it would have to be signed from Google, but maybe this unicorn doesn't exist.
I'm in the marshmallow-brick club, desperately searching for solutions while I wait "7-10 days" for HTC escalation to get back to me. The LMY48T OTA apparently applied fine, but then MRA58K bricked me. I wasn't watching the update the whole time, just came back to see it stuck at the Google boot logo. I did a factory reset both from hboot and from recovery, still gets nowhere.
Recovery says I'm still on LMY48T. I tried to sideload MRA58K, and I get "system partition has unexpected contents". Since that check is part of the update script, I thought a mythical full-OTA wouldn't need to bother, but I'm probably grasping at straws.
I'm still OEM locked, and until now I didn't realize the full implications in "Developer options" of not enabling "OEM unlocking". How lovely. I'd be happy to blow it away with a factory image right now, but it seems there's no way...
What worked for me
I just sideload the Nexus 9 (WIFI) image from here: droid-life.com/2015/12/09/download-android-6-0-1-marshmallow-updates-for-nexus-devices
I was at 6.0.0 (MRA58N) according to the error messages I received when I tried to revert to lollipop. But, like you, the OTA update soft-briked my Nexus 9 which was working fine before on lollipop. I was just not aware that I had to OEM unlock it before the OTA update. Well...
The update process is long but it worked!
No more OEM-locked-endless-boot loop.
---------- Post added at 05:47 AM ---------- Previous post was at 05:43 AM ----------
Applying that image using adb sideload (while your device is locked) will erase all your data. I didn't find a way to not lose everything. On first boot, I was asked to provide my master password and did receive a message that my data is corrupted, then the device did a factory reset. On next reboot, was able to log on Google account, etc.
At least, my Nexus 9 will be working again!
If you are not an H918, H830, or US996 (Unlocked, NOT US Cellular) user, kindly leave this thread, this will not do anything for your device, exchange it if you're so desperate. Thank you.
Note for US996: It's probably easier for you guys just to flash TWRP the normal way and pull your battery then do the factory reset dance to get in!
Team Win Recovery Project 3.0.2-1
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
This will allow you to install TWRP and flash SuperSU!
Step 1: Unlocking your bootloader
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
H918/H830 users only:
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You will probably need to complete the Android setup wizard at this point to get access to ADB again.
US996 users only:
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Once you're finished with unlocking your bootloader, continue on to step 2.
Step 2: Running recowvery
You can find the recowvery binaries (you need to download all of these) at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow#running (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3: Flashing TWRP & Rooting
Notice: There is currently no decryption support, just the same as the LG G5, I'm running into the exact same scenario (unable to start rpmb device).
Due to this, I have disabled hardware decryption in this build to keep it stable. If you wish to have your data work in TWRP, you will need to disable decryption.
If you're coming from the Note 7 or S7, this will be a familiar scenario for you.
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, you can also just use adb push. (mentioned here)
Download TWRP: (official builds, V20 is waiting for TWRP 3.1.0 for twrp.me download)
H918: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
US996: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
H830: https://twrp.me/devices/lgg5h830.html
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU: https://download.chainfire.eu/supersu
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4: Have fun!
I know a few people have mentioned donating, there is a button right on this post under my username.
Sorry, I don't keep a list as I prefer to keep people's information confidential, but if you do send any money my way, you can request that I mention you at the bottom of this post with any details.
I ask that people please not attach files in this thread, everything required is mentioned in this post, and should be stable in its present state. Thank you.
Thanks for testing on my phone! =]
Does This wipe data on the phone?
justthefacts said:
Does This wipe data on the phone?
Click to expand...
Click to collapse
Unlocking the bootloader does.
jcadduono said:
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that I'm still working on getting TWRP to boot, there seems to be something about the stock kernel sources that doesn't want TWRP to be a part of it.
This will not get you SuperSU or app root access, this is only a root shell allowing you to flash TWRP when it's ready and do other things.
This does however open up some methods of installing SuperSU without TWRP. @Chainfire might have some ideas if he wishes to show up here and stir up some noise.
We do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for TWRP.
For the instructions on using recowvery, you should read the README.md on the GitHub page:
https://github.com/jcadduono/android_external_dirtycow
You can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, I'm really tired.
Click to expand...
Click to collapse
Thank you for taking the time to begin with the first step to develop on this device! (although i will have to do a replacement tomorrow for 2 defects that emerged on my phone) I always had in mind that this device had only a 50% of chances to get rooted, and that it might actually never get rooted . But now chances have increased even more thanks to your hard work. and also thanks to the others you previously mentioned. Let us see if Chainfire takes an interest on adding the final details :good:
I've got ADB working fine, but get nothing with fastboot. Just a blank line when I type 'fastboot devices'. Tried 3 different USB ports also. Windows 10 x64.
I did grab the ADB/fastboot files linked in the first post, but the older files I had don't work either, and they have no issues with my Nexus 7 2013 and HTC 10.
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
So Idk what to do or how to get the file to flash it.. Any help?
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
My advice? Never, ever take an update until the developers say that they are sure they can exploit it. From what I can see, this process uses the "dirty cow" exploit which will assuredly be fixed on the next security update.
---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------
bambam126 said:
So Idk what to do or how to get the file to flash it.. Any help?
Click to expand...
Click to collapse
Why not wait until they can get full root and TWRP? As I see it, this process is to help other developers and people that know what they're doing refine and advance the move to full root. I don't think it's quite ready for prime time yet. It does nothing but get the foot in the door for rooting.
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
And, we're off to the races. Let the "I bricked my phone" threads begin!
douger1957 said:
[/COLOR]And, we're off to the races. Let the "I bricked my phone" threads begin!
Click to expand...
Click to collapse
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Oh. Great to know. I hope they manage to do something with the verizon variants, in fact, with all the variants . Maybe after that they will have more interest on the device
jcadduono said:
alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over teamviewer thanks to @slayerh4x and @darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that i'm still working on getting twrp to boot, there seems to be something about the stock kernel sources that doesn't want twrp to be a part of it.
this will not get you supersu or app root access, this is only a root shell allowing you to flash twrp when it's ready and do other things.
this does however open up some methods of installing supersu without twrp. @chainfire might have some ideas if he wishes to show up here and stir up some noise.
we do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for twrp.
For the instructions on using recowvery, you should read the readme.md on the github page:
https://github.com/jcadduono/android_external_dirtycow
you can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
you will need to unlock your bootloader first. For this you'll probably need lg's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00120120425
mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00320110909
you will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
start by turning on developer options in settings -> about device -> software info -> build number. (tap 7 times until it's enabled)
now navigate to settings -> developer options -> oem unlock. (turn it on)
don't ever turn oem unlock or developer options off when using a custom rom or recovery. This could lose to loss of all your data.
For your computer to see adb, you will need to put the phone in ptp mode (for transferring images). I don't know why this is, a misconfiguration in lg's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your pc.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other usb ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
warning: This step will wipe all your data and factory reset your phone!
you can check the status of your bootloader lock with the fastboot getvar all command.
Ex. (bootloader) unlocked:yes
you should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
there's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, i'm really tired.
Click to expand...
Click to collapse
you are the man !!!!!!!!!!!!!!!!!!!!!!!
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
douger1957 said:
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
Click to expand...
Click to collapse
yup! i couldn't have written it better hahaha. But it is bound to happen for some people that will not pay careful attention. I mena, im not an expert, im maybe a little more than a noob now since i have been dealing with this for quite some time, and that is why i just started my C++ class in order to reach at least a good-to-go level of understanding.
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a H918 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Locked or unlock
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Oh, ye of little faith. Where there's a will, there's a way.
Chainfire just tweeted:
Just installed SuperSU on a V20, based on @jcadduono 's initial work. Good times.
Can this method be used on other devices?
Sent from my R1HD(ZenUI) via Tapatalk
Any guides to relocking bootloader and restoring to stock on EU version of V30 ?
Thanks in advance.
leicablue said:
Any guides to relocking bootloader and restoring to stock on EU version of V30 ?
Thanks in advance.
Click to expand...
Click to collapse
Should be as easy as using the "fastboot oem lock" command
leicablue said:
Any guides to relocking bootloader and restoring to stock on EU version of V30 ?
Thanks in advance.
Click to expand...
Click to collapse
Any reason you are doing this? The stock debloated, tweaked ROM in development section should give you all the features you need. You can also flash KZD without relocking bootloader.
LG still has a record that you unlocked your bootloader so it's not like they don't know.
ChazzMatt said:
Any reason you are doing this? The stock debloated, tweaked ROM in development section should give you all the features you need. You can also flash KZD without relocking bootloader.
LG still has a record that you unlocked your bootloader so it's not like they don't know.
Click to expand...
Click to collapse
Probably trying to prepare it for RMA
I’m thinking of selling it..Thanks for info.
leicablue said:
I’m thinking of selling it..Thanks for info.
Click to expand...
Click to collapse
Did you manage to relock the bootloader with the "fastboot oem lock" command (as it happens for other models)?
Thanks.
Yes, these are the commands i used to lock the bootloader again (note you have to setup the device again)
Code:
adb reboot bootloader
fastboot oem lock
fastboot reboot
what about the rom?
so when i do lock the bootloader, does the software get checked or updated or do I have to install it manually... what happens after i run all the commands in adb? Im currently on LineageOS 15.1 (LG-h930)
Question I ran fastboot oem lock and now I'm bricked with "your device has failed a routine safety check and will not boot" Does anyone have the fix for this?
MARKREIF said:
Question I ran fastboot oem lock and now I'm bricked with "your device has failed a routine safety check and will not boot" Does anyone have the fix for this?
Click to expand...
Click to collapse
You need to be on a stock KDZ(literally 0 changes) before locking. try booting to download mode by turning phone off and holding Vol+ and plugging into a computer. Then flash a stock KDZ.
thanks but slight problem is the device won't turn off.....
---------- Post added at 02:52 PM ---------- Previous post was at 02:48 PM ----------
ok I'm in firmware update and being seen via LGUP - can you point me in the direction of the latest stock KDZ?>
---------- Post added at 03:04 PM ---------- Previous post was at 02:52 PM ----------
LG UP keeps asking for an update DLL -any thoughts?
MARKREIF said:
thanks but slight problem is the device won't turn off.....
---------- Post added at 02:52 PM ---------- Previous post was at 02:48 PM ----------
ok I'm in firmware update and being seen via LGUP - can you point me in the direction of the latest stock KDZ?>
---------- Post added at 03:04 PM ---------- Previous post was at 02:52 PM ----------
LG UP keeps asking for an update DLL -any thoughts?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
20e is the latest KDZ for US998(i assume thats what you have considering thats what is in your Signature). Use the LGUP_common_DLL_V30_ALL_VARIANTS attachment(there is directions in that thread on how to use that DLL).
tried everything still having dll issues grrrr
---------- Post added at 04:06 PM ---------- Previous post was at 03:30 PM ----------
uninstalled all LG drivers etc rebooted windows 10 reinstalled "LGUP_Install_Ver_1_14_3 .msi" and LGUP_common_DLL_V30_ALLVARIANTS and I'm still getting "error 0x81000302, Please use latest DLL LAF Protocol version is not match DLL= 174187400 Device = 177360928" when i try to flash......
---------- Post added at 04:28 PM ---------- Previous post was at 04:06 PM ----------
Store version 1.14 - DLL Version 1.0.28.9
MARKREIF said:
tried everything still having dll issues grrrr
---------- Post added at 04:06 PM ---------- Previous post was at 03:30 PM ----------
uninstalled all LG drivers etc rebooted windows 10 reinstalled "LGUP_Install_Ver_1_14_3 .msi" and LGUP_common_DLL_V30_ALLVARIANTS and I'm still getting "error 0x81000302, Please use latest DLL LAF Protocol version is not match DLL= 174187400 Device = 177360928" when i try to flash......
---------- Post added at 04:28 PM ---------- Previous post was at 04:06 PM ----------
Store version 1.14 - DLL Version 1.0.28.9
Click to expand...
Click to collapse
Never seen that error. Maybe @ChazzMatt or @runningnak3d would know that one.
also at the bottom of the device screen instead of seeing device info I'm seeing 633A B100 on the top line and Modified / E /L / RO on the bottom
Happened to me as well. Do NOT use uppercut method, as it is not working on Oreo. Instead use lgup dev method. It is working.
As @kanehun stated, you must use the patched LG UP, and you must use partition DL mode (select all partitions) -- upgrade or refurbish won't work.
If you don't want to wipe your phone and just want to get it to boot again, only select recovery, boot and system and make sure that you are using the KDZ for the version that is on your phone. You should be able to salvage your data if you need to.
-- Brian
Does relocking the bootloader basically unroot the v30?
If not, is there a way of unrooting a US998?
charliebigpot said:
Does relocking the bootloader basically unroot the v30?
If not, is there a way of unrooting a US998?
Click to expand...
Click to collapse
If you JUST relock the bootloader you are going to cause LOTS of problems, UNLESS you first restore full stock firmware. Possibly even bricking your phone.
1) You want to flash stock KDZ via LGUP, which replaces TWRP custom recovery with stock Recovery.
Use "Refurbish" or "DL Partition". Then you no longer have root.
2) You can also relock the bootloader AFTER that -- if you wish to get rid of unlocked bootloader warning.
But step #1 will "unroot" your phone.
charliebigpot said:
Does relocking the bootloader basically unroot the v30?
Click to expand...
Click to collapse
Completely different operations.
Unlocking the bootloader allows custom software to run because partition signature checking is skipped. This is what allows flashing and running non-LG ROMs, custom recovery, etc.
Manufacturers don't want you doing this because it enables updating the device once it hits planned obsolescence; they want you to give them another $800+ at that point, not keep updating what you have.
An example I like to point out: the Motorola Droid 4 stopped being supported at android 4.3 (Jellybean). Thanks to Safestrap - the bootloader is permanently fused shut but an exploit allowed loading an entirely different kernel and ROM via kexec after the stock kernel startup- and some particularly determined developers, it's running up to 7.1 (Nougat). The kernel is ancient at this point and spackled together with pieces from Amazon devices, and the phone is a bit slow using a modern O/S because it only had 1gb of memory, but it still works and people still use it as a daily driver because they like it. Last CDMA landscape QWERTY phone and all.
Root privileges are part of Android itself; think of it a combination of Administrator and TrustedInstaller account privileges from a Windows PC.
Google doesn't want you rooting because of the myriad ways the average user can ruin their Android installation by screwing with system files, the many security implications (easy example: let the wrong app have root, now the app has access to any data on the phone it wants and can manipulate whatever it likes), and it making it a lot easier to do things like block ads system-wide.
TL;DR bootloader unlocking is more device-side that disables certain "security" checks to allow booting non-OEM software. Rooting is software-side, lets you use the Admin account in Android for any number of useful shenanigans. They are independent of one another, but depending on the method rooting can prevent a locked-bootloader device from booting.
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Info about the device
For some unknown reason, I can't upload photos, here is the device info:
Model number: SM-S327VL
Android version: 6.0.1
baseband version: S327VLUDS4ARF2
kernel version:
3.18.24-11771718
[email protected] #1
Mon Jun 11 11:55:20 KST 2018
Build number
MMB29M.S327VLUDS4ARF2
HenryGong2001 said:
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Click to expand...
Click to collapse
I have the exact same problem. This is as close as I have gotten to installing custom recovery in order to root my phone
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
I have the stock firmware if anyone needs it. It's the arf2 variety. Flashed it several times. Check hovatec if you want to find a root this year. I haven't found it yet but they are more active.
schrstopph said:
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
Click to expand...
Click to collapse
I think the problem could be that the bootloader is locked. I don't think there is a way to unlock it . I should be getting a new phone here soon, (Moto G6 that allows bootloader unlocking), so I will be able to test more freely with the SM-S327VL without worrying about bricking it.
schrstopph said:
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
I have the stock firmware if anyone needs it. It's the arf2 variety. Flashed it several times. Check hovatec if you want to find a root this year. I haven't found it yet but they are more active.
Click to expand...
Click to collapse
I need it.
I Want to put the newest Android version on my phone and I Need some help I tried 3 times.
My email: [email protected]
HenryGong2001 said:
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Click to expand...
Click to collapse
From what I know enabling oem unlock is only half of the issue. I assume you forgot the adb steps to perform the oem unlock commands.