Related
Has anyone been able to successfully installed Lineage on an HTc One A9? I've unlocked my bootloader and turned S Off but Recovery Mode will not accept a flash of TWRP. Previous attempts have frozen device at Recovery Mode screen. The only way to correct is through reflashing factory ROM. I'm running the at&t version with Marshmallow. Please help!
StarSage said:
Has anyone been able to successfully installed Lineage on an HTc One A9? I've unlocked my bootloader and turned S Off but Recovery Mode will not accept a flash of TWRP. Previous attempts have frozen device at Recovery Mode screen. The only way to correct is through reflashing factory ROM. I'm running the at&t version with Marshmallow. Please help!
Click to expand...
Click to collapse
I'm not sure if you're aware of this but, LineageOS has 2 different types of builds for the A9...
Are you sure that your using the "hiaeul" builds on the following link?
https://download.lineageos.org/hiaeul
That's the one for the AT&T HTC One A9.
Just wondering...
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
Yup. I was attempting to load hiaeul. No go. HTC's boot splash page just laughs at me. Denied
My HTC One A9 hiaeul is also failing to boot after installing lineageos-14.1 from TWRP.
It stops at the white boot screen, green "htc" and red "This build is for development purposes" message.
I'm surprised there are no answers posted here. There is only one correct package it will allow to be installed, so I don't think "try the other A9" is any sort of final answer.
Maybe the bootloader is too old?? If so, are there any solutions?
Hi,
got the same isue with my german A9. I changed Firmware Version to latest available 2.X Version and flashed the Nougat RUU from last years April (i guess). Stock Nougat is running great...but even after flashing TWRP via fastboot the Stock System will start staying in a bootloop of the HTC Logo. Turning off, vibrating, Logo, tunring off, vibrating, Logo and so on.
When I Flash latest LineageOS and gapps pico, it starts up and stays in Lineage-Boot-Animation for hours (let it try while i was sleeping last night for 6 hours)
Any idea? I can´t find out, which Firmware Version i Need for a working LineageOS. Also I don´t know if i Need some Special boot-Image or how the way is. I wonder why there isn´t a tutoril for this issue, though I found a few threads dealing with that issue and pretending I´m not alone.
Greetz Cutter
After trying and trying different paths it finally works.
What I did:
1.) Flash the right firmware 2.xx (2.17.401.2 for me) via Download Mode and SD-Card method
2.) Flash the complete RUU for that firmware version with HTC nougat the same way like the firmware
3.) Booted the system to work.
4.) Flashed twrp 3.2.1.0 via Fastboot in Download Mode
5.) Booted Recovery and formated data and wiped everything (including system and data) except internal memory, external memory and USB-OTG
6.) Followed the instructions on lineagos website for installing lineageOS for the first time
6a.) Install lineageOS zip via recovery
6b.) NO(!!) wipe dalvik/cache
6c.) REBOOT into recovery (which is writen to be very important
6d.) Install gapps pico - and again no wipe dalvik afterwards
6e.) Flash lineageos_supersu zip
6f.) reboot system for the first time and be patient
System works. Hope i could help
Cheers
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error
Code:
FAILED (remote: unkown command)
since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Bennou said:
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Click to expand...
Click to collapse
It's clearly written on the official website and in the official TWRP support thread for the g4 what you have to do when on Nougat bootloader and want to flash TWRP... and keeping it.
Sent from my LG-H815 using XDA Labs
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Bennou said:
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Click to expand...
Click to collapse
Okay if it doesn't work for you you must do something wrong. It works 100%. If you really want help you should explain in detail exactly which steps you took as otherwise it's all just guessing what you're doing.
Sent from my LG-H815 using XDA Labs
Indeed, I didn't followed the procedure exactly, didn't do the step after flashing TWRP (removing battery and boot manually to recovery). Well thank you, was my bad on that.
Should I do a clean new install of cypheros or should I keep it like that, what would be your advice ? Knowing that at the moment CypherOS works like a charm. I also plan to install Magisk on it to root it.
To help others newbie like me, solution can be found here : https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
I've been at this for days now and I am getting absolutely nowhere and I'm very frustrated. I have a Verizon model G7 (LM-G710VM). I was able to unlock the bootloader without much difficulty by following this guide, but from that point on I've had nothing but problems.
In order to install Evo X I need to have stock Android 10 installed, and OrangeFox recovery. So I crossflashed various Android 10 ROMs and attempted to install OrangeFox, but no matter what ROM I used, OrangeFox would not install because fastboot won't open on my phone unless Android 8 is installed. So I flashed an Android 8 ROM and tried again, but the "fastboot flash" command failed every time I tried with an error that said "read status failed (too many links)". I googled the error and found absolutely nothing. I googled how to install OrangeFox on an LG G7 and again I found nothing. I dug through every thread I could find on this forum and again I found nothing. The orangeFox instructions said that you could install OrangeFox using another recovery like TWRP, so I tried to install TWRP, but the only guide I could find anywhere for installing TWRP on a G7 required Android 9 and fastboot, which I still haven't figured out how to have both at the same time. I'm exhausted now and stuck, and I would really appreciate if anyone on here could explain how I can get Evo X on my phone or at least point me in the right direction to make some progress.
Current status: bootloader unlocked, can crossflash whatever ROM I need, fastboot not working with Android 9 or 10 ROMs, can't install recovery
Goal: install Evolution X on my Verizon LG G7 ThinQ
Hi, I have Moto G7 Power xt1955-4 with Android 10 Q, unlocked for any GSM carrier, used on T-Mobile network. I unlocked the bootloader and i'm trying to install TWRP recovery image into it. Mostly I follow this guide https://www.androidinfotech.com/root-moto-g7-power-ocean-android-10 . I got the latest available for my phone TWRP -3.5.2-10-ocean from https://dl.twrp.me/ocean/twrp-3.5.2_10-0-ocean.img.html, switched my phone into fastboot mode so it's visible to 'fastboot devices" command, then i run "fastboot boot twrp-3.5.2_10-0-ocean.img" Phone reboots to temporary TWRP now, shows "Enter password for User [0] - ... Data successfully decrypted".
Now, when I try to permanently install TWRP, I got a problem, even though everything looks ok, no error messages: first I installed Disable_Dm-Verity_ForceEncrypt.zip file, with Success. Then I installed twrp-installer-3.5.2_10-0-ocean.zip via TWRP itself: it shows "######## TWRP installer for A/B devices ######## Running image patcher on boot_a... Running image patcher on boot_b... Image patcher complete! Done installing TWRP ***Note: You are now unrooted!*** Updating partition details... Success!" - note no errors here.
BUT when I reboot into recovery mode again, I see only TWRP logo, then phone beeps for 1 sec, and nothing happens after that, no menu shows up, no prompt to "Enter password for user" as before. No response from screen touches. Only reboot helps.
So I understand that TWRP was not installed correctly. What did I do wrong?
Any suggestions will be appreciated.
You should join and follow the G7P (Ocean) telegram group if you haven't already done so. Any questions can be asked there or are already answered in the #notes section. As far as twrp goes because the device is a/b type I never install the zip. I connect to pc and fast boot twrp image to flash ROMs.
Skippy12359 said:
You should join and follow the G7P (Ocean) telegram group if you haven't already done so. Any questions can be asked there or are already answered in the #notes section. As far as twrp goes because the device is a/b type I never install the zip. I connect to pc and fast boot twrp image to flash ROMs.
Click to expand...
Click to collapse
Thank you Skippy12359, I found just "Moto G7 Power Ocean/River Channel" on Telegram, with 10 subscribers - is it the one you mentioned?
My goal is to install Magisk-v23 on my phone, to complete rooting procedure. I was going to use TWRP for this, and install it via zip file. But if I use temporary TWRP and just install Magisk-v23.0_renamed_apk.zip, after reboot Magisk app shows "Installed" status as N/A! Apparently it doesn't work as intended... So I thought that permanently installed TWRP would give better result.
UPD: Also I see "Moto G⁷ Power | Builds™" channel with 445 subscribers, and "Moto G⁷ Power | Discussion™" with 379 members. Signed up for those!
There's a Moto g7 power discussion group and a Moto g7 power builds group. If you're new to flashing ROMs put all your ROMs, magisk, gapp files on your sdcard. Then fastboot twrp and flash ROMs, magisk from there. You can install the twrp zip if you want just found it easier not to because it gets overwritten anyway because the device has no separate partition for recovery like an A- only has for example.
Actually this method (fastboot to temporary TWRP, then install magisk.zip file from sd card) works! I was able to install Magisk this way, and first time it boots normally, Magisk shows Install status v23, CheckRoot app shows that everything is ok. But on second reboot i'm getting into bootloop After Warning message and 5 sec wait my phone beeps and reboots.
Magisk has an uninstall zip file if you have boot problems. Once magisk is uninstalled from recovery it should boot up fine. There is also a magisk canary version on github which should fix any boot issues after flashing. You need both the magisk zip and the magisk app installed to have full root
I try Magisk-Canary (after uninstalling Magisk v23 by renaming zip file to uninstall.zip and run it via TWRP) from https://github.com/topjohnwu/Magisk, the result is the same- first boot is Ok, Magisk app shows that it's installed (Magisk status 5d6d2417 (23015) version installed), but second boot gives me bootloop...
What ROM are you using?
I use Original stock ROM, that comes with the phone. XT1955-4_OCEAN_RETEU_10_QPOS30.52-29-7-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip file from ttps://mirrors.lolinet.com/firmware/moto/ocean/official/RETEU ( i just found it to get boot.img and patch it with Magisk, I didn't change original firmware , just unlocked bootloader.
I haven't used stock for over a year and I don't recall having any problems rooting or ever had a boot loop on rooted stock Q. Also I've never needed to patch a boot image to get root. I just reflashed stock firmware, installed all the apps I wanted and fast boot to recovery. Flash copy partitions zip and then flash Magisk. After reboot to system I install Magisk app and I'm done. Always worked for me. Rooted and no reboots.
I assume that you have Moto xt1955-4, correct? Which ROM you have installed then? At the time of Magisk installation , was it custom ROM or original stock ROM on your phone?
I have the usa model of the same phone xt1955-5 and have always had it rooted whatever custom ROM or stock firmware used at the time. I'm currently on AICP 11 official custom ROM but switch frequently from Arrow, Colt and other ROMs.
Skippy12359 said:
I have the usa model of the same phone xt1955-5 and have always had it rooted whatever custom ROM or stock firmware used at the time. I'm currently on AICP 11 official custom ROM but switch frequently from Arrow, Colt and other ROMs.
Click to expand...
Click to collapse
Hey Skippy, When I originally got the phone, I bought it outright from Cricket. A Supra, but still the same as G7 Power.. No payments. No years agreements. Now that it is no longer supported, I want to unlock the bootloader and install a custom rom. Setup ADB and went to Motorola's website for the unlock code. I get "Does not qualify for unlocking." For the above two reasons, I'm a bit miffed. Has anyone found a work-a-round for this? I got up at 6 AM. All day studying and learning how to do this. Only to get the message. "No you can't. Sorry. Notta". And with Motorola's piss poor support policy, it grinds my gears.
Danny3568 said:
Hey Skippy, When I originally got the phone, I bought it outright from Cricket. A Supra, but still the same as G7 Power.. No payments. No years agreements. Now that it is no longer supported, I want to unlock the bootloader and install a custom rom. Setup ADB and went to Motorola's website for the unlock code. I get "Does not qualify for unlocking." For the above two reasons, I'm a bit miffed. Has anyone found a work-a-round for this? I got up at 6 AM. All day studying and learning how to do this. Only to get the message. "No you can't. Sorry. Notta". And with Motorola's piss poor support policy, it grinds my gears.
Click to expand...
Click to collapse
I have the TMobile variant codenamed Ocean, so I'm not going to be much help on your question. I suggest you ask in the Moto g7 power discussion group on telegram. I'm sure someone there can let you know if the cricket variant is unlockable or not. Good luck
Skippy12359 said:
I have the TMobile variant codenamed Ocean, so I'm not going to be much help on your question. I suggest you ask in the Moto g7 power discussion group on telegram. I'm sure someone there can let you know if the cricket variant is unlockable or not. Good luck
Click to expand...
Click to collapse
Thanks for the quick response! I don't use Telegram, but I guess I better get signed up. I wish there was a repository of, an HCL of sorts, where people can refer to before buying phones to avoid these issues.
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
TWRP doesn't work with A12.
ffejy462 said:
TWRP doesn't work with A12.
Click to expand...
Click to collapse
This, decryption isn't supported AT ALL by any recovery running on A12. I've seen modified recoveries for A12 for other devices and it seems they try to disable forced encryption which is a BAD idea!
If you want to decrypt, would recommend either staying with OOS 11 or a custom ROM on A11. Bear in mind there have been numerous reported issues with TWRP hence why most custom ROMs for the OP9P choose to stick to LineageOS recovery.
cat139lyleb said:
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
Click to expand...
Click to collapse
It's because you flashed an incompatible TWRP (not compatible with Android 12 ROMS)
Okay, maybe TWRP is already aware of this problem with 12 ROMS, plus I already did tried a few times with OEM unlock in 11, but no luck. So that's why OEM unlocked in 12... very weird...
The bootloader won't unlock until OEM unlocks in any android versions. So first, that's why.
I have a question about that. Do you think it's why -> SECURE BOOT - YES?
Then how do we make it say NO?
Because we are aware that it is FULLY unlocked as DEVICE STATE - UNLOCKED, correct?