Related
[SOLVED]
okay so i have a working goldcard. my adb is working
i have a 32b
but heres the weird part. i loaded the sappimg.zip on my goldcard and did fastboot. that was loaded just fine. yet im still on 1.6 , but i thought im suppose to be on 1.5. im going by the directions on the (how to) for rooting made by RA.
then when i fastboot usb to load the recovery img. it says failed. i really have no idea what im doing wrong.
i have done all this for my g1. cuz i hand changed the boot screen. so im not new to this.
i have checked to see if my drivers are all working. when im on the home screen , i made sure my mytouch was connected to adb with *adb devices* but when i go to fastboot usb it says theres nothing there. also i have the recovery.img in both places. one on my normal mem card and one in ANDROIDSDK/tools/
so im not even sure what the problem is. once i get the recovery.img on there then ill be good to go.
if anyone knows what this may be. then thank you in advanced for the help
posted in wrong section... And try unlocker to get yourself a video you can't seem to read. B/c you don't need a gold card or fastboot... REALLY over thinking it.. get a newer updated guide really/
wow dbag. i am using unlocker also. forgot to put that in there.
okay all great master of phones. why not help then
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
Downgrade to DC83 (1.5). Just drag and drop Sapp onto the root of your card, unmount, turn the phone off, volume down and power, hit END key to start update, wait awhile (make sure your phone has full power), once its done hit the trackball to restart and you should be good to go. Reboot phone and check system settings for 1.5 firm.
ok first off we need your phone info... not all mt3g need a goldcard to root.. basically i found if you mt3g came with 1.6 preloaded then you do need a goldcard.. you wont be able to just downgrade using the mt3g sappimg from theunlockr how to..
ceas909 said:
ok first off we need your phone info... not all mt3g need a goldcard to root.. basically i found if you mt3g came with 1.6 preloaded then you do need a goldcard.. you wont be able to just downgrade using the mt3g sappimg from theunlockr how to..
Click to expand...
Click to collapse
yeah this was a replacement MT3g that came with 1.6
to the guy above. i tried those steps already. it stops at sig. and says failed something.
i made a goldcard and tried with the Sapp zip file
it loads and all. but then its still on 1.6
G-Fetus6 said:
to the guy above. i tried those steps already. it stops at sig. and says failed something.
i made a goldcard and tried with the Sapp zip file
it loads and all. but then its still on 1.6
Click to expand...
Click to collapse
Downgrade to DC83 (1.5). Just drag and drop Sapp onto the root of your card, unmount, turn the phone off, volume down and power, hit END key to start update, wait awhile (make sure your phone has full power), once its done hit the trackball to restart and you should be good to go. Reboot phone and check system settings for 1.5 firm.
Click to expand...
Click to collapse
Well. Those are right steps. If it says signature fail - that's your problem that you need to fix.
r3s-rt said:
Well. Those are right steps. If it says signature fail - that's your problem that you need to fix.
Click to expand...
Click to collapse
hmm ive tried everything. just doesnt wanna seem to downgrade. i redownloaded the files from other places to make sure it wasnt my files.
still nothing . hmmm i guess more reason to sell this phone and upgrade to a better one... maybe a N1
G-Fetus6 said:
hmm ive tried everything. just doesnt wanna seem to downgrade. i redownloaded the files from other places to make sure it wasnt my files.
still nothing . hmmm i guess more reason to sell this phone and upgrade to a better one... maybe a N1
Click to expand...
Click to collapse
no no no.. you cant downgrade your device with the regular mt3g 1.5 sappimg... if your phone came with 1.6 already loaded you need to find a sappimg that has a higher hboot then your phone... im betting your current hboot is 1.33.0007 ... and the mt3g sappimg used to downgrade to 1.5 is for hboot 1.33.0006.. you can use a hboot lower then what you have to down grade try this how to.. http://forum.xda-developers.com/showthread.php?t=674003
turtleiscool said:
posted in wrong section... And try unlocker to get yourself a video you can't seem to read. B/c you don't need a gold card or fastboot... REALLY over thinking it.. get a newer updated guide really/
Click to expand...
Click to collapse
o and its funny how noobs try to step in and give their 2 cents when they have no idea of what their talking about....
ceas909 said:
no no no.. you cant downgrade your device with the regular mt3g 1.5 sappimg... if your phone came with 1.6 already loaded you need to find a sappimg that has a higher hboot then your phone... im betting your current hboot is 1.33.0007 ... and the mt3g sappimg used to downgrade to 1.5 is for hboot 1.33.0006.. you can use a hboot lower then what you have to down grade try this how to.. http://forum.xda-developers.com/showthread.php?t=674003
Click to expand...
Click to collapse
Never knew that. Ty.
i solved it . went and looked threw the magic wiki more. and found my problem hinding. the spl was perfected an such.
turtleiscool said:
posted in wrong section... And try unlocker to get yourself a video you can't seem to read. B/c you don't need a gold card or fastboot... REALLY over thinking it.. get a newer updated guide really/
Click to expand...
Click to collapse
and yeah i posted in the wrong section. but thats cuz i though i was in the general section on my phone <not a noob lol
I TRIED THE HBOOT 2.2 ROOT GOT BRICKED AND USED THE FIX FROM "Monarky"
THANKS DUDE AND IT WORKED SO IVE PUT TOGETHER
A SHORTER FIX I ACTUALLY DID THE WORK MYSELF SO ALL YOU HAVE TO DO IS REPLACE THE ATTACHED FILE WITH THE ONE ON YOUR SD CARD
AND RELOAD BOOTLOADER AND IT SHOULD UNBRICK BUT ITS GOING TO SWITCH YOUR "PRI VERSION" BUT IT WORKS
ALL I ASK FOR IS A SIMPLE THANKS
FIX - http://www.megaupload.com/?d=2KA69REH
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
he was probably referring to being stuck at the RUU update screen
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
s0xpan said:
he was probably referring to being stuck at the RUU update screen
Click to expand...
Click to collapse
well yea the red triangle
I haven't downloaded what you cooked up there, but if included radios or the wimax partition, you really need to warn people that they could lose 4G.
If you "brick" your phone, you should only use the RUU from Sprint to fix it. If the phone isn't recognized by the RUU, then extract the PC36IMG.zip from it and use the fastboot command line to flash.
-- Brian
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
Nope, your wrong. Back when I used to mod PSPs, if you flashed a firmware incorrectly, you'd either get a semi-brick or a brick. A semi-brick is when you can't get into the OS, but you can access some sort of recovery menu/method. A brick is when it won't turn on at all or it will turn on but won't do anything (or freeze at splash screen).
mlin said:
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
Click to expand...
Click to collapse
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post. I don't think you understood what I said. Though you could get the phone into bootloader, the screen was not on. The only reason you would even know the phone was on was if you had it hooked up to your comp when you powered up. There was no method you could use that would allow anything to be written to the internal memory. There was a hardware problem with some of the evos, where in they have a TON off bad blocks. This prevented the os from being rewritten. I have meet a few other guys on xda who have the problem with bad blocks. So, how would you define this, if not as a brick? It wasn't hung up somewhere. It was totally unusable. After spending 2 hours on IRC, we decided it was totally unfixable. Took it to a sprint repair center the next day and, funny enough, they agreed. They couldn't even access it enough to tell that I had an unlocked bootloader. Yes, they replaced it.
tejasrichard said:
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post.
Click to expand...
Click to collapse
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
mlin said:
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
Click to expand...
Click to collapse
No big deal, man
The whole thing is pretty silly, anyway. My only point was you could be bricked and still have your charge light comer on. No hard feelings here.
Tejasrichard is right. I got one of the bad blocks phone, brand new too. I guess ill use it for a spare touchscreen
Bootup Problem
So I have an evo that when powered up only displays the startup white HTC EVO 4G screen for 5 sec....turns off for 3 or 4 sec then back on and same in a continuous loop. I can access regular android recovery with the white screen and androids on the bottom. When I choose recovery from the options on that page it does nothing but the white HTC EVO 4G screen boot looping over and over.
Things I have tried:
New SD Card
PC36IMG - tons of them from many methods
Flash a new recovery
The computer does recognize the phone but I can't find it anywhere?
Any help ?
PM me please.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
X2!.................
After trying this method my phone stills only boots to the white screen
I know we're going to get at least one person who says their phone is bricked. Here's how to unbrick it (links to stock rom/kernel, etc) for Virgin and Sprint versions:
http://www.howardforums.com/showthread.php/1691827-Intercept-free-stock-ROMs-and-apps!
You'll need to know how to install and patch SWUpdate for the Moment so it works for the Intercept. Not hard at all.
Did I miss something? How did we go from the EVO to the Moment/Intercept? Anyhow I'm having the same problem as whoisjlk in post #14. Please if anyone has a solution I would greatly appreciate it and even donate. PLEASE PLEASE PLEASE...thanks in advance.
Wow I guess I posted in the wrong section LOL.
Ok, I have an Evo that I would like to recover from the dark side.
I rooted my HTC EVO 4g using Unrevoked, it worked fine, then I decided to flash a new rom, followed all the steps and I backed up my stock and wipe data/factory reset and Davik, now my phone doesn't read the sd card.
Took the sd card out and did a FAT32 format (4 times already), downloaded the new zip to it and still not reading.'
Bought a couple different SD cards.
Can't do a restore because the sd card and is not recognized.
As soon as I check install zip from card it reads
ClockworkMod Recovery v2.5.0.1
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(No such file or directory)
E:Can't mount /sdcard
Now I know Amon RA Recovery is way better.
I had S-OFF, after wipe all data have S-ON and don't know why.
This is what I tried:
All kinds of PC36IMG (Recoveries, ROMS, Unrevoked S on and S off)
ADB doesn't work.
Phone is not found, when try to update drivers using Windows 7 it says that Qualcomm-CDMA-Technologies-MSM driver is not found, but my other EVO and the ones that I rooted have no problems.
Phone boots into HBOOT and Recovery.
After opening HBOOT PC36IMG gets recognized but not updated.
In recovery when try to flash from SD has the message E: Can't blah blah
If I try to reboot the phone, it just goes to a black screen with a flashing LED or gets stock on white screen forever.
Any ideas?
I would like to fix it, already have a working phone, and I don't need this one, is just to put all the help together and maybe some one that has a similar problem can avoid all the troubles and follow a single post and not spend hours searching just to find the wrong answers.
Otherwise is going to be just for spare parts and that doesn't help many.
Thanks in advance.
If you have an idea, lets try it, PM or reply here.
This thread is just to direct all the noobs into the right direction, related to root and flash new roms in the Inspire 4G.
[*]Rooting and reverting to stock
Due to the retirement of the Hack Kit, rooting methods have been reduced to:
http://forum.xda-developers.com/showthread.php?t=2168500
or if you are skilled in using adb and fastboot commands:
http://tau.shadowchild.nl/attn1/?cat=6
If you are still stuck and want to revert your phone back to out of the box, then use Marsdta's Guide:
http://forum.xda-developers.com/showthread.php?t=1396229
or Gene Poole's Tool (that will revert also S-OFF):
http://forum.xda-developers.com/showthread.php?t=1208507
[*]Flashing a Custom Rom
To flash a custom rom you need to be rooted and S-OFF (if u used the Hack Kit) or have and unlocked bootloader using HTCDEV tool (wich I don't suggest)
Once u are S-OFF and have CWM or some other custom recovery installed (I personally prefer 4ext) you have to follow these steps (read the dev's thread about particularities. This is just a general guide on how to do it):
Download the custom rom .zip file and put it in your sdcard. Make sure that u check md5sum first just to avoid bootloops.
Reboot phone in recovery. There are many ways to do that, the first can be using Rom Manager (I don't suggest using it for anything else but that) and choosing reboot in recovery option. The second way is to boot in bootloader (press power down and reboot choosing hboot) or just turn phone off and power it up pressing power and volume down. And the last is to use adb commands. Plug the phone as charge only with usb debugging on, open a cmd as admin or terminal as root in your PC and then type adb reboot recovery.
Once in recovery, you need to do a full wipe (wipe data / factory reset and wipe cache + dalvik cache). You can also format some other partitions such as data and system, but the full wipe will work.
When full wipe is finished, go to flash zip from sdcard option, choose zip file and then flash that file.
Reboot the phone once it has finished flashing and wait for the device to fully reboot. The first boot will take a while (probably longer than usual) so don't get scared.
If you flashed a CM based rom, you need to flash google apps separately as well, so find the gapps file corresponding to your rom and flash it in the same manner as above described.
Trouble Shooting
Bootloops: If your phone repeats over and over the bootanimation, don't panic, you are not bricked. Something must have gotten wrong but you can reboot in recovery and re flash the rom as previously described. If bootloop is still there, then try downloading the zip again or choose a diffrent rom.
Factory Reset: If you factory reset the phone and you are not stock, then the phone won't have a rom...you will get stuck in the splash screen (white screen with the green HTC). Just do as described above, get a rom to the sdcard and then flash it. You are not bricked, you are just stuck
Well, this was just to try to point you in the right direction. If you think that I missed something, feel free to tell me and will add it to the OP.....Salud! :good:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Teichopsia said:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, let's hope that people find it usefull...
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Teichopsia said:
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Click to expand...
Click to collapse
hahaha...ummmm you shouldn't have problems. Just install SDK and apk multi tool in the SDK>tools folder or somewhere else. Then from command prompt you should be able to run the commands for the apk multi tool. I use the apktool and I have no problem at all. The main thing is to have adb installed...but there's no need to have the phone plugged to use the apk tool.
In the case of your device, make sure that u have the HTC drivers installed, if you have HTC Sync, you should have them...to try that just plug the phone as charge only, make sure that usb debugging is on and then open a cmd as admin and type adb devices...you should see your HTCserialnumber....
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Teichopsia said:
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Click to expand...
Click to collapse
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
glevitan said:
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
Click to expand...
Click to collapse
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Teichopsia said:
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Click to expand...
Click to collapse
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
glevitan said:
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
Click to expand...
Click to collapse
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Teichopsia said:
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Click to expand...
Click to collapse
AHH I was talking about Adamsoutler´s tutorial in XDA TV. He explains how to set SDK and develop APKs....it is awesome!..look at the XDA TV thread.
Bump.
Sent from a dream.
not able to go back to stock
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
krjkinan said:
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
Click to expand...
Click to collapse
RUUs can not be flashed with an unlocked bootloader. Relock it first, then run the RUU.
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
romanvaldezo said:
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This post is no longer timely. The tool it refers to has been retired. You can no longer get S-Off, but you can unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=2169515.
hey
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Hey, not being mean, but did you read the post right above yours...? Or anything in the Desire HD forums, which is the same phone and is more populated?
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Then are not reading the OP. You have all the information neeeded in there...if your first post in here Is to whine, then you have not Read the rules or understand the spirit of xda.
Follow the instructions And You will be fine, if You don't Get them take time To learn. Nobody Is going To do your homework.
I just recently rooted my inspire it took some time reading and a few attempts to get it down. But after my homework and grasping the concept it was fairly easy.
Sent from my Desire HD using xda app-developers app
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
bimplebean said:
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
Click to expand...
Click to collapse
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
glevitan said:
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
Click to expand...
Click to collapse
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
you can run the RUU exe file from fastboot usb
glevitan said:
you can run the RUU exe file from fastboot usb
Click to expand...
Click to collapse
It's an EXE. How do I run that from fastboot?
bimplebean said:
It's an EXE. How do I run that from fastboot?
Click to expand...
Click to collapse
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
glevitan said:
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
Click to expand...
Click to collapse
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
bimplebean said:
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
Click to expand...
Click to collapse
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
glevitan said:
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
Click to expand...
Click to collapse
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
bimplebean said:
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
Click to expand...
Click to collapse
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
bananagranola said:
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
Click to expand...
Click to collapse
I apologize, this is not my strong suit. I've been through so many things I'm not sure I remember all the things I've tried. I think I tried flash the recovery with Ace Hack Kit.
Let me describe what I DO know.
I can boot in to Fastboot (Vol Down + Power)
Here's what it says:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
There is no LOCKED or UNLOCKED indicator at all.
I'd he happy with an RUU stock ROM, but when I try to re-run the RUU from my computer, the system tries to reboot the phone into the bootloader. This is when I get the HTC screen and it just sits there. The RUU program reports a connection error.
I have several ZIP files, one for the Froyo image, one for the Gingerbread one, they're supposed to be for this phone.
I tried to reload the Gingerbread one from the SD card (I renamed it update.zip) but it failed. I booted into fastboot, then selected Recovery. While I had the green symbol I waited...after a bit it went to HTC screen and froze.
Tried again - this time when I had the green symbol I pressed vol up + power and got to the recovery options.Here's what I see
formatting / data
can't open /data/cwpkg.zip
can't open /data/cw.prop
can't open /cache/cwpkg.zip
can't open /cache/cw.prop
formatting /cache.....
Then I get the blue list of options. I select apply update from SDCard...
-- Invalid Operation ---
Then it reboots into the HTC screen and stays there.
Suggestions?
would love a copy of your file...
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
pharoah1974 said:
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
Click to expand...
Click to collapse
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
glevitan said:
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
Click to expand...
Click to collapse
Thanks. I will try that.
Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
So does it power on at all?
Sent from my Evita
timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!
Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Hi from Canada!... I just wanted to be part of the greetings.. :laugh:
exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)
I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.
My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita
timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:
Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now