Database Users

[Q] Help: No OS installed message after lastest OTA update

Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?

Double_U said:
Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?
Click to expand...
Click to collapse
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.

blankit said:
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.
Click to expand...
Click to collapse
Wow, followed your advice and am now running CM 10.1.3.. Will see whether I keep it or try to return to stock but I'm so relieved that at least my phone is working again. Thanks ever so much!!

Your welcome.
Sent from my Nexus 4 using XDA Premium 4 mobile app

OnePlus 6T ADB Sideloading error

Hello everyone,
I am trying to install a custom ROM on my OnePlus 6T, as I currently have no OS installed. I tried ADB sideloading LineageOS through TWRP recovery, but it gives me an error: "* failed to read command:". I also tried using the ADB push command. But that did not work either, it gives me the error: "no such file or directory". My OnePlus 6T is rooted and has the bootloader unlocked. I also am in ADB Sideload mode in TWRP when I attempt the sideload if anyone was gonna ask.
Is it just a simple driver issue or what is going on?
I have trouble finding help online, so I hope you guys can help me find a solution.
P.S: I know this isn't the right board for this type of question, but I don't have enough posting history to post in the ROM and kernels board on the XDA forum. Kind request to the mods to move this thread there. Thanks.
Kind regards.

Have you tried things like
Rebooting PC?
Different USB cable?
Different USB port?
Ensured that you have the drivers loaded?
Make sure that the copy of ADB you are using is the latest?
What have you tried thus far?

U need latest adb files.... U r using outdated ones

Revert Android 11 to Android 10...

I have been on Android 11 DP since it was released and for the most part it has been stable. Unfortunately, my password app isn't working and could take months for it to be functional on 11.
Has anyone had success reverting back to 10 from 11? I've tried more times than I care to admit, but have not had any success.
Any suggestions would be welcomed.
G.

https://developers.google.com/android/images

Here you go

shannoncole05 said:
https://developers.google.com/android/images
Click to expand...
Click to collapse
I've tried several times, but have been unable to revert back!

Take note of which partition you are on, either A or B, check this on the main bootloader screen at the bottom of the screen. After you see if you're on A or B, flash the March factory image. As soon as the flash completes, you need to go right back to the bootloader screen and switch to the opposite partition that you are on. For example if you were on A before flashing the image, you need to switch to B and visa versa. To switch, from the bootloader screen type: fastboot --set-active=a or fastboot --set-active=b
After switching the active partition, reboot the phone and you'll be able to boot into Android 10 and will no longer be stuck on the 11 preview.

Hi there good people wonder if anyone could help me please i tried the android 11 through sideload but when i try going back to android 10 using the same method has i went to android 11 i get the following error from adb sideload
adb sideload flame-ota-qq2a.200305.003-1b5d6984.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
i have tried everything even another computer i get the same error tried different firmware i even tried uploading android 11 again has a test and that failed with the same error .... android 11 webpage say it can revert back to android 10 via adb sideload but i seam to be stuck here.... my bootloader is locked and i cannot unlock oem unlock thats why i choose adb sideload option
can anyone help me thank you

Downgrade
badwolf1972 said:
Hi there good people wonder if anyone could help me please i tried the android 11 through sideload but when i try going back to android 10 using the same method has i went to android 11 i get the following error from adb sideload
adb sideload flame-ota-qq2a.200305.003-1b5d6984.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
i have tried everything even another computer i get the same error tried different firmware i even tried uploading android 11 again has a test and that failed with the same error .... android 11 webpage say it can revert back to android 10 via adb sideload but i seam to be stuck here.... my bootloader is locked and i cannot unlock oem unlock thats why i choose adb sideload option
can anyone help me thank you
Click to expand...
Click to collapse
Did you try with latest platform here's the link.:good:
https://developer.android.com/studio/releases/platform-tools

Thank You!
caballon said:
Did you try with latest platform here's the link.:good:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I was having the same problem and this solved it! I had to download the tool from the Google site and copy/paste it into the "flash-all" folder and it worked!

klm2349 said:
I was having the same problem and this solved it! I had to download the tool from the Google site and copy/paste it into the "flash-all" folder and it worked!
Click to expand...
Click to collapse
Erased all right?

Question?
Not sure what the question is? It erased correctly and reinstalled Android 10.

Sideload OTA not working

I always used it to load updates, I can't succeed with Android 11 DP2.1
Deamon is started, adb devices shows the phone, but sideload fails with:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Suggestions, please?

Oneplus 6T qualcomm crash dump error when installing TWRP

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!