Hi all, thanks in advance for any help and my apologies if this exact problem has already been resolved. I searched through this forum and found issues *similar* to my problem but nothing exact enough for me to find a solution.
My experience with Android is limited but have quite a bit of terminal UNIX experience...so I'm not a total noob and I can follow directions pretty well.
I purchased a MT3G from someone and everything seemed to be in order when I checked it out (and the price was good, so I figured I didn't have much to lose). He was running Cyanogen Mod on there but of course I wanted to restore to factory settings and build it up from scratch on my own. Thinking that I knew what I was doing, I booted into Recovery (Home/End key simultaneously) with no issues and ran the factory reset utility, thinking that this would just drop the phone back to factory settings and I could re-root it from there. When I turn the phone back on, it just hangs at the "splash" screen and runs the animation over and over again.
I can still boot into Recovery and I can get into Fast Boot so I hope I am not bricked.
Here is the output I get from Fast Boot (attached file).
I tried to restore with a SAPPIMG.zip that I found but it said wrong device...
Any help would be GREATLY appreciated. Thanks!
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
If you get an error, you need to download an engineering spl, and then try. (Engineering 2010 SPL)
The link and instructions are around somewhere on XDA.
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Vontropnats said:
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Click to expand...
Click to collapse
Yes sir, that is the easy way!
there are plenty of 1.6, and 2.2 roms out there.
Just download to sdcard, boot into recovery, wipe and flash
Don't flash any SPLs. Your fine as long as you've got a custom recovery. Just flash another ROM from there and make sure you wipe data, dalvik-cache, and cache before flashing. I've been running CyanogenMod 5.0.8 since the summer (CM6 ran like crap) and I've been happy with it so far.
Sent from my HTC Magic using Tapatalk
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Vontropnats said:
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Click to expand...
Click to collapse
Not true you can root using the this app then use rom manager to install clockwork mod recovery. This is how I helped my friend root his device.
attached is the app
Related
Hi
similar to an other thread here if tried to change my SPL
and never recovered.
I can still get the blue led going using TrackBall + EndCall buttons.
The orange led lights up when I connect the usb cable.
But I cannot see it from the pc in any way (adb/fastboot).
there is some life in it but not a lot, have not seen the screen light
up at all.
Would it be possible to get a new bootloader/spl on it? Perhaps using
some kind of automatic update mechanism that is build in using an
update.zip file on the sd card?
Any help is more than welcome.
abe
*bump*
hmm, post needs al least 10 chars... should be enough now...
Has everyone also drawn a blank on this?
abe
Try downloading the ruu from your phone's official reseller.
T-Mobile USA standard OS.
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Sorry to hear that. I was thinking of installing Haykuro Apps to SD ROM and it needs to change the SPL. But I think not worth taking a risk.
Can you tell a little bit more which ROM were you planning to install?
Which SPL did you update to?
Which ROM did you have at the time of SPL update?
Which thread or instructions did you follow if any?
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
@Reignzone
I do have a nandroid backup but I cannot get back into recovery mode,
or fastboot mode or anything... the pc does not recognize it either.
@technicolor
I installed the Cyanogen recovery image and was able to install
one of his rom's. It worked fine but then I wanted to install
a Hero rom and I wanted to update the SPL.
Used the cyanogen recovery to update the spl using an update.zip
file. the phone restarted the "android" update screen came on
briefly and it never came back on...
changing the recovery rom should not be an issue,
and normally I think you do not need to flash your spl at all any more.
you can do a lot with the fastboot mode and one of the recovery roms
mentioned by Reignzone
abe
Reignzone said:
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Click to expand...
Click to collapse
This is the same advise you gave me yesterday on my bricked MT3G, but if you can't enter recovery mode, a nandroid backup ain't gonna help much, is it?
Also, any cupcake downloads are not going to help either, if you can't fastboot or enter recovery.
I appreciate you trying to help, but if you pay attention to the OP (and my own post), you'll see that your advise isn't going to solve anything.
For starters:
My advice to have those of you who are in need to take an approach that allows you to backtrack you work. Perhaps you left out various details of your issue or process taken in order to end up where you're at.
Your bitterness isn't appreciated for my having misread the problem.
YOU are the one with the F***** device, not me.
Anyway, all that aside; you might try to read-up on various threads that could be of some help. Google search, HTC support, ADB, etc.
There's always something to be done.
Good luck.
abeman said:
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
Click to expand...
Click to collapse
forum puffering aside, RUU is ROM Upgrade Utility
Prepackaged programs that bypass the phone's software altogether to reflash the rom
My carrier is Rogers of Canada and I have their "HTC Magic" phone
Be warned that Rogers is intentionally altering their hboot to disable system changes, you may not be able to cook your os after using this rom update.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe
Ive got a bit of a problem. I didn't read things over carefully and didn't realize i had HBOOT 1.33.0010 from Rogers in Canada...
So I booted into RA recovery 1.2.3H and loaded cyanogen 4.2.13 onto my magic. Now whenever I startup or go to market i get an error "com.google.process.gapps has stopped working" force quit and im not able to download anything.
Did I screw up by not working around the perfect GPL first and how do I fix this? Thanks in advance for the help
You need to flash the base defanged before you flash the CM build. Read the Cyanogen Wiki
Go to Installing Tutorial, choose your device, and follow the instructions.
What SPL should you have to flash a rom
Cyanogen's roms does not require you to have an engineering spl. So you're good with stock.
This may be a stupid question...but how do you know when you have root? and is it possible to load another rom onto the device without root?
You would know if you have root. You have to go through a process to get it. And no, you can not install another rom without it. Google how to root your phone. Takes 2 mins.
Oh...well I flashed another rom onto my magic and everything works great now. I guess I do have root. Sorry for the bother and thanks all for the responses.
Hello all,
Here's what happened - I DL'd the app 'ROM Manager' from the Android Market, installed and allowed this app to be the recovery for my MT3g (non-Fender and non-headphone jack version).
Suffice it to say that the ROM Manager app jacked up my phone... none of their items worked for me. I uninstalled the ROM Manager and now when I tried to go to recovery mode (power + Home) I get nothing but stuck on the MT splash screen
My phone is rooted, originally ran the recovery-RA-dream-v1.6.2 recovery and am currently running a 2.1 ROM.
I have tried to redo the flashrec-1.1.3x and this does not work.
Where do I go from here? I'd like to be able to partition my new 8GB SD card and I can't even do that...
Thanks in advance.
If your phone is rooted, can't you just flash the previous working recovery via fastboot again?
-------------------------------------
Sent via the XDA Tapatalk App
You should be able to put the recovery image on your sd card and use the flash_image command from the terminal right? thats what i did
Mod. edit: not dev related, moved to general
twigster said:
If your phone is rooted, can't you just flash the previous working recovery via fastboot again?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Just to let you know, it is possible to root a mytouch without ever having installed an SPL that allows flashing though fastboot. I know from personal experience that the one-click flashrec method does this
adavis159 said:
Just to let you know, it is possible to root a mytouch without ever having installed an SPL that allows flashing though fastboot. I know from personal experience that the one-click flashrec method does this
Click to expand...
Click to collapse
I know, thats what I did as well.
But since then, till the date I changed to an engineering SPL, im pretty sure I have always done the subsequent changes to my recovery and spl using fastboot, even after starting with the 0010 SPL (which was at the time a problem SPL) and using flashrec to change the recovery before installing my first non stock rom, being cyanogen 4.x.x, still with the 0010 SPL.
I do know that it only became necessary for me to change my SPL when I wanted to try new radio ROMs (subsequently moved back, and took the chance to move to the 2010 engineering SPL) Before that I was actually too scared to change the SPL because of the brick threats.
I used the cursorsense rom thread instructions on how to change the radio and spl, and it worked great.
Maybe, so far, I have been lucky not to brick my phone. But I have always followed well documented threads on the dev section and so far so good, not excluding one or two times when I thought I had made a nice brick, but just persevered.
Fastboot is your friend, and so is XDA if you are nice to it and the good people who frequent it.
If you look through the threads, and in the development section, there are alot of areas where they give the commands necessary for a variety of actions, and peoples responses on whether it works.
I don't yet believe in the programs created to do everything for you, nothing against the devs, who are all great, just not quite happy enough with comments posted to try them out yet.
(I think my response was little longer than needed) ;-)
Thanks for the info guys...
Problem was I could not boot into fast boot - the recovery was not there.
What I ended up doing was unrooting then rerooting my phone, reloaded my ROM and went on from there...
That might have been the long way of doing things but it all worked out well.
Hi there!
I've been searching and looking for any other posts with the problem I have. And I've come up with nothing..
This is my situation; Rooted my HTC Hero (EU) and flashed Eclair Vanilla 4.0 just days before the release of the original update from HTC.. Wanted to go back to the original ROM, followed the instructions and this is where it all breaks down.
It doesn't work and now I've lost the Amon RA bootloader and I can't boot it up, all though the Eclair Vanilla boots up if you boot the phone. Recovery boot doesn't work, been trying with several methods i.e. Goldcard method.. But no luck. And I've even tried the RUU program and it didn't find the connection on the USB but when I boot the phone in to Fastboot it can find it :/
And now I'm hoping that someone here on XDA could help me, since users on Swedroid forums doesn't know how to answer a post.
I'd really like to have some help, thankfull for every advice and I really hope I can fix this since the Eclair Vanilla 4.0 ROM really sucks and drains my battery.
Sincerely yours
Andreas
Download ROM Manager from the market made by Koush, open the app and flash his recovery image. Once this is done, re-open the app, scroll down and click the flash alternate recovery image (Amon_Ra-v1.6.2). It happened to me not long ago to lose my recovery image and I did this and it all worked ok!
As for returning to the original ROM well sorry bud but I can't help you with that!
Hope this helps!
Cheers
Okay, the only one I found was from some ClockworkMod guessing that would work too.. Imma try that one out
If you want to go back to unrooted ROM. I think this should work.
- Download the appropriate (EU) RUU ROM
- connect your phone to your PC
- flash the official ROM from your PC
That didn't work since it didn't find the USB Connection, but the ROM Manager did work! And I'm flashing HTC_HERO_WWE now.. Thank you sooo much kukussi! You made my life so much easier now!
addestyle said:
That didn't work since it didn't find the USB Connection
Click to expand...
Click to collapse
In Device Manager, right-click on HTC Bootloader, Update Driver..., Search on Hard Disk, and choose "My HTC".
RUU will now recognize the phone
no problem!
addestyle said:
That didn't work since it didn't find the USB Connection, but the ROM Manager did work! And I'm flashing HTC_HERO_WWE now.. Thank you sooo much kukussi! You made my life so much easier now!
Click to expand...
Click to collapse
Glad I could help bud! Enjoy your phone!
Cheers
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