Related
I started this thread as a constructive and positive place for those of us that have recently lost our G1's or ADP's. I am going to document all my settings, Radio version, Firmware, Build info, etc here and hopefully reverse engineer this issue until I have an answer. If anyone has any hardware engineering information on this device it would be greatly appreciated. I'm even willing to host a private forum from my site to work on this.
Thanks everyone for your continued hard work and Haykuro, you're still the man!
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Partioned Fat32/EXT2 1GB SDcard from t-mobile
Flashed RC29 via Bootloader .NBH file
Rooted with RC29
Updated to RC33
Flashed Hard SPL
Flashed JF v1.5 ADP Lucid MOD - did APPs2SD and Dalvik2SD
Flash 2.22.19.26I Radio
Flashed Grafitti Citrus Theme JFv1.50 Beta
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL.
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
ivanmmj said:
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
Click to expand...
Click to collapse
Goldcard as in a specialized SIM?
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
Goldcards as in a specialized SD card
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
MosquitoD4K said:
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Click to expand...
Click to collapse
This has happened to me many times when I didn't wipe (the PHONE ). Take the battery out, place back in and hold Home + Power to get into menu. Type alt + w to wipe, afterwards, alt + s to apply update.zip from sdcard, then Home+Back to restart. The first time loading, it can take up to ten minutes to get past the Android screen (mine took 7-10 minutes), so be patient.
Post back with any results.
ivanmmj said:
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
Click to expand...
Click to collapse
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you can bricking you phone. take patience and wait.
Good luck
ps:i change the final text for sir*mez
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
satru said:
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you and only you bricking you phone. take patience and wait.
Good luck
Click to expand...
Click to collapse
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone for my bricked phone, im just trying to find a solution. you are going to get this locked because of the bickering.
hey sir*mes was no my intentions blaming to anyone , i only want to say that all need to give more time to flash before take out the battery. only that.
i will do something for you , i will change the text, happy?
Good luck
sir*mez said:
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone im just trying to find a solution. you are going to get this locked because of the bickering.
Click to expand...
Click to collapse
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
I tried it and so far no luck...
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
ok but the phone wont go into bootloader. which is what im trying to get it to do. if i get it to bootloader i know i can fix it. even if it went to the recovery i could fix it. but I get nothing.
in order to create a goldcard for the dream it has to read the sdcard off fastboot which i cant get into.
d474rpr said:
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
Click to expand...
Click to collapse
Are you saying your screen doesn't turn on?
neoobs said:
Are you saying your screen doesn't turn on?
Click to expand...
Click to collapse
No, I'm saying it doesn't turn on.
d474rpr said:
No, I'm saying it doesn't turn on.
Click to expand...
Click to collapse
The same happens on Heralds when the imgfs is messed up. To fix it, we force it to go into the bootloader mode and it does turn on. I wonder if it's something similar.
I meantioned in the big main topic an idea though I dont think anyone saw it.
In the past for other phones I was able to make recoveries using the computer while it was in the boot loop.
Anyone with the brick, try to see what happens when you do this:
adb remount
After the "T-Mobile G1" screen shows up. See if it says mount sucessful. I would try though it does not stay on the screen too long for me, not only that it might work for me just because it continues fine so its inconclusive.
If you get lucky and it says remount successful, you could try this:
adb shell recovery
I am not sure of the commands to follow from there, but it might allow you to flash a different update.zip file from the command line. If you get lucky like that, look up the commands and see how that might go. There has to be a way to communicate to the hardware when that screen comes up. Its good that that screen comes up, because it means its not 'fried' so to speak, it just has a misconfigured loader which doesnt have the correct set of instructions (good point about the different types of boards, thats most likely the issue) for THAT board. I would go back to the one that worked previously.
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06img that I found on here on the root of my card, and it will never load it up.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Rooster85 said:
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
samcrac said:
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
Click to expand...
Click to collapse
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Sent from my Supreme Shift
notsointeresting said:
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Click to expand...
Click to collapse
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
samcrac said:
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
Click to expand...
Click to collapse
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
notsointeresting said:
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
Click to expand...
Click to collapse
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
samcrac said:
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
notsointeresting said:
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
Click to expand...
Click to collapse
Make it 2! Thanks for your help though!!!
Also Stuck In A Bootloop
samcrac said:
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06IMG that I found on here on the root of my card, and it will load it up (I'll see the blue loading bar and then the brown loading bar in the top right hand corner of the screen), but it then checks it again, and then goes back to the original screen for the bootloader.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Click to expand...
Click to collapse
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Ok .. HERE'S THE SOLUTION:
First off all if your S- ON it means you are NOT rooted
If you get stuck in a bootloop .. don't worry it can be fixed.
What you need to do is download PG06IMG.ZIP and place it on your sd card, you can access your sd card by going into recovery then mount section, then usb. This will allow you to move the file from your computer to the root of your sd card.
Once you do this be sure you back up any info you don't want to lose. Once you have the file in place, go back to fastboot ( hold vol down and power) it will read file and when it asks you to update press vol up. It will take a few minutes to update this will revert your phone back to stock but if you have an old recovery it will not do a full restore, it will only update the rom.
Once you get your phone back to working, I recommend updating your recovery by downloading Rom Manager and flashing the latest clockwork recovery. This problem happens usually due to an old recovery.
One other thing you can try if you do NOT want to reset your phone, you can try flashing a new kernal.
Sent from my PG06100 using Tapatalk
RUU won't work if your stuck in bootloop ..
Sent from my PG06100 using Tapatalk
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
flylike2kites said:
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk
Also if your phone can't be found its b/c you need to put it into diag mode .. ##DATA .. if you need more help google
tech-9 said:
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk
For the thread starter, the person that sold you the phone probably tried writing to the system partition with s-on. Since you can get to the bootloader, see if you can get into recovery. If you can, recovery can be seen in adb, even the stock recovery. From there, gingerbread root, plenty of guides out there, make sure you flash the misc.img, download the froyo downgrade zip (that pgimg09.zip or something like that, just search for it, but not with the numbers I just gave, those are made up.)
From there either flash the gingerbread zip or ruu, and goon with a unrooted life. Or follow one of the many guides to froyo root, and live the life of the rooted. Your choice.
For the second person with a similar issue, the same method will work for you (assuming you can get to recovery), gingerroot, froyo downgrade, and since you like being unrooted, just ruu or zip back to gingerbread.
Solution found enjoy, and just think, if root hadn't been discovered for gingerbread, you would be screwed right now, make sure to thank otaking.
I have the same boot loop problem. I tried using the PG06IMG.zip file and fastboot/bootloader screen says I have the wrong image. It's most likely because it's for 2.2 and I have 2.3. I also don't have any recovery. Is there a PG06IMG.zip for 2.3 or the like?
similar problem here
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
zdavidzz said:
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
Click to expand...
Click to collapse
Try downloading the zip again and re run it. Possibly a bad download?
Sent from my PG06100 using Tapatalk
also adb is telling me device not found. i think i might have to factory reset. is that crazy?
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
and... that didn't help
i'm downloading the zip again right now.
since i have s-on, will i be able to install it though?
i can get the file on the root of the sdcard with an adapter since i can't push from adb. and i can't temp root the phone because if i try a normal reboot i get this stupid boot loop. is there a way to get s-off through hboot on the phone?
i don't know why i didn't notice that first file was messed up, it was only 6MB.
Hey was looking for a little help or guidance.
The touchscreen on my HTC Sensation 4g stopped working. Everything else works, volume rockers, power button. Even on the home screen it shows the volume increase/decrease but none of the apps are touchable and the lockscreen won't unlock either.
I used to be on Cyanogen Alpha8 when this happened before. I flashed to alpha9 and it fixed the issue. This time nothing is helping. I wiped the phone a couple times now, including wiping the sd card even and have deleted/installed Cyanogen 7.1 alpha10 and Android Revolution HD a couple of time seeing if that could fix the issue. Apparently it's not the rom as neither worked.
Recovery and everything works fine, but even when I did a backup restore it didn't fix the issue. Is this hardware?
TLDR- Touchscreen and lower 4 android buttons do not respond. Physical buttons all still respond.
Is there some screen lock key that I enabled and don't even know about or something?
First it happened when phone was 10 days old, now it happened again 10 days later.
Thank you for any help.
If you remove your cover, you can se a "polished" square on the right side. Make sure that it has good contact with the small metal "plate" on the right side of your phone. It's the touch ground, and I've seen people resolve their issues by checking that.
There is a thread about this, I can't find it now though. Using my mobile. Search for "sensation touchscreen issues" or something like that.
Sent from my Sensation using xda premium
Yeah I've tried extracting it a bit to get better contact. It's not that the touchscreen stutters in working, it doesn't work at all. When I'm on the lockscreen and pull the ring on Android HD rom it doesn't budge even the slightest. No notion that it is recognizing any kind of touch input. Thanks for the suggestion, I'll post back if it fixes the issue somehow later but currently contacting that small little square better hasn't helped.
I've read up on a few touchscreen issues like that but couldn't find anything so thought to post on here. Thanks again for the tip but touchscreen still not working.
Veritasvii said:
Yeah I've tried extracting it a bit to get better contact. It's not that the touchscreen stutters in working, it doesn't work at all. When I'm on the lockscreen and pull the ring on Android HD rom it doesn't budge even the slightest. No notion that it is recognizing any kind of touch input. Thanks for the suggestion, I'll post back if it fixes the issue somehow later but currently contacting that small little square better hasn't helped.
I've read up on a few touchscreen issues like that but couldn't find anything so thought to post on here. Thanks again for the tip but touchscreen still not working.
Click to expand...
Click to collapse
Try doing the procedure from my sig. I'd suggest to discharge first, leave overnight with no battery, and charge with no touching... It's all in that thread.
But... I still haven’t heard of a case when the screen didn't work AT ALL. Perhaps your issue is a bit more drastic and can’t be fixed so easily :\
Tried it. Didn't work. Put in foil as well, that also didn't work.
Thank you for the suggestion though.
Touchscreen still does not function AT ALL, with or without the back cover on so it's not the usual grounding pin issue I think. Could a cable pop out somewhere inside the phone to disconnect touch feedback without disabling the actual screen? Anyone have any hypotheses?
I would like to exhaust all methods before cracking open the phone and voiding the little warranty seal just in case.
Very annoyed at this phone/htc. Thank you for all the help on here guys and gals.
If you already tried clearing all the cashes, flashing several roms and different kernels, than it's hardware. Take it to a service center... :/
same problem
hey, any luck on solving your problem? i have precisely the same problem with my htc sensation as well. was working perfectly but now it wouldnt respond to any thing at all. it wouldnt even let me use ruu to restore it back to the original firmware. i really dont want to crack it open. i have ordered a new battery touse to test it. will kep you posted. did you manage to solve yours?
fix for none working screen
Hi there " dude that started this thread V*****"
i have managed to fix my screen issue. it involves having to take the phone apart VERY CAREFULLY. The flex behind the screen sometimes comes loose. all you need do is just fit it back in. You have to be careful though as there is a possibility you might damage the phone. oh, doing this will VOID your warranty. look on youtube for how to take the phone apart. i just bought another one on eBay and am going to fix it. best of luck and let me know how you get on.
shelay said:
Hi there " dude that started this thread V*****"
i have managed to fix my screen issue. it involves having to take the phone apart VERY CAREFULLY. The flex behind the screen sometimes comes loose. all you need do is just fit it back in. You have to be careful though as there is a possibility you might damage the phone. oh, doing this will VOID your warranty. look on youtube for how to take the phone apart. i just bought another one on eBay and am going to fix it. best of luck and let me know how you get on.
Click to expand...
Click to collapse
So I have this issue as well. Can you tell me what exactly you did to fix it? What flex came loose? And what did you buy on Ebay to fix?
Thanks
I did this last night and managed to fix the touch screen. The flex is located on the underside of the top PCB, the one that has the little chip on the cable. Mine looked ok but I pushed it in gently and did a quick test just by booting the phone before putting it all back together.
If your screen looks fine but doesn't respond to touch at all then I suspect this is also your problem. Worked for me :thumbup:
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
I know this thread has been inactive for a while but just thought I'd mention I just had this problem of dead touchscreen and fixed it simple by squeezing my phone! I took the battery out and pressed all over in the hope of pushing in any loose cable and it is perfectly back to normal just thought I'd mention this to save any potential future sufferers from taking their phone to pieces!
Regards,
lifeisfaked
ditto
lifeisfaked said:
I know this thread has been inactive for a while but just thought I'd mention I just had this problem of dead touchscreen and fixed it simple by squeezing my phone! I took the battery out and pressed all over in the hope of pushing in any loose cable and it is perfectly back to normal just thought I'd mention this to save any potential future sufferers from taking their phone to pieces!
Regards,
lifeisfaked
Click to expand...
Click to collapse
I have had this issue twice! I have a Motorola droid 4, and the touchscreen simply goes dead. First time it happened, I had just hung up with Verizon Customer Service. I fixed it by changing the slider/touchscreen assembly off of a different D4. Now it's happened to that assembly too. I"m starting to think it's a software issue. I will try this fix however. Dry heat was suggested as a fix on a different forum. Hope this helps someone.
The only working solution i find that works perfectly for touchscreen problems
I have tried every single solution for touchscreen issues on this site. I have found one that is basically guaranteed to work here it is:
INSTRUCTIONS: (YOUR PHONE WILL NEED TO BE ALREADY S-OFF AND UNLOCKED FOR THIS TO WORK WHICH YOU CAN DO THEN RETURN TO THIS TUTORIAL)
YOU WILL NEED TO DOWNLOAD THEESE 2 FILES
Recalibration tool - http://www.mediafire.com/?akul70qy128lo3u
Revolutionary hboot - http://www.mediafire.com/?1ed2y87pld66638
1. Take the NBH file from the provided link, and place it on root of your SD Card.
2. Boot into bootloader, by turning off your phone and then while its off hold the volume down button and then hold down the power button until the bootloader comes on then release bot of the buttons.
3. Once you’ve booted into the bootloader wait a second and you will notice that it searches for and finds the nbh file that you put on your sd card, It will then proceed to flash it. Some instructions will appear on the screen very quickly for about 2 seconds asking you to hold the phone horizontally while it calibrates it. Do this quickly and follow the rest of the instructions.
4. You will now see a screen appear giving you 2 options. Run the first option by selecting using the volume button if its not already selected and press power to run the process then run the second one once it is complete. Then simply remove the battery from your phone to turn it off.
5. Once again using the button combination, boot into the bootloader and select recovery. Once recovery boots into clockwork mod, do a factory reset and wipe data as well as the dalvik cache. Then reboot your phone.
Your touchscreen should now be calibrated and working perfectly.
Do not forget to delete the nbh file from your sd card once you’re done so it does not auto flash next time you go into your bootloader.
IMPORTANT!!!!!
If the process of flashing the nbh file does not work and gives you an error like this
“Security fail! Update fail! Press <POWER> to reboot.”
This is because the firmware is not the right one needed to flash the file and this can be corrected by flashing the Revolutionary hboot v 1.27.0000 following these instructions:
1. First make sure that you deleted the nbh file from the sd card root.
2. Place the file named “PG58IMG.zip” at the root of your sd card.
3. Power off your phone and use the button combination to boot into the bootloader.
4. The file will be detected and automatically start to flash, follow any onscreen instructions if necessary until this process completes.
5. Once this completes your phone should boot so that you can delete the zip file from your sd. If the phone is taking too long to boot you will need to remove the battery then the sd card. VERY IMPORTANT “With the sd card out of the phone” you will need to boot into the bootloader once more and enter recovery and factory reset the phone as well as wipe the data and dalvic cache.
6. Now the phone should be powered down and the turned back on. After the phone is finished booting up you should then replace the sd card and use whatever file explorer you have to delete the zip file from the root of the folder so that it does not autoboot the next time you enter the bootloader.(or you can do this whole step by deleting the zip file using a card reader and your computer)
7. You have now successfully flashed the correct firmware/hboot which is the revolutionary hboot required for the recalibration tool to work. Now you can try to reflash the calibration tool following the instructions at the very top of this tutorial again with the nbh file and it should work since I had to go through all this for mine to work and now my phone touchscreen work like a charm and is in perfect working order.
8. Thanks. I do not take credit for this fix, I have simply made a detailed explanation of how to get it to work as intended by this user on XDA http://forum.xda-developers.com/showthread.php?t=2437293
hugo2690 said:
I have tried every single solution for touchscreen issues on this site. I have found one that is basically guaranteed to work here it is:
INSTRUCTIONS: (YOUR PHONE WILL NEED TO BE ALREADY S-OFF AND UNLOCKED FOR THIS TO WORK WHICH YOU CAN DO THEN RETURN TO THIS TUTORIAL)
YOU WILL NEED TO DOWNLOAD THEESE 2 FILES
Recalibration tool - http://www.mediafire.com/?akul70qy128lo3u
Revolutionary hboot - http://www.mediafire.com/?1ed2y87pld66638
1. Take the NBH file from the provided link, and place it on root of your SD Card.
2. Boot into bootloader, by turning off your phone and then while its off hold the volume down button and then hold down the power button until the bootloader comes on then release bot of the buttons.
3. Once you’ve booted into the bootloader wait a second and you will notice that it searches for and finds the nbh file that you put on your sd card, It will then proceed to flash it. Some instructions will appear on the screen very quickly for about 2 seconds asking you to hold the phone horizontally while it calibrates it. Do this quickly and follow the rest of the instructions.
4. You will now see a screen appear giving you 2 options. Run the first option by selecting using the volume button if its not already selected and press power to run the process then run the second one once it is complete. Then simply remove the battery from your phone to turn it off.
5. Once again using the button combination, boot into the bootloader and select recovery. Once recovery boots into clockwork mod, do a factory reset and wipe data as well as the dalvik cache. Then reboot your phone.
Your touchscreen should now be calibrated and working perfectly.
Do not forget to delete the nbh file from your sd card once you’re done so it does not auto flash next time you go into your bootloader.
IMPORTANT!!!!!
If the process of flashing the nbh file does not work and gives you an error like this
“Security fail! Update fail! Press <POWER> to reboot.”
This is because the firmware is not the right one needed to flash the file and this can be corrected by flashing the Revolutionary hboot v 1.27.0000 following these instructions:
1. First make sure that you deleted the nbh file from the sd card root.
2. Place the file named “PG58IMG.zip” at the root of your sd card.
3. Power off your phone and use the button combination to boot into the bootloader.
4. The file will be detected and automatically start to flash, follow any onscreen instructions if necessary until this process completes.
5. Once this completes your phone should boot so that you can delete the zip file from your sd. If the phone is taking too long to boot you will need to remove the battery then the sd card. VERY IMPORTANT “With the sd card out of the phone” you will need to boot into the bootloader once more and enter recovery and factory reset the phone as well as wipe the data and dalvic cache.
6. Now the phone should be powered down and the turned back on. After the phone is finished booting up you should then replace the sd card and use whatever file explorer you have to delete the zip file from the root of the folder so that it does not autoboot the next time you enter the bootloader.(or you can do this whole step by deleting the zip file using a card reader and your computer)
7. You have now successfully flashed the correct firmware/hboot which is the revolutionary hboot required for the recalibration tool to work. Now you can try to reflash the calibration tool following the instructions at the very top of this tutorial again with the nbh file and it should work since I had to go through all this for mine to work and now my phone touchscreen work like a charm and is in perfect working order.
8. Thanks. I do not take credit for this fix, I have simply made a detailed explanation of how to get it to work as intended by this user on XDA http://forum.xda-developers.com/showthread.php?t=2437293
Click to expand...
Click to collapse
I tried this on my droid 4. I followed the directions for the .nbh file, and when i got into the bootloader, nothing happened. it ended up booting normally. so I tried the .zip file. same thing, I got into the bootloader, nothing happened, it timed out and booted normally. I am at a loss as to what I did wrong. any suggestions?
KrellaKrentoshi said:
I tried this on my droid 4. I followed the directions for the .nbh file, and when i got into the bootloader, nothing happened. it ended up booting normally. so I tried the .zip file. same thing, I got into the bootloader, nothing happened, it timed out and booted normally. I am at a loss as to what I did wrong. any suggestions?
Click to expand...
Click to collapse
I should have mentioned that this method only works on the HTC bootloader as it is very different from other bootloaders.
OK thanks for that update
HTC Sensation - Touch Screen Replacement
First you can to disassemble the phone and reconnect the Touch screen Flex cable. If this not help you, you must change it.
Video tutorial:
-----------------------------------------------------------------
HTC Sensation - Touch Screen Replacement
-----------------------------------------------------------------
Like most of the users here, my phone has been buttery smooth and fast for awhile thanks to our amazing devs. Today, something unexpected happened. I was attempting to get a screenshot of the lockscreen. I think I was successful, but when I checked the gallery, everything had corrupted icons on them. Ok, I will just reboot. Reboot, and I hear Linda speaking to me. I didn't catch it, but I know it had something to do with the SD card. 5 minutes later, my phone boots up and my card is nowhere to be found. I figure the whole card somehow got corrupted.
Now I originally started typing this because it looked like my phone wasn't going to boot past the galaxy S 4g logo, but after about 5 minutes it did. Now with the phone booted, my phone can't see the card at all. The only thing that comes up is the option to mount, but that doesn't work at all anymore. The previous time I restarted it before it hung at the boot logo, it showed up in my computer and opened to nothing and ended up freezing the computer for a second until I shut it down.
I need to format this card obviously, but can't see how I am going to do that if it isn't recognized. On top of that, I might as well use this as an excuse to reflash a new rom, but I have even more problems. None of my button combos work to get into recovery or download at all. I then figured I would use terminal emulator to get into it, as that has worked before, but the app won't install due to an "invalid package file" or something like that. I appear to be stuck in a very weird soft brick, and need some help.
Might have made some progress. I removed the sd card and installed terminal emulator on the phone. Hopefully it is going to reboot into recovery, but it is stuck at the boot screen again. Ill see in a few minutes if it makes it there. From there I can start trying to restore/wipe/format/etc...
Was able to get into recovery. Did a factory reset and wiped everything. Looks like it is still going to take more than 5 minutes to get past that boot screen though. Has anyone ever had this problem? Could my card be done for good? Unless I can find a way for my computer to recognize it, I don't know how I will format it.
I have seen them do this and in the end the card needed to be replaced. I haven't been able to figure out if it was the phone or the card but the ones I have seen like this I ended up flashing the software again from the factory flashing tool and the new card worked normally. If you need the factory flashing tool I can upload it but not til Tuesday when I go back to work. Let me know.
Sent from my MB855 using XDA App
yentlequible said:
Was able to get into recovery. Did a factory reset and wiped everything. Looks like it is still going to take more than 5 minutes to get past that boot screen though. Has anyone ever had this problem? Could my card be done for good? Unless I can find a way for my computer to recognize it, I don't know how I will format it.
Click to expand...
Click to collapse
If you have a card reader for your PC, download one of the Live distributions (Fedora, SuSE, Ubuntu, etc.) and, if you card is viable, you should be able to read the ext4 filesystem on it, get the files off, then format it to vfat.
Dboy352 said:
I have seen them do this and in the end the card needed to be replaced. I haven't been able to figure out if it was the phone or the card but the ones I have seen like this I ended up flashing the software again from the factory flashing tool and the new card worked normally. If you need the factory flashing tool I can upload it but not til Tuesday when I go back to work. Let me know.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I can still get the card to show up in my computer, but it will crash when I try and open it up. Ill see what formatting does in this state, but it guess I will just have to get a new card if I can't get this one working again.
stephen_w said:
If you have a card reader for your PC, download one of the Live distributions (Fedora, SuSE, Ubuntu, etc.) and, if you card is viable, you should be able to read the ext4 filesystem on it, get the files off, then format it to vfat.
Click to expand...
Click to collapse
I already lost the files, but I didn't have too much on there anyway. BUT, I did format it from My Computer, and it appears to be working fine now, luckily. I can see my few Android folders on there at least. Ill see how it works now.
yentlequible said:
I already lost the files, but I didn't have too much on there anyway. BUT, I did format it from My Computer, and it appears to be working fine now, luckily. I can see my few Android folders on there at least. Ill see how it works now.
Click to expand...
Click to collapse
Bummer you lost the files but glad you got it working. Best of luck.
Yeah man. I have seen this a few times. I try to backup my memory card at least once a week just incase. Sorry to hear about this bro.
Sent from my MB855 using XDA App
Thanks for the replies guys. Luckily, I didn't have anything that important on my card other than a few pictures, so it didn't turn out too bad. Ill be upgrading to the galaxy note in a few weeks anyway, so I don't really mind.
HTC Sensation 4g, on Bell (canada).
It has LeeDroid ICS v4.2.0
My phone will not turn on at all. At first I thought it was the common, dead battery, but its not. I have three batteries, and I even bought an external battery charger to isolate this issue. When I found that it wouldn't turn on, I had not tried to upgrade the firmware or anything for weeks, so a flashing issue is not it.
I cannot get into hboot, recovery, nothing. Nothing has ever shown on the screen since. I have tried for hours to get it into hboot by pressing the vol - and power buttons together, but nothing. I've tried doing it with different batteries, with and without my memory card, with a different memory card etc.
When I press the power button, or after I try to put it into hboot, it vibrates every 15 seconds or so, and this will not stop until either the battery runs out (gets very hot) or I take the battery out.
NOW, the odd thing is, is that I can sometimes get it connected to my computer, and the only thing that I can connect to the phone is fastboot. I cannot connect adb, and obviously htc sync won't work. I've tried everything to get adb working, but nothing works.
In conclusion, my phone is dead, and the only thing that works is command-line fastboot on my pc.
(I like to explain as much as I can in a main post so I get the best help possible) Also, please know that my phone worked perfectly (well as perfect as android gets) for WEEKS before this happened.
thanks guys!
Do you have a backup of any stage? If you can run fastboot you may still be able to save it. There is a thread for unbricking the sensation i'd start there and see if that helps. Can you boot to bootloader at all? If you can download an /RUU and extract the rom.zip, rename to PG58IMG.zip and put on the sdcard then power on using volume down and it will load the file just press power to flash it
bonesy said:
Do you have a backup of any stage? If you can run fastboot you may still be able to save it. There is a thread for unbricking the sensation i'd start there and see if that helps. Can you boot to bootloader at all? If you can download an /RUU and extract the rom.zip, rename to PG58IMG.zip and put on the sdcard then power on using volume down and it will load the file just press power to flash it
Click to expand...
Click to collapse
Could I flash the rom.zip in fast boot? I do have backups, I will try my luck at one of those.
But I cannot get into any recovery or boot loader at all.
I'm going to try this at work, and will let you Know!
I tried flashing the recovery, and boot using a RUU that I found. I still am getting in fastboot, but thats all. I cannot get to HBoot or any type of recovery.
Ever Found a solution?
Hi, did you ever found a solution to this problem? Because I'm having the exact same one.
Denobe said:
Hi, did you ever found a solution to this problem? Because I'm having the exact same one.
Click to expand...
Click to collapse
Sadly I didn't. I deemed it dead after trying a bagillion different things. I read somewhere that it may be a mobo issue, but to fix it, wasn't worth it when I had only a bit left on my contract. I upgraded to an iPhone 5 because android just wasn't for me.