Related
Last night I tried to flash CM 11 through TWRP. I wiped factory and it failed. This morning I rebooted and no sim card or sd card could be found. I went to fastboot, tried to unroot back to stock and now my phone is stuck on boot loop. I can still boot into twrp but now my backup is missing and its not recognizing the sd. Can anyone help?
there's an sd card slot?!?
dicecuber said:
there's an sd card slot?!?
Click to expand...
Click to collapse
No, just the internal sd.
is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701
Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk
jj14 said:
is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Thanks, trying this now.
jj14 said:
is it not letting you flash the stock image?
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
It's saying fastboot is not a recognized as an internal or external command
FuMMoD said:
Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Where are these stickies at? I'm not finding one in either development forum.
You skipped a step somewhere
Which method are you using? If you are using method 2, you have to set the path (or change directory) - depending on where you installed abd/fastboot to.
Top in general and top in question&answer forum.
Sent from my Nexus 5 using Tapatalk
FuMMoD said:
Have you tried reading the sticky threads that tell you how to unbrick the device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Was it necessary to be rude? Would it have been more helpful to provide a link?
Engineer4life said:
It's saying fastboot is not a recognized as an internal or external command
Click to expand...
Click to collapse
Engineer4life said:
Where are these stickies at? I'm not finding one in either development forum.
Click to expand...
Click to collapse
You need to have adb and fastboot .exe's in the same directory as the factory images(assuming you're using Windows). Here's a link to a guide. You're definitely not bricked, just some problems with TWRP right now. http://forum.xda-developers.com/showthread.php?t=2513701
i would also suggest you to try to use some toolkit and bring it back to factory setting and then re root it...
housry23 said:
Was it necessary to be rude? Would it have been more helpful to provide a link?
You need to have adb and fastboot .exe's in the same directory as the factory images(assuming you're using Windows). Here's a link to a guide. You're definitely not bricked, just some problems with TWRP right now. http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
I went through the steps of adding the different drives. Downloaded SDK, saved to C:/ and tried to run fastboot to flash image. It keeps telling me fastboot is not recognized. Do you know of any other methods to flash a stock image. I cant even access my internal sd through TWRP, it's not recognized.
Engineer4life said:
I went through the steps of adding the different drives. Downloaded SDK, saved to C:/ and tried to run fastboot to flash image. It keeps telling me fastboot is not recognized. Do you know of any other methods to flash a stock image. I cant even access my internal sd through TWRP, it's not recognized.
Click to expand...
Click to collapse
You need to open a command prompt in the same directory as the fastboot executable. There are a million tutorials on exactly how to set up your adb/fastboot properly. Even Google provides the instructions on the same page you download the factory images. It isn't hard to do so
Sent from my Nexus 5
Pirateghost said:
You need to open a command prompt in the same directory as the fastboot executable. There are a million tutorials on exactly how to set up your adb/fastboot properly. Even Google provides the instructions on the same page you download the factory images. It isn't hard to do so
Sent from my Nexus 5
Click to expand...
Click to collapse
I've followed every step from this link
http://forum.xda-developers.com/showthread.php?t=2513701
I created and named the file image-hammerhead-krt16m and saved to C:/
the folder contains
android-info
boot.img
bootloader.img
cache.img
flash-all
flash-all.sh
flash-base.sh
image-hammerhead-krt16m..zip
radio.img
recovery.img
systerm.img
userdata.img
I've tried executing the command "fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img" from C:/android-adb/. It keeps giving me error: cannot open 'C:/image-hammerhead-krt16m/bootloader.img'
Engineer4life said:
I've followed every step from this link
http://forum.xda-developers.com/showthread.php?t=2513701
I created and named the file image-hammerhead-krt16m and saved to C:/
the folder contains
android-info
boot.img
bootloader.img
cache.img
flash-all
flash-all.sh
flash-base.sh
image-hammerhead-krt16m..zip
radio.img
recovery.img
systerm.img
userdata.img
I've tried executing the command "fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img" from C:/android-adb/. It keeps giving me error: cannot open 'C:/image-hammerhead-krt16m/bootloader.img'
Click to expand...
Click to collapse
You're using the wrong slashes. File directories are C:\file\goes\here, not C:/file/goes/here
bilago said:
You're using the wrong slashes. File directories are C:\file\goes\here, not C:/file/goes/here
Click to expand...
Click to collapse
Sorry, I used the right slashed in cmd and it's the same error
Engineer4life said:
Sorry, I used the right slashed in cmd and it's the same error
Click to expand...
Click to collapse
try making a simple folder . Move all the files from this directory to C:\nexus5\ .
open a command prompt and type this:
Code:
pushd c:\nexus5
then type
Code:
fastboot flash bootloader bootloader.img
what is the results
open command prompt from start menu. on mine, it starts me at
Code:
C:\Documents and Settings\Users\Austin
Use the command "cd.." to back up until you're at C:\
From there, type
Code:
cd image-hammerhead-krt16m
You should be at that directory now. and it'll say
Code:
C:\image-hammerhead-krt16m
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
without having to try and navigate to them every time. This worked for me. If you have adb drivers installed correctly and the "adb version" and "fastboot devices" command both work, you're good.
EDIT : Just as a heads up, the last command "fastboot erase cache" messed up something on mine. It wouldn't hold APNs or connect to any network, so I had to run fastboot flash cache cache.img
Synyster06Gates said:
open command prompt from start menu. on mine, it starts me at
Code:
C:\Documents and Settings\Users\Austin
Use the command "cd.." to back up until you're at C:\
From there, type
Code:
cd image-hammerhead-krt16m
Click to expand...
Click to collapse
Its a lot faster and efficient to just type
Code:
pushd c:\image-hammerhead-krt16m
Your method will not work if the user has their documents folder on another partition, which is a smart way to set up your computer.
Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon
Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a
Bear with me: Right now my nexus is stuck in a bootloop. My nexus had been partially rooted, everytime i went to download the OTA 5.0.1. update it would just take me to TWRP, and i didn't know what to do with that. So I finally tried to fully root the phone, and also use TWRP to install the OTA update. Now I'm stuck, I've tried wiping the cache/factory reset. How do I got about flashing it back to stock without losing all my data?
(apologies for the title, I thought originally that I had killed mtp and adb, but I figured out how to get them back just after posting)
Thanks!
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Ben36 said:
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Click to expand...
Click to collapse
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
The reason I say read the guides is simply it saves me or anyone else typing out a massive guide that already exists in many places.
If you're looping then something is more than likely wrong with the system not the data. So flashing just the system will keep your data safe (as long as you flash the same android version as you previously had, lollipop or kitkat)
You need to be in the bootloader not recovery and use the command fastboot flash system system.img
Google img's are here - https://developers.google.com/android/nexus/images
(just keep unzipping until you find the individual img files)
photobumm said:
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
Click to expand...
Click to collapse
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
_MetalHead_ said:
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
Click to expand...
Click to collapse
So I have adb and fastboot running. And I changed the flash-all.bat file. However, I don't understand what I do now? I downloaded the Hammerhead zip and it has a bunch of things in it. Which files do I put into the adb/fastboot folder and how do I then flash them?
In the hammerhead file it lists the bootloader, flash-all, radio and then a zip file "image-hammerhead...". What files am I using and what is the code that I input? Is this the same sa flashing a rom?
I also tried placing the system.img in the adb folder, and then using the
Code:
fastboot flash system system.img
but it gives me an error "cannot load 'system.img'
So now my issue is I get a "error: could not load 'system.img'. after running
Code:
fastboot flash system system.img [code/] . I also tried with boot.img. Same error.
I ran the "flash all" script, by accident, a screenshot of the terminal is attached.. I'm still stuck in a the boot loop, however, and if try to enter recovery mode an android lying down with a red triangle is present. The above "error: could not load..." is still present.
Create a folder and put fastboot in it.
So you unzipped the stock image. You said you have some images in the folder and a zip image.
Unzip that second zip.
There you will find the rest of the images you need.
Now take the recovery, bootloader, system, userdata, cache, and radio images and move them into the folder which you created for fastboot.
Rename the bootloader image to bootloader. img
Now when looking at that open folder containing all the images and fastboot hold down shift and left click and select "open command promt from window"
Type
/fastboot erase bootloader
/fastboot flash bootloader bootloader.img
/fastboot reboot-bootloader
/fastboot erase recovery
/fastboot flash recovery recovery.img
/fastboot erase radio
/fastboot flash radio radio.img
Repeat for the rest of the image files
Finally type /fastboot reboot
Profit.
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
P. S. Make sure your phone is booted in fastboot mode first.
Oh and that android is stock recovery
U fixed it?
So for some reason I still kept getting that error. I ended up restoring to stock using the nexus root toolkit. So it all worked out in the end.
Hi all.
I have searched the forum for solution to my problem but can't seem to find it.
When trying to flash 5.1 I get an error
After,I try to flash all .img files manually. All flash normal except system.img
I searched forums, used Wugs tool, tried on different PC's (Windows 8.1 & Windows 7) tried with different fastboot versions but no result.
Older versions flash normal(5.0.1, 4.4.4, etc..)
Any suggestions?
How much ram the PCs have?
One has 8gb ram installed,another one has 16gb
arsen4oo said:
One has 8gb ram installed,another one has 16gb
Click to expand...
Click to collapse
Strange...
Can you pack the adbs and fastboots to a zip or rar and upload it to somewhere or give me a link which adb and fastboot you use. I am going to try flash 5.1 in 30 minutes.
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
arsen4oo said:
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
Click to expand...
Click to collapse
Using your binaries it flashed fine, I got no errors.
My specs: Windows 8.1 Pro 8GB ram.
What is different with my setup about ram management is that since I have an SSD as drive C I moved the pagefile.sys to my HDD.
I also have Microsoft Visual C++ 2008, 2010, 2012 redistributables installed. I have no idea if that counts
I don't think problem is caused by pagefile.
But seems many people have this issue when flashing 5.1
Flashing from ubuntu is an alternative solution..
I have no idea what the issue is but here is how I got round exactly the same error message on my Windows 7 machine.
Create a new local user (with admin rights) and then reboot your machine. Log in with that user and close any applications that try to auto-start. Then try the batch file and it should now work.
I think it must be related to memory/open applications. I have loads of stuff open in the background, i.e. in the systray, with my standard login. This new user had nothing. Using this user after a reboot seems to do the trick!
Try to download the nexus image again. It might be corrupted or extract it again using 7zip. Just flashed mine a while ago using "minimal adb and fastboot" on windows 7 x64 with 2gb of RAM. Machines doesn't have anything to do with adb flashing. It's the file itself or the adb drivers.
Edit: I see you've already sorted this out via ubunta machine. Good for you.
I had the same issue last night too. I downloaded the latest nexus USB drivers and the flash completed successfully.
Had the same issue. Spent all night unbricking my phone. One of the partitions didn't flash right and i left my phone over night and it still didn't boot up. got 2 hours of sleep.
Kitkat flashed fine though.
So what i did. im using minimal adb fastboot
1) flash 4.4.4 images
2) extract ALL 5.1 image files (boot, system, etc) into the minimal adb fastboot folder C:\\program files etc etc
3) flash each item manuall
-fastboot flash bootloader bootloadername.img
-fastboot flash radio radioname.img
-then do the same with boot, radio, system, userdata, cache. (fastboot flash "partition" "name".img) so if youre flashing boot, then boot boot.img
this should boot up just fine. 2-5 minutes tops.
Manual flashing fixes it
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
BorgKing said:
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
yep you got it right :good:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Sanjay Varma said:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Click to expand...
Click to collapse
lol i got the idea from the same vid. Just ive flashed partitions manually before.
russian392 said:
lol i got the idea from the same vid. Just ive flashed partitions manually before.
Click to expand...
Click to collapse
lolz - though he is explaining well, I did mistakes as the commands and file names identically followed by each other
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!