Develop Bugs

Mac OS X Fastboot Mode <Waiting for Device>

Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks

i use windows but i also get problems when i didnt had a break after the flash parts/ update parts

brosenz said:
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
Click to expand...
Click to collapse
I know nothing about using Macs but have you installed the device drivers? As you are getting no serial number returned when using fastboot devices im guessing not.
Mark.
On a side note please do not post questions in the Development Forums as that is not the place for them.
Thanks.

The device is being detected while running in normal mode, meaning I do have the drivers, the problem is when I go into FASTBOOT MODE, I can no longer see the phone

Craiq said:
i use windows but i also get problems when i didnt had a break after the flash parts/ update parts
Click to expand...
Click to collapse
But for the simple command ./fastboot-mac devices should work and it's not

in bootloader mode u need other drivers
but dont know how to install them on mac

First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?

dhemke17 said:
First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?
Click to expand...
Click to collapse
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"

brosenz said:
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"
Click to expand...
Click to collapse
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?

dhemke17 said:
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?
Click to expand...
Click to collapse
I've done that, going into FASTBOOT MODE manually and the same result. Yes I am rooted.

I just want to go back to stock and re-lock the phone, is there other way to accomplish that ?
NOTE: I've tried Mac and PC (Galaxy Nexus Root Toolkit 1.3), different USB cables, different USB ports, reinstalled all the drivers on the Windows computer, NOTHING, the phone it's not being detected in FASTBOOT MODE.
Is it possible to go back to stock and re-lock from the Recovery Mode ?, I have ClockWorkMode 5.5.0.2 installed and working fine.

You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.

mskip said:
You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.
Click to expand...
Click to collapse
I used FASTBOOT to unlock and Root, no problem at all, use the phone for 10 days and them decided to go back to Stock and Re-Lock. If I connect the phone in normal operating mode to the computer it will be recognized and I can see the phone from the computer connected via USB, so the cabe, port on the phone and port on the computer are OK. I've tried different computer (Mac and PC), different OS (Mac OS X and Windows 7), different USB cable, different USB port.

Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.

dhemke17 said:
Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.
Click to expand...
Click to collapse
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks

brosenz said:
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks
Click to expand...
Click to collapse
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol -... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...

dhemke17 said:
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol +... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...
Click to expand...
Click to collapse
I do not know why but Vol + does not work in my phone

brosenz said:
I do not know why but Vol + does not work in my phone
Click to expand...
Click to collapse
My bad lol...down...volume down

I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I just used your video to unroot my galaxy nexus 4.0.4 thanks a lot!

[Q] Arc S, fastboot stuck at " sending 'boot' "

Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen

First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i

The file from the zip file is called "boot.img". I have copied it to the fastboot folder, and I am running "fastboot flash boot boot.img", as the "how to-" says.

Reinstall drivers
Sent from my LT15i using xda premium

espenta said:
Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen
Click to expand...
Click to collapse
did you make the phone enter fastboot mode?
you should run "fastboot devices" to see.

Thanks for the replies!
I tried on a different computer this morning, and here it worked immediately. Not sure what was wrong on the other one, because I installed the same SDK packages and USB driver. Installing ROM at the moment.
[Edit]: Everything seems to be working fine. Very happy with CM10 at the moment

dewa999 said:
First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i
Click to expand...
Click to collapse
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...

Tech-G.ONE said:
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...
Click to expand...
Click to collapse
You already asked for help in another topic, why here again?

Someguyfromhell said:
You already asked for help in another topic, why here again?
Click to expand...
Click to collapse
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....

Tech-G.ONE said:
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....
Click to expand...
Click to collapse
i dont like flashing kernel by flashtool, as far i done several 2011 devices the best method allways was over adb:good: & it pretty easy.
download android sdk & open the exe. leave all like it is (only may make sure google usb drivers are checked) & press on install.
after install place the boot.img here: ...\sdk\platform-tools
2. connect device into fastboot mode (blue led)
3.click in a empty space in the folder. now HOLD SHIFT & right click, choose ''open command line window here'' (<-- or sth like that sorry my setup is german)
4. enter 'fastboot devices' --> your device should be recognized as a bunch of numbers.
5. flash kernel by entering ''fastboot flash boot boot.img'' it tells you all done.
6. ''fastboot reboot''
7. enjoy new kernel

[Q] Phone Unlocked but can't ROOT!

