HI all,
I've come from flashing Samsung S4's for years but after trying to flash an update I got the boot screen and nothing happens.
Here's the situation.
I had originally installed PureNexus, rooted, unlocked the boot loader and probably turned off USB ADB settings (and I don't typically want an alert when plugging in the USB cable) as I usually transfer media and ROM's to the download folder for future flashing.
I saw that 6.01 was released and saw that the bootloader and radio were updated. So I tried to flash those before updating with PureNexus 6.01.
I did a nandroid backup before I did this, knowing something might go wrong.
I think my camera wasn't working so I tried a nandroid recovery to get it back.
Unfortunately I didn't read about the password encryption bug which TWRP had as I did the restore in my car and didn't have internet as it was free down time. When it was completed, I got the failed password issue. So I decided just to format everything. I used TWRP and formatted everything including the vendor partition. Of course, I forgot it would delete the Nandroid, too. I'm too used to having a spare external SD card to store all of the Nandroids on.
Anyway after that I can only get to TWRP.
I've tried installing the original 6.0 ROM, PureNexus ROM through TWRP with the appropriate ZIP files. It says it's completed, no errors but just the boot screen.
I've tried restoring through ADB with Windows 10 and through the USB. I don't get to an ADB selection on the bootloader, but can get to the ADB sideload throught TWRP. The problem is when I tried to restore through ADB nothing happens as it says "waiting" when I use fastboot flash-all. ADB devices does give me an ID when I do ADB so it is connecting. However, I believe ADB is waiting for the USB-ADB to be turned on which I can't do because I can't get to the OS system partition.
I've tried using several of the Skip Soft Toolkit and again, it waits and says closed.
I'm assuming that USB-ADB is closed and not turned on. I don't know why TWRP can't overwrite the system partitions if I try to flash, unless it's still encrypted but shouldn't be as I formatted everything, except for the boot loader and that is unlocked as I get the screen that I should lock the bootloader because the OS can't tell if it is corrupted.
Any ideas? I can only think if someone sends me a Nandroid of a configuration that may flash it back to a level I can get into Android and then get back to USB ADB and do a clean install with fastboot flash-all.
Please help!! Thanks in advance for your suggestions. I hope I gave you enough information to help me out.
Update. I apparently found a way. Luckily TWRP has a Flash image feature as well as flashing the vendor image. Flashed PureNexus 6.01 and PureNexus Gapps and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Methods tried - 1-21
*TWRP #IRC*
Boot phone into TWRP, run these commands. You may have to flash factory images one more time if you get stuck at the splash screen (rather than looping)
Enter adb shell then copy and paste these two lines, separately.
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix bootloops for most. TWRP 3.2.1-1 causes a fatal error. The above shell commands should get 'most' running.
-----------------------------------------------------------------------
All methods below are MTC20F unless otherwise stated.
If you notice a method that worked, that I haven't listed please share with me with the source so I can have a full list.
Method 1
Followed instructions on flashing full firmware, found on g.co/ABH
Method 2
Followed instructions for OTA, found on g.co/ABH
Method 3
Followed @Heisenberg instructions in the HOWTO for manually flashing firmware via fastboot
Method 4
Flashed stock firmware, then wiped data/cache in stock recovery
Method 5
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-0
Method 6
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-1
Method 7
Flashed firmware via fastboot, then flashed full stock firmware through twrp (specify which version)
Method 8
Flashed firmware via fastboot, then flashed OTA firmware through twrp (specify which version)
Method 9
Utilized Wugs tool to flash full firmware
Method 10
Flashed firmware via fastboot, then sideload OTA via adb
Method 11
Flashed firmware, then flash your own TWRP backup
Method 12
@Eric214 says
Advanced wipe - System, Data, Cache and Dalvik.
Flash vendor image MTC20F.
Flash PureNexus, Gapps, SuperSu 2.76.
Reboot.
Method 13
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via fastboot
Method 14
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via update.zip
Method 15
@shiftr182 method
Fastboot firmware, flash twrp, repair and resize, flash nougat bootloader, flash nougat update from HERE
Method 16
@neaznc021 method
"I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked"
Method 17
Fastboot stock, flash backup, flash MM ROM
Method 18
@rbouza1 method
"Fastboot format user data partition
Run factory image
Fastboot bootloader radio vendor
Flash twrp
Try and boot if not flash stock rom /any mm rom boot into twrp and try a restore. Those were my steps and it worked"
Method 19
@FragmentsOfLife method
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Method 20 @avivasaf
"Got backup from my friend, you need this!
Format userdata
Flash twrp
Make any backup
Move the good backup to the file backup
Restore it
Flash any Mm rom(i flashed cm13)
Fastboot flash mm bootloader, radio, vendor
And you got it!!!!"
Method 21 @Azhar05 method
flash developer preview 5 and flash latest twrp and then copy mtc 20f vendor image to twrp folder and then in twrp install image mtc 20f
Method 22
Let me know if you have more!
reserve 2
tr4nqui1i7y said:
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Click to expand...
Click to collapse
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
sixgunmojo said:
[/HIDE]
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
Click to expand...
Click to collapse
Thanks, that would be useful. I'm thinking of how to incorporate that in a simple enough way that people don't accidentally provide incorrect information.
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
busbeepbeep said:
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
Click to expand...
Click to collapse
Your device isn't recognized by adb/fastboot?
tr4nqui1i7y said:
Your device isn't recognized by adb/fastboot?
Click to expand...
Click to collapse
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
busbeepbeep said:
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
Click to expand...
Click to collapse
Try this tool to make things a little easier, and more automated for now. Wugs
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
busbeepbeep said:
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
Click to expand...
Click to collapse
Boot into bootloader manually then try to run something
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Eric214 said:
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Click to expand...
Click to collapse
What eMMC is your device using, if you don't mind?
tr4nqui1i7y said:
What eMMC is your device using, if you don't mind?
Click to expand...
Click to collapse
64GB Toshiba
Eric214 said:
64GB Toshiba
Click to expand...
Click to collapse
Just to clarify, you were able to get your device to boot?
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Jammol said:
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Click to expand...
Click to collapse
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
tr4nqui1i7y said:
Just to clarify, you were able to get your device to boot?
Click to expand...
Click to collapse
Originally i had no issues I flashed factory images from Pure Nexus June build Via Fastboot. Rebooted the phone and took the OTA through the phone and then flashed TWRP 3.0.2-1 (the Newest one) and through TWRP flashed SuperSU 2.76 then FDR the phone before setting it up. All was fine and perfect. I made a backup and then factory data reset my phone Saturday and then restrored the backup. No go, Bootloop city. Got home did most of what was mentioned and nothing happened. Flashed PN through TWRP 3.0.2-1 and flashed my stock rom that came with the phone in Feb (29Q) and restored my EFS (I backup my EFS after any Android version change). The phone booted perfectly. no issues since. Took me about 2 hours total once i got home and was able to start using ADB and Fastboot commands.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
Also i forgot to add my info....
BL: 03.58
Baseband: 3.72
Varient: Angler-VN2
CPU: 0x20001
eMMC: 64GB Toshiba
DRAM: 3072MB Samsung LDDR4
UNLOCKED
Qfuse status: ENABLED
Off-mode-charge: Enabled
Download Mode: DISABLED
I also forgot, I was enrolled in the beta program obviously since i took the OTA through the phone.
tr4nqui1i7y said:
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
Click to expand...
Click to collapse
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Jammol said:
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Click to expand...
Click to collapse
Alright, thanks for clarifying. Didn't want to accidentally add something to the second post haha.
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
x0nar said:
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
Click to expand...
Click to collapse
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You have to install marshmallow firmware first.
Best option would be to go back to the working TWRP version, flash oxygenos, reboot to Oxygen once, flash new recovery in fastboot, reboot recovery, flash rom
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't know if this does anything different, but here's what worked for me
1. Ensure that device enters into fastboot mode
2. "fastboot flash recovery recovery.img"
3. **IMP** After your flashing is successful, directly enter the device into recovery mode by pressimg Power (+) Vol Down button.
4. Now a TWRP prompt shall appear asking your permit for modifications, swipe yes.
Note that: I'm not sure if this makes a difference, but earlier I rebooted after Fastboot and then entered into recovery, but the key was to directly enter into recovery after fastboot.
Let me know if that works for you.
So I unlocked bootloader on my redmi note 7.
Then I flashed twrp and rooted my device.
Then I flashed pixel experience but it stuck on the Google logo after reboot. I tried factory reset in twrp but it didn't work.
So I restored the backup I did before flashing pixel experience.
And then my phone stuck on bootloop.
So I booted into fastboot mode and flashed the fastboot rom and it worked. I have successfully unbricked my device.
But now it shows "find device storage corrupted your device is unsafe now"
Everything works fine except I can't turn on find device and also can't install miui ota updates via twrp.
(And also when flashing twrp for the first time when I reboot it showed the stock recovery because I hadn't flashed disable dm-verify because when I am in twrp and try to mount my system to my computer my phone doesn't show up in the computer. So first I copied the disable dm-verify file then again flashed twrp then booted into twrp and then flashed disable dm-verify. I don't know if it is necessary to format data when flashing twrp. Maybe that's why the problem occured. I don't know.)
Please help.
Thank you.
Extract persist.img from official fastboot rom and replace the existing persist in Orangefox.
At least it helped me.
Persist.img flash through recovery gonna fix the problem but forget about Netflix and L1!!
Personally speaking had that problem with corrupted message pop up every time i reboot my device and when i flashed the persist.img through OrangeFox recovery i lost L1 forever (and there is no turning back).
If you wanna try that method i highly suggest you to Backup your Persist Partition first.
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Lucky-thirteen said:
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Click to expand...
Click to collapse
I tried may hours to define the problem's source but i think that's unclear in every situation. Others say that's a persist.img corruption while others had that problem with Mi Account corruption, etc.
Mine corrupted message came when i tried to flash Global Official MIUI in a EU variant device through normal process that doesn't engage any kind of Persist partition rewrite.
I had a backup of persist.img and flashed original from EU fastboot file and finally after that I repatch my old persist.img. The first time i did that process my device and L1 worked properly (even that spam message disappeared) but after a long time that I tried same process for same problem i completely lost my L1 [strange af!].
So, a safe process to try now is to flash back the official fastboot image of your variant (Erase + Lock [for L1]) through MiFlash tool and check that corruption message if it goes away (be careful to flash the correct fastboot image or you will get a a bricked device).
In conclusion it's Extremely advisable to keep a full backup of your partitions and especially Persist partition if you wanna flash Roms and generally unlock bootloader!
I use twrp recovery
I don't know about orange fox recovery
Strange51 said:
I use twrp recovery
I don't know about orange fox recovery
Click to expand...
Click to collapse
Always use OrangeFox for Lavender here is the link (download and test with latest R10.1_02-Stable)
Hi,
I have an international 6t and trying to install Lineage 18.1. After the following steps, I get the qualcomm crash dump error:
- Use MSM to install: ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222
- System Update to latest version of OOS: 11.1.2.2
- Unlock bootloader (tried via both ADB and TOOL ALL IN ONE)
- Flash: twrp-installer-3.6.0_9-0-fajita (tried via both ADB and TOOL ALL IN ONE)
- Qualcomm crash dump error
Am I doing anything wrong? I have looked at different guides and seems to be the right steps.
I also tried using MSM to install an older (9) ROM and didn't uprade. Found here that I could get TWRP working... However, after flashing Lineage Rom I got stuck in fastboot loop.
Some hours later...
OK, so I just tried it again, following this guidance exactly (and with Lineage Recover rather than TWRP) : https://lineageosroms.com/fajita/
Without TWRP I didn't have the crash dump error... but when I came to finally Reboot the System, I got another error:
Can't load Android System. Your data may be corrupt......
Then with this text at the bottom:
E: Failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
E Emulated failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
Any help very much appreciated!
benh77 said:
Hi,
I have an international 6t and trying to install Lineage 18.1. After the following steps, I get the qualcomm crash dump error:
- Use MSM to install: ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222
- System Update to latest version of OOS: 11.1.2.2
- Unlock bootloader (tried via both ADB and TOOL ALL IN ONE)
- Flash: twrp-installer-3.6.0_9-0-fajita (tried via both ADB and TOOL ALL IN ONE)
- Qualcomm crash dump error
Am I doing anything wrong? I have looked at different guides and seems to be the right steps.
I also tried using MSM to install an older (9) ROM and didn't uprade. Found here that I could get TWRP working... However, after flashing Lineage Rom I got stuck in fastboot loop.
Some hours later...
OK, so I just tried it again, following this guidance exactly (and with Lineage Recover rather than TWRP) : https://lineageosroms.com/fajita/
Without TWRP I didn't have the crash dump error... but when I came to finally Reboot the System, I got another error:
Can't load Android System. Your data may be corrupt......
Then with this text at the bottom:
E: Failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
E Emulated failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
Any help very much appreciated!
Click to expand...
Click to collapse
You should have already know by now that TWRP version is not compatible with OOS11.
You can try to restore your Phone with MSM tool and try again with this version [file attached]
Thanks
s.seila said:
You should have already know by now that TWRP version is not compatible with OOS11.
You can try to restore your Phone with MSM tool and try again with this version [file attached]
Click to expand...
Click to collapse
Thanks, I just tried with this... although with TWRP I am unable to switch on ADB Sideload. It just times out forever.
With Lineage Recovery instead of TWRP I could use ADB, although got other errors as in initial message.
benh77 said:
Thanks
Thanks, I just tried with this... although with TWRP I am unable to switch on ADB Sideload. It just times out forever.
With Lineage Recovery instead of TWRP I could use ADB, although got other errors as in initial message.
Click to expand...
Click to collapse
I thought sideload worked on that twrp. But you can try booting that twrp then install lineage recovery or another version of twrp from twrp.
Thanks, I think there is an underlying issue with my phone or I am just out of my depth. Pretty much followed every set of instructions I can find and always results in a bricking, bootloop or qualcomm crash dump. Was a second hand phone, so just got it back to 11.1.2.2 and will re-sell.
Got my trusted Z5 Compact onto 17.1 and that will do me for a few years yet!