Are there any problems when changing the recovery to TWRP? - Google Pixel 2 XL Guides, News, & Discussion

I was reading to see if I found something related to the consequences of rooting my PIXEL 2XL and put a custom recovery (TWRP), if it happens as with my previous Galaxy S8, which changed the KNOX to 1, meaning that it could not be left as newly purchased, it showed that it had been manipulated and could not be used with any of its own APKs for being "manipulated".
In definitive it is possible to revert the action of rootear and to change the recovery to PIXEL 2XL without major consequences?:confuso:

lmmerono said:
I was reading to see if I found something related to the consequences of rooting my PIXEL 2XL and put a custom recovery (TWRP), if it happens as with my previous Galaxy S8, which changed the KNOX to 1, meaning that it could not be left as newly purchased, it showed that it had been manipulated and could not be used with any of its own APKs for being "manipulated".
In definitive it is possible to revert the action of rootear and to change the recovery to PIXEL 2XL without major consequences?:confuso:
Click to expand...
Click to collapse
Absolutely you can without issue. I've run twrp on my P2XL since it's inception in late 2017 without issue. Since we have an A/B partitioned device, there is no separate recovery, it is built in with the boot.img. Which means twrp can easily be removed by flashing or fastbooting the stock boot.img :good:

Badger50 said:
Absolutely you can without issue. I've run twrp on my P2XL since it's inception in late 2017 without issue. Since we have an A/B partitioned device, there is no separate recovery, it is built in with the boot.img. Which means twrp can easily be removed by flashing or fastbooting the stock boot.img :good:
Click to expand...
Click to collapse
Thank you very much, but there is no "waste" in the mobile as in the Galaxy S8?:confuso:

lmmerono said:
Thank you very much, but there is no "waste" in the mobile as in the Galaxy S8?:confuso:
Click to expand...
Click to collapse
Not sure I understand what you mean. "No waste in the mobile"???

Badger50 said:
Not sure I understand what you mean. "No waste in the mobile"???
Click to expand...
Click to collapse
that is registered in some internal counter as in the galaxy s8

lmmerono said:
that is registered in some internal counter as in the galaxy s8
Click to expand...
Click to collapse
That's just because it uses Sammy's memory chip I believe. Nothing to worry about :good:

Badger50 said:
That's just because it uses Sammy's memory chip I believe. Nothing to worry about :good:
Click to expand...
Click to collapse
Thank you very much, I already did it and in part and to be the first time that I put my hand, it has not gone too badly.
Let me explain, update it by means of "TOOL ALL IN ONE" to version 9 PIE, the last one that appears in the list, I flashed twrp-3.2.3-0-taimen and 3.2.3-1 and there is this problem when starting in recovery mode. ask for a password and when you do not know it (provide with the access pin to the screen and with the digital fingerprint without results) it does not allow me to make some options like trying to decrypt the DATA and that is a problem for me.
Is there any magic formula as a possible "default password ist xxxxxxxx"?
There is some rational way to decrypt data because using the TWRP when I make a backup and get to the partition of DATA hangs up and I have to do the backups without copying DATA.
Forgive the beating I'm giving you but I do not find much literature from this terminal, my previous phone was the Galaxy S8 G-950F and with that phone everything was relatively easy.
Thank you.:confuso:

lmmerono said:
Thank you very much, I already did it and in part and to be the first time that I put my hand, it has not gone too badly.
Let me explain, update it by means of "TOOL ALL IN ONE" to version 9 PIE, the last one that appears in the list, I flashed twrp-3.2.3-0-taimen and 3.2.3-1 and there is this problem when starting in recovery mode. ask for a password and when you do not know it (provide with the access pin to the screen and with the digital fingerprint without results) it does not allow me to make some options like trying to decrypt the DATA and that is a problem for me.
Is there any magic formula as a possible "default password ist xxxxxxxx"?
There is some rational way to decrypt data because using the TWRP when I make a backup and get to the partition of DATA hangs up and I have to do the backups without copying DATA.
Forgive the beating I'm giving you but I do not find much literature from this terminal, my previous phone was the Galaxy S8 G-950F and with that phone everything was relatively easy.
Thank you.:confuso:
Click to expand...
Click to collapse
No trouble at all my friend. The twrp password would be the same as your screen unlock pin. However, to save time and trouble going forward, set your screen lock to swipe, then enter twrp to make your backups. When done, go back to the OS, setup screen lock pin, or whatever you use, then when you go back to twrp and enter your screen lock password, twrp should decrypt just fine :good:

