Related
Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?
Somehow, your file system can't be accessed....was your phone encrypted?
itouchables said:
Somehow, your file system can't be accessed....was your phone encrypted?
Click to expand...
Click to collapse
It wasn't, I never encrypted it.
Also fastboot getvar all shows that my partition type is RAW.
Shouldn't it be F2FS or EXT4?
Maybe anyone has a proper partition mount point list for the Moto G?
I would try mkfs.ext4 formatting every possible mount point (cache,data,system and etc)
For example dev/block/mmcblk0p38
I found a Moto X mount point list but I have no clue if it's the same or not
Aequus.Mihi said:
Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?
Click to expand...
Click to collapse
Hi! did you find a solution?!
Oliverrlh said:
Hi! did you find a solution?!
Click to expand...
Click to collapse
No. Turns out my phone memory chip was corrupted due to flashing
Aequus.Mihi said:
No. Turns out my phone memory chip was corrupted due to flashing
Click to expand...
Click to collapse
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?
Icon000 said:
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?
Click to expand...
Click to collapse
That's the same situation I was in.
Even if you try to flash another ROM, it will never install.
You can't modify any files because the memory is ****ed.
I sold the phone for parts and bought a S4
Hey there,
so I wanted to update LineageOS to the latest nightly (1st August) coming from an April nightly. I did it OTA, entered TWRP, installed the update and got stuck in TWRP, which is apparently a known issue with TWRP 3.0.2.0. But I didn't know that, and tried to fix it by installing a backup of CM 13 WITHOUT wiping data, because I did not want to lose my data. Stupid, I know.
I then found a fix to leave TWRP and tried booting into CM 13 but now I'm stuck in a bootloop when the phone is connected to my pc. . It shows the CM logo, then prepares apps, shows the logo, prepares apps, logo, and so on... When I unplug it, it gets stuck at "Preparing Apps"
I can't enter Download mode or Recovery mode using the keys and adb/fastboot commands don't work while the phone is turned off or booting.
Any ideas what I can do?
Hello, what is your device?
If battery is removable, remove battery then put it back and try to boot to download mode
Its an LG 2 Mini and i have done that already.
Do you know how i could possibly fix the issue with rebooting when connected to my computer? Maybe then i can recover it via adb
Turn off the phone
Keep holding down Volume Up button.
Put a USB cable that is connected to pc
Continue holding Volume Up button throughout download mode until fastboot mode appears and you can release the Volume Up button.
If that didn't work try with volume down
I'm in Download mode now, thanks! However i can't use adb or fastboot commands, even though i have the right drivers installed.
In the Windows device manager it shows it as" "LGE Android MTP device" with Code 10 Error (the device couldnt be started)
Anyone knows how to proceed?
lionboy33 said:
In the Windows device manager it shows it as" "LGE Android MTP device" with Code 10 Error (the device couldnt be started)
Anyone knows how to proceed?
Click to expand...
Click to collapse
What do you get when you try to use fastboot commands?
"waiting for any device"
Fastboot devices is also empty
---
I believe it's a problem with my adb or my drivers, because I can't get it to work with my other phone either
Sorry for being late, try installing usb drivers again from the lg site
I did, but it didnt help
On Linux Mint it shows "unable to mount LGE Android Phone"
lionboy33 said:
Hey there,
so I wanted to update LineageOS to the latest nightly (1st August) coming from an April nightly. I did it OTA, entered TWRP, installed the update and got stuck in TWRP, which is apparently a known issue with TWRP 3.0.2.0. But I didn't know that, and tried to fix it by installing a backup of CM 13 WITHOUT wiping data, because I did not want to lose my data. Stupid, I know.
I then found a fix to leave TWRP and tried booting into CM 13 but now I'm stuck in a bootloop when the phone is connected to my pc. . It shows the CM logo, then prepares apps, shows the logo, prepares apps, logo, and so on... When I unplug it, it gets stuck at "Preparing Apps"
I can't enter Download mode or Recovery mode using the keys and adb/fastboot commands don't work while the phone is turned off or booting.
Any ideas what I can do?
Click to expand...
Click to collapse
First of all, when restoring a backup, wipes are not necessary because the partitions are automatically formatted during the restore process. It wipes data for you, anything there would have been wiped anyway even though you were trying to avoid losing data, it is intentionally designed to do this so that you don't have conflicts with existing data.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
First of all, when restoring a backup, wipes are not necessary because the partitions are automatically formatted during the restore process. It wipes data for you, anything there would have been wiped anyway even though you were trying to avoid losing data, it is intentionally designed to do this so that you don't have conflicts with existing data.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
What i meant when i said i didnt wipe data was that i didnt choose to restore data when restoring the backup - just system and boot
lionboy33 said:
What i meant when i said i didnt wipe data was that i didnt choose to restore data when restoring the backup - just system and boot
Click to expand...
Click to collapse
but this shouldn't cause troubles and the system should boot :/
try with another cable or usb port
run
`sudo fastboot devices`
-Hope- said:
but this shouldn't cause troubles and the system should boot :/
try with another cable or usb port
run
`sudo fastboot devices`
Click to expand...
Click to collapse
I assume the backup i tried to restore was corrupted then maybe...
I tried several cables, none worked I believe its a problem with drivers on the device, because it didnt get in a bootloop with a non data usb cable
lionboy33 said:
I assume the backup i tried to restore was corrupted then maybe...
I tried several cables, none worked I believe its a problem with drivers on the device, because it didnt get in a bootloop with a non data usb cable
Click to expand...
Click to collapse
Linux usually comes with needed files by default, just install the platform tools package + fastboot and adb package and try again i don't think you would need to install drivers.
lionboy33 said:
What i meant when i said i didnt wipe data was that i didnt choose to restore data when restoring the backup - just system and boot
Click to expand...
Click to collapse
Yeah, that would have caused problems.
You can't use data from one ROM in a different ROM. When you restored, you left the data from LOS, the system and boot from CM13 won't work with the data from LOS.
For future reference, don't mix data from other ROMs, they don't play well in most cases.
Using advanced restore to only restore certain partitions usually only works when using the same ROM or an older/newer version of the same ROM.
If you can get back into recovery somehow, you'll probably need to do advanced wipes to wipe system partition and data partition then flash a ROM. Wipe cache and dalvik/ART cache after flashing the ROM, then reboot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Yeah, that would have caused problems.
You can't use data from one ROM in a different ROM. When you restored, you left the data from LOS, the system and boot from CM13 won't work with the data from LOS.
For future reference, don't mix data from other ROMs, they don't play well in most cases.
Using advanced restore to only restore certain partitions usually only works when using the same ROM or an older/newer version of the same ROM.
If you can get back into recovery somehow, you'll probably need to do advanced wipes to wipe system partition and data partition then flash a ROM. Wipe cache and dalvik/ART cache after flashing the ROM, then reboot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I can't enter recovery, it always just boots normally. I can only enter Download mode without fastboot access
lionboy33 said:
I can't enter recovery, it always just boots normally. I can only enter Download mode without fastboot access
Click to expand...
Click to collapse
Keywords "if" and "somehow"
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Does flashtool detect the phone ?
We can zero the laf partition to force the phone in fastboot mode but we must proceed in caution if you want to.
-Hope- said:
Does flashtool detect the phone ?
We can zero the laf partition to force the phone in fastboot mode but we must proceed in caution if you want to.
Click to expand...
Click to collapse
No, flash tool doesn't recognize it
Requirements:
1. Bootloader Must Be Unlocked.
2. Have a backup of your working Magisk Patched boot.img saved to your External SDcard.A little INFO:
The Sony L1 recovery seems to be disabled by SONY for some unknown and Probably stupid reason.
I have tried all ways to get the TWRP and Stock recovery to boot up from the fotakernel partition (recovery) but TWRP and even the stock recovery refuse to boot.
Anyway to cut a very long story short I am releasing this TWRP which is 95% functional and needs to be flashed to the boot partition
Working Method/flow:
Make sure you have a Back up of your working Boot.img "You know the one you used to root the device in the first place".
For ease of use You can use this app by XDA dev @wanam (Thread here) app on playstore Here You can also use this app to flash the v5-twrp-l1.img to your "boot" partition or you can go old skool and use dd (Via adb shell) or use the Magisk patched_boot.img you first rooted with..
Make SURE to Copy this working boot.img to your External SDcard.
When you require TWRP flash the downloaded TWRP to your boot partition using Fastboot (cmd's below) or the above app then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
IMPORTANT:
Remember Just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
Things Not Working:
1. You will not be able to mount encrypted data therefore you would need to FORMAT your data and then leave it unencrypted.
SuperSU and Magisk will disable forceencrypt for you.
2. Does not Charge or show battery % so I don't know if it's actually charging. (Probably Qnovo battery module used by sony)
It will probably work on all variants but I am not able to test that.
It's use is for backups and restores wipes and installs for which it seems fully functional. :good:
Install Instructios.
Boot to the bootloader then
Code:
fastboot flash boot v5-twrp-l1.img
Then
Code:
fastboot reboot
Download HERE v5-twrp-l1.img
Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311
Chronic2k13 said:
Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311
Click to expand...
Click to collapse
:laugh:
Ok maybe I should update the OP as it seems it's not really clear enough that obviously the boot is replaced by the recovery.
Method would be make sure you have a Back up your working Boot.img You know the one you used to root the device in the first place.
You can also use dd (Via adb shell) or a app from the playstore or better still use the Magisk patched_boot.img .
Copy this working boot.img to your External SDcard.
When required flash the recovery to your boot partition using Fastboot then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
Then just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
OP Updated let me know if it's clearer to understand now.
Thanks for reporting back. :good:
I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?
Chronic2k13 said:
I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?
Click to expand...
Click to collapse
I don't think you have really read or understood the OP
You are only ever flashing the "boot partition".
When you need to use TWRP you flash the TWRP.img to the boot partition and when your done you flash back your boot.img again to the boot partition as in the OP.
BTW Have you ever been able to enter the STOCK recovery using Power and Volume Down or using any commands
My phone could not enter the STOCK recovery at all let alone a custom one and since no one ever replied to my question about this I assumed this was the case for everyone as many sony devices from 7.0 had the recovery disabled?
I'm unable to get into stock recovery too!
So,
If we don't have a Recovery partition maybe we can
Create one...
Tutorial in here
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
I'll try it if i have time.
I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?
alegatorul said:
I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?
Click to expand...
Click to collapse
Mate you really need to be careful unless you really know what your doing
You will likely brick the phone if you continue to blindly mess with re-partitioning and the like.
If you were in TWRP which was flashed to the boot partition as directed in the OP then flashing the supersu.zip will simply modify your TWRP.img not your boot.img since TWRP is living in the boot partition at the time you run the .zip hence your looping.
This device has bootloader issues since it will not allow the booting of another partition except "boot" recovery, fotakernel, rdimage, all tested all failed to boot the TWRP recovery and stock recovery.
There is another method used by some sony devices but this will need to be heavily modified for this MediaTek SoC and will require a lot of study and script re-writes.
Spending all this time on a device that's pretty much obsolete before it was launched since it's not planned to receive oreo and Sony 90% locked down the bootloader is kinda futile so use the phone for what it is then throw it in the bin when done in a year or two.
Mate, you are right
Hi, please make recovery for L1 G3312 i hope you can do it.
tweak8 said:
Hi, please make recovery for L1 G3312 i hope you can do it.
Click to expand...
Click to collapse
I think this one may very well work for the dual SIM also so please try it and then report back with some actual details.
eg: bootloader status, firmware version, your region, etc etc.
Thanks.
Works great on the G3113 model, thank you for developing this! Now hoping to find a custom rom to install via .zip.
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?
dumb person said:
Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?
Click to expand...
Click to collapse
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...
bigrammy said:
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.
Click to expand...
Click to collapse
I downloaded the boot from the link you posted and flashed it. Now it phone works again. Many thanks!!
riadjblicd said:
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...
Click to expand...
Click to collapse
Yes but Sony Disabled the recovery partition (fotakernel) by design so you can not boot from it.
The OP is clear about the need to flash the TWRP to your boot partition and the reason I also give full instruction in the workflow/method but people simply don't read anymore it seems. :crying:
TWRP can be injected into the boot.img so you can boot normally or boot TWRP using the volume keys at boot time but I can't be bothered working on this since Sony are not going to update the Android Version.
While the phone is OK I have far better phones to spend my time on at the moment.
how to backup boot.img without root? if its impossible then how do i root this phone?
i have used my phone and all was fine, but i wanted to reboot it and something went wrong. first it has stuck in boot loop, i waited ~10 minutes and tought it'll boot but no, then i tried enter a Recovery (twrp) and it just doesnt want to boot even in recovery. So i went to fastboot and flashed a new verion of twrp, but it still won't boot. All the times when i have been stuck in a bootloop i just cleared caches wia twrp and phone booted fine but now i really doesn`t know what i can do to rescue it and not lose my data. So maybe there is a way i can wipe caches without accessing the recovery menu? =(
if i force bootloader to load from fastboot it throws me back into a fastboot.
Poco x3 nfc (surya) Android 12 Pixel Experience (official from their website)
also i have tried alot of recoveries ( bunch of twrps, 3 orange foxes, PE recovery) no one works, TWRP&OF just hangs on splash screens and PErecovery is just a black screen. i just have no clue what do i do. i can try flash rom from a fastboot but then i will lose all my data.
i have no much knowlege about logging in android, here is adb logcat https://pastebin.com/6bSFURBM
EnderDremurr said:
i have used my phone and all was fine, but i wanted to reboot it and something went wrong. first it has stuck in boot loop, i waited ~10 minutes and tought it'll boot but no, then i tried enter a Recovery (twrp) and it just doesnt want to boot even in recovery. So i went to fastboot and flashed a new verion of twrp, but it still won't boot. All the times when i have been stuck in a bootloop i just cleared caches wia twrp and phone booted fine but now i really doesn`t know what i can do to rescue it and not lose my data. So maybe there is a way i can wipe caches without accessing the recovery menu? =(
if i force bootloader to load from fastboot it throws me back into a fastboot.
Poco x3 nfc (surya) Android 12 Pixel Experience (official from their website)
also i have tried alot of recoveries ( bunch of twrps, 3 orange foxes, PE recovery) no one works, TWRP&OF just hangs on splash screens and PErecovery is just a black screen. i just have no clue what do i do. i can try flash rom from a fastboot but then i will lose all my data.
i have no much knowlege about logging in android, here is adb logcat https://pastebin.com/6bSFURBM
Click to expand...
Click to collapse
Try this tool: https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
Try this tool: https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
does that thing works on linux? sadly i have no pc with a windows now
EnderDremurr said:
does that thing works on linux? sadly i have no pc with a windows now
Click to expand...
Click to collapse
You can flash fastboot ROMs on Linux with fastboot and adb tools
or
https://forum.xda-developers.com/t/tool-linux-miflash-for-linux.3708847/
https://www.bettermobileapp.com/article/10416422/[TOOL][Linux]+MiFlash+for+Linux
https://gist.github.com/duyfken/574f570f40f813604849bd40d9e1a048
To check .
do a search
NOSS8 said:
You can flash fastboot ROMs on Linux with fastboot and adb tools
or
https://forum.xda-developers.com/t/tool-linux-miflash-for-linux.3708847/
https://www.bettermobileapp.com/article/10416422/[TOOL][Linux]+MiFlash+for+Linux
https://gist.github.com/duyfken/574f570f40f813604849bd40d9e1a048
To check .
do a search
Click to expand...
Click to collapse
hi, i have one more question, is there way i can check my phone`s internal memory from adb ( for dead sectors etc.) i think my internal memory just have died somehow
EnderDremurr said:
hi, i have one more question, is there way i can check my phone`s internal memory from adb ( for dead sectors etc.) i think my internal memory just have died somehow
Click to expand...
Click to collapse
Start by format data,miflash can do it.(will erase the data and create a new partition if necessary).
And use this TWRP https://androidfilehost.com/?w=files&flid=318270
just flash stock rom with miflash and select save user data and done, will flash the entire rom without lose your personal data
tutibreaker said:
just flash stock rom with miflash and select save user data and done, will flash the entire rom without lose your personal data
Click to expand...
Click to collapse
From an AOSP rom to MIUI?
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
UPDATE EDIT 11/6: So now I can get into Recovery and have access to an older Lineage Recovery for 18.1 and TWRP but neither allows me to flash any of the Lineage 18.1 OTA files I had extracted from my phone, resulting in a Code:: kInstallDeviceOpenError.
Did I mess up the firmware by trying to install 19.1 without updating the firmware?
I am trying to preserve some files so don't want to wipe the phone completely if at all possible.
LOSXDA98 said:
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
Click to expand...
Click to collapse
Try to boot the recovery file from bootloader mode with fastboot.
LOSXDA98 said:
Started to go down the Lineage 19.1 route. Despite the warning, I forgot to update firmware to 12, realized this halfway through the flash.
Thought no worries, I will just flash 18.1 again as I still have the files, but now I can't get into recovery. Any booting leads only to the crash dump screen
Is an MSM tool reset the only way?
Now I am pretty much an amateur when it comes to this stuff, but I want to think that I did a lineage19 upgrade on another device I didn't have to do a firmware upgrade.
I downloaded the files a while ago and I definitely read the instructions then, so I can only assume I forgot about the firmware update in the time since.
Click to expand...
Click to collapse
You can manually update your firmware and flash the ROM with fastboot.
This thread should have been started in the 8T Q&A forum.
Depending on what you've done, you can sometimes switch slots in bootloader and then boot recovery.
But as recommended by the other responses, reflashing in bootloader is also a good option.
If neither work, then the MSM Tool is the best option to get things going again.
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
LOSXDA98 said:
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
Click to expand...
Click to collapse
No fastboot means the only solution is the MSM Tool. You should feel lucky that you are not on the 10 Pro.
Can I use MSM tool to reflash lineage or is the only option a factory reset?
Not sure if there is any other way to access the data on the device.
LOSXDA98 said:
Can I use MSM tool to reflash lineage or is the only option a factory reset?
Not sure if there is any other way to access the data on the device.
Click to expand...
Click to collapse
I don't know any. Even the firehose readback feature of MSM Tool doesn't allow to backup the data partition.
LOSXDA98 said:
The problem is I can't get into fastboot mode from the hardware buttons, it still results in crash dump screen. Trying to get into recovery the same way results in the same.
Click to expand...
Click to collapse
You can't go straight to fastboot from Crash Dump mode.
You must first get out of Crash Dump using power + vol up (see https://community.oneplus.com/wap/thread/1316587) and then use the keys to get into fastboot.
If you wait too long after getting out of Crash Dump the phone tries to boot again and you'll end up back in CD.
I can get it to shut down using the volume up and power.
So starting from a completely shutdown phone, and holding Volume up and power to go to fast boot, results in crash dump.
Holding volume up and releasing power when the logo appears also results in a crash dump.
Lastly holding both Volume up and Power the entire time results in crash dump.
If there is another combination or I am doing something wrong, I am happy to try again.
Sadly I'm out of ideas.
Well I managed to get into fastboot. I had to hold all buttons down until it loaded.
So I was able to reinstall TWRP, thinking I could use the access to the root to reinstall OS 18.1 from the OTA folder. I just get errors Failed to Mount, 'system root' invalid and 'vendor.'
So now I cannot reinstall 18.1.
Trying to use Lineage Recovery it would not even start the install process.
So now I am not sure what I should try next
LOSXDA98 said:
Well I managed to get into fastboot. I had to hold all buttons down until it loaded.
So I was able to reinstall TWRP, thinking I could use the access to the root to reinstall OS 18.1 from the OTA folder. I just get errors Failed to Mount, 'system root' invalid and 'vendor.'
So now I cannot reinstall 18.1.
Trying to use Lineage Recovery it would not even start the install process.
So now I am not sure what I should try next
Click to expand...
Click to collapse
The first thing I would do is backup important data if you have any using adb from TWRP. Then you could factory reset with MSM Tool or try to flash LOS from fastboot.
Pictures and texts are the important files and to my knowledge TWRP doesn't back those up
I am trying to figure out what the failed install might have corrupted and what I can reflash.
Do I need to reflash dtbo and vbm?
Can I use the newer 19.1 recovery with older OS files?
None of the older 18.1 official build files seem to exist online anymore.
Did I somehow switch partitions, and how would I know this?
LOSXDA98 said:
Pictures and texts are the important files and to my knowledge TWRP doesn't back those up
I am trying to figure out what the failed install might have corrupted and what I can reflash.
Do I need to reflash dtbo and vbm?
Can I use the newer 19.1 recovery with older OS files?
None of the older 18.1 official build files seem to exist online anymore.
Did I somehow switch partitions, and how would I know this?
Click to expand...
Click to collapse
You can use adb to backup files in the internal sdcard while being in TWRP.
Regarding switching partitions, in the reboot menu of TWRP you can see which slot you have activate and switch it.
Does that include texts?
What slot should I be installing in?
I want to say active slot was A
LOSXDA98 said:
Does that include texts?
What slot should I be installing in?
I want to say active slot was A
Click to expand...
Click to collapse
With texts do you mean whatsapp messages or sms?
I would try to install in both slots (first A and if it doesn't work B)
Sms
LOSXDA98 said:
Sms
Click to expand...
Click to collapse
For sure a backup of the data partition will include them but the problem is to be able to restore them afterwards. You can try to find a guide on the internet like this (although this one is old and may be outdated).