I flashed the wrong recovery for my mytouch3g 1.2 and can't get past the mytouch screen the phone was already rooted. I was updating to a new recovery and realized after I flashed it was the wrong recovery. I can still boot into fastboot mode but I am locked from uploading the correct recovery. So I need to make a new gold card to root the phone again to flash the correct recovery but I am unable to get the CID# to make a new gold card is there another way to accomplish this? I was testing a new ROM when I flashed a the recovery that's way the phone wont boot.
If you posted this in the correct thread you would get more responses.
I moved it to General for you because this has nothing to do with the development of roms.
Im in the same boat - Someone help?
I asked a friend to let me borrow their android phone>> I installed terminal, popped in my SD card and pulled the CID. --- Know anyone with an Android phone? My best solution for ya.
Did it work for you?
Yes, I installed terminal on my friend's phone from Market - booted her phone with my SD card, ran the cat command and pulled the CID. --- Had even more fun getting the Hex formatting to work on my Gold card... but I finally got my phone up and running again. Good Luck and if I can help let me know. the unlckr GoldCard instructions were the most concise. Then Amon_RA's posts were the best.
Related
Probably regrettable i am fixing to room my 1.2
As we speak i am...slowly...downloading the sappimg and stock root rom.
I already have a "working" goldcard, but when i got the email it said it was a goldcard for a G1?
This is my first time messing with Anrdroid stuff, but is the G1 thing correct?
Also, I know the goldcard method works for unbricking a S620.
But will is also work for the MT3G...I just know you can unroot with the sappimg & RUU...
Yeah Yeah i know n00b here.
To bad flashing and "unlocking" an android isnt as easy as it is on windows mobile
Also, just another really stupid question.
If i created a working goldcard and dont brick my 1.2
will the same goldcard work on my mothers Fender?
i know they are the same phone, but will the card work on it after i use it?
Okay, I'm not sure i did this right.
my goldcard is actually working in the phone.
Hboot and all comes up BUT when it tried to read the SAPPIMG.img (2.53.707.2_-_sappimg.zip renamed Via winzip, it comes up as a Jasc .img file on my computer like the .img's in the .zip)
It says reading sappimg.img
No Image
about 5 times and then kicks back to Hboot.
Perhaps i just named it wrong??
If only i could do this in a terminal on Mandriva....
I would have been done by now...lol
Thanks guys.
***EDIT***
Okay I got it to boot.
SAPPIMG.zip worked downloading recovery-RA-sapphire-v1.5.2G
But please tell me the incompatible rom i just flashed is supposed to hang on the HTC magic screen.
Nevermind.
Its booting up as i type, already on the Android screen.
Thank you guys for all your hard work on the rooting and ROM's
hi all im pretty sure ive bricked my hd2 but im not positive i can get into the boot loader and i have tried to flash via the sd card and that even fails right now when i turn it on i get the black screen with the white triangle with the exclamation and it says software update failed now i followed this guide http://forum.xda-developers.com/showthread.php?t=681317 and used that stock rom but that fails im putting this up in hopes that i can get help with this now what happened is a bit odd i was running android on the sd card and it would reboot at random whenever i tried too do something then all of a sudden it started too flash my winmo rom so i didn't interrupt it then everything worked ok i put a different version of android on the card i was even able too try and flash the rom via usb somehow it went threw but that failed too i was at the 2.12 radio first things first does anyone know how too change the radio via sd card and does anyone have any suggestions and remember i can get into the bootloader thanks in advance everyone for any help you can give on this
Please read this whole post before clicking on links.
Yes, and apparently you never read mskips thread which was posted in the guide you used. Check this link out to flash a radio via sdcard
http://forum.xda-developers.com/showthread.php?t=653614
If you can get into boot loader mode you might have a chance to save the phone. Have you tired Task 29? It'll erase everything on your phone (besides the radio)?
Also please provide me with the link to the thread where you got the radio from.
If you need some help hit me up on gtalk using your google account. ldgarcia4283, i'm gonig to walmart but i can chat on gtalk.
I was using the new HTC Gratia Rom that was posted in the development forum, was restoring some apps with Titanium Backup manager when my phone rebooted, then it got stuck in a boot loop. I wiped it and rebooted again but no joy, stayed stuck in the loop.
Anyway, I recently installed a new recovery image, one of the ones for jailbreaking the PS3, so I have no USB access. Also it has a few extra options for wiping than the Amon RA recovery, and I guess I shouldn't have used the format boot option! Now on bootup all I get is "FASTBOOT USB", though I can still get into the psfMod recovery image.
That isn't much use to me though, as I stupidly deleted my nandroid backup and the update.zip file from my SD Card earlier while tidying it up a little bit. I don't have any other way of accessing the SD card and attempts to push another recovery image (with USB access) have failed.
I've also tried to install RUU's, both a T-Mobile UK one and a WWE one. That results in the following error: "ERROR [140] BOOTLOADER VERSION ERROR".
I guess because the current image version is: 3.31.110.1 and the RUU is only: 2.73.110.26. I don't think there's an RUU of this version available, from reading it sounds like it was an OTA, it's not something I installed myself, T-Mobile sent me this phone recently after my screen stopped working properly.
If you've managed to read this far without falling asleep, any suggestions would be welcome hopefully not just that I should buy a card reader cos I could do with getting my phone going again asap.
You got access to another phone which uses a micro SD? Could use that to put the zip onto the card.
Making a goldcard springs to mind as well
Sent from my HTC Hero using XDA App
Thanks for the tip, I had considered this already but I thought my brothers Legend (he doesn't live close) was my best bet. Turns out I had access to an N95 that did the trick
same problem
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
mithdol said:
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
Click to expand...
Click to collapse
What is the problem with urs exactly?
the problem is that im stuck in a cyanogen boot loop.
i have access to the generic fastboot only. therefore i have no ability to repair my phone from within the phone itself.
my phone is currently on hboot 1.76.0007.
i thought i had flashed clockworkmod. but for some reason or another beyond me it has disappeared.
the version of android i have running is 2.1, the tmobile version. the update number is 3.31.110.1. i understand that is the perfected spl version.
i have tried to fix using the ruu files. but i understand that the version on my phone as an ota update. therefore no ruu is applicable at this time.
i have tried many methods mentioned in various forums with no success.
thanks for responding to my post so quickly.
mithdol
Problem solved now
and the solution was so obvious............
...and what was that obvious solution? Because I'm facing a similar problem...
Thx in advance!
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one
Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.
This this a decent guide from Paul over at MoDaCo.
Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.
There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier
Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks
i am trying to root and put jellybean on my My-touch 4g. i know all the processes and i have gone through a great deal of time reading and watching videos. the first thing i was supposed to do was to downgrade my My-touch 4g to 2.2.1 since you can't root the version 2.3.4. well i downloaded the files necessary and put them on the root of the SD card and booted into H Boot.
so my problem is that the H Boot doesn't recognized the PD15IMG.zip ( hence me not being able to do anything). please help ....
i was also wondering if i could flash a Custom Rom through recovery without having to root or downgrade?
If the HBOOT doesn't recognize your PD15IMG, you might be either naming it wrongly or using an unrecognized SD card.
Grab another SD card or reformat yours, and try again. And again. And next time please use search for questions that have been already asked zillion times.
And if there was a simpler way, tell me, do you think that people would use more complicated ways for 2 years now?? Some basic logic.
And you posted in the wrong section.
thanks
thanks for the help.... but it didn't work ...
nothing works...
and the reason i decided to post my own thread was because i have tried almost everything on other threads and nothing worked i have also tried to use a different SD card and that also failed. and thanks for the advises but i already knew that ....
Did Ty check to see if the file is PD15IMG.zip.zip? If so, delete a .zip.Also make sure it isn't in a folder on your sd card.
If nothing works - then you're doing something wrong. Plain and simple.
Your MT4G isn't different from any other MT4G.
Look for what you're doing wrong. There are very few options.