I have a T-Mobile MyTouch 3g 1.2 and I have tried to unroot it and load the original rom back on it and for the life of me I can't. It updates the sappimg just fine in hboot until it gets to system and then I get some sort of error and have to reroot it and flash CM6.1 RC1 back on. I have tried running Universal Androot to unroot it with no success. Well, today I downloaded this nice little app from the Market called z4root by RyanZA(I think that's his name) and low and behold it actually unrooted my phone. I confirmed this by rebooting, opening rom manager app and it told me I need root to use it. I used z4root to reroot with no problems. My question is how would I flash the original T-mobile rom if I use this app to unroot my phone. Could I use the RUU.exe or is there a better way? I really want to go back to stock when the OTA for this phone comes out. I don't need to right now, but I just want to know how and try it so I know I can do it when the time comes. Would it be best to use a goldcard after unrooting to load sappimg? If anyone has any ideas or experience doing this please advise and I appreciate everyone here. This forum is great. I am a noob to Android devices and have been coming here about every day to read, read, read. I have learned so much here. Some of it is still gibberish to me, but I am learning. Thanks all!
When not flash a 32A 'port' of the mytouch 1.1 froyo ROM? It will perform exactly the same as any official update.
I was thinking about doing that, but after trying to go back to stock and failing I have kind of made it a challenge to get this done and figure it out. I guess since no one knows what to do I will just keep trying blind and keep reading. Thanks all and have a great day.
Related
I wanna wipe radio/pri/prl/rom/custom recovery/EVERYTHING completely to a stock 2.2 froyo sprint rom WITHOUT root and custom recovery.
After i return my phone to 2.2 like i just got it from sprint...
Then i want to full root it and have the new 1.8 RA recovery...
I guess whatever custom rom i go back to from there, i'll decide.. but for now
I want a piece of mind that my phone is properly working like it should from factory.
Thanks for any assistance on what proper steps i should take.
TorxT3D said:
I wanna wipe radio/pri/prl/rom/custom recovery/EVERYTHING completely to a stock 2.2 froyo sprint rom WITHOUT root and custom recovery.
After i return my phone to 2.2 like i just got it from sprint...
Then i want to full root it and have the new 1.8 RA recovery...
I guess whatever custom rom i go back to from there, i'll decide.. but for now
I want a piece of mind that my phone is properly working like it should from factory.
Thanks for any assistance on what proper steps i should take.
Click to expand...
Click to collapse
Firstly, how did you root your phone? I see your join date is from '07, so you aren't a newbie that came on here in June when you got your Evo (like me.....lol). If you rooted the "old school" way using toast's method, all you have to do is flash a Sprint RUU (any Sprint RUU, as it will prompt you to the an OTA update to 2.2 even if you flash an older RUU) and your phone goes back to stock. If you rooted with Unrevoked Forever that keeps S-off, then it may be more complicated. I wouldn't be able to tell you because I've personally never used any of the Unrevoked team's stuff.
oh, sorry for lack of pre-rooting details.
yea launch phone with(at the time) 2.1, and i used that 3 button OTA simpleroot.
can i flash the sprint ruu 2.2, then use the new unrevoked?
do i need to wipe any details with ##786#?
So just decided to get an evo. My wife has had hers since release day. This one Has the 2.20 and the 3.30.651.2 Build. The quality of the screen is horrible compared to hers (the color and brightness). Before even being able to root it I couldnt use QIK because it reboots the phone. Downloaded the latest one and I can open the software and its after my camera kicks on that it reboots now....
So i rooted it and got the s-off. Now I can take nand backups but its says they are corrupt. Cant flash a rom because it will hang on the Evo boot screen or it will drop to a boot loader loop with the HTC with 4 exclamations....
Is anyone else seeing this or is this guy flat out a lemon?
I have looked around the forums a little and found people having a hard time rooting and s-off which was easy after skimming the forums for a while. Thanks ahead of time for any input in this.
The screen problems im not sure how to fix
there is a new ota to fix your camera issues, yours is most likely the new hardware/camera 004 model.
for rooting the only method that works is toast's, unrevoked wont. Unless im behind on info. Have you tried toast's method?
Unrevoked works fine. Took me about five minutes to root useing that method when I got my replacement phone.
As far as your phone issues, take it back to the store and show them the problems. Get a replacement.
Oracle, go to your bootloader. What is the first line? Is it Supersonic EVT2-3 S-off? If so, I had the same problem. You have bad blocks. My recommendation is the that you flash sprintlovers ROM. It cones as a pc36img.zip, and you flash it through bootloader. I tried every method of rooting and none of them would let me flash through recovery.... I always either got errors while flashing or, even if it seemed to flash fine, it would never boot. Also, Sprintlovers will get your pri corrected. If this works for you, give me a shout, and I have an idea we can try.
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
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 have looked and looked but probably not in the right places... I have a rooted Evo 4G with froyo 2.2. I used unrevoked forever and know how to get the s-on back... I just would like to update the phone to the newest update and root it again. Is it still necessary to get s-on back then load the original ruu rom? I would think I just need to remove the unrevoked then update. The phone works I just want newer firmware on it... My apologies if I did not look for my response properly, but all I see is a reload the IMG file... I dont want to set back to factory... just wanted to post this question. Thank You
Mee2 said:
I have looked and looked but probably not in the right places... I have a rooted Evo 4G with froyo 2.2. I used unrevoked forever and know how to get the s-on back... I just would like to update the phone to the newest update and root it again. Is it still necessary to get s-on back then load the original ruu rom? I would think I just need to remove the unrevoked then update. The phone works I just want newer firmware on it... My apologies if I did not look for my response properly, but all I see is a reload the IMG file... I dont want to set back to factory... just wanted to post this question. Thank You
Click to expand...
Click to collapse
There is absolutely no reason to unroot. All you have to do is flash a custom stock ROM based on the newest firmware. A whole bunch are available for flashing in the Development forum.
It is much easier to leave the phone S-OFF and then either flash a rooted stock ROM or run a stock RUU. Then all you would need to do to obtain full root again (with stock ROM) would be to install a custom recovery and then flash a superuser.zip file, rather than turning the phone back S-ON and then going through a potentially complicated procedure just to reroot and possibly turn the phone back S-OFF.
Thank You guys sounds like a custom rom is the way to go... it would get rid of that IQAgent also... I'll look around for a nice looking rooted rom.