Related
Hello,
I have a Vodafone Magic:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Click to expand...
Click to collapse
I'm using Ubuntu 9.04 and I installed the usb drivers (like here) and everything works perfectly with the phone in normal mode: "adb devices" shows the device.
But the problem is when I start in fastboot mode. Then "adb devices" doesn't show me anything. I enabled "USB Debugging" too.
I also tested it on Windows XP. I installed the 2 drivers (HTC Composite ADB and HTC Bootloader -and it appears in the device manager, so windows is using it-), but with the same problem: the device is not recognized in fastboot (perfect in normal mode). However, I can run fastboot ("fastboot boot recovery-new.img", for example) and the phone run it properly.
Any idea for windows or linux?
Thanks in advance.
try "fastboot boot <modded recovery.img>". After a while my device turns up on "adb devices"
Feynmannn said:
Hello,
I have a Vodafone Magic:
I'm using Ubuntu 9.04 and I installed the usb drivers (like here) and everything works perfectly with the phone in normal mode: "adb devices" shows the device.
But the problem is when I start in fastboot mode. Then "adb devices" doesn't show me anything. I enabled "USB Debugging" too.
I also tested it on Windows XP. I installed the 2 drivers (HTC Composite ADB and HTC Bootloader -and it appears in the device manager, so windows is using it-), but with the same problem: the device is not recognized in fastboot (perfect in normal mode). However, I can run fastboot ("fastboot boot recovery-new.img", for example) and the phone run it properly.
Any idea for windows or linux?
Thanks in advance.
Click to expand...
Click to collapse
Did you solve the problem plz? I got the same problem...
... adb will NEVER work in fastbootmode... Use the fastboot command in fastbootmode.
Amon_RA said:
... adb will NEVER work in fastbootmode... Use the fastboot command in fastbootmode.
Click to expand...
Click to collapse
Yeah I made the same dumb frakking mistake a few months back.
Try this, it worked for me on my ADB1:
1. Boot the phone normally.
2. Connect via USB and do NOT mount SD card.
3. Go into Device Manager and unistall the ADB device driver.
4. Re-Boot phone into fastboot mode (hold BACK button while powering up, connect USB and press BACK again - should now say FASTBOOT on device screen).
5. In device manager, right-click any device and scan for hardware changes.
6. Under USB Controllers there should now be a USB mass storage device - right click it and Install Driver (search automatically). The ADB driver should re-install.
7. Now try FASTBOOT DEVICES - your device serial should come up.
DeeEmmSee.
Dear forum members,
In the following A, B, C and D sections is described the flashing process
of the NON NoDo unbranded ROM: RUU_Schubert_Cingular_US_1.54.531.02_Radio_5.66.09.09a_22.46.50.21U_Signed_by_ansar
It is suitable for chevronWP7 unlock and can be upgraded to 7008 and then to 7392 NoDo OS and keep unlocking
See my relevant thread: [Guide How To]Pass ChevronWP7 Unlocker from 7004 to 7392 NoDo via zune, by ansar
A. Pre-Requisites
If your HD 7 is flashed with a ROM of the following release:
1. RUU_Schubert_Cingular_US_3.03.502.02_Radio_5.66.09.09a_22.46.50.21U
then you can flash the following NON NoDo unbranded ROM and when you like you can comeback to your previous NoDo ROM
In case your HD 7 is flashed with a different of the above 1 ROM but your Firmware version at your phone settings>about>more information
is of the form xxxx.yy.zzzzz.502 i.e. with characteristic value 502
then you can also flash the following NON NoDo unbranded ROM, but you can comeback only to the above 1 ROM
B. Downloading
You must download the following 2 ROMs:
1. Download this zip ROM file: RUU_Schubert_Cingular_US_1.54.531.02_Radio_5.66.09.09a_22.46.50.21U_by_ansar
2. Download this zip ROM file: RUU_Schubert_Cingular_US_1.54.531.02_Radio_5.66.09.09a_22.46.50.21U_Signed_by_ansar
Extract the downloaded zip ROM files with an unzip / 7zip utility in separate folders of your choice
C. Flashing Process
In order to successfully flash the provided ROMs you must follow these steps:
1. Flash the ROM of the above (B.1.) extracted zip ROM file
2. After flashing HD 7 will automatically enter again in bootloader mode
3. In the screen of your computer the ROMUpdateUtility will report an ERROR[270]
4. Ignore it and exit from ROMUpdateUtility
5. Now flash the ROM of the above (B.2.) extracted zip ROM file
6. After flashing your HD 7 will boot normally
7. Exit from ROMUpdateUtility and proceed with your brand new ROM
If you do not want them you can delete all operator apps, in order to have more free RAM
Beware, in WP7 deleting an application means it is deleted from ROM
D. ROM Flashing Instructions
In order to flash a ROM follow these steps:
1. Press and hold power-on/off button to power-off the phone
2. Press and hold volume-down button and then press power-on/off button to enter bootloader mode
3. When your phone enters the tricolor screen bootloader mode, release volume-down button
4. Connect your phone to your windows 7/vista pc/laptop with a usb cable
5. Verify that your phone will be identified and relevant drivers will be installed by windows os of your pc/laptop
6. After completion of (D.5.) above, check the usb message connection on your phone screen
7. To flash the ROM go to your pc/laptop folder where the downloaded zip ROM file is extracted
8. Double click on the ROMUpdateUtility.exe file and strictly follow the instructions on your pc/laptop screen
Till next version enjoy!!!
Regards, ansar
Thank you, ansar.
Would you like to create a non-NoDo Europe ROM with latest radio? So ppl can unlock and then update to NoDo with latest radion.
hoaisonongame said:
Thank you, ansar.
Would you like to create a non-NoDo Europe ROM with latest radio? So ppl can unlock and then update to NoDo with latest radion.
Click to expand...
Click to collapse
Hi,
Not yet, but maybe will be possible, we will see ...
Thnx for commenting and supporting!!
Regards, ansar
bro
Thank you, ansar.
Bro_toyota said:
Thank you, ansar.
Click to expand...
Click to collapse
Hi,
Thnx for supporting!!
Regards, ansar
Hi, i can't update... it stays on 0% and then it shows me Error 260 which is Comm Error... but the usb is fine, and i tried in the 3 usb ports of my pc... so, what could it be?? thanks.
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
EDIT: Now it shows error 262...
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
i upgraded it to 7392... does it have to do something with it??
ZeroCool11 said:
Hi, i can't update... it stays on 0% and then it shows me Error 260 which is Comm Error... but the usb is fine, and i tried in the 3 usb ports of my pc... so, what could it be?? thanks.
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
EDIT: Now it shows error 262...
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
i upgraded it to 7392... does it have to do something with it??
Click to expand...
Click to collapse
Hi,
Do you start from tricolor screen in bootloader?
Regards, ansar
Thank you for this rom, great work!
For anyone wondering, if you have the HD7 S with AT&T, flash this rom, chevron unlock your phone, apply registry hack to keep phone unlocked, then update through zune to get back to NoDo
Hi guys,
I'm having problems unlocking bootloader.
The phone enter into fastboot mode but when I type "fastboot oem unlock-go" in the cmd of windows it doesn't recognize my device.
I have installed Minimal ADB and Fastboot and I have installed ADB Driver installer too but it doesn't recognize the device.
Can anybody help me with this please?
I need to unlock it because I want to root it.
Thanks
Have you tried unplugging and replugging when the phone goes into fastboot mode?
I just got my pro 3, did the OTA to the .19 software and unlocked and rooted just today and my girlfriend's very very fresh windows 10 install.
If that doesn't work just delete the adb driver, replug the device and windows should install the same drivers I used.
Hello!
I have a very big problem. My LG Leon H340N is "bricked" totally, there is only fastboot mode in phone, nothing else.
The problem is that fastboot is not working, when i try to execute some commands it all the time gives me answer: FAILED(Unknow Command) and i don't know how to fix this, i don't have access to download mode, i don't have access to hard reset menu, i don't have access to recovery mode, only fastboot
Could somebody help me ?
How did you get into fastboot mode?
I connect device and laptop via USB and device is starting into fastboot mode automatically.
When device is connected i open cmd (run as administrator) and C:\ cd adb = C:\adb> fastboot devices - and it shows me my device connected as fastboot device then I try to execute some commands but it always gives FAILED(UnknowCommand). The fastboot drivers are installed - original google drivers from android sdk. I'm using Windows 7 Home Premium, i try execute some commands on other laptop with windows 7 starter but the same thing - FAILED(Unknow Command).
Thank you for reply, Regards
Flash the version MS34510d_00
I don't have MetroPCS version it's h340n. And i can't flash anything, because fastboot is not working
Install android 5
Dude, i know, i want to install android 5 but you don't see that fastboot in my phone IS NOT WORKING ? every time, when i try to exec some commands it gives me: FAILED(UnknowCommand)
for mode download
Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!