Can anybody help me with this? (Really important)

[claudenegm]

Hey guys,
So, basically I'm giving my finishing touches to the new version 1.2.0.0 of my application Android Recovery Manager...
Since my phone has been stolen, so I'm not able to test..
I just want any of you to test this for me:
1. Do not connect your device.
2. Execute this command "fastboot -s SERIALNUMBER" where the SERIALNUMBER is your device's serial number.
3. it will say "< waiting for device >"
4. Connect your phone.

What happens?
Can you post me the output please? I need to know what happens exactly after that

About ADB, what's the output of something like this:
"adb -s SERIALNUMBER wait-for-device"
If you write a wrong serial number, and connect your device will it continue? or will it still wait for the device with the correct "SERIALNUMBER" to be connected?

Thanks

 

[dansharpy]

Where's the link to v1.2.0.0? I will test for you.

 

[claudenegm]

Where's the link to v1.2.0.0? I will test for you.

I still didn't release it, I just wanna know if both adb and fastboot commands wait for only the device with the entered serial number..
Those are the last things I need to know to release the new version..
It would be great if you can test them for me
Thanks

 

[dansharpy]

Mine still says 'waiting for device' when i connect it. Dont think there's anything wrong with my adb as i can use it to read the device serial and reboot. Tried everything and still doesnt do anything.

 

[claudenegm]

Mine still says 'waiting for device' when i connect it. Dont think there's anything wrong with my adb as i can use it to read the device serial and reboot. Tried everything and still doesnt do anything.

Thank you!
I think I know what's wrong.

Can you execute those commands please?
- adb reboot-bootloader
- fastboot -s SERIALNUMBER

Write them exactly after each other, don't wait for the device to get into bootloader.
It should say < waiting for device >, I'm wondering if it still waits even when the device enters into bootloader and says on your device "FASTBOOT USB".
If yes, you can cancel the command by pressing CTR + C on your keyboard.

To restart your phone into OS execute fastboot reboot

When you're done with the steps above, can you also test this for me please:
- Make sure your device is opened normally and USB debugging is enabled.
- Do not connect your phone.
- Execute adb -s SERIALNUMBER wait-for-device
- Connect your phone.
- Does it recognize it?

Thanks alot dude

 

[dansharpy]

Should i have the phone connected for the first bit:

'Can you execute those commands please?
- adb reboot-bootloader
- fastboot -s SERIALNUMBER'

Or connect it when it says 'waiting for device'?

The second thing you asked me to do comes up saying adb version and then a long list of adb commands. It does this as soon as i press enter on the command, before i have a chance to connect the device. Then goes back to an empty command prompt 'c:\adb:>'

---------- Post added at 02:04 PM ---------- Previous post was at 01:55 PM ----------

Ok on the first bit you asked me to do;

If the device is connected: It doesnt allow you to type anything until it has rebooted into bootloader. So you cant type the 'fastboot -s SERIAL NUMBER' until its already in bootloader menu. EDIT: Sorry just tried it again but typing the command regardless of if it showed up on the screen, it did say <waiting for device> but boots into bootloader so quickly you have to type the commands really quickly.

If the device isnt connected: It just comes up saying 'error: device not found' after you press enter after the 'adb reboot-bootloader' command.

 

[claudenegm]

Should i have the phone connected for the first bit:

'Can you execute those commands please?
- adb reboot-bootloader
- fastboot -s SERIALNUMBER'

Yes, connect your phone then execute those commands.

The second thing you asked me to do comes up saying adb version and then a long list of adb commands. It does this as soon as i press enter on the command, before i have a chance to connect the device. Then goes back to an empty command prompt 'c:\adb:>'

are you sure you wrote it exactly the same with no typos?
it should be "adb -s SERIALNUMBER wait-for-device" where the serial number is your phone's serial number and without quotes for sure.
Make sure there is only one space when needed and wait-for-device is written eactly like that right after the space after your serial number.

Thanks

 

[claudenegm]

Ok on the first bit you asked me to do;

If the device is connected: It doesnt allow you to type anything until it has rebooted into bootloader. So you cant type the 'fastboot -s SERIAL NUMBER' until its already in bootloader menu.

