MyTouch3G [32b]
(Sapphire/Magic/ -MT3G)
"ORIGINAL"
ok i'v read alot on this but still getting mixxed results... my last research was on the wiki
FIRST: my concerns are SPL N RADIO spec's for "FROYO" (CM6 RC-NightlyBuilds)
iv ran engineering 1.33.2005 SPL
W/ BOTH - 2.22.19.26i and 2.22.23.02 RADIOS
now seeing there is a new SPL HBOOT "1.33.2010"
R We suppose to UPGRade? or even just FLash in general?
(take note: i am a graphic designer, so i perfer to make changes to boot-ups)
* -the wiki on sapphire hacking states
-"For T-Mobile MyTouch 3G or PVT32B Magics, it is reccommended you use the 1.33.2005 engineering SPL."
i couldnt find any date that this was posted so here i ask.
as for radio's both seem to work the same i suppose.... but i beailve updates r updates for a reason right?
I Have recently Unrooted to fix any issues,erase,etc the past years worth of crumbles n jumples that could be floating around somewhere outthere... hah.
as for unrooting it changed my radio back to 2.22.19.26i / n hboot to 1.33.0006
n yes i am currently rerooted with the same radio n hboot listed above. im currently on froyo cm6 rc3 nightly....
also my other issue in needing to despratley know what the sd partitioning should be for the cm6 nightly froyo builds...
im currently 96/512/ex2-3-ex4
reasoning in asking is because i do feel like there is lagging or strain somewhere on the device yett this could be the issues of froyo or the rom itself.
but these issues r in no way dramatic. i just want to know what the legit correccct proper scoop is on this shizzit. once again iv done the reading over n over again. but the dates r back from cm5 in 2009. so im wanting up to speed on 2010 information seeing that i cant seem to find.
also * clockwork recovery or amon RA recovery *
which is a better route for mt3g... personally im happy with amonRA's clean recovery work. but im just wanting to know the deali-O.
your help is greatly appreciated...
You can flash SPL 1.33.2010 to your MT3G, I just did that last week (from whatever came stock with the device, prevented me from using fastboot). I also flashed the radio to the newest version (2.22.23.02) and now get slightly-better reception (I think, anyway).
I like Amon Ra better than Clockwork. I tried installing Clockwork once and my phone refused to boot into recovery (stuck at mt3g screen), so I avoid it like the plague.
As for partitioning, I just leave my entire card FAT and use "Swapper2" to create a swap file. Works just fine, and without the hastle of partitioning (we are talking about swap, right?)
Are there any issues in installing Clockwork recovery over amonRa? I have a rooted MT3g 1.2 with amonRa, but would like to use ROM Manager (requries Clockwork). Did you use Rom Manager to install Clockwork?
jdbuddy said:
Are there any issues in installing Clockwork recovery over amonRa? I have a rooted MT3g 1.2 with amonRa, but would like to use ROM Manager (requries Clockwork). Did you use Rom Manager to install Clockwork?
Click to expand...
Click to collapse
It can be done but from my experience it was not good Amon_Ra is more stable in my opinion i would have problems with clockwork. For instance with the MyTouch 1.2 I had to flash manually then tell recovery manager that I did and it will work. Both recoveries are excellent its just a matter of opinion and personal choice.
Related
So I guess it really is easy to brick a MT3G - can't fastboot, can't enter recovery.
Just stays on the MT3G boot screen.
I've tried all the boot key combinations, does anyone have any magic solutions that may work?
It was rooted just fine (from the first day rooting was discovered, using the gold card method). Tried to upgrade to a CyanogenMod, and somehow messed things up. I suspect I screwed up when I flashed the radio.
Hmph.
Why did you flash a "new" radio...?
The radio that comes standard as a packaged feature for the T-Mobile USA version of the HTC Sapphire (MT3G) is 2.22.19.26I - there was NO NEED for that adjustment. I'm not suggesting that flashing a new radio is what corrupted your device, but it certainly could have contributed to the eventual cause.
The One-Click Root Method is the safest way (until patched via Google 1.6 build - also known as Donut) to ROOT your MyTouch. I've used that for three various Android devices, all of which functioned properly immediately after. No flashing of upgraded radios, SPLs, etc.
Finally, from the beginning - as any ROM flasher should know, you SHOULD HAVE backed up your STANDARD, T-MOBILE PROVIDED, Cupcake v1.5 build using NANDROID from the Recovery image. If that is the case, restore those settings and start all over with the "rooting" process using the One-Click method via the Recovery Flasher application.
Good luck.
damn i think i brick my phone after loading a radio ugh it sux
Again.
Tobi87 said:
damn i think i brick my phone after loading a radio ugh it sux
Click to expand...
Click to collapse
Re-read what I posted previously.
The MyTouch comes standard with the latest radio and and SPL (even if considered PERFECT) doesn't prevent you from running any of Cyanogen's latest builds. I don't see why you thought that flashing a "new" radio was going to do something special. As for the "Gold Card" method...I don't see why you didn't think to try the easier, safer, much less work type of method. THE ONE-CLICK ROOT METHOD!
I rooted my MT3G early on using the goldcard method - it is currently running the RAv1.1.0h rom from the original rooting thread. It has the 1.33.2005 SPL and the 3.22.20.17 radio. In fastboot I can see that it the SPL is an HTC version (I think that is what PVT 32B ENG S-OFF H means, right?).
I'm having trouble moving to a 32B rom, and no matter what I try, I can't get the damn recovery image to switch from the current RAv1.2.1H to the G - which is (I assume) why I can't install any 32B roms.
Any foolproof way to change my recovery image from H to G? I've followed all the steps listed on how to do this in Fastboot and using ADB to switch it over, but no matter what I do, it has no problems booting correctly with an H recovery image, but not with a G.
Any 32B roms just makes the phone hang at the splashscreen, so I know it's a rom issue.
OR - Am I missing a step here - is there a different spl I need in order to get my MyTouch 3G to think it is a G edition again. OR easier yet, should I stop whining and just find a reliable 32A rom that works on it (assuming something without too much HERO stuff?).
YES - I searched everywhere, I spent countless hours on it, but I can't help feel I've missed something really stupid, so feel free to call me names and point out the obvious (just don't say "try Google).
Are you still able to use flashrec? If yes try to flash this one>> cm-recovery-1.4 works fine if you want 32B roms. Enom uploaded latest version yesterday.
http://forum.xda-developers.com/showthread.php?t=549754 nd if you want version prior to this then go to http://www.4shared.com/file/129108782/3953f016/HTC__crc1__Android_rooted_Rom_32B_TMobile.html
unzip and make sure to install one after the other. Large one first and rename as update ,put in your sd card. Once that is performed then go to the next small one about 14mb. Rename as update and put it in sdcard. Dont forget to delete the large one if already there.
Let us know how you go on.
No - Flashrec won't run since the rom I'm currently using has the exploit patched.
Good tip though, thanks! Any other thoughts on why I can't get the 1.2.1G recovery image on my phone? Or an alternative way to get it to install?
EDIT: Took a few steps back, installed the sappimg for the MT3G, then did flashrec and then did the update with the rom you posted. Thanks so much for the tip and inspiration!
Yes, well done.Thanks for letting us know.And yes flashrec wont work on these rom also. I tried many times to flash with RAv 1.2.1image but it seems it was not possible. I asked emon in his T Mobile rom thread where he gave me a tip as to how to go about RAv.... but that hasnt worked.
But there is a solution if al you want is to make 3 partitions.
I followed Paaragon method as described on http://forum.xda-developers.com/showthread.php?t=512873
and it worked. So try that.
I tried many different roms and finally settled on enomther's
because it is very fast, not too cluttered and just perfect for 32B boards. And further more, there isnt anything that doesnt function.
PS: I prefered the one prior to current as on 4shared. But thats personal.
unroot completly by re insttalling the saphimg and go with the oneclick root method from the unlocker thats what i did and TITS! perfict running hero and full 32 b envierment raido and roms ... be carefull with the 32 a 32 b mixup could be the end of your touch....
Hello...
Fairly new here...
Also new to this rooting/rom business...
but, to the point.
I have a Rogers Magic 32A, with the stock Rogers rom.
my fastboot specs are
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76. 0010 (SAPP50000)
CPLD-12
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
I am using the universal androot app, and running ROM Manager.
Whenever I boot into recovery, it either freezes after a few seconds, or resets the phone back to the first splash screen, and continues to work as normal (no bricking or any of that jazz.)
So anyway, my question is...
Does anyone know why it's doing this?
I got it to flash Cyanogenmod 6.0 once, but it didn't actually install.
Do I need a different radio and SPL?
I've tried searching, and I found nothing... but if there is already a thread with this issue, I'll gladly revert to that, and delete this thread.
TL;DR
-Phone is involuntarily restarting when I go into recovery mode
-Running stock Rogers rom, ROM manager, rooted with universal androot app
-New to android customization
-Am I doing anything wrong?
Thanks for reading.
I have the same problem!!
What I can do to fix it?
I'm really scared ...
the problem likely is you are loading the ebi1 recovery (magic 32a running 3.x radio) on you "hero like" magic (magic 32a running 6.x radio)
The hero recovery will work but you may find few roms.
I'd reccomend these rooting instructions
The process will work from the top I believe but since you ran androot after placing the files onto the phone you can skip to where I run exploid (with the seceetlol password) and run 'su' instead of exploid.
Once you have a 3.x radio with working rom and recovery if you want to checkout rom manager you can hopefully with less issues and if an issue happens you can always flash a recovery via fastboot.
I did end up fixing my issue.
Great Big Dog on the androidforums helped me out...
I tried to look for my thread that I posted on the androidforums, but I guess it got deleted...
pretty much... I followed GBD's quick root guide for the post 911 update for rogers magics, with a tiny bit of a switch for flashing the amonRA rom.
I can't remember exactly what it was, and I really wish that thread didn't get deleted.
And I can't link in any posts, so I can't really help you out.
I usually always just suggest installing a fresh RUU, especially if you don't know what you're doing... like me.
you can probably find one on the htc website.
I have an HTC Magic 32B (myTouch 3G) and I installed CM6.1 to it a few days after the new year started. I noticed on Wikipedia that it is supposed to have 192MB or RAM. However, if I look at the OSMonitor app it only reports 98568K total memory. (To be sure that OSMonitor is correct it says my Samsung Galaxy S has 341000K which is what speedmod kernel says)
I read on other websites that flashing a new SPL unlocks more RAM but I am not sure which one to flash. It looks like this kind of flash is one of the most dangerous. I would really appreciate any help in flashing a new SPL. From what I have read, it appears that flashing is done using "fastboot" through ADB.
Just a side note: I got the phone in December and it came with Android 1.5. Immediately it did 2 over the air updates. One of them appeared to hang in recovery mode until I pressed a key and I got the choice to restart. The other over the air update went by flawlessly but none of the updates appeared to upgrade Android 1.5 (which is why I installed CM6.1).
Need your current fastboot information. There is an SPL made by ezterry that remaps some of the system RAM from the camera to the OS's usable memory that you can upgrade to...it's known as the 1.33.0013d SPL which will also require a radio upgrade to 2.22.28.25 or 2.22.27.08. It's fairly simple, the danger parts comes from trying to do the process improperly or by using an incorrect SPL/radio combination for your device. The danger is minimum as long as you do everything correctly. The only real danger would be if you let the battery die during the update or if you do something radical like dropping the phone during the process. Even then the danger is slight. I'm assuming you've already got a custom recovery installed since your using CM 6.1, did you install Amon Ra's recovery or are you using ClockWorkMod?
hboot-1.33.0013
radio-2.22.19.261
recovery: amon-1.7
From what I read it would be: wipe cache, wipe dalvik, flash radio, flash SPL, reflash CM6.1? I've heard bad things about flashing radios. I've noticed that the web browsing on the mytouch 3g (htc magic) is considerably slower than my SGS, both running android 2.2. Would the RAM increase really help the performance or not?
Not really. There isn't much you can do for the speed on the Magic because of the hardware limitations. You can actually just flash the new SPL from recovery. If you search for the 1.33.0013d SPL there's a thread for it that has an update package for going from the 1.33.0013 SPL to the hacked one.
Sent from my LG-P500 using Tapatalk
Well if it is not worth it, then I don't think I'll do it. Thanks for the opinion.
Well it couldn't hurt either and it's not that complicated. Just download this file and flash it from recovery.
Well according to this won't I have to flash a new radio? On top of that, will I have to reinstall a ROM because I read that after flashing a new SPL it takes you back to recovery after rebooting because the ROM has been erased. In that case, could I use a nandroid backup? I also read that you must do radio first then SPL right?
I also saw this on that link "> A Rom (note: many cm6 based roms block install because of the '1.33.0013d' bootloader Please use firerat's SpoofSPL) "
My apologizes, I brain farted on the part about you having CM 6.1 installed.
I have been trying to get this thing to work. I got it rooted, i installed CM6.1 and it had that horrible green tint.
I updated the radio and hboot to SPL 1.33.0013d and RADIO 2.22.28.25
the hboot wouldnt update for whatever reason to the newest one.
I installed yoshi's rom since thats the reason i even updated the spl to begin with and sure enough it ran but it was SO slow i could barely use it.
Went back to install a diff rom like the CM nightly and its stuck in bootloop. Doesn't seem to matter what I do, I can get back into CWM but i cant seem to get a rom to install right.
Im coming from the epic but any help with this would be immensely appreciated.
Have you tried flashing a different kernel (like ezterry's)? It cures the green tint thing...
Maybe it will solve the other issues too...
Here's the link:
http://forum.xda-developers.com/showpost.php?p=8930875&postcount=475
or
http://forum.cyanogenmod.com/topic/...ghtlies/page__st__5660__p__117678#entry117678
or
http://droidbasement.com/db-blog/?p=1498
I should of explained more. After installing CM6.1 and getting the green tint I tried yoshis but had to update my hboot and radio. Now that it's updated every single other rom I try BESIDES yoshi's bootloops.
The issue is yoshi's runs too slow on 32B, there just isnt enough ram and I have to get back to CM6.1 for the phone to run properly.
I have no way of reverting back to an older radio and I dont know why the newer radios are stopping the rom from installing but it seems like im sutck and I really need to fix this issue.
I've tried installing the sappimg.nbh and my hboot wont recognize it for going back to stock.
I cant get amon Ra recovery to work through rom manager only CWM
At this point I have no idea what to do bc I cant give them the phone with it running this slow. It's unuseable
marquimsp said:
Have you tried flashing a different kernel (like ezterry's)? It cures the green tint thing...
Maybe it will solve the other issues too...
Here's the link:
http://forum.xda-developers.com/showpost.php?p=8930875&postcount=475
or
http://forum.cyanogenmod.com/topic/...ghtlies/page__st__5660__p__117678#entry117678
or
http://droidbasement.com/db-blog/?p=1498
Click to expand...
Click to collapse
got it working, required 2806 based kernal and the cyanogen mod nightly RC1
basically found here
http://forum.cyanogenmod.com/topic/9819-cm61-rc1-2708port-for-new-radiospl/
really wish **** wasnt that complicated when the answer was so simple
Unless the rom supports the new radio/spl (cm6 doesn't), you will have to flash a 2708+ kernel.
Try a rom with Autokernel (ezgingerbread, cos-ds, sense-lx, dreamteam froyo [in rom manager as AOSP Froyo])