I flashed TWRP and the superSU. My phone kept looping to 'fastboot enabled' in red letters. Through adb I was able to run TWRP. I flashed boot image and restore image.
When I reboot, it only gets to the LG logo screen, with 'bootloader unlocked' in the top left. It goes no further. I cannot powerdown. I have to remove the battery. I'm stuck. The computer isn't seeing the device at all now no matter what I do. How bad did I screw the pooch? Can anything be done or am I screwed?
Please help! Someone!
You might be able to get into recovery following the instructions in this thread so you can flash the zip recovery:
Getting into Recovery:
http://forum.xda-developers.com/lg-v10/help/booting-recovery-t3240305 (Post #2)
The Zip file:
http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170
mbnin32 said:
You might be able to get into recovery following the instructions in this thread so you can flash the zip recovery:
Getting into Recovery:
http://forum.xda-developers.com/lg-v10/help/booting-recovery-t3240305 (Post #2)
The Zip file:
http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170
Click to expand...
Click to collapse
I wish that worked. It was the first thing I tried. Also tried holding power and up volume as well as holding volume while plugging in USB [which brought me to a firmware update screen] but still no luck.
FuDog said:
I flashed TWRP and the superSU. My phone kept looping to 'fastboot enabled' in red letters. Through adb I was able to run TWRP. I flashed boot image and restore image.
When I reboot, it only gets to the LG logo screen, with 'bootloader unlocked' in the top left. It goes no further. I cannot powerdown. I have to remove the battery. I'm stuck. The computer isn't seeing the device at all now no matter what I do. How bad did I screw the pooch? Can anything be done or am I screwed?
Please help! Someone!
Click to expand...
Click to collapse
Try this @KAsp3rd fixed a similar, if not identical problem.
http://forum.xda-developers.com/showthread.php?p=63688728
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
To get into recovery ftom the hardware side you have to press the power and volume down together until very start of Lg logo release power while still holding volume down then press power again. You have to be quick
FuDog said:
I flashed TWRP and the superSU. My phone kept looping to 'fastboot enabled' in red letters. Through adb I was able to run TWRP. I flashed boot image and restore image.
When I reboot, it only gets to the LG logo screen, with 'bootloader unlocked' in the top left. It goes no further. I cannot powerdown. I have to remove the battery. I'm stuck. The computer isn't seeing the device at all now no matter what I do. How bad did I screw the pooch? Can anything be done or am I screwed?
Please help! Someone!
Click to expand...
Click to collapse
Follow the thread that Warrior1975 posted. I had almost the exact same problem & I was able to fix it
Just make sure you have the LG G4 drivers installed.
Warrior1975 said:
Try this @KAsp3rd fixed a similar, if not identical problem.
http://forum.xda-developers.com/showthread.php?p=63688728
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Thanks. This got back to where I can flash again. Thanks for sharing the link!
Now I was able to flash the boot.IMG and stock_recovery.IMG files but unable to flash system.IMG. also, even though I flashed TWRP, I can't open it. Power + down volume just gets me to LG logo screen and can do nothing from there. Or, holding down volume and plug in USB cable brings me to fastboot screen. From there, with fastboot I can see the device. I can reboot-bootloader. But cannot flash system.IMG. I have no clue from here.
Hold power and volume down when LG pops up let go of volume but not power then press it down again it will sari your erase your phone but choose it of you have twrp it will take you there.
Dozenboy0012 said:
Hold power and volume down when LG pops up let go of volume but not power then press it down again it will sari your erase your phone but choose it of you have twrp it will take you there.
Click to expand...
Click to collapse
When I do that, it still hangs at the logo screen. I try to adb sideload v10_stock.zip and get null error for the device even though the device is there...
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
39d74068 fastboot
C:\Program Files\Minimal ADB and Fastboot>adb sideload v10_stock.zip
loading: 'v10_stock.zip'
error: device '(null)' not found
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
39d74068 fastboot
FuDog said:
When I do that, it still hangs at the logo screen. I try to adb sideload v10_stock.zip and get null error for the device even though the device is there...
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
39d74068 fastboot
C:\Program Files\Minimal ADB and Fastboot>adb sideload v10_stock.zip
loading: 'v10_stock.zip'
error: device '(null)' not found
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
39d74068 fastboot
Click to expand...
Click to collapse
1) Hold the POWER and the VOL DOWN button until the LG logo appears
2) Quickly release and repress the POWER button and hold both buttons down until another menu pops up.
So you're basically pressing the POWER button twice. You never let go of the VOL DOWN button.
HOLD POWER+VOL DOWN
Repress POWER BUTTON when LG logo appears.
No my bad its the opposite let go of power when you see LG logo then press down again not volume sorry for confusion I just tried it and took me to recovery the way I said it should. That will take you to twrp if you have it installed.
FuDog said:
When I do that, it still hangs at the logo screen. I try to adb sideload v10_stock.zip and get null error for the device even though the device is there...
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
39d74068 fastboot
C:\Program Files\Minimal ADB and Fastboot>adb sideload v10_stock.zip
loading: 'v10_stock.zip'
error: device '(null)' not found
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
39d74068 fastboot
Click to expand...
Click to collapse
Try adb devices while in TWRP also while in twrp you need to go to advanced then sideload. If fastboot can see the device then adb cannot and vise versa . If you cannot get into twrp then fastboot boot twrp-2.7.8.1_h901.img
Sent from my LG-H901 using Tapatalk
Related
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
KrisM22 said:
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
Click to expand...
Click to collapse
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
kuisma said:
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
Click to expand...
Click to collapse
Thanks! Please pardon my ignorance... I did:
Code:
adb devices
pause
adb reboot-bootloader
pause
fastboot reboot
After adb reboot-bootloader my phone changed from the recovery screen to the white tmo logo screen and hung.
fastboot reboot still says waiting for device...
EDIT Okay, I think I've figured out that, from power off, volup+power=recovery screen , and voldn+power=fastboot screen(white with tmo logo).
But I can't do anything from that fastboot screen. The computer recognizes it when I USB plug it, but it still says waiting for device.
EDIT: It appears I have a driver for adb, but no driver for fastboot, or just plugging the powered off phone in to usb.
fixed.
<deleted>
I'm having some issues with this device connecting to ADB and I need to flash a different HBOOT so I dont get the error message on boot up. Because of said issue I cant flash a newer HBOOT version to my device via ADB. Is there another way that you can flash other than ADB? I know on previous HTC devices you were able to flash it from the bootloader itself if I remember correctly. Any ideas? Thanks.
Place the hboot in a zip with the android-info.txt file, in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
Code:
fastboot oem rebootRUU
(this puts the device in RUU mode)
Code:
fastboot flash zip hboot.zip
(this flashes the hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Code:
fastboot reboot-bootloader
(this reboots the device to bootloader)
santod040 said:
Place the hboot in a zip with the android-info.txt file, in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
Code:
fastboot oem rebootRUU
(this puts the device in RUU mode)
Code:
fastboot flash zip hboot.zip
(this flashes the hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Code:
fastboot reboot-bootloader
(this reboots the device to bootloader)
Click to expand...
Click to collapse
Thank you for the response, maybe I wasn't clear enough. I cannot use ADB from my computer AT ALL with this device. It recognizes other devices and shows them when I do adb devices but on the DNA it shows as offline and commands do not work because of that.
spincredible said:
Thank you for the response, maybe I wasn't clear enough. I cannot use ADB from my computer AT ALL with this device. It recognizes other devices and shows them when I do adb devices but on the DNA it shows as offline and commands do not work because of that.
Click to expand...
Click to collapse
what devices does it show?
thayl0 said:
what devices does it show?
Click to expand...
Click to collapse
This is what it shows in ADB:
List of devices attached
FA34GSXXXXXX offline (shows full device but was told by somebody in the past leave most of that info out.)
I know that its DNA related as ADB works just fine on my Gnex without issue.
Are you using Windows 8? There is no HTC drivers for windows 8 that will work. You must use a different windows version or dual boot with Linux.
If you are on a compatible version of windows, try reinstalling the drivers.
Sent from my DNA using my mind.
I'm using Windows 7
Sent from my VS980 4G using Tapatalk
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
I just waited 360 hours and unlocked a new Mi8 dipper as I have done with 5 Xiaomi phones previously. Everything looks normal. MiUI v10 says it is unlocked. With USB debugging activated the device code shows up with the 'adb devices' command. However when it comes to actually modifying the bootloader in Fastboot mode things look very locked in place. In the terminal console 'abd devices' command shows no devices. Similarly when trying to load TWRP with 'fastboot flash recovery TWRP. img' command it searches to find no device and ends with a fault. I have tried with 3 different USB-C cables on three different PC's. Two with Windows 10 with ADB tools and another on current ArchLinux with 4.20 kernel and ADB tools.
Incidentally, my wife has an untouched and therefore unlocked Pocophone F1. It does the same thing as above.
Has anyone heard of such a tbing? Is it possible that Xiaomi thinks this phone has been unlocked when in fact the bootloader is still locked?
As far as a fix goes,the unlock tool says its locked and won't try again to unlock it. This would be utterly painful were it not for Lawnchair launcher coming to the user experience rescue.
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
khanhdx said:
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
Click to expand...
Click to collapse
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
p-we said:
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
Click to expand...
Click to collapse
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
khanhdx said:
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
Click to expand...
Click to collapse
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
p-we said:
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
Click to expand...
Click to collapse
I never face any case like this. So maybe i can help you.
Try install different version of TWRP maybe can help..
ShafiX94 said:
Try install different version of TWRP maybe can help..
Click to expand...
Click to collapse
Very strange but I followed your steps on another PC in exactly the same way and now it has flashed TWRP successfully. It did require using blue USB3 port
Thank-you! :good:
Glade to hear you solved it.
For the record: I had the exact same problem as yours. If I recall correctly, the only thing I had to do was to rename the recovery file to: recovery.img then wait a minute or so. Which is strange, but worked.
First tried to boot Pitchblack recovery when it succeeded then tried it with TWRP (recovery.img).
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
p-we said:
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
Click to expand...
Click to collapse
I am glad that you sorted your issue.
But I can assure you that the issue was strictly caused by your PC. It truly should not matter which USB port you use. We have 3 Mi8 in our house and I have unlocked 2 of them using an older laptop with a broken usb 3.0 port.
For the benefit of others who may experience this issue.
Always. remove peripheral devices from the PC such as an external hard drive, when perform tasks such as unlocking the bootloader or unbricking a phone.
Windows should be up to date and I can tell you that professionally, we absolutely require that people temporarily disable windows defender and antivirus when attempting to resolve these kinds of issues, as you are indeed affecting the bootloader of the device.
Windows antivirus will often remove files that it miscategorises as a virus. In example, if you attempt to download and install the All In One Tool, windows defender will neuter the software 90% of the time.
I have a Moto G Play 2021 (XT2093-4) (another one), that I made a mistake to relock the bootloader after I had it unlocked. I don't have access to the OS on the phone anymore. Previously I had the treble floss installed on it. I don't have TWRP installed. The only thing I have access to is fastboot. I realise I might have completely bricked this phone but I thought I ask here to see if there is any way to unlock the OEM again just using the fastboot.
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
strumcat said:
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
Click to expand...
Click to collapse
Thanks, but I think my phone is completely messed up now. If you can believe it, I can't even get to recovery mode. I can get to fastboot and then find the recovery mode and click to go to it but then it just starts the fastboot again. I'm basically stuck in fastboot forever. It's just weird cause there's nothing wrong with the hardware. Thanks again.
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
strumcat said:
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
Click to expand...
Click to collapse
Sorry for the really late reply. I tried what you said, but it fails right at the (fastboot flash partition gpt.bin) command and the output I get is:
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
It keeps saying flash permission denied. I have another exact same phone with an unlocked bootloader and I did the same on that one and I was able to flash a stock ROM to it. I've tried every RETCA and RETUS on this site: https://mirrors.lolinet.com/firmware/motorola/guamna/official/ but it fails with the same error. I'm going to try all the rest later but it's a lot to download for now.
Thanks again for the help!