Failure to Boot - BLISS ROMS Q&A

Successful installation, however OS failed to boot.
OS is installed in an empty partition. After successfully installing, I restarted through 'advanced startup', then 'use a device', pressed Android-OS.
Through GRUB, I tried x86-android but that failed after 'Android_#'; laptop's stuck in a frozen terminal. Also tried x86-android nomodset, but that caused the screen to glitch blue.
The nightly kernels I've tried booting were the 7th July and 9th July updates

Bump

Related

[Q] Help - TV110 (S805) Partition Problems

I have a TV110 (Amlogic S805, 1gb/8gb) Android TV Box. I was trying to replace the stock ROM with Openelec v5.0.8 from Kerber. The update went fine until it rebooted to launch Openelec then it hung at the Openelec logo for over an hour. I thought the box was hung so I removed power and rebooted. It hung again in the same place so I decided to use the reset button to launch recovery. I must have cycled power too quickly because it would only show the boot logo and would go no further. Something was seriously wrong with the box.
I created a bootup SD card with TWRP recovery on it. I booted up into TWRP 2.8.6 without any issues but could not restore any of the partitions. TWRP was getting errors trying to mount all the partitions. I figured I could go back to stock (I have a NAND backup). When I try to wipe or restore it fails because the partitions are not mounted. I tried to install the old firmware using the install from TWRP and I get "Error executing updater binary in zip".
At this point I am stumped. What do I do next?? How do I get my box bootable again?? Can I somehow re-create the partitions??
Any help would be appreciated.

Stuck on BlissPop loadscreen. Help.

Hello! I installed BlissPop on my tablet before getting the new one from the callback program. This worked fine for several months, until suddenly the tablet decided not to boot.
The current situation:
The tablet boots onto the Nvidia logo, stays there for about 3 mins, then starts booting BlissPop. The boot is then stuck at the BlissPop animated loading screen. (It does not freeze the tablet or anything like that)
The tablet is not bricked (I think). I do not get the bricked error when checking on serial number. I dont remember which version of BlissPop i flashed over half a year ago.
What I have tried:
1) Flash a new custom ROM through Recovery, installing from zip through adb. I get an error while installing from zip:
- mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA at /data: Invalid argument.
- unmount of /data failed; no such volume.
- Patching system image unconditionally
Also, I cannot mount /data or /cache from CWM. Is my partition table messed up?
2) Flash to stock recovery image, through fastboot.
These steps always end up in the same way, nothing has happened during the flashing or installation. The device is still in the same state.
3) I tried installing another recovery type (now using CWM v.6.0.5.0), but I always end up with the old one.
What seems to be the common result on whatever I try, is that nothing happens. I even tried erasing all the data from the tablet, but nothing changes. Still boots into BlissPop and is stuck there. It seems like I cannot write anything to the tablet. Recovery mode (CWM) is also VERY slow, and it takes about 3 mins to get into CWM from fastboot bootloader screen.
Does anyone have any idea what I'm doing wrong, or have any tips for new things to try out?

Bootloop after updating to COS 13.1

I searched the forums before posting. 73 results came up and I read through and followed instructions of 7 different posts that seemed similar to mine (including the ones that appear when making a new thread), but nothing has worked or I haven't found a situation like mine.
Hi.
I have a HUGE problem and need help.
I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed the zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that according to someone in Oneplus forums. Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!
Thanks for any advice.
note: I used the signed flashable zip from here.
EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.
EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!
EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready). After that, I got the "Android is starting" "Optimizing app xx of xxx" message again, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!
EDIT 4: I remembered that I did a nandroid backup last February so I restored it with "restore" in TWRP. My phone has been stuck on the "Cyanogen" boot screen for about 40 minutes. I'm lost.
To recap everything:
1. I was trying to manually upgrade from COS 12.1 to COS 13.1
2. My phone was rooted, had TWRP recovery and ADB debugging was enabled in dev options. I can enter fastboot mode using hardware keys. I cannot enter recovery using hardware keys (shows a blank screen), but I can enter recovery using "fastboot boot recovery.img.
3. After I flashed COS 13.1, I was asked (in TWRP) if I wanted to install SU and I said yes and flashed it. This is when I was in a loop of being stuck on COS 13.1 splash screen for about 5-10 minutes and then my phone was "optimizing app xx of xxx" for 15 minutes and then rebooted and did everything all over again.
4. I tried to restored a nandroid backup using "restore" in TWRP, but phone is stuck in "cyanogen" splash screen for more than 40 minutes.
No replies...
Not sure what to do at this point.
I ended up wiping data and performing a factory reset through TWRP. Might try to upgrade again in the future.

Need help restoring phone after failed EdXposed installation

I tried installing EdXposed but after the reboot, it is stuck on the boot animation.
I tried rebooting with power+volUP, but I end up stuck on the loading screen again.
I tried loading TWRP with my computer (`fastboot boot twrp.img`), but my phone gets stuck on the "Fastboot Mode" screen.
I also tried flashing the EdXposed uninstaller.zip but I get stuck on the "Fastboot Mode" just like before.
I'm not sure what else to do — any suggestions?
Edit: this is resolved. I was using an outdated TWRP image. I used a new one, installed the EdXposed uninstaller, and I can boot again!

My phone stuck flashing TWRP

I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Probably an encryption issue. As twrp doesn't support encryption in A11. I don't know what's causing the black screen. The best way out is using msmdownload tool, I believe.
CodeRida said:
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Click to expand...
Click to collapse
in that case reflash twrp,root and the os you were using(in the order you did it the first time and, when you get your next ota update
extract it and edit to remove code which makes it look for stock recovery
select all the decompressed files and compress to ota zip file again
then in update area choose local update and use the file you just edited

Categories

Resources