Database Develop

[Q] HTC One Goole Edition Stuck in Bootloop after 4.4 update. Help please!

Hello-
Here is the fast version:
HTC One GPE with stock JB rom and clockwork mod recovery.
Last night I flashed the recovery to a stock version I found on the boards here. This morning the most recent JB update was ready for installation on the phone. A while after that KitKat was ready and I installed. As soon as I did, the phone entered a boot loop and will not stay on. I've cleared the cache and factory reset with no luck. A kind individual on another thread attempted to help resolve the issue but no such luck.
I tried reinstalling 4.4 (having to relock my bootloader was the only way I could successfully attempt reloading, but it did not work. S-off is ON.
Now, I cannot enter a custom recovery (nor a recovery of any kind at this moment). Any time I select recovery it just reboots the phone.
Here are previous errors I received while attempting fastboot flash:
bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
FAILED (remote: 24 parsing android-info fail)
Here is my fastboot getvar all:
c:\And>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I appreciate any help you may be able to offer. I've never had this much trouble with a phone before (somewhat of a novice, but this is beyond me).
Thank you!!!

unlock the bootloader again and install a custom recovery
then install the zip from here using adb sideload: http://forum.xda-developers.com/showthread.php?t=2341395

Right, so your bootloader is locked or unlocked? If locked, are you able to unlock it?

SaHiLzZ said:
Right, so your bootloader is locked or unlocked? If locked, are you able to unlock it?
Click to expand...
Click to collapse
I use the command "fastboot oem lock" and "fastboot oem unlock" to lock and unlock the device (since it's google play edition), unless that is for unlocking something else besides the bootloader.
I cannot open the recovery so I don't know what is on there. I've loaded TWRP with fastboot but every time I select recovery from the menu on the phone it reboots the phone.
Here is what I get when I search for the phone. I assume the adb is not seeing it since I have not set up the phone for that option?
c:\And>adb devices
List of devices attached
c:\And>fastboot devices
HT36JW912382 fastboot

Can you download either CWM or TWRP and try the following from bootloader:
fastboot boot nameofrecovery.img
For example: If you get http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
then fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img in fastboot mode
Does the phone reboot into recovery now?

c:\And>fastboot boot openrecovery-twrp-2.6.3.3-m7.img
downloading 'boot.img'...
OKAY [ 1.202s]
booting...
OKAY [ 0.001s]
This just froze the phone.
It will NOT boot into recovery. Just turns on and shows "Google"
QUOTE=SaHiLzZ;47949555]Can you download either CWM or TWRP and try the following from bootloader:
fastboot boot nameofrecovery.img
For example: If you get http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
then fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img in fastboot mode
Does the phone reboot into recovery now?[/QUOTE]

Try the recovery linked and twrp 2.6.3.0?

fastboot erase cache

damon7620 said:
fastboot erase cache
Click to expand...
Click to collapse
SaHiLzZ said:
Try the recovery linked and twrp 2.6.3.0?
Click to expand...
Click to collapse
I have cleared the cache before and after loading the custom recovery. and I loaded the CWR recovery. Still will not load into recovery. Just turns off and boots to Google.

i was able to successfully re-load the stock recovery. Any suggestions from this point?

How? What recovery did you use?
Go to bootloader and a do a factory reset from bootloader, it should boot into stock recovery and wipe , (should not just get kicked out right away)
What's the result after doing this.?

SaHiLzZ said:
How? What recovery did you use?
Go to bootloader and a do a factory reset from bootloader, it should boot into stock recovery and wipe , (should not just get kicked out right away)
What's the result after doing this.?
Click to expand...
Click to collapse
I used one I found somewhere in this thread. http://forum.xda-developers.com/showthread.php?t=2358781&highlight=recovery
I cannot recall the exact one. It is the same one I installed last night before this morning's update.
I did the wipe and loaded into bootloader. Rebooted the phone and is now in a boot loop.

Hi @The_Doctor_Who here's what I would recommend:
- fastboot oem unlock (if not already in the unlocked state)
- download the latest official ClockworkMod touch recovery for m7ul directly from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7ul.img
- fastboot boot recovery-clockwork-touch-6.0.4.3-m7ul.img
Note the use of 'boot' instead of 'flash' for the last command... let's narrow this down and see if you can just boot a well-known/official recovery for this model without flashing anything. Sorry if these steps seem repetitive at this point, but it's a little hard to know what all has been done.

goldenratio said:
Hi @The_Doctor_Who here's what I would recommend:
- fastboot oem unlock (if not already in the unlocked state)
- download the latest official ClockworkMod touch recovery for m7ul directly from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7ul.img
- fastboot boot recovery-clockwork-touch-6.0.4.3-m7ul.img
Note the use of 'boot' instead of 'flash' for the last command... let's narrow this down and see if you can just boot a well-known/official recovery for this model without flashing anything. Sorry if these steps seem repetitive at this point, but it's a little hard to know what all has been done.
Click to expand...
Click to collapse
Hey! Thank!
I understand re: not knowing. I've tried using that recovery and cannot get into it. I also tried the fastboot boot and it froze the phone (someone motioned HTC removed the ability to use 'boot' with the hboot 1.54). I tried leting the phone sit in the frozen state but it would not do anything.

The_Doctor_Who said:
I've tried using that recovery and cannot get into it. I also tried the fastboot boot and it froze the phone.
Click to expand...
Click to collapse
I see. Do I understand the the sequence of events correctly:
- you flashed a stock JB ROM
- then flashed the stock recovery (which file exactly? was it for m7ul?)
- the phone booted okay at this point and prompted you for 2 over-the-air system updates:
= an update for JB
= an update to KitKat
- things broke at this point?
The_Doctor_Who said:
someone motioned HTC removed the ability to use 'boot' with the hboot 1.54.
Click to expand...
Click to collapse
Do you have a link for that thread handy? I wonder if it's trivial or not to downgrade the radio (HBOOT)... I haven't tried before.

goldenratio said:
I see. Do I understand the the sequence of events correctly:
- you flashed a stock JB ROM
- then flashed the stock recovery (which file exactly? was it for m7ul?)
I will have to find the file. I believe it was. It was indicated that the stock recovery was from the GPE One.
- the phone booted okay at this point and prompted you for 2 over-the-air system updates:
= an update for JB
= an update to KitKat
- things broke at this point?
The update for JB was fine. I was checking twitter, facebook, etc. Then the KitKat update came in. I selected download and install and that is where the problem started.
Do you have a link for that thread handy? I wonder if it's trivial or not to downgrade the radio (HBOOT)... I haven't tried before.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=47972147&postcount=16
From what I have seen downgrading is not an option, but I could be wrong.

@The_Doctor_Who thanks for the link. It doesn't specifically say you can't use 'fastboot boot' on the GPE version of HBOOT. I'm pretty sure you can (assuming things are working otherwise). At least, I had a version of the 1.54 HBOOT on m7ul which didn't seem to have this restriction... I don't know the exact version number unfortunately.
That aside, it does seem that the recovery partition may be corrupted or in a bad state somehow. I'm going to reply on the other thread since those guys seem to have some good info and have been super helpful. I have a couple of ideas I'll post there.

At this point what I would recommend is to use the factory images for it and attempt to restore it to full stock before trying to go any further.

[SOLVED] Please Help! Android bricked and no recovery boot either!

Hi folks,
i Have a HTC ONE with this configurations:
ROM: ANDROID REVOLUTION HD
HBOOT: 1.55 S-ON
Recovery: TWRP
When i start my device and android is starting, i get an message about System process isn't running. Yes, my android is completely dead.
So the logic thing to do is start in recovery TWRP and restore the last backup, right? Well... When I boot with hboot and press to enter on recovery mode...
I get the HTC logo and the "entering recovery" screen forever. Recovery TWRP is completely dead too.
Using adb i can start a shell, view all my files on the device, perform any task.
The fastboot.exe boot recovery.img freezes the device and flash recovery doesnt work too.
Flash the rom doent work too.
Anyone knows what can I do?
thanks!
UPDATE: The solution on the last post was: RUU.

dogasantos said:
Hi folks,
i Have a HTC ONE with this configurations:
ROM: ANDROID REVOLUTION HD
HBOOT: 1.55 S-ON
Recovery: TWRP
When i start my device and android is starting, i get an message about System process isn't running. Yes, my android is completely dead.
So the logic thing to do is start in recovery TWRP and restore the last backup, right? Well... When I boot with hboot and press to enter on recovery mode...
I get the HTC logo and the "entering recovery" screen forever. Recovery TWRP is completely dead too.
Using adb i can start a shell, view all my files on the device, perform any task.
The fastboot.exe boot recovery.img freezes the device and flash recovery doesnt work too.
Flash the rom doent work too.
Anyone knows what can I do?
thanks!
Click to expand...
Click to collapse
Code:
fastboot boot recovery
only works on hboot 1.44
please answer all questions below:
post the output of fastboot getvar all excluding imei and serialno
what version of twrp are you using?
what version of arhd?
what you did before the phone bricked?
if you fastboot erase cache then fastboot reboot-bootloader, are you able to boot in recovery mode?

alray said:
Code:
fastboot boot recovery
only works on hboot 1.44
please answer all questions below:
post the output of fastboot getvar all excluding imei and serialno
what version of twrp are you using?
what version of arhd?
what you did before the phone bricked?
if you fastboot erase cache then fastboot reboot-bootloader, are you able to boot in recovery mode?
Click to expand...
Click to collapse
Hi ! thanks for your quick reply!
Here is the informations:
C:\mini-sdk>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXX
(bootloader) imei: XXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Click to expand...
Click to collapse
[*]what version of twrp are you using?
A: A recovery.log from last backup (2013) shows TWRP 2.6.3.3.
[*]what version of arhd?
A: ARHD 40.3 (android 4.4 + sense 5.5 + htc sdk api 5.65)
[*]what you did before the phone bricked?
A: A TWRP reset to default
[*]if you fastboot erase cache then fastboot reboot-bootloader, are you able to boot in recovery mode?
A: reboot-bootloader get me to the fastboot and when i hit the recovery i get stuck on "entering recovery" screen forever.
As I mentioned above, i have a TWRP backup with this files:
boot.emmc.win
data.ext4.win
recovery.emmc
system.ext4.win000
system.ext4.win001
Click to expand...
Click to collapse
I see this as 2 problems, (1) android doesnt boot anymore due to system process failure and (2) recovery partition/firmware is corrupted somehow.
I really dont know what to do, I spent the last 12 hours looking for directions here and over internet but nothing works. What you think i can do?
Thanks for your help @alray.

dogasantos said:
[*]if you fastboot erase cache then fastboot reboot-bootloader, are you able to boot in recovery mode?
A: reboot-bootloader get me to the fastboot and when i hit the recovery i get stuck on "entering recovery" screen forever.
As I mentioned above, i have a TWRP backup with this files:
Click to expand...
Click to collapse
just want to be sure:
in bootloader mode (fastboot) you did the following:
Code:
fastboot erase cache
fastboot reboot-bootloader
then you tried to boot the recovery and it still doesnt work?
try to download the recovery again from here
make sure md5 match: 72067aefb69541d40e8420d7aa46408d
Code:
then
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and try to boot in recovery again
post a screenshot if you get any error

alray said:
just want to be sure:
in bootloader mode (fastboot) you did the following:
Code:
fastboot erase cache
fastboot reboot-bootloader
then you tried to boot the recovery and it still doesnt work?
Click to expand...
Click to collapse
A: yes, this is right. The TWRP doesn't show up
alray said:
try to download the recovery again from here
make sure md5 match: 72067aefb69541d40e8420d7aa46408d
Code:
then
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and try to boot in recovery again
post a screenshot if you get any error
Click to expand...
Click to collapse
Hi @alray !
here is the sequence:
C:\mini-sdk>fastboot.exe flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.076s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.794s
C:\mini-sdk>fastboot.exe erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\mini-sdk>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\mini-sdk>
Click to expand...
Click to collapse
But.. when I select to enter RECOVERY on bootloader i got the same freezing screen
Thanks for your reply on this thread!! I really appreciated all your help!!

dogasantos said:
A: yes, this is right. The TWRP doesn't show up
Hi @alray !
let me post the error when flash this recovery version (the md5 hash match):
Thanks for your reply on this thread!! I really appreciated all your help!!
Click to expand...
Click to collapse
:laugh:
Your bootloader is locked or re-locked. you must have unlocked bootloader

alray said:
:laugh:
Your bootloader is locked or re-locked. you must have unlocked bootloader
Click to expand...
Click to collapse
LOL, yes, sorry.
i updated the previous post with the correct information (re-unlock with htc unlock)!
I try this step (relock) between your messages, but nothing new.
All sequence is OK, but i got the same freezing screen :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

dogasantos said:
LOL, yes, sorry.
i updated the previous post with the correct information (re-unlock with htc unlock)!
I try this step (relock) between your messages, but nothing new.
All sequence is OK, but i got the same freezing screen :crying:
Click to expand...
Click to collapse
strange, maybe you could try with CWM recovery.
flash cwm recovery the same way you just did for twrp and see if it boot. don't forget to "fastboot erase cache" and "fastboot reboot-bootloader" before attempting to boot the recovery.

alray said:
strange, maybe you could try with CWM recovery.
flash cwm recovery the same way you just did for twrp and see if it boot. don't forget to "fastboot erase cache" and "fastboot reboot-bootloader" before attempting to boot the recovery.
Click to expand...
Click to collapse
the same happens with CWM recovery img :crying:
thanks anyway!

dogasantos said:
the same happens with CWM recovery img :crying:
thanks anyway!
Click to expand...
Click to collapse
try this recovery just in case: http://www.androidfilehost.com/?fid=23329332407590873

alray said:
try this recovery just in case: http://www.androidfilehost.com/?fid=23329332407590873
Click to expand...
Click to collapse
the same happens.
there is a way to format the recovery (raw) partition?
Maybe this could fix some corrupted data (if flashing new recovery doesn't do that)
What about trying RRU? I found this link
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
But the mirror is TOO SLOW down here, will take hours to download this file.

dogasantos said:
the same happens.
there is a way to format the recovery (raw) partition?
Maybe this could fix some corrupted data (if flashing new recovery doesn't do that)
What about trying RRU? I found this link
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
But the mirror is TOO SLOW down here, will take hours to download this file.
Click to expand...
Click to collapse
yes in theroy the ruu should do the job, but many users reported that ruu isn't working properly, anyway give it a try. htc1guru.com is sometime slow because too much traffic. Try to restart the download, sometime you can get a good/fast connection. make sure md5 match 9ad4111ce86981e3dffcce6d9ee80551
you can also download the ruu from here: http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe

SOLVED
alray said:
yes in theroy the ruu should do the job, but many users reported that ruu isn't working properly, anyway give it a try. htc1guru.com is sometime slow because too much traffic. Try to restart the download, sometime you can get a good/fast connection. make sure md5 match 9ad4111ce86981e3dffcce6d9ee80551
you can also download the ruu from here: http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
Hi @alray !
yes, RUU do the trick ! Bring my phone back to life! haha
thanks for all your help, I really appreciated !!!
I performed the steps described here (for the users with similar problem in the future): http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
How i can tag this thread as SOLVED ?
cya!

dogasantos said:
Hi @alray !
yes, RUU do the trick ! Bring my phone back to life! haha
thanks for all your help, I really appreciated !!!
I performed the steps described here (for the users with similar problem in the future): http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
How i can tag this thread as SOLVED ?
cya!
Click to expand...
Click to collapse
glad it finally worked :highfive:
you can tag your thread with [solved] by editing your first post in this thread.
click "edit / delete" then click on "go advanced" and edit you thread title with [solved]

Twrp instalation 2.7+

I can't install any recovery TWRP from version 2.7.x.x+, etc, I can install, but when I try run recovery I see only Entering recovery, black screen for few seconds then again entering recovery and htc logo. When I install twrp 2.6.3.3 all works perfectly, I don't know what is wrong.. I trying fastboot metod and comend fastboot erase cache, didn't help. What Can I do now? I Try use flashify and more more more, I have a root, unlock bootloader, s-on. When I try instalation cwm or cwm touch the newest is the same problem, but I need this twrp, because I wanna try new rom port from Oneplus One.
THANK U VERY MUCH MAJMOZ AND ALRAY! If u will know how to install twrp 2.7.0.0+, message me

schizyk12 said:
I can't install any recovery TWRP from version 2.7.x.x+, etc, I can install, but when I try run recovery I see only Entering recovery, black screen for few seconds then again entering recovery and htc logo. When I install twrp 2.6.3.3 all works perfectly, I don't know what is wrong.. I trying fastboot metod and comend fastboot erase cache, didn't help. What Can I do now? I Try use flashify and more more more, I have a root, unlock bootloader, s-on. When I try instalation cwm or cwm touch the newest is the same problem, but I need this twrp, because I wanna try new rom port from Oneplus One.
Click to expand...
Click to collapse
Don't know why they are failing but 2.7.0.0 and 2.7.1.0 have caused problems before. And some people say that 2.7.1.1 can cause issues, I didn't have issue with it but not all phones are created equal. You can try 2.7.1.2, I have used it for the past month or so. I read the OP on the port and they stated the lastest TWRP but you could try the 2.6.3.3 if you cannot get the others to work. I am also assuming that you have a GSM phone not Sprint or Verizon.

majmoz said:
Don't know why they are failing but 2.7.0.0 and 2.7.1.0 have caused problems before. And some people say that 2.7.1.1 can cause issues, I didn't have issue with it but not all phones are created equal. You can try 2.7.1.2, I have used it for the past month or so. I read the OP on the port and they stated the lastest TWRP but you could try the 2.6.3.3 if you cannot get the others to work. I am also assuming that you have a GSM phone not Sprint or Verizon.
Click to expand...
Click to collapse
I try everyone, 2.7.1.3 beta also, everyone.. ;< What Can I do? 2.7.0.0+ and bootlop on htc logo when I try run recovery with inscription entering recovery.. I try flashify, fastboot and many aplications from play store to flash recovery. :< Can I flashed this rom, port from oneplus one other metod?

schizyk12 said:
I try everyone, 2.7.1.3 beta also, everyone.. ;< What Can I do? 2.7.0.0+ and bootlop on htc logo when I try run recovery with inscription entering recovery.. I try flashify, fastboot and many aplications from play store to flash recovery. :< Can I flashed this rom, port from oneplus one other metod?
Click to expand...
Click to collapse
Post a fastboot getvar all except the imei and serialno. What computer are you using Win 7 or Win 8?

majmoz said:
Post a fastboot getvar all except the imei and serialno. What computer are you using Win 7 or Win 8?
Click to expand...
Click to collapse
I use old computer with windows xp, because I post in the official twrp thread, I'm im collage and I use only tablet and phone.

schizyk12 said:
I use old computer with windows xp, because I post in the official twrp thread, I'm im collage and I use only tablet and phone.
Click to expand...
Click to collapse
Microsoft Windows XP [Wersja 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Adam>cd C:\fastboot
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
C:\fastboot>

schizyk12 said:
I use old computer with windows xp, because I post in the official twrp thread, I'm im collage and I use only tablet and phone.
Click to expand...
Click to collapse
Lets check the basics:
** Double check the MD5 of the recovery to see if it downloaded properly
** Place the recovery.img in the adb/fastboot folder
** Fast boot is disabled in Settings >> Power >> Fast boot
** Boot into Bootloader/FASTBOOT USB
** Type: fastboot devices
You should see your device listed.
** Type: fastboot flash recovery <file-name>.img Replace file name with the actual recovery name.
** Type: fastboot erase cache
** Type: fastboot reboot-bootloader
Now check to see if it worked!

majmoz said:
Lets check the basics:
** Double check the MD5 of the recovery to see if it downloaded properly
** Place the recovery.img in the adb/fastboot folder
** Fast boot is disabled in Settings >> Power >> Fast boot
** Boot into Bootloader/FASTBOOT USB
** Type: fastboot devices
You should see your device listed.
** Type: fastboot flash recovery <file-name>.img Replace file name with the actual recovery name.
** Type: fastboot erase cache
** Type: fastboot reboot-bootloader
Now check to see if it worked!
Click to expand...
Click to collapse
All installation complete final 100%. But twrp doesn't work ;<

schizyk12 said:
All installation complete final 100%. But twrp doesn't work ;<
Click to expand...
Click to collapse
Let try flashing the stock firmware for your phone.
** Find the unlock code you got from HTCDev when you unlocked your bootloader - "Unlock_code.bin" and place in your fastboot folder
** Download stock_firmware 5.11.401.10.zip and rename "firmware.zip" then place in your fastboot folder. Check the MD5: 3b7b13b52f75ed516c888b827710f29a
** Backup your phone to include all of your personal data and copy the files off of your phone.
** Put your phone in bootloader/FASTBOOT USB
Code:
fastboot erase cache
Code:
fastboot oem lock
Code:
[B][I]fastboot oem rebootRUU[/I][/B]
Note: You will see a silver HTC logo on the phone screen
Code:
fastboot flash zip firmware.zip
Note: This will fail with a please flush again message; repeat the same command:
Code:
fastboot flash zip firmware.zip
Note: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Code:
fastboot reboot-bootloader
Note: We need to unlock your bootloader to flash the custom recovery. Using your previous code:
Code:
fastboot flash unlocktoken Unlock_code.bin
Now you should try to flash TWRP, I would try 2.7.1.1 or 2.7.1.2
Hopefully by flashing the stock firmware, it will clean up past flashes to allow the custom recovery to work.

But i'm s-on. I have unlock bootloader, but I Have s-on and I dont know my unlock Code, because before me whose had my HTC and he unlock my device

Any idea?

schizyk12 said:
But i'm s-on. I have unlock bootloader, but I Have s-on and I dont know my unlock Code, because before me whose had my HTC and he unlock my device
Click to expand...
Click to collapse
Here is a step by step guide to unlock your HTC One. There is also a video of the process here. It is pretty straight forward and if you encounter a problem just ask.

But I dont have unlock code and I cant get it

majmoz said:
Here is a step by step guide to unlock your HTC One. There is also a video of the process here. It is pretty straight forward and if you encounter a problem just ask.
Click to expand...
Click to collapse
But I dont have unlock code, and I cant get it

schizyk12 said:
But I dont have unlock code, and I cant get it
Click to expand...
Click to collapse
The procedure in my last post is for getting the code after you flash the firmware!

majmoz said:
The procedure in my last post is for getting the code after you flash the firmware!
Click to expand...
Click to collapse
Hello! I try do it, but I can't flash this firmware. I try few time and I saw only error. What Can I do? I relock my bootloader, and next lock again, but it didn't help.

schizyk12 said:
Hello! I try do it, but I can't flash this firmware. I try few time and I saw only error. What Can I do? I relock my bootloader, and next lock again, but it didn't help.
Click to expand...
Click to collapse
What was the error and when did you get it? Did it look like this:
Code:
sending 'zip' (71868 KB)...
OKAY [4.936s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.410s
If so, then this is expected. You just need to run the command again.
Code:
fastboot flash zip firmware.zip
If not, can you post the error so we can see it?

majmoz said:
What was the error and when did you get it? Did it look like this:
Code:
sending 'zip' (71868 KB)...
OKAY [4.936s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.410s
If so, then this is expected. You just need to run the command again.
Code:
fastboot flash zip firmware.zip
If not, can you post the error so we can see it?
Click to expand...
Click to collapse
Ok, no problem. I do anything and is the same situation. Look post down.

schizyk12 said:
I have a big prolem ;< all is okay, flash succesed. Green line 100%, reboot-bootloader
and I try boot into recovery, and screen is black, soo volume down+power, and I can't now boot into bootloader mode, device only boot again and try run, But I Have a custom rom, and device can't boot to firmware, soo I must run it in bootloader mode and Try install recovery.
Click to expand...
Click to collapse
Nevermind, but all of your instruction done, I boot into bootloader mode and flash twrp, again entering recovery, 2-3sec black screen, and again entering recovery every time..

schizyk12 said:
Nevermind, but all of your instruction done, I boot into bootloader mode and flash twrp, again entering recovery, 2-3sec black screen, and again entering recovery every time..
Click to expand...
Click to collapse
After the firmware update you have to unlock your bootloader before you can install TWRP. Follow this guide for unlocking your bootloader. It was in my earlier post. After you unlock the bootloader, reboot the phone into bootloader/FASTBOOT USB:
Code:
[B][I]fastboot devices[/I][/B]
** You should see your device listed.
Code:
[B][I]fastboot flash recovery <file-name>.img[/I][/B]
** Replace file name with the actual recovery name.
Code:
fastboot erase cache
fastboot reboot-bootloader

[Q] Potential Bricked Device?

Hi, I have an issue as well. It appears my M7 is bricked.
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause. However, I cannot make it S-OFF as adb is not functioning correctly, I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Attempted to factory reset in CWM. Wiped all caches. Attempted to re-flash ROM. Attempted to fastboot oem lock, but still no change.
Please assist if at all possible. Can contact me on Skype as well. Fastboot details are below...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36AW910839
(bootloader) imei: 3544xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4061mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Many thanks!

timex321321 said:
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause.
Click to expand...
Click to collapse
You must be S-OFF to flash ARHD GPE edition otherwise it will bootloop like its doing now.
However, I cannot make it S-OFF as adb is not functioning correctly
Click to expand...
Click to collapse
ADB is only working from a booted rom or from a custom recovery
I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Click to expand...
Click to collapse
Of course, ADB debugging is set to off by default so if you ahve flashed a rom, it will be off unless you turn it on from the dev option menu. Anyway USB debug is only to use ADB when booted in the OS. You can still use ADB from custom recovery even if USB debug is turned off.
Attempted to factory reset in CWM. Wiped all caches. Attempted to re-flash ROM.
Click to expand...
Click to collapse
Will not work unless you s-off the phone first
Attempted to fastboot oem lock, but still no change.
Click to expand...
Click to collapse
Why have you re-locked the bootloader on a bootlooping phone? unlock it again...
Please assist if at all possible. Can contact me on Skype as well. Fastboot details are below...
Click to expand...
Click to collapse
You'll need to flash a rom that doesn't require S-OFF (basically all roms except GPE). Then if you still want to use a GPE rom, achieve S-OFF on a Sense rom (ARHD 81 for example) and flash your GPE rom after.
If you are gonna flash a Sense rom (ARHD 81), get rid of CWM and flash TWRP 2.6.3.3.

timex321321 said:
Hi, I have an issue as well. It appears my M7 is bricked.
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause. However, I cannot make it S-OFF as adb is not functioning correctly, I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Many thanks!
Click to expand...
Click to collapse
According to the OP:
Android Revolution HD 6.1 Google Edition
You need S-OFF, otherwise you'll experience boot-loop!
You need TRWP 2.6.3.3 custom recovery!​
Flash TWRP 2.6.3.3
Install AHRD 81.0
If you want to flash GPe ROM, then obtain S-OFF!
ADB only needs USB Debugging when in the OS; it works just fine in Recovery Mode without USB Debugging. You can use alray's method to push the ROM to your phone:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?

timex321321 said:
I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?
Click to expand...
Click to collapse
See my post #3 above yours!

timex321321 said:
I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?
Click to expand...
Click to collapse
read the first post. Particularly what said about ADB or at least take the time to read the instructions Majmoz just posted...

Flash twrp 2.6.3.3, boot into it and then use adb push or adb sideload commands to push or install a ROM.

Thanks for the information. I re-unlocked, and flashed TWRP. When trying to push firewater for S-OFF it just hangs. The good news is that the device is now being recognized when doing adb devices. Any ideas?

timex321321 said:
Thanks for the information. I re-unlocked, and flashed TWRP. When trying to push firewater for S-OFF it just hangs. The good news is that the device is now being recognized when doing adb devices. Any ideas?
Click to expand...
Click to collapse
You need a working ROM on your phone for firewater to work. Push ARHD 81.0 first and boot into it. After you know it is working then try firewater!

majmoz said:
You need a working ROM on your phone for firewater to work. Push ARHD 81.0 first and boot into it. After you know it is working then try firewater!
Click to expand...
Click to collapse
Doesn't that ROM require S-OFF? Hence why I am trying to install Firewater.

timex321321 said:
Doesn't that ROM require S-OFF? Hence why I am trying to install Firewater.
Click to expand...
Click to collapse
ARHD 81.0 requires S-ON and an unlocked bootloader. You really need to read the OP:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock

majmoz said:
ARHD 81.0 requires S-ON and an unlocked bootloader. You really need to read the OP:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
Click to expand...
Click to collapse
Even on base 4.4.2 still go to ARHD 81.0? Or will I have to upgrade my base?

timex321321 said:
Even on base 4.4.2 still go to ARHD 81.0? Or will I have to upgrade my base?
Click to expand...
Click to collapse
You will be alright with your current base.

Big thanks to all the posters here. Issue has been solved successfully with your help! :good::good::good:

[ROM][11.0][UNOFFICIAL][Vanilla]LineageOS v18.1 Sofiar

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1​
​
Links
ROM Download
LineageOS Website
Vache's TWRP Recovery
Magisk
FlameGApps
Installation
First Time Installation:
Reboot to recovery
Wipe data, cache, and dalvik if coming from another ROM
Flash ROM zip
(optional) Flash GApps (for vanilla builds)
(optional) Flash Magisk (root)
Format data
Reboot and voila!
Upgrading to a Newer Build:
Reboot to recovery
Flash ROM zip (The update downloaded by the ota updater will be located in /data/ota_package)
(optional) Flash Magisk (root)
Reboot and voila!
Source
LineageOS Source
Device Build Info
​Known Issues
• FM Radio doesn't work
• USB tethering doesn't work on first boot
• Must use android 10 vendor like other sofiar roms
• Android Auto doesn't work on android 10 vendor
• Stylus actions dies between reboots, just open it within settings
• OTA updater still isn't working properly
LineageOS, ROM for Rav/Sofia-R-P(commonly shortened to sofiar)
Devices: Sofiap (Moto G Stylus/G Pro), Sofia/Sofiar (Moto G Power/G⁸ Power), and Rav (Moto G⁸/G Fast)
Maintainer: ph4n70m
Build Type: Unofficial
Credits
- Vache: The initial device and vendor tree
- Beetle84: Giving me a ton of help

@ph4n70m-404 , is signature spoofing enabled for MicroG? Also is it patched for proper TTS functioning?
One more thing, can this be flashed on stock 11 base or like all the others on stock 10?

celrau said:
@ph4n70m-404 , is signature spoofing enabled for MicroG? Also is it patched for proper TTS functioning?
One more thing, can this be flashed on stock 11 base or like all the others on stock 10?
Click to expand...
Click to collapse
No mostly because on telegram there is already Lineage Foss builds (but i might make a magisk module to apply the patch), probably not because no one has brought that edit to my attention, no you must flash it ontop of android 10.

Fantastic thanks for the work on this!
Can confirm working on my moto g power (2020) with Magisk.
Some notes I took that might help others:
Spoiler: instructions
Note: I don't guarantee that my notes give the fastest or best way of installing this ROM! I'm just including these instructions because they detail one working way of doing this. Use at your own risk!
You have two ways to flash, using fastboot (where you need to download lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip) or sideloading with TWRP (where you need to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip). Probably use the newest version (the datestamp in the filename should be the latest). I chose to sideload with TWRP. Since I also wanted magisk (root) I also ended up needing to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip anyway to flash boot.img, which it contains (see below).
The main instructions I used can be found here: https://wiki.lineageos.org/devices/channel/install
1 - I flashed the linked TWRP to temporary recovery by fastboot flashing to boot_a and boot_b. Upon reboot to recovery it would first reboot to android recovery (pic of dead droid with red exclamation point) and hang. I needed to press the power button until that screen disappeared. It would then reboot into TWRP.
2 - I sideloaded lineage-18.1-20211010-UNOFFICIAL-sofiar.zip using TWRP (Advanced->ADB Sideload) after reverting to factory (i.e. clearing data and cache)
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
4 - I wanted magisk (follow the instructions at https://topjohnwu.github.io/Magisk/install.html) so I installed the Magisk apk and then used its app to flash the boot.img in lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip, then transferred that back to my PC ('adb pull /sdcard/Download/magisk_patched_[random_strings].img')
5 - then 'adb reboot fastboot' will take you to fastbootd (this is different from fastboot, although you can probably also use fastboot) where you can run 'fastboot flash boot /path/to/magisk_patched.img'
6 - reboot and done
** In the process of figuring this out I got caught in some softlocks and bootloops. Just turn off the phone and turn it back on holding the down-volume with power to get into fastboot, then restart at step 1. I think this happens sometimes when A/B conflict arises, I'm not sure...
EDIT: @ehidle reminded me that there are some steps before flashing I didn't mention:
You need to first unlock your bootloader. Follow
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
(You'll need to create a Motorola account.)
You also need to have a stock ROM with Android 10 (not 11!). You can find instructions at this guide.
TLDR:
If you have the US version Moto G Power (2020) you can find them here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
If you have the G8 Power you can find them here: https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Addendum: Updating with new release
Just upgraded to the Nov 8th release from the October one. Worked seamlessly! A few notes:
1-You can find the updater at Settings->System->Advanced->Updater. Refresh and then click on the release you want to download. It will download and prepare the image.
2- Once it says it is done, you can reboot to TWRP (which for me isn't permanent so I had to reflash that into boot_a and boot_b as explained above in my first instructions) and "Install" the updated lineage image zip (i.e. flash the ROM) you downloaded. Note: I found the zip in /data/lineageos_updates not in /data/ota_package as indicated by @ph4n70m-404 in the original post.
3- Reboot and you're done. Everything will be saved as before except magisk root will be gone if you had it before. The magisk app will still be there.
4- (Optional to get back root). Repeat the same steps as above in my first instructions to get back root. i.e. download the FASTBOOT version of the corresponding new release (ROM Download) and unzip and transfer boot.img to your phone and patch it with the magisk app, and finally reboot to TWRP and flash boot with this patched magisk_patched*.img (or alternately return to fastboot and 'fastboot flash boot /path/to/magisk_patched.img).

was able to flash the rom fine (used fastbootd version, flashed boot, product, system, vbmeta imgs (in that order) then switched from fastbootd to regular fastboot to do "fastboot -w") but my Sprint LTE internet is not working. it just says 1X or 3G, but there will never be a connection. SMS messages and calls still work. here's my "fastboot getvar all" output after installing patched boot.img from magisk:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofia_retail-3b6d53a311-200901
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 07E6EA84
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805261312
(bootloader) reason: Volume down key pressed
(bootloader) date: 06-18-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) battid: SB18C57587
(bootloader) battery-voltage: 4187
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-109-5/2d6e7:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Tue Sep 1 03:2
(bootloader) kernel.version[3]: 3:51 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-61355838c-200901
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-61355838c-200901
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-200901
(bootloader) git:tz: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:hyp: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:devcfg: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:keymaster: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:prov: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:abl: MBM-3.0-sofia_retail-3b6d53a311-200901
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-200901
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C55260
all: listed above
Finished. Total time: 0.072s

Excellent. I was just looking for a way to restore my horrifically sluggish G Power to some usability.
Question though: no mention in this post of unlocking the bootloader... is that not necessary?

ehidle said:
Excellent. I was just looking for a way to restore my horrifically sluggish G Power to some usability.
Question though: no mention in this post of unlocking the bootloader... is that not necessary?
Click to expand...
Click to collapse
Unlocking the bootloader is a given, you will also need to downgrade back to stock a10.

ph4n70m-404 said:
Unlocking the bootloader is a given, you will also need to downgrade back to stock a10.
Click to expand...
Click to collapse
That's what I figured but it was not listed in the instructions.
Help me out though since I'm not up on all the lingo. Downgrade to stock A10? What does this mean exactly?
EDIT: OOOHHHH duh... stock Android 10... okay so I need to find some stock images for that because it's on 11 now... Got it.. too early

rightonyourtail said:
Fantastic thanks for the work on this!
Can confirm working on my moto g power (2020) with Magisk.
Some notes I took that might help others:
Note: I don't guarantee that my notes give the fastest or best way of installing this ROM! I'm just including these instructions because they detail one working way of doing this. Use at your own risk!
You have two ways to flash, using fastboot (where you need to download lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip) or sideloading with TWRP (where you need to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip). Probably use the newest version (the datestamp in the filename should be the latest). I chose to sideload with TWRP. Since I also wanted magisk (root) I also ended up needing to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip anyway to flash boot.img, which it contains (see below).
The main instructions I used can be found here: https://wiki.lineageos.org/devices/channel/install
1 - I flashed the linked TWRP to temporary recovery by fastboot flashing to boot_a and boot_b. Upon reboot to recovery it would first reboot to android recovery (pic of dead droid with red exclamation point) and hang. I needed to press the power button until that screen disappeared. It would then reboot into TWRP.
2 - I sideloaded lineage-18.1-20211010-UNOFFICIAL-sofiar.zip using TWRP (Advanced->ADB Sideload) after reverting to factory (i.e. clearing data and cache)
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
4 - I wanted magisk (follow the instructions at https://topjohnwu.github.io/Magisk/install.html) so I installed the Magisk apk and then used its app to flash the boot.img in lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip, then transferred that back to my PC ('adb pull /sdcard/Download/magisk_patched_[random_strings].img')
5 - then 'adb reboot fastboot' will take you to fastbootd (this is different from fastboot, although you can probably also use fastboot) where you can run 'fastboot flash boot /path/to/magisk_patched.img'
6 - reboot and done
** In the process of figuring this out I got caught in some softlocks and bootloops. Just turn off the phone and turn it back on holding the down-volume with power to get into fastboot, then restart at step 1. I think this happens sometimes when A/B conflict arises, I'm not sure...
EDIT: @ehidle reminded me that there are some steps before flashing I didn't mention:
You need to first unlock your bootloader. Follow
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
(You'll need to create a Motorola account.)
You also need to have a stock ROM with Android 10 (not 11!).
If you have the US version Moto G Power (2020) you can find them here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
If you have the G8 Power you can find them here: https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Addendum: Updating with new release
Just upgraded to the Nov 8th release from the October one. Worked seamlessly! A few notes:
1-You can find the updater at Settings->System->Advanced->Updater. Refresh and then click on the release you want to download. It will download and prepare the image.
2- Once it says it is done, you can reboot to TWRP (which for me isn't permanent so I had to reflash that into boot_a and boot_b as explained above in my first instructions) and "Install" the updated lineage image zip (i.e. flash the ROM) you downloaded. Note: I found the zip in /data/lineageos_updates not in /data/ota_package as indicated by @ph4n70m-404 in the original post.
3- Reboot and you're done. Everything will be saved as before except magisk root will be gone if you had it before. The magisk app will still be there.
4- (Optional to get back root). Repeat the same steps as above in my first instructions to get back root. i.e. download the FASTBOOT version of the corresponding new release (ROM Download) and unzip and transfer boot.img to your phone and patch it with the magisk app, and finally reboot to TWRP and flash boot with this patched magisk_patched*.img (or alternately return to fastboot and 'fastboot flash boot /path/to/magisk_patched.img).
Click to expand...
Click to collapse
@rightonyourtail. I just found this today. I'm currently using @Beetle84's Havoc 4.8 on my Moto G8 Power 2020 (Sofia), but my battery charge is only lasting about a day. I'm very familiar with LOS and I'm running followmsi's LOS 18.1 on my ancient Galaxy Note 4 Snapdragon, and my 3 Nexus 7 2013 deb (4G/LTE) tablets. Do you think this ROM will increase my battery life, and do I need to do something special considering that I'm already running @Beetle84's Havoc 4.8? I look forward to flashing this ROM pursuant to your useful notes.
Thanks

whenever i try to adb sideload the non fastbootd one i just get a boot loop with the lineage os boot screen with the circle going across the screen. anyone able to help me figure that out?

jhford said:
@rightonyourtail. I just found this today. I'm currently using @Beetle84's Havoc 4.8 on my Moto G8 Power 2020 (Sofia), but my battery charge is only lasting about a day. I'm very familiar with LOS and I'm running followmsi's LOS 18.1 on my ancient Galaxy Note 4 Snapdragon, and my 3 Nexus 7 2013 deb (4G/LTE) tablets. Do you think this ROM will increase my battery life, and do I need to do something special considering that I'm already running @Beetle84's Havoc 4.8? I look forward to flashing this ROM pursuant to your useful notes.
Thanks
Click to expand...
Click to collapse
I don't have any familiarity with Havoc. I can only say that I regularly get >3 days of battery life with LOS but with heavy video streaming it can get down to one day.
If you decide to try LOS, you'll need to flash stock Android 10 on the device with Havoc first.

thep_irate said:
whenever i try to adb sideload the non fastbootd one i just get a boot loop with the lineage os boot screen with the circle going across the screen. anyone able to help me figure that out?
Click to expand...
Click to collapse
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
I assume you've waited over, say 5 minutes (or maybe 10-20 min to be sure)? If so, you might want to try again but first wipe data, system, cache, and dalvik cache in TWRP.

rightonyourtail said:
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
I assume you've waited over, say 5 minutes (or maybe 10-20 min to be sure)? If so, you might want to try again but first wipe data, system, cache, and dalvik cache in TWRP.
Click to expand...
Click to collapse
i know i waited over 20 minutes i let it sit overnight so ill try all that

rightonyourtail said:
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
I assume you've waited over, say 5 minutes (or maybe 10-20 min to be sure)? If so, you might want to try again but first wipe data, system, cache, and dalvik cache in TWRP.
Click to expand...
Click to collapse
i think its still boot looping

thep_irate said:
i think its still boot looping
Click to expand...
Click to collapse
Were you on android 10 or 11 before flashing?

Beetle84 said:
Were you on android 10 or 11 before flashing?
Click to expand...
Click to collapse
11 pretty sure

rightonyourtail said:
I don't have any familiarity with Havoc. I can only say that I regularly get >3 days of battery life with LOS but with heavy video streaming it can get down to one day.
If you decide to try LOS, you'll need to flash stock Android 10 on the device with Havoc first.
Click to expand...
Click to collapse
This brings up a question I've wondered about: We know that if you're running stock A11, you must downgrade to A10 before installing a custom A11 ROM. But is that required when switching from a custom A11 to a different custom A11?
I went straight from OEM A10 to a custom ROM and have switched among a handful without the downgrade (most recently from Beetle's Havoc to Arrow) with no discernable issues. BTW I've always installed via the fastbootd files.

Leroy_Sparks said:
This brings up a question I've wondered about: We know that if you're running stock A11, you must downgrade to A10 before installing a custom A11 ROM. But is that required when switching from a custom A11 to a different custom A11?
I went straight from OEM A10 to a custom ROM and have switched among a handful without the downgrade (most recently from Beetle's Havoc to Arrow) with no discernable issues. BTW I've always installed via the fastbootd files.
Click to expand...
Click to collapse
im a huge noob. how would i go about downgrading to android 10?

thep_irate said:
im a huge noob. how would i go about downgrading to android 10?
Click to expand...
Click to collapse
From my instructions above:
You also need to have a stock ROM with Android 10 (not 11!).
If you have the US version Moto G Power (2020) you can find them here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
If you have the G8 Power you can find them here: https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
Flash stock A10 first and then reboot before trying to flash LOS. Hope this solves your problem!

rightonyourtail said:
From my instructions above:
Flash stock A10 first and then reboot before trying to flash LOS. Hope this solves your problem!
Click to expand...
Click to collapse
flashing A10 now. hope this fixes it