Disclaimer: As in every case your choice to flash any memory on your phone is YOUR decision and you run the risk of making a expensive Paperweight. Research Flashing and read post about new Rom's or Builds to learn from others mistakes.. There are a lot of risk takers here on XDA that will be glad to bite the bullet to help the community with rom stability and issues. But ultimately you CHOOSE to flash your phone Not us.
I created this thread for new users unfamiliar with Flashing and modding their phone to get technical Support for any technical Issue that comes up regarding the phone. However Please Avoid Posting things such as "I am bricked how do I fix" or "Help my phone doesn't Start up" Because they will not allow the more experienced users to Help you.
Suggestions:
1. List the following in the reply
- What Model Is your Phone (Should Be HTC Dream AKA Tmobile G1)
- What SPL are you using (Boot Holding Power + Camera then first line)
- What Recovery Image are you using(Stock, Jesus Freakes 1.42, 1.43 or HK)
- What Rom is Currently Loaded (Booted up go to Settings-> About Phone)
- What Radio do you have currently (Settings -> About Phone)
2. What are you Trying to do (Ultimate Goal)
3. What steps has you taken (In Detail please)
4. Once you problem has been resolved please Edit your Original Post indicating that it was resolved.
Thanks In advance for Keeping this thread Neat.
Some Reading Material for you:
APN Info Thread
General Questions Thread
G1 Wiki Thread
G1 Tips and Tricks Thread
jf recovery 1.43
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.
build..?
I did my first fastboot recovery, even though I didn't need to. Pretty decent operation. Just wanted to get the feel of it. I think I'll be using nandroid and fastboot a whole lot in the near future
Goal: To either build myself, or at least play a part in the building of one sweetest ROM's. I guess i'll start small, with a theme.
(it's been a 12 pack of Mountain Dew and B movies kinda night.)
CC CEO said:
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.
Click to expand...
Click to collapse
Installing JF Recovery 1.43 is just like any flash update for a rom...
You find and download the recovery file. Rename it to update.zip (Keep in mind that windows by default hides the.zip part so if you rename it to update.zip windows actually sees it as update.zip.zip.. This is a common problem.
Then Boot to SPL by powering off your phone and powering up with Home + Power Key.
Once loaded then hit Alt + L (If you don't have a modded Recovery already) and then If you have to wipe(which I usually do) Alt-W then you need to load the new firmware with Alt + S.
If all goes well it will load the new recover image and will reboot back into Recovery mode in which you just Home + Back to Exit and reboot.
I don't wanna step on anyones toes but I believe to load the new image after wipe it'll be alt + s....
Hero beta's
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?
mvanwyk83 said:
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?
Click to expand...
Click to collapse
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.
Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem.
tia
Curunir said:
Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem. Tia
Click to expand...
Click to collapse
Before you consider flashing the new spl. Make sure you have a pvt revision board. Power + camera when turning on your phone. It will be at the top. If it says dvt don't flash.
You also need the 26I radio firmware.
If you do not have a memory card reader or a second memory card ten do not flash the new spl. Once you flash the spl, your phone will not boot until you flash a new Rom onto it
I believe this is correct. Anyone with experience care to confirm?
Actually now that I am rested and thinking straight.. Don't you load a recovery image by loading the recovery.img file on your sd card and booting to Bootloader?
Man I was sick and tired last night =)
Go to My Hero Thread and in the first post is the JF 1.43 Zip file you can use to Flash to JF 1.43 in update.zip format.
ubernicholi said:
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.
Click to expand...
Click to collapse
Now is that process the same for Beta 4??
,
mvanwyk83 said:
Now is that process the same for Beta 4??
Click to expand...
Click to collapse
Should be. Can anyone confirm?
I put some music on beta 4. The album cover is in my pics but doesnt show where it should when playing music, do i need to somehow manually put it there?
Am I asking this in the right place even? thanks
1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)
cronin4392 said:
1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)
Click to expand...
Click to collapse
What errors did you get or what problems are you having?
stuck on android screen
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated
rschuman90 said:
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated
Click to expand...
Click to collapse
Wipe your phone. Press and hold home+power. Continue to hold it till youe see a caution triangle. Press alt+l and then alt+w when its done select reboot from the top of the list. Good luck
Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.
Mast3rmatt said:
Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.
Click to expand...
Click to collapse
From what I know, its a bad idea to downgrade your spl. Check you screen brightness and your screen time out if you are running an overclock program, try setting it to 384 max 128 min. Double check to make sure your screen actually times out. See if your wifi is running, as well as your gps. If you use twidroid change the rate from 5 minutes to 1 hour
i have to wipe my entire phone and loose everything now!!?
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 have a black G1 with a 32b board,I found a rom online that was for the rogers dream,I didn't think it would flash the recovery image too,so I flashed it thinking if it didn't work I would be able to just flash to a different rom. That didn't work. it boots up as a rogers dream,and is fully working,but I can't flash back to anything else because it's a stock recovery image,and even though I had the engineering spl,it messed that up too,it still shows the skateboarding androids,but with a cyan stripe at the top of the screen and it won't even flash the htc images for the dev phone,or the normal rc29 DREAIMG.nbh. anyone have any ideas? fastboot tells me remote not allow,bootloader to the DREAIMG.nbh says either main version old,or model id mismatch,most of the time it's the main version thing though,and the recovery thing tells me no signature found if I try to flash the htc images and verification failed if I try to flash anything else that i've tried. anyone have any ideas? it was the 911 mandatory update from rogers that was supposed to also add sense if that helps anyone any.
1) THERE IS NO SUCH THING AS A 32A DREAM!!!!
32A means SOME HTC MAGIC, and ALL HTC HERO.
ALL DREAM 100% WORLDWIDE are 32B
*** NO EXCEPTIONS.
2) You need to provide more information: WHAT did you flash to the device.... SPECIFICALLY. And HOW DOES EVERYTHING IDENTIFY ITSELF, i.e. SPL, BASEBAND, KERNEL, etc., does the "su" command work?
3) I have ZERO expectations for you. Anyone with a screen name of "msnuser" is not worthy of android.
it's the rom from comment 102 on this page:androidforums.com/rogers/38624-rogers-update-911-fix-rogers-htc-dream-magic-ready-3.html the rom says on the recovery screen dream PVT-32A and it used to be PVT-32B. Not sure how it worked or how it booted,but the phone says it has 87mb free on the internal storage and it runs a lot quicker than it did on any rom I've ever used before,I just miss my rooted apps. I traded phones with my brother because he never uses rooted apps anyway,he was running stock tmobile firmware and was glad to have a faster os.
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
greeklegend said:
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
Click to expand...
Click to collapse
unfortunately wont work... it wont allow you to flash an older spl...probably will have to wait till an official 2.1 update comes out and hope that it might be rootable..
And THAT will teach me to look before I leap! I guess I can live with this update because its actually a HUGE improvement over what I was using before (radio reception is much better, text correction in the browser,sense is win in general and its much snappier) and I can still do usb tethering. But still, WHY DID YOU DO THIS TO US HTC!!!
EDIT:
I tried taking the rom image from the RUU and using fastboot to boot the boot.img from that but not even that works! I was thinking to do something like init=/system/bin/sh... I don't suppose theres another way to supply cmdline parameters to the kernel?
Does your new MyTouch have a 3.5 mm headphone jack?
Are you confused on wether it's a 32A or a 32B?
Do you need to know how to root it?
Do you need to know how to flash a custom recovery and which one?
Do you have the right radio?
Are you afraid that you might brick your phone?
THEN THIS IS THE THREAD FOR YOU!!!
HURRY!!! HURRY!!! HURRY!!!
For a limited time only! Get your questions answered without having to post a new thread!*
Good while supplies last!
*XDA-Developers and it's members are not held responsible for any damages and encourages all readers (members and non-members) to read thoroughly before attempting any modification of any device. Proceed with caution and at your own risk.
More information
crypysmoker said:
Universal Androot confirmed working. This method is no longer needed and is to dangourous for some people so please use universal androot 1.5.3+
IF READ CORRECTLY YOU WILL NOT BRICK. BUT, Since a few of you dont have that ability, I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR PHONE. There are no pros to rooting this phone yet, leave it alone if you dont know what your doing PLEASE. I beg you. You are in essence almost bricking your phone in order to root it in the first place. These arent fun and games, It is dangerous to rush this stuff
Listen.. Im more then happy to help people. BUt I fully understand why so many devs have left this place. Some of you are so utterly ridiculous with your questions, wanting someone to hold your hand. I cant sit on gtalk for hours helping you go through what should take 10 min , I have a life and kids and other things to do. I did this because I was bored and wanted to see if I could. There is not point in rooting it yet, there are no roms, nor will there be for at least a month. Please, if you cant even understand simple questions, have never rooted or even used an android phone before, please.. do not bother me. This place is insane with stupidity. I will change the tutorial in a little more detail later, but fo rnow, DO NOT DO THIS IF YOU DONT KNOW WHAT YORU DOING. IF YOUR BREAK YOUR CRAP< I DONT CARE, BECAUSE IT WASNT MY FAULT.
I am in no way an angry or mean person, but you people have given me a migraine. I see why all the rom devs hide from here so much
THERE IS NO POINT IN ROOTING THIS PHONE YET PEOPLE, SO STOP.. OMG PLEASE STOP LOL
IT HAS BEEN DONE!!! lol
After 3 days, sleepless night and 5 min from returning the phone, Together with the Awesome Cursordroid We have achieved full root of the fender mytouch/ Mytouch 1.2 revision.
Now.. Understand.. not many will have the fender Mytouch.. but this is the hardware they WILL be using in the fully confirmed Mytouch 1.2
If you do not follow my instructions fully, NOTHING WILL WORK.
Start by making a working gold card, pay VERY CLOSE attention to what the instructions for making a gold card say
http://theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/
READ READ READ. DO NOT download the SAPPimg.zip file it says on that page.
Get the top fixed SPL file 2010 from here
http://forum.xda-developers.com/showpost.php?p=4332591&postcount=1
Once you have you working goldcard (remember, apply to PHYSICAL not LOGICAL) rename the fixed SPL/rom you just downloaded to SAPPIMG.img
Put that file on your gold card
Hold volume down while hitting power
You will boot into Hboot, and if goldcard was made correcly and file is in root, it will begin to read. MAke sure battery is full or chargeing. follow on screen directions for flashing. Reboot into Hboot.
You are now screwed with a downgraded SPL and radio that do not work on this phone YAAAAAAY.
Now grab the stock radio and SPL from Cursordroid here http://forum.xda-developers.com/showthread.php?p=5451898&posted=1#post5451898
From there on follow hiw directions for reupdating your radio and spl, plus give yourself a new recovery making ROOT.
Im not good at tutorials or typing on a tiny netbook keyboard so please forgive. Anyquestions please ask and I will go into more detail
In order
Goldcard
Amen ras fixed spl rom renamed SAPPIMG.img
Boot into Hboot volume down/power
let rom install saying yes to what it says. If it works..
Now boot into your recovery through fastboot
Flash phone with stock fender rom
reboot into fastboot
back out of update when it asks and flash STOCK radio and SPL back, now reboot
your splash screen for fender IS GONE, get over it. You can make a new one later if you realllly need to.
Click to expand...
Click to collapse
Yet, even more information.
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Fender/1.2
Installing CyanogenMod on the 32A (myTouch 3G 1.2 / Fender LE (3.5mm jack) version) requires an additional step whereby a "gold card" is created as part of the installation process.
The process of upgrading from a stock ROM is fairly simple, following the instructions below.
Click to expand...
Click to collapse
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced your phone with your Google account, your contacts, calendar, Gmail, and some Google data will not be lost and will come back after the next sync; However, you should backup anything you want to keep that is not stored on your SD card.
SMS/MMS messages
Call Log
Bookmarks
Applications; use Titanium Backup or the Astro file manager, for example
Any application data not on the SD card
It would also be a good idea to back up everything stored on your SD card in the rare case the card must be formatted to resolve any major problems.
Click to expand...
Click to collapse
Before you begin
What You'll Need:
1.Your myTouch 3G 1.2 or Fender LE.
2.Mini USB cable.
3.microSD to SD adapter for your computer.
Prep
1.Get the latest Amon_Ra recovery
Make sure you chose the G version
2.Create a "Gold Card". It is recommended (but not necessary) to use a spare microSD card.
3.Back up all your microSD card contents to your computer.
Creating the Gold Card
Create a Goldcard
Click to expand...
Click to collapse
Rooting
Downgrading
1.Download the sapping.zip file from here: Link Mirror 2.Place the zip file on your newly created Gold Card. If it isn't already, shut the phone off and place the microSD card back into the phone.
3.Then turn the phone back on by holding down Volume Down and Power. It should boot into bootloader mode and automatically find the sappimg file and ask you to push the trackball (action) to begin the update. Push the trackball and let it update.
4.Once it finishes flashing, it should ask you to reboot. Reboot and let it load to the new "htc Magic" boot screen.
5.Chances are at this point that the phone will not successfully boot. THIS IS NORMAL. Simply remove and re-insert the battery, as we're not done yet!
6.Download the following zip file (the stock myTouch SPL and Radio) and extract it: [1]
7.Copy the two files inside the zip to the root of your SD Card
8.Take the latest Amon_RA recovery you downloaded earlier and copy it to the root of your SD Card.
9.Download terminal emulator from the market and run the following commands:
flash_image flash radio /sdcard/radio.img
flash_image flash hboot /sdcard/hboot_7201A_1.33.0013G_091021.nb0
flash_image flash recovery /sdcard/recovery-RA-sapphire-v1.7.0G-cyan.img
WARNING: Do NOT upgrade the SPL (hboot) with anything other than the 1.33.0013G version! Otherwise, You will lose audio to your earpeice.
1.Press MENU to power down the phone.
2.Reboot holding down the Power and Home buttons until the recovery menu appears.
Click to expand...
Click to collapse
Easiest method!
Easiest method!
candymanmike said:
This is a guide on how to root your phone and install a custom ROM using Universal AndRoot. It supports several phone models and is the simplest way to root a phone I have ever seen. It features a 1 click root and a 1 click unroot option. Rooting with this method does NOT affect your bootloader, therefore if your phone needs serviced you can (theoretically, I have not verified this to be true) simply unroot and restore to normal.
As always myself, XDA, ROM developers, your friends, your mom, the rulers of the world and the developers of this app are NOT responsible for any bricks YOU create by taking the risk of rooting your phone. Also there are no guarantees that your warranty will not be null and void. If you NEED your warranty, DO NOT root your phone. Use at your own risk!
First we will gather the items needed to complete this process.
Universal AndRoot Version 1.6.1 is the newest STABLE release. The newest version is 1.6.2 beta 5, which is where the updated list above comes from and is said to be very close to the final release version.
Next go to the Android Market and install AppInstaller (there are a few versions including appsInstaller by modmymobile, all are free)
While in the market, also grab ROM Manager (also free)
Next download the ROM you would like to use. I personally recommend CyanogenMod 6.0.0 DS - stable. This link will take you to the Cyanogen downloads section where you will have to select your phone and search for the ROM you want.
While you are there, also grab the Google Addon pack for your phone.
Of course it is up to you to choose a ROM you like. You can also keep your stock ROM if you choose.
Lets Begin!
Install the Universal AndRoot .apk file, the ROM you chose and the Google Addon to the root of your microSD card
Open AppInstaller and let it locate your AndRoot .apk on your microSD. Select it and install it to your phone.
Open Universal AndRoot from you app menu. It should read your phone and show your firmware version. Click the "Root" button and let it do it's thing. It really only takes a minute or 2. When finished it will let you know. Congratulations, at this point you are now rooted.
Now for a custom ROM!
Open ROM Manager. Install Recovery. The default recovery for ROM Manager is ClockworkMod Recovery (which is what I am using) but a lot of people seem to like RA Recovery. This option is at the bottom of ROM Manager under "Flash Alternate Recovery". Whichever you choose, let the Recovery flash.
Next choose "Backup Current ROM", then "Reboot Into Recovery" (for future reference, you can also get into recovery mode by turning your phone off, then hold down the "home" button hit the power button. continue hold home as it powers on.)
Chose "wipe data/factory reset" then "wipe cache partition". This step is important. I know from personal experience if you don't do this you may end up in a bootscreen loop!
Choose "install zip from sdcard". Navigate to the ROM you loaded on your microSD and flash it.
After the phone reboots (which can take a few minutes the first time after flashing a new firmware version) go back to ROM Manager and again choose "Reboot Into Recovery". Once in recovery, again choose "install zip from sdcard". Navigate to the Google Addon pack on your microSD and install it.
Once you are rooted and running your new ROM, go into ROM Manager and partition your sd card. This is optional.
That is it. You should be good to go! Way easier and faster than the old goldcard method!
This is my first XDA guide. I hope it is up to your standards!
Click to expand...
Click to collapse
Will all 32a/nr roms work on the 1.2?
Sent from my HTC Magic using XDA App
soub31 said:
Will all 32a/nr roms work on the 1.2?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
NO! 32A roms WILL NOT WORK!!!!
As Amon Ra put it:
"The following instructions :
will void all warranties of your phone!
will erase all your userdata!
will change your current ROM/SPL!
will change your current splash screen!
could brick your phone!
Proceed at your own risk!"
So I've taken the guide that I used to root my myTouch 1.2 with T-Mobile, updated some of the information, and added some explanations. All thanks is owed to The Unlockr for the guide, I'm merely going to attempt to explain what your actually doing in the process and just try make the whole ordeal easier. If I would have known what i was actually doing, it would have taken me 45 minutes to root my phone, vice the good 7-8 hours I put into it. I am by no means an expert on rooting, so feel free to critique what I put in here, and I'll make adjustments as needed.
What's unique about the myTouch 1.2 and the Fender edition is that both phone's have a "perfected" SPL, that does not allow for fastboot access via USB. This means that you can't push any command prompt commands to the phone from your computer, which is what you have to do to get the phone rooted. With these instructions, you'll flash a "non-perfected" SPL onto your phone, load up a custom recovery (which is how you will load up ROM's and do a few other things in the future), and then reflash the phones original "perfected" SPL. Without the original SPL, your phone will not function correctly.
I would suggest opening all the links before continuing so you won't have to wait for the downloads to start as your going. Make sure you remember which link is which tab!!!
From The Unlockr:
I. Setup ABD/Create a Goldcard
Follow this procedure completely to create a working goldcard, then return to this procedure and continue:
How to Create a Goldcard
Follow these instructions without fail. If anything get's messed up here then you won't be able to flash a new SPL and you'll have to attempt to remake the Goldcard again. If you attempt to load the sappimg without using the Goldcard or without a properly done Goldcard, you will get either "Incorrect model ID" or "Main Version is Older". The Goldcard basically tricks the phone into not checking these two parameters, which is what let's you get the "unperfected" SPL on to your phone. ADB is the program that allows you to have a command prompt interface from your computer to your phone.
Note for Windows Vista and Windows 7 users: When your setting up your phones drivers during the ADB setup process, be sure to allow Windows Update to check for drivers. It will allow your computer to automatically install the drivers vice having to manually install them yourself. The option to turn it on should come up when Windows gives the notification that it was unable to install drivers for your device
II. Flash the Sappimg file
1. Download the Sappimg File and save it to your newly created goldcard (NOT in any folders, just on the Goldcard itself).
sappimg.zip
2. Once the sappimg.zip file is on your goldcard, turn off the phone and put your Goldcard SD into your phone. Then turn it back on by holding down Volume Down and Power. It should boot into bootloader mode and automatically find the sappimg file and ask you to push the trackball to begin the update. Push the trackball and let it update.
*If it tells you Error – Wrong Model ID or anything similar, the goldcard was not created correctly, go back to that procedure and try again.
Here your loading an Engineering SPL, so that we'll be able to get access to the phone via Fastboot USB and load up your new recovery. Be patient once you turn your phone back on, as it will unzip the file, then check the contents. If you get an error, you've got a problem with your Goldcard and need to redo it.
3. Once it finishes flashing press the "Send" button to reboot and you will notice your touchscreen does not work (don’t panic). Turn off the phone, then turn it back on by holding down Back and Power (to get into fastboot mode).
4. Download these two files and save them into C:\AndroidSDK\Tools folder you setup during the ADB setup procedure:
Stock MyTouch SPL
and Radio
5. Then download the Custom Recovery Image and save it to the C:\AndroidSDK\Tools folder you setup during the ADB setup procedure as well:
Amon Ra’s Recovery
6. Now that you have the recovery, spl and radio all saved in the tools folder of the Android SDK (same folder as the adb program), plug in your phone (while in fastboot mode from step 3).
7. Open the command prompt on your computer and type the following with hitting enter at the end of each line:
cd\
cd AndroidSDK\tools
fastboot devices
A serial number should come up, indicating that your computer can see the phone in fastboot mode. If so continue by typing in the following with hitting enter at the end of each line:
fastboot flash radio radio.img
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
8. Once the phone starts to turn back on begin holding home and power (do not let go until you see the recovery mode) to boot into recovery mode.
This could take a while. I believe the first time I tried to get in I had to hold them down for ~1 minute before getting in. You should see the HTC Magic splash screen pop up first. There is a guide to changing out the splash screen (which is just a picture) within these forums but I'll leave it to you guys to search for it.
9. You should end up in Amon Ra’s recovery mode.
10. At this point, you want to plug your ORIGINAL SD card into your computer and copy the "DCIM" and "Music" folders (if you have them) over to your computer to backup your pictures/video/music. Then take the Goldcard out of your phone and put your ORIGINAL SD back in.
11. With your phone connected via USB to your computer and in Amon Ra's Recovery, highlight USB MS and press the trackball. This should mount your SD card to your computer so that you can move files to it.
12. Download these three .zip files:
Cyanogen 6.1
Google Apps
614 MHz OC/UV Kernel
You need the OC kernel because there's a known issue with CM 6.1 having a green tint without flashing a new kernel.
13. Copy those three files over to your phone's SD within Windows, "Safely remove hardware" in Windows, then disable USB MS by pressing the Home button. Back out to the main screen.
14. In the recovery select "Wipe" and you want to wipe "data/factory reset" then "Davik-cache".
15. Back out to the main menu and select "Flash zip from sdcard". First you want to select " update-cm-6.1.0-DS-signed.zip" and hit Home to confirm. Once complete, select "Flash zip from sdcard" and this time select "gapps-mdpi-tiny-20101020-signed.zip" and hit Home to confirm. Once complete, one again select "Flash zip from sdcard" and this time select "oc614-cm-2.6.34.1-6.0.0rc2-signed.zip" and hit Home to confirm.
16. Back at the main screen select "Reboot system now". This will load your phone back up as normal and you should now have a working rooted phone with the Cyanogen 6.1 ROM! Jump in there and check it out.
If you want to try out a different ROM, check this thread out. Go to the section called "MT3G 1.2 / LE Fender".
Credit to DonJuan692006 for this.
Thanks to Amon Ra for his recovery images!
Thanks to Unlockr for the original How To!
Thanks to the Cyanogen team for an awesome ROM!
LINK Resources:
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
http://forum.xda-developers.com/showthread.php?t=530492
http://forum.xda-developers.com/showthread.php?t=529019
wouldn't it better to recommend to use Pershoots OC/UV/XTRA kernel? It does OC to 614, is more current than Dumfuq 2.6.34.1 kernel.... honestly been pretty stable.
the previous builds of 2.6.35.9 and lower did not have the 3.5mm audio support.. but it was re-added in the 2.6.35.10. It also resolved the green tint issue of CM6.1-DS
NetrixTardis said:
wouldn't it better to recommend to use Pershoots OC/UV/XTRA kernel? It does OC to 614, is more current than Dumfuq 2.6.34.1 kernel.... honestly been pretty stable.
the previous builds of 2.6.35.9 and lower did not have the 3.5mm audio support.. but it was re-added in the 2.6.35.10. It also resolved the green tint issue of CM6.1-DS
Click to expand...
Click to collapse
Yeah I use pershoots myself from the rom manager.
Another OP made the thread actually and sent me the HTML via e-mail.
614 isn't stable for me though.
My Thoughts and Things to Know
READ ME BEFORE DOING ANYTHING TO YOUR PHONE OR STARTING A NEW THREAD!!!!!
The myTouch 1.2/Fender is a rather unique device. If you boot into fastboot you will notice that the following information is displayed:
Code:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
Let's break that down a little bit.
You see in the first line 32A...but this is very misleading. The myTouch 1.2 is actually a 32B device, just with 32A memory and controller, but it IS a 32B device for pretty much all intents and purposes.
Secondly, you'll notice S-ON. This means that remote security from the bootloader is enable. What does that mean for the user??? Simple, you'll never be able to run a remote fastboot command.
Second line, 1.33.0013. This is your SPL and the ONLY SPL that will allow the phone to function properly. This, as well as the radio, will always need to be the stock versions or you'll either brick your phone or never get a ROM to work.
Also to note, this is considered a perfected SPL. What does "perfected" mean? Remember the "S-ON"?? That is what makes it perfected.
Lastly, the radio, 2.22.23.02. There is actually now a newer radio, 2.22.28.25 available, however, I personally have noted no real performance gain/loss. Again, along with the SPL, you will never want to change this unless you absolutely know what your doing or an expert tells you to.
Now, on to the good stuff.
How do I root my phone???
The first few posts of this thread are the various methods to go about rooting the myTouch 1.2/Fender. The easiest and least dangerous method would be to use one of the one-click root programs such as Universal Androot or SuperOneClick. These methods will give your phone permanent root permissions (permanent until you do a factory reset or receive certain OTA updates later on down the road). The big deal here is that with root permissions you are able to download a nice little application from the Market called ROM Manager that allows you to flash a custom recovery onto your phone. The custom recovery is the bread and butter of modifying your phone. It allows you to flash custom ROM's, flash new kernel's for overclocking, etc.
What radio should I use?/What's the best SPL?
Simply put, don't mess with your radio or your SPL ever except for under very specific circumstances. Those circumstances being, your rooting your phone using the goldcard method or you need an engineering SPL to be able to run a command from fastboot. Even in either of those cases, this should be done very carefully and you will always need to revert back to the original SPL/radio. If you ever need to run something from fastboot and are thinking about flashing an
engineering SPL to do so, make sure you ask an expert first before proceeding. The number one reason for people bricking their phone is because they have taken it upon themselves to try flashing random file they've found via Google.
What ROM's can I use?
This is an easy one. Pretty much any ROM made for 32B phones that does not require a specific radio. I haven't personally tried this out, but I've had reports from a few people that just about every ROM for the G1 not requiring a specific radio works for the 1.2/Fender. Worse case scenario if you flash a ROM that isn't going to work, you'll get stuck in a boot loop and will just need to flash a new ROM or restore a backup.
What is a backup?
A backup essentially saves the state of your phone. For those computer savvy, it's like creating an image of a hard drive. The easiest way to create a backup is via a custom recovery. Both ClockworkMod and Amon Ra's recovery's include backup applications (e.g. Nandroid, Bart, ClockworkMod). Immediately after achieving root, getting your custom recovery installed, and verifying that your ROM boots properly, you should create a backup. This way, if your phone ever starts going down the tube or you manage to hose something up with your ROM, you can simply restore your backup and be back up and running. This will not fix a truely bricked device however, so don't get your hopes up.
Is my phone bricked?
The basic definition of a bricked devices is one that will not boot into a ROM, will not enter the bootloader, and will not enter recovery. If you still are able to boot into any of the three mentioned, your not bricked and there's a chance to save your device. The problem is that when most people get close to this state (they can only get into fastboot for example) they'll go into a panic and start trying any and everything to get their phone back up and running. This is NOT the thing to do. If you ever are stuck in a similar situation, please come ask for help and don't do anything else with guidance.
How do I get into the bootloader/recovery?
All of these steps are to be completed with the phone powered off.
For fastboot - hold back+power until your loaded into a white screen with the Android dude skateboarding.
For hboot - hold Volume Down+power until your loaded into a white screen with the Android dude skateboarding.
For recovery - hold the home button+power until your loaded into your recovery. For the stock recovery it'll be a triangle with an exclamation mark in it and an error pointing to a box. Hitting the home button again will get you the rest of the way into the stock recovery. If you have a custom recovery you will be loaded into a basic menu.
It's essential to familiarize yourself with these menu's. Before you do anything to start rooting, you should boot into fastboot and right down the information there and keep it somewhere. If your run into problems later on and you can still get into fastboot, make sure you get in there and right down what it's showing then. Make sure you include whatever your fastboot information is whenever your posting about a problem in the forums.
That's all I can think of for now. So good luck!
kernels and spls
Could anyone help with two (or four) nagging questions I've been trying to find answers to?
1.a. what is the difference between droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b-oc-uv-xtra-ram-fp-120810.zip
and
droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-120810.zip
?
1.b. I have successfully flashed the first one on my device to fix the green hue issue on CM6.1. Is there any benefit to flashing the second?
2.a. I would like to change my splash1, but can't use fastboot because I don't have the Engineering SPL. Is there any easy way to change the splash1 without having to do the 3-step process of a) flash to Engineering, b) update the splash screen, and c) flash back to stock SPL?
2.b. OK this may be a long shot, but as a programmer, I'm kind of curious: if the answer to 2.a. is "no", then, is the "splash1" image saved in any recovery files anywhere when you do a backup (e.g. if I go into ClockWordMod ROM Manager and choose "Backup Current ROM", does the backup include the splash1 data?), and, if so, would it be feasible to search the recovery image for the splash1 data (e.g. with a program that looks for a binary string matching the raw data of the current splash screen)-- of course, the data would have to be raw and unencrypted and uncompressed-- replace it with the new splash1 data, and then do a restore from the resulting modified recovery file, in order to change the splash screen?
-------
Androot + ClockworkMod ROM Manager + CM6.1
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009, 22:33:27
mattewong said:
Could anyone help with two (or four) nagging questions I've been trying to find answers to?
1.a. what is the difference between droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b-oc-uv-xtra-ram-fp-120810.zip
and
droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-120810.zip
?
1.b. I have successfully flashed the first one on my device to fix the green hue issue on CM6.1. Is there any benefit to flashing the second?
2.a. I would like to change my splash1, but can't use fastboot because I don't have the Engineering SPL. Is there any easy way to change the splash1 without having to do the 3-step process of a) flash to Engineering, b) update the splash screen, and c) flash back to stock SPL?
2.b. OK this may be a long shot, but as a programmer, I'm kind of curious: if the answer to 2.a. is "no", then, is the "splash1" image saved in any recovery files anywhere when you do a backup (e.g. if I go into ClockWordMod ROM Manager and choose "Backup Current ROM", does the backup include the splash1 data?), and, if so, would it be feasible to search the recovery image for the splash1 data (e.g. with a program that looks for a binary string matching the raw data of the current splash screen)-- of course, the data would have to be raw and unencrypted and uncompressed-- replace it with the new splash1 data, and then do a restore from the resulting modified recovery file, in order to change the splash screen?
-------
Androot + ClockworkMod ROM Manager + CM6.1
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009, 22:33:27
Click to expand...
Click to collapse
droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-120810.zip is for the 2708 radio which you DON'T have so don't flash it.
No. Flash the Engineering SPL, flash the splash screen, flash the stock spl back. Only way.
No. Splash files are not saved or effected by nandroid. So you can flash the splash screen and restore a nandroid backup (or clockwork backup, whatever) and you'll still have your splash screen.
ok, thank you
can we install the new radio or spl on our phones?
soub31 said:
can we install the new radio or spl on our phones?
Click to expand...
Click to collapse
I've heard that we could but I wouldn't recommend it because it really doesn't benefit.
Binary100100 said:
I've heard that we could but I wouldn't recommend it because it really doesn't benefit.
Click to expand...
Click to collapse
also one last thing i guess we use 32b roms on our phones what about roms the use 2708?
could we just flash an appropriate kernel afterwards?
soub31 said:
also one last thing i guess we use 32b roms on our phones what about roms the use 2708?
could we just flash an appropriate kernel afterwards?
Click to expand...
Click to collapse
If you're referring to CM 6.1.0 and the like, yes.
Binary100100 said:
If you're referring to CM 6.1.0 and the like, yes.
Click to expand...
Click to collapse
not just cm6 roms like yoshi and enomothers when ever i flash them and then the right kernel i just get stuck at the splash screen
I've flashed Yoshi and it did not work at all. It boots to the spalsh1 then to the Android but bootloops from there. So no on Yosi. As for Enomothers, I have successfully flashed this rom and and enjoyed it. However, read all the information before flashing. He has certain requirements that are not compatible with our phones.
Which version of Yoshi are you guys trying?