Hi everyone, I'm at a loss at what to do here.
I've attempted to unlock my phone which I've done successfully,flash the twrp image, and install the twrp zip but now because I'm running into issues, I just want to return to stock, I'm stuck in between. I thought if I flashed stock img from google and started over it would fix everything - but when I do flash stock img I get "not enough storage" and i cannot proceed. I've searched up and down this forum for an answer but to no avail. I'd appreciate the help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you updated your adb and fastboot? I've heard of a lot of problems cause by people's "minimal" setups being outdated. Also, there's a good chance you can get back to working simply by flashing the stock boot.img out of the system image you've already downloaded.
I think I have updated everything properly. At least, I think so.
When I try to flash just the system.img it hangs here;
OK, update. I was able to get NFM26Q to load up but it says my internal storage is corrupt upon booting and it doesn't recognize my SIM card (on Verizon). Should I flash a different factory image file? Or try something else? Thanks for any help.
iainaaldrich said:
Hi everyone, I'm at a loss at what to do here.
I've attempted to unlock my phone which I've done successfully,flash the twrp image, and install the twrp zip but now because I'm running into issues, I just want to return to stock, I'm stuck in between. I thought if I flashed stock img from google and started over it would fix everything - but when I do flash stock img I get "not enough storage" and i cannot proceed. I've searched up and down this forum for an answer but to no avail. I'd appreciate the help
Click to expand...
Click to collapse
I thought I saw that re-locking a Verizon bootloader would cause possible instability and would not be supported. I'm not sure if you're still under warranty but you might want to look into a replacement if you can't get it figured out. If you successfully relocked it then you should be ok under service.
I think at this point you might want to try a factory/reset in the stock recovery menu and see if Q loads up. Without seeing where you are and what you've done it's hard to diagnose.
bobby janow said:
I thought I saw that re-locking a Verizon bootloader would cause possible instability and would not be supported. I'm not sure if you're still under warranty but you might want to look into a replacement if you can't get it figured out. If you successfully relocked it then you should be ok under service.
I think at this point you might want to try a factory/reset in the stock recovery menu and see if Q loads up. Without seeing where you are and what you've done it's hard to diagnose.
Click to expand...
Click to collapse
First thing I did was unlock the phone, second thing I did was flash the IMG for twrp, booted into twrp and flashed the zip. I couldn't get past twrp, if I restarted the phone, it would just get stuck at twrp. So, I had no OS to boot into somehow and so at this point, I flashed the stock 7.1 file from Google and now it boots into the OS with no twrp, or bootloader, but the OS boots with an error message saying the internal storage is corrupt. I can use the phone but I have no data connection, camera fails to load, etc etc. So it's pretty useless. I made the mistake of thinking it would just be as easy as a Nexus, which clearly, it's not. I think I got everything I did there. I'm just trying to figure out how to get it back to stock, like right out if the box. My mistake surely, I'm just hoping someone can explain the necessary steps to get back to point A. Thanks for your help.
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
iainaaldrich said:
First thing I did was unlock the phone, second thing I did was flash the IMG for twrp, booted into twrp and flashed the zip. I couldn't get past twrp, if I restarted the phone, it would just get stuck at twrp. So, I had no OS to boot into somehow and so at this point, I flashed the stock 7.1 file from Google and now it boots into the OS with no twrp, or bootloader, but the OS boots with an error message saying the internal storage is corrupt. I can use the phone but I have no data connection, camera fails to load, etc etc. So it's pretty useless. I made the mistake of thinking it would just be as easy as a Nexus, which clearly, it's not. I think I got everything I did there. I'm just trying to figure out how to get it back to stock, like right out if the box. My mistake surely, I'm just hoping someone can explain the necessary steps to get back to point A. Thanks for your help.
Click to expand...
Click to collapse
First, if you haven't already done so, update your adb/fastboot setup to the latest version. I see you're using minimal adb. The latest version is 1.4.1. You can get it here. From the looks of your first screenshot I'd guess you need to update. Whatever the case, run the flashall batch file again. I don't know how long you let it sit at flashing system but I've flashed mine a couple times and it hangs on system for what seems forever. It looks like it's not doing a thing but if you wait long enough, eventually it jumps to life and continues. Give it time. How long? I don't really know. Guessing mine hung there for at least 5 minutes, maybe more.
iainaaldrich said:
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
Click to expand...
Click to collapse
Is your bootloader unlocked at this point? Have you tried a factory/reset from the stock recovery menu if you are not. If you are you can look for instructions on how to flash a factory image manually, which includes all the necessary files such as recovery, radio, bl, vendor etc. Just don't flash 7.1.1 yet. Get the phone working first on 7.1 (X) version preferably.
robocuff said:
First, if you haven't already done so, update your adb/fastboot setup to the latest version. I see you're using minimal adb. The latest version is 1.4.1. You can get it here. From the looks of your first screenshot I'd guess you need to update. Whatever the case, run the flashall batch file again. I don't know how long you let it sit at flashing system but I've flashed mine a couple times and it hangs on system for what seems forever. It looks like it's not doing a thing but if you wait long enough, eventually it jumps to life and continues. Give it time. How long? I don't really know. Guessing mine hung there for at least 5 minutes, maybe more.
Click to expand...
Click to collapse
Thanks, I'll try this again. The last time I tried, it just froze. But good point.
bobby janow said:
Is your bootloader unlocked at this point? Have you tried a factory/reset from the stock recovery menu if you are not. If you are you can look for instructions on how to flash a factory image manually, which includes all the necessary files such as recovery, radio, bl, vendor etc. Just don't flash 7.1.1 yet. Get the phone working first on 7.1 (X) version preferably.
Click to expand...
Click to collapse
When I boot up it has the unlocked logo, but if I try to boot into recovery I simply get "no command" with an exclamation point above the Android logo. So I'm not able to do a factory/reset from the recovery menu. I'll try refreshing everything again but I kept getting "not enough storage" or a similar error message.
iainaaldrich said:
When I boot up it has the unlocked logo, but if I try to boot into recovery I simply get "no command" with an exclamation point above the Android logo. So I'm not able to do a factory/reset from the recovery menu. I'll try refreshing everything again but I kept getting "not enough storage" or a similar error message.
Click to expand...
Click to collapse
In recovery with the no command logo, hold down the power key and hit the vol up key. That will get you into recovery where you can do those things. Use the vol keys to go up and down in the menu. Google stock recovery in android 7.1 for screenshots and more detailed instructions if you need.
I was able to get everything back up and running by following method 2 here - manually flashing using minimal adb: http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/ and using the verizon 7.1 image from google's site, then updated to 7.1.1 on an unlocked bootloader, everything is working fine, however I am having one issue - seems as though the system flashed twice? I should have a lot more storage than this:
Is there a way to completely wipe everything and manually reflash the stock image?
Anybody know what I can do to wipe everything and start fresh? My bootloader is already unlocked. Thank you!
iainaaldrich said:
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
Click to expand...
Click to collapse
Do not relock your bootloader. Ever.
Get your fastboot up to date, and use the flash all script that comes with the factory image.
Sent from my Pixel XL using XDA Labs
TonikJDK said:
Do not relock your bootloader. Ever.
Get your fastboot up to date, and use the flash all script that comes with the factory image.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Yeah, I'm not going to. I got it working by flashing it manually, the flash all script didn't work. How do I erase everything? Because for some reason now, my system image takes up almost all of my internal storage. It's as if, I have multiple system images on the same device...or something....
iainaaldrich said:
Yeah, I'm not going to. I got it working by flashing it manually, the flash all script didn't work. How do I erase everything? Because for some reason now, my system image takes up almost all of my internal storage. It's as if, I have multiple system images on the same device...or something....
Click to expand...
Click to collapse
Is this a 128 or 32? 128 often misreports space after flash. Have to factory reset to get it back.
Sent from my Pixel XL using XDA Labs
TonikJDK said:
Is this a 128 or 32? 128 often misreports space after flash. Have to factory reset to get it back.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
No, 32. It's reporting correctly, but I don't get why it's taking up so much space.
iainaaldrich said:
No, 32. It's reporting correctly, but I don't get why it's taking up so much space.
Click to expand...
Click to collapse
How much does storage say system is using?
Sent from my Pixel XL using XDA Labs
Related
Hi folks,
I'm a little kerfluffled if you will by the sheer number of threads - search isn't pointing me to a thread that deals with this - so apologies if this has been answered before.
I originally rooted my phone with towelroot. I kept stock but installed a few things like Xposed, greenify, gravity box, etc... (also i switched to ART some time back).
Once i received the OTA notification, I deactivated greenify and gravity box, then uninstalled them, then "unrooted" the phone using SuperSU. I did forget to reset my "startup animation" but otherwise everything seems fine. The root checker confirms that the phone is no longer rooted. Since i forgot to backup the stock animation i just renamed the .zip and now when i boot the animation just says Android (with a little animation regarding the color of the letters).
I then DLed the update, restarted and approximately 30 ~ 40% of the way through the update screen it freezes up and then i get the little android dude with his belly open and the red error triangle. The text below says "error" but provides no further information. The only way to resolve the issue is to power off the phone and then turn it back on. It goes back into 4.4.4 and works fine but i can't get past that error and have no idea how to tell what the error actually is.
Any suggestions will be appreciated! I would prefer to not have to wipe my phone if at all possible.
You'll must wipe your phone as I am. Then you'll be able to OTA update your phone.
I do exactly like you, but error appears every time in the middle of update process. After wipe everything was fine
Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.
Lokke9191 said:
Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.
Click to expand...
Click to collapse
Since I'm not concerned about root in Lollipop for now - if i can find the original boot animation and "reinstall it" so to speak - will that allow me to use the ota without having to wipe my phone?
Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.
Lokke9191 said:
Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.
Click to expand...
Click to collapse
okay thanks! i'm going to try and find the original boot animation somehow and if that doesn't solve the problem, i'm going to fastboot everything.
Just dont flash userdata, or you'll lose your setup.
Lokke9191 said:
Just dont flash userdata, or you'll lose your setup.
Click to expand...
Click to collapse
thanks mate!
So recently, I was trying to flash something, I forgot, all I know that it was not a ROM and I was stuck on the android is upgrading, took too long so I wiped through TWRP, still wont boot. I can see what is on my phone through file explorer and nothing is there but twrp. I really messed up this time e.e. I am open for teamviewer.
Joebizzle said:
So recently, I was trying to flash something, I forgot, all I know that it was not a ROM and I was stuck on the android is upgrading, took too long so I wiped through TWRP, still wont boot. I can see what is on my phone through file explorer and nothing is there but twrp. I really messed up this time e.e. I am open for teamviewer.
Click to expand...
Click to collapse
I tried doing fastboot oem unlock, but this takes me to TWRP recovery.
How on earth do you not know what you were flashing? It's no wonder your phone is in the state it's in right now. That's just crazy bad. Any why are you trying to unlock the bootloader again? If you have TWRP recovery installed it must already be unlocked unless you deliberately relocked it again. Anyway, looks like you've wiped everything, including your internal storage. The best idea right now is flash fresh with fastboot using the stock images.
Transmitted via Bacon
Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
DrakMC said:
Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
Click to expand...
Click to collapse
You didn't explain your Problem quite well. Does it reboot to fastboot or does it reboot to system? (aka a Bootloop). if it reboots to system, here's what to do:
Boot into a custom recovery (twrp/Orangefox) and flash the required recovery MIUI ROM mentioned in your custom ROM's thread instructions.
Flash the custom ROM/Gapps, followed by Formatting /data using the Advanced Options in the wipe menu.
Reboot.
If you can't find the format option (which is mandatory before a new boot of a custom ROM), you can use this command while in fastboot mode:
Code:
fastboot erase userdata
Formatting /data is required for Encrypted devices to reset the encryption key and avoid a Bootloop. Please refer to this thread for more Custom ROM flashing instructions. If all else fails, you could EDL flash your device through MI flash tool/Command line, this process costs money (you need an Authorized Xiaomi Account) to complete.
Thank you very much for your help!
Slim K said:
Does it reboot to fastboot or does it reboot to system? (aka a Bootloop).
Click to expand...
Click to collapse
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
DrakMC said:
Thank you very much for your help!
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
Click to expand...
Click to collapse
Again, when I say FORMAT, I meant formatting by typing ”yes".
Also, you haven't looked at the ArrowOS thread close enough, see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says latest R firmware, basically V12.0.7.0.RJGEUXM. Another point I mentioned is the fact that a recovery MIUI is flashable through TWRP/Orangefox and not Fastboot/Mi flash tool, It comes in a .zip archive.
Regarding returning to stock, have you tried booting into stock recovery after fastboot flash and factory resetting? That could work.
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
I'm using TWRP 3.5.2_10-1-surya.
DrakMC said:
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
View attachment 5307411
I'm using TWRP 3.5.2_10-1-surya.
Click to expand...
Click to collapse
Error 1 just means a mismatch between the underlying stock and the newly flashed ROM, just ignore it and flash ArrowOS, Format data and reboot. If it still doesn't work, then return to stock through fastboot. (I never encountered so many problems as you did)
I followed your instructions. When I turn on smartphone, the Poco logo is displayed, then the ArrowOS animation will appear and freezes. After a while, the mobile phone restarts and this is repeated over and over again. (If I flash MIUI using the Mi Flash Tool, I also have a bootloop.)
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
sevachcomunist4 said:
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
Click to expand...
Click to collapse
You're welcome! I'm glad I could help someone! It took me about 40+ hours to resolve this issue before trying all possible methods.
DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
please give me link
DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
DP FH said:
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
Click to expand...
Click to collapse
You are welcome. I'm glad I could help someone.
I was whole week without the phone until I've fixed it. It took me over 40 hours to fix the issue.
I have been trying to flash lineage-14.1-20190213-nightly-xt897-signed to my xt897 using TWRP 3.0.2 and all has seemed to go well, however I now can not boot past the "Warning Bootloader Unlocked" screen. I can still access TWRP. Makes no difference whether sideload or within TWRP. I have tried several other images. All have the same issue. I did not make a back up, and can not find a stock rom online. Does anybody have a copy of the stock rom image, or would somebody be able to help me get this thing to boot?
dezgrz said:
I have been trying to flash lineage-14.1-20190213-nightly-xt897-signed to my xt897 using TWRP 3.0.2 and all has seemed to go well, however I now can not boot past the "Warning Bootloader Unlocked" screen. I can still access TWRP. Makes no difference whether sideload or within TWRP. I have tried several other images. All have the same issue. I did not make a back up, and can not find a stock rom online. Does anybody have a copy of the stock rom image, or would somebody be able to help me get this thing to boot?
Click to expand...
Click to collapse
Just search your phone bro. Then add stock ROM.
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).