Related
Hello,
I have a good buddy who was given a late prototype Dream from HTC, not a Google or tmobile branded device.
She is however unable to perform software updates via standard methods.
Is there anything that can be done for her? what info do yall need from her? the only thing we wont give is the imei and HTC serial #.
please let us know
Thank you
If it is one of the white dreams issued to Googlers for engineering/development purposes before the G1 launch, it's probably signed with test keys. In which case, get the prepackaged updates here:
http://forum.xda-developers.com/showthread.php?t=451090
Also, in case it doesn't have a recovery image with test-keys, you might try connecting to the phone with adb shell from your computer. do you get a $ prompt or a # prompt? If you get a $ prompt (non-root prompt), try typing "su", and see if it goes to a # prompt.
If you can't get root via the above, try rebooting the phone, and then once it's back on, type <enter>reboot<enter> on the keyboard (it doesn't matter what application is up, if any). If that causes the phone to reboot, then you can follow the instructions posted elsewhere to get root access on a normal pre-RC30 G1.
Finally, if none of the above work, try booting the phone into spl mode. Turn off the phone, and then boot it with back+power. If it boots up to a white screen with skateboarding androids then you can use the fastboot program to connect to the phone, which will allow you to flash a different image onto the phone. If you see colored bars instead of the white screen, you're out of luck.
ok here are the version numbers
DREA100 DVT2-1 32B
HBOOT-0.95.0000
CPLD-4
Radio-1.22.12.28
Sep 2 2008
Serial0
Also, she can reboot from the terminal in the background so I guess she is in luck, next step would be to place a dev bootloader I presume?
Hello,
Sorry, my english is pretty bad.
I have my htc relocked with stock recovery, and 4.0.4 official ruu SuperCID 11111111, today has left the official update to 4.1.1. After downloading and then install it to the phone off. Do not answer anything. No lights, no power + vol for HBOOT, the computer does not recognize it with "fastboot devices"
What happens? What do I do?
Thank you.
Your CID was htc_001 and somehow u bricked ut phone?
Through this tutorial i make SUPERCID and then only install 4.1.1 through "Software Update" in settings android:
Google Translate:
The phone must be switched on (normal) and connected to the PC
Open CMD and go to the directory where you have installed the ADB and type "adb shell" and press enter
Now type "su" and press enter, have root privileges
Now write the following: "dd if = / dev/block/mmcblk0p4 of = / sdcard/mmcblk0p4" and press enter, it overturned your sdcard
Type "exit" and again and enter "exit" and enter, it returns you to leave the command prompt
Then type "adb pull / sdcard/mmcblk0p4"
Now run the hex editor and open the file mmcblk0p4 we have it in the same folder where the ADB have
We seek offset 00000210 and the far right have followed the current cid our imei number
Change the current CID 11111111 (must have eight ones) and without changing the imei and save it as mmcblk0p4MOD, this will give us super CID. Make sure to have the same size you had before modifying the CID
Now we return to CMD and type the following "adb push mmcblk0p4MOD / sdcard/mmcblk0p4MOD" and enter
Type "adb shell" and then enter "su" and enter, again have root privileges
Now type "dd if = / sdcard/mmcblk0p4MOD of = / dev/block/mmcblk0p4" and enter now "exit" and again enter "exit" and enter and prompt again. To test if it works Now reboot into bootloader mode by typing the following "adb reboot bootloader" enter, and once on the screen type "fastboot oem readcid" and enter. If everything went right we have to leave we have super CID 11111111
It says "if everything went right" before flashing the zip did u check if you successfully changed to htc_001?
k1llacanon said:
It says "if everything went right" before flashing the zip did u check if you successfully changed to htc_001?
Click to expand...
Click to collapse
I have not used the ruu in .zip, was an official update 4.1.1 which launched today. I've updated the operating system itself.
The supercid 1 month ago I had changed, and if I checked on her day
I would NOT recommend to install the update if youre on supercid. There are some guys in a German forum with the same problem!!
Sorry man I don't know how to fix that now...
Sent by pacman
slainbybeats said:
I would NOT recommend to install the update if youre on supercid. There are some guys in a German forum with the same problem!!
Sorry man I don't know how to fix that now...
Sent by pacman
Click to expand...
Click to collapse
Believe that the guarantee it to be fixed? :crying:
I have the same problem ... my phone had even the supercid ....
You guys need to follow this guide to rewrite the hboot on your phone. Once you're done you should be able to recover by running a different RUU. It's your only option at this point.
http://forum.xda-developers.com/showthread.php?t=1990043&page=36
One question.
I cant make this:
"2. Download terminal emulator on your phone if it isn't installed already"
¿?
KeroG said:
One question.
I cant make this:
"2. Download terminal emulator on your phone if it isn't installed already"
¿?
Click to expand...
Click to collapse
You can skip that section. That section details how to brick your phone (placing it into qhsusb_dload mode). Your phone is currently already in that state. If it's not your screwed. Plug it in via USB to a Windows PC and you should see qhsusb_dload in device manager.
Continue on after "Enumerating your partitions" in the guide. I suggest posting your follow up questions in that thread as some of the most knowledgeable people watch and help people through the process.
dc211 said:
Your phone is currently already in that state. If it's not your screwed. Plug it in via USB to a Windows PC and you should see qhsusb_dload in device manager.
Click to expand...
Click to collapse
Yes, i see.
dc211 said:
Continue on after "Enumerating your partitions" in the guide. I suggest posting your follow up questions in that thread as some of the most knowledgeable people watch and help people through the process.
Click to expand...
Click to collapse
This tutorial is for ubuntu, I failed at step which has to detect the partitions (command: ls / dev / sd *) does not detect anything.
So I can not continue. I have read all the posts and some users with problems have been resolved by restarting, or trying several times, took many hours and no way intentadolo.
Why can it be?
I can not answer in the corresponding thread because I need to have 10 posts to be allowed.
KeroG said:
Yes, i see.
This tutorial is for ubuntu, I failed at step which has to detect the partitions (command: ls / dev / sd *) does not detect anything.
So I can not continue. I have read all the posts and some users with problems have been resolved by restarting, or trying several times, took many hours and no way intentadolo.
Why can it be?
I can not answer in the corresponding thread because I need to have 10 posts to be allowed.
Click to expand...
Click to collapse
your phone is in the QDL mode
when in the directory of your tools
do ./emmc_recover -r
then
ls /dev/sd*
until it pops up for a split second
Go to step 3
3. Now, hold power down on your phone for about 10 seconds*,OR until you see (QDL mode) disappear and let go, Then go to your second window and spam
So type in "ls /dev/sd* " and press enter. Then press up, then enter over and over while you are resetting the phone. Until your output changes. Look at the 2nd picture on the OP. He ran the command 7 times in a row before he got it. You need to do the same.
KeroG said:
Yes, i see.
This tutorial is for ubuntu, I failed at step which has to detect the partitions (command: ls / dev / sd *) does not detect anything.
So I can not continue. I have read all the posts and some users with problems have been resolved by restarting, or trying several times, took many hours and no way intentadolo.
Why can it be?
I can not answer in the corresponding thread because I need to have 10 posts to be allowed.
Click to expand...
Click to collapse
I did so all night long, didn't help. In Russia many phones died after official updating.
Problem in that isn't visible sections. How to restore them?
Same problem here, i guess, accidentally erase all in the phone with twrp, and i dont have OS installed (i have it JB with OTA update), phone is "empty".. Fastbootusb is working, phone is relocked..hboot 2.15.0000, SHIP S-ON RL
The question is, how to install RUU JB on my HOS? Any simply procedure?
Downloaded JB file, but that is zip file, not exe.. How to install zip on the phone? tnx
zujko said:
Same problem here, i guess, accidentally erase all in the phone with twrp, and i dont have OS installed (i have it JB with OTA update), phone is "empty".. Fastbootusb is working, phone is relocked..hboot 2.15.0000, SHIP S-ON RL
The question is, how to install RUU JB on my HOS? Any simply procedure?
Downloaded JB file, but that is zip file, not exe.. How to install zip on the phone? tnx
Click to expand...
Click to collapse
You have a other problem than described here mate. We are stuck in QHSUSB_DLOAD. We don't see a hboot or any sign of life. This as a result of flashing the JB OTA.
I Tried http://unlimited.io/qhsusbdload.htm and the HTC one V fix to pull it out of dload (which will only work if nothing else is wrong with your device). But still no sign of life. My gues will be it somehow messed up the instalation of our hboot?
I've been looking into the guide for downgrading your hboot aswell as it talks about unbricking. But its really confusing if you have no experience with ubuntu and don't follow every step....
dc211 said:
Go to step 3
3. Now, hold power down on your phone for about 10 seconds*,OR until you see (QDL mode) disappear and let go, Then go to your second window and spam
So type in "ls /dev/sd* " and press enter. Then press up, then enter over and over while you are resetting the phone. Until your output changes. Look at the 2nd picture on the OP. He ran the command 7 times in a row before he got it. You need to do the same.
Click to expand...
Click to collapse
After entering the command "sudo ./emmc_recover -r" I begin to continually put the command "ls /dev/sd*" for more than one minute and the display did not see any sd * 12 or anything. It is because my bootloader is locked?
If QDL mode disappears but then even put the command "ls /dev/sd*" reappears in QDL mode
KeroG said:
After entering the command "sudo ./emmc_recover -r" I begin to continually put the command "ls /dev/sd*" for more than one minute and the display did not see any sd * 12 or anything. It is because my bootloader is locked?
If QDL mode disappears but then even put the command "ls /dev/sd*" reappears in QDL mode
Click to expand...
Click to collapse
Yes I'm not usre if we can do that on a locked bootloader, If our hboot isnt corrupted. And I'm really glad your trying to recover your phone aswell but we can't do the final step either right?
12. Now we restore the original mmcblk0p4 that you should have saved as "bakp4"
Or doesn't that matter for us?
Vauix said:
You have a other problem than described here mate. We are stuck in QHSUSB_DLOAD. We don't see a hboot or any sign of life. This as a result of flashing the JB OTA.
I Tried http://unlimited.io/qhsusbdload.htm and the HTC one V fix to pull it out of dload (which will only work if nothing else is wrong with your device). But still no sign of life. My gues will be it somehow messed up the instalation of our hboot?
I've been looking into the guide for downgrading your hboot aswell as it talks about unbricking. But its really confusing if you have no experience with ubuntu and don't follow every step....
Click to expand...
Click to collapse
Sry for my post here..
I have win7 x64, I'm looking for right there where JB.exe, simple as that..
Consider other options..
Thanks for reply
Hi. I'm a newbie on these forums, so please be easy on me. My father recently decided that he wanted to enter the smartphone world and decided on a One XL. He bought it on eBay from a Chinese seller, so I'm pretty sure the One XL is the Chinese variant w/ the 2600 band for LTE.
I'm generally a BlackBerry guy (currently own a Z10), but have used all the phone OSes at some point. I've been pretty comfortable modifying my own BlackBerry, I use Linux at home as my main OS, and I'm also a computer science major studying programming (so I'm not in over my head here).
There are few things that I think would be cool for my Dad:
1) LTE speeds on T-Mobile. If not, 3G or HSPA
2) Android 4.4 KitKat
3) Sense 5
I'm pretty familiar with sideloading so that shouldn't be a problem (Flappy Bird).
I hope my Dad didn't didn't mess up for himself by buying the Chinese version if he wants faster speeds (than EDGE) on T-Mobile. I appreciate any help you may give. Thank you!
You should have no problems getting LTE on the device. You can have KitKat but it will be via an aosp ROM, not Sense. Sense ROMs for our device only go up to Android 4.2.2 and that's probably where they'll stay.
If you want to run a custom ROM on it just head over to htcdev and unlock the bootloader, then you can install a custom recovery, and from there you can install a custom ROM. I have detailed instructions for many of these operations in my How-To Guide For Beginners thread in my signature. You should also read the Evita FAQ thread in my signature, and bookmark the resource thread.
What are the bootloader details on the device? To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my One XL using Tapatalk
timmaaa said:
You should have no problems getting LTE on the device. You can have KitKat but it will be via an aosp ROM, not Sense. Sense ROMs for our device only go up to Android 4.2.2 and that's probably where they'll stay.
If you want to run a custom ROM on it just head over to htcdev and unlock the bootloader, then you can install a custom recovery, and from there you can install a custom ROM. I have detailed instructions for many of these operations in my How-To Guide For Beginners thread in my signature. You should also read the Evita FAQ thread in my signature, and bookmark the resource thread.
What are the bootloader details on the device? To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
Thanks! My dad can live without KitKat. Here's the bootloader details:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.16a.32.09.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
EVITA
Jaguarandine said:
Thanks! My dad can live without KitKat. Here's the bootloader details:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.16a.32.09.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
EVITA
Click to expand...
Click to collapse
Well you got really lucky and bought a device that's been modified in the past. It already has s-off and SuperCID (11111111). That's half the work done for you. What does it say above those lines though? It should say locked/unlocked/relocked and possibly also tampered.
Your firmware is a bit outdated so you'll need to update that, which will be easy because you already have s-off on the device. Before we go any further I need the other lines from the bootloader though.
Sent from my One XL using Tapatalk
timmaaa said:
Well you got really lucky and bought a device that's been modified in the past. It already has s-off and SuperCID (11111111). That's half the work done for you. What does it say above those lines though? It should say locked/unlocked/relocked and possibly also tampered.
Your firmware is a bit outdated so you'll need to update that, which will be easy because you already have s-off on the device. Before we go any further I need the other lines from the bootloader though.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
I'm at work now, and left the phone at home. I believe it said unlocked. I'll be able to work on this some more in a few hours. Thanks for all your help so far.
No problems. I'm subscribed to this thread so just pop in later and we'll sort you out. If it does say unlocked that leaves very little actual work for you to do, it's pretty much all been done. One thing you will need to do though is to install adb & fastboot on your PC, if you Google "minimal adb & fastboot" the first result will be an XDA thread which details how to do it, that's the easiest way. Another thing you'll need to do is install HTC drivers on the PC, the best way to do this is to install HTC Sync Manager and then connect your phone (first while booted into the OS, and secondly while in bootloader mode), this should install the drivers automatically. Once you've done that you test it by doing the following:
Navigate to the folder where adb.exe and fastboot.exe are located on your PC, shift + right click, select open command prompt here, then issue these commands:
Code:
adb devices
(While booted into Android)
Code:
fastboot devices
(While in bootloader mode, with "fastboot usb" showing on the phone screen)
Each command should return the serial number of your device. While you're issuing the adb command make sure your screen is on and unlocked because you may see a prompt asking to grant access which you need to confirm.
Before doing this you will also need to navigate to /settings/developer options on the device and enable usb debugging. If developer options doesn't appear in your settings you just need to navigate to /settings/about phone, then find the "build number" category and tap it about eight or so times, this unlocks developer options.
Sent from my One XL using Tapatalk
timmaaa said:
No problems. I'm subscribed to this thread so just pop in later and we'll sort you out. If it does say unlocked that leaves very little actual work for you to do, it's pretty much all been done. One thing you will need to do though is to install adb & fastboot on your PC, if you Google "minimal adb & fastboot" the first result will be an XDA thread which details how to do it, that's the easiest way. Another thing you'll need to do is install HTC drivers on the PC, the best way to do this is to install HTC Sync Manager and then connect your phone (first while booted into the OS, and secondly while in bootloader mode), this should install the drivers automatically. Once you've done that you test it by doing the following:
Navigate to the folder where adb.exe and fastboot.exe are located on your PC, shift + right click, select open command prompt here, then issue these commands:
Code:
adb devices
(While booted into Android)
Code:
fastboot devices
(While in bootloader mode, with "fastboot usb" showing on the phone screen)
Each command should return the serial number of your device. While you're issuing the adb command make sure your screen is on and unlocked because you may see a prompt asking to grant access which you need to confirm.
Before doing this you will also need to navigate to /settings/developer options on the device and enable usb debugging. If developer options doesn't appear in your settings you just need to navigate to /settings/about phone, then find the "build number" category and tap it about eight or so times, this unlocks developer options.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
So it looks like my Dad bought a used phone, right? With everything that's been done, I'm not sure if that's a bad thing or not. Since my Dad wouldn't be happy, I do think I'll keep this little detail between us though
4.2.2 + Sense is better, right? I wouldn't want to shoehorn KitKat on here if there are some features missing and the performance is not as good.
Btw out of curiosity, do these programs have a Linux equivalent? If not, it's cool, I have a Windows machine at home too.
Jaguarandine said:
So it looks like my Dad bought a used phone, right? With everything that's been done, I'm not sure if that's a bad thing or not. Since my Dad wouldn't be happy, I do think I'll keep this little detail between us though
4.2.2 + Sense is better, right? I wouldn't want to shoehorn KitKat on here if there are some features missing and the performance is not as good.
Btw out of curiosity, do these programs have a Linux equivalent? If not, it's cool, I have a Windows machine at home too.
Click to expand...
Click to collapse
Oh yeah, the phone is without a doubt pre-owned. Whether Sense or aosp is better is a matter of taste, and your dad won't really know which one is best for him unless he's able to play with each of them for a few days to get the feel of them both.
I had forgotten you mentioned having Linux as your main OS at home, and yes adb & fastboot are Linux compatible, they're actually much easier to install because they don't require drivers on Linux. Just Google how to install them on Linux, you should get a bunch of results with clear directions.
Sent from my One XL using Tapatalk
Well, I was wrong. The top line says *** LOCKED ***. Looking for the other programs now.
Edit: Took me a while, but I was able to find and get the drivers working in Ubuntu successfully
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT288W303498 device
After going into bootloader, and entering fastboot mode, I get the following:
Code:
[email protected]:~$ sudo fastboot devices
HT288W303498 fastboot
Ok, that's good. Your bootloader is actually in a relocked state but the previous owner has spoofed it to say locked, that's my guess anyway. Either way, your next step is to head over to htcdev and dole the directions there to unlock your bootloader. You can skip the installing fastboot part obviously.
Sent from my Evita
Ok, bootloader now says unlocked.
Jaguarandine said:
Ok, bootloader now says unlocked.
Click to expand...
Click to collapse
Cool. Now is the point where you need to upgrade the firmware on the device. This is pretty straight forward command line stuff using fastboot.
Download the firmware from here:
http://www.androidfilehost.com/?fid=23060877490004040
Place it in your fastboot folder (the folder where you have fastboot located on your PC). Rename it to "215firmware.zip" to make things easier later on. Open a command prompt from within that folder, or just open a command prompt and use the CD command to change directory to that fastboot directory. Connect your phone in fastboot mode and issue this command to make sure your connection is good:
Code:
fastboot devices
Once you've established a working connection (it'll show your serial number) you can start the process with this command:
Code:
fastboot oem rebootRUU
The phone will not boot into rebootRUU mode which is a black screen with the HTC logo. Now issue this command:
Code:
fastboot flash zip 215firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
Code:
fastboot reboot-bootloader
Verify everything was successful by looking at the hboot version and radio version in the bootloader screen. They should be as follows:
Hboot: 2.15
Radio: 1.31a.32.45.16_2
Now just reboot your phone by issuing this command:
Code:
fastboot reboot
Sent from my Evita
timmaaa said:
Cool. Now is the point where you need to upgrade the firmware on the device. This is pretty straight forward command line stuff using fastboot.
Download the firmware from here:
http://www.androidfilehost.com/?fid=23060877490004040
Place it in your fastboot folder (the folder where you have fastboot located on your PC). Rename it to "215firmware.zip" to make things easier later on. Open a command prompt from within that folder, or just open a command prompt and use the CD command to change directory to that fastboot directory. Connect your phone in fastboot mode and issue this command to make sure your connection is good:
Code:
fastboot devices
Once you've established a working connection (it'll show your serial number) you can start the process with this command:
Code:
fastboot oem rebootRUU
The phone will not boot into rebootRUU mode which is a black screen with the HTC logo. Now issue this command:
Code:
fastboot flash zip 215firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
Code:
fastboot reboot-bootloader
Verify everything was successful by looking at the hboot version and radio version in the bootloader screen. They should be as follows:
Hboot: 2.15
Radio: 1.31a.32.45.16_2
Now just reboot your phone by issuing this command:
Code:
fastboot reboot
Sent from my Evita
Click to expand...
Click to collapse
Very detailed instructions, thanks! everything Seems to be working well and Hboot and Radio have been updated.
Jaguarandine said:
Very detailed instructions, thanks! everything Seems to be working well and Hboot and Radio have been updated.
Click to expand...
Click to collapse
You're doing well, all that's left to do now is to flash TWRP recovery and install a ROM. You'll need to decide what kind of ROM you're going to flash because currently Sense ROMs and KitKat aosp ROMs need different recoveries.
For any Sense ROM you can use this recovery:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.3.0-evita.img
For any KitKat aosp ROM you need to ue this recovery:
http://www.androidfilehost.com/?fid=23252070760973615
Once you've installed the recovery you will need to make a backup of your current system just in case anything goes wrong in future, or if you want to use it again. Check the How-To Guide For Beginners thread in my signature for detailed instructions on how to do that.
Once you've done that you can go ahead and find a ROM you want to install and flash it. Our two develpment sections are as follows:
Android Development
(for Sense ROMs)
Original Android Development
(for aosp ROMs)
Once you've picked one you can download it and head back to my guide thread for full instructions on how to flash it.
@timmaaa your awesome dude, keep up the great help you offer :thumbup:
Sent from my One using Xparent Red Tapatalk 2
I started noticing this strange flickering on the sides of the screen. The screen is fine on a white background or when the brightness is turned down. But as soon as color is introduced on a white background, the flickering starts. Is this normal? And will it go away?
Jaguarandine said:
I started noticing this strange flickering on the sides of the screen. The screen is fine on a white background or when the brightness is turned down. But as soon as color is introduced on a white background, the flickering starts. Is this normal? And will it go away?
Click to expand...
Click to collapse
Was this happening before the firmware flash? Is it happening since the firmware flash?
---------- Post added at 04:00 AM ---------- Previous post was at 04:00 AM ----------
rc420head said:
@timmaaa your awesome dude, keep up the great help you offer :thumbup:
Sent from my One using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks buddy, appreciate it.
Well, I've never noticed it before. I am however, using the phone a lot more regularly since I started updating it. I looked around, and it seems to be an issue a number of people have with the screen. I'll deal with it for now and see if gets any better. Brightness levels won't be too high most of the time anyway.
I think I'll choose Sense 5 and start installing the recovery.
It could simply be a mismatch between the firmware and whatever software version is currently installed on it. Or it could be a hardware defect. You could try running an RUU to rule that out, but that would require a Windows machine with adb/fastboot plus drivers.
Sent from my Evita
Now it's gone away. I dunno. The phone otherwise seems fine. I'll keep observing and if anything happens, I'll report back here.
Recovery installation went well. Now on to flashing the ROM.
Out of curiosity, which ROM do you have on your phone?
One thing I did notice is that some ROMS recommend Jellybean should be installed. Is that an issue for this phone?
First off: I have an AT&T HTC one X
I am an almost total noob when it comes to this stuff so please bear with me here.
I had my roommate put cyanogenmod onto my phone when I got it and all was well until I moved to Asia and got an unlock code from AT&T to be able to use it over here. The unlock code wouldn't work and I found some stuff online saying that it might be a problem with cyanogenmod.
I followed a youtube instruction guide on how to get rid of the mod and everything was going fine until right at the end when I got a windows notification that the RUU had stopped working. I figured I would just do it again, but the actual program itself said it was successful. As I waited for it to reboot and load the roms, it started a loop. The loop is the white screen with the green htc letters for a few seconds and then it goes to a black screen with a phone logo in the middle. Around the phone logo is what looks like a recycling symbol except circular instead of triangular and on the screen portion of the phone logo there is an arrow facing down.
I assume this is just telling me I need to actually download some software on the phone, but it won't connect via USB and every time it starts up it says that the drivers were not successfully installed and htc sync manager doesn't recognize that a device is even connected. The loop continued and i tried to boot it back into the fastloader which did nothing. I held down the buttons as if to boot it into fastloader, but this time for about 15 seconds which took me to a battery charging screen and finally ended the loop.
I assume(hope) that since it's actually responding to input from the buttons that it's not irreversibly bricked. Is there any way I can get some version of android back on this thing? Any help would be much appreciated
Are you able to get the phone into the bootloader?
To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines. Also, exactly which RUU did you try to use?
Sent from my Evita
Happened to me as well..I reran ruu and then flashed a custom recovery. That symbol of charging with that arrow scared me. Lol
Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock
Swilli89 said:
Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock
Click to expand...
Click to collapse
This is why people should be learning to do things themselves. Now you've put him in a situation where he doesn't know what he's doing, very dangerous on a modified device with root access.
Sent from my Evita
the RUU i tried was the update from the htc site "HTC One X for AT&T Software Upgrade 1.29.2014"
the first five lines that appear on the phone are
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.18.0000
RADIO-1.35A.32.45.27
OpenDSP-v33.1.0.45.1128
also my computer doesn't recognize my phone is even plugged in at this point
Before you attempt to run the RUU again it's very important that we find out what your current CID is, if it's still SuperCID and you run the RUU you could brick your phone. To do this you're gonna need to have a working connection between your phone and your PC, so you'll need to make sure you have drivers installed, and you'll also need to have adb/fastboot installed. Do you have any drivers currently installed? If so, how did you install them?
Sent from my Evita
i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation
tpankfashank said:
i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation
Click to expand...
Click to collapse
Whoa. Whoa, whoa, whoa. Where on earth did you get that RUU? It isn't even for this device. Delete it now.
Drivers don't go on your phone, they're on your PC. HTC Sync Manager fits into the equation because it's the best way to get the drivers installed on your PC.
Uninstall HTC Sync Manager and the drivers that should be in the same sub-menu in the start bar on your PC. Uninstall any other phone software you might have on your PC.
Install HTC Sync Manager again, put your phone in fastboot mode, connect your phone to your PC, drivers should begin to auto-install.
Navigate to where you have adb.exe and fastboot.exe on your PC (we'll call this your fastboot folder). Shift + right click anywhere within that folder, select open command prompt here, issue the following command:
Code:
fastboot oem readcid
Please post the result.
Before we go any further, I need to be brutally honest with you. Once you have successfully run the correct RUU, which will return the phone to a stock configuration, leave it stock. Judging from your couple of posts here you're on a collision course to bricking your phone. You just don't seen to posses the slightest idea of what you're doing, couple that with owning a modified device, and the results are almost always disastrous. I'm not saying this to be cruel, I'm saying this because I'd hate to see you brick your device. The only way it's safe to have a modified device is if you're willing to put in the hard work of researching (days/weeks/months/years), and continuing to research to stay on top of this ever changing game.
Sent from my Evita
ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says <waiting for device> when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help
tpankfashank said:
ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help
Click to expand...
Click to collapse
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
Tpank, use the snipping tool on your computer to post a screen capture of your fastboot adb folder. its the folder that you are running the command prompt from (or should be).
BTW thanks Timaaaaa for helping my friend out. When I unlocked his phone we didn't know he would have the opportunity to move out of the US to Thailand so I figured I would be around to help with something like this. Thanks again.
Why would we need a screenshot of the fastboot folder?
Sent from my Evita
These guys are on a collision course. ?
timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
ok so it says "Fastboot usb". I am using the original htc usb cable. I'm not sure if it's a usd 2.0 port all I know is that it's an Intel 6 Series/C200 Series.
When I ran the command prompt it says:
<bootloader> cid: 11111111
OKAY [ 0.017s]
Ok, so you have a working fastboot connection now, right? The problem you face at the moment is that you can't run an RUU with your phone in the current configuration. S-on + SuperCID + jb RUU = brick. Your only real option at this stage is to do this:
-Unlock the bootloader at htcdev.
-Flash TWRP recovery.
-Flash a ROM to get the phone booting.
-Get s-off via Facepalm S-off.
-Run the correct at&t RUU to return the device to stock
-Change the CID back to the at&t CID.
-Relock the bootloader.
-Go back to s-on.
That probably seems like a lot of work but it's the only way for you to proceed. I have detailed instructions for several of those procedures in the How-To Guide For Beginners thread in my signature.
Sent from my Evita
So I can;t get past the first step because it's not recognizing my phone still. When I ran the first command in the command prompt, where it should have listed my phone it says "List of connected devices" and nothing underneath it.
How did you get the CID?
Sent from my Evita
I'm not sure why I can find the CID and not get it listed as an attached device. I tried to run the adb devices command a few times and then ran the fastboot oem readcid command in the same window and I could get the cid but still cant get it to recognize the device
Are you attempting adb commands while the device is in fastboot mode? They won't work, only fastboot commands will work there, adb commands work while the phone is booted into the OS. Use "fastboot devices" while in fastboot mode.
Sent from my Evita
Hi there,
i have a huge problem. As there was no warrenty left for my One S I thought about to change the firmware to CM11.
I have to admit that i don't have any experience in doing such things, but i thought, it couldnt go wrong if i follow a tutorial.
So at first i unlocked the bootloader via HTC website and istalled TWRP 2.7.1 (latest version). Everything went well, I placed the ROM into the phones root directory, started the recovery and then whiped it before choosing install and selected the file. After about 30 seconds the phone reported the step was successful and i pressed reboot. Then there was the HTC starting screen and then a black screen.
After that i had no reaction but the blinking buttons when i press the power button for a longer time. But it changes nothing. No normal boot. No access to fastboot. Only if i connect it to my PC there is an aditional device to see, but whitout any access.
I know I did wrong but i have no idea what or how to fix it. I hope you can help me.
ElDorado1993
Now i found a way to get access to fastboot again, but i dont really know what to do now.
Can you give me an detailed tutorial, for jelly bean or kitkat (dont matter) that is surely working now?
My main problem is that i can't copy my files into the root directory as i cant boot the phone.
Does it show up in computer connected devices?
If it does, download stock kernel and ROM and upload to phone and go into recovery[power +volume up while off] and flash them both kernel first.
Sent from my ZTE_N9511 using XDA Free mobile app
The problem is the phone wasnt ever shown as device on the pc (like a flash drive) since version 4.1 so I allways needed some tricks like airdroid. So i suppose i need adb commands to copy files and i dont have so much experience in doing this.
Do you know how to use adb?You don't need adb I just wanted to know to see if it shows up there and not on computer you simply need to install the drivers.Try holding down all 3 buttons to see if it powers down. Do what it says http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930 if works go into fast boot. Does it say locked or unlocked. If unlocked go herehttps://github.com/koush/UniversalAdbDriver and get the windows installer if your on windows.
Sent from my ZTE_N9511
I now found out how adb and fastboot are working, but the main problem now is, that it says the sdcard cant be mounted. I tried this tutorial http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 but i dont know how to do the first step. Du i need an extra file and where do i get it from and how to use it. As long as i dont get back this access, i couldnt install any OS. I tried also sideload. It was able to copy but cant install because of the missing sdcard access.
I hope you can help me to become my phone running again.
Go here http://m.youtube.com/watch?v=xWmnHwkDrKk but first type adb devices in cmd. If it shows ur HTC type adb shell and and type mount sdcard next to the "#" once it appears although you should be using the fastboot shell not adb commands.adb should only work on a powered on device or you can use fast boot in cmd while phone is in fastboot not recovery(you did say the phone can go into fast boot right?). Just make sure you got the right drivers and both fast boot and adb. You should get Koush's Universal drivers from my previous post since some phones have multiple drivers and MAY cause problems with cmd. Also HTC one S doesn't have expandable storage correct?
Sent from my ZTE_N9511
Wow. Now I incidentally soft bricked my phone again if you would believe it and nothing works this time.
Have you been able to fix?
Sent from my ZTE_N9511
Okay, i forgot to write but adb and fastboot are working on my Mac. I use the Mac because Win 8.1 has the known driver problems.
I tried a lot now, but i recognized maybe the main problem. My phone is still S-ON in bootloader. For sure thats the problem. Do I need to get rid of it and how do I do. The tutorial i used hasn't mentioned this step, maybe the person was still S-OFF.
The first thing i try now is to flash the original recovery, lock the bootloader and execute the original signed RUU to get back the original software first. Im going on holiday on tuesday and it would be a pitty without the phone. When I get it working i will leave it, and thy it again, when I'm back. Otherwise.......****
Use this tutorialhttp://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/unless its the one you used already. From boot loader you were supposed to have gone to fastboot.boot loader has to be unlocked.From fast boot you flash TWRP.IMG which happens to have a special adb side load feature under advanced options. There you upload another ROM and kernel.here is the full list of supported devices as I don't know what variant or carrier you havehttp://teamw.in/twrp_view_all_devicesAlso, a stock kernel is optional but it always seems to fix my problems.
Sent from my ZTE_N9511
Thank you. But I already did it like this. The issue is, than after using sideload successfully the installation fails because of the known "unable to mount storage" text. And i don't know what to do wrong.
Like I already said, my phone is still S-ON, but can this make a difference?
Now i got it to bring the stock ROM running again, and as I'm on holiday for a few days I'm happy it is working again.
But one thing is left. It seems like there is no 3G/HSDPA connection now, only EDGE. I dont know what went wrong. Did you hear about this problem.
By the way, my phone is the standalone version whithout any provider.
Search the forums about edge only. There is a huge thread on this.