If the device isnt connected: It just comes up saying 'error: device not found' after you press enter after the 'adb reboot-bootloader' command.

Can you execute the command "fastboot -s SERIAL NUMBER" and when it says < waiting for device >:
- Open your phone into HBOOT manually and press bootloader.
- Anything happens next?

 

[dansharpy]

ah, sorry didnt write the wait for device part, i thought that was what it should come up with after entering the command!

When entered properly the cursor waits under the command, then when i connect the phone it starts a new blank command prompt 'c:\adb>'

 

[claudenegm]

ah, sorry didnt write the wait for device part, i thought that was what it should come up with after entering the command!

When entered properly the cursor waits under the command, then when i connect the phone it starts a new blank command prompt 'c:\adb>'

hahah it's okay
That's exactly what I wanted to know thanks
I need to know one more thing about ADB please, can you try this:
"adb -s 1234566 wait-for-device" exactly as it is, and connect your phone.
Does the the wait cursor go away and starts a new blank prompt? or it just stays there?

 

[dansharpy]

Can you execute the command "fastboot -s SERIAL NUMBER" and when it says < waiting for device >:
- Open your phone into HBOOT manually and press bootloader.
- Anything happens next?

How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?

If you press vol- and power it just vibrates but doesnt load into HBOOT.

---------- Post added at 02:20 PM ---------- Previous post was at 02:17 PM ----------

hahah it's okay
That's exactly what I wanted to know thanks
I need to know one more thing about ADB please, can you try this:
"adb -s 1234566 wait-for-device" exactly as it is, and connect your phone.
Does the the wait cursor go away and starts a new blank prompt? or it just stays there?

It just stays waiting under the command, i assume for the device with serial 1234566?

 

[claudenegm]

How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?

If you press vol- and power it just vibrates but doesnt load into HBOOT.

Yes, that's what I meant, sorry
- Execute the command.
- Turn off your phone.
- Press Vol. Down + Power
- Press power down to select Bootloader.
- Connect your device, it should read on your phone FASTBOOT USB.
- What happens next on your PC? A new blank line shows or what?

It just stays waiting under the command, i assume for the device with serial 1234566?

Yea, that's exactly what I needed. I was checking if the wait-for-device is only for the right serial number or not, as my application needs to wait for the specific device until it restarts to begin executing the commands, so basically this is an easier way for me to wait for the device than by doing a loop, which takes more memory resources

 

[dansharpy]

How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?

If you press vol- and power it just vibrates but doesnt load into HBOOT.[/

Yes, that's what I meant, sorry
- Execute the command.
- Turn off your phone.
- Press Vol. Down + Power
- Press power down to select Bootloader.
- Connect your device, it should read on your phone FASTBOOT USB.
- What happens next on your PC? A new blank line shows or what?


Yea, that's exactly what I needed. I was checking if the wait-for-device is only for the right serial number or not, as my application needs to wait for the specific device until it restarts to begin executing the commands, so basically this is an easier way for me to wait for the device than by doing a loop, which takes more memory resources

Yep, it brings up a new blank command line when the device is in HBOOT.

 

[claudenegm]

How do i get into HBOOT with the phone plugged in still? Or do you mean execute the command, put phone into HBOOT and then connect phone?

If you press vol- and power it just vibrates but doesnt load into HBOOT.[/

Yep, it brings up a new blank command line when the device is in HBOOT.

Wow, you really helped me a lot
Thank you!

I just have one last question please, if you execute this:
"fastboot -s 1234566" does it wait even if you connected your device in hboot?

 

[dansharpy]

Wow, you really helped me a lot
Thank you!

I just have one last question please, if you execute this:
"fastboot -s 1234566" does it wait even if you connected your device in hboot?

Yes, it keeps waiting even if device is in HBOOT.

Ive just got to pop out for a while, ill check this thread when i get back though to make sure you dont need anything else.

 

[claudenegm]

Yes, it keeps waiting even if device is in HBOOT.

Ive just got to pop out for a while, ill check this thread when i get back though to make sure you dont need anything else.

Thanks a lot
That's all I needed to know anyways!

Thanks again, you really helped me out

 

[claudenegm]

v1.2.0.0 has been released!
Android Recovery Manager