Related
A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!
Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.
Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.
morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).
Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Kopiok said:
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Click to expand...
Click to collapse
Try the solution in the last few posts on this thread. http://forum.xda-developers.com/showthread.php?t=2465695
I hope you get more knowledgeable advice than mine but, were I in your situation, my primary goal would be to get back to STOCK. Forget CM and modding for now. Either through TWRP or through the recovery settings on the phone itself I'd get to where I could do a factory reset. If you're continuously able to boot into TWRP I don't see how your phone could be bricked. My experience is, if I can get a phone to do ANYTHING I've got a shot at figuring out how to get out of whatever mess I've created. I don't know if this could be a factor but I'd put in a different micro SD card too, in case there's something on the card you've got in there.
Just an update. So, I got it to go back to fastboot this morning and I tried using the Razr Utility to flash back stock and stock recovery, but I got a "Failed" line with the reason "Remote Failure". Not sure what that's about. When it reset it got back to the Cyanogenmod boot graphic, but it never started. I left it there for a good 12 minutes.
Right now it's sitting in TWRP. I'm going to let it charge to 100% (it was a little less when I tried all of this) and attempt it again at 100% battery. Thanks for the help so far!
So, I tried using the Razr Utility to flash the system, kernel, radio and for system it was unsuccessful (something about too many threads or strings, something to that effect), but the rest said OK. Now my phone doesn't seem to turn on. My computer still makes the device plugged in sound when it's plugged/unplugged, but I cannot get the screen to show anything or seem to turn on the phone.
Is this it? Is it... bricked!? ;-;
Edit: I ordered the Factory Adapter as a last resort sort of thing. This is lame.
Edit Edit: I've seen the boot logo since my last edit! But... it's not coming back and I still can't even bring up the bootloader. I don't know why it will sometimes turn on or sometimes not. In any case, I'm now hopeful that not ALL is lost.
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
That's the plan! One odd thing happening now... My phone's screen isn't showing anything, so I assumed it was off. I left it unplugged and went to see a movie..... and the phone is still warm. This leads me to believe the phone is still drawing power, for some reason... God this is weird. I'll wait for the adapter and try again. Thanks for the help!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
according to the packaging on mine from tbh a chinaman made it, just sayin
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
cellzealot said:
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
Click to expand...
Click to collapse
thanks for making it either way, better to have and not need.
havent had to use it so far
bweN diorD said:
thanks for making it either way, better to have and not need.
havent had to use it so far
Click to expand...
Click to collapse
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
cellzealot said:
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
Click to expand...
Click to collapse
how many thousands, and whats the plan?
I got the Factory Adapter and used RSD Lite to flash stock. And it works! Yay! It's starting up reliably and everything.
Except... it won't start up without the cable attached, and the battery icon has a big question mark on it. It also won't connect to the cell network (but does connect to WiFi). What do I do now?
Edit: So I noticed that while the battery status said "Unknown", it did go from 2% to 3% charge level when I plugged it in normally for a little. My plan at the moment is to try leaving it plugged in for a while and then try taking the OTA update to see if that fixes everything. Good plan?
Edit Edit: Never mind! I just had to let it charge for a bit. It seems to be back in working order, now! Thank you so much for all the help everyone!
That is exactly what is supposed to happen. Congrats on fixing your phone!
The factory cable/adapter does not charge the device but powers it directly, allowing it to boot no matter what state the battery is in or even without a battery at all.
You cannot charge in bootloader, which is why the cable/adapter is so valuable. Once the device can boot/charge normally then you are all set.
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
Unlocked, rooted, TWRP, Cataclysm Final Lollipop (my phone never played nice with any MM ROM I tried, so I just went back to this and have been great ever since)
My phone has been rock stable for months, today I pull it out of my pocket and the screen is black. I turn it back on and it freezes on the Google screen with the unlock logo.
I can get into bootloader via power+voldown, but if I launch recovery it gets past the Google screen but then freezes on the TeamWin page.
Any suggestions, please? Searches intimate power button issues, but given I get no bootloops, I can turn the phone off reliably by holding the power button down, and it freezes at the same point consistently, it's hard for me to think that's the issue in my scenario, too. Thank you!
As an update, I used fastboot to successfully flash the newest version of TWRP, just to be sure, but it still gets stuck in the same spot, as does trying to boot normally.
Try flashing a stock ROM including userdata.img file.
audit13 said:
Try flashing a stock ROM including userdata.img file.
Click to expand...
Click to collapse
Thanks for the suggestion. Is there any way to get my personal data off before I do this?
I guess beggars can't be choosers, but I'd hate to lose anything I don't have backed up already if it ends up being another issue after all (the power button, etc.).
A corrupted ROM can prevent a clean, freshly-installed recovery from launching properly?
Thanks again.
Try flashing different version of TWRP? Maybe one of them will allow you to mount the data partition and copy off your data.
While trying to flash the (stock) new system images, I keep getting "remote: flash write failure" and/or "remote: failed to erase partition." This is via a toolkit or manually via fastboot.
The bootloader remains unlocked through all this
It's especially odd, since now I'm getting it on my recovery partition, which I was able to write to earlier today.
A cursory search of this forum suggests I'm SOL unless I replace the whole motherboard, at which point I might as well get a new phone. Do you (all) concur?
Last ditch thought: I went jogging when it went dead--outside chance a connection to the memory on the motherboard got jostled and could be reattached? Or is it fried?
Continued thanks.
The memory is soldered into place but it is possible that something happened during your jog. I also jog with my nexus 5 for 20 to 30 km per week and have done so for the past year without any issues.
*hangs head in shame*
Ok, I'm stumped and I need help.
Last time I rooted a phone, it was our old HTC Thunderbolts... Things have changed significantly since then, or so it would appear.
Trying to fix my wife's phone after a Verizon OTA update seems to have jumped her phone from Android 10 to 11, and in the process nerfed the hotspot (which we need, as we're rural with no landline broadband available)
I'm working on a Moto G Power (sofia XT2041-4), bought late last year off the shelf from Best Buy.
Home PC is a Windows 10 box. I do not have a linux environment available to me.
I am \ was trying to put LinageOS on it, but honestly don't care what OS it is as long as we can turn the hotspot on ourselves, regardless of what Verizon wants. Over a decade ago, I rooted our phones with ICS image, so I have some outdated experience here. CalyxOS looks nice but I don't think it'll work on Moto G Power.
So, here's where I'm at in the last 48 hours.
I have gone in and gotten the unlock key from motorola, and successfully undone the OEM Lock. (I know this is the case because it tells me I'm an idiot and I should lock it, every time it boots up now). This also managed to wipe the phone, which, oops, read to the end of the paragraph BEFORE unlocking and deleting pictures of the grandkids which came in since the last backup.
Somehow last night, I managed to get it to be a brick, but used LMSA to unbrick it, but that version is still the OTA updated Android 11, so same problem with the hotspot.
I have installed the Android SDK, newest motorola drivers, and also the standalone 'Minimal ADB and Fastboot' on my PC
I've managed to get TWRP installed in the recovery portion of the phone. (note: may have been wiped now, but I can get it back on I believe)
Following this video, I managed to bring TWRP up, wiped the device, then copied the Lineage OS image to the microSD card, as well as Open GApps. The only thing I couldn't get to work, other than, you know, the new OS, is I didn't see a place to enable advanced boot options, so I have to get back to the bootloader via Volume Down and Power from a full shutdown state.
When I try to install the LinageOS (17.1), it looks like it's installing, goes through steps 1 and 2, then a slew of error messages in the log.
I've got the 4 image files I pulled out of one of the LineageOS zip files (Boot, Product, System, VBMeta) in the 'Minimal ADB and Fastboot' directory.
I can run 'fastboot flash boot boot.img' from the 'Minimal ADB and Fastboot' directory and it succeeds.
When I try to run Product, System or VBMeta in the same way (cmdline = fastboot flash product product.img), all of them fail the Preflash Validation and it comes back with 'FAILED (remote failure)'
During this process, somehow I bricked my wife's phone AGAIN, but just got it reset with LMSA for the second time. So, I may have wiped out everything I've done previously on the phone, which may or may not be a good thing. But, I believe everything I've done up to this point is repeatable (which is somewhat why I wrote all of the above details out)
Edit: Progress is Made! - Ok, now that I've got FASTBOOTD figured out, I was able to flash the Boot, Product, System and VBMeta into active partition A. But when I use the command 'flashboot reboot' it just keeps coming back to the fastboot flashload screen with the green android with it's access panel open. I tried to get back into TWRP via entering 'Recovery Mode' at the loader, but apparently it got wiped. I'm guessing I should flash it back into the recovery slot ("fastboot flash recovery twrp-3.4.0-0-sofia-test9") and then maybe try to recover from Partition A via TWRP?
Things I'm not sure about
First, I'm pretty sure I'm not in FastbootD. I don't see a big red FASTBOOTD at the top, and according to this thread, means I'm not in it.
Update: Ok, I realized I didn't have the 'platform tools', which I have now downloaded, and once I was back in fastboot, I was able to run 'Flashboot reboot flashboot' and now I know I'm in FlashbootD. Not sure what I'm supposed to do in here at this point, but hey, I've now got the correct interface.
I think FASTBOOTD should be something I'm interacting with on the Moto G Power, but for the life of me, I can't figure out how to get to it.
Update on this, see above.
I feel like I've got to be CLOSE to getting this thing working, but damned if I can seem to cross the finish line.
Help?
Further Edit: So, I tried another OS, ResurrectionOS, just to see if it was an issue with the image.
Started with another reset with LMSA (I love that tool... It zeroes out all the stupid things I'm doing on the Moto G Power during this process)
Rebooted into FastBootD mode (with the nice red at the top)
Flashed all four of the images. No errors noted during the process
Wiped the Data
Rebooted... And right back to the bootloader. Cannot seem to get out of the boot loader to get the new OS to initialize.
Again, Help?
Did you ever solve this riddle?