Well long story short, my G2 is semi-bricked, and i dont think i have CWM on it, but i still can get to bootloader/fastboot. But the problem is, i cant flash or do ANYTHING! when i try to use adb (example: adb devices) on a command prompt, it doesnt detect my G2 HOWEVER when i use fastboot and on the command prompt i use (fastboot devices) it detects it. and i understand that fastboot can flash boot, recovery, system etc. but when i try to flash, it gives me "FAILED <remote: signature verify fail>"
I've been working on my G2 for the past weeks already and im still stuck please help!
Related
Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread
Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery <3e>
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance
Nazneen said:
Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance
Click to expand...
Click to collapse
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)
pradeeppk said:
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)
Click to expand...
Click to collapse
it is not "recoveryimage". I just used it for this question. I tried with many files. So, I gave the name of the file and used the command and I got the success message also in CLI saying "Okay" and finished. But no file made any difference to device.
I had a pass code to unlock my screen. Two times I was able to get the screen (Other times it become dark after loading M) and it required the authentication code I gave to enter unlock screen. and I was filled with errors showing continuously "unfortunately not loaded 'system files' ". I suspect that whether the flash worked properly because it was asking for the screen unlock code.
So, I've almost bricked a moto g by trying to flash the stock firmware again, I am able to access the bootloader and the recovery, but the device doesn't boot up. Also, when I try to flash a new ROM I get some warnings that say "unable to mount /data" and then I it fails the installation and I get "unable to mount storage".
First I tried manually flashing the firmware from this post: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and that's when the phone got stuck.
Then I tried using this script: http://forum.xda-developers.com/showthread.php?t=2646415 but it still doesn't boot up, and I get an error during the flash of motoboot.img, everything else "flashes properly".
I'm pretty sure that there is a way to solve this, since I can still use fastboot commands and adb through recovery. Please help.
Edit: I just solved it. Looks like I wasn't flashing with "mfastboot" but instead with just the "fastboot" command, now it works perfectly
Hello everyone,
after unlocking my bootloader (on a Realme 5 Pro) to install TWRP and custom ROM, I am now stuck at trying to make fastboot do anything.
No matter which fastboot command I try, the phone won't execute it. I instantly get a "FAILED" and "(No error)" returned and the phone exits fastboot, showing some logo with a chinese message, as well as "press any key to shutdown" in the top left corner.
The only excpetions to that behaviour:
1. "fastboot devices" works as expected and recognizes the phone.
2. "fastboot boot [path to TWRP .img file]" sometimes gets stuck at "downloading boot.img..." indefinitely, sometimes it fails like all the other commands
3. "fastboot flash recovery [path to TWRP .img file]" gives an instant "FAILED", but the error message is "requested download size is more than max allowed"
I've tried re-locking and unlocking the bootloader, when unlocked both colorOS and fastboot recognize the bootloader as being unlocked.
I have no clue what to try at this point, hopefully someone can help me out?
Same problem here.
Mine is Realme 3 pro with the new version of realme UI, RMX1851, C.04, I have unlocked bootloader without downgrading it to color os 6, but now I cannot flash twrp in my device. After going into fastboot mode, after applying the commands, it says "FAILED" (remote: GetVar variable not found) and sometimes directly "ERROR"
The fix was an incredibly easy one, but I only found it/got the idea through a lot of googling... simply used a different PC (that I never used adb and fastboot with before), let windows search for drivers online, and BAM, it works!
Hopefully this will help someone in the future.
If you don't have more than one PC, I guess the best bet would be uninstalling all adb and fastboot related drivers.
I was test installing a ROM and then went to wipe my phone for another test run. However when I formatted the phone I got a ton of errors. Trying to reformat or wipe the phone results in the same errors (or looks like it at least)
Here's the last one in an incredibly long list (takes two minutes to scroll through): Error opening: '/data/ssh/OFJF8xpsY7U8SodJ9qcy6B' (Operation not permitted)
Now I'm kind of stuck and don't know what to do. I can't install a new ROM or anything really through recovery...I'm kind of stuck.
Any advice would be appreciated.
I've tried going into fastboot, to try installing a different recovery, but while the phone screen is on and I'm assuming in fastboot, if I type "fastboot devices" into the terminal, I don't get any output. The weird thing is I can go into fastboot mode via the terminal (so adb reboot bootloader)
But immediately after executing that command, if I type in fastboot devices...nothing