Related
Hey guys, I tried unlocking my phone but I think I ruined everything LOL.
Basically now, the phone only boots to the AT&T screen and restarts, over and over. Only turns on if connected to USB.
I followed the Kaiser Sim unlocker instructions all the way till like the 8th step and this happened. I installed the HARDSPL OLIPROF, it shows it on the tri color screen.
I can still bring it to the tri color screen, but when I connect it to computer it doesn’t show the active sync green screen (stays gray). I ran the sim unlocker again, it went to 100% complete, but phone still doesn’t turn on.
When I try to do a hard reset it stays click send, when I click send, nothing happens. I don’t know what to do. Did I permanently ruin the phone? I’ve searched Google for the past 3-4 days still can’t find an answer so I decided to post here for some help. Anything will be helpful thank you.
Your phone is fine. This part of the FAQ applies, I believe:
"*Put your phone into Bootloader and update to a 6.1 Rom first if you get a black screen after Flashing the Patched Radio*"
I had the same problem. Flash a generic 6.1 ROM such as _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship, then repeat the unlocking procedure. Instead of a blank screen, you'll see the correct prompts on your phone to complete the unlock.
thx 4 the info. i was gettin ready to try to unlock my tilt.
Uracil said:
Your phone is fine. This part of the FAQ applies, I believe:
"*Put your phone into Bootloader and update to a 6.1 Rom first if you get a black screen after Flashing the Patched Radio*"
I had the same problem. Flash a generic 6.1 ROM such as _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship, then repeat the unlocking procedure. Instead of a blank screen, you'll see the correct prompts on your phone to complete the unlock.
Click to expand...
Click to collapse
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
I downloaded that rom. It completed. The phone is still in the same condition. Wont even turn on unless its pluged to usb and when its plugged in usb it wont pass the AT&T screen(restarts over and over). Did i install an incorrect rom?
Also, theres no sim card or sd card in it. Does that matter for now?
Sorry for posting 3 times. But the second the rom completes, the phone automatically restarts, so I don’t have a chance to do anything. And active sync doesn’t detect it
Try flashing through SD card. Check Wiki for more details on how!
Also take battery off, wait 10 secs, and put if back on. Make sure the batter is charged as well.
you should have askdd in that thread as your question doesnt warrant the starting of a new thread. go back and ask there and good luck
Hi all..
I'll get directly into the scenario..
HardSPLed (1.17) my HTC Snap device ->
installed [WM6.5 STD 21854][Build 3VO.2.50.112509] works perfectly but I wanted to get back to the original WM6.1 ->
went back to WM6.1 successfully, after a while the official WM6.5 ROM realesed by HTC ->
downloaded it ->
tried to install it, everything goes well till the upgrade indicator reaches 29% and hang for no reason and giving me a 262 error after a while!!! then I followed instructions to recover the upgrade process as shown in the upgrade application then it hangs again at point 29% giving me the same error!!!!
I tried many times the steps of recovering and the same thing happens.. I'm confirming that my usb cable is working good and Windows Mobile sync application works great.
So I decided to install the 3VO.2.50 version again since I had a dead device and surprisingly everything works fine with the cooked version..
Now the problem is I need to install the new HTC OFFICIAL ROM and I can't do this... i've followed many topics here that nearly the same my problem but there is nothing except the frustration now i stucked in the coocked ROM and can't install the official ROM nor getting back to the original WM6.1 version
Any help guys will be much appreciated ..
Thanx in advance..
See this thread, follow the directions of the last post.
http://forum.xda-developers.com/showthread.php?t=586827
I have had the same issue installing WM 6.5 official ROM from HTC on mine. I followed the recovery process around 6 or 7 times before succeeding. it's kind of frustrating, but it worked in the end.
Thanks for help..
After walkingthrough sikkboy626 link i was able to install the official WM6.5 ROM
But after the upgrade process ends successfully the device restarted and only shows a black screen with 'smart mobility' and at the down left of the screen there is a B G R D letters, beside each of them there are some kind of numbers (in orange color)
Then it just hangs !!!!
Any clue guys ???
abdelaleem said:
Thanks for help..
After walkingthrough sikkboy626 link i was able to install the official WM6.5 ROM
But after the upgrade process ends successfully the device restarted and only shows a black screen with 'smart mobility' and at the down left of the screen there is a B G R D letters, beside each of them there are some kind of numbers (in orange color)
Then it just hangs !!!!
Any clue guys ???
Click to expand...
Click to collapse
that's the normal boot screen which indicates the radio version, rom version. just wait a few minutes for the phone to boot for the 1st time. if it still doesn't do anything, try re-flashing.
raphaelc said:
if it still doesn't do anything, try re-flashing.
Click to expand...
Click to collapse
Tried everything with no success ... tried to hard reset and didn't work, tried to flashing also didn't work, gave me 260 error message 'cause it's not seeing the device, my computer also doesn't see the device... !!!!!!
I'm about to crash my snap
abdelaleem said:
Tried everything with no success ... tried to hard reset and didn't work, tried to flashing also didn't work, gave me 260 error message 'cause it's not seeing the device, my computer also doesn't see the device... !!!!!!
I'm about to crash my snap
Click to expand...
Click to collapse
this is really a common error when flashing the ROM. try doing the recovery process as indicated many many times until success.
raphaelc said:
this is really a common error when flashing the ROM. try doing the recovery process as indicated many many times until success.
Click to expand...
Click to collapse
Can't flashing because the sync application nor pc seeing the device !!!!
abdelaleem said:
Can't flashing because the sync application nor pc seeing the device !!!!
Click to expand...
Click to collapse
in the recovery process, you don't need sync. read the documentation delivered with the ROM, they say how to recover.
Yes I know that i don't need sync in a recovery process.. i'm just proofing that the recovery/upgrade application doesn't see the device.. so i'm stuck here, i can't re-flash, i can't hard reset i can't do anything using my pc 'cause simply it doesn't know that the phone is connected to it...!!!!
abdelaleem said:
Yes I know that i don't need sync in a recovery process.. i'm just proofing that the recovery/upgrade application doesn't see the device.. so i'm stuck here, i can't re-flash, i can't hard reset i can't do anything using my pc 'cause simply it doesn't know that the phone is connected to it...!!!!
Click to expand...
Click to collapse
the only thing that i can tell you is to try the recovery process over and over until it connects correctly to the device. i have had the same issue as you : my phone wouldn't boot at all and was stuck at 29%. i re-booted my computer and followed the recovery process around 6 or 7 times as suugested on the screen, and then it worked.
abdelaleem said:
Yes I know that i don't need sync in a recovery process.. i'm just proofing that the recovery/upgrade application doesn't see the device.. so i'm stuck here, i can't re-flash, i can't hard reset i can't do anything using my pc 'cause simply it doesn't know that the phone is connected to it...!!!!
Click to expand...
Click to collapse
also, try to check this out : http://forum.xda-developers.com/showthread.php?t=324369
still the same after trying hundreds of times:
-Restarting my pc
-Re-installing Windows Mobile Device Center
-removing the battery to insure that it's shutdowned
-trying another pc with a deferent version of windows
don't know what to do else
I've now a useless dead phone
ok, so what do you get when you start flashing ? do you see the progressbar on the phone ? do you see a black screen ? please be more specific than "it doesn't work". detail each step you do and i will try to help.
Ok.. sorry for not being specific..
While trying the steps in my last post the screen of my Snap just showing a black screen written on it 'smart mobility' and at the down left of the screen there is a B G R D letters, beside each of them there are some kind of numbers (in orange color)
and it's showing this screen all the time, after restarting the device, while trying to flash... all the time nothing but the same screen appears, no progress bar, no tri-color screen no anything but the 'smart mobility' screen...
Thanks alot for tryin' to help
abdelaleem said:
Ok.. sorry for not being specific..
While trying the steps in my last post the screen of my Snap just showing a black screen written on it 'smart mobility' and at the down left of the screen there is a B G R D letters, beside each of them there are some kind of numbers (in orange color)
and it's showing this screen all the time, after restarting the device, while trying to flash... all the time nothing but the same screen appears, no progress bar, no tri-color screen no anything but the 'smart mobility' screen...
Thanks alot for tryin' to help
Click to expand...
Click to collapse
Ok :
1 - Remove the battery from your phone for a few seconds. Put the battery back in.
2 - While holding volume DOWN button, press the power button. The phone will enter "bootloader" mode and you will see a tricolor bootscreen.
do you see this screen ?
Yes... finally i see the tri color screen now...
what should i do after that??
and btw the pc realize the phone now do I have to try reflashing again??
Thanks alot raphaelc for helping me.. phone is working now perfectly after reflashing
Really appreciate your help..
no pb. i had really the same bad experience
Does anyone know how to recover and unbrick a Samsung Ace from a bad flash. My friend tried to upgrade to WM 6.1 using the official upgrade available from samsungusa.com.
All went well, so he says, and the device reset. Instead of loading up it became stuck on a bootloader screen which dispays the samsung logo and www.samsungusa.com.
All attempts to hard reset:
1. hold soft keys
2. press power button
3. press left soft key for clean boot.
have proved futile.
when it is connected to the USB cable it does not recognize the device.
Any help would be greatly appreciated.
P.S. I do not think that a call to Sprint Help center will help so I will have to find a community assisted solution.
first advice: after a flash, the initial boot takes very long compared to the normal boot - so let the device sit for 5-10 minutes after switch on, leave the room, have a coffee and wait.
Not sure about the upgrade process for Samsung, but the normal sequence is anyway that the device enters the bootloader when loading the new software.
So as long as you have the bootloader (are you sure it is the bootoloader and not some splashscreen?) nothing is really "bricked".
First make sure you put the device in bootloader mode, then you can just retry the flash with the device connected via USB sitting in boot loader. AS will not find it in this mode, but the flash program should after a while and then continue with the flashing.
tobbbie said:
first advice: after a flash, the initial boot takes very long compared to the normal boot - so let the device sit for 5-10 minutes after switch on, leave the room, have a coffee and wait.
Not sure about the upgrade process for Samsung, but the normal sequence is anyway that the device enters the bootloader when loading the new software.
So as long as you have the bootloader (are you sure it is the bootoloader and not some splashscreen?) nothing is really "bricked".
First make sure you put the device in bootloader mode, then you can just retry the flash with the device connected via USB sitting in boot loader. AS will not find it in this mode, but the flash program should after a while and then continue with the flashing.
Click to expand...
Click to collapse
Thanks Tobbbie, with the above I should be able to clarify:
But first my apologies for my newbie-ness. I did leave the room, went to be, got up and still no change. I am attaching a pic of what I see on the phone. It seems to be the splashscreen.
I am still able to access the hard reset screen using the procedure as shown in the original post, but this takes me nowhere either. Doing a hard reset takes me back to the logo screen with text : "Clean boot mode" included. this also sits for hours.
I was hoping someone would be able to post a solution of the form seen here: http://forum.xda-developers.com/showthread.php?t=689423
Sorry, cannot help any further here as I do not have this device. If the flash process from the PC does not recognize the connected device in this mode, try to disable USB connections in AS and retry flashing. Normally the flash-SW on the PC will terminate AS so this is not required - but just in case...
http://www.samsungmobileusa.com/i325/upgrade/
try to reinstall the usb drivers or try another pc! Do you use vista? try XP! Remove SIM and SD-Card
Did all the above recommended but came up blank. Still hoping for a solution from the community.
same problem,i tried to upgrade to wm6.1,on the middle,my pc restarted and iam struck.pls some body help me.
I have also same problem. if any one have tested solution plzzzzz share
I will b very greatful
I own a htc sensation 4G. The phone was S-off and was rooted. I am new to android but i did follow every procedure perfectly till the following happened.
I downloaded the ota update. Whilst updating it, the update was successful but now my phone just shows a blank display. The phones on, i can receive calls too but its a blank black display with no touch capable.
I tried to run recovery (PG58IMG), it was successful, but when rebooting same problem.
From boot(vol down + power), if i go into recovery, nothing happens, phone simply boots up
Same is the result with factory reset. No matter what i try to do, the phone accepts the command and boots up leaving me with an on phone and no screen.
Next i tried RUU , RUU_Pyramid_TMOUS_1.45.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_208218_signed and the RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_signed VERSIONS.
It runs but, when it comes to the point where it says, waiting for fastboot, There is a htc screen(white and black text) and the phone just wont go into fastboot. ten odd mins later i get a msg saying error 177, usb not found on my cpu and the only option on screen is exit. When i pull out the usb from the phone, for abt 5 seconds it shows the fast boot screen with RUU written below the basic information and it goes back to the htc screen. Only way to cancel is to pull out the battery...
Now everything that i could find on the forum and net, i have tried.. Please tell me if there is another option or am i doing something wrong???
My big problem at the moment is that im not in the states, am in India and cant take the phone to a service centre... PLS HELP
Any inputs guys?? really stuck here
Have u tried the tmous 1.50.ruu?
mugetsu666 said:
Have u tried the tmous 1.50.ruu?
Click to expand...
Click to collapse
RUU in general has a problem, the program keeps waiting for fastboot whilst i only have a screen with an htc logo on it. Only after waiting for a couple of hrs and disconnecting the usb cable, i get a fastboot screen with ruu written for abt 5 secs and it automatically goes back to the HTC screen..
I have tried 2 different ruu's and same end result.. so so..
Have u tried talking to a tech at HTC?
mugetsu666 said:
Have u tried talking to a tech at HTC?
Click to expand...
Click to collapse
i did today, they told me that everything possible that he would advice me to do, you have already done so. There is nothing left to be done. Get it over at a service centre to check for hardware defects or a possible re-programing of the phone.
The thing is, In india, htc sells like hot cakes, but their back-end service is horrendous. Service centers are not htc's but third party and they charge crazy sums for a customer doesn't have a 2nd option.
Hence am considering and trying all other options before going to a htc service center.
Is there anything that i have missed out in trying from my end???
Not that I know of, it sounds like the ota bricked ur phone and I'm not that good at that part. My knowledge only goes so far, sorry man.
Have you tried getting the PC to recognise the phone in fastboot?
If you have working fastboot then you can normally recover it.
Pull battery, reinsert, volume down & power then connect to PC.
Open cmd prompt as admin, cd to your fastboot folder, then enter "fastboot devices" and post the result.
Instructions on fastboot/adb if you are unfamiliar in the sticky guide to everything in dev forum.
Sent from my HTC Pyramid using xda premium
#mugetsu666 , i doubt the phones bricked, whilst everything is not working, aka fastboot, recovery, factory restore etc, the phone does boot and is on. How do i know this?? well, when i dial my no, the phone does ring but the screen is dead, as in black.. the 4 tabs below too r lit up but just no response..
#stringer7 , i did all of that already but whilst u asked me to post results, something just struck me.. when the phones put on usb, it charges and i can take it to fastboot too, but, on the task bar far right in devices, the pc is trying to search drivers for usb. Thats always on, even after leaving the phone on load overnight.. The pc is always searching for drivers and when i unplug usb, the no drivers found error does pop up..
"device driver software not successfully installed", is the windows error
Is the above info of any help?? considering the fact that i can take the phone on fastboot usb, but on the pc screen comes the error that usb not found or waiting for fastboot...
help
----------
Can you get a message from "fastboot devices" as above? If so you should be able to run the correct ruu to recover.
Sent from my HTC Pyramid using xda premium
The thing is, that the comps not reading the phone as a android device.
It charges the phone but doesn't read it. Hence cant do anything..
Any RUU doesnt move beyond the usb detection point leaving me with an "ERROR 170", cannot read usb..
Did the ota do this or does this look like an hardware error?
The 1.45 ruu of t-mobile seems like the most common one, but i cant even put that 1 to the test cause it just doesnt go beyond detection
Is there a chance that my problem could have cause a motherboard or other hardware problem???
I was updating my inspire 4g from the HTC's update sense 3.0. I got it directly from their site. My micro-usb cable apparently wiggled loose during the "Installing Bootloader" phase of the installation. Now my phone will turn on after about 20 minutes. It does not respond to me pressing the power button and I can not get it into recovery mode. It hangs at either a Black HTC screen or a White HTC screen. It's different each time it boots. When it boots into the white HTC screen it vibrates for a good 5 minutes then eventually boots up. My phone is not rooted. Is there anything that I can do to fix this?
EDIT: I just booted into recovery after holding the volume down and power button for like 5 minutes. Although, my volume and power buttons do not work in recovery mode :/
fix
235tylerlee said:
I was updating my inspire 4g from the HTC's update sense 3.0. I got it directly from their site. My micro-usb cable apparently wiggled loose during the "Installing Bootloader" phase of the installation. Now my phone will turn on after about 20 minutes. It does not respond to me pressing the power button and I can not get it into recovery mode. It hangs at either a Black HTC screen or a White HTC screen. It's different each time it boots. When it boots into the white HTC screen it vibrates for a good 5 minutes then eventually boots up. My phone is not rooted. Is there anything that I can do to fix this?
EDIT: I just booted into recovery after holding the volume down and power button for like 5 minutes. Although, my volume and power buttons do not work in recovery mode :/
Click to expand...
Click to collapse
I've same problem here
I'm searching for fix about 5-6 hours
If your phone boots up, it's more easy to fix it.
All you need now is to turn you phone fully to android desktop and follow this thread
tau.shadowchild.nl/attn1/?p=188
(I'm new here, i can't use "insert link" option, copy and paste link in browser)
or try this http://forum.xda-developers.com/showthread.php?t=1875134&page=2
Mine even doesn't boot up after 2 hours
Takes up to 20 minutes to enter in hboot, then up to 40 minutes to enter in fastboot
and then another 40 minute for fastboot usb
But still adb doesn't recognize device :/
Any help would be greatly appreciated
uNdea said:
I've same problem here
I'm searching for fix about 5-6 hours
If your phone boots up, it's more easy to fix it.
All you need now is to turn you phone fully to android desktop and follow this thread
tau.shadowchild.nl/attn1/?p=188
(I'm new here, i can't use "insert link" option, copy and paste link in browser)
or try this http://forum.xda-developers.com/showthread.php?t=1875134&page=2
Mine even doesn't boot up after 2 hours
Takes up to 20 minutes to enter in hboot, then up to 40 minutes to enter in fastboot
and then another 40 minute for fastboot usb
But still adb doesn't recognize device :/
Any help would be greatly appreciated
Click to expand...
Click to collapse
It sucks man! but I have finally booted my phone this morning. In order for my phone to boot it must be plugged into my computer for some reason?
is there a way to fix the bootloader while the phone is on and plugged into the pc? Or is there a way to boot into recovery without turning the phone off? BTW my device is not rooted.
EDIT: I attempted to redo the AT&T update and it failed because it took to long for my device to boot. So now, I'm attempting to root it again threw Ace Advanced Hack Kit. I know that this kit is no longer supported but I did use it in the past and it worked flawlessly. So now, AAHK is waiting for my device to boot. AAHK aparently doesnt care how long it takes so I guess thats a plus. My phone will eventually turn on. I'll post the results when/if it finishes
EDIT 2: AAHK aparently did not work. AAHK still says waiting for device after the device booted normally.
235tylerlee said:
It sucks man! but I have finally booted my phone this morning. In order for my phone to boot it must be plugged into my computer for some reason?
is there a way to fix the bootloader while the phone is on and plugged into the pc? Or is there a way to boot into recovery without turning the phone off? BTW my device is not rooted.
EDIT: I attempted to redo the AT&T update and it failed because it took to long for my device to boot. So now, I'm attempting to root it again threw Ace Advanced Hack Kit. I know that this kit is no longer supported but I did use it in the past and it worked flawlessly. So now, AAHK is waiting for my device to boot. AAHK aparently doesnt care how long it takes so I guess thats a plus. My phone will eventually turn on. I'll post the results when/if it finishes
EDIT 2: AAHK aparently did not work. AAHK still says waiting for device after the device booted normally.
Click to expand...
Click to collapse
If you try to run a RUU your device will probably end up bricked. You need to fix that using this:
http://tau.shadowchild.nl/attn1/?p=188
Any other method might leave you with a dead $200 device.
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
How to fix Corrupted bootloader with RUU
glevitan said:
If you try to run a RUU your device will probably end up bricked. You need to fix that using this:
Any other method might leave you with a dead $200 device.
Click to expand...
Click to collapse
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
bananagranola said:
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
Click to expand...
Click to collapse
Well, thank you guys. I'm in the process of reading everything. I messed my bootloader up by updating my phone btw not trying to root it. BUT thank you guys for the links. I'll post back with my results after I finish doing everything that the articles insist that I try.
uNdea said:
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
Click to expand...
Click to collapse
Your english is pretty good
BUT what you suggested is almost exactly what the above said link suggested. only he did not inform you about the Device manager things.
Thanks for the update
235tylerlee said:
Your english is pretty good
BUT what you suggested is almost exactly what the above said link suggested. only he did not inform you about the Device manager things.
Thanks for the update
Click to expand...
Click to collapse
I don't know, when i researched i didn't find bootloader fix with RUU, everyone warned about brick, so i was little confused when tried that.
It was my last hope to fix, because PD98IMG.zip way doesn't worked for me, neither "boot up and ADB" method. Some thread was about making goldcard and then flashing hboot like pd98img, but i hadn't goldcard. Also, i had S-ON and i think there was no way for S-Off
Anyway, thanks to xda and google :good:
Hope this would help you too ))
bananagranola said:
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
Click to expand...
Click to collapse
I have attempted what this PDF guide has insisted that I do and I get an error. The cmd prompt says the following
"C:\Users\mine\Desktop\help\tools>fastboot flash zip PD98IMG-HBFX.zip
< waiting for device >
send 'zip' (262 KB)...OKAY [ 0.080s]
writing 'zip'...FAILED(status read failed(Too many links))
finished. total time:1911.686s
C:Users\mine\Desktop\help\tools>'
EDIT: now it booted into something..idk. It says the following
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0019
NUCRIO-0437
RADIO-26.06.04.06_M
eMMC-boot
Dec 27 2010 14:47:30
RUU
NEVERMIND Aparently the article was true..I am a dumbass..I fixed it thank you guys
HElp
uNdea said:
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
Click to expand...
Click to collapse
My Bootloader hangs up when booted...and i have the same problem as u guyz mentioned! So plz help me
waleedbutt256 said:
My Bootloader hangs up when booted...and i have the same problem as u guyz mentioned! So plz help me
Click to expand...
Click to collapse
write detailed information, how u corrupted bootloader, what u tried to fix it and etc. If u tried my method, on which state it hangs up?
uNdea said:
write detailed information, how u corrupted bootloader, what u tried to fix it and etc. If u tried my method, on which state it hangs up?
Click to expand...
Click to collapse
flashed a froyo hboot on your HTC Inspire/DHD shipped with gingerbread. Phone takes forever to turn on, then it buzzes like cheap vibrator got hit by lightning for two or three minutes – then it finally begins to boot. I tried Using IAMADUMBASS FIX by attn1..which is specifically for this problem but my DHD hangs up in bootloader + when flashing unknown error occurs!
waleedbutt256 said:
flashed a froyo hboot on your HTC Inspire/DHD shipped with gingerbread. Phone takes forever to turn on, then it buzzes like cheap vibrator got hit by lightning for two or three minutes – then it finally begins to boot. I tried Using IAMADUMBASS FIX by attn1..which is specifically for this problem but my DHD hangs up in bootloader + when flashing unknown error occurs!
Click to expand...
Click to collapse
So was my phone too, and attn1 fix doesn't worked. Try that method that I've described above step by step and let me know result))
I've checked RUU download link and it's still working