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.
Related
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
4SHR4F said:
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
Click to expand...
Click to collapse
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
how did you delete recovery?
cyanogen mod forum has a good wiki on fastboot.
buhohitr said:
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
4SHR4F said:
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
Click to expand...
Click to collapse
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
buhohitr said:
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
Click to expand...
Click to collapse
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
4SHR4F said:
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
Click to expand...
Click to collapse
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
buhohitr said:
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
Click to expand...
Click to collapse
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
4SHR4F said:
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
Click to expand...
Click to collapse
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
buhohitr said:
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
Click to expand...
Click to collapse
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
4SHR4F said:
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
Click to expand...
Click to collapse
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
buhohitr said:
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
Click to expand...
Click to collapse
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
H:\Users\Install user>
Also I would also like to point out it does not let me reboot after I write the files (using holding shift key and opening command prompt) as it freezes I think??? BEcause I can reboot from fastboot before I input writing flash recovery but after it wont allow don't know why?
4SHR4F said:
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
Click to expand...
Click to collapse
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
_that said:
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
Click to expand...
Click to collapse
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
4SHR4F said:
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
Click to expand...
Click to collapse
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
buhohitr said:
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
Click to expand...
Click to collapse
Same problem says its sent and that it is written but after if I try to reboot the tablet doesn't respond and cant go into recovery because of that error 0x00000000
All I want to do is get UBuntu and Clean ROM on my Tablet then no more modding
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
4SHR4F said:
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
Click to expand...
Click to collapse
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
buhohitr said:
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
Click to expand...
Click to collapse
What about install linux without root and from there send in the recovery that way will that work
4SHR4F said:
What about install linux without root and from there send in the recovery that way will that work
Click to expand...
Click to collapse
You can be the first one to try...it may or may not works, but the methods I provided proved by many that they worked.
Hi guys,
I've got an HTC Chacha unlocked bootloader S-ON. I just successfully rooted it yesterday and had CWM installed. Unfortunately, while I was browsing how to increase internal memory via youtube, I installed another CWM (SkinCWM) as his video told the viewers that it can work on any android phone.I even partitioned my SD card for it.
My problem is I cant go to Recovery. It just keeps saying CID Incorrect, Update Fail!
I know there are a lot of CID threads but I assume the problem came when I installed the SkinCWM (for galaxy Y).
Please help. Knowledge on this: Dependent on tutorials.
Thank you.
[A]
rltinio said:
Hi guys,
I've got an HTC Chacha unlocked bootloader S-ON. I just successfully rooted it yesterday and had CWM installed. Unfortunately, while I was browsing how to increase internal memory via youtube, I installed another CWM (SkinCWM) as his video told the viewers that it can work on any android phone.I even partitioned my SD card for it.
My problem is I cant go to Recovery. It just keeps saying CID Incorrect, Update Fail!
I know there are a lot of CID threads but I assume the problem came when I installed the SkinCWM (for galaxy Y).
Please help. Knowledge on this: Dependent on tutorials.
Thank you.
Click to expand...
Click to collapse
Connect your phone in fastboot-usb mode and run commend prompt in your pc(if you are using Windows). then go to fastboot.exe directory by typing:
Code:
cd X:\directory
now erase your recovery partition by typing :
Code:
fastboot erase your-partition-name
This trick must solve your problem.
Please press Thanks if you found this post useful
Click to expand...
Click to collapse
mortal19xx said:
Connect your phone in fastboot-usb mode and run commend prompt in your pc(if you are using Windows). then go to fastboot.exe directory by typing:
Code:
cd X:\directory
now erase your recovery partition by typing :
Code:
fastboot erase your-partition-name
This trick must solve your problem.
Click to expand...
Click to collapse
Thanks for the prompt reply. Please bear with me.
1. Im assuming fastboot on my phone's settings will be checked.
2. Will i find the fastboot.exe on my PC (in my case, on my c: fastboot)?
Thanks again.
[A]
rltinio said:
Thanks for the prompt reply. Please bear with me.
1. Im assuming fastboot on my phone's settings will be checked.
2. Will i find the fastboot.exe on my PC (in my case, on my c: fastboot)?
Thanks again.
Click to expand...
Click to collapse
At first you should download adb-fastboot toolkit to your computer.
Download it here : CLICK TO DOWNLOAD
Then extract it to your Windows drive.
Run Commend Prompt in your computer by typing CMD in RUN.(or anyway)
Type :
Code:
cd C:\Android
(C is your Windows drive, it could be D,E,etc.)
Now boot your phone on fastboot mode and connect it to PC and type :
Code:
fastboot erase <partition>
(you should type your recovery partition name instead of <partition>, it could be
Code:
fastboot erase recovery
etc.)
and you can follow this instruction if you have problem around ROOT : [Guide][S-OFF] How to root HTC Chacha (for S-OFF only)
Please press Thanks:good: if you found this post useful
Click to expand...
Click to collapse
mortal19xx said:
At first you should download adb-fastboot toolkit to your computer.
Download it here : CLICK TO DOWNLOAD
Then extract it to your Windows drive.
Run Commend Prompt in your computer by typing CMD in RUN.(or anyway)
Type :
Code:
cd C:\Android
(C is your Windows drive, it could be D,E,etc.)
Now boot your phone on fastboot mode and connect it to PC and type :
Code:
fastboot erase <partition>
(you should type your recovery partition name instead of <partition>, it could be
Code:
fastboot erase recovery
etc.)
and you can follow this instruction if you have problem around ROOT : [Guide][S-OFF] How to root HTC Chacha (for S-OFF only)
Click to expand...
Click to collapse
Thanks mortal. However, as a noob on this, i really dont know how to get the partition name to erase it.... Would a factory reset do the trick? or would it just be in the same scenario after factory reset?
mortal19xx said:
At first you should download adb-fastboot toolkit to your computer.
Download it here : CLICK TO DOWNLOAD
Then extract it to your Windows drive.
Run Commend Prompt in your computer by typing CMD in RUN.(or anyway)
Type :
Code:
cd C:\Android
(C is your Windows drive, it could be D,E,etc.)
Now boot your phone on fastboot mode and connect it to PC and type :
Code:
fastboot erase <partition>
(you should type your recovery partition name instead of <partition>, it could be
Code:
fastboot erase recovery
etc.)
and you can follow this instruction if you have problem around ROOT : [Guide][S-OFF] How to root HTC Chacha (for S-OFF only)
Click to expand...
Click to collapse
When I tried the command prompt. it just says <waiting for device> and stops there.
[A]
rltinio said:
When I tried the command prompt. it just says <waiting for device> and stops there.
Click to expand...
Click to collapse
you should dpwnload your phone driver.
mortal19xx said:
you should dpwnload your phone driver.
Click to expand...
Click to collapse
It's now working! I just pasted "su-2.3.6.1-ef-signed.zip" on my SD card and rebooted to bootloader. Now it works! Thank you!
...and now finding how to increase internal memory (again). :fingers-crossed:
Hi,
I have messed around with my rooted Moto G and edited build.props. I turned on my phone and a message came up saying "error system.ui has stopped"' this message kept repeating every time I pressed OK.
After failing to fix it, I went onto my recovery and wiped the storage, cache and dalvik. Obviously now when I turn on the phone it just stays on the boot image and nothing happens.I put the phone into fast boot by holding power and vol down, then tried to flash 4.4.2 Stock ROM to my phone but all CMD says is "waiting for device". I'm not sure what to do from here.
Can anyone help me at all? I've already posted before but no one seems to help me.
If you need any screenshots etc I will add them
Thanks,
Matt
@barky02
what are you using to try and install your stock rom? are you just in command prompt terminal or using a program?
anyway,,, your phone needs to be in fastboot mode to be able to run adb commands
hhp_211 said:
@barky02
what are you using to try and install your stock rom? are you just in command prompt terminal or using a program?
anyway,,, your phone needs to be in fastboot mode to be able to run adb commands
Click to expand...
Click to collapse
@hhp_211
@Martin3lli
I'm using CMD, and I was following this guide: http://forum.xda-developers.com/showthread.php?t=2542219
I am unsure how to put my phone into fastboot mode, can you show me how? I put the phone into fast boot by holding power and vol down, and thats how I tried to flash the ROM. all command prompt was saying was <waiting for device>
Thanks,
Matt
barky02 said:
I'm using CMD, and I was following this guide: http://forum.xda-developers.com/showthread.php?t=2542219
@hhp_211
I am unsure how to put my phone into fastboot mode, can you show me how?
Thanks,
Matt
Click to expand...
Click to collapse
When your phone is off, push volume down and power button simultaneously for a few seconds, then it should start fastboot. Plug in your USB cable and proceed with other steps as guide says.
Martin3lli said:
When your phone is off, push volume down and power button simultaneously for a few seconds, then it should start fastboot. Plug in your USB cable and proceed with other steps as guide says.
Click to expand...
Click to collapse
@Martin3lli
Sorry I misunderstood, I did put my phone into fastboot but it still didn't work, I updated my previous reply with the details
try this
I don't know if this will work, this is my threat. Hope it helps
http://forum.xda-developers.com/moto...t1032-t2814093
Saphire007 said:
I don't know if this will work, this is my threat. Hope it helps
http://forum.xda-developers.com/moto...t1032-t2814093
Click to expand...
Click to collapse
Thank youu :3
404 error? is it the right link?
I assume you are trying to run "flashall.bat"?
in the command prompt try this
adb kill-server
then type
adb start-server
then try running the commands...
I believe you are a full xt1028 Verizon phone?
I know what I do for 4.4.2 is using the file
CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip
un-zip [extract] that file,,,
then make sure you copy and paste from the "/windows" folder in the zip
fastboot.exe
AdbWinApi.dll
cAdbWinUsbApi.dll
into the main folder [where your .bat file is]
with phone connected to pc...
then open it up and double click on the .bat file
CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.bat
and it will do all the necessary work
.
hhp_211 said:
I assume you are trying to run "flashall.bat"?
in the command prompt try this
adb kill-server
then type
adb start-server
then try running the commands...
I believe you are a full xt1028 Verizon phone?
I know what I do for 4.4.2 is using the file
CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip
un-zip [extract] that file,,,
then make sure you copy and paste from the "/windows" folder in the zip
fastboot.exe
AdbWinApi.dll
cAdbWinUsbApi.dll
into the main folder [where your .bat file is]
with phone connected to pc...
then open it up and double click on the .bat file
CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.bat
and it will do all the necessary work
.
Click to expand...
Click to collapse
I have an english phone, none of the things you have said were in the tutorial, and the xml I am using doesn't come with any of those, only mfastboot.exe
I don't think my PC is recognising my Moto G properly. On the fastboot screen it says USB connected, but in my devices my phone is called "Fastboot Falcon S"
barky02 said:
I have an english phone, none of the things you have said were in the tutorial, and the xml I am using doesn't come with any of those, only mfastboot.exe
I don't think my PC is recognising my Moto G properly. On the fastboot screen it says USB connected, but in my devices my phone is called "Fastboot Falcon S"
Click to expand...
Click to collapse
Yes you have a Verizon Moto G Right [XT1028]? not a converted Boost Mobile [XT1031]?
what is the name of the zip file you have?
hhp_211 said:
Yes you have a Verizon Moto G Right [XT1028]? not a converted Boost Mobile [XT1031]?
what is the name of the zip file you have?
Click to expand...
Click to collapse
I have a T-Mobile Moto G XT1032
The Zip file name is: EE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF.xml
barky02 said:
I have a T-Mobile Moto G XT1032
The Zip file name is: EE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF.xml
Click to expand...
Click to collapse
Ahhh... I keep forgetting there are so freakin may versions...
can you show a screenshot of what files you have in there
also did you try the
in the command prompt try this
adb kill-server
then type
adb start-server
this will restart the adb session
Here is a another thread to restore stock
http://forum.xda-developers.com/showthread.php?t=2794271
Sent from my Moto G using XDA Free mobile app
hhp_211 said:
Ahhh... I keep forgetting there are so freakin may versions...
can you show a screenshot of what files you have in there
also did you try the
in the command prompt try this
adb kill-server
then type
adb start-server
this will restart the adb session
Click to expand...
Click to collapse
These are the files in the xml folder - mflashboot was the thing I added
Im not too brainy with cmd, at what time do I put adb kill-server in?
sorry
barky02 said:
Thank youu :3
404 error? is it the right link?
Click to expand...
Click to collapse
Sorry bro, my bad xs hope this works.
http://forum.xda-developers.com/moto-g/help/fix-bricked-xt1032-t2814093
barky02 said:
These are the files in the xml folder - mflashboot was the thing I added
Im not too brainy with cmd, at what time do I put adb kill-server in?
Click to expand...
Click to collapse
thanks
after reading some more up on mfastboot I don't believe you have to use the adb commands...
you should be able to use this file mfastboot.bat.txt as long as you have the mfastboot.exe on your pc
download it and move it into your "EE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF.xml" folder
then rename it to just mfastboot.bat
and doubleclick that
and follow along
don't worry if you see errors on your device screen, it's normal
this is the contents and the correct flashing order of the bat file
and are for that xml.zip that you have
edit:: edited to remove file and update below code to hopefully work
Code:
SET mfastboot=mfastboot.exe
%mfastboot% flash aboot emmc_appsboot.mbn
%mfastboot% flash partition gpt.bin
%mfastboot% flash motoboot motoboot.img
%mfastboot% flash logo logo.bin
%mfastboot% flash boot boot.img
%mfastboot% flash recovery recovery.img
%mfastboot% flash system system.img_sparsechunk.0
%mfastboot% flash system system.img_sparsechunk.1
%mfastboot% flash system system.img_sparsechunk.2
%mfastboot% flash modem NON-HLOS.bin
%mfastboot% erase modemst1
%mfastboot% erase modemst2
%mfastboot% flash fsg fsg.mbn
%mfastboot% erase cache
%mfastboot% erase userdata
hhp_211 said:
thanks
after reading some more up on mfastboot I don't believe you have to use the adb commands...
you should be able to use this file mfastboot.bat.txt as long as you have the mfastboot.exe on your pc
download it and move it into your "EE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF.xml" folder
then rename it to just mfastboot.bat
and doubleclick that
and follow along
don't worry if you see errors on your device screen, it's normal
this is the contents and the correct flashing order of the bat file
and are for that xml.zip that you have
Code:
SET mfastboot=mfastboot.exe
%mfastboot% flash aboot emmc_appsboot.mbn
%mfastboot% reboot-bootloader
%mfastboot% flash partition gpt.bin
%mfastboot% flash motoboot motoboot.img
%mfastboot% flash logo logo.bin
%mfastboot% flash boot boot.img
%mfastboot% flash recovery recovery.img
%mfastboot% flash system system.img_sparsechunk.0
%mfastboot% flash system system.img_sparsechunk.1
%mfastboot% flash system system.img_sparsechunk.2
%mfastboot% flash modem NON-HLOS.bin
%mfastboot% erase modemst1
%mfastboot% erase modemst2
%mfastboot% flash fsg fsg.mbn
%mfastboot% erase cache
%mfastboot% erase userdata
%mfastboot% reboot-bootloader
Click to expand...
Click to collapse
@hhp_211
I think this will work but I just need the pc to recognise the device, I have attached screenshots of what the device is coming up as. I have installed Motorola Device Manager, SDK tools and Google USB but it still won't be recognise.
I ran the .bat file but command prompt is still saying <waiting for device>
Thank you so much for your help, I think its nearly fixed
Matt
barky02 said:
@hhp_211
I think this will work but I just need the pc to recognise the device, I have attached screenshots of what the device is coming up as. I have installed Motorola Device Manager, SDK tools and Google USB but it still won't be recognise.
I ran the .bat file but command prompt is still saying <waiting for device>
Thank you so much for your help, I think its nearly fixed
Matt
Click to expand...
Click to collapse
@ barky02
have you also installed the
Moto G USB Drivers (WinXP/7 32Bit-64Bit)
http://forum.xda-developers.com/showthread.php?t=2550635
what os are you running on your pc?
.
hhp_211 said:
@ barky02
have you also installed the
Moto G USB Drivers (WinXP/7 32Bit-64Bit)
http://forum.xda-developers.com/showthread.php?t=2550635
what os are you running on your pc?
.
Click to expand...
Click to collapse
@hhp_211
Windows 7 (just with 98 theme)
I already have that installed, and it still doesn't work. A lot of threads are saying to enable usb debugging, but I can't do that in the phones current state right?
I attached the screenshot of what cmd stays on
barky02 said:
Windows 7 (just with 98 theme)
I already have that installed, and it still doesn't work. A lot of threads are saying to enable usb debugging, but I can't do that in the phones current state right?
Click to expand...
Click to collapse
Ok I thought Win 7, but then other shots were looking different...
well I'll ask anyway...
have you downloaded and installed
the Minimal ADB and Fastboot -- Version 1.1.3
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
the mfastboot-v2.zip
http://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280
[[[and extract the zip then copy mfastboot.exe into the same folder as the stock firmware files (the same folder as the .bin and .img files).]]]
then put the .bat file inside the firmware folder,,, then doubleclick the .bat file while phone is in fastboot mode and attached to pc
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
It means you've not copied the files into your ADB folder as it can't find the fastboot files
ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
gamer.11 said:
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
Click to expand...
Click to collapse
This won't work if fastboot binary isn't in env PATH.
EddyOS said:
It means you've not copied the files into your ADB folder as it can't find the fastboot files
Click to expand...
Click to collapse
"Into your FASTBOOT folder". adb's got nothing to do with this.
http://forum.xda-developers.com/showthread.php?t=2513701
Follow method two in this guide.
beekay201 said:
This won't work if fastboot binary isn't in env PATH.
Click to expand...
Click to collapse
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Easiest way is to extract the sh1t out of the Google file until you eventually see all the img files. Then extract the fastboot zip into the same folder they're in and open a command prompt there.
Fastboot zip -
https://www.dropbox.com/s/b8wxmwfi2ekdw3a/Adb And Fastboot.zip?dl=0
Sent from my Android 5.0 Nexus 5
gamer.11 said:
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Click to expand...
Click to collapse
Because it's in your PATH.
beekay201 said:
This won't work if fastboot binary isn't in env PATH.
"Into your FASTBOOT folder". adb's got nothing to do with this.
Click to expand...
Click to collapse
People refer to the folder with ADB and fastboot in it as the ADB folder (If you had adb/fastboot in the system path this wouldn't even be required)
Do you really think I meant them to use ADB? Come on, now
beekay201 said:
Because it's in your PATH.
Click to expand...
Click to collapse
oh "env" meant environment, sorry did not understand your shot hand.
by the way OP? solved your issue?
EddyOS said:
People refer to the folder with ADB and fastboot in it as the ADB folder
Click to expand...
Click to collapse
I refer to this folder as the platform tools folder
nikon120 said:
I refer to this folder as the platform tools folder
Click to expand...
Click to collapse
Makes more sense I guess, just more to type! This is where being in PATH makes life better
My phone is the Indian version of XT1033 2013. I was trying to install a factory image so downloaded an image(XML). I have downloaded 3 more images since(all XML). Every time the same error message pops up 'image is too big'. My internal data got erased so it's not as if I can go back to my previous ROM. One solution on a XDA thread suggested using mfastboot( I use minimal adb and fastboot), but my device isn't recognized by mfastboot. No such problems arose with minimal fastboot. My adb is also disabled, so I cannot push any ROM. What should I do now ?
Edit: i got out of the boot loop easy. My OTG wasn't recognized by CWM because it was using NTFS. Formatted and changed to FAT32, and voila !
You have to drop mfastboot.exe in the same folder as the firmware image files. Then navigate in command prompt to that location.
mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide a log if you still have problems. Copy and paste command prompt screen. Take screenshots.
Done that already
lost101 said:
You have to drop mfastboot.exe in the same folder as the firmware image files. Then navigate in command prompt to that location.
mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide a log if you still have problems. Copy and paste command prompt screen. Take screenshots.
Click to expand...
Click to collapse
The image file was too big. As I said, i tried it with 4-5 factory images. Nothing. So I managed to flash a ROM using OTG. It was simple,really. Thanks for repying !