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
Yesterday I took some time to attempt to upgrade my OnePlus to Android Pie after finding out earlier that it's not as simple as just installing an update when your boot loader is unlocked. After a bit of searching I found this guide which I followed to upgrade OxygenOS to version 9.0.5. After some initial problems (I didn't pay enough attention and TWRP was set to auto-reboot which complicated matters a little) I managed to finish the upgrade and the device booted.
After confirming everything worked well I figured I should flash Magisk back onto the device so that I would have root access again. I flashed Magisk 19.3 and tried to boot the phone but it got stuck on the spinning OnePlus logo during boot. Left it running for over an hour, nothing happened so eventually I decided to flash the OTA update and the BL/KM patch again, which made my phone boot again but without Magisk, obviously.
After that I tried flashing Magisk 19.2 and Canary (19.4), both with the same results: a spinning logo, nothing more.
I'm not sure what else I can try. In a particular braindead moment I thought I should just try to take a look at Magisk's log file but of course that's not accessible without root access. I've got a feeling that the patch to the bootloader is causing issues with Magisk's firmware patch but I'm not familiar enough with this kind of problem to figure out what is going on exactly.
Does anyone recognize this problem or can one of you tell me what I could try to get Magisk running again?
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot
dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot
Click to expand...
Click to collapse
Thanks, I'll give it a go later tonight!
dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Click to expand...
Click to collapse
I tried it just now. Sadly I get the same end result. Thanks anyway though.
I have an ADB log of the crash that happens that causes the phone not to boot, maybe that's familiar to someone around here? I uploaded it here.
Hello can I ask a question why do you need root
OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6. I flashed Magisk with no issue. Here are the steps I took:
Starting with unlocked BL
Boot into the newest official version of TWRP via fastboot.
Flash OOS 9.0.5 and boot into it, completing device setup.
Reboot into OnePlus recovery, then from within, reboot into fastboot
Flash TWRP to recovery in fastboot, then shut down device (do not attempt to fastboot reboot recovery, it will boot into OOS and overwrite TWRP)
Boot device, use volume key to interrupt startup, boot into recovery (TWRP)
Follow installation instructions from Havoc thread, do not wipe cache/dalvik after flashing, do not boot before flashing all zips (I flashed ROM -> gapps -> Magisk in that order)
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.
kallum7 said:
Hello can I ask a question why do you need root
Click to expand...
Click to collapse
I work on an app that uses location data and it's pretty convenient to be able to test it on a real device but with a joystick instead of real location data. To make matters more complicated it's my personal phone and I use that to play Pokémon Go too. Without cheating I might add, the root is not for PG but because I do want to be able to play it on the same phone that I use to test my app I need Magisk to hide the fact that it's rooted or the game won't start.
LunarisDream said:
OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6.
Click to expand...
Click to collapse
Thanks for the suggestion but I'd rather keep using OOS on this phone as long as I don't have a new phone for daily use. I don't really want to modify this thing too much without having a replacement ready in the likely case that I screw something up.
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.
Click to expand...
Click to collapse
I tried both flashing the OTA, the modded firmware and Magisk in one go and separately after confirming that the OTA/FW were working. Sadly both methods resulted in the same problem.
If anyone's wondering I did a clean flash and factory reset, then installed Magisk again after that. Everything's working again now. Thanks for trying to help!
Hi,
I've previously managed to install twrp and boot into it. however, forgot to install dmverify.
since then the SG prenormal flag shows on download screen.
i've reinstalled stock rom and everything works fine, except the bootloader warning appears. (can remove this by turning bootloader unlock off).
tried reinstalling twrp again, but this time keep getting error message that unofficial binaries cannot be installed, due to the SG prenormal flag.
How can this be reset so I can install twrp to finally root device (and later remove all bootloader warnings)?
please help.
it seems I need to unlock knoxguard (used to be unlock rmm)
so that KG prenormal stops blocking twrp installation.
Seems to be a paid way to do this via chimera tool.
https://chimeratool.com/en/docs/sam...onitoring-and-management-rmm-unlock-functions
If they can do it paid, then its technically possible to unlock knoxguard.
Does anybody have another way to all TWRP installation after KG prenormal is set in download mode?
thanks
lawmanukdc said:
it seems I need to unlock knoxguard (used to be unlock rmm)
so that KG prenormal stops blocking twrp installation.
Seems to be a paid way to do this via chimera tool.
https://chimeratool.com/en/docs/sam...onitoring-and-management-rmm-unlock-functions
If they can do it paid, then its technically possible to unlock knoxguard.
Does anybody have another way to all TWRP installation after KG prenormal is set in download mode?
thanks
Click to expand...
Click to collapse
Reflash stock,just skip all setup go to develop options and enable usb debug.And try again.If you don't succeed first time try again.
muhamet said:
Reflash stock,just skip all setup go to develop options and enable usb debug.And try again.If you don't succeed first time try again.
Click to expand...
Click to collapse
Hi,
1. I enabled usb debug, then went back into download mode.
2. It still shows KG STATE prenormal.
3. tried to install twrp again and same problem = refused to install unknown binary.
4. reinstalled stock (with home_csc)
5. went back into download mode and still showed KG STATE PRENORMAL.
6. Tried to install twrp again and same problem = refused to install unknown binary.
please confirm:
A. Is KG STATE PRENORMAL supposed to change after usb debug?
B. when you say 'try again', what are you referring to?
1) try installing twrp again - tried this already as above
2) try installing stock again? (with/without home crc?) - tried this already as above
still stuck but sounds like you may have the answer?
thanks
lawmanukdc said:
Hi,
1. I enabled usb debug, then went back into download mode.
2. It still shows KG STATE prenormal.
3. tried to install twrp again and same problem = refused to install unknown binary.
4. reinstalled stock (with home_csc)
5. went back into download mode and still showed KG STATE PRENORMAL.
6. Tried to install twrp again and same problem = refused to install unknown binary.
please confirm:
A. Is KG STATE PRENORMAL supposed to change after usb debug?
B. when you say 'try again', what are you referring to?
1) try installing twrp again - tried this already as above
2) try installing stock again? (with/without home crc?) - tried this already as above
still stuck but sounds like you may have the answer?
thanks
Click to expand...
Click to collapse
What model you are using??FN? Don't flash twrp magisk patched.Use just twrp. @samsunggalaxya50
Use telegram chanel i will help from there
muhamet said:
What model you are using??FN? Don't flash twrp magisk patched.Use just twrp. @samsunggalaxya50
Use telegram chanel i will help from there
Click to expand...
Click to collapse
Surprised so few responses. Had expected KG tripping to be a common problem.
I'm using 505FN.
Installed TWRP once in beginning and it worked but forgot to do the dm-verify thing.
Since then tried others including the magisk patched one, but KG PRENORMAL stops any unofficial binaries.
Been trying this TWRP from xda but still no joy.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
totally stuck at this point on how to progress, and hope there is a way to kill KG PRENORMAL.
Installed Telegram, but no option to add channel - only to create one. Searched in https://tlgrm.eu/channels for channel samsunggalaxya50 but couldn't find it. Please advise how to install channel?
Thanks
ok, i follwed below guide and that seems to have fixed the KG prenormal issue turning it into KG checking...
https://www.youtube.com/watch?v=zqbu7jCmeMY
I then tried installing TWRP.
1. this version flashed ok ,but wouldn't go into recovery - just kept looping.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
2. I then installed another version I had got without magisk in it v. 3.3.1
this flashed ok and I rebooted into TWRP recovery.
Only problem is theres no way to install the DMverify file.
1. Not sure to install DMVerify
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
or
2. Multi-disabler?
https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
It doesn't matter anyway, as TWRP sideload isn't working properly... keeps saying starting.
On my windows or linux machine, adb start-server, adb devices doesn't show anything.
So I can't install the above fixes and worried it will go crazy after I turn phone off.
How can I get anything onto the a50 now without sideload on twrp working?
Maybe you know of a twrp version that works fine with sideload?
lawmanukdc said:
Surprised so few responses. Had expected KG tripping to be a common problem.
I'm using 505FN.
Installed TWRP once in beginning and it worked but forgot to do the dm-verify thing.
Since then tried others including the magisk patched one, but KG PRENORMAL stops any unofficial binaries.
Been trying this TWRP from xda but still no joy.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
totally stuck at this point on how to progress, and hope there is a way to kill KG PRENORMAL.
Installed Telegram, but no option to add channel - only to create one. Searched in https://tlgrm.eu/channels for channel samsunggalaxya50 but couldn't find it. Please advise how to install channel?
Thanks
Click to expand...
Click to collapse
kg is not a common problem if u followed the steps correctly from the start
lawmanukdc said:
ok, i follwed below guide and that seems to have fixed the KG prenormal issue turning it into KG checking...
I then tried installing TWRP.
1. this version flashed ok ,but wouldn't go into recovery - just kept looping.
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
2. I then installed another version I had got without magisk in it v. 3.3.1
this flashed ok and I rebooted into TWRP recovery.
Only problem is theres no way to install the DMverify file.
1. Not sure to install DMVerify
https://forum.xda-developers.com/galaxy-a50/how-to/how-to-installing-twrp-a50-100-t3966636
or
2. Multi-disabler?
https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
It doesn't matter anyway, as TWRP sideload isn't working properly... keeps saying starting.
On my windows or linux machine, adb start-server, adb devices doesn't show anything.
So I can't install the above fixes and worried it will go crazy after I turn phone off.
How can I get anything onto the a50 now without sideload on twrp working?
Maybe you know of a twrp version that works fine with sideload?
Click to expand...
Click to collapse
you just got all sorts of problems lol.. y dont u follow the instructions exactly in the proper thread? when u go off n start missin stuff or usin other files etc. then ur bound to have problems if u dont know what ur doing.. just saying
Which thread works correctly?
I installed multi disabler and then magisk.
Rebooted twrp into official ROM.
Multi disabler didn't work.
On reboot, phone had KG prenormal again and refused to boot due to twrp installation.
What to do?
1. Is there a better disabler that works
2. Would installing custom ROM help?
lawmanukdc said:
I installed multi disabler and then magisk.
Rebooted twrp into official ROM.
Multi disabler didn't work.
On reboot, phone had KG prenormal again and refused to boot due to twrp installation.
What to do?
1. Is there a better disabler that works
2. Would installing custom ROM help?
Click to expand...
Click to collapse
technically you dont even need it lol.. my s10 5g is rooted simply using a patched tar
Hello could someone help me?
I'm trying to root my Moto G7 Play (XT1952-2) using the ROM CHANNEL_RETAIL_10_QPYS30.52-22-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. The problem is that in the latest version of Magisk Mananger (v23) there are no advanced configuration options, as well as the possibility to enable the recovery option.
I tried to flash the boot.img file and run the command "fastboot flash boot magisk_patched.img", but I was unsuccessful.
Note that when I try to flash Magisk-v23.zip on TWRP, root is successfully installed, BUT Wi-Fi crashes.
The same thing happens to me, my screen stays in a combination of letters and numbers and it never goes from there, I also do not have a twrp installed, would you help me to know how to install it?
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.