Hi,
Already posted part of the situation in Amon_RA's recovery thread but neither of the answers there seem to solve my problems. Decided to post it here since the problem seems to involve aspects other than the recovery itself.
Here's the complete situation:
Had problems with RA recovery freezes since the start and with different versions. I could (and can) enter recovery mode (v1.6.2), scroll down the options but after 15 seconds the recovery just freezes and reboots every single time. Checked the version (H) and the MD5, they where all correct. Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Tried booting the latest RA recovery trough fast-boot and it worked fine the first two times I did it (scrolled down the options for like 10 minutes and it didn't freeze). After that it did not work and got the freezes+rebooting problem back again. Tried ADB, Flash-rec and flashed the recovery but got the freeze+reboot problem once again. Re-checked the version and MD5 and they where all correct.
Why does this happen? Any clues?
Thanks for your help!
I'm kind of lost here...Could it be a radio or SPL problem? Should I re-flash/update it? I never had problems with the stock ROM so this situation is really odd...
Can anyone help?
Thanks in advance!
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
But anyways, I'm a bit confused. What rom are u using?
noroses said:
Hi,
Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Click to expand...
Click to collapse
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
I have no idea dude but what I would do if I was in your situation:
1) Flash ENG SPL, something like 1.33.0010 (double check everything, i dont like advising people to play with their spl/radio so dont just take my word)
2) load up recovery and give it a try! if all that fails...
3) I'd backup your phone via nandroid in recovery (i pray that it doesn't freeze lol)
4) Wipe wipe wipe
5) Go into fastboot, fastboot erase system -w and then try another rom! And if the rom is good, then go back to your old one. Try to find out what the prob is.
It appears that you're able to flash roms still even with your recovery freezing (so weird) so I dunno. Just give it a try I guess lol
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Hi,
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
Click to expand...
Click to collapse
Will try this. Can I flash the SPL trough the recovery?
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
Click to expand...
Click to collapse
Will have to check and recheck this complex process.
But anyways, I'm a bit confused. What rom are u using?
Click to expand...
Click to collapse
Now I'm using stock 1.5. I tried cyanogen, superD and other 1.6 Roms and they all freezed at the android setup process. Used myhero for a week with no problems whatsoever. Since I have a nandroid backup done with CM's recovery I restore everything back as it was.
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
Click to expand...
Click to collapse
The Amon_Ra recovery freezes every time. It doesn't give me enough time to do anything...Now I'm using CM's recovery and I have no freezing problems while in recovery mode. The problem is after I flash a Rom and reboot. The ROM experiences freezing problems (just like the Amon_Ra's recovery).
Thank you for your answer and suggestions!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi,
Thanks for your answer.
I have never tried with the phone plugged into a socket but did it with the phone running on battery and connected via usb to the computer. Should it make a difference?
Could it be a hardware problem? I never had problems with the stock ROM or with the myhero ROM...
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
digitaljeff said:
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
Click to expand...
Click to collapse
Checked that guide but I'm unsure about this part:
If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
Click to expand...
Click to collapse
This part I can do within the recovery to enable flashing via fast-boot right?
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
digitaljeff said:
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
Click to expand...
Click to collapse
Will try that tomorrow.
Thanks for your help!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi again,
Still didn't mess with SPL and Radio. I'm still afraid I'll brick the phone..However yesterday tried a few simple things like using another sd card or entering recovery while plugged in. These two things seem to influence the behavior of the latest Amon_RA recovery but don't solve my problem completely. Example: When I enter recovery using the original SD card (2gb) the recovery would freeze within 20 secs max. Using another SD card (128mb) most of the times it would take longer to freeze (4 or 5 minutes). Sometimes it would not freeze at all. Although this seemed to influence what happened it wasn't constant and could not find a pattern. The same with the phone plugged into computer. Sometimes it helped. One thing is certain: with the original SD card and unplugged from the computer the recovery freezes within 20 secs every single time.
With the CM 1.4 recovery never had any freeze problems. It seems to work great while in recovery mode. The problem is after a flash a ROM I have freeze problems with the ROM itself (tried different ROM's, CM, SuperD, etc and got the same freeze problem). The only Rom that worked fine was myhero 2.0.5.
This is a very strange situation and I'm starting to think that this could be hardware..
Would that be a SD card problem?
try using another SD card and see if the problem still occurs
I am having exactly the same problem, did you ever find a solution?
Went from a fully updated magic 32A (1.76.0009H) now i'm at 1.76.0008
UPDATE: I just found that the hero recovery works (I would post link but xda doesn't allow new users to do that) however it may still be necessary to downgrade radio and spl
I had also same problem. My device is Magic 32A radio 6.35. Solution was to reflash recovery-RA-hero-v1.6.2.img.
Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).
knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.
so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814
lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App
knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App
knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit
NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.
Possibly try to re download the sappimg from the mgic spl thread?
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.
NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!
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.
So.. I had CM6.0.0 Stable running on my 32A HTC Magic. All fine and dandy. Then I saw the Smoki ROM and I decided I wanted to flash that, but only one problem. It required a different radio and SPL. So no problem, right? I flashed the required SPL and Radio through fastboot. Looks good right now! Then I turn off the phone and boot into recovery.. but wait.. it just doesn't boot into recovery and just decides to hang at the HTC Magic logo.
I no longer have a ROM installed since I wiped. So I can only go into fastboot. Is there any way I can fix this, or did I just brick the **** out of my phone?
You should be able to still have a Rom running. That happened to me I wiped, I forgot to go into recovery and it loaded the phone and everything was fine
Sent from my PC36100 using XDA App
Try to flash different recovery from the flashboot. It seems that the latest Hero recovery doesn't work with the new radio, get a previous version.
There is a comment in red from Amon_RA:
"Only flash recovery-RA-hero-v1.6.2.img if you have a 32A Sapphire with 6.35.x.x radio and 1.76.x SPL, recovery-RA-hero-v1.7.0.1.img will NOT boot! I'll create a new Sapphire version soon."
Post here ALL fastboot info. ALL.
I see you have posted in different threads but the info you provide contradict each other!!!
Start by doing NOTHING MORE and post here all fastboot info so we can get an overview of what you have been doing.
Also which recovery image you have on and which roms you have used.
DON'T WORRY.. as long you can boot into fastboot you are NOT bricked :0)
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.