Related
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
Hi - I have a OP3T that won't let me get into TWRP.
I have an encrypted phone (I'm OK with losing all my data ... like I have a choice now )
I was trying to upgrade to a LOS 15.1 ROM, and I saw an error during the flashing process.
Now, I can't get into TWRP. It asks me for my pattern to unlock, but TWRP doesn't work at all - TWRP doesn't respond when I'm trying to enter my pattern or press any buttons on the OP3T.
I expect that I need to do something through fastboot to get my OP3T functional again, but I figured I should ask the experts before I make a "misteak" that really bricks my OP3T permanently.
What should I do at this point to safely get my OP3T functional again?
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I have a OP3T that won't let me get into TWRP.
I have an encrypted phone (I'm OK with losing all my data ... like I have a choice now )
I was trying to upgrade to a LOS 15.1 ROM, and I saw an error during the flashing process.
Now, I can't get into TWRP. It asks me for my pattern to unlock, but TWRP doesn't work at all - TWRP doesn't respond when I'm trying to enter my pattern or press any buttons on the OP3T.
I expect that I need to do something through fastboot to get my OP3T functional again, but I figured I should ask the experts before I make a "misteak" that really bricks my OP3T permanently.
What should I do at this point to safely get my OP3T functional again?
Thanks,
¿GJ?
Click to expand...
Click to collapse
It's not bricked -, -.
Which twrp are you using currently. Your gonna need to use the one by Bluspark.
I have an official TWRP loaded (Not sure of the version, but probably v3.2.1.0).
I'm not sure if Blu Spark's TWRP will get me any further. I did a fastboot boot twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img, and I saw the same problem: The phone was totally unresponsive to me entering my unlock pattern. I couldn't even "Swipe to Unlock" TWRP when the screen lock came on. My swipe didn't do anything. It's like my OP3T currently isn't recognizing the touch screen for some reason.
What do you recommend that I do after I load the Bluspark TWRP?
If Bluspark TWRP isn't viable anymore based on what I am seeing, I expect that I've already lost all my data. What can I do to wipe my partitions and do a clean install of LOS 15.1 or OOS 5.x?
¿GJ?
¿GotJazz? said:
I have an official TWRP loaded (Not sure of the version, but probably v3.2.1.0).
I'm not sure if Blu Spark's TWRP will get me any further. I did a fastboot boot twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img, and I saw the same problem: The phone was totally unresponsive to me entering my unlock pattern. I couldn't even "Swipe to Unlock" TWRP when the screen lock came on. My swipe didn't do anything. It's like my OP3T currently isn't recognizing the touch screen for some reason.
What do you recommend that I do after I load the Bluspark TWRP?
¿GJ?
Click to expand...
Click to collapse
We recommend the one by Bluspark. I've avoided alot of decryption issues and such and many other recommend it because of that reason. Something seems to be off with your phone (software sided). I do recommend using the Unbrick Guide (make sure you use one for Oneplus 3T). Then start over again with Bluspark twrp.
When upgrading roms to major versions do check which firmware is required and perhaps wipe System and reflash the rom + opengapps to avoid issues. Good luck let me now!
Puddi_Puddin said:
We recommend the one by Bluspark. I've avoided alot of decryption issues and such and many other recommend it because of that reason. Something seems to be off with your phone (software sided). I do recommend using the Unbrick Guide (make sure you use one for Oneplus 3T). Then start over again with Bluspark twrp.
When upgrading roms to major versions do check which firmware is required and perhaps wipe System and reflash the rom + opengapps to avoid issues. Good luck let me now!
Click to expand...
Click to collapse
Thanks, @Puddi_Puddin - Do I need to go through the Mega Unbrick if I already have fastboot working on my OP3T? I think I just need to erase my O/S partitions at this point via fastboot and then install something like a OOS 5 or LOS 15 full image.
¿GotJazz? said:
Thanks, @Puddi_Puddin - Do I need to go through the Mega Unbrick if I already have fastboot working on my OP3T? I think I just need to erase my O/S partitions at this point via fastboot and then install something like a OOS 5 or LOS 15 full image.
Click to expand...
Click to collapse
You could try indeed. Don't erase the partitions but format them.
So that would be:
Fastboot format <partition>
Well ... fastboot format userdata did get rid of the unlock pattern issue. I don't see a request for an unlock pattern anymore in TWRP.
The bad news is that my touchscreen still doesn't work. I also tried a fastboot flash recovery twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img, and my touchscreen still doesn't work.
So, I did a fastboot boot recovery_op3t.img to boot from the button-controlled OP Recovery Mode instead of a touch screen recovery. Then, I did an adb sideload of the latest OOS 5.0.3 zip.
I booted up OOS 5.0.3, and my touch screen is working again.
Thanks for the help!
Hey people since long time i am loving your base helped me alot for many years with my different projects but now i am really stuck i cant progress any futher, i am quite frustrated.
I flashed the twrp different versions i think all official ones plus one i found somewhere here but it all the time has the same problem of a non working touchscreen. I know that with this kind of adapter USBC to USB and a mouse it should work but i dont have one and I live quite remote.... so it would be nice if it works without.
So what i tried is to boot into recovery and open a but the "set_active b" that was suggested also but i am not sure if i found it with the chiron but rather with the a1 one or something with same problem touchscreen not working. adb shell twrp wipe cache dalvik system data and then adb sideload but when i am trying to flash the lineage it finishes with the success message i found somewhere in a thread here but its way to fast it needs like 0.2 seconds and of course it isnt working. also i tried to fastboot flash the lineage recovery but everytime i am ending up in twrp in the end so it doesnt get replaced also if fastboot reboot recovery afterwards or fastboot boot lineagerecovery. I just dont know anymore also i tried to update to new adb and fastboot but didnt work. Also i tried fastboot -w before doing everything it cleaned the encryption password so twrp looked different afterwards but after repeating the steps still the same result no lineage
I was really excited about this phone but now it got really the hardest phone to flash of all the five I ever tried
Help would be highly appreciated.
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.
Hi i have a pixel xl. I had it rooted via magisk and I had LOS on it. But then i decided to go back to stock. I did that but i forgot that I had to uninstall magisk so i locked the bootloader and wound up with a stock rom rooted. It worked for a while them it started crashing. Im not too sure what happened or what i did it was a year ago. So anyway when i turn it on it says the bootloader is corrupt which it did before. Android flash tool did not work wok. I can boot into recovery but i dont know what to mdo no.
can someone please help me.
Also I am able to use fastboot I just tried from my pc. I just dont know what to do to fix this. I know I have to somehow get twrp back on the phone and flash the magisk uninstall.zip. But this was so long ago i dont even remember which version of magisk I was using or which magisk uninstall file to flash.
i was able to get a flash-all .bat to work but im still in the same position. Basically the phone gives me the message your device cant be checked for corruption then goes on to the google screen and eventually the screen goes blank and it starts over so it is bootlooping i guess.
Can anyone tell me how i can flash twrp.img on the phone with fastboot? Right now the current active slot is b. I tried typing fastboot flash b then the twrp.img file name and it gives me an error. Am I supposed to be flashing to a certain partition?
Please someone help I am not very good with the command line. I dont know all the lingo