Hi all, first time trying to root/mod a phone - stuck at the first hurdle.
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide
Following the above guide, installed everything as instructed but when I plugged phone in & press the Vol Up button then run the 'fastboot -i 0x0fce getvar version' command I get the <waiting for device> message.
What do I do now?
Fraooke said:
Hi all, first time trying to root/mod a phone - stuck at the first hurdle.
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide
Following the above guide, installed everything as instructed but when I plugged phone in & press the Vol Up button then run the 'fastboot -i 0x0fce getvar version' command I get the <waiting for device> message.
What do I do now?
Click to expand...
Click to collapse
well first of all you must watch to see if your device goes into fastboot once you connected it to the computer, the notification led should go on blue.
Does the light turn blue?
if it doesnt,try this:
first open fastboot,
then remove the battery.Next, connect it to PC,then keep pressing the vol up button while install the battery.Then the light will turn blue and everything will go well.
I hope it will help you and sorry for my bad english
Related
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
rodabi said:
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
Click to expand...
Click to collapse
flash the recovery again using fastboot
Thanks for the reply. So my problem so is that I'm trying to boot in to RSD mode but it get the message "Battery is too low to flash".
I'm trying to charge the battery but whenever i plug it in to charge phone starts up and ends up in the boot cycle, and the battery doesn't end up charging.
How can i force the phone not to turn on when I plug it in to the wall charger?
Ok, I was able to McGyver a usb charger from an old cable and I got the battery charged enough where it would enter fastboot.
However... now I can't get either of my laptops to recognize the phone in fastboot.
I attach the phone to the usb port, turn the phone on and hold the volume down button. I press the volume up button when fastboot appears, the message "Starting Fastboot protocol support" appears and then nothing happens. Windows just sits there, the phone just sits there...
If I do moto-fastboot devices at the command prompt there is no serial.
Any thoughts?
Well, normally nothing happens until you issue a fastboot command. I usually boot into fastboot mode first, THEN connect the phone & open a command line, etc.
What happens if you do the above and type "fastboot devices"? Does it see your phone then?
Ok, so I tried your method, and installing some different windows drivers and now windows does recognize the phone!
For the record, I am on windows xp and currently i'm using driver version 2.0.40 (same problem with 2.0.53).
Now windows isn't able to install the fastboot drivers, it comes up as an unrecognized device. Is there a way to manually install the fastboot drivers?
Although it's recognized by windows, issuing the moto-fastboot devices command still returns blank.
So I am no noob and have unlocked and rooted 50+ androids in my day. I have personally done 12 Atrixs in the last 12 months. Today I got my hands on a free Atrix and decided I'd go ahead and do the norm.
I used the http://forum.xda-developers.com/showthread.php?t=1182871 method which I always do and proceeded as normal.
I ran the script like always and got the failed to boot 0x1000 error like always. Got the phone to run fastboot and ran the fix but on cmd for the first time ever I got the <waiting for device> message that never seemed to stop "waiting." I have never ran into this before and did everything as I normally do... I'm guessing I hard bricked it but have no idea how that could be.
Since I can get the phone into fastboot is there a way to recover the device and retry the method? If not no biggie as it was free and I could really care less as I have my Atrix, a S II and a Skyrocket lying around that I use regularly but would love to get this bad boy up and running. Please let me know ASAP if there is a fix...
Soo when you type cmd and choose your option
if it says "waiting for device " reboot it into "Fastboot mode
make sure u press volume Up
so then phone should read" Starting fastboot protocal" and type Fastboot devices your output should read
List of devices connected
then your device id like TA084327
something like that then type
fastboot oem unlock
ltdanno360 said:
Soo when you type cmd into pc go to your fastboot folder then type fastboot oem unlock
if it says "waiting for device " unplug phone reboot it into "Fastboot mode
make sure u press volume Up
so the phone will read Starting fastboot protocal Then plug into Pc
Click to expand...
Click to collapse
No no no... I run the script from http://forum.xda-developers.com/showthread.php?t=1182871 and I get to the point where it says "Starting fastboot protocal" and then the script tells me to plug in phone. I do and then I hit enter on script and it then says <waiting for device> ...... therein lies the problem.
*Solved
hello,i tried to change the CID of my phone(gsm) and the usb cable was removed. now i think that it is bricked,and it shows "error device not found" in cmd. can anyone help me plz?:crying: am ready to donate as much as you want.
Can you still get fastboot to work? If so, try typing this command fastboot oem writecid 11111111
No mate,only the red led lights when connected to my pc. No sign of life after that. When i adb reeboot bootloader,it shows "device not found".
can you boot into bootloader using power+vol down(pull batery first)? If so go into fastboot mode and check if device is detected (type "fastboot devices" )
if all goes well you could maybe try running an RUU to get your phone working again
EM|NEM said:
can you boot into bootloader using power+vol down(pull batery first)? If so go into fastboot mode and check if device is detected (type "fastboot devices" )
if all goes well you could maybe try running an RUU to get your phone working again
Click to expand...
Click to collapse
Nothing hapens mate. Can't get in bootloader nor recovery. If i connect to charger or pc via usb,only the red led lights up. Nothing more.
Hi guys,
This Is my first post so I hope I do it correctly. As the title says I am having problems with fastboot on my Acer Iconia One 10 B3-A40. I have enabled developer settings on my device and turned on the setting to unlock OEM. The problem is when I try to run the tablet in fastboot mode to unlock the OEM through ADB commands. When connected to my computer and running the command "adb devices" it shows my device Id and that it is connected. I then run the command "adb reboot-bootloader" to which the tablet switches off and makes the chime that it was disconnected from the computer and makes another chime and connects back onto the computer, the screen on my tablet remains blank with no indication it is in fastboot mode. When I run the command "fastboot devices" my device id shows up again that it is connected. When I originally tried to flash a patched boot image of my stock firmware it went through the process and failed mid way through saying it couldn be done cos the device was locked. After that I googled a bit to see what to do so that’s when I realised OEM unlock was to be switched on in developer settings and also using ADB commands. After returning to fast boot mode I ran the command "fastboot oem unlock" the 3 dots come up on command prompt to show the process is going but nothing happens on my device. Nothing will happen if I press the power button or the volume down button but if I press the volume up bottom, on command prompt it shows OKAY and then the amount of seconds it took to complete, the time changes based on how quick or long i take to press the volume up button but the device remains locked. I have being trying to find a solution for days and have searched everything i could find before making this post. It would be greatly appreciated if someone could help.
Need some urgent help..
I bought Amazfit 2 chinese Version today. Tried to change it to international firmware. Installed minimal Adb 1.4.3
Connected my watch to my laptop
Entered 1st command "adb devices"
Device was shown
Entered "adb shell reboot bootloader"
Device entered in fastboot mode
Entered "fastboot getvar all"
And it was stuck after <waiting for device>
Stuck here for ever.. and now the watch is also stuck on fastboot screen. Any help to get out of this and any probable cause ?
Check Device Manager, if you are using Windowze, sometimes the fastboot driver isn't properly configured, it is need to flash any ROM as far as I know.
To leave fastboot mode, either use "fastboot reboot" or press and hold the top/red button to turn watch off, then turn it back on.