Related
I have a Oneplus 3 running TWRP 3.0.2-1 and the last stable kernal I had was cyanogenmod 14.1 I have access to fastboot and TWRP recovery but I can't mount the data partition and i'm pretty certain its corrupted and I don't know how to fix it.
Yesterday I was trying out CM14.1 and ended up deciding that I would rather go to OxygenOS 3.5.6 open beta 7 instead. TWRP wouldn't load so I freaked out and flashed several versions of TWRP in a misguided attempt to fix the problem. At some point i'm pretty sure I also flashed the OxygenOS 3.5.6. Somehow I managed to get TWRP working but I can't boot into Oxygen. I get the Oxygen icon for a few seconds and then the phone reboots.
There was nothing important on the phone so i'm not concerned with saving anything. I just want to return to a working state and I have no idea how to do that. It seems like I somehow have to repair my data partition or create a new one? I don't know. Please help or guide me in the right direction!
Solved
I noticed an option in TWRP to format the data partition and that solved the problem. I was able to load Oxygen OS onto it like I intended and now all is well!
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
EDIT:
I've solved the issue. After re-flashing the RUU, flashing TWRP, and re-rooting over and over, I figured out what seemed to be going on.
In case anyone else has the same problem as me, here was my solution:
Starting from stock, I went ahead and flashed my phone with the latest TWRP compatible with N (3.0.3.0 at this current time). Afterwards I flashed LineageOS and GApps. As usual, upon reboot, the phone needed a password to get in. So, I rebooted to Recovery, which also required a password. I hit cancel, wiped the phone with a factory reset, formatted all data, and restarted. This did the trick, and I've been running LineageOS 7.1 with no problems whatsoever!
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
Click to expand...
Click to collapse
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
5m4r7ph0n36uru said:
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
dladz said:
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
Click to expand...
Click to collapse
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
dreDREb13 said:
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
Could have thought of that myself. Encryption used by Cyanogen/Lineage is different to HTCs encryption used on Sense based ROMs. Thanks for your feedback.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
There is no password and I've had it out in the cm thread, apparently it's common knowledge, which we've both found out its not, there is no password either so you did what was required.
Also, click thanks instead of saying mate [emoji6]
Glad you're back up and running.
thanks had same issue when installing Lineage 14.1 nightly on my HTC 10 today, which already had twrp on it and the stock rom - your solution worked.
i.e.
turn off device
hold volume down while pressing power for few seconds
choose reboot to bootloader from menu
choose boot to recovery mode
hit cancel when prompted for password
choose wipe from twrp, use default options
reboot
no more password prompt.
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message "android.process.media has stopped".
I've used the following installation procedure:
1. Starting with the stock Samsung Android v4.4.2, I used Odin v3.1.2, to root the device, by installing
CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md
2. I used Odin to install picassowifi TWRP v2.8.7.0. I didn't use the latest v3.1.1-0, because it reboots the
device while making Nandroid backups. Available here
https://eu.dl.twrp.me/picassowifi/
3. I copied several versions of Lineage OS amd Gapps (see below) to the device's SD card
4. I used TWRP to wipe the cache/dalvic/data/system each time, using the Wipe->Advanced option
5. I used TWRP to install the Lineage OS amd Gapps as an atomic operation on the device
6. After installation, I rebooted from TWRP:
- without rooting: I get the message "Google Services Framework keeps stopping"
- with rooting, by installing SuperSU: The device enters into a boot loop, displaying the sliding Lineage logo
I followed the same procedure to update my Samsung Galaxy S4 Mini, and it worked flawlessly.
I tried the following Lineage OS versions, available here:
https://download.exynos5420.com/LineageOS-14.1/n2awifi/
lineage-14.1-20170506-UNOFFICIAL-n2awifi.zip
lineage-14.1-20170715-UNOFFICIAL-n2awifi.zip
I also tried the folowing Lineage OS versions, available here:
https://download.lineageos.org/n2awifi
lineage-14.1-20170608-nightly-n2awifi-signed.zip
lineage-14.1-20170713-nightly-n2awifi-signed.zip
I tried the following versions of Gapps, available here (32-bit arm, Android v7.1, stock variant):
http://opengapps.org/?api=7.1&variant=stock
open_gapps-arm-7.1-stock-20170505.ziip
open_gapps-arm-7.1-stock-20170711
I tried several combinations of these 2 packages. With all the combinations I tried, I got the results summarised above.
This post suggests installing Lineage OS alone without Gapps, and then install Webview Implementation, if not installed:
http://www.lineageosrom.com/2017/02/how-to-fix-google-play-services-error.html
When I tried this and reboot, I get the messages "android.process.media" has stopped, followed by the message "clock has stopped". When I click away these messages, and click on next on the Lineage OS screen, the device enters into a boot loop displaying the sliding Lineage logo. This agrees with the Lineage recommendation, that both packages need to be installed at the same time:
https://wiki.lineageos.org/devices/n2awifi/install
Can anyone please help? I really don't want to go back to Android v4.4.2 on my SM-T520.
Hello so to get rid of the error I would suggest downloading samsung kies 1 not 2 or 3 and flashing completely back to stock then try rooting and flashing rom should get rid of system errors and force closes. Kies will ask you for model and serial number. Serial is found on back of the tablet. As another suggestion I would try resurrection remix by cosmox. It is very stable everything works. I just posted a link in that thread with a link to download samsung kies for a 64 bit windows and other relevant files if you need. Let me know if you need any other help. Also closer inspection of your links. I think for sm-t520 u should be using twrp Picassowifi, not n2awifi so idk if that will work or not. Not sure about that part though because they may have made it work on Picasso.
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
paintball,
I've found a solution, that I thought I'd post here in case anyone else has the same problem.
I wiped the cache/dalvic after each step of the installation:
Wipe-> Advanced -> wipe cache / data / dalvic / system
Install -> flash Lineage -> wipe cache/dalvic
Install -> flash Gapps -> wipe cache/dalvic
Reboot -> don't install SuRoot
I got a Music closed error during the first boot, which hasn't appeared since.
Afterwards, I used Odin to install CF-Auto-Root. The device rebooted twice after this step, but now appears to be OK.
A final problem I had was that it couldn't find my wifi SSID. I solved this by setting wifi region to Europe.
ppmoore said:
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
Click to expand...
Click to collapse
I suggested using Samsung kies which I'm positive works, not Odin, but I'm glad you got it fixed.
ppmoore said:
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message
<snip>
Click to expand...
Click to collapse
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
I have tried several permutations of Lineage OS nightlies along with various flavors of OpenGApps, with and without root, wiping cache/dalvik/data/system, wiping only some, wiping none.
I also cannot restore the backup of the running LOS that I had up (I did take a backup before going back to the original setup). When I try, I get the same results as above--as if I had backed-up an un-instantiated setup.
Any thoughts?
eckster said:
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
Any thoughts?
Click to expand...
Click to collapse
Hi Eckster,
I have exactly the same problem on a LG G2 with LOS 14.1. It ran July version perfectly but I didn't make a backup and now I'm stuck. Did you ever manage to fix this?
Thanks,
Kevin
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
how did you format the partitions? I can only find "format data".. thx
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
:thumbsup: I was on lineage 14, all was well. I tried an old stock rom NK2, that was fine. I tried to restore lineage backup via twrp, got this problem with the framework crashing. No amount of re-flashing twrp nor lineage, gapps, modem, bootloader, etc nothing worked; always crashed right after boot to lock screen. Finally twrp "format data" - yes. Now lineage boots to welcome, no crash; restore backup - after copying it back to internal - and all is good.
I'm glad it works but why is it needed in this case to remake the filesystem on data - does it work by removing some bad file or does it work by rebuilding the ext4 and security context? this is with latest twrp twrp-3.2.1-0-klte.
Hi,
don't know if you solved it eventually, or maybe helpful for other people with the same problem. I had the same problem, spent 6 days digging around on the internet why the framework keeps stopping and crashing.
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Say whatever you need to whatever deity you prefer and wait for the tablet to boot.
I hope to be of some help to other people having the same problem
Code:
Sent from my SM-S920L using Tapatalk
grammar
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
Was going crazy trying to figure out why LineageOS was encountering so many ANRs. The first time I flashed Lineage it worked beautifully but every time after that it just went nuts. This fixed it for me, thanks dude!
Note to others who may end up here, after formating data I had to install a stock ROM, then wipe and install Lineage. Lineage wouldn't install due to Updater process ended with ERROR: 7 which was because there was some bit of information that was on the data partition that showed the install script that the phone was actually a Note II. Formating data blows that info away but installing stock puts it back on.
LievenVanh said:
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Click to expand...
Click to collapse
Coming into this thread after a few hours of struggle with an old GS4 I can say that this method instantly worked for me as well.
Thanks!
Thanks for the help to resolve my issue of installation. Do you have a solution for Zoom , where my audio (cannot hear other speakers) and video is missing. Did enable access for Mic, Camera etc in App permission.
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
hamudistan said:
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
Click to expand...
Click to collapse
That solution didn't work. My Zoom audio still not working.
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
For almost a month now I have been happily using LOS 17.1 on my Xiaomi Redmi Note 8T (flashed via LOS recovery, everything working great), until yesterday all of a sudden the OS crashed (I actually don't know what happend, I put the phone away and when I wanted to use it again I just saw the boot screen). Now the phone wont boot to OS no matter what I do (restart, turn off and on, fastboot and back), but I can still enter recovery.
What the hell happened??
What I can do to fix it - e.g. reinstall LOS/install last update?
Will any of the steps to fix it remove the data on my phone?
lueromat said:
For almost a month now I have been happily using LOS 17.1 on my Xiaomi Redmi Note 8T (flashed via LOS recovery, everything working great), until yesterday all of a sudden the OS crashed (I actually don't know what happend, I put the phone away and when I wanted to use it again I just saw the boot screen). Now the phone wont boot to OS no matter what I do (restart, turn off and on, fastboot and back), but I can still enter recovery.
What the hell happened??
What I can do to fix it - e.g. reinstall LOS/install last update?
Will any of the steps to fix it remove the data on my phone?
Click to expand...
Click to collapse
1-delete the folder : data/system/dropbox
reboot,and when the system restarts , read logs in that folder to know what is happening
2-if you didn't remove any important system file, reinstall will fix nothing
3-in most cases,wiping data will fix the problem, just be prepared to it
your best shot would be making a twrp backup of data and explore it with 7z and try to restore your app + data when the system boots
thanks !
how can I access the dropbox folder if the system isn't booting? not finding the device in fastboot...
I don't have twrp, but lineage recovery - is that an issue? there are also some logs here, but probably not related to the system, I assume?
lueromat said:
how can I access the dropbox folder if the system isn't booting?
I don't have twrp, but lineage recovery - is that an issue? there are also some logs here, but probably not related to the system, I assume?
Click to expand...
Click to collapse
next time use "quote" or "reply" so i get a notification
i don't know if lineage recovery has a file manager or not, but i strongly recomand using orangefox recovery for multiple reasons ...
when you make a backup of data, browse to that folder and do what i said
and when your system is on you can restore your app + data using that backup and titanium backup app or copy paste if you know the path ...
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
loopypalm said:
i don't know if lineage recovery has a file manager or not, but i strongly recomand using orangefox recovery for multiple reasons ...
Click to expand...
Click to collapse
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
lueromat said:
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
lueromat said:
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
Click to expand...
Click to collapse
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
Click to expand...
Click to collapse
You shouldn't have flashed pic GApps coz of that it will go to same issue when the rom gets updated. Instead flash OpenGapps one of the best GApps for LineageOS. There was same issue with my Moto G3 Turbo(Merlin) when I flashed BitGapps, always use Trusted GApps by LineageOS. It is also available on the LineageOS Forum