Hello Guys
I own a HTC One X (4.1.1) which i bought a month ago and i m new to android. I unlocked my phone with the help of Hasoon2000 all in one toolkit. While rebooting into Bootloader it says unlocked and when i try to flash a recovery like CWM or TWRP it says "Error : No Device Found".
OR if i try to do it manually by rebooting in bootloader and then going in recovery it shows me a RED TRIANGLE. Toolkit installed the HTC drivers and I even copied CWM SuperSu folder in my HTC Storage. Pls Help as i really want to root my phone but i m not able to.
Tell me a procedure for how to root.
Thanks!

So the bootloader is unlocked?
Manually boot to bootloader(vol- and power), highlight fastboot and press power to confirm. Hook usb cable. Now it says 'fastboot usb' on the screen doesn't it?
Now go to your lil toolkit and try to flash a recovery. It should work.
Sent from my IceCold One X

TToivanen said:
So the bootloader is unlocked?
Manually boot to bootloader(vol- and power), highlight fastboot and press power to confirm. Hook usb cable. Now it says 'fastboot usb' on the screen doesn't it?
Now go to your lil toolkit and try to flash a recovery. It should work.
Sent from my IceCold One X
Click to expand...
Click to collapse
No man still the same thing "Error : No Device Found"
Any other solution..

It should not be a driver problem since unlocking the bootloader already used fastboot connection...
Try another usb port, another usb cable, reboot pc and try another pc if possible.
Sent from my IceCold One X

TToivanen said:
It should not be a driver problem since unlocking the bootloader already used fastboot connection...
Try another usb port, another usb cable, reboot pc and try another pc if possible.
Sent from my IceCold One X
Click to expand...
Click to collapse
Done everything u said but to no avail...
how did u root your one x??
can i again lock my phone and start the process all over again?

alcatus1708 said:
Done everything u said but to no avail...
how did u root your one x??
can i again lock my phone and start the process all over again?
Click to expand...
Click to collapse
tyr installing HTC Sync: http://dl4.htc.com/managed-assets/support/software/htc-sync/htc_sync_setup_3.3.21.exe

Ditch the damn toolkit and use a command prompt like a boss: http://d-h.st/592
Extract the 'win32' folder on your pc and launch the cmd prompt like this:
Hold shift and right click anywhere in the folder. Select open command prompt here.
Now DL the recovery from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Put it to the same folder as the fastboot files, rename it to recovery.img
Then type: fastboot flash recovery recovery.img

it says error cannot load recovery
I m using windows 7 64 bit

Have the recovery.img in the same folder as the files fastboot.exe, etc.
If your windoze hides file extensions, make sure it ain't named recovery.img.img
Sent from my IceCold One X

i copied the recovery file into the fastboot+adb folder which u told me to download and then entered command prompt. then it says that error while loading recovery. Do i have to copy the recovery file into other folder or something?

alcatus1708 said:
i copied the recovery file into the fastboot+adb folder which u told me to download and then entered command prompt. then it says that error while loading recovery. Do i have to copy the recovery file into other folder or something?
Click to expand...
Click to collapse
Your phone has to be on "fastboot usb" then do the command prompt thing.

robchongke said:
Your phone has to be on "fastboot usb" then do the command prompt thing.
Click to expand...
Click to collapse
See this is wat i did after unlocking the bootloader :
1) I downloaded the fastboot folder.
2) I downloaded the recovery file.(Clockworkmod)
3) I copy pasted the recovery file in the fastboot folder and renamed it recovery.img
4) I connect my phone to my pc using my usb cable.
5) I boot my phone into bootloader
6) on my pc using shift i open the command window in the fastboot folder.
7) I enter fastboot mode on my phone which says "Failed to open USB master mode"
8) I then type fastboot flash recovery recovery.img in the command windows and it shows error loading recovery file.
Am I doing something wrong??
I m not able to root my phone because of this.
pls help.
My phone is running 4.1.1 jellybean. Is dat a problem??

TToivanen said:
If your windoze hides file extensions, make sure it ain't named recovery.img.img
Click to expand...
Click to collapse
Bump

How about I just use teamviewer to flash your phone, OK? Please send me PW via Private Message(!)
Sent from my IceCold One X

Fastboot-unbrick your device with 'no display'

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 ?

TWRP installed but no OS. Udev problem?

Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things

Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.

NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?

ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.

Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.

mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back

Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess

Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure

Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv