I am on stock rom, rooted with magisk, and I cannot seem to get this phone decrypted. Every time I try to format data in twrp, I get an error, and I get stuck in a bootloop to recovery. Is there a step(s) I am missing here? I've tried looking through the forum but all I've seen are the same instructions on formatting data.
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
jdesignz said:
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
UPDATE:
I tried to redo the process again, just to verify the process, and I am still having the same network issues. I have 3g every once in a while, but its iffy and I no longer have LTE.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Well, as long as you have done backup with twrp you have nothing to worry about.
Sent from my XT1805 using Tapatalk
L4ndon said:
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Click to expand...
Click to collapse
Doing things the right way always works! Trouble is finding that right way (heed my warning about bad info in these threads - there is a lot of it - as you found out). Just so happens I also know how to splain things to users, I've done it for something like 25+ years (yeah, I am old - make that experienced). Tethering - used to be ya add a build.prop entry to allow it, but that was many years ago and most of not all enable it by default now.
Anyways, enjoy the ride. It may be a little bumpy, but it's the bumps that keep ya awake!
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
THX for that, got stuck in recovery process (loop).
I followed your instructions, but need of stock recovery.
My Path :
Backup DATA (w/o /media/)
Manually Backup Media with TWRP to Ext.SD
FORMAT /Data (use the DATA Button in TWRP), in my case it showed Errors, i ignored it and did it once again - this time it worked.
flashed Magisk
ended up in Recovery Loop - flashed stock recov. via FASTBOOT, reboot
a rainbow lightning circle turned up, said " DELETING", device rebooted by itself.
Now the Phone boots to Android, shut it down, restart with PWR BUTOON + VOL DOWN pressed to access bootloader and flash twrp again with FASTBOOT ( fastboot flash recovery nameoftheimage.img ENTER).
Now u can restore /DATA TWRP Backup and then the manually part - in my case that worked.
THX!
//EDIT
After first boot, i noticed missing write permissions for most Apps - so i decided to Reset SELinux via TWRP, worked !
te amo hice format data con r15 y al parecer se soluciono todo son lo maximo cauros
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
still sim not showing on my device which is xt1804
Never had the problem so can't help.
Related
I intend to create a post with how to do things on this phone.
Just bought the 64GB Black.
So, trying to pull the order of things to be done.
Please help, this is for newbies.
When you receive it. What should be done first? (and how did you do it???)
(EDIT : I will update this as I find things out.)
Bootloader
Follow the guide found here : http://xiaomitips.com/guide/unlock-mi-5-bootloader/
You should do this in advance of getting your phone.
Recovery - TWRP
Guide here : http://en.miui.com/thread-245756-1-1.html
Which ROM to install?
CM alternative?
Gapps?
If you own the Mi5, how did you go about it? Any tips? What went wrong? How did you fix?
First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.
regnarox said:
First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.
Click to expand...
Click to collapse
Which TWRP did you use (link?)
Which GApps did you use? (Nano, pico, stock etc) and presumably ARM64?
since there isn't a sdcard, are you able to do a full backup so you can revert back to if you have second thoughts. I guess you have to do a full wipe prior to flashing e.g CM13
Questions about rooting
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks
TWRP - https://www.androidfilehost.com/?fid=24533103863138514 (no touch screen issue which is present in other recoveries)
GApps - http://opengapps.org/ (ARM64) I used microG instead of gapps to save a lot of battery. (You can google it if you want)
It doesn't really matter what GApps do you use, although I'd go for nano/pico. I wouldn't want all the GApps to be my system apps.
---------- Post added at 11:11 AM ---------- Previous post was at 11:02 AM ----------
Sachuan said:
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks
Click to expand...
Click to collapse
1. You just need to format data, your system partition will not be wiped. You will just lose everything except the system.
2. You probably will be able to use MTP, although I'm not but other people are so you should too. If you don't, you'll need to go to advanced in TWRP, enter adb sideload and sideload the zip.
[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)
Sachuan said:
[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)
Click to expand...
Click to collapse
No, you don't
proag said:
No, you don't
Click to expand...
Click to collapse
Good thanks!
Sent from my MI 5 using XDA-Developers mobile app
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root
TWRP needed
Many people still have problems with bringing the device back to the ROM and Recovery stock, so once and for all I decided to make a simple post guide:
This is the backup.
https://mega.nz/#F!dQJAAJiT!9GCaOUGCjiahuNBkEbKIZQ
ONLY FOR P8 LITE 2017 [PRA-LX1C55] (but you can try with another branded or unbranded same device)
I do not feel responsible for any problems.
1: Put the ''BACKUPS'' folder in a new folder called ''TWRP'' in external_sd then reboot to TWRP.
2: In TWRP; Wipe cache and Dalvik cache, data and system. (Also Vendor if it was previously flashed)
3: Click on the restore option and select the backup; swipe and wait. When the installation finishes in my case, if an error appears you do not have to worry, you only need this backup to restore the original ROM and recovery after with eRecovery.
4: Reboot the device and when it shows the ''initial unlocked bootloader screen'', press vol +; it boot on eRecovery.
5: In eRecovery, if it shows erase data click on it firstly, if not, click directly on download and install fw and rom on the first option.
6: Insert your wifi password, and wait for the download of rom and recovery . An Italian TIM Branded c55b105 will be downloaded .
Installation performs automatic recovery, and twrp recovery will be overwritten.
Do not worry if you restart a couple of times, if all goes well you will have to wait for the device to boot and everything will be restored, if you want, you can also relock the bootloader.
I hope I can solve your problem:laugh::laugh::laugh:.
you are awesome!
you saved me! thanks!!!!!!:good::fingers-crossed:
SandXFX said:
you saved me! thanks!!!!!!:good::fingers-crossed:
Click to expand...
Click to collapse
Fr0nK said:
Click to expand...
Click to collapse
can someone give me a stock bakcup for pra-lx2
dazokevin28 said:
can someone give me a stock bakcup for pra-lx2
Click to expand...
Click to collapse
None here has lx2 version sorry , but you can also try this guide to back stock fw (without download lx1 fw obv)
GreenScreen problem
Hello, tried to perform that solution, but encounter a major problem.
In 2nd point I did wiped the Vendor as well (cause was using the haky's LinOS 14.1 previously);
then restored files from your backup (get warning "createTarFork() process ended with ERROR=255" at the end), and reboot.
Then some wierd stuff shows up - instead of any Huawei logo or unlocked bootload screen - I've got GreenScreen witch 2 rectangles (Blue&Red).
But it enters eRecovery; so yet without any worries tried to start recovery over there - "Getting package info failed" made that impossible.
And now I'm bricked a little bit - cause can not enter TWRP, can not flash the TWRP again, only thing that is possible - the eRecovery mode.
Anyone have any ideas how ot unbrick it?
<!-- Edit -->
Sorry for troubles, as just realized the steps made my phone locked again, so "fastboot oen unlock [...]" it again, and now everything is like before.
<!-- Edit2 -->
Already installed SlimOS and everything seems just fine. Therefore the spectacular GreenScreen still showing up every rebooting, even though I did wiped eveything (every single position) in TWRP since then. x)
Would be greatfull for any informations about this phenomenon.
Sixter said:
Hello, tried to perform that solution, but encounter a major problem.
In 2nd point I did wiped the Vendor as well (cause was using the haky's LinOS 14.1 previously);
then restored files from your backup (get warning "createTarFork() process ended with ERROR=255" at the end), and reboot.
Then some wierd stuff shows up - instead of any Huawei logo or unlocked bootload screen - I've got GreenScreen witch 2 rectangles (Blue&Red).
But it enters eRecovery; so yet without any worries tried to start recovery over there - "Getting package info failed" made that impossible.
And now I'm bricked a little bit - cause can not enter TWRP, can not flash the TWRP again, only thing that is possible - the eRecovery mode.
Anyone have any ideas how ot unbrick it?
<!-- Edit -->
Sorry for troubles, as just realized the steps made my phone locked again, so "fastboot oen unlock [...]" it again, and now everything is like before.
<!-- Edit2 -->
Already installed SlimOS and everything seems just fine. Therefore the spectacular GreenScreen still showing up every rebooting, even though I did wiped eveything (every single position) in TWRP since then. x)
Would be greatfull for any informations about this phenomenon.
Click to expand...
Click to collapse
unfortunately I have not encountered this problem
to restore the phone check here
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
regards
Plz upload as a single zip, not a whole folder on mega .
Can someone give me a stock back up for PRA-LX1C432B### Single Sim please and thanks
Fr0nk0 said:
TWRP needed
Many people still have problems with bringing the device back to the ROM and Recovery stock, so once and for all I decided to make a simple post guide:
This is the backup.
https://mega.nz/#F!dQJAAJiT!9GCaOUGCjiahuNBkEbKIZQ
ONLY FOR P8 LITE 2017 [PRA-LX1C55] (but you can try with another branded or unbranded same device)
I do not feel responsible for any problems.
1: Put the ''BACKUPS'' folder in a new folder called ''TWRP'' in external_sd then reboot to TWRP.
2: In TWRP; Wipe cache and Dalvik cache, data and system. (Also Vendor if it was previously flashed)
3: Click on the restore option and select the backup; swipe and wait. When the installation finishes in my case, if an error appears you do not have to worry, you only need this backup to restore the original ROM and recovery after with eRecovery.
4: Reboot the device and when it shows the ''initial unlocked bootloader screen'', press vol +; it boot on eRecovery.
5: In eRecovery, if it shows erase data click on it firstly, if not, click directly on download and install fw and rom on the first option.
6: Insert your wifi password, and wait for the download of rom and recovery . An Italian TIM Branded c55b105 will be downloaded .
Installation performs automatic recovery, and twrp recovery will be overwritten.
Do not worry if you restart a couple of times, if all goes well you will have to wait for the device to boot and everything will be restored, if you want, you can also relock the bootloader.
I hope I can solve your problem:laugh::laugh::laugh:.
Click to expand...
Click to collapse
thanks for your tread it's very helpfully but i flashed the oeminfo only without restore everything just the oeminfo backup i changed in img mode and i flashed with twrp and done. I reboot to eRecovery mode, connect to WiFi and done i installed the firmware pra-lx1c55b105 with success TIM firmware
thanks for your great job ?
jalel25 said:
thanks for your tread it's very helpfully but i flashed the oeminfo only without restore everything just the oeminfo backup i changed in img mode and i flashed with twrp and done. I reboot to eRecovery mode, connect to WiFi and done i installed the firmware pra-lx1c55b105 with success TIM firmware
thanks for your great job
Click to expand...
Click to collapse
Nice to hear. :fingers-crossed:
T-Mobile G6 H872 11G Stock Collection
Based on OEM 11g KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
SysBoot ROMs were test flashed over 11g and 20a bootloaders. 11h has not been tested.
11G Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you Flashed SysBoot with Patched Kernel and Root, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:43dcc7f82c501147da6500efdd594d5c
SysBoot ROM - md5:2ac20008794eb74523a442da7b8bafdc
SysBoot Deodexed - md5:b92fcb7649bddf934ff9be0246c9fab6
SysBoot w/Patched Kernel + Magisk Root - md5:ae4bab194a69b2044f3aee69ba495464
FullStock ROM - md5:e919fe16852b5f0b830a48cda914003a
StockLAF - md5:ce70b36e4d293e183544a18409a526de
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
These files are long overdue. I hope you all find them helpful. Please let me know if you run into any problems with them. Thanks!
Other H872 Projects
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
H872 20D Stock Collection
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h87211g, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 11g KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-09-30
Current Beta Version: 0.9
Beta Release Date: 2018-09-30
Created 2018-09-29
Last Updated 2018-10-19
Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?
DmytroPitenko said:
Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?
Click to expand...
Click to collapse
very welcome. if you flash the bootloader only it will leave whatever laf you have untouched, and yes fingerprint scanner will work with custom ROMs like AOSP Extended.
However, I have not tested running stock 20a with the 11g bootloader. But it doesn't sound like that's what you are wanting to do
*edit*
if you have already flashed a custom Rom and FP doesn't work, simply flashing the 11g bootloader zip will fix it. it is not necessary to reflash the rom
also, not sure why anybody would want to, but 11g bootloader with stock 20a rom will not work. it will hang on the boot logo indefinitely which can be dangerous for your phone. so please make sure you are using a custom Rom or stock 11g with this bootloader
Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Sent from my XT1575 using Tapatalk
Ken C said:
Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Click to expand...
Click to collapse
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file on your sdcard and rename it to laf.bin, and run these
adb shell
su
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/laf
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf
weakNPCdotCom said:
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file in the folder with adb.exe, rename it to laf.bin, and run these
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/laf
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf
Click to expand...
Click to collapse
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk
Ken C said:
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak
weakNPCdotCom said:
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak
Click to expand...
Click to collapse
Ok. Figured it was something like that. Always meant to ask somebody, just never did
Sent from my XT1575 using Tapatalk
weakNPCdotCom said:
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
[/CENTER]
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
Click to expand...
Click to collapse
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).
ryanrod said:
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).
Click to expand...
Click to collapse
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
Awesome. Yeah, I am going to give it a flash tomorrow morning. I do not think I will need the stock recovery at this time, but thanks for offering! I have been stuck with the whole twrp on LAF issue, not being able to use LGUP, and this just a godsend to get back to 11g. Thanks again! :good:
weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.
ryanrod said:
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.
Click to expand...
Click to collapse
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.
If I were to downgrade if able to, would that have a chance? I still am getting stuck in fastboot mode unless I'm hooked up to the pic and let lgup do it's thing.
It detects the device, does it's thing, reboots it and gives me a factory reset phone back just no dl mode.
It's not bricked yet lol.
Sent from my XT1575 using Tapatalk
weakNPCdotCom said:
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.
Click to expand...
Click to collapse
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:
ryanrod said:
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:
Click to expand...
Click to collapse
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.
weakNPCdotCom said:
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.
Click to expand...
Click to collapse
Ahh yes this makes sense. Maybe it was a stock recovery repair due to magisk failure as you mentioned? I still don't understand why with these LG phones (ever since the G3 I think), when you boot into recovery using the hardware buttons, it asks if you want to factory reset the device. Then if you say yes, it doesn't reset/format anything, and it boots right into twrp recovery after that. So weird. I can boot directly into recovery just fine from a reboot app or adb from a running system without getting that factory reset screen...
I'm sure your laf zip with twrp works for the reasons you mention. Luckily I don't have to find out since my laf partition is fine and still has twrp!
Regarding bluetooth, I will give the sysboot flash a try and update you with the results. First I want to wait until my backup phone is running again. I bent the sim pins on the backup phone due to those ****ty plastic adapters that catch the pins (an old E980 w/ the larger sim size) so I ordered another sim reader to fix that. I also read in some forums that wiping cache and dalvik cache resolved others bluetooth issues with the G6. I will try that too.
Either way, I will update soon. I am happy to share my notes as I really appreciate the help!
@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk
Ken C said:
@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
Yes that's the message I get. So your saying not to worry about it for the moment? I only see it regularly on a stock rom when going into recovery not aex.
I just wanted to make sure. With the mess I been going through.
So, I can flash this stock build you have and if I wanted normal download back flash the laf zip and I'll have DL mode on laf, twrp on recovery and everything should Mount correctly and all that?
And if I go to flash something custom FP will work? I know I'm a pain I just want to "know" my setup isn't weird somehow. Probably over thinking it, but I think I'm good, except that when I rooted I was getting that message off & on, on the stock build of 20a. I'm hoping that running this build I can get that worked out. Maybe that deal is a 20a thing? Reading through the root thread it seemed to happen less to people on a lower numbered build and it would stop after the format.
I can make backups Burt I've yet to try to restore one.
Sent from my LG-H872 using Tapatalk
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Jonny6921 said:
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Click to expand...
Click to collapse
Perhaps you should say which version of NitrogenOS you're using. Also asking in Nitrogen's thread has a higher chance of answers for your question.
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
runekock said:
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
Click to expand...
Click to collapse
Additionally TWRP's format function is broken.
Try "fastboot format userdata" if TWRP isn't properly formatting.
Elektroschmock said:
Additionally TWRP's format function is broken.
Click to expand...
Click to collapse
Can you elaborate on this?
I usually try to erase and format in fastboot anyway. But fastboot throws a can't format raw partition or something like that.
format (not wipe) data or use oreo builds
i've already done it
upgrade your twrp if it keeps failing, i'm using the latest release
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Flaco05 said:
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Click to expand...
Click to collapse
Without explaining what the problem is, it is hard to help you. Since you are using TWRP, you should have backup to restore.
Thank you for replying. I have the exact problem described by OP. And yes, I have a backup, so technically not bricked, you are right. Just very disappointed that following the flashing instructions let to this problem. Thank you again.
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Hi, that is exactly what I did! I have repeated the process with LineageOS 15.1 (and the matching GApps) and it worked. Might this be an encryption problem related to LinerageOS 16? And thank you for responding.
Incidentally, what GApps package is the one most recommend? I used Open GApps Stock, but some of the Google Apps are acting up.
I use Opengapps Pico Arm (not Arm64).
All I can say is that I've installed LineageOS 16 on 2 N5s, 2 N4s and a Lenovo 8" tablet, all with no problems at all. Your problem is not device-specific, since the original query was not for an N6, and I myself know about this "corrupt" problem because I suffered from it myself a year or so ago on my own N6. The procedure I specified has always worked 100% for me every time.
Looking at the LineageOS 16 thread, there is a specific TWRP linked, and MindTheGapps is also linked which is different than openGapps.
If you haven't decrypted by FORMATING user data (not wiping), that may also be a problem.
Thanks, ktmom. The format was part of my instructions, and Flaco05 says he did exactly that. Normally I don't use fastboot to format - I just rely on TWRP and it's worked fine.
I've always used the standard Opengapps Pico and TWRP 3.3.1, no special versions, and they have always worked flawlessly - never any problems. Still, since Flaco05 is having problems, I guess he has nothing to lose by trying the recommended versions...
Thank you all. I will try some of these things tomorrow. I love this community!
dahawthorne said:
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Click to expand...
Click to collapse
OK, I did all this, but have been stuck at the Google screen upon reboot for 30 minutes. Is this bad news, or this normal?
No, definitely not normal. A new ROM takes longer to boot but it's generally ten minutes maximum.
Have you tried flashing only the ROM & Gapps, without Magisk? Once you boot successfully you can then flash Magisk later. Try starting again from the top and see if that works.
(P.S. In a slow quiet thread, as this one is at the moment, there's no need to copy the entire post to which you're replying... )
Edit: No, sorry, not from the top. TWRP will still be there after formatting & wiping, so start at the third (format data) part.
Thank you. There is still some kind of a problem. After I finish flashing ROM and Gapps using the instructions, and then reboot (after wiping cache/davlik, right?), I get the Lineage OS logo in motion, and then finally boots into recovery (not system) again. Not sure what to do. Maybe try a different build? I am currently using the latest LineageOS 16 nightly.
Strange. Maybe try LineageOS 15.1?
I enjoy playing with bleeding-edge software, but when you can't get it to work at all then it sort of ruins the fun. A lot of people seem to prefer the stability of 15.1. Personally I never see much difference between even major versions. Maybe I'm just a bit unobservant...