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.
I have a T-Mobile MyTouch I purchased on Friday, which had an SPL of 1.33.006 (SAP30000). I followed the instructions in the following thread to unroot my phone:
http://forum.xda-developers.com/showthread.php?t=547133
I would have posted in the original thread, but the couple of times I've seen my issue come up, there are no answers given (or, sometimes it's "did you follow the instructions exactly?") so I didn't want to get it lost if others have the same problem. I've tried the instructions step by step (took me a while to get the GoldCard done because of a couple of inaccuracies in the instructions), but now it seems that I'm stuck with a 1.33.0009 (SAPP30000) SPL and need to install 32A ROM's - I can't seem to get it to 1.33.0005 no mater how many times I follow the instructions. And it also seems that I can't revert to a 32B situation, nor can I unroot the phone based on the last series of instructions in the Original Thread.
Has anyone else had this problem and if so, how did you fix it? Or is it unfixable? I'd like to be able to install 32B Hero ROM as only a couple of the 32A ones will install on my phone, and it's hard to tell what might be causing the slowdown (the lack of memory, or just the ROM itself). I now have Amon_RA's RAv1.2.1H ROM installed, and it works great, but it's the Hero ones I'd like to get.
Note that my main reason for unrooting was to tether the phone, but for now that goal has been set aside until I can determine how to proceed from here (although I might just give Azilink a try anyway while waiting for this to be resolved).
Any help would be appreciated.
I'm not sure if we had the same problem. I followed the instruction in installing the spl it says turn off after installing the spl.
- Once the recovery is booted wait a while
- Apply the update.zip (you are now flashing the 1.33.2005 SPL)
- Once the SPL is flashed you have to power off your device and boot it again in fastboot mode. <--I did not follow this line
after the flashing I pressed restart and let it do it's thing until a couple of restart/flashing and stucked with the vodafone bootscreen thats the time I removed my battery (just be sure it's done flashing) then go to fastboot you should see .0005 let me know if it works I'm pretty sure that's what happened to me
P.S. I believe you want to root you phone to tether right? not unroot?
jrherras said:
I'm not sure if we had the same problem. I followed the instruction in installing the spl it says turn off after installing the spl.
- Once the recovery is booted wait a while
- Apply the update.zip (you are now flashing the 1.33.2005 SPL)
- Once the SPL is flashed you have to power off your device and boot it again in fastboot mode. <--I did not followed this line
after the flashing I pressed restart and let it do it's thing until a couple of restart/flashing and stucked with the vodafone bootscreen thats the time I removed my battery (just be sure it's done flashing) then go to fastboot you should see .0005 let me know if it works I'm pretty sure that's what happened to me
Click to expand...
Click to collapse
Hey jrherras,
Thanks for that tip. I'll give it a try tonight (while possibly getting other suggestions along the way). I think I MAY have tried that, but I don't remember at which stage this happened. One time it said on the screen to reboot using the "Home+Power" reset (hard reset, I think), and re-flash the update. So I tried and got the same results.
So, just to be clear, what you're saying is at the third step above, instead of powering off the phone (by removing the battery), just choose the "reset device" option at the top of the recovery menu? Or are you suggesting to do the "Home+Power" reset? And it seems that you may have also re-flashed the SPL update a couple more times as well?
courtmagician said:
Hey jrherras,
Thanks for that tip. I'll give it a try tonight (while possibly getting other suggestions along the way). I think I MAY have tried that, but I don't remember at which stage this happened. One time it said on the screen to reboot using the "Home+Power" reset (hard reset, I think), and re-flash the update. So I tried and got the same results.
So, just to be clear, what you're saying is at the third step above, instead of powering off the phone (by removing the battery), just choose the "reset device" option at the top of the recovery menu? Or are you suggesting to do the "Home+Power" reset? And it seems that you may have also re-flashed the SPL update a couple more times as well?
Click to expand...
Click to collapse
Yes I flashed couple of times and thought I'm stucked at .0009 SPL until I decided to restart not turn off.
I pressed the 1st selection from the recovery which is "Restart device" and let it flash it self. If I'm not mistaken once you pressed restart you will see a flashing in progress and after a couple of restart when your stucked in the vodafone logo and no more flashing in progress that's the time you remove the battery to turn off After that you should have .0005 SPL pm me if it worked since I don't browse too much
Hey jrherras,
Thanks again for that info. I'll give it a try later on and update both this thread and you once I see if it does or doesn't work.
~CM
Seems that the extra reboot did the trick. I had misread the "Home+Back" to reboot as "Home+Power", and that's where my confusion set in (although the instructions in the original thread were not clear on this step). Right now, I'm flashing a 32B ROM and seeing how it goes.
Thank you very much for your help.
I wanted to go to the official ION with my Magic 32A, so first I flashed the update.Engineering-SPL-HBOOT-1.33.2010-signed.zip and that seemed to go fine, then restart into fastboot and applied the signed-google_ion-ota-14721.zip from the htc developer site and thats when the s**t started.
When restarting I get the "htc magic" slash screen and thats it. I cannot get into the fastboot console (home/power or back/power) in fact nothing seems to do anything.
Before I burst into tears, is there a solution to my problem?
This was a HTC badged unlocked phone that I have flashed roms before, but this attempt has gone horribly wrong....
Can you get it into bootloader?
VOLUME DOWN+ POWER ?
no, it buzzes once, shows the "htc magic" splash then nothing :-(
does the same thing with any of the key combinations I try...
no, it buzzes once, shows the "htc magic" splash then nothing :-(
does the same thing with any of the key combinations I try...
ghaywood said:
no, it buzzes once, shows the "htc magic" splash then nothing :-(
does the same thing with any of the key combinations I try...
Click to expand...
Click to collapse
edit : that is only system image and only for ion
does adb detect it?
you can try one thing
make a gold card
paste some ones backup (make sure its for 32A)
boot.img
system.img
recovery.img , etc
and then
try loading boot loader
i.e vdown + power
and check if ruu picks ur phone or not
mostly it wont
Thanks for the reply, I have a nandroid backup with the *.img files would they do for a gold card?
Also, I know this is n00b, but I an a bit confused with the gold card thing. Is there a howto for using via ubuntu?
Thanks
I have read the gold card creation, and it talks about getting the CID when the phone is on. Obvoiusly I cant do that
Is there a way to get this CID even though I cannot start my phone?
Did you check this thread:
http://forum.xda-developers.com/showthread.php?t=571457&highlight=unbrick ?
Been there, done that. Send it into HTC. They fixed mine for $20.00. Had to use my iPhone and actual ion for 10 days.
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.
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!