Hey,
I have a Vodafone Magic 32B, which I am using with a Three simcard.
Yesterday, I started trying to root my device.
My device was running 1.6, so I tried to downgrade, following theunlockr. com/2009/08/14/how-to-root-your-mytouch-3g/
After many issues, I managed to get to stage 27.
Noticing that he linked to a 32A Driver, i instead tried to progress with the lastest AmonRa-Sapphire-V1.7.0G.img.
When this didn't work, I tried a few other versions that I had downloaded throughout my exploration of rooting.
At this point, it was 4.30 in the morning, and I decided to call it quits.
Luckily, i had made a nandroid backup.
I restored it, and, thank god, my phone booted.
However, it wasn't a restore as such.
The menu is different, the app store is different (and the camera is noticeably poorer).
However, checking the Firmware version, it says v1.5?!
1)Does this mean I successfully downgraded?
2)From here, how would i root the phone?
3)After i root the phone, is there any way to get back to the 1.6 interface? With a better camera (that can be accessed by apps)?
Thanks for any advice you can give. I'm aware that there may be loads of post like this, because i spent a good 12 hours yesterday sifting through the various methods. However, I would really appreciate any help, because I don't want to brick my new phone (i just got it, second hand, yesterday).
Figured that i'd post what pops up on the fastboot screen
Sapphire PVT 32B ENG s-off H
Hboot-1.33.2005 (SAPP10000)
CPLD-10
Radio-3.22.29.17
Hopefully, this might give someone the info they need to advise me.
Moved to General
SO my roommate and I have been trying for daays to root my phone now and we just dont know what to do. He has a rooted nexus one and knows how to do alot of stuff and we cannot figure this out.
So far alls we have been able to do is downgrade to cupcake using the goldcard method. We used the method from the UNLOCKR and can get as far as installing the rom and it will reboot and stay on the vodaphone screen for hours and do nothing i have tried taking the battery out and restarting multiple times. Just something isnt working here.
I then reverted back to the goldcard and tried doing the one click method and whenever i try to backup the recovery image, it says backup failed.
I hate 1.5 and hated 1.6 I have spent many many many hours trying to do this and just cannot figure this out. If anybody has any idea whats going on here any help would be appreciated.
Questions:
I see many people while rooted have the mytouch loading screen, mine is now vodafone? why?
any links or very specific instructions to get me as far as loading a rom again?
my phone info:
SAPPHIRE PVT 32B SHIP S-ON H
HBOOT-1.33.0009 (SAPP30000)
CPLD-10
RADIO- 3.22.20.17
I know its annoying for my newb self to ask questions without searching But i have been for HOURS, its been taking the majority of my last 4 days.
I would really appreciate any help.
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.
So my wife just upgraded her phone and i was left with a stock MyTouch 3g with 3.5mm headphone jack and I thought I would expand my Android knowledge base and see what I could do with it. I am not knew to Android and I have a Samsung Vibrant that I can pretty much do whatever I want with. The Galaxy line is extremely easy compared to this device.
So I did my fair share or reading and research and was able to root the phone with Universal Androot and installed busybox via titanium backup. I downloaded ROM manager from the market and flashed clockwork recovery. I used recovery to installl CM 5.0.8 DS and once it reboots in wont load past the mytouch splash.
This is what I started with:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013
CPLD-13
RADIO-2.22.23.02
Oct 21 2009, 22:33:27
And this is what it reads now:
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Jun 2 2009, 17:27:03
I read that Binary said that it is really a 32B not an A so to stick with the B ROMs. I can also access fastboot and recovery.
The easy part with the Vibrant is that if I screw up the phone you can just simply Odin back to stock and start over, but the mytouch is a little more complex than that. So basically I want to get back to stock and start over. There are so many threads and links that say user friendly but I didn't find it quite user friendly. I must just be spoiled with the Galaxy.
Any help would be greatly appreciated. It's not a rush or it's not my daily driver. Just a toy phone now to learn on.
Thanks!
mod edit because of inaccurate information.
So you are saying if I just follow the normal root guide for the fender 1.2 that I should be good?
Sent from my GT-I9000 using XDA App
CBATESY said:
usually any of the 3.5mm jack phones are 32a devices. 32b is the original mt3g. ones with the jack in the top is a mt3g 1.2 or 32a. If you have recovery working you can use that to restore back to factory or installed sapping.img
here something to help you out .
http://wiki.cyanogenmod.com/index.php?title=HTC_Magic
Click to expand...
Click to collapse
NO! Damn it! Listen to me everybody! The 1.2 device (Fender, etc) are a 32A/32B hybrid. The ONLY thing that makes this phone ANY different than the regular 23B MyTouch devices is the additional ram. That's it! You CANNOT fit a 32A ROM on the device because it lacks the internal storage. Even if you COULD the kernel for that rom would require a 32A radio. You cannot use a 32A radio because the 1.33.0013 32A s-ON spl requires the 32B radio. And it requires a 32B radio else it will brick. The 1.33.0013 is the S-ON stock SPL that the phone requires to use the memory map. If you try the Engineering SPL (1.33.2010 32B S-ON) the phone might boot, but you will not have touch screen or the use of the headphone jack because of the different drivers and memory map. When you flash the Engineering SPL it will read 32B because that is what is needed to flash the custom recovery and roms. However your device will not work properly because it's a 32A/32B hybrid. You need the 32A stock firmware (1.33.0013 S-ON) for the phone to operate. You also need the appropriate 32B radio and rom as well.
I have the phone and I've had it since it's release. I started off by making custom roms for it and ports before roms were using VoxLuna's driver patch. Trust me when I say that I know a little about this damn phone!
You know what... to hell with it. Do whatever you want. Don't be sending me private messages begging for help when you brick your device because you think it's a 32A.
custom ported rom #1
custom ported rom #2
custom ported rom #3
custom rom #1
They all require 1.33.0013 S-ON with 32B radio.
offdutyninja808 said:
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
Click to expand...
Click to collapse
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Binary100100 said:
NO! Damn it! Listen to me everybody! The 1.2 device (Fender, etc) are a 32A/32B hybrid. The ONLY thing that makes this phone ANY different than the regular 23B MyTouch devices is the additional ram. That's it! You CANNOT fit a 32A ROM on the device because it lacks the internal storage. Even if you COULD the kernel for that rom would require a 32A radio. You cannot use a 32A radio because the 1.33.0013 32A s-ON spl requires the 32B radio. And it requires a 32B radio else it will brick. The 1.33.0013 is the S-ON stock SPL that the phone requires to use the memory map. If you try the Engineering SPL (1.33.2010 32B S-ON) the phone might boot, but you will not have touch screen or the use of the headphone jack because of the different drivers and memory map. When you flash the Engineering SPL it will read 32B because that is what is needed to flash the custom recovery and roms. However your device will not work properly because it's a 32A/32B hybrid. You need the 32A stock firmware (1.33.0013 S-ON) for the phone to operate. You also need the appropriate 32B radio and rom as well.
I have the phone and I've had it since it's release. I started off by making custom roms for it and ports before roms were using VoxLuna's driver patch. Trust me when I say that I know a little about this damn phone!
You know what... to hell with it. Do whatever you want. Don't be sending me private messages begging for help when you brick your device because you think it's a 32A.
Click to expand...
Click to collapse
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Exactly, all he needs is a custom G recovery (which he should have) and then flash the 1.33.0013 stock spl BACK on. Afterwards, he can flash any 32B rom he wants and it should work as long as it's later than CM-4.2.15.
DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Thank you for the non-violent approach. I know how it is when you have a new guy just blowing his phone up and he goes screaming for help. Not what I was trying to do. Just tinkering with a new device to get some more know-how under the belt.
Much appreciated, Don!
I will let you know what I can get accomplished with your advice.
offdutyninja808 said:
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
Click to expand...
Click to collapse
He wasn't fussing at you, he was getting at the other guy for feeding you false information.
Sent from my HTC Magic using Tapatalk
My apologies, Binary. Following forums over time you tend to see so much hostility over pretty much nothing. It's a learning experience. Just as I had to learn my other phone, some things the hard way, I will be able to steer people in the right direction and help others after I get this one down.
offdutyninja808 said:
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
Click to expand...
Click to collapse
I'm not trying to be hostile but all of the information is available here in the forums. The developers, senior members and moderators like myself have spent HUNDREDS OF HOURS making sure it can be referenced one way or another. They are in stickies and even in MY SIGNATURE. The only other thing we can do for you is do it ourselves! Yet even with a clean and clear explaination this still comes up. We even get some people that post threads saying that they bricked their phones because they thought for sure it was a 32A and they try to hold me responsible. I will be happy to forward some hateful e-mails to you that I get at least 2 or 3 times a week average because people couldn't find the information... yet... if they followed rule #1 of the forums... they wouldn't have the problem.
Look... at least you got the right information and avoided bricking your phone. But I really hate repeating myself over and over again with the same information so I need to be tougher to get my point across otherwise other members will likely use the wrong information and end up breaking their phones... which I will not be held liable for!
DonJuan692006 said:
He wasn't fussing at you, he was getting at the other guy for feeding you false information.
Sent from my HTC Magic using Tapatalk
Click to expand...
Click to collapse
Right on Don. I'm not angry at you OffDutyNinja808 however the other guy (CBATESY) should be warned that I could give him an infraction for giving out bad information.
Binary100100 said:
Right on Don. I'm not angry at you OffDutyNinja808 however the other guy (CBATESY) should be warned that I could give him an infraction for giving out bad information.
Click to expand...
Click to collapse
On another note, Don, I made a new sticky thread just for this issue.
Feel free to add your wisdom to it.
http://forum.xda-developers.com/showthread.php?t=893004
Okay... so I followed Don's instructions and the phone now says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23. 02
I tried flashing the same CM and it gets past the mytouch splash but doesn't go past the next loading X screen.
From what you guys said everything is looking right. Any thing look out of ordinary or sound crazy from what i'm saying?
Thanks again!
Sent from my GT-I9000 using XDA App
offdutyninja808 said:
Okay... so I followed Don's instructions and the phone now says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23. 02
I tried flashing the same CM and it gets past the mytouch splash but doesn't go past the next loading X screen.
From what you guys said everything is looking right. Any thing look out of ordinary or sound crazy from what i'm saying?
Thanks again!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Loading X screen?
What rom are you trying to install?
What kernel?
And now i'm in like tube socks! I just woke up and tried it again and it booted right up.
Binary, it was the same CM 5.0.8-DS. As far as the kernel goes, I didn't flash any separate. The X boot screen I mentioned is the Nexus One load screen (I believe).
The only thing that I did differently this morning was wipe/factory reset, then davlik.
Okay... so from my understanding now:
I have to have a perfected SPL, not an engineering SPL.
I have to use the custom (AMAN RA) recovery and never use ClockworkMod.
Ensure that any other roms I want are 32b.
Now as far as the radio goes, is it best to stay with the radio it came with?
Again, thanks for the advice!
Sent from my GT-I9000 using XDA App
DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Don, two things...
1. I searched through the ROM bible and didn't find any place to download 6.1.
2. When I try to download the Google Apps from the page you sent me the link to yesterday, it asks for a user name and password. I have 5.0.8 up and running, but with no market and things like that.
Thanks!
Okay... I am now running FroyoRedux-1.9.5 with the Galaxy theme. Everything is smooth as butter.
I fixed the links in the post I pointed you to and updated them to what you news for CM 6.1
Sent from my HTC Magic using Tapatalk
offdutyninja808 said:
And now i'm in like tube socks! I just woke up and tried it again and it booted right up.
Binary, it was the same CM 5.0.8-DS. As far as the kernel goes, I didn't flash any separate. The X boot screen I mentioned is the Nexus One load screen (I believe).
The only thing that I did differently this morning was wipe/factory reset, then davlik.
Okay... so from my understanding now:
I have to use the custom (AMAN RA) recovery and never use ClockworkMod.
Now as far as the radio goes, is it best to stay with the radio it came with?
Again, thanks for the advice!
Click to expand...
Click to collapse
You can use clockwork. I use it without any problems. Some people like AmonRa better though. If you run CM6 there have been issues about people not being able to flash the recovery for some reason. Just keep trying and it will stick eventually. Just make sure that you flash the one for MyTouch/Ion devices.
Radio - keep the one that your using.
Roms - 32B ONLY
Hey xda crew,
I am pretty sure my Desire Z is up sh*t creek now without a hope. As such I am here with my begging on... Help please!!
Last night I went through the app library and manually updated about 7 apps simultaneously. At some point the phone hung, and wouldn't respond. I pulled the battery and booted it back up, and it simply hung again as soon as it connected to wifi. It ran fine without a data connection however.
So this went on and on. I booted, connected to wifi and tried to kill each download asap before it hung again (can't access the market to kill the d/l w/o connection!). Inevitably it would hang each time and then i'd repeat. Finally though it simply got stuck on the HTC boot screen and never went any further.
I've tried everything googleable so far, but unfortunately no love. Here are my specs:
Desire Z, stock standard, no modding, ever.
Vision pvt ship S-ON
HBOOT-0.85.0013
Microp-0425
Radio-26.10.04.03_M
eMMC-boot
Apr 11 2011
I have tried the following to recover the phone:
Leave it loading on HTC screen (30+ mins): Never loads
Factory reset in HBOOT: Hangs
Recovery in HBOOT: Goes to HTC screen, then the green recovery icon, and then blacks out. As soon as the screen goes black it vibrates fiercely 7 times in anger and then dies.
Fastboot w/ RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe: RUU sees phone but cannot reboot into bootloader, times out.
Flash manually using PC10IMG.zip, (rom.zip) from the RUU above: Initially didn't work due to CID invalid warning in HBOOT, however have made a gold card manually on PC and gotten past that warning. The ROM reads and verifies fully in HBOOT but upon verification just goes back to HBOOT screen without the option to flash.
With the intent to wipe everything: Flash the HBOOT with an engineering version from here: virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html: As per the RUU Rom, HBOOT reads and verifies successfully but never gives the option to flash.
Erase cache from fastboot command line: Hangs
Beyond that I don't know what else to try. I can't use adb as I cannot boot and don't have any custom recovery roms installed that will allow it. Likewise I can't flash with fastboot due to S-ON.
So because warranty ended a month ago, it goes in the bin tomorrow unless someone has an alternative Even if it is a highly dangerous method, I don't really care, it's good as dead anyway...
Interestingly enough it seems there are a few people with the same issue, all posted within about a week of each other. Everyone was doing the same thing... updating a bunch of apps!
Thanks in advance
When I rooted mine, I simply followed the instructions provided over at CyanogenMod ( http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread) ) doing the firmware downgrade and then the rooting exploit, from there I actually upgraded the radio (thread in my signature) and then got the EliteMod rom.
PS: My Bootloader screen is basically:
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
Aug 20 2010,16:51:01
Just not entirely sure how you're going to go bout the fr3vo method without least a stock rom to exploit into.
well jtag... not what you wanted to hear I'm sure
not trying to add insult to injury but next phone make sure you root it right away, chances are this all could have been fixed with the right permissions, short of a hardware failure of course
Sent from my HTC Vision using xda premium
Thanks for taking the time to help out mate.
As it stands, there is no way to use adb so I can't downgrade as per the directions in the link.
I have since tried several other newer and older roms as well, still the same thing, it unpacks them and verifies and then does nothing.
Quite sure now it is dead, so I have just bought a new one off ebay.
Poor old thing, I did enjoy that phone!
demkantor said:
well jtag... not what you wanted to hear I'm sure
not trying to add insult to injury but next phone make sure you root it right away, chances are this all could have been fixed with the right permissions, short of a hardware failure of course
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you are absolutely right... I was thinking the same thing. Thew new one will be rooted the minute it arrives. The good news i suppose is that desire z's are so cheap now that they are discontinued.
I honestly love the functionality, speed etc.. no need to upgrade whatsoever.
Your bootloader is stock and you are S-On why not just use your warranty ?