Related
I managed to somehow break my 3 week old HTC 10's rear camera glass so I'm going to get it replaced via the "Uh-Oh Protection" since I bought from HTC directly.
I have the Unlocked US edition, but use it on Verizon. When I get my replacement phone, I'll go through the steps to Unlock via HTC dev, run Sunshine for S-OFF and change the CID/MID to Verizon. At that point, can I just flash a NANDROID backup from my old device onto the new one to get my ROM / Apps / etc. back? Will there be any issues since it'll be different hardware? The NANDROID will contain everything I need so I won't need to first apply the VZW RUU right? I think I've done it before on previous HTC hardware but I want to check if it'll work before I try it. Will encryption be an issue?
Sounds good as long as correct firmware is also flashed
drumz0rz said:
I managed to somehow break my 3 week old HTC 10's rear camera glass so I'm going to get it replaced via the "Uh-Oh Protection" since I bought from HTC directly.
I have the Unlocked US edition, but use it on Verizon. When I get my replacement phone, I'll go through the steps to Unlock via HTC dev, run Sunshine for S-OFF and change the CID/MID to Verizon. At that point, can I just flash a NANDROID backup from my old device onto the new one to get my ROM / Apps / etc. back? Will there be any issues since it'll be different hardware? The NANDROID will contain everything I need so I won't need to first apply the VZW RUU right? I think I've done it before on previous HTC hardware but I want to check if it'll work before I try it. Will encryption be an issue?
Click to expand...
Click to collapse
I don't see it being any issue.
So I just got my replacement phone. I followed the exact same steps as I did on my original HTC 10 to get s-off and convert to Verizon (used the same files as well). I made a fresh NANADROID backup on the old phone in TWRP, copied it over to the new phone, and restored it. When I reboot I get stuck on the white splash screen. I tried wiping the cache but I can't progress further.
I was really hoping I'd just be able to use the NANDROID so I don't have to go through the arduous process of backing up all of my apps and settings, and copying them over in TiBu, and having to recustomize everything in VenomHub/Xposed.
What am I doing wrong?
drumz0rz said:
So I just got my replacement phone. I followed the exact same steps as I did on my original HTC 10 to get s-off and convert to Verizon (used the same files as well). I made a fresh NANADROID backup on the old phone in TWRP, copied it over to the new phone, and restored it. When I reboot I get stuck on the white splash screen. I tried wiping the cache but I can't progress further.
I was really hoping I'd just be able to use the NANDROID so I don't have to go through the arduous process of backing up all of my apps and settings, and copying them over in TiBu, and having to recustomize everything in VenomHub/Xposed.
What am I doing wrong?
Click to expand...
Click to collapse
Try dirty flashing ROM
How would changing devices between TWRP backup/restore affect encryption?
EDIT: Since TWRP decrypts now, phone encryption would be a moot point in this context.
I received a replacement Uh-Oh phone from HTC. Unlocked bootloader, installed TWRP and S-Offed. Tried using my Nandroid to restore but TWRP would not see it (file names different, based on S/N). I created a small new backup to create the proper file structure and renamed the old Nandroid backup and placed it in the proper directory. Still would not work so I went to my TiBu backup and reset everything back up.
Here's a strange result though - my fingerprint works fine to unlock the phone but somewhere along the line (perhaps my attempt restoring Nandroid) the pattern lock changed. So now I cannot unlock phone using the pattern and cannot change it. I can use fingerprint so it works for now but I would like to reset the pattern lock - any ideas?
stebaile said:
I received a replacement Uh-Oh phone from HTC. Unlocked bootloader, installed TWRP and S-Offed. Tried using my Nandroid to restore but TWRP would not see it (file names different, based on S/N). I created a small new backup to create the proper file structure and renamed the old Nandroid backup and placed it in the proper directory. Still would not work so I went to my TiBu backup and reset everything back up.
Here's a strange result though - my fingerprint works fine to unlock the phone but somewhere along the line (perhaps my attempt restoring Nandroid) the pattern lock changed. So now I cannot unlock phone using the pattern and cannot change it. I can use fingerprint so it works for now but I would like to reset the pattern lock - any ideas?
Click to expand...
Click to collapse
So when you did a restore with TWRP, what was the result? What does "still would not work" mean exactly? What did the log say?
I'll have to dig into the log file but it is my habit to only backup /data. That's what I was trying to restore. I might need to factory reset to get the pin reset I suppose. Was hoping there was a file I could delete to reset the encryption.
Sent from my HTC 10 using XDA-Developers mobile app
Just in case anyone has this issue of losing their pattern lock from a Nandroid restore I found the answer in a different thread. Use a file manager with root access such as Root Explorer, or use TWRP's file manager capability to delete the locksettings.* files in /data/system. Reboot and your device will no longer have a pattern lock. You will need to create a new pattern lock along with new fingerprint unlocks.
stebaile said:
might need to factory reset to get the pin reset I suppose. Was hoping there was a file I could delete to reset the encryption.
Click to expand...
Click to collapse
Factory reset erases everything, leaving nothing to decrypt.
Your idea of "reset encryption" would make encryption useless if anyone could just remove the lock without the PIN/password.
stebaile said:
Just in case anyone has this issue of losing their pattern lock from a Nandroid restore I found the answer in a different thread. Use a file manager with root access such as Root Explorer, or use TWRP's file manager capability to delete the locksettings.* files in /data/system. Reboot and your device will no longer have a pattern lock. You will need to create a new pattern lock along with new fingerprint unlocks.
Click to expand...
Click to collapse
Rolo42 said:
Factory reset erases everything, leaving nothing to decrypt.
Your idea of "reset encryption" would make encryption useless if anyone could just remove the lock without the PIN/password.
Click to expand...
Click to collapse
Next time just read the TWRP FAQ
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139/page74
10. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
Disable security in Android?*before?*making a backup of data.
After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone.
Click to expand...
Click to collapse
Maik268 said:
Next time just read the TWRP FAQ
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139/page74
Click to expand...
Click to collapse
Is that referring to unlocking the screen or decrypting the device?
The question was referring to encryption.
When TWRP restores a backup, is it encrypted? (There's a few "it depends" to that question I would think.)
While Im not an avid flashaholic, Im curious about newer 7.0 builds. So recently I tried a new 7.0 build ( AICP ) and it asked me to add fingerprint. So I did. Of course, you cant just add a fingerprint, you need to add something else .. like a pattern or pin.
Well now it seems that pattern I added is everywhere. I need it to boot up my phone and / or get into my recovery / fastboot - everything. I remember reading this screwed someone when they flipped to another ROM. In my settings my security is "swipe" only, but I still need to add in the pattern I used on the previous 7.0 attempt ( I restored - it didnt work right )
Is there anyway to remove this damn thing?
When I flashed resurrection remix on my OP3 I changed back to oxygen os because the fingerprint scanner wouldn't work and when I booted into oxygen it said my pin was incorrect so to fix I simply flashed the original ota for oxygen 3.2.4 from OnePlus website , as a side note if you flash the original firmware and in twrp it says something like are you sure you want to boot as no OS is found just click yes and oxygen will boot up fully restored...
Not sure about AICP (or other custom ROMs), but stock OOS asks you if you want to use that password/pin/pattern at boot. If you check that checkbox, you'll have additional security everywhere (like you're describing), if not then it'll be used just for unlocking the screen, recovery and fastboot remain freely accessible.
Sent from my OnePlus 3 using Tapatalk
So now I can't even boot up my phone, says I need a password. No idea what it is, I certainly didn't set one. No recovery, I have fastboot though.
Will an img of some sort work?
EDIT: Ok, I can get into my phone using the numeric version of the pattern I put in ... but cripes lol, talk about a headache.
UltraBoykj said:
So now I can't even boot up my phone, says I need a password. No idea what it is, I certainly didn't set one. No recovery, I have fastboot though.
Will an img of some sort work?
EDIT: Ok, I can get into my phone using the numeric version of the pattern I put in ... but cripes lol, talk about a headache.
Click to expand...
Click to collapse
Seems the nougat install encrypted my phone.
UltraBoykj said:
Seems the nougat install encrypted my phone.
Click to expand...
Click to collapse
Not able to understand what you mean by that. Even on OOS, your phone is encrypted by default.
Explorer23 said:
Not sure about AICP (or other custom ROMs), but stock OOS asks you if you want to use that password/pin/pattern at boot. If you check that checkbox, you'll have additional security everywhere (like you're describing), if not then it'll be used just for unlocking the screen, recovery and fastboot remain freely accessible.
Click to expand...
Click to collapse
Other custom N ROMs also ask whether to require pin to boot.
UltraBoykj said:
So now I can't even boot up my phone, says I need a password. No idea what it is, I certainly didn't set one. No recovery, I have fastboot though.
Will an img of some sort work?
EDIT: Ok, I can get into my phone using the numeric version of the pattern I put in ... but cripes lol, talk about a headache.
Click to expand...
Click to collapse
I faced a similar issue when restoring my data after switching to CM14. But I could still go into recovery and normal boot. I couldn't but unlock the phone as it was asking a pin I hadn't set. I had to do a clean flash of the OS then.
Xceeder said:
When I flashed resurrection remix on my OP3 I changed back to oxygen os because the fingerprint scanner wouldn't work and when I booted into oxygen it said my pin was incorrect so to fix I simply flashed the original ota for oxygen 3.2.4 from OnePlus website , as a side note if you flash the original firmware and in twrp it says something like are you sure you want to boot as no OS is found just click yes and oxygen will boot up fully restored...
Click to expand...
Click to collapse
You must have gone from 3.2.6 to CM based rom, flash 3.2.4 then RR and home button/fingerprint will work fine
Its always the PIN you set as backup. Surprised you didn't try it earlier before panicking lol.
Hi..
I updated to Android N, and everything went fine, but I found it a little buggy and (my mistake) didn't realize xposed was not working yet, and there are some privacy modules I really would like.... So, I decided to downgrade back to MM.
As I am s-off, I booted into a rom.zip RUU (1.96.617.20). During the subsequent initial setup, I picked a screen pattern (to be used on restarts only)..for whatever reason, I decided to pick something different besides the rather easy pattern I had used since the M8... I will call this pattern B. Also during setup I copied over my internal storage files which I had backed up my laptop.
I then flashed the correct TWRP and then installed the correct SuperSU.zip. When I rebooted from here, Pattern B worked fine as I expected it to. I then thought I it would save time by restoring a nandroid (also 1.96.617.20) which had a lot of tweaks and other things. That nandroid backup however I know used my old screen pattern, which I will call Pattern A. That restore finished without error.
After reboot I got the restart screen asking for the pattern... I wasn't sure which one would work, so I first tried Pattern A which would have been used in the nandroid restore I just finished.... no luck. So I thought ok, I will try the pattern I used when I set up MM, Pattern B. But that didn't work...
This makes no sense... I have never used a screen unlock pattern other than Pattern A, and then today, I tried Pattern B which I know I remembered correctly because I used it once before I restored the nandroid.
When I search on how to solve this problem, I see "do a reset"... but wouldn't a reset be the same as restoring a nandroid backup? And since I just restored a nandroid and the pattern doesn't work, I am stumped.
Anyone have any clue how I can fix this???
Thanks in advance!
syntropic said:
Anyone have any clue how I can fix this???
Thanks in advance!
Click to expand...
Click to collapse
I found in the Nexus Forum someone with this problem... I rebooted into TWRP, and using the file manager I deleted these files:
/data/system/locksettings.db
/data/system/*.key
And this allowed me into the OS.
Thank you for anyone who has read this anyway!!
syntropic said:
I found in the Nexus Forum someone with this problem... I rebooted into TWRP, and using the file manager I deleted these files:
/data/system/locksettings.db
/data/system/*.key
And this allowed me into the OS.
Thank you for anyone who has read this anyway!!
Click to expand...
Click to collapse
A hint: You are talking about twrp, sill you are searching a nexus forum. Next time try twrp htc 10 thread instead
mirok said:
A hint: You are talking about twrp, sill you are searching a nexus forum. Next time try twrp htc 10 thread instead
Click to expand...
Click to collapse
I just googled "site:sea-developers.com pattern security not working HTC 10"
This wasn't strictly a TWRP issue... You could use TWRP or ADB to access the system partition IF the files which stored this security code were stored there (of this I wasn't entirely sure).
I didn't know for certain if these files were located in the same place or even under the same name as the Nexus, so I used TWRP's file manager to look around (starting in the above location) aa maybe I'd find them.
Sent from my HTC 10 using XDA Labs
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
StATicxTW0T said:
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
Click to expand...
Click to collapse
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
allstar21369 said:
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
Click to expand...
Click to collapse
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I have a rooted XT1710-01, also. If you are going to install Xposed and Gravity Box, I recommend not updating Magisk, above v14. After v15 and now v16, I have had issues with Automate It app and Tasker rules not working, until I uninstalled Xposed.
Downgrading Magisk versions requires flashing your stock ROM and basically starting over.
Motorola has not posted firmware for this model.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
So glad to see someone have it working and with a clear guide. I'm going to buy the phone this week.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Johmama said:
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Click to expand...
Click to collapse
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
allstar21369 said:
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
Click to expand...
Click to collapse
I didn't flash TWRP on my phone. I think I tried it once and it failed for some reason, so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup. Flashing it is up to you, I've always flashed a custom recovery but on this phone I'm keeping the original recovery so I can get an OTA. On my Nexus devices I don't care about OTA because I just flash ROMs all the time so it's no big deal.
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked. As far as turning off encryption, I'm not sure if there's a way to do that. There could be, but to turn it off, it wipes your data as a security measure.
Johmama said:
so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup.
Click to expand...
Click to collapse
Yeah, I can't backup my ROM most likely because I don't have an FBE password. When I go to backup my ROM in TWRP it fails.
Johmama said:
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked.
Click to expand...
Click to collapse
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
allstar21369 said:
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
Click to expand...
Click to collapse
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Johmama said:
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Click to expand...
Click to collapse
Okay. I just wiped and re-set up everything and still no FBE password was asked for OR works when I go into TWRP. I'm using TWRP 3.1.1-0... I suppose I'll try it all again using TWRP 3.2.1-0-albus after deleting data.
*Edit: I did exactly what I just said I was doing booted TWRP 3.2.1-0-albus instead of 3.1.1-0 and when I it booted up and asked me for a decryption password I entered the pin I set up previously and it has been stuck at the "Mount, Trying Decryption" screen for a long time... but it's not frozen. It says "Updating partition details... ...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block device: '/dev
/block/dm-0'
Updating partition details...
...done"
And the progress bar/thing at the bottom is still animated like it's working... no forward or back buttons or anything and turning off/on the screen hasn't done anything... not really sure what to do here... I don't want to unplug it and brick my phone or force it off...
*Edit 2:
I now have it all sorted out.
TWRP never finished trying to decrypt data so I long pressed the power button and eventually went here -> https://forum.xda-developers.com/z2-play/development/twrp-moto-z2-play-t3729531 , downloaded "twrp_albus_3.1.2_r18_64.img" and in adb used the command:
fastboot boot twrp_albus_3.1.2_r18_64.img
This TWRP looks a bit different than all of the others but it let me boot up and use my recently created PIN code to actually decrypt my data and make a full backup. After that I just installed Magisk (the latest one, 16.4) as indicated in this guide -> https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792 and everything is fine. I never even flashed TWRP, just booted it.
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
joefuf said:
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
Click to expand...
Click to collapse
I didn't want updates, especially the oreo "upgrade".
pizza_pablo said:
I didn't want updates, especially the oreo "upgrade".
Click to expand...
Click to collapse
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
joefuf said:
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
Click to expand...
Click to collapse
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Double - double \_0_/
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
Yeah, very understandable. It really is superfluous to the general experience.
allstar21369 said:
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
Click to expand...
Click to collapse
Thank you sir! Keep me posted. I'm posting everywhere right now to learn the new methods so I know if there ever comes a time. This is my first phone since my Motorola Droid 4. Back then it was one click root, install and run Safestrap apk to get custom recovery, boot into custom recovery and flash zips to your heart's content. I'm sure this will be as "simple" once I learn, but it's pretty daunting in prospect.
I made this so let me know if it works I tested it on my phone and my girlfriends phone it's for the Hannah varient which is MetroPCS/T-Mobile this was my first ever project I updated it today try out the new one
twrp by SIR KRIEGER and decrypting files credits go out to authors of those files
https://drive.google.com/folderview?id=105qE_sXIiCF2W9IffzSMpfFUXQc7N-dz
sirkrieger1993 said:
I made this so let me know if it works I tested it on my phone and my girlfriends phone it's for the Hannah varient which is MetroPCS/T-Mobile this was my first ever project ill be updating g the version tomorrow to the newest twrp source
twrp by SIR KRIEGER
https://drive.google.com/file/d/1ylBbg4gZt4tXGz-EBnrYtcO9AjXA2qNv/view?usp=drivesdk
Click to expand...
Click to collapse
yes it seems to not work at 1st on first boot! doesnt detect storage 0mb
but when i hit wipe/advanced wipe/data then
hit repair change file system then hit change file system
to ext2 then back ext2
it detects internal storage
but when i booted into android it wanted to encrypt data and wipe it.
so i manually wiped data in recovery then rebooted an bam it works
an it still detects my internal storage........yay thank you so much
it just doesnt detect my micro sd card
brandonlee96 said:
yes it seems to not work at 1st on first boot! doesnt detect storage 0mb
but when i hit wipe/advanced wipe/data then
hit repair change file system then hit change file system
to ext2 then back ext2
it detects internal storage
but when i booted into android it wanted to encrypt data and wipe it.
so i manually wiped data in recovery then rebooted an bam it works
an it still detects my internal storage........yay thank you so much
it just doesnt detect my micro sd card
Click to expand...
Click to collapse
I'll look into trying to fix it but my SD card words so that's weird
Ok so I tried it on another friend of mines phone and his sd card and everything is working fine so I'm really confused why yours wouldn't work????
Me too I really don't understand it.
I'll keep looking into it for you...I wish other people would let me know how it's working on there device
I didn't realize people were still having issues with twrp on the tmo/Metro variant. Id have to double check with Aeorsyn but im pretty sure we posted one somewhere in this forum that works...at least for me...perfectly with the exception of the time being off every now and then. It flashes zip and image files, makes backups, restores, wipes, works with twrp themes, reads internal and external sd, and even usb via otg. I've been running it for a couple months now without issue. Is there something im missing that people are trying to do that I'm just blind too? Lol if anyone wants a link to the twrp I'm using just lemme know.
Sent from my Motorola moto e5 plus using XDA Labs
theUsualSuspexx said:
I didn't realize people were still having issues with twrp on the tmo/Metro variant. Id have to double check with Aeorsyn but im pretty sure we posted one somewhere in this forum that works...at least for me...perfectly with the exception of the time being off every now and then. It flashes zip and image files, makes backups, restores, wipes, works with twrp themes, reads internal and external sd, and even usb via otg. I've been running it for a couple months now without issue. Is there something im missing that people are trying to do that I'm just blind too? Lol if anyone wants a link to the twrp I'm using just lemme know.
Click to expand...
Click to collapse
Please
I tried the one that was posted and I couldn't flash anything so I tried the James varient but I couldn't flash it I had to fastboot boot it
theUsualSuspexx said:
I didn't realize people were still having issues with twrp on the tmo/Metro variant. Id have to double check with Aeorsyn but im pretty sure we posted one somewhere in this forum that works...at least for me...perfectly with the exception of the time being off every now and then. It flashes zip and image files, makes backups, restores, wipes, works with twrp themes, reads internal and external sd, and even usb via otg. I've been running it for a couple months now without issue. Is there something im missing that people are trying to do that I'm just blind too? Lol if anyone wants a link to the twrp I'm using just lemme know.
Sent from my Motorola moto e5 plus using XDA Labs
Click to expand...
Click to collapse
Please ! , Thanks & Merry XMas!
Twrp deletes stock rom
Maybe you can help me out, maybe im missing something. I have the g5 (hannah) MetroPCS variant. Everytime I flash TWRP it deletes my system. Ive tried 3 other TWRPs with no luck. One way or another I cannot boot, (bad key). Then I reflash my stock rom and try again. Ive tried with and without allowing system modifications with no avail. However when I first flash and boot into recovery there is a screen asking to decrypt. it asks to enter a password but the screen doesnt respond to touch for the pattern dots. Does that decrypting need to happen for TWRP to work correctly? Thanks
scaicardi said:
Maybe you can help me out, maybe im missing something. I have the g5 (hannah) MetroPCS variant. Everytime I flash TWRP it deletes my system. Ive tried 3 other TWRPs with no luck. One way or another I cannot boot, (bad key). Then I reflash my stock rom and try again. Ive tried with and without allowing system modifications with no avail. However when I first flash and boot into recovery there is a screen asking to decrypt. it asks to enter a password but the screen doesnt respond to touch for the pattern dots. Does that decrypting need to happen for TWRP to work correctly? Thanks
Click to expand...
Click to collapse
dm me, I have a working twrp build and stock system image on google drive
scaicardi said:
Maybe you can help me out, maybe im missing something. I have the g5 (hannah) MetroPCS variant. Everytime I flash TWRP it deletes my system. Ive tried 3 other TWRPs with no luck. One way or another I cannot boot, (bad key). Then I reflash my stock rom and try again. Ive tried with and without allowing system modifications with no avail. However when I first flash and boot into recovery there is a screen asking to decrypt. it asks to enter a password but the screen doesnt respond to touch for the pattern dots. Does that decrypting need to happen for TWRP to work correctly? Thanks
Click to expand...
Click to collapse
Did you try using the decrypt.zip
sirkrieger1993 said:
Did you try using the decrypt.zip
Click to expand...
Click to collapse
No I have not...I will try and find a copy.
sirkrieger1993 said:
Did you try using the decrypt.zip
Click to expand...
Click to collapse
I used Sir's (THANKS!) twrp and just booted it without flashing,(worked great!) it boots fine but asks for unlock pattern and doesn't accept the one I have set, (I'm guessing this is where decrypt.zip comes into play, but unsure), I hit cancel and KEPT READ ONLY , then made individual backups of boot + system + system.image
I also get the Bad key however I believe this is normal after unlocking the bootloader.. If you wait a bit it should still eventually boot.. I'd like to try to make a boot animation..
scaicardi said:
No I have not...I will try and find a copy.
Click to expand...
Click to collapse
turns out its not deleting the rom. its a problem with the boot image or encryption . When i first boot into twrp i cannot see internal storage. if i change my partition from ext4 then back to ext2 it shows up and the decrypt.zip is successful. however when i reboot phone it hangs at motorola screen. I then went back to fastboot and flashed stock boot.img and the phone almost booted up. I got hung at decryption unsuccessful perform factory reset. I dont know why this is so complicated any suggestions.
kinda sucks i go in for surgery and wake up and find a new twrp for hannah good luck ill be deleting my guide instead of working on twrp bye
Good to see work being done on the device!
skullkid383 said:
kinda sucks i go in for surgery and wake up and find a new twrp for hannah good luck ill be deleting my guide instead of working on twrp bye
Click to expand...
Click to collapse
Bro no keep it up don't hurt to have two twrps that worrk for are device
Project89Odin said:
Good to see work being done on the device!
Click to expand...
Click to collapse
Thanks bro I got a few gsi ROMs to boot up and work also to I'll post a thread soon on which ones I got working so there's more custom ROMs that work