Related
Hi there.
As the above title says, what happen if I do so?
I do not have recovery version 2.5.1.3 in my ROM Manager anymore(I have no idea know why). Also do not have 3.0.2.5.
The only recovery I have is 2.5.1.4, 3.0.0.5, 3.0.0.6 and 3.0.2.4. Plus I am unable to flash 2.5.1.4 version(it pops up an error)
Some have no issues, but some have experienced issues when trying to restore cwm backups.
Have a look in the LeeDrOiD 2.2.3 thread a few days ago. I have posted methods to manually flash it via a tool or adb commands. I have also provided dl links as well.
Sent from my Desire HD using XDA App
Hi Upintheair
Thanks for the reply. Erm.. do you remember the exact date you post that in LeeDroid's thread? The thread is overloading. I cannot find them. =(
From Index of /cm/recoveries Download recovery-clockwork-2.5.1.3-ace.img
Try one of these 2 tools, instructions are on the threads;
1. Thread: [TOOL][All devices & OS] Fastboot Commander [v.1.1]
Download: Fastboot Commander v1.1
2. Thread: Android Flasher
Download: [UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.7.4]
OR
Manually through ADB:
1. Place the image in where fastboot.exe is located.
2. Connect phone to PC with Bootloader FASTBOOT USB
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
Click to expand...
Click to collapse
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
kgulruh said:
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
Click to expand...
Click to collapse
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash . Also ensure notebook & phone batteries have near full charge.
Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.
...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux
Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)
To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.
If you want to use CMD:
Place image inside SDK folder where fastboot & adb.exe are located.
Rename it to radio.img (unless you like to type the whole name again)
CMD type: " fastboot flash radio radio.img", then
"fastboot reboot"
I am not too sure about Linux PCs, always been Windows until Android.
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
SERGI.3210 said:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
Click to expand...
Click to collapse
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Thanks UpInTheAir
I'll try it later tonight. Guess I will try to manually flash them.
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
I just recalled I read it somewhere last time when I was learning how to flash new radio. x)
superstick1 said:
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
Click to expand...
Click to collapse
If you are referring to the "tool" as in the CMD (Command Prompt)?
If this is what you mean, the answer is Yes & Yes.
Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
superstick1 said:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
Click to expand...
Click to collapse
Ensure Fastboot is OFF & USB debugging ON in phone settings
When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
Did you test Fastboot communication by command "fastboot devices"?
Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
superstick1 said:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
Click to expand...
Click to collapse
1. Mine works fine with usb debugging on & fastboot off.
2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.
3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"
If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
Sent from my Desire HD using XDA App
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
UpInTheAir said:
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Click to expand...
Click to collapse
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.
Certainly .... which is the meaning of "koush"???
superstick1 said:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
Click to expand...
Click to collapse
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.
3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.
Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8
I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.
View attachment Recovery_Ace_v2.5.1.3.zip
View attachment Recovery_Ace_v3.0.2.8.zip
Installation:
1. Power off your DHD
2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.
3. Plug-in the USB cable. (FASTBOOT USB)
4. Extract xxxx.zip
5. Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
6. Done! The device will be automatically rebooted.
7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.
I tested the windows commands and worked perfect Linux should too!!
I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
UpInTheAir said:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Click to expand...
Click to collapse
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.
For me typing in linux is better then knowing nothing in windows
superstick1 said:
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
Click to expand...
Click to collapse
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).
Try that way.
Install Instruction:
Set flashtool to fastboot mode.
Extract the boot.img from the ROM zip.
Place the ROM zip onto your SD card.
Flash the boot.img using fastboot.
Boot into CWM.
Select install zip, choose from SD card and select the ROM zip.
Then flash the GApps package is you put it on your SD card.
Reboot phone and you should be running CM10.1 on your phone now.
------------
Hi,
I am trying to install this rom legacy xperia 4.2.2 But I am stuck at flashing kernel
The tool is flashtool as you can see in picture
http://www.uppic.org/share-AA2F_520F170B.html
When I click select kernel to flash, it doesnt do anything and the red text says error...
Don't use flashtool, try using fastboot.exe instead.
Place the kernel in the same directory as fastboot.exe, press shift and right click on the directory and click "open command window here"
Then type they following into cmd:
fastboot devices
Confirm you see at least one device there, it will appear as a jumbled set of numbers and letters followed by the word fastboot. That will be your device.
After that, type this into cmd:
fastboot flash boot boot.img
If done correctly, it will say boot.img sent or something, it will definitely show some kind of success.
You can disconnect your phone now, boot it up and press vol down when you see a blue flash. This will bring you into CWM recovery.
From there, select install zip -> choose from SD card -> ROM zip
Flash it and reboot, you should have CM10.1 running on your phone now.
P.S this should be in Q&A section instead of general.
僕のLT18iから送られてきた
niruzz said:
Install Instruction:
Set flashtool to fastboot mode.
Extract the boot.img from the ROM zip.
Place the ROM zip onto your SD card.
Flash the boot.img using fastboot.
Boot into CWM.
Select install zip, choose from SD card and select the ROM zip.
Then flash the GApps package is you put it on your SD card.
Reboot phone and you should be running CM10.1 on your phone now.
------------
Hi,
I am trying to install this rom legacy xperia 4.2.2 But I am stuck at flashing kernel
The tool is flashtool as you can see in picture
http://www.uppic.org/share-AA2F_520F170B.html
When I click select kernel to flash, it doesnt do anything and the red text says error...
Click to expand...
Click to collapse
Connect your phone in fastboot mode first. For that, turn off your phone, connect USB cable to the PC, then hold down Menu button and connect USB cable to the phone. If blue LED lights up, phone is in fastboot mode. If not, try again.
popthosegaskets said:
Don't use flashtool, try using fastboot.exe instead.
Place the kernel in the same directory as fastboot.exe, press shift and right click on the directory and click "open command window here"
Then type they following into cmd:
fastboot devices
Confirm you see at least one device there, it will appear as a jumbled set of numbers and letters followed by the word fastboot. That will be your device.
After that, type this into cmd:
fastboot flash boot boot.img
If done correctly, it will say boot.img sent or something, it will definitely show some kind of success.
You can disconnect your phone now, boot it up and press vol down when you see a blue flash. This will bring you into CWM recovery.
From there, select install zip -> choose from SD card -> ROM zip
Flash it and reboot, you should have CM10.1 running on your phone now.
P.S this should be in Q&A section instead of general.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
What's wrong with using the fastboot within Flashtool? It is a lot easier for most of the users.
popthosegaskets said:
Don't use flashtool, try using fastboot.exe instead.
Place the kernel in the same directory as fastboot.exe, press shift and right click on the directory and click "open command window here"
Then type they following into cmd:
fastboot devices
Confirm you see at least one device there, it will appear as a jumbled set of numbers and letters followed by the word fastboot. That will be your device.
After that, type this into cmd:
fastboot flash boot boot.img
If done correctly, it will say boot.img sent or something, it will definitely show some kind of success.
You can disconnect your phone now, boot it up and press vol down when you see a blue flash. This will bring you into CWM recovery.
From there, select install zip -> choose from SD card -> ROM zip
Flash it and reboot, you should have CM10.1 running on your phone now.
P.S this should be in Q&A section instead of general.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Thanks but it doesnt work.
fastboot devices < doesnt return with anything
fastboot flash boot boot.img < it says waiting for device >
I have try many program like Sony flashtool emma, and both do not work
http://postimg.org/image/jnx079uwd/
niruzz said:
Thanks but it doesnt work.
fastboot devices < doesnt return with anything
fastboot flash boot boot.img < it says waiting for device >
I have try many program like Sony flashtool emma, and both do not work
http://postimg.org/image/jnx079uwd/
Click to expand...
Click to collapse
Have you installed adb drivers for your phone?
Sent from International Space Station
yes, http://postimg.org/image/eau58isot/
What API do I have to install?
I am on ultimate HD4 Rom
niruzz said:
yes, http://postimg.org/image/eau58isot/
What API do I have to install?
I am on ultimate HD4 Rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1582554 download it from here.
ChillToucH said:
http://forum.xda-developers.com/showthread.php?t=1582554 download it from here.
Click to expand...
Click to collapse
IT WORKS!!!
:victory:
popthosegaskets said:
Don't use flashtool, try using fastboot.exe instead.
Place the kernel in the same directory as fastboot.exe, press shift and right click on the directory and click "open command window here"
Then type they following into cmd:
fastboot devices
Confirm you see at least one device there, it will appear as a jumbled set of numbers and letters followed by the word fastboot. That will be your device.
After that, type this into cmd:
fastboot flash boot boot.img
If done correctly, it will say boot.img sent or something, it will definitely show some kind of success.
You can disconnect your phone now, boot it up and press vol down when you see a blue flash. This will bring you into CWM recovery.
From there, select install zip -> choose from SD card -> ROM zip
Flash it and reboot, you should have CM10.1 running on your phone now.
P.S this should be in Q&A section instead of general.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
yes flashtool doesnt work. but fastboot works.
:laugh:
delete by me
niruzz said:
yes flashtool doesnt work. but fastboot works.
:laugh:
Click to expand...
Click to collapse
Flashtool works. You just have to learn how to use it, like connecting phone in fastboot mode before selecting any fastboot options in flashtool
Sent from my Xperia Arc S using xda premium
I am having problem flashing kernel through fastboot.I get an error "unknow partition .......img" when flashing kernel via fastboot from my laptop.Flashing kernel via my desktop is fine though.Since i am having problem with my desktop i wanted to use laptop to flash kernel to be safe.I have installed drivers,flashtool drivers,fastboot driver,google usb driver,android sdk etc.My laptop is 64 bit windows 7.In device manager it shows android device >> adb device inteface.
Fastboot shows device number with "fastboot devices" and i can reboot my phone as well with "fastboot reboot" command but when i tun fastboot flash xxx.img it gives "unknow partition .."error.I have tried different kernels to flash but can't flash them.However same kernel flashing command works on my desktop with 32 bit win7.
My device is bootloader unlocked and i have flahsed many kernels and ROMs via my desktop.What might be missing to install in my laptop?
Anybody around to help solve this problem? When i connect my device is fastboot mode(bootloader). It recognizes it has 'S1 fastboot drive",there is also ADB android device shown in device manager.I can run fastboot commands like "fastboot device","fastboot reboot".They work fine but i can't flash kernel for some reason.I have my kernel file places in same folder as fastboot.exe and running command prompt from same folder.
What might i have been doing wrong?
shoeseat said:
Anybody around to help solve this problem? When i connect my device is fastboot mode(bootloader). It recognizes it has 'S1 fastboot drive",there is also ADB android device shown in device manager.I can run fastboot commands like "fastboot device","fastboot reboot".They work fine but i can't flash kernel for some reason.I have my kernel file places in same folder as fastboot.exe and running command prompt from same folder.
What might i have been doing wrong?
Click to expand...
Click to collapse
What are the commands you used?
Rename the kernel if you have to since fastboot cannot read spaces.
popthosegaskets said:
What are the commands you used?
Rename the kernel if you have to since fastboot cannot read spaces.
Click to expand...
Click to collapse
Thankx for the reply.I have tried to flash different kernels which i have flashed from my desktop.In fact there are more the 10+ kernels which i can flash successfully from desktop.Kernels and fastboot files are all in same folder and i have copied them to my laptop.The names are like boot.img, 5_4fusion_2.img, LuPuS_anzu_jBv12-ram.img etc as they are when i download them.
i think fastboot is working since fastboot devices shows my device serial and fastboot reboot reboots my device but somehow i can't flahs kernel.i even installed adb intaller from this http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/ but still having problem.
If my computer crashed during kernel flash, does it brick my mobile?
shoeseat said:
If my computer crashed during kernel flash, does it brick my mobile?
Click to expand...
Click to collapse
It shouldn't, you will just need to reconnect the phone to the computer in fastboot mode and flash the kernel again. Did you try using flashtool in fastboot mode rather than command line?
僕のLT18iから送られてきた
You missed a part of the command, you need to use this:
fastboot flash boot yourboot.img
Sent from my Xperia C using Tapatalk
popthosegaskets said:
It shouldn't, you will just need to reconnect the phone to the computer in fastboot mode and flash the kernel again. Did you try using flashtool in fastboot mode rather than command line?
僕のLT18iから送られてきた
Click to expand...
Click to collapse
I did run flashtool when connected in fastboot.Flashtool gies message as device connected to fastboot mode but the "kernel" button is disabled i think.Not sure but some buttons are greyed.
devstaff said:
You missed a part of the command, you need to use this:
fastboot flash boot yourboot.img
Sent from my Xperia C using Tapatalk
Click to expand...
Click to collapse
In desktop i always used "fastboot flash yourboot.img".I have command saved in notepad as well.i will try "fastboot flash boot yourboot.img" today,is it due to 64 bit OS i have to use "fastboot flash boot"?
"fastboot flash boot yourboot.img" was right command."boot" was missing from my command but "fastboot flash yourboot.img" was working on my desktop.Is it due to 64 bit OS i have to add "boot" in command?
Anyway thankx for help.
shoeseat said:
I did run flashtool when connected in fastboot.Flashtool gies message as device connected to fastboot mode but the "kernel" button is disabled i think.Not sure but some buttons are greyed.
Click to expand...
Click to collapse
Try Clicking on the lightning bolt (Flash) and then choose the fastboot mode... From here on out you can hotboot or flash your new kernel. BUT ... make sure you click on reboot into fastboot mode first (ADB)
Let me know if it worked for you
shoeseat said:
In desktop i always used "fastboot flash yourboot.img".I have command saved in notepad as well.i will try "fastboot flash boot yourboot.img" today,is it due to 64 bit OS i have to use "fastboot flash boot"?
Click to expand...
Click to collapse
Nope, it is not due to 64 bit OS, it is like this for every OS (at least for Windows PC, not sure about Linux). The command tells computer, how the process must be done.
If you use
Code:
fastboot flash boot.img
then it is understood as fastboot has to flash nothing to partition named "boot.img". Using
Code:
fastboot flash boot boot.img
is the proper way, then fastboot knows, that it must flash boot.img to 'boot' partition.
MrMaddTraxx said:
Try Clicking on the lightning bolt (Flash) and then choose the fastboot mode... From here on out you can hotboot or flash your new kernel. BUT ... make sure you click on reboot into fastboot mode first (ADB)
Let me know if it worked for you
Click to expand...
Click to collapse
Thankx for the suggestion but it's already working now with fastboot command.
How to USE FASTBOOT commands in case your Device got Soft-Bricked with NO DISPLAY
Click to expand...
Click to collapse
Let's describe Softbrik:-Anything caused to your phone except damage to Hardware of your phone which put your Device into a state where it is not booting up and kept showing White, Gray, Blue or Black Screen or Either It gets stuck at Company logo Screen. This may occur if something goes wrong during Rooting, flashing Recovery or ROMs or during Updating in Recovery Mode or either being caught by some wrong software or VIRUS !!!
Preface to the Guide:
Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host computer via USB. It allows flashing of unsigned partition images and also can erase partitions. Its a part of Android Developement Kit (Android SDK).
Use of FASTBOOT is disabled in production devices since USB support has been disabled in the bootloader. You must have an Engineering SPL, or an SPL that is S-OFF or Unlocked bootloader to use 'fastboot'.
After installing the Android SDK or ADB Standalone you can use 'fastboot' in addition to the more common ADB.
One can use the attached .android folder if u want to skip downloading Android SDK. (Refer Attachment)
Verify SPL S-OFF or Bootloader Unlocked:
Not required for Micromax !! But certain Production Devices like Sony HTC LG etc may need bootloader to be unlocked before carrying out this process. My simple advice to people is.. "If you enjoy experiments on your device, you must be ROOTED and to ROOT you device you may need to have unlock bootloader"
Preparations:
(1) Download attached .android.zip, Extract and place .androidfolder on C:/ drive of your PC. So the path of this folder will look likeC:/.android
(Never remove this ".android" folder from C:/ coz you will require it whenever u want to experiment with you Droid using ADB or FASTBOOT methods. I assure... You can do a lot more with it; if you really explore how to use various commands !!!)
.android folder is containing adb.exe, fastboot.exe and related drivers adb_usb.ini, android_winusb.ini AdbWinApi.dll and AdbWinUsbApi.dll and other files; all together not more than 800KB
(2) Connect Device in 'USB debugging ON' mode.
Ensure Drivers for your Device are already installed on the host computer
Note: I recommend you should always keep USB Debugging opetion 'ON' as it only can help you, in case, your device get SoftBricked and you cant see anything on Device Screen. Remember that with USB debugging 'OFF' your Device can't communicate with your Host Computer.
(3) Host Computer Ability to Launch Command Prompt:
On Windows-XP or earlier, to start ADB (Android Debug Bridge) You need to locate your folder containing adb.exe where as Windows-7/Vista/Other-Latest-OS can directly launch command prompt from the Folder itself by Shift+Right Click on Mouse and Selecting "Open Command Prompt from here".
Hence 'Locating 'adb' folder-steps' are for XP users only, However higher OS users can skip it and can directly start giving 'adb' commands after opening cmd from .android folder.
(4) So now, Open Command Prompt (in Windows XP), it will return like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\USERNAME>
(As our adb.exe is in C:/.android.... we will type: Cd C:\.android)
C:\Documents and Settings\USERNAME>Cd C:\.android (Hit Enter)
C:\.android>
Let's give command to detect attached device by writing: 'adb device'. On hitting enter it will list all devices attached to your PC.
Code:
C:\.android>adb devices
List of devices attached
XXXXXXXX-XXXX device
Now u can do a lot while your Device is attached in 'adb mode' e.g.:
Code:
1. Rebooting into Bootloader (FASTBOOT)
2. Installing apps on as /system/app or /data/app
3. Copying Files to/from your SDCARD
4. Pulling Files or Apps already installed on your /system or /data partition
To Understand adb commands and how they work please read:
http://developer.android.com/tools/help/adb.html#commandsummary
Let's come back to ISSUE: "We have a SOFTBRICKED devices !!!"
(1) Booting into FASTBOOT mode:
Let's come back to'fastboot' as we need to flash new ROM or to apply update.zip in a Softbricked deviceNote: Let your device remain connected to PC and don't disconnect untill You finish you job-successfully and get your Device again in working Factory Condition.
""fastboot reboot-bootloader" This command is used to reboot your device into bootloader i.e into fastboot mode) and In this Mode your device will stuck into boot logo only and u cant operate it. ;D Well we are not concerned as we already have a bricked device with no screen display !!!. Lets go ahead...on cmd follow:
Code:
C:\.android>adb reboot-bootloader
C:\.android>fastboot devices
XXXXXXXXXXXX fastboot
(2) Unlocking-ReLocking Bootloader:
(Skip if u working with pre-unlocked devices)
C:\.android>fastboot oem unlock
...
SUCCESSFUL
finished. total time: 118.063s
Click to expand...
Click to collapse
(Accept/Decline warning on your devices screen. Select YES to Unlock)
(Once ROM is flashed) To relock Bootloader use command: fastboot oem lock:
Code:
C:\.android>fastboot oem unlock
...
SUCCESSFULL
finished. total time: 118.063s
(Accept/Decline warning on your devices screen. Select YES to ReLock)]
(Skip if u working with pre-unlocked devices)
(3)Get 'Recovery.img' and 'Update.zip' for your Device:
Lets Wipe the Data and then proceed to Flash new ROM/Update.zip
IMPORTANT: Copy the stock recovery.img and your devices' Update.zip[ in .android folder(You can get it even by searching it in this forum or by Googling for it..) So I assume that you have it....in your .android
Abbreviations:
recovery.img = Stock Recovery of your Device
Update.zip = Update Package/Stock ROM of your Device
Let's start wiping and updating process with following commands:
(4)Wiping Old Data and Flashing new Update.zip:
Code:
C:\.android>fastboot -w
SUCCESSFUL
C:\.android>fastboot update Update.zip
(Here Replace Update with Full Name of your any Update.zip that you copied to .android folder)
Your phone will update and automatically reboot into the Factory State. Cheers !!!
Note: Its important to spell the file name correctly that u want to flash/update. No space between name are allowed. This process will only be successful if your device is still carrying recovery partition 'intact'.
.....If above wiping/updating FAILS....
If you still in "No Display State", extract update.zip to .android folder (U can use 7zip).
You will find following main .img files, each incorporate specific partition on any android device. In our case we can extract following:
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Code:
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partionsusing the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Code:
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img :(here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
..If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Code:
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Code:
C:\.android>adb push update.zip /data/sdcard
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Code:
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)'ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!!
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
RmatriX1218 said:
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
Click to expand...
Click to collapse
bro if your volume + key is not working so how can u say that your device is soft bricked...
i think you should repair your volume keys and than try to move to recovery...
& one more thing without installing all drivers/thing u will not be able to access fastboot mode.....
Hey!!
Please please help me!!
I have MICROMAX a54 ninja 3.5.my mobile stuck in bootloop and soft bricked!!
When I turn on my devices it stuck in logo ninja 3.5.
I also try to go in recovery mode by pressing volume up+home key+lock key!
But it doesn't enter in recovery mod!!
Now what am I do??
Please please help me.
Thank you in advance..
I think for going in recovery:-
1. Press and hold power button.
2. While holding power key, press and hold both volume keys, (vol+ & vol-)
3. When mmx logo comes it will display a message vol(+) for recovery and vol(-) for fast boot then again press vol(+) for once,
And now your in recovery
I lost my recovery.
And I can't go into recovery mod!!
Please help me
Sent from my YU5010 using XDA Free mobile app
What do u mean by, lost your recovery???
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Ok ok just try flashing your official rom
---------- Post added at 10:35 AM ---------- Previous post was at 10:17 AM ----------
Aakash mehta said:
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Just download your official rom, Your device driver for pc, and install the rom to your device using "sp flash tool"
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Aakash mehta said:
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
1.First download your stock recovery for your mmx a54 from here http://d-h.st/D7G
2. Now download sp flash tool from here https://drive.google.com/file/d/0B9S_ERLSMngHVE9Qc25ObGU1UU0/edit?pli=1 install it to your pc.
3. Download drivers for a54 from here singledrivers.blogspot.in/2013/12/micromax-ninja-a54-usb-driver-for.html?m=1 install the driver to your pc.
4. Download your phone stock rom from here http://d-h.st/fg2 place it in your external sd card(mmc) of your device.
5. Download scatter file from here www.mediafire.com/view/rvz1c5tiifx7yck/MT6575_Android_scatter.txt
6. Now run sp flash tool in your pc, browse to the scatter file.txt, turn off your phone remove the battery and connect it through usb to your pc. (Connect the device without battery)
7. Now select the recovery tab in sp flash tool browse to the recovery.img file (Which we hv downloaded before). Now select the option download in sp flash tool it will Start flashing your stock recovery to the device, A green tick marked will be comes as the flashing complete, now remove your device from pc.
8. Now goto recovery by vol key combination.
9. Now select apply update from sd card and select the stock rom.zip file
10. When flashing done then, Wipe Cache Partition and factory data reset of your device.
Now just select reboot device now it will take around 10min to boot for the first time so wait. Hope this helps you
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Aakash mehta said:
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Don't say thanks my Buddy just press thanks button.
Hello
I tried sp tool flasher!!
I followed all steps which were given by you!!
BT although not any change in my mobile..
When I tick recovery and then browse recovery.img file and click download button but nothing had happened..
It didn't detect my mobile and didn't go for procedure!!
So now what am I do???
You helped me very much!!
Bu please further help me...
Sent from my YU5010 using XDA Free mobile app
Hv u installed driver properly, just trust me try different usb ports
Yeah i installed drivers properly!!!
Sent from my YU5010 using XDA Free mobile app
So your device is not recognizing by sp flash tool r8
I think so
Sent from my YU5010 using XDA Free mobile app
micromax a210
I have a problem with fastboot stuck on system erasing on adb fastboot mood also userdata and cache only flash recovery and boot img sp flash not working with this phone I do other mtk android with sp tool successfully what I do
What if the device is recongised in adb as : (device name) recovery, but can't actually boot into recovery (twrp) and thus when entering the command : adb reboot fastboot it can never actually boot into fastboot ?
Are there any adb commands that can do the trick or is it game over ?
Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastboot getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Joheee said:
Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastbood getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Click to expand...
Click to collapse
Probably just a typo, but you wrote 'fastbood' in your post. Computer definitely won't recognize that. If you are spelling it right, either 1) you're in the wrong directly in terminal, (cd /(wherever adb is installed), or 2) adb package didn't install correctly, (reinstall). While you're testing it, you can just type 'fastboot', and you should get a list of command options, showing that it is installed.
Sorry yes fastbood was a typo. But what do you mean with: you're in the wrong directly in terminal, (cd /(wherever adb is installed).
A terminal is the same as a command prompt right?
And to reinstall adb package, i would have to delete the platform-tools right? And when i click on delete package, it asks if Im sure about it, bacause it can not be undone.
When you open command prompt, you're 'in a directory', usually in Windows, it's C:/(user)/desktop, or something. You need to get to the directory where adb is. If you installed it with defaults, it's probably C:/adb. If so, once you open command prompt, type 'cd /adb', and hit 'enter'. Then you'll be 'in the right directory'. If adb installed somewhere else, you'll have to find out where, then type 'cd /(whatever)/(whatever)/adb.
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Joheee said:
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Click to expand...
Click to collapse
First thing you have to do is find out where on your PC the adb files are. The computer won't recognize anything you type with fastboot, adb, etc., unless you're in that directory. I believe adding the environmental variable path is supposed to make that easier, but obviously it's not working out for you, so I would just skip that and find out where the files are, then you can just use 'cd', and go there. It should be easy to do a search in Explorer if you can't find it.
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Joheee said:
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Click to expand...
Click to collapse
Can you tell me what directory on your PC the adb files are located? As far as drivers, best bet is usually PC companion, or Flashtool.
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Joheee said:
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Click to expand...
Click to collapse
If PC Companion is giving you that msg, you might be OK w/ drivers. With that being the location of your adb files, you would open command prompt, and type - cd \Users\BTO\AppData\Local\Android\sdk\platform-tools\adb - then you'll be 'in' the right directory, (just to make sure, look in the 'adb' folder and see if fastboot exe is in there). Your command prompt should show - C:\Users\BTO\AppData\Local\Android\sdk\platform-tools\adb. Then type 'fastboot', and you should get output of command options.
If all goes well and you want to make it easier in the future, just move the whole 'adb' folder to C drive root. Then you'll only have to type 'cd \adb'.
Or you could just open a window in the correct directory, hold right shift button on keyboard and click right mouse button and select "open command prompt here "
Easy peezy
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Joheee said:
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Click to expand...
Click to collapse
Sorry i missed that... How about Flashtool driver installer? If you DL Flashtool, there's an exe in the 'drivers' folder that will install for you.
Hey you might be using windows 10,8,8.1 if so follow this guide http://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114
All The Best
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Joheee said:
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Click to expand...
Click to collapse
Try different files. Here's a boot IMG that I've used successfully - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM - and try this for recovery - https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
Use 'fastoot devices' before flashing to confirm connection.
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Joheee said:
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Click to expand...
Click to collapse
The boot and recovery files will just enable you to get into recovery. You'll need a ROM file to put a ROM on your phone. There are many to choose from in the 'android development', and 'original android development' threads. To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img'). Then you can reboot into recovery. Once you download your ROM file, you want it to be on your SD card in the phone. When you get into recovery, you go to your ROM file and install.
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 40 minutes on the blue 'waving' startscreen, and getting quite hot even.
Click to expand...
Click to collapse
If your phone is stock, it won't boot with the new IMG you flashed. That's also why the computer doesn't recognize it. You can copy your ROM onto the SD card with your computer, using a card reader or adapter. Just flash both IMGs, then unplug, then turn it on, and hit vol up when you see purple. Make sure you type flash 'boot' for the boot, and flash 'recovery' for the recovery, not 'boot' for both. Also, if you want, there are custom IMG files with recovery on xda for stock ROM that you could flash the same way, if you just want to use your stock.
---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Click to expand...
Click to collapse
Try this for stock - https://mega.nz/#!k0cTUQbS!5XUZhTEK4xBKVBSeO83TEHE3xs9JEpvxt3g1Sc8tVH8