So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
jlee08517 said:
So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
Click to expand...
Click to collapse
I have the same problem on LineageOS. I even removed password before booting to TWRP, which usually caused the encryption message in twrp asking for a password.
jlee08517 said:
So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
Click to expand...
Click to collapse
Oh boy! Your the first I've seen with this one. I've used that method on the 6p many many times without issue. The P2XL is a different beast evidently. I'm sure the code master guys could figure it out, but that's not me. Did you make a backup before you started (S.O.P)?? I always do that before any update, and then move it to the pc before I begin. Been burned to many times with this stuff. I'm afraid the only advice I can give is to do a clean install of the latest update, then restore your data from a previous backup through twrp. Sorry my friend...been there...done that! ??
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
Btw...this is a known issue with twrp now until it's updated. You have to remove all lock screen security in order to use TWRP effectively. Unfortunately, that does you no good I know. But, at least, now you know.
Badger50 said:
Oh boy! Your the first I've seen with this one. I've used that method on the 6p many many times without issue. The P2XL is a different beast evidently. I'm sure the code master guys could figure it out, but that's not me. Did you make a backup before you started (S.O.P)?? I always do that before any update, and then move it to the pc before I begin. Been burned to many times with this stuff. I'm afraid the only advice I can give is to do a clean install of the latest update, then restore your data from a previous backup through twrp. Sorry my friend...been there...done that! ??
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
Btw...this is a known issue with twrp now until it's updated. You have to remove all lock screen security in order to use TWRP effectively. Unfortunately, that does you no good I know. But, at least, now you know.
Click to expand...
Click to collapse
Well of course I made a twrp backup on the device before I did all this but I can't get to any of those since twrp can't decrypt...
Remember I deleted the locksettings since twrp won't take my pattern? Haha it was just unlucky on my part.
jlee08517 said:
Well of course I made a twrp backup on the device before I did all this but I can't get to any of those since twrp can't decrypt...
Remember I deleted the locksettings since twrp won't take my pattern? Haha it was just unlucky on my part.
Click to expand...
Click to collapse
Wasn't trying to criticize your method, but you'd be surprised how many don't do backups then flash away...then something goes wrong, and, well, you know the rest. Since you tried dirty flashing the factory image, I'm afraid all you can do is clean instal the factory image and wipe it clean. Stupid question, but if you fastboot twrp again, are you still in the same boat? Probably so, but thought I'd ask.
Badger50 said:
Wasn't trying to criticize your method, but you'd be surprised how many don't do backups then flash away...then something goes wrong, and, well, you know the rest. Since you tried dirty flashing the factory image, I'm afraid all you can do is clean instal the factory image and wipe it clean. Stupid question, but if you fastboot twrp again, are you still in the same boat? Probably so, but thought I'd ask.
Click to expand...
Click to collapse
Ah I didn't mean to come off that way. It's all good. Yeah I probably should write a PSA on twrp about this. So I went back to twrp and everything is gibberish since it's encrypted. I tried adb but it wasn't able to find the /sdcard path. I'm guessing that's also because the device was not being decrypted? And i tried to reboot into the safe mode. All kinds of mess. I just gave up and formatted the device. There goes all my /sdcard stuff.... I really need to start backing up titanium into the cloud..
jlee08517 said:
Ah I didn't mean to come off that way. It's all good. Yeah I probably should write a PSA on twrp about this. So I went back to twrp and everything is gibberish since it's encrypted. I tried adb but it wasn't able to find the /sdcard path. I'm guessing that's also because the device was not being decrypted? And i tried to reboot into the safe mode. All kinds of mess. I just gave up and formatted the device. There goes all my /sdcard stuff.... I really need to start backing up titanium into the cloud..
Click to expand...
Click to collapse
Sorry man, that sucks! I've done that more times than I can remember. Going forward, after I backup everything, including all my apps on TiBu, I save my TiBu file to my pc, then transfer it back after I'm back up and running. Best of luck to ya bro ?
A similar saga can be found here. For an encrypted data partition there is still no solution, as it seems, see my posting in that same thread.
Related
Hi everyone,
I recently upgraded my cwm from 6.0.1.2 non touch to 6.0.2.3 touch with Odin and when doing a backup it takes a really long time and eventually fails about halfway through backing up /data. I thought maybe the recovery got corrupt or something so I used rom manager to upgrade to 6.0.3.1 non touch and tried again. This time it took longer to backup /system and while backing up data the phone rebooted. I've been running CM10.1 nightlies for quite some time now and kt kernel with no issues, and I always backup before flashing but I need to fix this before i flash anymore nightlies. Anyone else have this issue before? I've been wanting to clean wipe/install my phone for a while now but I just don't have the time right now.
My phone is a d2can on Bell. I know that's relatively irrelevant information but doesn't hurt to mention.
Also I installed the same 6.0.2.3 touch on a GS3 that I just got for my girlfriend and it backs up fine.
Also apparently in attempting these backups it somehow messed up some of my settings. I had a sign in error for gmail which went away as soon as I hit sync now in the Google account, although I had to sign back in to Facebook. It also changed a bunch of my sound settings... Imagine my surprise as I get a Whatsapp message and an Opeth song starts blaring (and also doesn't stop upon checking the message...) lol.
I back up my apps and settings with Titanium Backup so I can easily restore everything when I have a chance to do a clean wipe and install, but how do I fully wipe/reinstall the recovery to fix this backup issue? Maybe I just have to hit the factory reset button in the recovery?
Lessaj said:
Also apparently in attempting these backups it somehow messed up some of my settings. I had a sign in error for gmail which went away as soon as I hit sync now in the Google account, although I had to sign back in to Facebook. It also changed a bunch of my sound settings... Imagine my surprise as I get a Whatsapp message and an Opeth song starts blaring (and also doesn't stop upon checking the message...) lol.
I back up my apps and settings with Titanium Backup so I can easily restore everything when I have a chance to do a clean wipe and install, but how do I fully wipe/reinstall the recovery to fix this backup issue? Maybe I just have to hit the factory reset button in the recovery?
Click to expand...
Click to collapse
I would download Goo Manager and flash TWRP, forget CWM. If you hit factory reset then you are going to have to go through the clean install process. If I were you I'd flash TWRP and then clean install whatever your into. It'll take maybe 30 minutes to get the rom setup the way you want it and you'll have the piece of mint that everything was cleanly wiped and you have a fresh start.
I guess I can try TWRP. I don't really get why everyone rags on CWM, it works just fine. I was using 6.0.1.2 for about 7 months without a hitch, this is the first problem.
If I did a clean wipe I'd still backup my pictures and my apps from TiBu and restore everything after wiping, it would just take a while. I don't have an external SD so it's all on the internal. I might have some time tonight to try it out.
Lessaj said:
I guess I can try TWRP. I don't really get why everyone rags on CWM, it works just fine. I was using 6.0.1.2 for about 7 months without a hitch, this is the first problem.
If I did a clean wipe I'd still backup my pictures and my apps from TiBu and restore everything after wiping, it would just take a while. I don't have an external SD so it's all on the internal. I might have some time tonight to try it out.
Click to expand...
Click to collapse
I would copy your pictures (or any other irreplaceable files) to a computer for safe keeping just in case it hits the fan. Apps are whatever, but you can't retake pictures so I'd back them up somehow; computer, dropbox, etc.
Same Issues on a SG3
I also recently upgraded and have been having the same issues. It doesn't seem to matter whether I enter recovery through or use Rom Manager to enter into in recovery. Each time the back up fails. I had just switch back after having TWRP issues where it back up would not fail but when they were to be use in recovery I would get a message before restarting stating I didn't actually back up the OS. ( I realize it might not be reliant info but I've learn a little to much is better than not at all)
I've noticed it will fail and restart only when I try to back up to my SD card. Yesterday it was giving me trouble by mounting and unmounting repeatedly. I thought I had fixed all the problems after I did a diskcheck and had my computer scan and fix all found errors.
If anyone can link me to a previous version of CWM or help with this back up issue you'll have the OP's and my appreciation.
Thanks in advance.
---------- Post added at 03:36 PM ---------- Previous post was at 03:00 PM ----------
Are you backing up to an SD card or the phone it's self?
Lessaj said:
Hi everyone,
I recently upgraded my cwm from 6.0.1.2 non touch to 6.0.2.3 touch with Odin and when doing a backup it takes a really long time and eventually fails about halfway through backing up /data. I thought maybe the recovery got corrupt or something so I used rom manager to upgrade to 6.0.3.1 non touch and tried again. This time it took longer to backup /system and while backing up data the phone rebooted. I've been running CM10.1 nightlies for quite some time now and kt kernel with no issues, and I always backup before flashing but I need to fix this before i flash anymore nightlies. Anyone else have this issue before? I've been wanting to clean wipe/install my phone for a while now but I just don't have the time right now.
My phone is a d2can on Bell. I know that's relatively irrelevant information but doesn't hurt to mention.
Also I installed the same 6.0.2.3 touch on a GS3 that I just got for my girlfriend and it backs up fine.
Click to expand...
Click to collapse
Icon000 said:
Are you backing up to an SD card or the phone it's self?
Click to expand...
Click to collapse
I'm backing up to the phone itself, I do not have an SD card.
Lessaj said:
I'm backing up to the phone itself, I do not have an SD card.
Click to expand...
Click to collapse
So was your problem fixed by switching to TWRP?
I know when I had tried using TWRP, the issue I was having after back ups, was it would ask me if I was sure I wanted to leave since it said I didn;t install a OS.
Does that help you to find a solution?
post-mortem said:
So was your problem fixed by switching to TWRP?
Click to expand...
Click to collapse
post-mortem said:
So was your problem fixed by switching to TWRP?
Click to expand...
Click to collapse
Yes.
I'm not very good at Android technical stuffs as I'm new to it but learned decent basic knowledge before doing any rooting and flashing stuffs.
To start off, I installed ARHD 22.1 back in December and then upgraded to ARHD 30.1 just yesterday, successfully. I'm S-On, using Taiwan HTC One M8x 2.5 ghz unlocked.
I then decided to add the eXtremeBeats audio mod which is compatible to Android L. I followed the instruction there ( DL File, put to phone, flash via recovery, wipe cache & dalvik, reboot ). At the reboot the problem starts, after optimizing the apps, and then it says "starting apps" there it got stuck, I waited it for an hour and a half and decided to force shut my phone. So after turning it on again, it's now stuck on the HTC logo only. I decided to re-install ARHD 30.1 at that same day, successfully installed but when the phone starts, it says "Unfortunately, HTC Dot View has stopped" then followed by "Unfortunately, System UI has stopped". So yeah, I don't have any on screen bottons on my phone, no slide down notification, but can access apps ( no going back though ). I tried to wipe cache & dalvik again, tried re-installing the ARHD 30.1 again for the 3rd time, no luck.
I searched my problem at Google but mine's different. Their "Unfortunately, System UI has stopped" is like soldemly happening in the middle of phone usage and returning back to normal after some seconds, mine gets that problem at the very start up and the UI doesn't return.
What did I do wrong? What must I do? Thanks in advance!
Edit: I noticed that my OS is missing where it's supposed to say something like 3.28.xxx.x. I wiped everything including system at the time I install ARHD 30.1 the second time (where the problem occurred). I think this might have caused the problem? How do I fix this?
Restore your nandroid and see what happens.
redpoint73 said:
Restore your nandroid and see what happens.
Click to expand...
Click to collapse
Yes, I'm currently trying to figure out on how to do this. I'm having problems.
I have a Nandroid backup file in my PC. But I don't know how to push it to /sdcard/TWRP/BACKUP/. I tried the pushing file tutorial via mini-sdk and some cmd commands from ARHD's website tutorial, it can push to /data but I can't get it to work on /sdcard ( I tried to >mount /sdcard == gives error ). The other way I know is to transfer the Nandroid backup file from PC to phone normally via the file copy pasting, my computer can recognize my phone having the ARHD 30.1 (w/ UI problem) installed and USB Debugging on, though I can't access the storage or transfer files.
How do I push my Nandroid backup file from PC to /sdcard/TWRP/BACKUP ... ? Any advice please? I think this will solve my issue.
TheMabaet said:
How do I push my Nandroid backup file from PC to /sdcard/TWRP/BACKUP ... ? Any advice please? I think this will solve my issue.
Click to expand...
Click to collapse
Yes, the syntax for adb pushing a TWRP backup to internal storage can be challenging. If you have a removable SD available, that might be easier, change the save location in TWRP to that. Then make a "mock" backup, purely so that the TWRP folder is created on the SD card. Then either copy/paste your nandroid to the SD with your phone connected to your PC; or use a card reader connected to your PC.
Alternately, you can try to mount the internal storage in TWRP instead of in the OS. That might work better.
redpoint73 said:
Yes, the syntax for adb pushing a TWRP backup to internal storage can be challenging. If you have a removable SD available, that might be easier, change the save location in TWRP to that. Then make a "mock" backup, purely so that the TWRP folder is created on the SD card. Then either copy/paste your nandroid to the SD with your phone connected to your PC; or use a card reader connected to your PC.
Alternately, you can try to mount the internal storage in TWRP instead of in the OS. That might work better.
Click to expand...
Click to collapse
Amazing! I understand the first method, but the alternative... can you explain a bit further? As I tap the Mount button at the main page of TWRP, it says "Select Partitions to Mount:", having System, Cache, Data, Micro SDCard, USB-OTG as options. And then nothing else to do, I see no any other button. Clearly I didn't understood the practice, and I google "How to mount internal storage to TWRP" but somehow didn't get any good result. Could you please tell me how it is done or link me to a guide?
Edit: The first method is fine, though I'd like to know how the second one is done. I apologize if you find me cumbersome but I'd like to learn, might come in handy at some peculiar point. I'm curious as what you said that that might work better but I can't perform the latter, it got me really cheesy
EDIT 2: I managed to do the BACKUP. But now it got stuck to BOOT LOOP. I tried to wipe data, cache, and dalvik... but still it BOOT LOOP. What now?
I'm having a similar problem, did you manage to fix it? How? Thanks.
NOT flashing the correct firmware / Kernel is a most frequent cause of SystemUI crashes. Flash the correct firmware/Kernel to correct this.
wth is wrong with my backup?
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''. what gets me crazy and confused is that it works perfectly sometimes when i erase the system and everything then when i restore the same lollipop backup and here we go again, system ui has freakin' stopped! this doesnt happen to any other kitkat backup only lollipop.
i have twrp recovery 2.8.02
my hboot is 2.49
i am currently having s on.
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!
kimosab said:
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''. what gets me crazy and confused is that it works perfectly sometimes when i erase the system and everything then when i restore the same lollipop backup and here we go again, system ui has freakin' stopped! this doesnt happen to any other kitkat backup only lollipop.
i have twrp recovery 2.8.02
my hboot is 2.49
i am currently having s on.
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!
Click to expand...
Click to collapse
Hboot should be 3.19 in Lollipop. 2.49 is Android4.4.2 KitKat
Also, update your recovery. 2.8.7.0 works wonderfully.
Bottom line is you need to update your firmware before you try to restore a Lollipop backup.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Get into ADB/fastboot and do fastboot getvar all
Post the readout here minus your IMEI and serial# (that's private information you should never post on a public forum)
With that information, it will help us to direct you on the proper way to update, and to provide you with the proper downloads for your device.
kimosab said:
i am sick of htc and their stupid s off and on thing like why should we pay 25 dollars i mean android hacking should be open source right? convert 25 $ to riyals and i cold live for a week, happily!!!
Click to expand...
Click to collapse
Why bash on HTC and sunshine s-off ? You unlocked it, flashed twrp.....that's something HTC didn't nor the guys from sunshine. And you don't need s-off, it's not mandatory but it can make it easier.
I would kindly suggest to drop the ignorant attitude towards the wrong people and focus on the problem you have to solve.
kimosab said:
alright is there a specific solution to this? me and my mother both have the same phone so i took the lollipop backup from her, renamed it like mines and restored it. once i finish the restore and boot up im greeted with ''unfortunately system ui has stopped''.
my hboot is 2.49
Click to expand...
Click to collapse
That is not a valid hboot number for the M8 (which this forum section is specific to). I think you have a One Max.
But as mentioned, you can't just migrate a nandroid from one phone to another. The firmware needs to match also. Running a LP nandroid with KK firmware is going to result in issues.
---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
xunholyx said:
Hboot should be 3.19 in Lollipop. 2.49 is Android4.4.2 KitKat
Click to expand...
Click to collapse
Corresponding hboot for Android 4.4.2 on this device is 3.16.
---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------
Mr Hofs said:
Why bash on HTC and sunshine s-off ? You unlocked it, flashed twrp.....that's something HTC didn't nor the guys from sunshine. And you don't need s-off, it's not mandatory but it can make it easier.
I would kindly suggest to drop the ignorant attitude towards the wrong people and focus on the problem you have to solve.
Click to expand...
Click to collapse
Agreed. S-off isn't the problem, and not needed to remedy the previous user's issue. Main problem is lack of research before messing with the phone.
found an awesome solution. i used to have a nandroid of android 4.4.3, so i restored it, didn't do any kind of wipe and then restored my moms nandroid backup of android L. its working great! i have the htc one m7 dual sim m7_cdug 802w
--delete
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
WyldOne91 said:
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
Click to expand...
Click to collapse
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Badger50 said:
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Click to expand...
Click to collapse
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
WyldOne91 said:
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
Click to expand...
Click to collapse
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Badger50 said:
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Click to expand...
Click to collapse
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Badger50 said:
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
Click to expand...
Click to collapse
Yeah for sure. I'm always willing to learn!
CyberpodS2 said:
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Click to expand...
Click to collapse
Yeah I actually already ran a backup with Titanium Backup and moved it to my PC last night just in case I did something stupid haha but I appreciate the tips!
Long story short, my phone bootlooped. I have a pattern set and cannot get into twrp because of it. I dirty flashed the rom again, but got stuck at the "android is starting" screen. I wiped and flashed the rom and got the 'Just a sec' screen of death. Then I wiped, and flashed the stock OS and got the 'Just a sec' SOD again.
I just want to figure out a way to pull my files from my phone before I factory reset. I cannot access ADB since I can't boot. I can only get to fastboot and an encrypted version of twrp. I deleted the locksettings.db to see if that would help, but no luck.
Any ideas?
Akomack said:
Long story short, my phone bootlooped. I have a pattern set and cannot get into twrp because of it. I dirty flashed the rom again, but got stuck at the "android is starting" screen. I wiped and flashed the rom and got the 'Just a sec' screen of death. Then I wiped, and flashed the stock OS and got the 'Just a sec' SOD again.
I just want to figure out a way to pull my files from my phone before I factory reset. I cannot access ADB since I can't boot. I can only get to fastboot and an encrypted version of twrp. I deleted the locksettings.db to see if that would help, but no luck.
Any ideas?
Click to expand...
Click to collapse
I think you might be in luck. Dees_Troy just posted to Twitter that he was able to find the time to get TWRP to decrypt Pixel and other devices on the Feb Security patch. Not sure when he will post updated files(they aren't there yet)...but perhaps you might be able to fastboot boot the new version once he releases it and maybe that will allow you to get back into your phone.
(From Twitter): Dees_Troy: Finally able to decrypt the February security patch on Pixel and other FBE devices:
https://plus.google.com/+DeesTroy/posts/By3p15BHJD5
Good luck!
Boot twrp 3.2.1-0. Wipe the lockscreen databases.
Boot 3.2.0-0 and do what you need to do.
I think.
Good luck.
Sent from my Pixel C using Tapatalk
sb1893 said:
I think you might be in luck. Dees_Troy just posted to Twitter that he was able to find the time to get TWRP to decrypt Pixel and other devices on the Feb Security patch. Not sure when he will post updated files(they aren't there yet)...but perhaps you might be able to fastboot boot the new version once he releases it and maybe that will allow you to get back into your phone.
(From Twitter): Dees_Troy: Finally able to decrypt the February security patch on Pixel and other FBE devices:
https://plus.google.com/+DeesTroy/posts/By3p15BHJD5
Good luck!
Click to expand...
Click to collapse
I couldn't wait that long. I had a useless phone without factory resetting it. I'm glad DeesTroy is working on this though, really annoying having to remove lock settings to use twrp. Not to mention if you get stuck in a bootloop with it enabled, you're pretty much SOL. Luckily I had titanium backups of my apps from the end of January on a pen drive, I'm going to start uploading them to drive because of this.
pkelly517 said:
Boot twrp 3.2.1-0. Wipe the lockscreen databases.
Boot 3.2.0-0 and do what you need to do.
I think.
Good luck.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It doesn't work. I believe Google recently fixed that loophole. I deleted the locksettings databases, which I believe would work to get past the lockscreen when the phone is booted, but it won't allow me to decrypt in twrp.
Either way I had to factory reset and start from scratch. I spent a good 2-3 hours trying to figure anything out to try to recover my titanium backups, with no luck.
Next time, fastboot update the factory image without -w, either manually through terminal or edit the bat file so It doesn't wipe the internal storage.
Can you get into bootloader screen? If so, you could flash TWRP from ADB maybe.
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe
Some details might help .....
RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe
Click to expand...
Click to collapse
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.
nezlek said:
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.
Click to expand...
Click to collapse
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?
Ouch
RobeStar said:
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?
Click to expand...
Click to collapse
FIRST - Always better (in my book) to flash with TWRP. Others my have different experiences and opinions but it has never let me down.
You predicament is, in a word, not good. If I were you, I would first try re-flashing the previous Lineage build via TWRP. Unfortunately you are probably going to lose some data in all of this. If anything works well enough to backup your system and data partitions, do that first and move that to removable storage and remove it so it is SAFE. Maybe you have Titanium Backup and can do some of the pieces you need ?? Boot into TWRP and re-flash the build file that was on it before this all started. If that "dirty" flash doesn't give you anything useful, try wiping cache, davlik, etc... and repeating (a full factory reset). If THAT fails, download the zip file(s) - LOS, su-add-on, gapps, etc... and pretend you are doing it for the first time (maybe even wipe data and system but then, your stuff is GONE without a backup). But at this point, what have you got to lose? ASSUMING you get things back to a proper working condition, only then do a complete backup and ponder starting over again. The radio, who knows? Losing the IMEI info is much more of a problem since carriers will often not like that. I know it is trivially easy to restore IMEI data on an MTK device, but yours I have no personal knowledge of. There ARE places that will apparently do it for you if you do a little judicious web searching and are willing to part with a little cash for it, but SOMEBODY out here on XDA has to know how to do it for what you have.
And I'm NOT going to say somebody told you so, but they did. NEVER do this sort of thing without a backup in hand or a willingness to wave goodbye to whatever you have installed on or done to a device. I spend not more than 10 minutes a week doing a Nandroid of devices I use regularly. It has saved me a hell of a lot more time than that the very few times I've needed it. So, with apologies for rubbing salt in the wound, it is always better to have 'em and not need 'em than to need 'em and not have 'em
One thing is pretty certain. Most of us rarely repeat this sort of thing. Good Luck.
Can someone flash My phone without my pin
Even though I encrypted it???
RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally....
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3528508
If all else fails, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device as well.
https://forum.xda-developers.com/showthread.php?t=3527639
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Yesterday, installing OTA and going from 20191008 to 20191010 destroyed my IMEIs on my Moto X4 payton.
Any idea why this happened?