[HTC TUT] Fix error "writing 'recovery'...FAILED (remote: not allowed)" in Fastboot - Android General

[HTC TUT] Fix error "writing 'recovery'...FAILED (remote: not allowed)" in Fastboot
Hello all, I recently experienced a Fastboot error when I tried to flash the TWRP recovery for my device.
The error said,
Code:
writing 'recovery'...FAILED (remote: not allowed)
Today I will be showing you how I fixed that error.
First of all, you will need:
a fastboot firmware package for your device (which will be called firmware.zip for this tutorial).
your custom recovery of choice (which will be called customrecovery.img for this tutorial)
a Windows, Linux, or I *believe* Mac PC
Fastboot installed and working on said PC
knowledge of zipping/unzipping files and renaming files
Now, for the fun part!
PREPARING YOUR FILES
1. Create a new folder and name it something you will remember and recognize.
2. Open your firmware.zip. There should be a file called "android-info.txt", copy that and put it in the folder you just created.
3. Next, you will need to take your recovery. Rename it to "recovery.img" (all lowercase, btw), and put it in the folder with the android-info.txt.
4. Highlight the two files (android-info.txt and recovery.img) and zip them up as a .zip file. Name it whatever you'd like. For the purposes of this tutorial, I will be calling it "recov.zip"
FLASHING THE FILES
1. Put your device into Fastboot mode
2. Open cmd/terminal/etc. and cd to the folder with recov.zip.
3. in cmd/terminal, run the following command:
Code:
fastboot oem rebootRUU
4. now you should be on an HTC screen with "HTC" in pretty silver letters
5. run the following command:
Code:
fastboot flash zip recov.zip
(but with your zip name)
6. You should get a success message and you should be able to reboot in your custom recovery.
HAPPY FLASHING!
(if this tutorial helped you please thank this topic!)

Worked For Me
nuuits said:
Hello all, I recently experienced a Fastboot error when I tried to flash the TWRP recovery for my device.
The error said,
Code:
writing 'recovery'...FAILED (remote: not allowed)
Today I will be showing you how I fixed that error.
First of all, you will need:
a fastboot firmware package for your device (which will be called firmware.zip for this tutorial).
your custom recovery of choice (which will be called customrecovery.img for this tutorial)
a Windows, Linux, or I *believe* Mac PC
Fastboot installed and working on said PC
knowledge of zipping/unzipping files and renaming files
Now, for the fun part!
PREPARING YOUR FILES
1. Create a new folder and name it something you will remember and recognize.
2. Open your firmware.zip. There should be a file called "android-info.txt", copy that and put it in the folder you just created.
3. Next, you will need to take your recovery. Rename it to "recovery.img" (all lowercase, btw), and put it in the folder with the android-info.txt.
4. Highlight the two files (android-info.txt and recovery.img) and zip them up as a .zip file. Name it whatever you'd like. For the purposes of this tutorial, I will be calling it "recov.zip"
FLASHING THE FILES
1. Put your device into Fastboot mode
2. Open cmd/terminal/etc. and cd to the folder with recov.zip.
3. in cmd/terminal, run the following command:
Code:
fastboot oem rebootRUU
4. now you should be on an HTC screen with "HTC" in pretty silver letters
5. run the following command:
Code:
fastboot flash zip recov.zip
(but with your zip name)
6. You should get a success message and you should be able to reboot in your custom recovery.
HAPPY FLASHING!
(if this tutorial helped you please thank this topic!)
Click to expand...
Click to collapse
Thanks, this worked for me with HTC M8 updating TWRP

Hello,
You just saved me. I confirm it works. Actually, for me just entering "fastboot oem rebootRUU" did the trick, because here I could flash anything.

i get a android-info fail

