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.

trouble with bootloader unlock

Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.

KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done

KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.

Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app

I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.

sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd

Hard Reset Not Working

Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?

If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk

Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked

coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk

luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.

HTC One china unicom 802w stuck in bootloader

Hi I think i messed up my phone and I defiantly seem to be needing some serious help
I was trying to s-off my phone with this guide.
I have the same exact phone as the one he is using in the guide. I download the zip file.
Then proceeded to do
a. Lock the device - [fastboot oem lock]
Click to expand...
Click to collapse
After I oem locked my phone "fastboot usb" changed to "fastboot" and my pc doesnt recognize the phone anymore.
Now when I turn on the phone It says "Tampered" "Security warning" "Relocked".
I can't boot into rom nor connect my phone to pc via fastboot.
I tried with Macintosh, Windows 8 and Ubuntu none of which seem to be working.
Any help would be appreciated.
Regards

locked in bootloop and adb wont connect, rom wont flash from sd error 21

Hi Community,
I was rooted and got some nasty popup virus, then I factory reseted through settings. Everything was fine, then I entered in my software "superuser" and he said he would reinstall something, then booom bootloop!
I tried factory resetting through fastboot didnt work;
I tried flashing stockrom, latest rom, downgrade rom and the error is the same:
Verifying update package...
E: footer is wrong
Update package verification took 0.2 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted
ADB doesnt recognize my device!!! guess because after rebooting I never re authorized usb debugging mode or oem..
What Can I do now? any help appreciated

Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Everything is described there.
If your Device is on Android One, don't take the Rom from the thread but from this link: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again

AdB dont recognize my device fastboot sees im plugged in but adb wont see the device

irongas said:
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
Click to expand...
Click to collapse
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands

screwyou00 said:
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
Click to expand...
Click to collapse
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..

irongas said:
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
Click to expand...
Click to collapse
Did you install Motorola fastboot drivers?
The menu what you talk about is Recovery. Look if there's an option to boot to bootloader. If not go down to reboot the device and keep VOL-Down pressed so it reboots to bootloader. There you can just use fastboot commands.

sleeptab said:
Did you install Motorola fastboot drivers?
I did, I used to workaround with adb and sending commands, but the command prompt would recognize my device, now, even in bootloader when I plug it in bootloader says: usb plugged in, but the pc wont see my device... im almost crying here lol
Click to expand...
Click to collapse

RESOLVED!
hEY i JUST looked in device manager and there was a driver issue, then I reinstalled the driver from the pc adb phone, and it came back to liiiife!!! I just followed the second sequence and boom its working
Thank you a looot guys!!! sorry being such a noob! =)
Have a nice one!!