quick question :( - myTouch 3G, Magic General

hey can someone tell me how to change from the rom evil hero 2.7 that i have now to MLIGN 3.3? my recovery image is 1.2.1 and i heard i need to get the 1.5.2 is that true? if i do need to change my recovery image to 1.5.2 how do i do that.

dowlnoad a 1.5.2 recovery (although there are even newer ones) and flash that as well. Instructions are... everywhere (even at the page where you download recoverys)
Then get the mlign rom and flash it
Learn to help yourself and do some searches. Instructions are literally everywhere.
edit- since ive never dealt with that version recovery before, I don't know why you have to upgrade and don't really see a need for it but it doesnt hurt to go to something newer.
Also, i have a question. How were you able to find MLign3.3 but not the recovery image+instructions? I don't get it.

ok thanks so i did as you told me and it seemed to work perfectly when i rebooted the HTC screen came up and said process not responding and it gave me the option to force close or wait. what do i do?

Not sure, did you wipe and everything before flashing the rom?

Related

Flashing problem...

Hi all,
I have a Magic 32b and recently put the Modaco_custom_1_51 rom on, I think with the Amon Ra's recovery image (as recommended on unlockr)
It was working ok, not great, a bit slow and mms wouldnt work, so...
I decided to change the rom, unfortunately I was in a bit of a rush and I kind of forgot what I was doing...
I went straight to the Recovery mode and clicked 'part sd: fat32+ext2+swap'
Then I put the new rom on using usb storage mode, I clicked on apply sdcard:update.zip and of course it wouldnt work (all without applying any recovery image when the phone was working), I rebooted the phone and now after the vodafone image I just get a blank black screen...
I then woke up and realised what i'd done.
I have tried searching what to do when this happens but I couldnt find anything... I've never used abd and dont know how the commands and stuff work... I just flashed and applied the rom using the 'one click' method on unlockr.
I would appreciate any help you can give, theres propably a simple way to do it (well simple for you guys) but I just cant work it out, if anyone can give me some instructions it would be really grateful.
Im new here so take it easy on me
Also... im not sure if I posted this in the right place, sorry if I did.
Regards
Gino
One of the 35 people that have looked at this must know the answer....
Pleasee

I'm incompetent. Is there anything I'm missing?

When I first became active, I rooted my phone, I made a recovery off the original recovery rom. I updated to the what my phone says is the unofficial modaco rom v1.3 + an update
+ a theme.... bu then me and my girl split and my recovery images were on a flash device she had. I see some stuff about an updated version of recovery... talk of radio's amongst other things.
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Cloned2 said:
When I first became active, I rooted my phone, I made a recovery off the original recovery rom. I updated to the what my phone says is the unofficial modaco rom v1.3 + an update
+ a theme.... bu then me and my girl split and my recovery images were on a flash device she had. I see some stuff about an updated version of recovery... talk of radio's amongst other things.
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Click to expand...
Click to collapse
Flash a new recovery....fisrt things first
Then do factory data wipe from recovery.
You should probably reformat your SD card...
Wipe Dalvik....
then flash any of the good ole' zips that are up now..
Personally before I do any more flashing I am waiting on sprint release OR this new "Toasts Awesome Sauce" I see in another thread...if it blows everyone else away speed wise....I hope they got OC working.
Only reason I am waiting for an official sprint is because I am sick of wiping my phone ~ to lazy to back up ~.
Cloned2 said:
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Click to expand...
Click to collapse
You don't have to install the new recovery to flash the 2.x ROM's. However, the new RA 1.6.2 was updated and had some bugs fixed, with also a little more added features, so it's probably worth your time to download and flash.
To flash a 2.x ROM, just do as you did before, find one you think you might like, download it and then copy it to your SD Card, after that its a matter of Nadroid back up and then flashing the new ROM.
thanks for the heads up guys.
I just couldn't be sure if there were things that needed to be changed outside of just flashing the new roms.
Back when i was more active I recall there being some roms that you couldn't flash from but a factory reset will revert me out of my modoca flash so that, that problem doesn't potentially crop up?

Downgrade Problem!

I have searched and searched, tried every method, but I am offically stuck (I think) - I'm prepping a rooted Eris for return - i had previously been able to flash the 2.1 RUU to return to stock, but it now will not work - I guess somewhere along the lines of rooting/ROM flashing my bootloader has changed (it is now v1.49.000) - I can't get any RUU to work (get ERROR in RUU interface) - I have also tried flashing a P00IMG through HBOOT, but it also errors out (something is older than something else - forgot exactly) - I have tried flashing new HBOOT/Recovery Image through ADB per a JCASE post, but that will not work either - I've gotten older ROM's loaded that will allow for new OTA updates, but they ultimately will not work (signature issues i believe) -
So the question is, is there a method that will get me back to 2.1 "stock" & get rid of Amon Ra recovery?
Again, I have searched and tried every method I could find - I have updated my SDK - help anyone?
Ive seen people just send in rooted ones without any problem, so I dont know if they'll check. But if your worried, i would just flash a 2.1 rom that looks like the stock, cause i dont think they'll know the difference.
Do you have a Nandroid backup from when you first rooted?
crax0r said:
Do you have a Nandroid backup from when you first rooted?
Click to expand...
Click to collapse
Unfortunately I don't have it - you wanna loan me yours?
I'm only kind of kidding....
download unzipme.zip which jcase removed on xda from here http://androidmobileos.com/?p=14928 Inside theres dowgrade rom that you flash through custom recovery (which ever one you use). After that you just follow the instructions (adb parts). Works very well. If you will have any issues with adb part as far as flashing back to stock recovery and hboot than check your hboot version and make sure its s-off. If its not you can get it s-off with batery pull trick.
i had an issue like this where the ruu would say that my phone was disconnected and told me to connect it to the computer,i was on a froyo rom,i flashed a 2.1 rom and the ruu worked,just an fyi just incase this might help if you want to return to stock 2.1,once you run the ruu and sync with google you wiil receive the july update also.
sent from my Eris using Tapatalk pro

[Q] MT3G 1.2 Stuck @ Splash Screen

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

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

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

Categories

Resources