Related
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.
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
Hello guys
I flashed my Moto G XT1033 (1st 2013) with GPE 4.4.4 a long time ago. I used to have TWRP installed just in case. Last weekend I decide do download a CM ROM of Lollipop (5.1) and just installed it. Worked like a charm.
Later that day when I got home, Android itself started update process from Motorola! The progressbar was showing and never ended. Suddenly the phone powers off, never coming back.
Doing a quick research I was able to turn it on again to the bootloader, who says:
"Fastboot reason: Failed do initialize partition table"
Since then, I've tried every sort of methods to install ANYTHING on this phone, as for say:
- Boot loader seems locked again, as I see the message "Device is LOCKED. Status Code: 0"
- When trying "fastboot oem get_unlock_data" I get "Could not get unlock data"
- Trying to use a previous key that I have to unlock returned "fastboot oem unlock disabled!"
- Trying to flash partition with many gpt.bin files (from different versions), seems useless always returning "Pre-flash validation failed FAILED Remote Failure" and on the phone is says "version downgraded for primary_gpt"
It looks like I'm on a real trouble in here, since I cannot flash anything to the phone, or even unlock the bootloader.
Any help would be appreciated.
Have you tried following the instructions here?:
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
aha360 said:
Have you tried following the instructions here?:
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
Click to expand...
Click to collapse
Yes, everything works fine until step 15. These are actually the instructions I used to bring the phone "to life" again. All the after steps who tries to flash files to the phone, end up as "remote failure".
Success
aha360 said:
Have you tried following the instructions here?:
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
Click to expand...
Click to collapse
Fortunately I was able to completely restore my MotoG 2013 following the instructions from this post:
https://forum.xda-developers.com/showthread.php?t=2623587&page=6
It's noticeble that:
- I MUST flash mototboot.img FIRST because this unlocks the bootloader
- This ALLOWS do flash gpt.bin
- Then you should flash AGAIN the motoboot.img
- And go ahead flashing the other files --- OR --- flash a Custom recovery (TWRP in my case) and use sideload to load your prefered custom ROM.
Thanks to everyone
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.
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!