Hi,
My phone was working fine till i tried to revert to old radio and spl to use the superD rom. Ive used many roms and all works fine. When i did the revert my recovery stopped working, so i tried going back to the higher radio and spl and still my recovery doesnt work, i press home and end call and insteasd of going to recovery it just sits there with the htc magic logo for 5 mins then reboots and loops. I have no OS on the phone now so I cant boot into O/S or recovery so I thought id try to install an RUU that I know lets me change the SPL and radio. I thought the only way would be in fastboot so I went into fastboot and loaded the RUU in windows and get the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". Now my fastboot has a little picture of a processor(I think) with a red cross through it and now I cant even change the SPL or radio as I keep getting the error "FAILED (remote: signature verify fail)" this is so frustrating and I really need my phone . I am not smart enough to fix this so if someone could PLEASE help i would be greatly appreciative, thanks.
In fasboot I have the little processor photo with a red cross and the following info.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.008(SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
***Update***
Now I can only get into fastboot, even when I just turn the phone on. Please view this link of the photo of my phone to see what I mean, thanks.
http://i43.tinypic.com/2n1ylwk.jpg
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
MicroMina said:
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Click to expand...
Click to collapse
Hi MicroMina,
Thanks for the reply. I hope someone can help me too im really stuck here. I have attached a photo in my first post, not sure its even fastboot anymore I can access
kbeezie said:
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
Click to expand...
Click to collapse
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
ddmmh said:
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
Click to expand...
Click to collapse
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
kbeezie said:
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
Click to expand...
Click to collapse
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
ddmmh said:
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
Click to expand...
Click to collapse
If you had it working... why did you bother to flash the radio?
kbeezie said:
If you had it working... why did you bother to flash the radio?
Click to expand...
Click to collapse
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
ddmmh said:
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
Click to expand...
Click to collapse
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
kbeezie said:
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
Click to expand...
Click to collapse
Hmm i see, does the SPL or radio determine this? Because like i said earlier I was using the latest RUU for hutchinson AUS which installed fine so I believe thats not the issue, the only problem was the perfected SPL which was finally cracked a few days ago. I never thought id actually brick my phone. Do you think theres nothing I can do? I tried googling a locked fastboot with no results either, is this the first problem of its kind that you know of?
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Carlos1970 said:
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Click to expand...
Click to collapse
Hi Carlos,
No I cannot see any devices when i CMD adb devices
When you say go back to the providers code do you mean the RUU? If so then ive tried this without success(last one not original). If not can you explain what you mean? thanks
...and you have the SDK and USB drivers installed; correct? I run WinXP and the ADB driver was not automatically installed; had to be installed manually.
"fastboot devices" should work; does that one show anything?
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
eyegor said:
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
Click to expand...
Click to collapse
The problem of course is those who don't know what they're talking bout wouldn't know that?
And yet they talk. (not directed at Carlos, he did in fact tell the OP to try fastboot devices as well, only later)
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Carlos1970 said:
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Click to expand...
Click to collapse
Hi Carlos and everyone thanks for your input.
I read through that post and all related posts but there wasnt really much of a solution.
I CAN access fastboot devices so i tried to flash a recovery via fastboot it starts to write then I get an error "FAILED (remote: 12 signature verify fail).
I think because I have S-ON? So i was thinking if there was a way to turn S-OFF would I be able to flash a custom recovery via fastboot??? Cheers
BUMP ^ ^
$20 into paypal account for anyone can give me a solution to fix this 100%.
Related
Hi there
i'm really stuck at the moment and i've been reading threads after threads on this forum and i still couldn't find any solution and no luck with search as well.
my current problem is that i flashed a hero rom (i believe it's called myhero) about half a year ago when i first got it, but now i want to go back to the original Roger rom so that i can update to the new RUU. But i have no luck going back to the original rom at all. Anyone here would like to help?? i dun want to see my data plan go to waste just because of this
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT - 1.33.0009 (SAPP50000)
CPLD-12
RADIO - 3.22.20.17
PS: i tried many different ways, including unlockr's unrooting method, someone's nandroid wiped roger rom etc, but either htc sync said usb error or my fastboot screen said update failed. please help~
Should work using this method, just apply the update while the phone is in fastboot mode.
i tried that but i never knew i need to go into fastboot mode, i will give that a try, thank you very much
~dimdim~ said:
i tried that but i never knew i need to go into fastboot mode, i will give that a try, thank you very much
Click to expand...
Click to collapse
You don't usually need it. But if HTC Sync can't find the phone, you can apply the update trough fastboot. Let me hear your result.
yes same as before i get an error 170: usb error, is there any other way :S??
fastboot errors on mine also.
(If ROM installed via official HTC RUU- RUU_Sapphire_Rogers_WWE_3.05.631.7_R_release_signed_NoDriver.exe)
UPDATE!! **SOLVED** April 25, 2010
Download new RUU
http://www.multiupload.com/XQEH9NVGY7
Flash with Goldcard method http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
1. Download RUU linked above.
2. Install update using RUU.
3. Turn on phone and connect to computer.
4. Get RA recovery and SPL also linked above and drop them to sdcard root directory.
5. Run SDK: adb shell
6. Install recovery: flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img http://forum.xda-developers.com/showthread.php?t=561124
6. Turn off phone and turn on again holding Power+Home. RA Recovery should appear.
7. Flash zip from sdcard.
8. Use file: update-hboot-1762007-signed
9. Done. PSPL broken.
10. Build a shrine for orange_24
****************************************************
**Not Successfully Rooted: Feb. 2, 2010 (AFAIK)
I decided to start this thread because the info for again obtaining root, for those of us dumb enough to update to the official Rogers ROM 3.05.631.7 via the RUU, is all over the place in about a million different threads. My hope is that we can organize it all in 1 place.
At this point, yes, we all know we were impatient and newbs and everything else. Ok, lesson learned. So, lets move forward and try to get this thing rooted.
If you are a developer who has the talent to help root this ROM and have lost interest in the Magic or moved on to the Nexus One or Droid, we ask that you please try to spend a few moments on this and help out those of us who are really stuck here. Personally, I'm getting pretty desperate and thinking of even replacing the phone.
Please post what you've tried in attempting to again obtain root, your failures and hopefully successes.
*One Click Root: http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/ Cant' back up Recovery.img Error(Tried clicking the hidden Star next to "Back Up Recovery" and skipping this step...and just flashing recovery-RA-sapphire-v1.5.2H.img. Didn't work either) Tried with Amon_RA Hero recovery.img also, without success.
*Tried downgrading to Rogers' last official ROM via the RUU for (Rogers)_RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed. Attempted several times both with and without a goldcard installed.
*ADB: Will see the device, initially, but a command of "adb remount" kills the connect. same with "adb root" **EDIT
*Fastboot: Error- Does not allow access
*Relentless Rooter: http://forum.xda-developers.com/showthread.php?t=556200 No luck obtaining root
*Fix Perfect SPL: http://forum.xda-developers.com/showthread.php?t=548218&highlight=create+gold+card With one GoldCard getting Update Fail error that SAPPIMG is older than one installed. When trying the other GC, get Update Fail Error that Model ID is incorrect. Tried 2 different micro sd cards, one Sandisk and one Patriot. The card was recognized by my pc after I was done creating the GoldCard, so unless I'm doing something wrong the GC was created properly. Is the goldcard.img supposed to dissapear or remain on the card after your copy/paste write/save to the sd card disk?
* Tried RUU for RUU_Sapphire_HTC_Europe_3.04.401.2_HTC_AT_test_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=625108 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU for RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=621415 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
I've probably tried a few more methods to obtain root. Those were all fails, too. I'll post the links, as well, when I find them again.
Hopefully this thread will lead us all in the right direction.
Here is the link to the same topic in the HTC Dream Forum-in case they find out something that might help us out: http://forum.xda-developers.com/showthread.php?t=625732
i guess its time to play doctor with my new phone from rogers and swap the board from my old one.....
considering nothing works, i think any new idea would be a good idea
novadoc said:
considering nothing works, i think any new idea would be a good idea
Click to expand...
Click to collapse
like i said my idea was to swap my old motherboard into the new phone
you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware
novadoc said:
you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware
Click to expand...
Click to collapse
i already did it lol im more of a hardware then software
I know it might be nothing but when the Rogers RUU unpacks the img file loads as sappdimg and not sappimg. I don't know if the extra d in there means anything or if its something that shows up later.
I also try every method above and not luck also...
is there a possible way of tricking the system... with a higher build number and SPL with a custom installation from files that I see from one of the post where rogers send the user some files because they were running Win7?
I think that's the problem
We have the highest spl# and its perfected
So until someone gets their hands on a higher version than ours that is imperfect or engineering...
We are SOL, although I am hopeful someone is working on this for us.
shael said:
i already did it lol im more of a hardware then software
Click to expand...
Click to collapse
Did it work?
I have an Rogers HTC Magic and I didn't apply any update from Rogers since I bought it on June 2nd.
It's very strange that "adb devices" doesn't see the device?
have you enable the "USB debugging" ?
That part should work (when the devices is started).
novadoc said:
Did it work?
Click to expand...
Click to collapse
pfft ya ofcourse it worked... i have my older motherboard with my old rom and my old info all i did was swap the screen and case.... done deal... 5 min job lol
Would someone please report the radio and SPL versions (for the result of the 3.05.631.7 update)?
feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18
feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18
Well, until it gets cracked, here's something that will make you feel a little better about being stuck on this ROM.
Google Search by Voice, installable .apk from Euro Android Market. Just run the installer through Astro, etc., and G Search by Voice is back on the Search button of your phone. You might need to launch the app first via the icon in the app tray, then reboot the phone to make the search button recognize its there. But it will be there.
http://www.eclosion-android.com/com.google.android.voicesearch.apk
BTW, not my link in case mods want to get involved.
Enjoy!
i think the first step would be to getting ADB working again
any ideas?
novadoc said:
i think the first step would be to getting ADB working again
any ideas?
Click to expand...
Click to collapse
I can used adb devices to see my connected htc magic.... but other function permission not allow...
Is this thread in the Dream Forum a path to follow to try, or just a good way to brick your Magic? I haven't fully read through it to see if this is to keep root, if you already have it and flash the Rogers Dream ROM for data/ or to regain root if you flashed the official Rogers RUU with a Dream. The post says should work on all Rogers phones, but i feel a brick coming on for me.
http://forum.xda-developers.com/showpost.php?p=5480955&postcount=416
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
My first guess is that you are f**ked!
Only 2 "Nexus" roms I know that require new radio are for the 32A. And only new radio I know is for the 32A Magic!
Don't know where you got the instructions to upgrade your radio, but the ones I read stated that you have to flash radio, hboot, recovery in this sequence, and THEN reboot. Also, your recovery should be for 32B, dunno how you missed that one.
Try this: find your old radio image, your old hboot and recovery, boot in fastboot mode (back+power) and type in the following commands from the Android SDK tool directory:
Code:
fastboot flash radio your_radio.img <enter>
fastboot flash hboot your_hboot.img <enter>
fastboot flash recovery your_recovery.img <enter>
fastboot erase system -w <enter>
fastboot reboot-bootloader <enter>
You should now have rebooted back in fastboot mode. If that worked, try to reboot into recovery and see that works.
Once in recovery you can restore or flash another 32B rom.
See here for Engineering hboot images.
Download recovery for 32B
I found the link on theunlockr.com
developers.com/showthread.php?t=598973
And found instructions on youtube "ECLAIR 2.1 ROM REVIEW AND TUTORIAL !!!" and tweaked it slightly because i found a recovery image for my sapphire which didn't support either the spl or the radio, i forget... I've been up since 3am on Wednesday because of work and school, and now its 9am Thursday.
I was reading that 32b ROMs were working for the 32a, so i thought i might try a 32a since none of the links on Amon_RA's page developers.com/showthread.php?t=529019 were working for me.
I cant get to the fast boot menu... so that way doesnt work
Some_Biker_Guy said:
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
I think you are rather screwed. I believe the phone boots up the radio image before the bootloader and therefore you can't even get to flash a new recovery or radio image as the boot process is halted because of the defective radio image.
The only salvation I know if is a JTAG connection. This involves open up and soldering stuff to the mainboard of your phone. Since you're asking you probably not familiar with it I wouldn't recommend it to you.
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
KAwAtA said:
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
Click to expand...
Click to collapse
I agree with KAwAtA. You pretty much did the right steps (kinda) but you got the wrong files and now you got a nice brick. You should do research and know how to tell if your phone is 32A or 32B, why you should never flash the wrong radio/spl for your type of phone, and what ROMs are compatible with your hardware and why you should never flash the ROMs for another piece of hardware.
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real but do not ROOt it because you might flash a 32B radio on it and make that a fancy brick.
damn sorry bro. does sound like everything that could have gone wrong went wrong for you. i also went to theunlockr to root my phone and add roms to it but i read those instructions like 3 times and watched the videos a few times when i first did it. oh well, you'll learn from this at any rate.
AndroidNoobie said:
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real
Click to expand...
Click to collapse
that lucky SOB!
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Some_Biker_Guy said:
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
iluvmymytouch said:
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
maybe u already tried.
dan-htc-touch said:
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Click to expand...
Click to collapse
he already said that he couldnt get into fastboot mode. most likely its a brick..
oshizzle1991 said:
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
Click to expand...
Click to collapse
I tried the "G" and it didn't work, so i tried the "H" and it worked. Fastboot didn't work...
Thanks everyone for you input... this is my reply to everyone since i cant reply to one/ a few at a time.
1) I knew how to root my phone, and did it multiple times. I also unrooted it a few times as well (just to get a fresh start and make sure i knew how to). I also loaded many different ROM's onto it including Hero and tweaked cupcake ROM's
2) Fast boot did not work, and the computer would not recognize the phone at any point.
3) The unlockr did a good job with instructions on how to root and unroot then loading the hero and cupcake rom's onto it but it had no explanation for loading the nexus rom onto it, although it did feature a link on where to get it. therefore i tried to piece together ways to update the radio and spl (this is where it all went to hell). i figured out that that is what i needed to do to run the nexus rom.
ok, ok now i know, wait for a full set of instructions for my specific phone to try to put the newest and coolest rom onto my phone... :/
4) i got it all taken care of, got "new" phone for free! so glad it worked out.
so get this...
I just rooted my sensation and was waiting for a custom ROM to download through the phones browser. My buddy came over and I was setting him up with root for his Aria and for some reason his phone got stuck after getting s off. I tried to use adb to flash the recovery to his phone but it just said "waiting for device" forever. After about 10 mins I said forget it, too nice outside and unplugged his phone, I didn't think to close adb first but I put my phone on the usb to charge and then it instantly flashed the Aria recovery to my phone.................
Good news is I can root his phone knowing it was the wrong installed driver before. Bad news is I now can only get into fastboot (white screen, skating androids at the bottom) where it still says revolutionary at the top but I can see the Aria's radio and the wrong HBOOT version. I still have the factory reset, recovery etc options but if it boots up it'll get stuck at the stock HTC image. I tried flashing CWM recovery through adb the exact same way but it just says waiting for device now too? I may have typed the code wrong or do I need Aria drivers now? I assume there is a way out since I'm still in fastboot but not sure.
Any help would be appreciated and thanked! Until then, its back to my g2x, its not so bad...
you would need to download the RUU (Rom Update Utility) for your phone, where you get it I have no idea, hopefully another more skilled member will be able to point you in this direction..... I got the Vodafone uk one from a thread on here but I for the life of e can not remember where.
Nah I figured it out, I downloaded the img file and flashed the zip in hboot, then used adb to push the stock radio back up. I was really scared there for awhile but thanks to this place I got a bunch of help.. Love this place.. Thanks anyway though man!
It's good to know that a bad radio no longer prevents booting to hboot. I bricked a g1 back in the day from having an hboot and radio that were incompatible with each other. The thing wouldn't boot to anything other than a special service mode that is only useful if you solder in a hardware jtag.
Sent from my HTC Sensation Z710e using XDA Premium App
Hello all, I'm hoping there are some sincere members will to help out a total noob.
I picked up my sensation and stumbled upon this website, in order to find a way to "jailbreak" my phone (I use that term lightly, I was a previous iPhone user and so far know very little, if nothing, about android development.
Lets get to it, to start I was attracted to installing this rom.
http://forum.xda-developers.com/showthread.php?t=1098849
At the time of noticing this post, my phone was brand new-- I read carefuly and understood that I should follow this post.
http://forum.xda-developers.com/showthread.php?t=1192300
I correctly (to my knowledge) Installed S-Off, ClockWork, Root, SuperCID..
While waiting for the Revolution rom to download, I started fooling around with my phone, noticed I was having Wifi errors -- would not connect, constantly trying to obtain IP address..
So heres where I think I goofed, I preformed a factory reset from my device, completely wiped the SD, -- did not fix wifi problem. I returned to the post about installing S-off, CWR, etc...
And understood that, "IF YOU ARE EXPERIENCING WIFI ERROR.
Currently the only way to fix this is to flash Stock Rom again or Custom Rom."
I then proceeded to follow STEP 4 in that guide in attempt to reinstall stock rom.
I was directed to this thread
http://forum.xda-developers.com/showthread.php?t=1074559
and downloaded
RUU_Pyramid_BM_1.35.666.1_Radio_10.50.9007.00U_10. 12.9007.21_2M_release_200555_signed
As I understood BM to stand for Bell Mobility (my carrier).
I went through the process, failed. I now have a black screen with HTC logo in the middle with exclamation marks in all four corners. There is a progress bar that is at approximately 90%. No matter what I've tried I cannot return to the boot menu.
At this point I am almost certain I've bricked my phone (fail), but if theres any possible way of fixing and returning to factory settings and fixing my wifi error I would greatly appreciate any help.
If I'm pretty much screwed I'd like to know where to go from here? Will I have to purchase a new phone.
Apologies if this post has been covered, (I did search the forums) but I've grown desperate and am certainly worried.
Please Help!!! What do I do?
sounds bad...you cant get to the fastboot menu at all? not even after a battery pull?
No, not after a battery pull or sdcard switch (idk if that does anything or not, but I tried it.)
hmmm....methinks its bricked...and we have no jtag or download mode :/
the only other option it to try to flash an eng hboot for fastboot commands, or an older RUU from the sd card.
it seems to me the only course of action is using a pg*****.img from the sd card and keep trying to access fastboot, or just return for repair
when its in this htc logo with exclimation screen, can you run ANY adb commands?
I'm going to try an older RUU, and no I cannot run any adb commands because the command prompt flashes for only a second.
One thing, when I pull out the USB
PVT Pyramid S-OFF
HBoot 1.17.0011
Radio 10.12.9007.21_2M
eMMC-boot
*date/time*
RUU
will flash on the screen for a moment, this is the only time (other than battery out) when it is not on HTC Logo with exlamations..
(soo bricked yeah?, feels good man.)
Obviously my warrantee is voided right, so how can I send in for repair? Will I end up having to purchase a new phone?..
dont just run a .bat or exe for commands, go to run>cmd and type commands manually, and see what it returns, espicially if you get return on "adb device" (no quotes)
also, if it shows the software info, it *should* flash any RUU/recovery files on the sd card, and then you can use CWM or TWRP to get a little farther...
im dl'ing an RUU to lookin to something else that might help, but if you dont mind a little work, you might be able to get it going again
if its easier, just pm me and i can help you out of the threads, with quicker response
Anything I can do to get it working again, just remember I'm really new, I'll catch on quick, but I've only been at this stuff a day! Also wanted to thank you properly, since I have yet too. So thanks for the help so far.
So, silly me, I can somewhat run adb commands now. But adb is not showing my device, however I type the commands
"fastboot reboot-bootloader"
"fastboot reboot"
and it reboots it, but returns it to the exclamation screen,
"fastboot getvar cid" seems to also be working, (I only know limited commands, from the tutorial)
awesome, that means you still have a chance!
ok gimme a moment, im checking something as we speak
EDIT* also, thanks for the "thanks"
ok try these commands (though they might not work on your hboot) and reply the output:
fastboot oem partition_test
fastboot oem test_emmc
these are to make sure there are no issues with any tables
also is this a bell sensation? if so, you will have to superCID to install the latest EU RUU, which may solve all your problems
also, this is the easiest way to flash an RUU for you (MUST BE SuperCID!):
http://forum.xda-developers.com/showpost.php?p=11441747&postcount=1
Output..:
C:\adb>fastboot oem partition_test
... INFO[ERR] Command error !!!
OKAY [ 0.019s]
finished. totla time: 0.019s
C:\adb>fastboot oem test_emmc
... INFO[ERR] Command error !!!
OKAY [ 0.021s]
finished. total time: 0.022s
And yes, bell sensation.
blerg, i thought it might output the errors, but thats more of a pc issue, not the phone
give the manual RUU a shot, seems to be the easiest/best chance atm, but try to supercid first
http://forum.xda-developers.com/showthread.php?t=1192300
go to step 4
I will give the manual RUU, which RUU do you suggest I try?
RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed
bottom of the list in the first post
http://forum.xda-developers.com/showpost.php?p=13698101&postcount=1
So I actually downloaded
RUU_Pyramid_HTC_Europe_1.24.401.1_Radio_10.39.9007 .00P_10.11.9007.09_M2_release_190934_signed
and ran it off my desktop and it restored my phone ! Yay! So its working fine right now (I think there was just an issue with the BM RUU) .. except for the wifi... my wifi is still not working...
Thanks for you help again.. You got my this far, so if you're ready to give up on me go ahead, but I would really like to sort this issue out..
Not quite sure where to go from here, but so thankful the phone is not bricked!
Should I update to the one you posted? I had previously downloaded this
this RUU is better, as for the wifi, lemme find the best wifi fix patch for ya
lol im also at work right now and VERY bored, so this is an excellen time killer
also, this RUU might fix the wifi problem, but if not, you will need to install clockwork recovery or teamwin recovery to flash the .zip of the wifi fix
EDIT* also, try turning off fastboot, reboot the fone, then wipe dalvik cache in recovery and boot back in, then check the wifi
if the wifi still doesnt work, give this a shot:
http://forum.xda-developers.com/showpost.php?p=15867636&postcount=42179