Badger50 said:
No trouble at all my friend. The twrp password would be the same as your screen unlock pin. However, to save time and trouble going forward, set your screen lock to swipe, then enter twrp to make your backups. When done, go back to the OS, setup screen lock pin, or whatever you use, then when you go back to twrp and enter your screen lock password, twrp should decrypt just fine :good:
Click to expand...
Click to collapse
[BAs simple as great.
Problem solved, I can access all the options except that, since the data is encrypted when I try to make a full backup when I get to DATA, the copy is broken and I can only remove it if I unmark the copy of DATA
Thank you very much for your time and attention.:bueno:

Related

Should I just give in and encrypt my phone? Do you use your phone encrypted?

When I got my phone I chose to decrypt it, mostly because I was afraid of TWRP not being able to read the encrypted partition (at the time) and fears of bad performance (which plagued the N6 when it came out).
Every time I update my phone I have to wait until a noencrypt boot partition for my version is released and it makes the whole process clunkier.
I was wondering how many people still have their phone decrypted. Are there any downsides to encrypting my phone now? I've also seen some talks about kernels that support decrypted phones - I thought this was something that was decided at the boot partition level? What does the kernel have to do with it?
Thanks in advance for any information that will help me decide how to move forward.
Slartibartfast_ said:
When I got my phone I chose to decrypt it, mostly because I was afraid of TWRP not being able to read the encrypted partition (at the time) and fears of bad performance (which plagued the N6 when it came out).
Every time I update my phone I have to wait until a noencrypt boot partition for my version is released and it makes the whole process clunkier.
I was wondering how many people still have their phone decrypted. Are there any downsides to encrypting my phone now? I've also seen some talks about kernels that support decrypted phones - I thought this was something that was decided at the boot partition level? What does the kernel have to do with it?
Thanks in advance for any information that will help me decide how to move forward.
Click to expand...
Click to collapse
I would say it all depends on the user. If you use your phone for sensitive material such as work-related Communications or financial transactions, it might be a good idea to do so. If on the other hand, you use your phone to Simply play games and communicate on social media, it may not matter so much depending on what type of information you have on your phone
Just speaking for myself, my phone is encrypted, and I have no problem reading it with TWRP. I can apply over-the-air patches without a problem granted I take steps to return to. Full stock beforehand
Sent from my Nexus 6P using Tapatalk
Having the phone decrypted doesn't really give any benefit, on paper there's a performance gain but in real world usage it isn't noticeable. Just encrypt it and then you don't have to worry about all this mess.
Thank you both for your replies!
Heisenberg said:
Having the phone decrypted doesn't really give any benefit, on paper there's a performance gain but in real world usage it isn't noticeable. Just encrypt it and then you don't have to worry about all this mess.
Click to expand...
Click to collapse
What will I see different if I allow it to encrypt my data now? Basically to my understanding if I update to the latest version, if I overwrite the boot image and the kernel, it will encrypt my data the first time I boot into Android, right? Will I then have to enter my Google password every time I boot the phone? or my phone unlock PIN?
Slartibartfast_ said:
Thank you both for your replies!
What will I see different if I allow it to encrypt my data now? Basically to my understanding if I update to the latest version, if I overwrite the boot image and the kernel, it will encrypt my data the first time I boot into Android, right? Will I then have to enter my Google password every time I boot the phone? or my phone unlock PIN?
Click to expand...
Click to collapse
You can encrypt your data at any time. It will encrypt on the first boot after removing the kernel that doesn't force encryption. You only need to enter a pin/pattern if you choose to have lockscreen security, you can choose not to have any lockscreen security at all.
Honestly I would say do it. I always had it un-encrypted and it was just a pain in the arse waiting for someone to post a boot.img that doesn't force encryption or flashing a custom kernel to keep it without encryption. With this there is no worrying before updates, I have not noticed any changes in performance, and if you do want to use a custom kernel they all work great with it.
Yes, and yes!
Sent from my Nexus 6P using Tapatalk
My 6P arrived yesterday and I was pondering this same question. I have read a number of resources that show slower read/write speeds with encryption in play; however I use this phone for work and a backup to our kids' tablets dying (car rides, rainy day, etc. lol).
I was about to ask you @Heisenberg about decryption in your How-To thread in the General forum as I was confused on how to do this now? I recall from Nexus 6 days it was always a custom boot.img and you were decrypted...our instructions read more like TWRP (after a certain version) drives this process now instead?
Regardless, I am debating whether to bother with decryption at this point since it will be used for work.
3's&7's said:
My 6P arrived yesterday and I was pondering this same question. I have read a number of resources that show slower read/write speeds with encryption in play; however I use this phone for work and a backup to our kids' tablets dying (car rides, rainy day, etc. lol).
I was about to ask you @Heisenberg about decryption in your How-To thread in the General forum as I was confused on how to do this now? I recall from Nexus 6 days it was always a custom boot.img and you were decrypted...our instructions read more like TWRP (after a certain version) drives this process now instead?
Regardless, I am debating whether to bother with decryption at this point since it will be used for work.
Click to expand...
Click to collapse
TWRP isn't involved in the process of decryption, it was that TWRP wasn't able to decrypt so deception was necessary to use TWRP. To decrypt you need a kernel that doesn't force encryption, and to issue the "fastboot format userdata" fastboot command. This will erase your data so back it up first.
Heisenberg said:
TWRP isn't involved in the process of decryption, it was that TWRP wasn't able to decrypt so deception was necessary to use TWRP. To decrypt you need a kernel that doesn't force encryption, and to issue the "fastboot format userdata" fastboot command. This will erase your data so back it up first.
Click to expand...
Click to collapse
@Heisenberg ...lol, I honestly thought deception was a typo for decryption!
How dare I question the typing capability of the keeper of knowledge for the Nexus community! Did some more research and get "Deception" now (how often do you read those words in a sentence together in life as an adult?!).
Thank you as always you are always a benefit to the community! Ill go hunting for a kernel and test both security modes for fun (its a Nexus, right?!)...probably wont bother long term as I have a few exchange accounts, shared files, etc. on my devices.

Samsung S7 Edge is locked - Unlock or Data Extract help? Unique Situation...

Ok guys, new here and I've done a bit of reading on this already. From what I gather, the S7 Edge is difficult if not impossible to unlock without a factory reset. Here's the issue.
This phone belongs to my friend's husband who was severely injured in an accident at work. He's in a coma and probably won't survive. He was severely burned over 90% of his body with chemicals and he has no fingerprints to unlock the fingerprint scanner. In addition, his wife doesn't know his password, so I figured I'd see if I could do anything for her. I tried the Dr. Fone program, but it's apparently incompatible with the S7 Edge. He keeps getting texts and messages and we can't check them. The phone is also set for a daily alarm at 1:30 AM, and apparently you can't power it down without the lock code either. Ideally, I'd like to either gain access for her or at least extract what data we can from the thing before factory resetting it. It would also be nice to power it down so that it doesn't keep putting out an alarm every night in the middle of the night. All his contacts with his family are inconveniently stored in the phone as well. It's kind of a worst case scenario.
Any assistance or recommendations for a course of action for this situation would be fantastic. I don't have any other information on the device itself other than that it's running on Freedom Mobile's network in Ontario, Canada. They've said they can factory reset it for her, but we were trying to avoid that and get any contacts or messages from his phone if possible.
Thanks in advance for any help! I know it's a long shot!
Edit: I managed to power down the phone with the Power Button/Volume Down trick after about 9 tries, so at least the alarm won't go off. Other than that, no luck.
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
UnNaMeD__ said:
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Click to expand...
Click to collapse
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Use odin 3.13 the latest
Then download twrp recovery 3.2.2.0 tar file for hero2lte the latest.
Boot your phone into odin mode by restarting your phone while holding power home button and vol down. When your reach the confirmation screen press OK.
Open odin and put the tar file in the ap slot and click the ap box and hit start to begin flashing.
Now restart ur phone by holding power home and vol down then immediately hold power home vol up to reach custom recovery.
Edit I just tested this myself
Flash the zip file from this thread no need to go looking for files in system.
https://forum.xda-developers.com/showthread.php?t=2780696
Should remove password pin or pattern.
To check if it's network locked just look at the back of your phone if it says 935u or Verizon wireless or 935W8 then the phone is unlocked for different networks.
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
UnNaMeD__ said:
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
Click to expand...
Click to collapse
maxlords said:
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
Click to expand...
Click to collapse
Hey alright no problem.
Download TWRP for G935W8 from official TWRP website:
https://teamw.in/samsung/samsunggalaxys7edge.html
You can follow some instructions from this thread regarding flashing:
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Flashing TWRP might cause your phone to not boot. You will need to download dm-verity disabler from the thread above.
So download TWRP, Aroma file manager, dm-verity bypass, and zip file to disable pass that the other user posted: https://forum.xda-developers.com/showthread.php?t=2780696
Download all these files and put aroma file manager, dm-verity bypass and that password zip file bypass on your SD.
Make sure auto reboot is disabled in odin, follow instruction in thread about how to install twrp. If the auto reboot is disabled, phone will just remain at the same screen, so after the flashing is done from odin. You need to force reboot on your phone (volume down + power button for few seconds), just when the screen goes off, you need to immediately press recovery button combination (vol up + home + power). Here once you enter TWRP recovery see if you can enable MTP and trasnfer data to PC, if not, goto install zip and try password bypass zip file. If it works file then ok and proceed to install dm-verity bypass file and reboot your phone. If that zip doesn't works. You need to go to same install zip file option and now install aroma file manager. From there delete the password files that I told you about earlier, flash dm-verity and reboot again.
Thats it, if get confused about a step, tell me.
Well, I attempted to install TWRP through the latest version of Odin, but it didn't work. The error message I got in Recovery/Download mode was:
"Custom Binary (RECOVERY) Blocked By FRP Lock."
I looked that up online and apparently to install TWRP, I need to remove the FRP lock. I found a program called RealTerm which can supposedly bypass the FRP lock, but it doesn't seem to be connecting to the locked phone and it's not exactly user friendly.
Am I missing something here? Or is there no way to bypass the FRP lock on the unit?

Problems with inital setup with used phone

I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
Click to expand...
Click to collapse
Enter into fastboot mode by pressing volume up + power button together when the device is powered off. Connect your pc to your phone and do fastboot format userdata. For more information you can contact @MrWilsonxD he is an expert for this.
sleepwalking0593 said:
Enter into fastboot mode by pressing volume up + power button together when the device is powered off. Connect your pc to your phone and do fastboot format userdata. For more information you can contact @MrWilsonxD he is an expert for this.
Click to expand...
Click to collapse
Aye did this and it failed (Flashing is not allowed in Lock State). So i guess it's because the bootloader is still locked which i can't do since i can't access the settings to enable it (which i have to if i carry out the steps of a basic tutorial). Can i access the settings somehow without finishing the inital setup? Maybe in addition to being able to unlock the bootloader i can also remove the restriction of the old user account?
Apotrox said:
Aye did this and it failed (Flashing is not allowed in Lock State). So i guess it's because the bootloader is still locked which i can't do since i can't access the settings to enable it (which i have to if i carry out the steps of a basic tutorial). Can i access the settings somehow without finishing the inital setup? Maybe in addition to being able to unlock the bootloader i can also remove the restriction of the old user account?
Click to expand...
Click to collapse
Okay do this now. Wipe system, data, cache, dlavik, vendor. Then go in format and type yes. Flash oos. Reboot to recovery. Flash magisk. Flash no verity. Boot into os. See if it solve your issue.
Next method. Delete these 3 colour files in twrp. Look at photo attached.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Refer to this thread.
Hope it solves your issue. Goodluck. Happy Friday. Don't forget to leave thanks if I helped.
Me sleep now goodnight. See you tomorrow. I would try to do my best to help you and solve your issue
sleepwalking0593 said:
Okay do this now. Wipe system, data, cache, dlavik, vendor. Then go in format and type yes. Flash oos. Reboot to recovery. Flash magisk. Flash no verity. Boot into os. See if it solve your issue.
Next method. Delete these 3 colour files in twrp. Look at photo attached.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Refer to this thread.
Hope it solves your issue. Goodluck. Happy Friday. Don't forget to leave thanks if I helped.
Me sleep now goodnight. See you tomorrow. I would try to do my best to help you and solve your issue
Click to expand...
Click to collapse
The op has a device with a locked bootloader.
So he cannot have twrp, flash magisk every other things that you suggested...
BTW: if you're sleeping you can grab a BBS idle dump file for sure, you know what I mean
---------- Post added at 09:43 PM ---------- Previous post was at 09:30 PM ----------
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Click to expand...
Click to collapse
If the device has nougat, you can try to type *#812# within the emergency calling screen to get access to the home screen and can factory reset your device.
Otherwise you can try to write the partitions from scratch with the unbrick tool which should also work https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
strongst said:
The op has a device with a locked bootloader.
So he cannot have twrp, flash magisk every other things that you suggested...
BTW: if you're sleeping you can grab a BBS idle dump file for sure, you know what I mean
---------- Post added at 09:43 PM ---------- Previous post was at 09:30 PM ----------
If the device has nougat, you can try to type *#812# within the emergency calling screen to get access to the home screen and can factory reset your device.
Otherwise you can try to write the partitions from scratch with the unbrick tool which should also work https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
But you didn't read my last message i moved to oos now. You don't understand that many people face this issue. Even lightning kernel developer whose kernel was used by Sian in his earlier ROM also had that issue. People don't report on XDA because of things i can't type because i will get warning from mods. Everyone has shifted to telegram and those chats are not moderated and things that happen aren't good. If you are on telegram you will know. Okay i guess i will have to become like others and don't post my own question. Just will reply to others. I will post dump file when i flash ROM again and also developer doesn't support it. + Logs won't show anything. If it was possible atleast a kernel developer would have sent to others. + It's definitely not because of me. Because i didn't install anything apart from magisk, no verity zip, fk kernel app, bbs when i did my last testing. Sorry to bother you.
sleepwalking0593 said:
But you didn't read my last message i moved to oos now. You don't understand that many people face this issue. Even lightning kernel developer whose kernel was used by Sian in his earlier ROM also had that issue. People don't report on XDA because of things i can't type because i will get warning from mods. Everyone has shifted to telegram and those chats are not moderated and things that happen aren't good. If you are on telegram you will know. Okay i guess i will have to become like others and don't post my own question. Just will reply to others. I will post dump file when i flash ROM again and also developer doesn't support it. + Logs won't show anything. If it was possible atleast a kernel developer would have sent to others. + It's definitely not because of me. Because i didn't install anything apart from magisk, no verity zip, fk kernel app, bbs when i did my last testing. Sorry to bother you.
Click to expand...
Click to collapse
Again: The op of this thread thread as the factory reset protection issue on stock rom with locked bootloader.
You cannot suggest him to boot to twrp or format several partitions, that's simply not possible!
strongst said:
Again: The op of this thread thread as the factory reset protection issue on stock rom with locked bootloader.
You cannot suggest him to boot to twrp or format several partitions, that's simply not possible!
Click to expand...
Click to collapse
I'm sorry, i got messed up with another thread i guess. Okay i will think of another solution now.
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Click to expand...
Click to collapse
If you click on i forgot my email id. Than you get an option to enter your phone number. Will that work for you.
If you click on i forgot my email id. Than you get an option to enter your phone number. Will that work for you.
Click to expand...
Click to collapse
Nope i don't have the phone number used with the google account (apparently the seller used another number than the one he has on ebay). I messaged him but haven't gotten an answer yet.
Apotrox said:
Nope i don't have the phone number used with the google account (apparently the seller used another number than the one he has on ebay). I messaged him but haven't gotten an answer yet.
Click to expand...
Click to collapse
Have you tried my suggestions?
strongst said:
Have you tried my suggestions?
Click to expand...
Click to collapse
I'm at it, the *#812# didn't work so i'll have to try the unbrick tool method which takes some time to download the files. I'll keep you updated
strongst said:
Have you tried my suggestions?
Click to expand...
Click to collapse
Alright i skipped the thing with the drivers because it showed up correctly and used the msm download tool for OOS 9.0.4.
And it did work!! Thank you so much!

Trying to flash files in TWRP and can't make sense of what I'm seeing

Sorry if this sounds dumb but I've been out of the modding game for a long time and I barely knew what I was doing when I started. I've had 2 other devices since I last rooted so something's aren't adding up.
When I view my files in TWRP they seem almost encrypted, mainly the sdcard. If I wanted to install an image or zip file in the past I would find them on the sdcard and flash away. I attached a video to show in detail what I am seeing. Sorry for the poor quality. EDIT: sorry, after uploading my gif I see it only made it a thumbnail. I'll work on a correct version.
Thank you in advance.
They are encrypted. I see you are using BluSpark's TWRP, what OS / Version are you running? Does BluSpark work with the May security patch? Previous versions of TWRP had problems with the latest security patch and could not decrypt it.
Boot 3.3.1-6 from here then see if your files are still encrypted.
OhioYJ said:
They are encrypted. I see you are using BluSpark's TWRP, what OS / Version are you running? Does BluSpark work with the May security patch? Previous versions of TWRP had problems with the latest security patch and could not decrypt it.
Boot 3.3.1-6 from here then see if your files are still encrypted.
Click to expand...
Click to collapse
I'm running 9.0.11
I'll try that version you linked. Thanks. I assume I have to install using adb sor USB OTG since my internal file system is encrypted, right?
tjlmbklr said:
I'm running 9.0.11
I'll try that version you linked. Thanks. I assume I have to install using adb sor USB OTG since my internal file system is encrypted, right?
Click to expand...
Click to collapse
Yeah, either use a USB drive through OTG or copy it to internal (when in OOS) and use fastboot to boot the newer TWRP. You should be able to install from internal storage after that.
Disable fingerprint, smartlock , face recognizing etc.
It's security related.
Reboot
Then the folders show normal
tjlmbklr said:
I'm running 9.0.11
I'll try that version you linked. Thanks. I assume I have to install using adb sor USB OTG since my internal file system is encrypted, right?
Click to expand...
Click to collapse
9.0.14 has the May security patch and the new encryption, which will be an issue. I'm not sure why you are seeing that with 9.0.11, but definitely try the other version I linked to, I know it is up to date. Worst case, as mentioned, if you temporarily remove your password / pin code / pattern everything will just work. However then you will have to redo this, along with all your finger prints. Not that it's a big deal. Just get the right TWRP, and you won't have to do that.
OhioYJ said:
They are encrypted. I see you are using BluSpark's TWRP, what OS / Version are you running? Does BluSpark work with the May security patch? Previous versions of TWRP had problems with the latest security patch and could not decrypt it.
Boot 3.3.1-6 from here then see if your files are still encrypted.
Click to expand...
Click to collapse
Duvel999 said:
Disable fingerprint, smartlock , face recognizing etc.
It's security related.
Reboot
Then the folders show normal
Click to expand...
Click to collapse
OhioYJ said:
9.0.14 has the May security patch and the new encryption, which will be an issue. I'm not sure why you are seeing that with 9.0.11, but definitely try the other version I linked to, I know it is up to date. Worst case, as mentioned, if you temporarily remove your password / pin code / pattern everything will just work. However then you will have to redo this, along with all your finger prints. Not that it's a big deal. Just get the right TWRP, and you won't have to do that.
Click to expand...
Click to collapse
Temporarily disabled? I'm not sure how to disable other than delete the fingerprints all together. Will I need to do this every time I need.to boot into recovery?
tjlmbklr said:
Temporarily disabled? I'm not sure how to disable other than delete the fingerprints all together. Will I need to do this every time I need.to boot into recovery?
Click to expand...
Click to collapse
If you just delete your password / pin / etc, it will automatically delete all your finger prints and your TWRP problem will go away. No you should NOT need to do this. This is only because you don't have an up to date, or the wrong version of TWRP installed. I never remove my password and go into TWRP all the time. It's not an issue.
tjlmbklr said:
Sorry if this sounds dumb but I've been out of the modding game for a long time and I barely knew what I was doing when I started. I've had 2 other devices since I last rooted so something's aren't adding up.
When I view my files in TWRP they seem almost encrypted, mainly the sdcard. If I wanted to install an image or zip file in the past I would find them on the sdcard and flash away. I attached a video to show in detail what I am seeing. Sorry for the poor quality. EDIT: sorry, after uploading my gif I see it only made it a thumbnail. I'll work on a correct version.
Thank you in advance.
Click to expand...
Click to collapse
I think all you need to do here is turn off your screen lock by setting it to "None."
When you reboot to TWRP, you should see the files now unencrypted.
TWRP had the potential to allow you to input a "Pattern" screen lock, but I can't guarantee it will work under all circumstances, nor do I know what it does with fingerprint scans, etc.

Is it possible to unlock a P8 lite 2017 today ?

Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
RedSkull23 said:
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
Click to expand...
Click to collapse
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
turboxav said:
Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Click to expand...
Click to collapse
What you mean by "unlock".
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
With my p10 lite with emui 8 it worked. So why not
0
yes
I Have unlock my phone yesterday with dc unlocker
Seppppx said:
You can downgrade (idk if it is possible from emui 8 I don't even own this phone) and then you can follow this tutorial to unlock your bootloader (FOR FREE) https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Edit : found this guide with HiSuite it may work https://youtu.be/xFCLpgGZEJM
Click to expand...
Click to collapse
Yeah, but not for Huawei P8 Lite 2017 version... I found this to be possible just for older phones (like the original P8 lite) which can be downgraded to Android 5. Newer ones can't be flashed with unsigned firmware (= firmware which is not straight from damn Huawei who decided not to provide the bootloader codes in the first place) so the only way apparently is to use paid software like DC-Unlocker as stated in this official XDA thread --> https://www.xda-developers.com/huawei-honor-unlock-bootloader-fee/
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
Unlocked the bootloader yesterday! I have Huawei P8 Lite 2017 PRA-LX1 and had latest Emui 8 build on it... Bought the code for 4€ from DC-Unlocker, and required around 2 minutes for unlocking. You can follow this guide --> https://www.youtube.com/watch?v=4xYybHAlWaQ
I tried so hard to get the code for free, and I know modding should not cost people money. But at the end of the day, I think those 4 euros were worth it
Yeah,4 Euros is ok and the only method!!!
-CALIBAN666- said:
Yeah,4 Euros is ok and the only method!!!
Click to expand...
Click to collapse
And also worth it if we consider fact that our phone is now EMUI free. ?
DunoCZ said:
And also worth it if we consider fact that our phone is now EMUI free.
Click to expand...
Click to collapse
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
af1985 said:
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
Click to expand...
Click to collapse
Did you after fastboot oem unlock leave phone format yourself right?
DunoCZ said:
Did you after fastboot oem unlock leave phone format yourself right?
Click to expand...
Click to collapse
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget ???
Momin8454 said:
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget
Click to expand...
Click to collapse
Lol you are dumb...
DunoCZ said:
Lol you are dumb...
Click to expand...
Click to collapse
Well, I didn't had any knowledge of it. Turns out my EMUI version was more recent one that's why I had more issues with TWRP.
And I was just sharing my experience with Honor 8 lite.
DunoCZ said:
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
Click to expand...
Click to collapse
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Some advice from a beginner
af1985 said:
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Click to expand...
Click to collapse
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Jujub said:
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Click to expand...
Click to collapse
Check out my SPECTRUM profile I wrote even simple tut how to flash kernel and enable adoptable storage

Categories

Resources