Hello, so recently I tried to fix my bootlooped Moto G 3rd gen(dual-sim, India) and made a mistake that has somewhat fixed my phone but the wifi doesn't work, there might be some undiscovered errors still, the whole story..
-The phone became bootlooped like I said above
-So I decided to flash stock rom for it, and looked up several guides on how to do it.
-Downloaded the correct rom, and connected the phone in recovery mode as I could still hold down power button while phone loops(switch on to logo-pause-black screen repeat...)
-After setting correct path for fastboot, I got the [FAILED ] REMOTE ERROR while flashing partition - the "gpt.bin file"
-So I decided to skip that and went on with rest of the given commands including all 6(number 0 to number 5) sparsechunks
-I received signed error for sparsechunks
-I continued upto reboot
After this the phone booted fine but wouldn't get past selecting wifi network phase of start setup screen
Somehow a repair guy I gave phone to fix got up to that with login details of account, and now the phone is functional but I can't manage to turn on the wifi, if I hit on it automatically slides back to off instantly.
Notes: After fastboot and the start phase issue I tried mfastboot with same rom files and went over all commands many times, with same error
: After the phone became functional I tried flashing process again with mfastboot and usb debugging enabled but received REMOTE ERROR at partition again and stopped there.
That's all so far, any advice or suggestion you could give is highly appreciated. Thanks for your time.
Same problem.
zarama12 said:
Hello, so recently I tried to fix my bootlooped Moto G 3rd gen(dual-sim, India) and made a mistake that has somewhat fixed my phone but the wifi doesn't work, there might be some undiscovered errors still, the whole story..
-The phone became bootlooped like I said above
-So I decided to flash stock rom for it, and looked up several guides on how to do it.
-Downloaded the correct rom, and connected the phone in recovery mode as I could still hold down power button while phone loops(switch on to logo-pause-black screen repeat...)
-After setting correct path for fastboot, I got the [FAILED ] REMOTE ERROR while flashing partition - the "gpt.bin file"
-So I decided to skip that and went on with rest of the given commands including all 6(number 0 to number 5) sparsechunks
-I received signed error for sparsechunks
-I continued upto reboot
After this the phone booted fine but wouldn't get past selecting wifi network phase of start setup screen
Somehow a repair guy I gave phone to fix got up to that with login details of account, and now the phone is functional but I can't manage to turn on the wifi, if I hit on it automatically slides back to off instantly.
Notes: After fastboot and the start phase issue I tried mfastboot with same rom files and went over all commands many times, with same error
: After the phone became functional I tried flashing process again with mfastboot and usb debugging enabled but received REMOTE ERROR at partition again and stopped there.
That's all so far, any advice or suggestion you could give is highly appreciated. Thanks for your time.
Click to expand...
Click to collapse
I have same problem. I can't use WiFi or Internet on other custom/Stock ROM. Not problem on nandroid backup.
Make sure you have the correct firmware files downloaded
Avinash Mali said:
I have same problem. I can't use WiFi or Internet on other custom/Stock ROM. Not problem on nandroid backup.
Click to expand...
Click to collapse
I was going to post how I fixed it but it slipped from my mind.
The flashing problem(Remote error) seems to be caused by the locked bootloader, which I only discovered after needing to root my phone following a guide to fix the wifi.
The thing is, a lot of people who have this problem seem to miss a file in the 'persist' folder of their root directory, see: http://forum.xda-developers.com/showthread.php?t=2619553
However for me it didn't fix the issue, mostly since the file isn't available for 3rd gen moto G, but with unlocked bootloader (see: http://theunlockr.com/2015/09/09/how-to-root-the-motorola-moto-g-3rd-gen/) I could flash other parts just fine (except gpt.bin still giving the same error) and it pretty much fixed my issue.
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...
Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.
Have you tried factory reset? Or boot into safe mode?
Zeljko1234 said:
Have you tried factory reset? Or boot into safe mode?
Click to expand...
Click to collapse
Factory reset yes , however after device reboot it does nothing comes back t same faulty OS.
Safe mode?
Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.
Zeljko1234 said:
Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.
Click to expand...
Click to collapse
Tried flashing , in safe mode no luck either , any other suggestions?
Cheers,
You probably left your USB plugged in after you flashed Recovery and that set you back to Stock Recovery.....unplug the usb....
Hmm sounds like symptons that my dad's old Nook color experienced being stuck in read only mode. Tried everything but it was stuck in that read only state no matter what I did. Hopefully that is not the case for your phone. Have you tried house of moto or other compatible utility to restore back to stock?
this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.
Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
desitunez said:
Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.
Click to expand...
Click to collapse
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
bweN diorD said:
this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.
Click to expand...
Click to collapse
surfmly said:
Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
Click to expand...
Click to collapse
if your phone goes to read only because of that faulty version of twrp, its toast. i am sorry for your loss
He can try to flash correct twrp...
Zeljko1234 said:
He can try to flash correct twrp...
Click to expand...
Click to collapse
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.
bweN diorD said:
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.
Click to expand...
Click to collapse
Well it looks like I was able to get through some of it. I followed the instructions here: http://www.droidrzr.com/index.php/topic/49699-1834614xt926-ota/. I did the extra step of going to stock 183 (unrooted) and then flashed the update in that and the phone is working fine. I am already unlocked (have been for long time), but not rooted at the moment. I believe I can root now (being that I am unlocked) but haven't tackled that yet. At the very least I have a phone that works for my upcoming business trip.....
BTW - the TWRP I had installed has been used on my phone for a long time (8-12 months??) so not sure why that version all of a sudden would have caused the issue, but at this point it doesn't appear to have been that issue (with data locked in read only mode).
I'm really glad that you found solution for you and for all of us who may have the same problem in the future. Thx.
Hello Everyone,
I have searched this forum and followed many useful threads which seemed related to my issue, alas none have actually been able to fix my phone.
I am using a stock ROM which upgraded to marshmallow not too long ago. The other day my phone rebooted for no reason got it's self into a boot loop. Since them I have tried the following:
1) I have used recovery mode and cleared the cache/performed a factory reset. I just the get the can't mount/cache line pop up.
2) Tried to use ADB to boot an image over the USB but couldn't get much from this (so I may have missed something with this).
3) Tried to use fastboot to move flash back to a version of marshmallow downloaded. When I go to flash files in I get failed messages on command prompt. (Failed, remote flash write error).
additional info
1) the device was encrypted from the settings menu when functional.
Any advice or help would be good at this point. Let me know if additional information is needed.
Thanks!
Hi all guys
i'm going to tell you my little problem, this morning, in my honor8 with stock rom:
my operations, step by step:
- unlock the bootloader, via adb and fastboot
- twrp installed
- from twrp, magisk installed
- Root OK, SafetyNet OK
- then I started to play with the apps, deleting the system that I could not uninstall before (such as gmail, the various pre-installed games etc etc, but no particular app, only known stuff)
- I tried to install a trivial apk inside the system folder. then I realize that now the SafetyNet gives negative result (I do not assure that it was the fault of the app installed on the system folder, but I realized after this operation).
- so, i wanted to restart from the beginning: I wiped and formatted the whole operating system
- with HuaweiUpdateExtractor e fastboot i reinstalled the os (official rom FRD-L09C432B389) with the files BOOT.img, CUST.img, RECOVERY.img, SYSTEM.img
- first problem: when i pressed vol.up+vol.down+power, I started the installation but shortly after I get stucked with the words "Software install failed". Restarting the system, I have seemingly functioning android.
- Apparently, cuz everything works, except for the developer options. I enable it, I click on it, crashes the "settings" app, making me return to the phone's home.
You know:
if i can't enter in the developer mode, i can't activate the "debug usb" options
if i can't activate the Debug usb, i can't recognize the smartphone with fastboot
if i can't recognize the smartphone with fastboot, i can't install twrp
if i can't install twrp, i can't do anything, root included
The only thing I have is the bootloader unlocked (in fact when I start the phone, it warns me of this).
By the way, pressing vol.su or vol.giù + power no longer enters me either in fastboot mode, or in, of course, twrp.
Has anyone come across my own problem?
Do I have a way to reinstall a rom (not necessarily the official) in my situation?
Hopefully, ideas on how to solve?
ps: the phone, in any case, works: google play it's ok, I get calls, internet it's ok etc etc .... the only thing is these developer options are not working and the inability to re-lock the bootloader to send it in assistance with the warranty
I add one thing:
I read that in the Q2 2018, honor8 should receive Oreo.
Is it possible that I solve the problem via the OTA update?
I apologize for my bad English, I hope I was clear enough
Had a similar issue when I was trying to go back to stock. Couldnt boot into an OS because there was not one, and I couldnt get USB debugging to work.
I then flashed the original OS through the original erecovery by loading it onto my SD card. I loaded the entire file onto it unzipped, not with just the 4 img files. For some reason, it came up as a half baked version of the OS (probably because of not flashing the region zip), but it was enough to get me to USB debugging and fastboot. I then flashed TWRP, flashed the operating system, did a factory reset, and went from there.
EDIT: Your English is plenty good enough for most people.
EDIT2: Have you also tried to maually go into download mode and see if you are able to flash TWRP from there? I've done that before as well.
Deemo13 said:
Had a similar issue when I was trying to go back to stock. Couldnt boot into an OS because there was not one, and I couldnt get USB debugging to work.
I then flashed the original OS through the original erecovery by loading it onto my SD card. I loaded the entire file onto it unzipped, not with just the 4 img files. For some reason, it came up as a half baked version of the OS (probably because of not flashing the region zip), but it was enough to get me to USB debugging and fastboot. I then flashed TWRP, flashed the operating system, did a factory reset, and went from there.
EDIT: Your English is plenty good enough for most people.
EDIT2: Have you also tried to maually go into download mode and see if you are able to flash TWRP from there? I've done that before as well.
Click to expand...
Click to collapse
thx for your help Deemo!
Last night i solved the problem just like you said:
the initial difficulty (not possible to enter in fastboot or twrp) was solved in the most banal way I could imagine: with phone off, hold the vol.down button and attach the usb cable. the terminal starts in fastboot mode....I didn't know this method
I found another thread here, where to download the official rom (link to the discussion)
instead of the one I used before, this have the dload folder (never found in previous downloads). I immediately put the dload folder (with the update.app in it) in the microsd.
once in there, everything was easy:
- reinstalled twrp from cmd.exe with fastboot
- started twrp from the mobile phone (a cell turned off, vol.up+power)
- wiped cache, data and dalvik
- turned off the phone
- press vol.up+vol.down+power, the installation starts, but this time, ends correctly.
at the first start, the honor logo in the blue background was there for several minutes (i was worried ) but then, started the initial configuration and the developer options are back to work!
Obviously the phone now no longer has the bootloader unlocked or the root. As if it were new!
This weekend I start all over again, at least I try to do other damages
Gabbbo85 said:
thx for your help Deemo!
Last night i solved the problem just like you said:
the initial difficulty (not possible to enter in fastboot or twrp) was solved in the most banal way I could imagine: with phone off, hold the vol.down button and attach the usb cable. the terminal starts in fastboot mode....I didn't know this method
I found another thread here, where to download the official rom (link to the discussion)
instead of the one I used before, this have the dload [/ B] folder (never found in previous downloads). I immediately put the dload folder (with the update.app in it) in the microsd.
once in there, everything was easy:
- reinstalled twrp from cmd.exe with fastboot
- started twrp from the mobile phone (a cell turned off, vol.up+power)
- wiped cache, data and dalvik
- turned off the phone
- press vol.up+vol.down+power, the installation starts, but this time, ends correctly.
at the first start, the honor logo in the blue background was there for several minutes (i was worried ) but then, started the initial configuration and the developer options are back to work!
Obviously the phone now no longer has the bootloader unlocked or the root. As if it were new!
This weekend I start all over again, at least I try to do other damages
Click to expand...
Click to collapse
Glad I could help!
You should be able to unlock the bootloader again if you kept your original bootloader code.
*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?