Anyone know how to relock the bootloader, also if doing so is there a known way to keep data on the V20 while doing it?
depends on which device. if you used dirtysanta you need to use a kdz to restore it to stock(wipes data). not sure about tmo.
Pretty sure with TMO its
fastboot oem lock
fastboot flashing lock
fastboot oem relock
if you relock bootloader, it wipes the phone to stock
me2151 said:
depends on which device. if you used dirtysanta you need to use a kdz to restore it to stock(wipes data). not sure about tmo.
Click to expand...
Click to collapse
I used the KDZ to restore to stock and it still has an unlocked bootloader. So the phone is stock except that part.
SaintZ93 said:
Pretty sure with TMO its
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Click to expand...
Click to collapse
I may have to do this. I restored to stock for work due to security, and unfortunately now since I still have a unlocked bootloader, I loose other features like Android Pay, also Netflix is starting to block installs on devices like mine as well. So I need to get all the way back to stock.
You can use the LG backup to make a pretty solid backup of everything including home screens that you can restore when you're back to stock
bond32 said:
You can use the LG backup to make a pretty solid backup of everything including home screens that you can restore when you're back to stock
Click to expand...
Click to collapse
I might use that, since I had to use Carbonite when going from rooted to stock since I didn't have LG Backup. It sucked loosing a few things.
BrokenWall said:
I might use that, since I had to use Carbonite when going from rooted to stock since I didn't have LG Backup. It sucked loosing a few things.
Click to expand...
Click to collapse
I go back and forth all the time between stock/root access. Im just indecisive. I frequently use the LG backup, its nice. Still quite a bit to setup but it helps.
BrokenWall said:
I used the KDZ to restore to stock and it still has an unlocked bootloader. So the phone is stock except that part.
I may have to do this. I restored to stock for work due to security, and unfortunately now since I still have a unlocked bootloader, I loose other features like Android Pay, also Netflix is starting to block installs on devices like mine as well. So I need to get all the way back to stock.
Click to expand...
Click to collapse
Did you manage to get it back to completely stock?
Still_living714 said:
Did you manage to get it back to completely stock?
Click to expand...
Click to collapse
I mean I am completely stock as far as ROM goes, just need to relock, I have been too busy with work to do that portion
BrokenWall said:
I mean I am completely stock as far as ROM goes, just need to relock, I have been too busy with work to do that portion
Click to expand...
Click to collapse
Turn your phone off.
Hold Volume Down while plugging in USB cable.
Open Command Prompt, type 'fastboot oem lock'
Profit.
bond32 said:
I go back and forth all the time between stock/root access. Im just indecisive. I frequently use the LG backup, its nice. Still quite a bit to setup but it helps.
Click to expand...
Click to collapse
What does it restore that Google does not? Thanks
recDNA said:
What does it restore that Google does not? Thanks
Click to expand...
Click to collapse
LG Backup will restore all your settings, apps, internal storage, *and* app data. It's an invaluable tool. It uses a local file as opposed to cloud storage.
Murphy71984 said:
Turn your phone off.
Hold Volume Down while plugging in USB cable.
Open Command Prompt, type 'fastboot oem lock'
Profit.
Click to expand...
Click to collapse
thank you soooooo much its just fastboot oem lock no quotes worked perfectly by the way, now time for the note 8!
bond32 said:
You can use the LG backup to make a pretty solid backup of everything including home screens that you can restore when you're back to stock
Click to expand...
Click to collapse
Is there a way to use that on stock VZW LG'20?
capnloo said:
thank you soooooo much its just fastboot oem lock no quotes worked perfectly by the way, now time for the note 8!
Click to expand...
Click to collapse
Sorry, I meant to type no quotes lol. Have fun. The V30 is miles ahead of the V20 though. I love it.
Murphy71984 said:
Sorry, I meant to type no quotes lol. Have fun. The V30 is miles ahead of the V20 though. I love it.
Click to expand...
Click to collapse
I just thought if I saved v20 setup I could use it on some other LG phone in the future
Related
So i'm new to android but i continued to root my device. I did it the "legit" way. No tool kit. I installed drivers. ADB and used bootloader. I unlocked the bootloader when the dialog popped on my phone. I navigated and selected "unlock the bootloader" sideloaded clockworkmod touch. Installed supersu from sdcard. Booted up and i still have my pictures and i even found a folder on the phone from the gosms app I had. I know im properly rooted because i was able to flash paranoid rom 3 successfully. Everywhere i've been reading states unlocking the bootloader wipes everything! My question is this normal?
Its standard protocol made by Google. Yes its normal. Just remember if you have stuff on your storage to make sure you back up your storage before unlocking
Jsparta26 said:
Its standard protocol made by Google. Yes its normal. Just remember if you have stuff on your storage to make sure you back up your storage before unlocking
Click to expand...
Click to collapse
standard protocol but it didn't wipe...lol
BugJuice said:
standard protocol but it didn't wipe...lol
Click to expand...
Click to collapse
All you had to do is setup fast boot and use fast boot command fastboot oem unlock to unlock your bootloader. A message always comes up letting you knlw that unlocking bootloader erases your data. You didn't necessarily had to adb not to mention you went and side loaded a custom recovery. Guess you beat the system. Lol
Jsparta26 said:
All you had to do is setup fast boot and use fast boot command fastboot oem unlock to unlock your bootloader. A message always comes up letting you knlw that unlocking bootloader erases your data. You didn't necessarily had to adb not to mention you went and side loaded a custom recovery. Guess you beat the system. Lol
Click to expand...
Click to collapse
I unlocked my bootloader but it didn't wipe my data. But i didn't unlock it correctly and rooted.
BugJuice said:
I unlocked my bootloader but it didn't wipe my data. But i didn't unlock it correctly and rooted.
Click to expand...
Click to collapse
The same thing happened to me. Apparently this happens if you flash the recovery right after unlocking the bootloader. Rather than unlocking, rebooting into android, then flashing the recovery.
Read this for more info.
chromium96 said:
The same thing happened to me. Apparently this happens if you flash the recovery right after unlocking the bootloader. Rather than unlocking, rebooting into android, then flashing the recovery.
Read this for more info.
Click to expand...
Click to collapse
ahhh gotcha! Thats my exact situation. I did not load into android either. Just flashed the recovery immediately afterwards. Is there any negative effects of this?
BugJuice said:
ahhh gotcha! Thats my exact situation. I did not load into android either. Just flashed the recovery immediately afterwards. Is there any negative effects of this?
Click to expand...
Click to collapse
Yep. I was pretty confused too.
So far I havent had any issues and everything seems fine. I flashed superuser on stock rom, flashed CM10.1, and flashed PA and everything has gone smoothly. Its only been about a week though, so im not sure if anything will happen. But i highly doubt that it will cause anything negative to occur.
Hey guys, i've been looking at some different guides and ill be trying to root my N4 running 5.1.1 using that, just wanted to make sure it's legit:
ive installed the adb drivers from the 15 sec installer found here: http://forum.xda-developers.com/showthread.php?t=2588979
and root it using this guide: http://www.ibtimes.co.uk/how-root-nexus-5-4-android-5-1-1-lollipop-install-cwm-recovery-1502856 (except ill be using twrp not cwm)
(backed up apps and messages using helium app, assuming this process will wipe my data)
just wanted to make sure if this way is legit, or i may have missed something (i assume my bootloader is locked)
Pingas12 said:
Hey guys, i've been looking at some different guides and ill be trying to root my N4 running 5.1.1 using that, just wanted to make sure it's legit:
ive installed the adb drivers from the 15 sec installer found here: http://forum.xda-developers.com/showthread.php?t=2588979
and root it using this guide: http://www.ibtimes.co.uk/how-root-nexus-5-4-android-5-1-1-lollipop-install-cwm-recovery-1502856 (except ill be using twrp not cwm)
(backed up apps and messages using helium app, assuming this process will wipe my data)
just wanted to make sure if this way is legit, or i may have missed something (i assume my bootloader is locked)
Click to expand...
Click to collapse
That looks good, just make sure you understand that in the when you flash the recovery the command is "fastboot flash recovery *the file name of your recovery file*" make sure to include the .img in the file name.
EDIT: Make sure to remember to unlock your bootloader before flashing the recovery by using the command "fastboot oem unlock" after booting into the bootloader.
theminikiller said:
That looks good, just make sure you understand that in the when you flash the recovery the command is "fastboot flash recovery *the file name of your recovery file*" make sure to include the .img in the file name.
EDIT: Make sure to remember to unlock your bootloader before flashing the recovery by using the command "fastboot oem unlock" after booting into the bootloader.
Click to expand...
Click to collapse
Thanks alot man! Is there a way to make sure my bootloader is locked (or unlocked)?
Is it going to wipe my data?
Pingas12 said:
Thanks alot man! Is there a way to make sure my bootloader is locked (or unlocked)?
Is it going to wipe my data?
Click to expand...
Click to collapse
I don't know of any way to check if the unlock was successful, but I imagine it would say something in the command prompt after running the command.
Yes, it is going to wipe your data and sdcard folder so anything you want to keep you have to make a backup of on your computer or somewhere else.
EDIT: BTW this guide goes over the process in alot more detail than the guide you found and are using, so if you're still unsure about the process this guide will probably help. http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
theminikiller said:
I don't know of any way to check if the unlock was successful, but I imagine it would say something in the command prompt after running the command.
Yes, it is going to wipe your data and sdcard folder so anything you want to keep you have to make a backup of on your computer or somewhere else.
EDIT: BTW this guide goes over the process in alot more detail than the guide you found and are using, so if you're still unsure about the process this guide will probably help. http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
Click to expand...
Click to collapse
First of all, Thanks! again!
Second, i've seen this guide, and even though you are probably right, it still refers to older versions of android and im a bit skeptical about using it. Plus, it shows a way of unlocking and rooting without losing data but i don't want to use it because it's not the "normal" way and im not sure if it will work.
and one more thing: flashing the recovery means i will have it as long as i want or each time i would want to use it i will have to flash it again?
Pingas12 said:
First of all, Thanks! again!
Second, i've seen this guide, and even though you are probably right, it still refers to older versions of android and im a bit skeptical about using it. Plus, it shows a way of unlocking and rooting without losing data but i don't want to use it because it's not the "normal" way and im not sure if it will work.
and one more thing: flashing the recovery means i will have it as long as i want or each time i would want to use it i will have to flash it again?
Click to expand...
Click to collapse
In the guide I linked it gives you a way to make it permanent. If you don't do that I think you have to reflash the recovery after every time you boot into the normal ROM.
theminikiller said:
In the guide I linked it gives you a way to make it permanent. If you don't do that I think you have to reflash the recovery after every time you boot into the normal ROM.
Click to expand...
Click to collapse
Got it! does some of the ways apply to twrp as well?
Pingas12 said:
Got it! does some of the ways apply to twrp as well?
Click to expand...
Click to collapse
If you use either the file explorer method or the adb method just do the exact same thing.
theminikiller said:
If you use either the file explorer method or the adb method just do the exact same thing.
Click to expand...
Click to collapse
Man, you helped me alot. i'll do the rooting process later today (just got home) I really appreciate your help.
Pingas12 said:
Man, you helped me alot. i'll do the rooting process later today (just got home) I really appreciate your help.
Click to expand...
Click to collapse
How did it go?
it shows a way of unlocking and rooting without losing data
theminikiller said:
How did it go?
Click to expand...
Click to collapse
It went great! today ill be busy restoring old data, already worked with whatsapp but for some reason the helium app cant find the backup files and it assumes there is no backup
Pingas12 said:
It went great! today ill be busy restoring old data, already worked with whatsapp but for some reason the helium app cant find the backup files and it assumes there is no backup
Click to expand...
Click to collapse
Great! Congratulations! Unfortunately I've never used helium so I don't know anything about that, I've always used titanium.
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
I was poking security options within my phone, and I accidentally locked it with a pattern that I cannot recall.
I tried looking for troubleshooting guides, but unfortunately Marshmallow no longer has a "forgot code?" option. Also, I tried Android Device Manager, but it tells me since my phone already has a lockscreen, I no longer need to add a password (which I intended to do, in order to know said password)
I would greatly appreciate any help, since I really don't want to factory reset, since I got lots of pics I don't want to lose.
xdmatt said:
I was poking security options within my phone, and I accidentally locked it with a pattern that I cannot recall.
I would greatly appreciate any help, since I really don't want to factory reset, since I got lots of pics I don't want to lose.
Click to expand...
Click to collapse
google is your friend http://www.addictivetips.com/android/how-to-bypass-disable-pattern-unlock-on-android-via-adb-commands/
edit: this does not work on marshmallow[tested]
i think this will help you http://forum.xda-developers.com/note-4/orig-development/bypass-lock-screen-pattern-password-pin-t2948336
bablu048 said:
google is your friend http://www.addictivetips.com/android/how-to-bypass-disable-pattern-unlock-on-android-via-adb-commands/
Click to expand...
Click to collapse
hopefully he enabled the usb debugging option
pijes said:
hopefully he enabled the usb debugging option
Click to expand...
Click to collapse
nope, this does not help. Just now i tried this on my device..if the device is locked adb doesn't recognize the device. this method does not work on marshmallow.
i don't know about lollipop. maybe it works.
pijes said:
hopefully he enabled the usb debugging option
Click to expand...
Click to collapse
bablu048 said:
nope, this does not help. Just now i tried this on my device..if the device is locked adb doesn't recognize the device. this method does not work on marshmallow.
i don't know about lollipop. maybe it works.
Click to expand...
Click to collapse
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
xdmatt said:
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
Click to expand...
Click to collapse
you don't need to be rooted to access recovery and install files.
for future reference see the 2nd link i posted. I haven't tried that yet, i'l report when i try.
bablu048 said:
you don't need to be rooted to access recovery and install files.
for future reference see the 2nd link i posted. I haven't tried that yet, i'l report when i try.
Click to expand...
Click to collapse
He wouldn't have been able to use it because you need a custom recovery to flash that file.
Well... I guess you know the system works? Probably not great for there to be an easy or sure-fire way to unlock a phone if you don't know the security details.
If it's just data you need, recovery mode should allow you to copy it off the device via USB (if you didnt encrypt the device). Getting into a phone you really locked yourself out of is probably not possible.
AtomicStryker said:
If it's just data you need, recovery mode should allow you to copy it off the device via USB (if you didnt encrypt the device). Getting into a phone you really locked yourself out of is probably not possible.
Click to expand...
Click to collapse
i want to know how to copy data from the device through recovery. do you know the process or where to find a guide?
edit: thanks for the idea. i hadn't thought that way.
xdmatt said:
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
Click to expand...
Click to collapse
For preventative measures, Tasker is your friend. Have a "Plan B" microSD with a special .txt file on it, and have Tasker detect SD inserted and scan that file. If the file matches, then Tasker should wipe /data/system/gesture.key and password.key, and sqlite3 into settings.db and "update system set value=0 where name='lock_pattern_autolock' " to unlock your device.
In the case of an aftermath, it is now (as of today) possible to recover files/photos from the lockscreen without root, ADB, or custom recovery. Just an internet connection, linked Google account, and access to the notification drawer. I just published my first app, Locked-out Phone Backup, that is similar to the old Screen Lock Bypass Pro for Gingerbread, but instead recovers files instead of disabling the screen lock, so no root is required!
Hope this answers your question!
Well, try some password remover.
I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!
williamvito said:
I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!
Click to expand...
Click to collapse
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method
me2151 said:
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method
Click to expand...
Click to collapse
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
Click to expand...
Click to collapse
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?
williamvito said:
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?
Click to expand...
Click to collapse
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
You're the man, thanks for the quick reply! I will give this another go tomorrow.
me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?
williamvito said:
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?
Click to expand...
Click to collapse
Once youve started the dirtysanta method it installs a new bootloader. you can access bootloader(fastboot) by holding VOL- and plugging iin the phone when powered off