{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello folks,
this is regarding a question that does seem to pop up just ever and ever again, with the respective developer teams, developers and tester over in the ROM and development section, seemingly, having to answer it always and again. By this the respective question has been answered at least a hundred times by people like e.g. Captain_Throwback, j to the 4n, nkk71, topjohnwu, LeeDrOiD, Llabtoofer and many other I'm - to keep the matter brief at this point - gonna leave uncredited. If anyone wants me to credit im personally please let me know via PM. I'll in such a case add his/her name to the credits section below.
What I did was just carrying together the needed information. All of it has been written prior to this, on various threads. Always by one the above mentioned and/or others. Anyway I'll give the steps again in this short tutorial as I think it is of importance to many to be able to find a solution to their problem right at the top of a quick thread. In addition such guides were really helpful to me in the past, learning about how Android works. Thus I decided to open up yet another thread.
If you - just like me - have set a lock pattern or password on your device, and you did a TWRP backup as long as the pattern has been set, you might - especially restoring different ROMs - be confronted by a little problem where after the HTC 10 boots up you cannot unlock it even if you enter the correct lock pattern/pin/password.
Well then this thread is about how you can fix it.
Method 1 - TWRP FileManager
boot to recovery
reboot to bootloader
reboot to recovery
In TWRP, go to "Advanced" > "File Manager"
In TWRP File Manager, go to /data/system folder
Find and delete the following files:
Code:
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone/tablet back into the ROM. Now you should be able to just swipe the lock screen and get into the launcher screen. You can then set a new lock from the Settings, if you want.
Method 2 - TWRP Terminal
boot to recovery
reboot to bootloader
reboot to recovery
In TWRP, go to "Advanced" > "Terminal"
Type the following commands:
Code:
cd /data/system
rm -f locksettings*
rm -f *.key
Method 3 - TWRP Flash of "lockjscreen_removed_signed.zip
Download the zip provided by @JohnFawkes in Post #5
Place downloaded zip onto your device
boot to recovery
reboot to bootloader
reboot to recovery
In TWRP, flash the downloaded zip
THANKS TO ALL DEVELOPERS AND DEVELOPER TEAMS, AS WELL AS THEIR TESTERS!
THEY FOUND OUT AND PRESENTED US WITH THE SOLUTION.
XDAevDB Information
PIN/PATTERN/PASSWORD not recognised after TWRP restore
Contributors
All referred to in Credits, 5m4r7ph0n36uru (OP Leader)
Shouldn't only deleting locksettings.db suffice?
It might do. But it'd be much safer to delete all, as it then works on all kind of devices
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
hello folks,
this is regarding a question that does seem to pop up just ever and ever again, with the respective developer teams, developers and tester over in the rom and development section, seemingly, having to answer it always and again. By this the respective question has been answered at least a hundred times by people like e.g. Captain_throwback, j to the 4n, nkk71, topjohnwu, leedroid, llabtoofer and many other i'm - to keep the matter brief at this point - gonna leave uncredited. If anyone wants me to credit im personally please let me know via pm. I'll in such a case add his/her name to the credits section below.
What i did was just carrying together the needed information. All of it has been written prior to this, on various threads. Always by one the above mentioned and/or others. Anyway i'll give the steps again in this short tutorial as i think it is of importance to many to be able to find a solution to their problem right at the top of a quick thread. In addition such guides were really helpful to me in the past, learning about how android works. Thus i decided to open up yet another thread.
If you - just like me - have set a lock pattern or password on your device, and you did a twrp backup as long as the pattern has been set, you might - especially restoring different roms - be confronted by a little problem where after the htc 10 boots up you cannot unlock it even if you enter the correct lock pattern/pin/password.
Well then this thread is about how you can fix it.
method 1 - twrp filemanager
boot to recovery
reboot to bootloader
reboot to recovery
in twrp, go to "advanced" > "file manager"
in twrp file manager, go to /data/system folder
find and delete the following files:
Code:
locksettings.db-wal
locksettings.db-shm
locksettings.db
reboot the phone/tablet back into the rom. Now you should be able to just swipe the lock screen and get into the launcher screen. You can then set a new lock from the settings, if you want.
method 2 - twrp terminal
boot to recovery
reboot to bootloader
reboot to recovery
in twrp, go to "advanced" > "terminal"
type the following commands:
Code:
cd /data/system
rm -f locksettings*
rm -f *.key
thanks to all developers and developer teams, as well as their testers!
They found out and presented us with the solution.
xda:devdb information
pin/pattern/password not recognised after twrp restore
contributors
all referred to in credits, 5m4r7ph0n36uru (op leader)
Click to expand...
Click to collapse
this really really saved my life!!!! :d:d:d
You can add this to OP if you want. But you can just flash this zip and it will delete the files automatically
Or you could just take password or swipe pattern off phone before doing full nandroid. That's what I did haven't had to restore yet, but I'm sure might work. ?
I managed to get phone unlocked using this method. However, when i try to add new pattern lock, same thing happened. The pattern saved is not the pattern i registered.
zhuhang said:
I managed to get phone unlocked using this method. However, when i try to add new pattern lock, same thing happened. The pattern saved is not the pattern i registered.
Click to expand...
Click to collapse
Flash the zip above my last post. Works like a charm
I am running into a similar issue after updated my HTC 10 to Oreo. After installing the system update it rebooted itself twice, then asked me for a lock screen pattern and I put in mine (and I am absolutely sure it's correct) but it rejected it, saying I have 29 more attempts before device data is deleted.
I don't have TWRP installed, is factory reset the only option? and will a factory reset take it back to the original Android 7 or the new Oreo 8?
Hello 5m4r7ph0n36uru, can you tell me...
If I follow your guide, eill this delete everything on my phone, photos, messages.
My problem is that I forgot the pattern required after restarting phone.
Thank you kindly, Dusty.
Dustymone said:
Hello 5m4r7ph0n36uru, can you tell me...
If I follow your guide, eill this delete everything on my phone, photos, messages.
My problem is that I forgot the pattern required after restarting phone.
Thank you kindly, Dusty.
Click to expand...
Click to collapse
There is no mentioning about losing data at all in the OP and the commands only show that they delete lockscreen password files so no you will not lose data.....
mattie_49 said:
Flash the zip above my last post. Works like a charm
Click to expand...
Click to collapse
I did flashed that zip and setup the password to phone and rebooted to twrp, there again i could see the pattern on twrp.
Thank you very much it has worked on my LG G6 H870 !! with Orangefox as recovery
Scenario: Let's say I have a smartphone with both configured, PIN and Pattern. Default would be Pattern, backup method would be PIN. And I don't know the PIN.
Question: Is it possible to remove only the .key files (using TWRP) that are responsible for the PIN but keep the Pattern protection active? After reboot, there would still be the Pattern protection but when switching to PIN, the (new) PIN would be empty.?
Or alternatively, would it also be feasible to REPLACE only the .key files that are responsible for the (unknown) PIN with other .key files of a known PIN and at the same time, keep the default Pattern protection intact?
IrenePappel said:
Scenario: Let's say I have a smartphone with both configured, PIN and Pattern. Default would be Pattern, backup method would be PIN. And I don't know the PIN.
Question: Is it possible to remove only the .key files (using TWRP) that are responsible for the PIN but keep the Pattern protection active? After reboot, there would still be the Pattern protection but when switching to PIN, the (new) PIN would be empty.?
Or alternatively, would it also be feasible to REPLACE only the .key files that are responsible for the (unknown) PIN with other .key files of a known PIN and at the same time, keep the default Pattern protection intact?
Click to expand...
Click to collapse
Once you remove the PIN and Pattern you will be able to boot into the system and set up the PIN and Pattern however you'd like. No need to mess with the files directly.
5m4r7ph0n36uru said:
boot to recovery
reboot to bootloader
reboot to recovery
In TWRP, go to "Advanced" > "File Manager"
In TWRP File Manager, go to /data/system folder
Find and delete the following files:
Code:
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone/tablet back into the ROM. Now you should be able to just swipe the lock screen and get into the launcher screen. You can then set a new lock from the Settings, if you want.
Click to expand...
Click to collapse
You save me from a factory reset, i flash the aicp_zl1_p-14.0-WEEKLY-20190627.zip update and i was getting blackscreen after putting pin, now works ok
My problem is weird
After rooting,I have kept a lockscreen pattern,then it shows incorrect pattern even I drawn correctly. I flashed that above zip and lock was bypasses,then I tried again keeping PIN lock,same problem again,shows incorrect PIN even I entered correct pin
Neelakanta tech said:
After rooting,I have kept a lockscreen pattern,then it shows incorrect pattern even I drawn correctly. I flashed that above zip and lock was bypasses,then I tried again keeping PIN lock,same problem again,shows incorrect PIN even I entered correct pin
Click to expand...
Click to collapse
This is what I would do personally, and do frequently when using multirom when on N firmware and restore a backup that has a pin.
From the xda HTC 10 twrp FAQ.
"while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone."
I find that just deleting the single locksettings.db file is enough for me to remove the pin/password or pattern, and keeps the fingerprints stored. This way I can still use my fingerprints to log into apps, but have no pin or anything to unlock phone.
Yup,I have enabled pattern now,my pattern and pin working fine. I got a Zip file named enable_encryption from Realme unofficial developers. Then I flashed it in TWRP , my problem fixed
Neelakanta tech said:
Yup,I have enabled pattern now,my pattern and pin working fine. I got a Zip file named enable_encryption from Realme unofficial developers. Then I flashed it in TWRP , my problem fixed
Click to expand...
Click to collapse
always risky flashing zip for another device.
glad it worked though
Related
Guys,
my OP3 is bootloader unlocked, rooted and encryption switched off.
Standard system was OOS 3.1.2. I installed the update to 3.2.1 via TWRP zip and found some bugs, so I decided to use the [ROM] [6.0.1] Unofficial CyanogenMod 13
from Grarak. Did a full wipe installed and all is ok. Now comes the strange thing:
I wanted to restore the original backup and it worked. When I rebooted, the system asks me for the SIM card sim and then the system says:
"for the new start of the device you need to enter the pin"
The ony pin I ever used for the card and not knowingly for the device doesn't work.
Neitehr 0000 nor 1234 works. Which means I can't restore the nand backup.
Does anyone have an idea what this behaviour is and how to work around?
That is normal before doing a Nandroid u have to delete the pin, there exist a way around it deleting ur pin keys in trwp, its listed on this site somewhere
Bradl79 said:
That is normal before doing a Nandroid u have to delete the pin, there exist a way around it deleting ur pin keys in trwp, its listed on this site somewhere
Click to expand...
Click to collapse
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
Thanks for sharing I wasn't aware and had to wipe my phone twice.
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
Where in twrp do I have to enter the pincode ? After I choose to restore ? Is that all or do have to delete the files also when I have twrp ?
magnum73 said:
Where in twrp do I have to enter the pincode ? After I choose to restore ? Is that all or do have to delete the files also when I have twrp ?
Click to expand...
Click to collapse
Good question. I did also look for the pin entry, but haven't found. Was also not necessary maybe because I had switched off encyption earlier. I just deleted the namend files (which were for me only the locksetting files).
After that rebooted to system and everything works fine. Once you did that, better create a new backup without the fingerprint installed and you're safe next time.
Can u back it up and then do a restore from ur nandroid and restore files, I use multi fingerprints and have my gf on there also I hate resetting things up
I know this is what I need to do. I just can't find these files anywhere. Guess I have to start from scratch.
?
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
THANK YOU SO MUCH! I just got stuck between ROMs and used my nandroid backup but could not get past the lock screen.
Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Valeeeu dms irmao, ajudou dmss
Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).
Hello dev's! Unfortunately, in January, my brother passed away, and I have been tasked with trying to get into his phone and recover any important images really to pass along to his wife and daughter. Needless to say, I don't know his PIN code - and I am down to 2 guesses before the phone is wiped. So here I am.
Pardon my lack of technical language here but my brother did install Team Win Recovery Project 3.1.1-0 so I have been able to get to "recovery mode". Unfortunately, his partition is encrypted and I have been unable to guess that password either.
Because his drive is encrypted, I can't get into /data to remove any .key files. I have successfully been able to figure out how to sideload zip files via ADB that are supposed to bypass the PIN screen but I have had no luck. The google "find my phone" method is not working probably because the phone isn't connecting to a network.
I have read through an alpha security post about a malicious charger hack but I don't see where to download that tool.
So - does anyone know of any possible application or ZIP file I can sideload that will either help remove the decryption password or completely and successfully bypass the PIN?
Can I update TWRP to a newer version in hopes that the encryption is removed?
Any help is appreciated!
FWIW, my brother was on these forms as Colomonster - and I know that he loved tinkering with his phone daily.
There's no efficient way of breaking the data partition if it's encrypted, sorry.
Any old version of twrp might do the trick and then in /data/system folder delete these files ( if they are there )
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
@catsruul I figured this would be the case but it does look like I get inifinite guesses, so there’s always that
@cpt.macp thanks for this tip! Can I downgrade via sideloading? I’ll have to look up a tutorial.. thanks!
You said any important photos correct?
https://support.google.com/accounts/troubleshooter/6357590?hl=en
I assume that your brother used Google Photos and any photos he took were most likely backed up to that. You can talk to Google about retrieving said data, you will need to prove things of course though. You will need to get a court order issued, that is if it is even approved, and everything else required should be on that page. Best of luck! Sorry to say but if the /data is encrypted you are pretty much screwed, although TWRP should decrypt in when it enters recovery so idk. That webpage is your best shot imo.
thanks @ZVNexus for the tip. I do have access to his Google account but because my brother was a super sleuth, he didn't have his images automatically upload to his photo drive. the photos that are there are few and from 2015
With access to his account, I do see his "activity", which I am not even sure he knew was being tracked (oh Google!) and I see that he used things like
Code:
Used com.android.gallery3d
and
Code:
Used org.cyanogenmod.snap
both of which look like photo apps.
you mentioned that TWRP should decrypt when I enter recovery.. what do you mean by that? if it is encrypted then it should always ask for a password right?
I wonder if this app is available anywhere for download and use.
HTML:
https://alephsecurity.com/2017/03/26/oneplus3t-adb-charger/
Lonoshea said:
thanks @ZVNexus for the tip. I do have access to his Google account but because my brother was a super sleuth, he didn't have his images automatically upload to his photo drive. the photos that are there are few and from 2015
With access to his account, I do see his "activity", which I am not even sure he knew was being tracked (oh Google!) and I see that he used things like
Code:
Used com.android.gallery3d
and
Code:
Used org.cyanogenmod.snap
both of which look like photo apps.
you mentioned that TWRP should decrypt when I enter recovery.. what do you mean by that? if it is encrypted then it should always ask for a password right?
I wonder if this app is available anywhere for download and use.
HTML:
https://alephsecurity.com/2017/03/26/oneplus3t-adb-charger/
Click to expand...
Click to collapse
I meant that even if the chip was encrypted TWRP should have let you touch the data partition. My phone is also encrypted but TWRP allows me to touch those partitions. Strange. Hopefully others can help.
Lonoshea said:
Hello dev's! Unfortunately, in January, my brother passed away, and I have been tasked with trying to get into his phone and recover any important images really to pass along to his wife and daughter. Needless to say, I don't know his PIN code - and I am down to 2 guesses before the phone is wiped. So here I am.
Pardon my lack of technical language here but my brother did install Team Win Recovery Project 3.1.1-0 so I have been able to get to "recovery mode". Unfortunately, his partition is encrypted and I have been unable to guess that password either.
Because his drive is encrypted, I can't get into /data to remove any .key files. I have successfully been able to figure out how to sideload zip files via ADB that are supposed to bypass the PIN screen but I have had no luck. The google "find my phone" method is not working probably because the phone isn't connecting to a network.
I have read through an alpha security post about a malicious charger hack but I don't see where to download that tool.
So - does anyone know of any possible application or ZIP file I can sideload that will either help remove the decryption password or completely and successfully bypass the PIN?
Can I update TWRP to a newer version in hopes that the encryption is removed?
Any help is appreciated!
Click to expand...
Click to collapse
I'm confused: if the partition is encrypted, you will generally be asked for a password during the boot process. If you're unable to enter the correct password (which AFAIK has unlimited tries), the phone simply won't boot. So you will never arrive at the lockscreen where you're supposed to enter the PIN (which offers a number of tries before wiping). With an encrypted partition, entering the recovery will prompt you for the same password you're supposed to enter during the boot process. Again, unlimited tries. As long as you're unable to do that the partitions will be 'invisible'. You can still wipe/partition them and that will remove the encryption as well as all of your data. But it seems the device you're working on works differently?
Either way: in order to gain access, you will need to either know the PIN directly (if the phone boots without a boot password) or gain access to the encrypted partition through TWRP, allowing you to remove the files responsible for the PIN lock. I'm sorry for your loss, but if it would work in any other way it simply wouldn't be secure for any Android user out there who is using encryption. Even google shouldn't be able to decrypt the phone, though it's theoretically possible they do have some kind of backdoor.
At this point, your best bet is probably trying to brute force the partition password. That would probably take a very long time, but I'm sure there's tools and organizations specializing in that sort of work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is Cypher. An extension to pure Android. Cypher tries maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving Simplicity.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
**** These builds are for UsU'd devices only ****
UsU? http://bit.do/unlockg4
Get your builds from my leech service
http://leech.binbash.rocks:8008/aoscp/nougat/h815-UsU/
Note: Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Become apart of our G+ community - JOIN
REMINDER
If you're having issues and want to submit a report (Logcat) please make sure you are reporting from the stock kernel, not a modified kernel. Modified kernels can break or fix, even improve things. It depends. I can't get a full clue of the issue when you're not running the original kernel.
Click to expand...
Click to collapse
Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
- Specials
- UsU compatible build so no need for a baseband package to be flashed!
- Using latest TITAN kernel sources
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable N modem (recommended)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash AOSCP
Flash GApps (7.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Credits
LineageOS
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
kessaras
steadfasterX
and more..
Sources
Kernel
device tree
reserved 1
reserved 2
Error Status 7
Using lastest TWRP preview, I get the above error.
I know to fix it I just need to delete the "assert" line in the .zip, but I thought this ROM (UsU's supported) had the model that TWRP show.
I mean, the model according to;
(*) TWRP: LGUSU
(*) ROM (assert): p1, h815, h815_usu & g4 (not 'LGUSU' as shown in TWRP).
Thanks!
the_naxhoo said:
Error Status 7
Using lastest TWRP preview, I get the above error.
I know to fix it I just need to delete the "assert" line in the .zip, but I thought this ROM (UsU's supported) had the model that TWRP show.
I mean, the model according to;
(*) TWRP: LGUSU
(*) ROM (assert): p1, h815, h815_usu & g4 (not 'LGUSU' as shown in TWRP).
Thanks!
Click to expand...
Click to collapse
correct the removal of that line is not needed but i can see that the model detection is wrong on your device.
Please share the recovery log file!
Sent from my LG-H815 using XDA Labs
steadfasterX said:
correct the removal of that line is not needed but i can see that the model detection is wrong on your device.
Please share the recovery log file!
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
OK. Here is the recovery.log
ROM works great. Very smooth with no bloatware.
Just one problem, when setting the lockscreen type in security it doesn't seem to apply correctly. I have set it to "pattern" but it keeps defaulting back to swipe. I then tried to set it to PIN and it just crashes when I go back into lock screen settings now.
the_naxhoo said:
OK. Here is the recovery.log
Click to expand...
Click to collapse
ok the reason is clear:
download: https://androidfilehost.com/?fid=746010030569958479
extract it
flash in fastboot:
Code:
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
Then boot into TWRP again and share the recovery log again.
Rich Rich said:
ROM works great. Very smooth with no bloatware.
Just one problem, when setting the lockscreen type in security it doesn't seem to apply correctly. I have set it to "pattern" but it keeps defaulting back to swipe. I then tried to set it to PIN and it just crashes when I go back into lock screen settings now.
Click to expand...
Click to collapse
seems to be a known issue for some rare cases.
I cannot reproduce it here it works fine so far.
Have you clean flashed ? Format(!) data as written in the OP?
steadfasterX said:
ok the reason is clear:
download: https://androidfilehost.com/?fid=746010030569958479
extract it
flash in fastboot:
Code:
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
Then boot into TWRP again and share the recovery log again.
Click to expand...
Click to collapse
lol its worked... thx!
steadfasterX said:
seems to be a known issue for some rare cases.
I cannot reproduce it here it works fine so far.
Have you clean flashed ? Format(!) data as written in the OP?
Click to expand...
Click to collapse
Yes, did the "format data" wipe before install.
It may be a slight difference in the way I set the device up. I did select "pattern lock" when I first installed the OS. I noticed this was not working then re-set "pattern lock" in settings a few times but nothing worked. I then tried setting it to "pin lock" and now it just crashes the settings app every time I try to change the security.
It's not a big issue for me as the G4 is just used as a work phone. I'll flash the next build when available and see if that sorts the problem.
Rich Rich said:
Yes, did the "format data" wipe before install.
It may be a slight difference in the way I set the device up. I did select "pattern lock" when I first installed the OS. I noticed this was not working then re-set "pattern lock" in settings a few times but nothing worked. I then tried setting it to "pin lock" and now it just crashes the settings app every time I try to change the security.
It's not a big issue for me as the G4 is just used as a work phone. I'll flash the next build when available and see if that sorts the problem.
Click to expand...
Click to collapse
oh well i have tried PIN only.. sorry havent read carefully. will try the pattern thing..
Hello thanks for all of your efforts I follow your toppic for long time and finally yesterday I unlocked my h815tr device successfully. And I flash the ROM you shared in this topic. All works fine thanks again. I just have a problem about Yahoo mail account. I can't add it to my Gmail app. I enter my mail and password I allow the permissions about mail and at final step screen shows 404 can't found. But I solve this by using Yahoo's mail app. But it would be good if I can use Gmail app. And I realised that if I take a photo and immediately if I tap to photo I took the camera app crash but if I wait few seconds and then if I tap the photo it's all ok. I'm not complaining don't get me wrong, again thank you so much.
Is this ROM support quick charge? Because when I plug to QC adapter, phone says slow charging. Original adapter says slow charging also
emrtnl said:
Is this ROM support quick charge? Because when I plug to QC adapter, phone says slow charging. Original adapter says slow charging also
Click to expand...
Click to collapse
slow charging is everywhere due to power hal and due to our sources.
In the rom to show if its fast normal or slow it needs to read the voltage not the ampere. but in kernel we read no voltage. we only read the ampere.
Totally stupid since its the ampere that matters , but thats how things work there.
EDIT:
i mean it's always showing slow for the reason i explained , but it's not.
kessaras said:
slow charging is everywhere due to power hal and due to our sources.
In the rom to show if its fast normal or slow it needs to read the voltage not the ampere. but in kernel we read no voltage. we only read the ampere.
Totally stupid since its the ampere that matters , but thats how things work there.
EDIT:
i mean it's always showing slow for the reason i explained , but it's not.
Click to expand...
Click to collapse
Thanks for that information. At v29 ROM previously I use I could see quick charging notification, that's why I asked.
emrtnl said:
Thanks for that information. At v29 ROM previously I use I could see quick charging notification, that's why I asked.
Click to expand...
Click to collapse
stock lg stuff handle many things differently from the open source.
but we do not have access there, only LG has.
What we do in this side of development is to work with the open source.
LG rom may read the ampere. Or they may have added a voltage reading. We do not know...
have done all steps but reboot into twrp always (((
floast said:
have done all steps but reboot into twrp always (((
Click to expand...
Click to collapse
I had the same problem.
While in TWRP go to Advanced, then select Terminal
type this command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
keep in mind that there's a space before if and before of, like below replaced with underscores:
dd_if=/dev/zero_of=/dev/block/bootdevice/by-name/fota
If you don't get an error, just reboot the phone and it will go into the system.
I found this solution here and adjusted it a bit:
https://forum.xda-developers.com/showthread.php?t=2451696
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
#EDIT: Ok, so funnily enough, me helping the guy above also risked having him screw his mac address up the same way I describe as a separate problem below Looks like we need to adjust he process below to our model:
https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12
Sorry for being clumsily underqualified, everyone.
#EDIT2: A better and easier solution that might work for us:
https://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And now my own problem. I cannot connect to any WiFi network and noticed that my mac address is 00:00:00:00:00:00.
I stays that way even if I do the whole process again: format data, flash the rom, flash the gapps, flash supersu.
After I reboot into the system and wait for it to initialise and enter the initial phone config, where it asks me to connect to a WiFi network I can see my zeroed out mac address at the bottom. If I try to connect to a 5G wifi network or 2.4G one it says "Connecting" and then just displays "Saved" under the selected network. It doesn't ever connect. I checked one 5G network and two different 2.4G networks, triple-checking the password each time.
In "settings>about phone>status>WiFi MAC address" I also see 00:00:00:00:00:00.
I checked /system/etc/wifi/bcmdhd.cal file and the attribute there seems normal:
Code:
macaddr=00:90:4c:c5:12:38
I've seen in a thread concernig a different phone that some people advise to put the desired mac address into a /system/etc/wifi/.mac_info file and reboot but this doesn't work (might be dumb to even try that but it didn't hurt so I gave it a shot).
I wanted to try working around the issue using a mac address changer app off of Play Store but I can't connect to any Google Account (in the settings or any Google app), even on the cellular data - seems like the authentication looks at my mac and doesn't like it.
I considered finding and sideloading an apk of some mac address changer app, but that's doesn't seem like a viable solution - people say it only works temporarily and I'm not even sure if that will fool Play Store authentication if it really does rely on mac add somehow.
Any ideas where else the system might be pulling that 00:00:00:00:00:00 from or where the mac is missing?
Does fixing the mac issue might also fix the Google Services authentication problem?
Derpthunder said:
I had the same problem.
While in TWRP go to Advanced, then select Terminal
type this command:
keep in mind that there's a space before if and before of, like below replaced with underscores:
dd_if=/dev/zero_of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/fota
Also, the soc.0/f9824900.sdhci/ part might be different in your case. If after typing the above command you'll get an error saying that there's no such file, type these commands:
And it will tell you if you have soc.0 or something else. Then type (if you had something else than soc.0 in the previous step, replace soc.0 with what it told you)
and you'll see what you have instead of f9824900.sdhci
Once you know what you have instead of soc.0/f9824900.sdhci/, just type that command again replacing that section:
If you don't get an error, just reboot the phone and it will go into the system.
I found this solution here and adjusted it a bit:
https://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
That's why
/dev/block/bootdevice/by-name/
exists. It's always pointing to the correct SOC path.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
That's why
/dev/block/bootdevice/by-name/
exists. It's always pointing to the correct SOC path.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Thanks, I edited the post to add the correction.
#EDIT: I don't quite remember if I actually overwrote the fota or the misc to get out of booting into TWRP loop. The G2 and G5 threads advise to overwrite the misc and the G3 one to overwrite fota. Is there a difference?
Plus, I added this since it turned out that my mac problem was due to that exact fix I recommended:
Derpthunder said:
#EDIT: Ok, so funnily enough, me helping the guy above also risked having him screw his mac address up the same way I describe as a separate problem below Looks like we need to adjust he process below to our model:
https://forum.xda-developers.com/sho...0&postcount=12
Sorry for being clumsily underqualified, everyone.
#EDIT2: A better and easier solution that might work for us:
https://forum.xda-developers.com/lg-...g-ota-t2907508
Click to expand...
Click to collapse
Hey guys, i have tested the new method posted by g96818 and it works perfect.
Since he has more experience than me with OnePlus rooting I'll delete this post soon.
My fear is the future proofing of my method and i understand that his method is better in the case of future updates and less risky.
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
hitzzzzzzzz said:
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
Click to expand...
Click to collapse
Hey man, but there is a full OTA for that, you just need to subtract the info you need from it.
Since i dont have that device, i dont want to tell you what to do.
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
scott.hart.bti said:
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
Click to expand...
Click to collapse
Yeah that's true that would be nice.
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
scottlam1 said:
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
Click to expand...
Click to collapse
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
blasbenoit said:
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me and other guys in this forum.
Important notes to consider: A big thanks to azsl1326 he got us the Patched Init_boot to make this possible.
-You need to unlock the bootloader of your device. This means you'll lose the data ect ect ect.
-People are losing Netflix access after this process, right now we haven't found a "cure" for this, but is pretty normal if you have root a Oneplus device before, when i found the fix i'll edit this right away.
-I'll write this for experts and newcomers a like just in case so they don't have to start asking for simple questions.
-After the root some people have the issue that they cant use security like passwords, fingerprint...ect ect. (as of now the only fix they have is to reset everything and doing the rooting again for 2+times). If i find the "cure" i'll let you guys know.
Spoiler: Issues connecting your device to the PC?
To some people the USB debugging is not working at all, because the phone turn it off after you try to use it or connect it to the PC.
I personally had this issue so i just workaround it. This is what i did:
1- Connect the OnePlus to the same network as your PC.
2- Turn On Wireless debugging on your OP11 and select Pair device with pairing code:
3- Then use this on your PC after you open CMD of course:
Then put the code you have.
The check with this command to see if it is connected:
Now that it is connected you can enter bootloader and connect it to your PC in that mode normally with:
OK now back to the deal:
1- Download the latest platform tools from here:
-Unzip it and put it in the desktop for easy access.
2-The bootloader
Spoiler: Unlock the Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
3- Flashing the Init_Boot.img
In this case i'll provide the already patched Init_boot.img for A07!!! so you don't have to look for it, is attached to this thread.
Download the img and put it in the same folder as the platform tools for easy access.
Spoiler: Magisk Canary
After you enter the device.
1. Dowload the Magisk Canary version from this link:
2. Install it on you device.
Spoiler: Opening CMD (Command Prompt)
After you got everything in place open the platform folder and type CMD on the location box, then press Enter.
If that doesn't work, just open CMD and type:
CD and write the location of the platform folder to get it to work.
Now to the "flashing"
Enter the bootloader like before to start, now type this:
The above command should automatically flash the init_boot to both the slots. However, if you face any issues while executing that command, then you could also manually specify the slots while flashing. Like this:
And
4-Restart your phone and check the magisk canary app that everything is OK.
Spoiler: Bypassing Safetynet
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
Download a safetynet check just to be sure.
And thats pretty much it, if you guys find some issues after the root, please post them here so i'll start adding more and more info about it for future references and fixes.
Click to expand...
Click to collapse
You are so helpful! This worked flawlessly!
ChrisFeiveel84 said:
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
Click to expand...
Click to collapse
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
scottlam1 said:
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
Click to expand...
Click to collapse
i never use adb over wifi sorry
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
ChrisFeiveel84 said:
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
Click to expand...
Click to collapse
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
H4X0R46 said:
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
Click to expand...
Click to collapse
I didn't have an issue with my lock screen and stuff. I also didn't do anything to the phone other than unlock bootloader and root. Once I did this my lock screen and fingerprint and stuff wasn't an issue at all. Maybe I got lucky.
H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
The password issue has nothing to do with rooting, it is caused by unlocking the bootloader. Before you do any rooting, first lock and unlock the bootloader 3 times. After the third time, you can set the password (or pin, or pattern/etc) and THEN do the actual rooting.
Do you have boot.img instead i rather have temp root
i accidentally pushed the patched init boot img to phone before updating, now i keep getting failed system update, any way to revert back to original A06 init_boot.img so i can take update and then come back and root
SappyHanger said:
Do you have boot.img instead i rather have temp root
Click to expand...
Click to collapse
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
blasbenoit said:
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
Click to expand...
Click to collapse
can you point me to the init boot image on A06, i accidentally pushed the patched a07 version to a06 w/o updating to a07
So I did the above and magisk turns into a green android icon and won't start. It did start before I flashed the init boot.... ?? Tried to re-install magisk, same thing. green icon.....
Do I need to sideload magisk? (adb sideload Magisk-v25.2.zip) ???