Develop Bugs

Unable to boot

Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)

JunkTardis said:
Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)
Click to expand...
Click to collapse
best thing is go to recovery factory reset and flash viper again
get to recovery by power vol down just in case you dont know

JunkTardis said:
Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)
Click to expand...
Click to collapse
there is 2 flashable zips in nexus 5 forum to swap between dalvik and art cant see why they shouldnt work can all ways ask and just side load them and flash them in recovery

jaythenut said:
best thing is go to recovery factory reset and flash viper again
get to recovery by power vol down just in case you dont know
Click to expand...
Click to collapse
That did not work at all, the entire phone was completely frozen on the Venom bootscreen. I did manage with some fiddling to get into Recovery. I did Power+VolUp to force reboot the device, then when the screen went black very quickly switched and did Power+VolDown to enter HBOOT and go to TWRP from there. Painstaking, and took a few goes. Luckily I still had my VenomRom on the USB Stick and after trying multiple different options in TWRP I made sure I had a backup of my data, and reinstalled Venom fresh with a full wipe. I tried doing just an install over it, as that's worked in the past - but the issue persisted. A full wipe was required.
For future until this bug is resolved, if you want to try ART on the One M8 with Venom, make sure to have a nandroid backup to hand as always. Mine was 2 days out of date, but no real loss to me
Thanks for your help!

Do an adb pull you should still have adb access at the boot screen.
/data/property/persist.sys.dalvik.vm.lib is a textfile containing one of two values: 'libart.so' or 'libdvm.so'. You can change from ART to Dalvik simply by editing this file.
Ex: adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'
It's because deodexed roms can't use art
Sent from my HTC One_M8 using Tapatalk

graffixnyc said:
Do an adb pull you should still have adb access at the boot screen.
/data/property/persist.sys.dalvik.vm.lib is a textfile containing one of two values: 'libart.so' or 'libdvm.so'. You can change from ART to Dalvik simply by editing this file.
Ex: adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'
It's because deodexed roms can't use art
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
That has actually helped me, and I appreciate it. I'm relatively experienced and comfortable in doing a lot of Android things such as bootloader unlocking and editing system files but I had no clue that deodexed roms can't use ART. I should submit a warning to the VenomDevs to grey out or hide the option in Developer Options or at least provide a warning

I killed my watch

1 week ago i bought in china the watch .i dont know Chinese and i was just there for business so i thought that when i will connect to my phone it will automatically change to English but that never happend . So i tried several threads in xda to understand how it is working and what can i do . And i followed the thread that says to flash another system img recovery and boot . So i first unlocked the bootloader and booted on it and i flash the images and tried to reboot to recovery but already the recovey option in the bootloader is missing i get only shutdown , reboot , reboot bootloader , so i thought that i haven't correct flash the recovery.img so i flash it again but still the same . I also tried twrp recoveries and other recoveries that i found in other threads but still the same i can only boot to bootloader and nothing else . Has any one had the same problem and fixed it ? And if not were can i find the stock chinese firmware to try to flash it maybe it will come back to life .. thanks in advance

Have you tried using adb and fastboot commands?
Ex::
adb reboot-bootloader (for bootloader)
adb push xxxxxxx.img or xxxxxxx.zip /sdcard/ (for transfer files to sdcard)
adb push recovery.img /sdcard/ (for transfer yours custom recovery - i recommend the latest 3.1.1.0 because the others have some bugs)
after that boot to recovery: fastboot boot recovery.img (personally i never tried to flash the recovery but just boot it, baut it works)
from recovery just install the files that you have transferred earlier to sdcard (oh, and prior that erase everything except internal memory, or that toot but you have to transfer your files again)
ex: install zip (i recommend negalite) after that install kernel (negalite too) and install performance or battery booster .
Oh, after kernel install, it will automatically reboot, so you have to repeat the process to install the booster.
Reboot.
p.s. - the reboot process take LOOONG, so wait patiently.
Hope i could help you.

Currently my watch is stuck on AW boot logo from Skin Sturgeon kernel, how can I boot back to stock to reflash? Am unable to access adb as it doesn't seem to get that far in the boot process.

Enter bootloader
spicerackk said:
Currently my watch is stuck on AW boot logo from Skin Sturgeon kernel, how can I boot back to stock to reflash? Am unable to access adb as it doesn't seem to get that far in the boot process.
Click to expand...
Click to collapse
If you want to enter the bootloader, to choose, where u want to reboot and you are stuck:
Hold the button on your watch...hold it, till you feel the first vibration after the restart at the HUAWEI-Logo. Then, press the button once again (Its just timing).
It should show you your bootloader and you can restart into recovery or wherever you want.
Hope I could help :highfive:

How can I keep MIUI from overwrite TWRP with stock recovery after a ROM flash?

