Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
I can help you out. Can you still go in Hboot?
Sent from my Desire HD using XDA
dnplee said:
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
Click to expand...
Click to collapse
Do not panic...although you did a factory reset and disabled usb debugging, you can solve your situation. Just flash the RUU (PD98IMG-GBx.zip) file you used to downgrade the phone. It has to be in the PD98IMG folder of the Hack Kit. Make sure that it is that file and no other. Rename it PD98IMG.zip and then put it in the root of the sdcard. Then boot in hboot and update pressing volume up. Let it finish....then you will have a working phone. Then re run the hack kit to Gain S-OFF and Root....if you can´t do it just hit the IRC Channel that is stated in the OP of the Hack Kit thread.
benydc, glevitan, thank you both for the offers of help and advice.
I eventually found my way to the IRC aahk support channel and was blessed to get the help of attn1, one of the ops there.
He helped me through my problem and now everything is as is should be. Thankfully I have a working rooted phone.
Everyone there was very friendly and helpful, not just attn1. He must have spent the last two hours or so juggling with helping out three users (probably more). We even got to make some friendly banter amongst ourselves.
Though I was freaked out initially, I am glad everything works now and from the support I got there, I am somehow not going to shy away from trying to learn about rooting.
I managed to save all the text during our conversation so when I get the time, I will try and build a simple but detailed walkthrough of how attn1 got my phone working again. I will post it here so that it may help others who find themselves in a similar position one day.
Many thanks you guys. This is a great community.
same problem,s-on,no recovery
hey there...ive got similar problem with u and i try putting the PG98IMG on the root of the SD card which i get from the folder from AAHK...but when i go to HBOOT and try to install the PG98IMG, it failed and it says MAIN VERSION IS OLDER ! what should i do?
hi
i have same phone whith you
2.3.5 sens 3.0
i used AAHK but the file name downloaded is "PD98IMG-GB2"
you can rename "PD98IMG" on "PD98IMG-GB2"
Related
So after what seemed to be the art of bricking my Incredible over the weekend (dead, black screen), I think we have found a fix for it.
This is what we did to bring the phone back to life:
** Please note: Make SURE you have the correct drivers installed. I used the modified Android ones.
1.) Download the Android SDK, and then fire up a command shell in the Tools directory
2.) Boot the Incredible into Recovery:
* Pull battery, then put back in
* Hold Power and Vol Down for 5 seconds
* Wait 20 seconds
* Hit Vol Down once
* Hit Power
* Wait 20 seconds
3.) Check to make sure that ADB can see it by typing adb devices into the command shell you opened earlier
4.) Type adb reboot oem-78 into the command shell. I let the phone sit for a few minutes.
5.) Run the RUU from Shipped-Roms, located here: shipped-roms.com/download.php?category=android&model=Incredible&file=RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe
Once the RUU finished running, my phone rebooted and my screen is alive!
Downloadding now I hope this works. I already called verizon and the replacement Phone should be here Wed.
let me know if this works for you, i worked with aracheon all last night and then was able to finally break it down and get it working this afternoon, if you need help let me know
Credit to be given where credit is due - I wouldn't have figured this out without Jobehonda's help.
I would not say "bricked" inc, just screen was dead because there were no drivers installed for SLCD. My phone was "OK", when i called my own number, it rings, vibrates etc, just i was not able to see anything.
What i did was just got the stock 2.2 PB31IMG.zip from somewhere around here, and using "timing" in my mind, i just repeated flashing process as usually. The only difference was that i did not see what i was doing. For the first time it failed, but i got lucky after second time, and my phone (scree that is) is back to life.
Now, i just have to root it again using caution this time....
Windows XP doesn't like RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe file name must rename to anything(.exe) shorter I used RUU.exe
fuzio1963 said:
I would not say "bricked" inc, just screen was dead because there were no drivers installed for SLCD. My phone was "OK", when i called my own number, it rings, vibrates etc, just i was not able to see anything.
What i did was just got the stock 2.2 PB31IMG.zip from somewhere around here, and using "timing" in my mind, i just repeated flashing process as usually. The only difference was that i did not see what i was doing. For the first time it failed, but i got lucky after second time, and my phone (scree that is) is back to life.
Now, i just have to root it again using caution this time....
Click to expand...
Click to collapse
Well, right. But the phone is effectively useless with the screen problem. The big guns are calling it an "SLCD Brick," sooo...
tjamscad said:
Windows XP doesn't like RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe file name must rename to anything(.exe) shorter I used RUU.exe
Click to expand...
Click to collapse
Depends on where you put it. You should be able to get away with dropping that on the root of your C drive and still keep the long filename.
Fixed It works it really works, Thank you Jobehonda and arache0n
tjamscad said:
Fixed It works it really works, Thank you Jobehonda and arache0n
Click to expand...
Click to collapse
Glad to hear it.
Awesome! Glad it worked for more than just one person!
arache0n said:
Well, right. But the phone is effectively useless with the screen problem. The big guns are calling it an "SLCD Brick," sooo...
QUOTE]
What's your point here?? You said "bricking my Incredible ", soooo......?
FYI, i just rooted my Dinc with unrev....3, got black screen with two white lines, (again). Flashed recovery fix, and all is goooood, this time.
G-night all.
Click to expand...
Click to collapse
the problem aracheon had is we accidently flashed the wrong image file to upgrade back to stock recovery when trying to load the correct flash file it was not working...not sure why. Either way, both seem to fix the problem.
Jobehonda,
I'm stuck with my Black screen SLCD Dinc as well, doing the same mentioned above, and when I tried following your instructions it hasn't worked out for me so far. I can't get past the "adb devices" thing. It tells me "devices not attached" or someting to that effect after running the command. I may be doing something incorrectly... Could you be of assistance? I also posted a comment to your "Droid Incredible is a Pile" post on your site. Looking forward to you helping me bring my Droid back to life...
Thanks!
Nevermind... I fixed my "SLCD Brick"!! I will post details later of how I did it...
tjamscad said:
Downloadding now I hope this works. I already called verizon and the replacement Phone should be here Wed.
Click to expand...
Click to collapse
Well, for what it's worth your replacement phone might be an AMOLED.
A week or two ago I got a replacement for the 3G issue and recieved another AMOLED.
OK, this is, what fixed mine:
-pull battery, then put back in
-hold power + vol down for 5 seconds, nothing happened...
-then hold power down for 5 seconds, got 1 vibration...
-then hold vol up + power for 5 seconds, and to my surprise, screen turned on and only had 1 option: Hboot
-then left the screen up and took my SDcard out (the battery cover was off already) and I went to the following thread (how-to-update-your-droid-incredible-to-leaked-android-2-2); and downloaded the "PB31IMG.zip" file from step 1 and copied it over to my SDcard. Please "google" the thread title above... I'm not allowed to post full links because I'm a new user.
-then I put the SDcard back in, pull the battery, then put back in
-hold power + vol down for 5 seconds
-Boots into hboot and select Bootloader
-PB31IMG.zip will start to install.
**Note** Your phone might reboot to either hboot or recovery after trying to install PB31IMG.ZIP, just get back to hboot and install again, when you get back to hboot you should notice its version .92 and S-OFF is still on, just install PB31IMG.ZIP again and all should be good. I believe at one point after it updates hboot it has to reboot to finish the install, so this might be what you are seeing.
-Finally it will reboot and you should see HTC Screen, Droid voice/Red eye will load, and you will have a fresh new 2.2 Dinc un-rooted. You then can try re-rooting at your own risk!!
I basically used part of jobehonda's instructions, and part of the thread's instructions, combined with my own messing around with my phone to fix my "bricked SLCD" Dinc... I hope this can help others as well as it helped me! ; )
Just one more option to try... What the heck, your droid is already screwed, it can't get worse. Just try this!
BTW, a buddy of mine with a rooted Droid X, also helped me with getting this far for the last 3 days!! He helped me with searching all the droid forums out there and random sites to get answers... Thanks CLIFF!
<---- Jackass
edit
fixed.
I am glad you figured it out, basically for the device to be recognized in adb you need to make sure your definately in recovery, if you follow the steps and count, one one thousand, two one thousand, etc etc you should be able to get it into recovery and recognized by adb.
the other thing is you need to make sure you have the HTC drivers installed prior, otherwise it wont recognize.
Then I shall edit it.
Few days ago, my G2's screen just went blank (dark blueish if I press any buttons on it). I live in Canada, so can't send it back to Tmobile since I'm not with them. But, I can send it back to HTC since it's still under warranty. Only problem is that I rooted the phone and s-off and then flashed Virtous Rom on it couple of months ago.
With the help of a senior member (eunkipark92), i was able to install ADB, and using that I can see that it recognizes my device when connected with PC. Now, I don't know whether the problem is with my phone's software or with the hardware (screen) itself.
I say that because I had a pattern set up to unlock the code before the screen went blank and even now I can swipe my finger on the screen in the specific manner that I used to before and it would unlock the phone. The screen still remains blank (dark blue) ofcourse, but I can change the phone's profile from vibration to loud etc after unlocking the screen by pressing the volume key up or down.
I was told by another member (PaganAng31) that if I can totally brick the phone using a command in ADB something like "dd = /dev/block/mmblk1p3" there will be noway for HTC people to figure out whether or not the phone was rooted before. But he wasn't sure and asked me to post here.
Now my first attempt will be to fix it somehow or unroot the phone and put the stock rom back in using ADB and then send it back to HTC. If I can't do that, then I would totally brick it (only if it's 100% sure that HTC won't figure out that this phone was rooted before) so that they can totally flash it or change the screen or send me a replacement. Also what's the exact command that is used in ADB and how do you use it for totally bricking the phone?
Any kind of help will be appreciated. Thanks
Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk
eunkipark92 said:
Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk
Click to expand...
Click to collapse
Ok. So what's the first step now? Do we reflash hboot and recovery? I flashed it 3 months ago using this method:
http://forum.xda-developers.com/showthread.php?t=833965
Now to reflash it, do we use this method on the wiki and just follow it. It looks pretty straight forward?
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
If that's the one, then the link to Engineering hboot for Tmobile G2 is broken. Any alternative?
Also do you know the command to completely brick the phone in ADB in case we are unable to fix it?
I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?
icruisin said:
I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?
Click to expand...
Click to collapse
Good luck buddy. Let me know if you find a way to get it fixed or brick it. From another thread I found the command is something like:
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
But I just don't know how to apply it.
Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.
fastludeh22 said:
Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.
Click to expand...
Click to collapse
Thanks. I know what to do next time if my G2 is messed up But I already bricked my phone last week and sent it back for repair, since I couldn't find any other to way fix it.
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks
anomander0108 said:
Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks
Click to expand...
Click to collapse
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..
avnr said:
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..
Click to expand...
Click to collapse
Yes this is the best thing to do. Something must have corrupted your stock ROM. If AAHK completed properly, then you should have ClockworkMod recovery installed.
The first thing I did was install 4EXT recovery but thats not necessary, that was just a personal choice.
So these are the steps you should take:
1: Download a new ROM and put it on your SD card in a convenient place (I recommend the RCMIX32 Runny 3.1 ROM)
2: Remove the battery and reinsert the battery
3: Hold down the volume down button and then hold down the power button. You will get to a white screen with some green robots on the bottom. This is the bootloader screen. You will have to wait a bit for it to finish scanning the SD card. It will tell you when it is finished
4: Use the volume buttons to select recovery and press the power button to select it
5: After a few seconds the recovery environment will appear
6: Go to the wipe menu. Wipe data, cache and dalvik cache (and system if you have the option. I havent used Clockworkmod in a while so I cant really remember what options you have there)
7: Go a few menu's back and select Install zip from SD card
8: Select the zip file
9: Press yes on the confirmation screen
10: When it is finished, click reboot now. It might be on the menu back
This will install a new ROM and it should work properly. If you have any problems along the way just say and we will help to the best of our ability
Thanks for the responses.
I don't think ClockworkMod is installed as there are no options available when I select recovery. It just reboots the device back to the HTC splash screen which as mentioned then fades / deteriorates to a black screen. I had tried the Android HD Revolution rom but no difference.
One thing I did yesterday in my panic was to select 'Factory reset'. Will this have usb debugging setting?
Finally, when I connect to a pc, it doesn't see it. Is this because it's still set on charge only mode?
I'm probably my own worst enemy
If you finally press "Factory reset" you will reset USB debugging, then you can't root your phone using this tools kit. Try to reinstall the stock rom.
If you didn't root your DHD. Phone may still under warranty.
Hi Guys
I've managed to get this back up and running again.
After a lot of playing about with various file downloads last night, I finally managed to get my pc to see the phone. After that, I just downloaded a stock rom and installed it.
After this fright, I am reluctantly going to stick with this and not bother with rooting / custom roms.
Anyway, many thanks for all your responses, I really appreciate the time you took to helpo me out.
This forum absolutely rocks.
Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!
Hi juicyp
juicyp said:
Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!
Click to expand...
Click to collapse
Did you check the MD5 Checksum of the .zip before you copied it to your SD Card? as it might is some way have got corrupted.
Here is a link to what I always use before I copy anything to my SD Card or install on my OS System:- MD5 Check 2.1.
Take Care
TheQuest
Thanks!
I'm all sorted (I think, fingers crossed).
It was principally because of the mac unzipping (Safari preferences not checked), this was the original and prime fault.
That caused me to doubt my partitions on the SD card (google is sometimes your enemy) which I altered.
So what then happened was CM7 installed but upon reboot looped continuously on the android skateboarding screen.
I finally resorted to formatting the SD Card, reapplying the CM7 zip and the google zips and so far it looks good.
Of course I (me and me alone) has stuffed up all the user data I had on the SD card. I might try to recover some photos but stuff like contacts I can regenerate no major loss there.
Thanks for replying!!
CM7 - the experience thus far
Well its 72 hours since I took the plunge!
Initially it looked odd and felt flakey, the Market refused to download 80% of the apps I tried. I resolved this (not sure if it was the right way) by going into recovery and clearing the cache 2-3 times and eventually downloaded all of my old apps.
Some apps cause frequent force-closes, I assume because they've not been updated for Gingerbread? Thats a very minor irritant, I can easily live without these apps anyway.
Battery life hasn't noticeably altered yet but I suppose I have been constantly been tinkering, playing with settings, trying wifi (seems a little less sensitive to signals) and gauging how the radio is working - I seem to get HSPDA a lot less and resort to 3G more than I previously did?
So, done it, like it despite some minor reservations - now what, is there anything else I can do to improve the experience?
I must add one thing this has shown me - I really really know very little about what goes on under the hood. Despite 20+ years experience in CIS this is a very different world and all credit to those who have developed CM7!!
Please help if you can.. please
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.
ravennyc said:
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.
Click to expand...
Click to collapse
Try to run the latest RUU.
Similar Issue
Hi all,
Similar issue as the thread, during AAHK had a "file not found" issue and now, only get HTC screen fading to black. Getting into HBOOT works fine.
I do have S-OFF but;
Have tried recovery, nothing.
Any RUU nothing
ADB shows device is offline
running any other option in AAHK device offline
Any help would be greatly appreciated.
Cheers!
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
m1ndh4x8r said:
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
Click to expand...
Click to collapse
I don't see how this helps me.
Help in the sense u have sent it to HTC for repair
Try this http://forum.xda-developers.com/showthread.php?t=1432425
Sent from my HTC_A510c using Tapatalk
kyleisah said:
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
Click to expand...
Click to collapse
ok, im not saying i can get it going again but i`ll do my best to help. lets start from the beginning, what actually works atm? you say when you try boot up the phone in any way it just vibrates 3 times.
does it do anything else, does the screen light up?
does it even stay on?
when you connect it to the charger does the led still light up?
have you tried to connect it to the pc? have you tried to connect it too the pc with volume down first?
all seem very basic stuff obviously but if the pc can register it in hboot we might be able to get a ruu running on it.
Found this on a different thread...
Nevermind. Just realized you were still getting three vibrates. Sorry man. I'll keep an eye out if I see anything else that might help.
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
hypercode said:
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
Click to expand...
Click to collapse
seriously , adb can install img files ?!
Alright, well, I called htc and told them about my problem, and I might have to just send it in. BUT. I had my phone rooted, and had CM Recovery on it. So, since nothing is booting up at all, only the three vibrates when trying to enter either boot mode, will they be able to see that I had it rooted or anything? They said they'll charge 35$ just to ship it back in the same condition if it is. Can't really afford anything like that right now.
tl;dr I had my phone rooted, but nothing on my phone comes up, will they see my root or anything?
if you are rooted you are probably s-off or at least have unlocked bootloader. and both they will find out very easily.
Sorry for my bad it was fastboot.exe you can install .img files with fastboot.exe i was installed stock recovery with that
Sent from my HTC Wildfire S A510e using XDA App