Database Develop

[Q] Converting my ONE into a GE Android

So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?

elfrisi said:
So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?
Click to expand...
Click to collapse
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.

davewuvswaffles said:
If you've still got s-off and can use fastboot, you could just change your CID and install a GE ruu.
Click to expand...
Click to collapse
I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:

Try a different USB cable, or port, or a different computer..
Your phone says Fastboot or Fastboot USB?

Remove unneeded drivers
elfrisi said:
I do have the S-OFF, however, once I enter the Fastboot menu, Windows wont recognize the device and wont let me push anything. It gets stuck in "Waiting for device". Ive installed the latest Google USB Device drivers using the SDK Manager and nothing has changed. :crying:
Click to expand...
Click to collapse
If Windows PC can see phone in normal working state ( like MTP device / Android ADB / USB disk ect ... ) mean - you no need to worry - HW is OK, then try to use a small free tool called DeviceRemover and just clean unneeded ( wrong / old / damaged / ect.. ) FastBoot driver(s) from your system and then try again to connect phone in fastboot mode. Hint - use last tab "Display Mode" to select "Hidden / Deattached" devices - these that not work for you.

elfrisi said:
So, I unlocked my One, got the S-OFF (HBOOT 1.55), when I was pushing the zip file containing the stock GE ROM, it got stuck on "waiting for device". I've tried uninstalling the drives, and installing them again, but its not working. I can turn on the phone fine, but the Recovery is the Google Bootloader and I can;t seem to find a way to go back to the original HTC Bootloader since it wont let me push files while in the bootloader...
What can I do!?
Click to expand...
Click to collapse
You'll have to use a different computer, one running a pre windows 8.1 os.
Windows 8.1 only recognises fastboot for 1.55 or greater bootloaders at the moment.
I had the same situation and had to re-install windows 8 which was a bit drastic but solved this problem

If you're having trouble with the connection in Windows 8.1 like that your Phone does not get recognised, easiest solution get a Linux Live ISO on a USB stick.
Get Universal USB Installer from here http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Let it Download a UBUNTU Live ISO
Let the Programm install it on your USB stick and set the Persistent File Size to your liking
Boot from the stick
Open Terminal Window
Install "adb" and "fastboot" with .... sudo apt-get install android-tools-adb android-tools-fastboot
Connect the Phone and check if the Phone is recognised (fastboot devices or adb devices)
Do the update

Well, it was a driver issue. I did everything using the Mac OS X partition of my MacBook (for some odd reason I thought all this process was "exclusive" to Windows due to the exes and whatnot, but I was wrong). Now I am running the Stock Google Play Edition on my phone with no issues.

[Q] Can't use adb/fastboot while in bootloader, after flashing failed.

Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated

TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.

rocktv88 said:
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
Click to expand...
Click to collapse
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/

TomFader said:
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
Click to expand...
Click to collapse
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?

rocktv88 said:
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
Click to expand...
Click to collapse
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>

TomFader said:
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
Click to expand...
Click to collapse
Are you on S-off?
Anyway, I would do the RUU. restore your phone and try again with a good custom ROM. Did you check MD5 with the rom you download? You still can connect your phone with ADB. That mean your phone is not brick yet. : )

TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot

clsA said:
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
Click to expand...
Click to collapse
You are right, i can confirm hboot 1.54.0000 - i was flashing the RUU to convert my HTC ONE toa Google Edition.
So all I need is a windows 7 or lower pc to get fastboot running again?
That's good news, I would have searched for ages.

Yeah it's frustrating I know
If you use the 1.54.000 from the 4.4 GPe update it works also
Sent from my HTC One using Tapatalk

[Solved] Stuck on white hboot screen while downgrading

Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.

Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer

If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)

err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5

Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.

RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.

072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.

Troubles with my HTC One Mini 2

Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?

AzweL said:
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
Click to expand...
Click to collapse
The very first thing I recommend you to do, is to download the right recovery and install it via command
Code:
fastboot flash recovery recovery.zip
Let me know if you run into any further troubles.

AzweL said:
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
Click to expand...
Click to collapse
Hi,
Frist in boot loader check your OS version it should be something like 2.19.401.2 or lower than this.
NB: ALWAYS TRY WITH MORE THAN 75% BATTERY, AND THAT FOR ANY CODE TO WORK PROPERLY, MAKE SURE TO SELECT FASTBOOT BY POWER KEY IN BOOTLOADER
Anyway, if you can enter fastboot, then you have some chance of recovering your device and because you have S-Off it is going to be a bit difficult.
First download this stock boot file : https://mega.nz/#!lEAVwRSL!wrP2hi6GEYLeJaPf2ssZo9wCtSi7E4yfyUHgh3Q3XSs
Then place this file in the ADB folder, then run command :
To flash boot file command is:
Code:
- Fastboot Devices (this command is important to know if the device is connected and accepting and responding commands)
- fastboot flash boot boot_signed.mg (assuming this is the name you saved the file with)
- fastboot reboot bootloader
Also download Stock Recovery: https://mega.nz/#!gVJE1Bxa!6SwXStAD8p-XlnQiPkRcdNo_ITFD1ykn-tN6wIBVi1I
Place this in ADB folder and run command:
Code:
fastboot flash recovery stockrec.img // (assuming that is the name you have saved the file with), only after flashing this you will know if the device has any OS, if OS exists it will boot up.
fastboot erase cache
Attempt and let us know how it went...Good Luck

No PC connection with adb/sync, fastboot works.

Hi guys,
I am trying to help out a mate and unfortunately dont have much experience with HTC's.
This is where i stand...phone wont be recognized in normal boot, nor in TWRP, so adb is not working at all. FASTBOOT works.
i have been circling around with locking and unlocking the bootloader to try out all the methods of updating the system, RUU fails with error 155. when unlocking, supercid fails with some java error.
To get S-OFF, i definitely need adb to load the "much talked for" file, but that is impossible right now.
RUU normal way fails as i said above, so does FUU with rom.zip (found away to get it out of exe, so it is untouched) as soon as it "updates signatures" it'll fail, I even use the fastboot command with the renamed file firmware.zip ends up saying it cannot verify partition ...adding zip after flash command says file is out of size
I am on 4.20.651.10, and trying to get the latest package, and am out of ideas. I found out the hard way that if i lock back the phone, it wont boot to TWRP and nor on a modified system.
I am really not sure what to do, having adb on would've spared me a lot of trouble. Friend says the USB port has been changed twice, it is so odd to have fastboot and not even a single refresh in Device Manager when i plug the damn phone on...

There are more replies to question threads outside the Help section then in here...
Anyway, i lost fastboot too, and no idea why. tried in two pc's, one of them with 3 different os's, tried two macs, tried even an OTG cable with my other android phone, nothing.
I cant even relock the phone so i can update through the RUU ZIP in the sdcard, but that's a scratched off solution if no USB connection is delivered.
I even tried the S-Off unlocking file on /data/local/tmp, but it doesnt seem to execute from TWRP terminal, and ofc it wont through a booted system either...
I managed to install a custom rom since i have no OS, and tried the "AndroidHtcSync.apk" solution to no avail
i seriously hope anyone has the will to help me...
EDIT: port is definitely fine, as the phone charges from the charger, and fastboot shows "fastboot ac".
EDIT2: fastboot is back... renamed the zip in sdcard, now it fails flashing there too with "Device halted due to large image update fail"