So...
I bought a new phone and bricked it. There are a whole range of issues, but unless I can get over "writing 'recovery'...FAILED (remote: not allowed)", I have no hope of even attempting to fix the others.
Thing is, I didn't back up (first time playing with Android - I thought I'd made a backup but I found out it was 0bytes and deleted it...) and it seems to be quite rare (HTC E8 MEC__TL) and nobody has uploaded much for this specific variant. When you say "your firmware.zip.", I don't think I have a way to get this.
If I buy another of this phone from the same seller, will I be able to extract the files to make your fix? Will this be effected by me having changed (or at least tried to change) the CID and MID?
Thanks!

Related

need help flashing recovery

I went ahead and did the oem unlock but when I try and flash the recovery (or boot) image through fastboot using this:
C:\androidsdk\tools\fastboot flash recovery XXXXXXX.img
or
C:\androidsdk\tools\fastboot flash boot rootboot.img
I keep getting this error:
error: cannot load 'XXXXXXX.img'
I've trouble shooted all of the main things. ...my device is definitely attached. I have the recovery .img file in the same folder as fastboot (along with the 2 needed .dll files). I've also done stuff like re-install usb drivers, re-install sdk, I've oem unlocked 3 times.
I have a stock wifi xoom with 3.2
Here are the 2 main root guides I've been using
http://forum.xda-developers.com/showthread.php?t=1170760&highlight=how+to+root
http://forum.xda-developers.com/showthread.php?t=1242241&highlight=how+to+root
Thank you for your help
in cmd(assuming windows) type cd c:/•••••tools
your xoom should be in adb reboot bootloader
type fastboot flash recovery recovery.img
rename recovery file as recovery.img and place in tools/platformtools as the case may be.
sending this message from stock xoom.
awesome, thanks. What you told me was enough to show me what I was doing wrong.
In case someone else reads this later on I had to type
cd C:\androidsdk\tools ...hit enter
then it looked like this
C:\androidsdk\tools> ...and I then typed
fastboot flash recovery XXXX.img
earlier I also renamed the folder to androidSDK from android-sdk

Stuck on htc screen 'flashed wrong rom'

Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
[Solved] Thank you all for helping me through, I finally, I can made it. See the last post of the actually summary of my own journey.
Without all of your value input, I will never made it.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
At the first place, why and how did you flash an HTC HD rom to Desire S without even knowing it?! You should have know from the start that you should have taken precautions, and known that its an HTC HD. It should be PORTED first.
To answer,
Try flashing the recovery again on fastboot. Check my guides on how to on my sig (preferrably the second one). Then see if it works. If it did, flash the CORRECT rom.
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
imkr said:
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
Click to expand...
Click to collapse
What I'm trying to say is to flash the recovery again. 4ext recovery recommended. And start from there. Clear instructions were given on that thread on how to flash a recovery image via fastboot, and I believe I can't simplify it much further.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
Mate don't worry, it happened to me many times.see this thread to know how I got a solution.forum.xda-developers.com/showthread.php?t=1281688
I used nandroid backup but you can flash another ROM
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
After you get the phone in FASTBOOT mode, open the cmd window and type:
FASTBOOT FLASH RECOVERY c:\recovery.img
I find it very worrying that some one who can claim to have made this mistake many times is prepared to offer advice!
nandroid backups, you now see the importance of taking them
Swyped from my Desire S using XDA Premium
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Rapier said:
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Click to expand...
Click to collapse
It's working for me now, thanks for your clear instructions:
I've type up the exact process that I experienced here
1. Get 4EXT
2. Extract to C:
3. Find android-win-tools
4. SHIFT + Right click to open cmd from here
5. Type 'fastboot flash recovery C:\recovery.img', then appeared:
sending 'recovery'... OKAY (keep looking around 10mn), another command appeared
writing 'recovery'...OKAY
6. fastboot reboot-bootloader
DONE!

ROOT Nextbook Ares 8 with Windows