I'm on fw Global 9.6.6.0.
(Bought the phone 'bogus' unlocked with "fake" 9.6.4.0, bricked it while trying to restore chinese fw and re-lock bootloader using miflash - I'm not doing that again
brought it back to life using the steps from Omer919's thread - thanks Omer919 and Nijel8)
I deleted install-recovery.sh from system/bin using TWRP's file manager before first boot, but it still overwrites MIUI recovery.
It's not a huge deal because I guess I can always fastboot flash twrp before flashing any new ROM, but does anyone have a solution? Much appreciated!

You have to boot to twrp right after flashing.
Go to twrp official site, choose your device and follow exactly instruction to the end.
It wouldnt harm your device if you reboot it to twrp twice.

Thanks, I tried but it reverts to stock recovery. After flashing TWRP in fastboot, I either try Fastboot boot twrp.img or disconnect the cable and hold power and vol+.
Either way, it goes into TWRP, and I make it boot back into TWRP several times with no problem.
But as soon as I boot to System, it reverts to stock.
TWRP site gives me this info (but it didn't work):
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

OMG I found it - Google really is a friend. All I had to do was install Magisk before booting to System.
Below are my exact steps, if that helps someone.
Preliminary:
Download Magisk 17.1 zip, place it on a USB flashdrive.
Install latest magiskmanager apk from Play store (or sideload it if not on the store)
1- In Fastboot:
fastboot flash recovery twrp.img
fastboot boot twrp.img (If all goes well, this boots to TWRP; if prompted for a code, hit cancel)
2- Disconnect the cable.
Reboot to recovery once more (just to make sure, this is probably redundant; hit cancel if prompted for a code)
3- Mount USB-OTG, connect your flashdrive.
Install Magisk.
During the installation, you'll see some red fail lines, but Magisk seems to work around the encryption, just be patient.
4-Reboot System. You're done! Launch MagiskManager. Device is rooted in the process, too. (Verify with a root checker app).
Power Off. Hit Power + volume Up - You should boot to TWRP.

thanks a million McNoob. I was lost, but due to your hints I managed to install Magisk

Hi i cant boot to twrp and it keeps reverting to stock recover..
already tried this "fastboot flash recovery twrp.img
fastboot boot twrp.img (If all goes well, this boots to TWRP; if prompted for a code, hit cancel) "
after sending the last command line the phone reboot but its just black screen.. i try to reboot the phone again and boot it to recovery but still stock recovery is preset.. thanks

Thanks man! It worked for me as well!

Lamantin001 said:
Thanks man! It worked for me as well!
Click to expand...
Click to collapse
How did it work for you

thanks but.... the twrp for nitrogen is corrupted apparently and nothing work

Relock bootloader on LOS microG

Hello all
I desperately try to relock my bootloader but failed many times and I am shortly before giving up. I was once on a locked bootloader on LOS but camera didn't work. (Couldn't reproduce)
Maybe you see something I missed out / didn't understand.
The main reason is, that some apps like ebanking check the state of the bootloader. And they also don't go through Securenet because of huawei.
So what I tried with this setup:
sign both boot.img and twrp.img with BootSignature.jar using own private key
Twrp Using: twrp-3.5.2_9-0-oneplus3
boot img from:
lineage-17.1-20210330-microG-oneplus3
lineage-18.1-20210403-microG-oneplus3
With firmware: oxygenos-9.0.6-firmware-3 from https://github.com/nvertigo/firmware-3t/tree/master/archive/op3
Mostly I got the ideas from https://forum.xda-developers.com/t/device-forum-rules-please-read-before-posting.3333345/
And what I do is this:
Using fastboot flash signed recovery
boot into recovery
whipe everything (is this needed every time?), data, factory reset, all partitions except internal & usb
reboot into recovery
sideload lineageos with signed boot.img inside
fastboot oem unlock => directly restarts after 'yes'
boot into LOS
fastboot oem unlock => directly restarts after 'yes' again
Do you see something I do wrong? Should I use other versions/files?
Hope to find a way
Edit: Also I can go back to stock where it gets locked again using the latest OnePlus3_16_A.86_191104_repack.

Problem Rebooting into Recovery

I am in the process of installing LineageOS 18.1 onto a Pixel 3 XL (I have done a Pixel 3 before with no issues). I am following the instructions from lineageos.org (https://wiki.lineageos.org/devices/crosshatch/install). It is specific instruction for the Pixel 3 XL. I have successfully completed the first number of steps but got stuck on the last one noted below:
Unlocking Bootloader (ALL COMPLETE)
enable OEM unlock
connect device to PC
adb reboot bootloader
fastboot devices
fastboot flashing unlock
reboot
re-enable usb debugging
Temporarily Booting a Custom Recovery
download a custom recover (lineage-18.1-20210803-recovery-crosshatch.img) - COMPLETE
connect device to PC - COMPLETE
adb reboot bootloader - COMPLETE
fastboot devices - COMPLETE
fastboot flash boot lineage-18.1-20210803-recover-crosshatch.img - COMPLETE (received msg that sending and writing to boot_a is okay)
reboot into recovery - INCOMPLETE
will not reboot into recovery, stays in fastboot mode
last line on fastboot mode screen says "no valid slot to boot" at one point it also said "error booting boot.img"
Any idea/suggestions on what would be the problem? I did try redoing the fastboot flash boot command an additional time and again it said it sent and wrote ok, however, still unable to reboot into recovery. I did not check the version of android on the phone before i flashed the lineage 18.1 recovery - could that be the problem? Might it be that the phone cannot run LIneage 18.1 because it is on android 10? (which I'm not sure how to check at this point). If this is the problem what would be the best solution - reflash with a lineage 17.1? Or, is there a way at this point to check and upgrade the android on the phone? Perhaps there is another problem entirely.