Related
Hey,
I'm new to all of this so I really don't know what I'm doing wrong.
I got the normal Moto G running on 4.4.4, unlocked bootloader and rooted.
I've read that if no system files are changed I can just normally update the phone. So I flashed stock recovery (I had CWM before) using MotoTool AiO. But when I want to enter recovery it just gives me the "No Command." screen.
Only other thing I have different is, that I deleted some preinstalled Google and Motorola apps.
When I try to update the phone it just reboots after about 10 seconds telling me the update failed. (I always have to download the update again.)
I hope you guys can help me get to 5.0.2.
Thanks
You need certain Motorola Apps on your phone before the OTA update will work. Also, it's best to be unrooted.
Is there a way to restore the Motorola Apps? With the app i deleted them I can't, because I deleted them completely. (I didn't thought I would need them again.)
I'm not sure if you can find the proper APKs.
It may be easier to just flash back to stock and take the OTA update.
Okay, so I tried to get back a custom recovery so I can flash 4.4.4, but the problem is I still only get the no command screen when entering the recovery.
First I tried flashing CWM with the MotoTool AiO, but I still couldn't enter recovery, so I tried Philz Recovery, but I got the same problem there.
How the hell can I get a recovery, so I can flash 4.4.4?
You need to flash a completely stock ROM, including recovery.
You should download the stock 4.4.4 ROM for your phone and manually flash each partition using fastboot or mfasboot commands.
I tried it with help of this thread.
But it always says i can't find the command mfastboot and with the command fastboot it tells me it can't find the files and when I'm entering the folder it says it can't find the command. And even if I move the extracted files to the same folder (Where the fastboot.exe is) it tells me the files can't be found...
Like I said I'm new to all of this and little more detailed help would be appreciated
PS:
I still got the same .zip with the stock 4.4.4 I used to flash the first time (After that I deleted the system apps)
And in this .zip is an app folder with all the apks, so is there a fast way to just reinstall all of them?
Enable USB debugging and use the Moto AIO tool's Utilities tab to flash APKs to your phone.
http://forum.xda-developers.com/showthread.php?t=2635706
In MotoTool when I'm in fastboot it tells me device not found (Minimal ADB and Fastboot can find my device, and yestery MotoTool could find it, too. USB-Debugging is active.) and when the phone is normally stared in the cmd window it tells me [failed] ... (Can't read the rest, because the window closes instantly), but MotoTool says the installation worked
You need to be booted into ROM in order to use the APK installer.
When installing an APK, you may be prompted on the phone screen to allow your computer to have access to the phone.
Okay I managed to flash 4.4.4 and then I could update to 5.0.2, thanks for the help.
That's great. Glad I could be of some help.
Hi guys, I need help, because I can't relock my bootloader. I have Honor 8 L09C432
I was on Carbon ROM and I had TWRP installed, and I wanted to go back to stock ROM, so I followed a procedure that I found in a comment on some thread.
( This is a screenshot of a comment that I followed, if that means anything to you ) https://forum.xda-developers.com/attachment.php?attachmentid=4385584&stc=1&d=1515621906
I successfully returned to EMUI 5.0 and I'm currently on B360, and I wanted to update to B381. I got an OTA, I downloaded it, but installation failed, and that's, I guess, because the bootloader is unlocked.
I tried to lock the bootloader with some adb commands:
-adb devices ( my device would appear )
-adb reboot bootloader
-fastboot oem lock * Bootloader code *
and then I would get a message that says " FAILED (remote: Command not allowed) "
( Here's also a screenshot of that too ) https://dl.xda-developers.com/4/3/8/5/5/8/5/Capture2.PNG?key=L_OuO3DslYw7HJaIJW-mGw&ts=1515622403
I enabled USB Debugging and OEM unlock options in Developer options, but it still doesn't work...
If someone's knows why this is happening, or how can I update the phone without even locking, I would really appreciate that, thank you in advance, and If I didn't mention something that may be important, please tell me, so I can help you to help me
Use fastboot oem relock instead of lock.
Note that relocking isn't the same as locking, for that you'd have to flash something like MM via dload which automatically locks the bootloader. Some other official packages might work, too
Edit: Also you need to be in fastboot mode to actually use the fasboot commands. (power+vol. down)
I'm not sure if an unlocked bootloader should actually break the OTA but it's been a while.
You can just download the flashable (for TWRP) versions from FF ( the full ota mf-pv) and use those otherwise
Sent from my OnePlus5 using XDA Labs
I tried Fastboot oem relock too, but that also didn't work, and I was in fastboot mode when I typed in the commands. I don't have TWRP since I installed stock ROM ( EMUI ). I guess you are suggesting that I should downgrade to MM, so then the bootloader will be locked? Still, thank you for your time and help!
You don't need to lock the bootloader in order to take an update. However, you must have the stock boot and recovery .img loaded for it to work. Here is a link for instructions on how to do this. Keep in mind that my instructions only talk about extracting the boot.img, but in your case it is probably best to extract both the boot and recovery.img just like the video shows. Use the B360 firmware to extract the files from. This will ensure all of your partitions are stock and that will hopefully allow you to take the update OTA.
sic0048 said:
You don't need to lock the bootloader in order to take an update. However, you must have the stock boot and recovery .img loaded for it to work. Here is a link for instructions on how to do this. Keep in mind that my instructions only talk about extracting the boot.img, but in your case it is probably best to extract both the boot and recovery.img just like the video shows. Use the B360 firmware to extract the files from. This will ensure all of your partitions are stock and that will hopefully allow you to take the update OTA.
Click to expand...
Click to collapse
I'll try this method, thank you very much for your help and time :angel:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?
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!
Hi Guys,
I think I f...ed up big time...
My device was rooted and I tried to unroot/factory reset to give it to my wife. Since I'm now sitting here for about 5 hrs I try to summarize what I've been doing:
1. I started with trying to Flash a Factory Image with the ALL-IN-ONE Tool
- My Device was on the Latest Oxygen OS 11 and I just stupidly followed the instructions of the Tool and downloaded a OOS 10 based Stock Rom and flashed it (thats where my nightmare began)
- After I flashed the OOS 10 Stock Rom I was Stuck in at the Open Bootloader warning screen ("the boot loader is unlocked and software integrity cannot be guaranteed ...")
2. Since there is no (at least I couldn't find one for the life of me) OOS 11 fastboot stock ROM I tried to downgrade via an OOS Beta ROM I found in a downgrade guide
- That didn't work either and I ended up stuck at the same Screen
3. After some googling I came across this guide and tried to manually flash a none fastboot OOS 11 ROM by manually extracting all the images of the payload.bin
- After I extracted all the images I flashed them one by one as mentioned in the guide via fastboot and this ended up with
Qualcomm Crash Dump mode dm-verity device corrupted force dump Kernel restart
Click to expand...
Click to collapse
4. After that I panicked a little since I've never seen this error before and tried to Flash the OOS 10 based Stock rom via the ALL-IN-ONE Tool again
- This worked with no errors but now I'm still stuck in the "Open Bootloader warning Screen"
Since then I tried Step 4 with another OOS 11 none fastboot ROM but now I keep getting following error everytime I try to flash one of the extracted images via fastboot (which worked before):
FAILED (remote: Flashing is not allowed for Critical Partitions
Click to expand...
Click to collapse
I did some research, seems like this error indicates a locked bootloader which is wrong, bootloader is still unlocked.
Even if I try to unlock the bootloader again I get the reply that bootloader cannot be unlocked since it already is unlocked.
So now I'm stuck with a completely f...ed up device with absolutely no clue if and how I can fix this.
I really hope anyone of you guys can help ...
Apologies for the bad writing but it's 5 am and I'm tired and frustrated af ...
greetings from Germany.
Timo
EDIT: Oh and yes, I know about the MSM-Tool and tried it but I can't get it to work since my device is not showing. I followed this guide several time but nothing is happening and my device is not even showing in the device manager. Only time it shows in the device manager is when in fastboot mode.
Guys I finally did it.
I deinstalled all stale/inactive drivers and reinstalled the Qualcomm drivers and finally managed to get the MSM Tool up and running and revived the phone.