Update: When you flash the recovery and supersu files make sure to have the remove encryption file on sd card aswell and add it to the list and flash and if you hang at boot screen.. boot into recovery and wipe cache.. reboot.
WINDOWS USERS ONLY.... USE AT YOUR OWN RISK
Make sure you have the proper drivers and make sure you have a real good usb cable... This rar has the usb drivers and the files already in the folder just drop onto desktop and run cmd.exe
Files Needed: http://www.filedropper.com/nocturnaladbfastboot
http://www.filedropper.com/removeencryption
DO NOT FORMAT SYSTEM!!!!!!!!!!!!!
Make sure you are in bootloader or this will not work..
Key combo to get into bootloader or recovery via hard keys.
power off
volume up + power = recovery
volume down + power = bootloader
from bootloader you have several choices to boot, just pres volume down to choose, power to select.
1. To make sure you are connected run command (adb devices) enter
2. Once you see your device run command (adb reboot bootloader) Then..
3. Run command (fastboot boot boot.img) wait for downloading dialog...
4. Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure...
5. once the screen says okay on tablet.. push the vol down button until you see recovery mode and then push power to start twrp recovery..
6. Once in twrp flash SuperSU246.zip and recovery.zip remove_encryption.zip then reboot... you should have root on reboot:good:
Instructions
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
ahunter said:
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
run them just as there posted make sure all files on the sd card and you should be fine..
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
ahunter said:
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
Click to expand...
Click to collapse
Make sure you uninstall and reinstall the usb drivers in the folder and run the cmd from the folder and if still nothing try a new cable and usb port... when you run command adb devices do you see your listed as numbers and some letters?
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
ahunter said:
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
Click to expand...
Click to collapse
there is a problem after you boot into bootloader i had the same problem for days.. i just played with cables and drivers use the ones inside the folder they worked for me...
I'll keep trying. It has be the drivers.
I followed these directions to a T, but for some reason the device can not read the SD card while in recovery. Any clues as to why this is happening?
So I was online shopping for my first tablet when I came across this thread. . . It led me down to the local WALMART and I picked one up. I successfully completed the process, or so I thought. I went to reboot after flashing everything, and twrp says " no OS installed! Are you sure you want to reboot?"
What did I do wrong?
I have tried several times to download the remove encryption file must be a bad link or something. Is there another download site or can someone send to me plz
Nvm I ran it over with my car because I couldn't get the download link to work. If anyone wants it for parts send me a message. Its brand new only been used maybe 2 weeks. The most wear and tear on it was my Buick regal hitting it at about 45 mph in a pissed off rage. don't think all the insides are smashed tho. Possibly a good fixer upper
Is this fastboot and adb custom versions?
I have adb and fastboot in my path (runable from anywhere)..
ADB says the version release is the same number.
do I need to use your versions for the tablet?
http://www.filedropper.com/removeencryption
does not work, link changes to http://www.filedropper.com
and asks me to upload a file?
Link working sorry...
http://www.filedropper.com/roottwrpremoveencryption
TWRP 3.0
http://www.filedropper.com/twrp3recovery
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>fastboot flash recovery twrp_
recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15558 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.830s
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>
Copied the two zip files to both a 4gb fat32 formatted microsdhc
and internal storage via MTP to the device then ran ADB 1.0.32
and rebooted to bootloader. (adb finds device fine)
fastboot devices reported device number fastboot.
flashed TWRP in package you uploaded yesterday.
it says both internal and external cards are empty?
internal card has files that the manufacturer put there,
but TWRP can't see them?
What am I doing wrong?
Any ideas how to fix?
log says 'unable to find crypto file'
and it couldn't mount /data or /storage filesystems
>>>
installed TWRP3 that allowed the installs although it still
could not open /data. It did find the external card installed
from there.
I am guessing the forced encryption made /data unreadable.
hopefully now with the encryption removed the /data
partition will be readable.
>>>
I reran recovery to check and log now has no failures!!!
I'm guessing the changed boot.img fixed the issues it was having.
*smiles*
cant get files. takes me to a site to sign up. can you dropbox link them please?
I just won this tablet in a contest. Anyone have the remove_encryption.zip file? I managed to find all of the other required files but none of the links in this thread work anymore.
whats the problem with the links? site says free but wants me to pay. losing my head here, and it seems im not the only one
Bad filedropper links
Filedroper no links available, asks us to register and pay for stuff that's not there anymore
can you like put them on Google drive, SendSpace, DropBox, Mega.nz and/or ZippyShare

[ROOT] [SOLVED] flashing recovery twrp MOTOROLA MOTO 3rd 2015

I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???
leodom01 said:
I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???
Click to expand...
Click to collapse
First verify that you have debugging enabled from the developer options, second check that the recovery file is located in the folder plataform tools (Tools with which the flashing process is done).
Third, verify that you have the device drivers installed correctly.
If it does not work try to do root with kingroot (Look for the official page, download the same apk), the process is not difficult ... Clarify the device will restart repeatedly, at each restart reopen the application to continue with the process, it may work as it may not. (Do it at your own risk). If this method works follow the steps in this video to install TWRP recovery: https://www.youtube.com/watch?v=xwFC41d-7Yg
I think that for process of rooteo you can go ahead alone.
leodom01 said:
I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???
Click to expand...
Click to collapse
Your answer is here "error: cannot load 'twrp-osprey-3.0.2-r1.img': No error"... Everything is working perfectly, except there is no file by that name that fastboot can find, therefore it didn't do anything, thus no error. The problem is your TWRP img is in the wrong place or named incorrectly. Your problem is basic commands or file structure, not a problem with the phone or fastboot.
leodom01 said:
I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???
Click to expand...
Click to collapse
i guess the name of recovery is wrongly typed so rename the recovery in that folder to something simple like twrp.img take note of the extension as in windows the extension is hidden by default. hope it helps you.
---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------
Arcade said:
i guess the name of recovery is wrongly typed so rename the recovery in that folder to something simple like twrp.img take note of the extension as in windows the extension is hidden by default. hope it helps you.
Click to expand...
Click to collapse
Or also you then have to use the command
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Thank you! I did it in past too, but I wasn't working I tried again today and I worked, don't ask me why! Thank you anyway guys!

"Cannot load Android system" after failed update - HELP!

My Android phone (Motorola Edge) can no longer start properly after a failed system update. The message I get is: "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
I've tried restarting it in recovery mode which didn't work. I've read that I may be able to install some software via USB and rescue the system but I have no idea how that's done. I've looked at some different rescue software such as Rescue and Smart Assistant (which would only let me rescue the phone which will erase all data) and Dr.Fone but the reviews aren't convincing and the unofficial software programs generally don't support Motorola phones. Does anyone know how to fix my phone without losing my data?? Any help is much appreciated.
Also; I'm in no way a developer so I need everything explained to me like I'm 12 years old.
hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
[email protected] said:
hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
Thank you so much for your input. Unfortunately I can't make it work. When I type 'adb devices', I get this text:
List of devices attached
ZY227HQ2BX sideload
I've attached more info. Not sure if this has something to do with "USB debugging"?
all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)
What file is the system file in this folder?
[email protected] said:
all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)
Click to expand...
Click to collapse
Hi again, I've spent all weekend trying to figure it out but so far no luck.
I don't know where to find the system file in the folder I downloader (see attached photo in my reply above this). I also tried making a service-batfile with guidance from YouTube but it seems my phone is locked so it doesn't work.
well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.
[email protected] said:
well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.
Click to expand...
Click to collapse
I tried doing it but no success (I really want to keep my data). See attached photo
bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)
[email protected] said:
bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)
Click to expand...
Click to collapse
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?
SirOinksalot said:
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?
Click to expand...
Click to collapse
try some windows app to recover it.
sorry unocking will delete data
[email protected] said:
try some windows app to recover it.
sorry unocking will delete data
Click to expand...
Click to collapse
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry
SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
How did you resolve your issue ?
[email protected] said:
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry
Click to expand...
Click to collapse
Hello buddy,hope your exams are over and you passed them all with wonderful grades!
I am facving the similar problem and unable to find a solution.Would you mind having a look at this ? Thank you!

Categories

Resources