Trying to flash 2.2 to G1.. Troubles! - G1 General

Maybe I'm more of a noob than I thought.
I bought a vanilla G1 on 1.5 locked to T-Mobile.
Unlocked it so I could use it on 3, no troubles there.
What I want to do is get 2.2 Froyo running, with ElegantSteel theme. Obviously the latter is more of a want, and I'm more concerned with just getting a working 2.2 on my device.
If someone could help me, tell me what I'm doing wrong that'd be great, what I've tried is below.
I installed HardSPL, so I'm now 10.95.3000
Believed I had rooted it.. I did the following:
Instructions:
Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse
However, it gave no real indication that anything was working, I just trusted, as I have no real past experience with Android.
So I tried several times to flash different ROMs, to no avail. Each time it returns:
Installing from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
Every time. With several different ROM's. Is the problem that I didn't root properly or what?
Thanks in advance for your time reading and helping,
Fordy.

There are several things which might cause, that your flashing fails:
1) amon-ra-1.5.2 is a bit old, should not have directly influence on flashing, but if you want to use the custom-mtd method, and you have to
2) HardSPL is providing only the standard partition layout of the phones flash memory, i.e. a /system partition of about 70MB which is not enough to flash a FroYo-ROM. To change this, you have to apply Firerat's custom-mtd patch, which enables you to change the layout as you want.
Below in my signature you can find the appropiate links. I suggest to you, to read these threads, especially the OPs. Than you will be able to prepare your phone in a wys, that flashing a FroYo rom should work.

Thanks so much for the reply.
I will check that out, however, since my post I have also tried ClockMod & 1.7 images, as well as DangerSPL.
Despite upgrading radio to 2.x DangerSPL seemed to temporarily brick my phone, and I had to reflash the .nbh to get it running again.
I don't know if that makes any difference to your response? (Ie. DangerSPL doesn't have the same 70MB limit maybe, and therefore that's not the cause, I don't know.)
Thanks again, I'l read up on your links anyway so if that is still correct to do, I'll know what I'm doing.

I'm not entirely convinced it is rooted..
Every time I reflash I have to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
again, which I thought wasn't necessary? I also have to re "enter, enter, telnetd, enter" before I can connect to localhost.
And once I have, if I type "su" it simply says:
su: not found
# #
And it shouldn't say "not found" - correct?
I don't understand what I've done wrong.
Also, how can I backup so that if it fails again, I don't have to keep running through initial setup everytime I reflash?
So if I flash HardSPL as update.zip again, and then is this FireRat also an update.zip job, after the SPL?
And then I can continue as I did?
Thanks, Fordy.

F***.
Never mind.
I bricked it. Good and proper.
No getting past T-Mob splash, no recover, no nothing.
£93 down the drain. S***.

Sad to hear, that you bricked your phone, but that was most likely due to flashing DangerSPL. Reading the MTD-post you would have seen, that DangerSPL is never(!) needed.
One advice to all you guys starting to root your phones and flashing custom-roms: Read first, if you are unsure ask, read again and then flash ...
Sent from my Htcclay's Superfly G1 BTX using XDA App

I did indeed flash Danger, bt that didn't brick it.
Or rather, it was recoverable. It just wouldn't boot. I could get into recovery and fastboot etc. and just reflashed the .nbh
The second time however, was even more stupid, I decided the custom MTD looked to fiddly, and just followed a easy to follow guide by KenMood, which said the 2005 SPL was necessary.
I'd read elsewhere that 2005 should never be used, as it as high brick rate and doesn't offer anything over the 2003, so I downloaded and flashed a Haykuro SPL - that, I believe, is where I was stupid.
Ah well.
I'll sell it for parts on eBay, and pick up another. It's a worthwhile experience I guess, just costly.
If you use HardSPL and an MTD patch - is there any danger of bricking it? I'm much more wary now, as I don't want to waste two.
So if I get another..:
1) Revert to RC7 with DREAIMG.nbh
2) Root and install Recovery.img in telnet
3) Upgrade radio to -what?-
4) Flash HardSPL? -which one?, link?-
5) Flash MTD patch -link?-
6) Flash 2.2 ROM -which one? CM 6.0 work ok despite the wiki requiring Danger?-
I think I mucked up last time around because I had so many guides open, with none of them completely relevant to me, I was trying to mix and match thebits that I thought were relevant. I obviously got it wrong.
If you could fill the gaps (Links to correct radio, SPL, MTD patch, ROM) and verify that the order there is correct, and I havn't missed anything, that'd be fantastic. I really want a working 2.2 G1, but don't want to brick another.
Thanks,
Fordy.

F012DY said:
I did indeed flash Danger, bt that didn't brick it.
Or rather, it was recoverable. It just wouldn't boot. I could get into recovery and fastboot etc. and just reflashed the .nbh
The second time however, was even more stupid, I decided the custom MTD looked to fiddly, and just followed a easy to follow guide by KenMood, which said the 2005 SPL was necessary.
I'd read elsewhere that 2005 should never be used, as it as high brick rate and doesn't offer anything over the 2003, so I downloaded and flashed a Haykuro SPL - that, I believe, is where I was stupid.
Ah well.
I'll sell it for parts on eBay, and pick up another. It's a worthwhile experience I guess, just costly.
If you use HardSPL and an MTD patch - is there any danger of bricking it? I'm much more wary now, as I don't want to waste two.
So if I get another..:
1) Revert to RC7 with DREAIMG.nbh
2) Root and install Recovery.img in telnet
3) Upgrade radio to -what?-
4) Flash HardSPL? -which one?, link?-
5) Flash MTD patch -link?-
6) Flash 2.2 ROM -which one? CM 6.0 work ok despite the wiki requiring Danger?-
I think I mucked up last time around because I had so many guides open, with none of them completely relevant to me, I was trying to mix and match thebits that I thought were relevant. I obviously got it wrong.
If you could fill the gaps (Links to correct radio, SPL, MTD patch, ROM) and verify that the order there is correct, and I havn't missed anything, that'd be fantastic. I really want a working 2.2 G1, but don't want to brick another.
Thanks,
Fordy.
Click to expand...
Click to collapse
The first two steps I've never done because I used the 1-click method, but it seems ok for me. Probably somebody else can confirm these steps.
The other steps are as you described (all information is available in my signature), but here again in more detail:
3) Upgrade radio to 2.22.23.02 You find it on Post #76
4) Flash SPL? 1.33.2003, available in the same thread and same Post as above
5) Flash MTD patch described here
6) Flash 2.2 ROM : Depends on you, what you want to have. CM6 will work fine, also each other FroYo-ROM, but remember using the mtd-patch

Related

Questions about rooting htc magic

Hi, I've recently bought a HTC Magic and since then I've been reading into how to root my phone. Before I start I would like to know if it's possible on my phone.
Details:
HTC Magic Vodafone Uk (32B)
Hboot: 1.33.0007
Firmware version: 1.5
Build: CRC24
I've read from a thread in another section of this forum
that it would be impossible because of 1.33.0007 being a perfect spl BUT my phone is running the firmware version 1.5, with a CRC24 build. Would this mean I will be able to root my phone or not?
Also I've been reading up on how you either have cupcake or donut. My version is 1.5 so would that mean I have cupcake?
I'm worried that I might brick my phone so would prefer to use the one click tutorial at theunlockr (would add link but I can't) which is for htc magic running on cupcake.
Would it work?
Sorry for all my questions and I probably will end up asking more
Thanks if anyone can answer these for me!
You should be able to root using the relentless rooter or by following the guide on the unlockr. You are lucky you are running cupcake and don't need to downgrade
I think you are only really at risk when you flash radio and spl. Using the unlockr's stuff shouldn't be too bad. But read eveerything a bajillion times incase
same boat
Hey bunnybag
Was in the same boat as you until yesterday.
Also had a perfect SPL (0010) on a 32A.
I was also reading up a lot wrt getting a new ROM on my phone, and was also afraid of bricking it...
The gold-card method seemed quite involved, and that QMAT application doesn't exist anymore, and the newer version of it, does not run in XP or Vista...
Yesterday, I used the one click method from theunlockr, and after a few mistakes, it worked! Now I have a shiny CyanogenMod running with a 1.6 donut
It seems with the one click method -that you do not need to change the radio or SPL (which I guess are the most dangerous flashes to attempt)
Quicky summary of what I did, and where I deviated:
1) Read the one click method from theunlocker, and some of the comments at the bottom. Also - very importantly - watch the YouTube video at the top of the one click method page a few times!!
2) Downloaded the FlashRec apk (follow link on the one click method's page)
3) Installed FlashRec (the latest version of FlashRec looks slightly different to the one in the YouTube video but functions the same)
4) Did a backup of the existing recovery image via FlashRec. After the backup, you can copy the backed up .img to your PC...
5) Copied the latest Amon RA recovery image (v1.5.2) onto the SD card. Make sure you get the right one... there is a different one for 32A/32B... [Deviation from the one click method- which uses an older version of the RA recovery image]
6) Attempted to flash the new RA recovery via FlashRec. Here is where I struck a problem - the thing just stalled - for a good 10mins - and said 'do not interrupt' :|
I hooked up the USB cable, and from the command prompt ran: adb catlog
From here, scrolling up, I could see that FlashRec gave some message of invalid recovery image... Bit of a bummer - I checked the CRCs of the recovery image after copying it to the SD, and also tripple-checked the filename I typed into FlashRec! In the one click method page, they also warn about inadvertently adding spaces to the end of the filename when you type it in. I also checked for that.
I attempted it once more as follows:
-Rebooted phone
-Deleted the RA recovery .img from the SD
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
-Flash succeeded! maybe FlashRec can't handle very long file names?
7) After the recovery was flashed, I booted into recovery mode (HOME & POWER). Seems like the Amon RA recovery image takes slightly longer to boot that the stock recovery... so - don't crap yourself if it takes a few seconds. This is also a good point to stop, and watch the second video from theunclockr on how to load a new ROM...
8) After verifying that the new recovery image was working I booted back into Android, and I copied my ROM's files onto the SD. I used the Cyanogen Mod. The Cyanogen wiki has a page on how to load it for a 32A and also 32B.
Basically, you need the latest stable cyanogen mod, an Android 1.6 "defanged" ROM (link available on the Cyanogen wiki), and a new kernel. The kernel is 32A/32B specific, so get the right one.
9) With the 3 files on the SD, I booted back into the new RA recovery I just flashed.
10) Did a Nandroid backup
11) Did a wipe/factory reset [Deviation from theunlockr method: I did not format my SD card, or partition it into Ext & Swap. I prefer not to have a Swap partition on the SD, nor do I think I'll need to swap any apps out to the SD card... I think the 32A has enough space... you can read further about it in the xda-developers wiki, under page: HTC_Sapphire_Hacking_2]
12) Still in RA recovery, I applied (in order) a) the defanged 1.6 ROM, b) the Cyanogen mod, c) the new 32A kernel
13) Flashing it takes a while - there is a progress bar...
14) Reboot after all 3 were flashed. The first reboot takes a looong time... couple of minutes... don't worry, or try to reboot again... just give it time.
15) Once inside - tested everything: GPS, Wifi, Phone, Market, G-sensor, Gtalk, Gmail.
16) It might be worth while to note that once the phone is booted, and you've entered your SIM PIN, and the Android desktop is displayed, it can still take a few seconds - 4 or 5 I guess, before you are able to interact (swipe desktop left/right). Give it time to settle down, and all is well
//TODO: still need to flash a new splash-image...
Good luck - post back here with your results!
How to root Magic (32A) with Europe ROM ROM Version:3.05.401.3 with Sense?
Have somebody any idea, how to root Magic (32A) with Europe ROM Version:3.05.401.3 with Sense? Thanks!
bogo_mips said:
Hey bunnybag
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
Good luck - post back here with your results!
Click to expand...
Click to collapse
Ah, I tried using the unlockr's method and failed at flashrec. The unlockr kept saying that the reason was because I was already on Donuts but that is not true. I ended up using the relentless rooter software (looking back, his method is basically an automation of the original method).
Maybe you should post this also in the unlockr so that people who have "backup failed" messages know what to do?
Thanks for the info. It will be very helpful for other members trying to use the unlockr method.
Thanks for the post guys.
@bogo_mips: Great advice and I'll more than likely use this along with the unlockr one click tutorial.
Oh and there's one thing I'm worried about. My phone has somehow automatically downloaded the 1.6 upgrade and it keeps asking me to install it. Anyone know of a way to delete it so that it won't upgrade?
I'm worried that it might install if I turn my phone off.
@bunnybag: that 1.6 download sounds like a problem... if it takes, you'll no longer be able to do to the one-click method...
Check around the forum for advice. I'd guess - since the download would have had to happen in user-space, that the downloaded file might be sitting on the SD card or possibly the phone's flash. Get that Linda Filemanager app from the market and poke around... I guess if you could find the file, and delete / rename it - you could avert an install?
Alternativley, I'm guessing that if you can attempt the one-click method, that you'll have a new recovery image before you power down your phone, so - I think that will keep you safe...
@visitador02: according to the FlashRec page, there are 1.5 cupcakes out there which have been patched, so - FlashRec can't work on them... maybe that is what happened to you...

Need help I have tried everything

Hi guys, I'm pretty new here so I hope someone can help me.
I am having serious issues trying to load ANY new ROM onto my missus HTC Vodafone Magic 32B Details -
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Since getting the phone second hand from eBay it has played up like nothing else, it now will not even boot into the OS, I’m pretty sure the guy I bought it from, who I cannot get in contact with, stuffed something up when he unlocked it for different carriers. But I'm positive it is an OS issue and not a straight hardware fault.
Anyway I have spent about a day and a half mucking about on here trying things and reading a HEAP of stuff and I just can’t seem find a definitive answer to my problem.
I have tried installing many different roms:
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.7 Swap
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.6 Swap.zip
st0kes-v1.4.1
HTC_Magic_Vodafone_AU_Original_ROM
and a few others I cannot remember.
I am using Amon RA recovery ROM, I have rooted the phone based on method 2 in the magic rooting wiki (everything went smoothly), I have updated the SPL to version 2005 which are all the apparent pre requisites for performing this kind of operation.
Anyway down to the problem every time I try and apply a ROM, by renaming it to update.zip, copying it to the root of my SD card, then loading up RA recovery ROM and going to flash zip from SDcard I get the following messages:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Install from sdcard...
finding update package...
opening update package...
verifying update package...
E:corrupt file:
<various file names based on which ROM I’m trying to use, always the same one on each ROM though>
E:verification failed
Installation aborted
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is starting to drive me insane, I really need to get ANY usable ROM on there I don’t care which one, otherwise I have a AU$400 lump of useless technology.
Any help people can provide me with be unbelievably appreciated.
Thanks in advance
i cant guarantee i can help, but i will try to see if i can, or also help wit some research for ya
first, what version of amon ra are you using???
2nd, do you know if you got 1.5 or 1.6 firmware???
idk too much about firmware, all i know is my mytouch was cupcake when i got it (1.5) then updated to 1.6 ota...
also are you making sure that you wipe before you try to load the roms???
Hi mate, thanks for getting back to me so quickly
The version of amon ra i am using is recovery-RA-sapphire-v1.6.2G.img this seemed to be the right one as i have a google branded phone
I am not sure what version of firmware i have, is there an easy way to check? the only real details I have is what i get from the fastboot screen as i posted above
And yes I am definately wiping the phone before I install the roms, every single time
Thanks
well i just did a few searches and i couldn't find out how to check the firmware...
i dont want to tell you to try something and then crash your system, but...lol...
i would try to "Unroot" the device, basically placing it back to 1.5 firmware and then you can "Root" it yourself.
if you want to try this here is the link for the 1.5 software
link for tutorial:
http://theunlockr .com/2009/08/22/how-to-unroot-your-mytouch-3g/
link for file:
http://www.megaupload .com/?d=BLM4EDGE
no space in the url tho...
all you have to do is,
boot into recovery
go to wipe, and wipe the top three options
go back to the main screen and select Usb-Ms toggle
then plug your device in via usb
and drop the file to your sd card. (not in a sub folder)
then safely remove your phone from pc
then press home on your phone to disable usb
then choose power off.
now to turn it back on,
holding Volume "Down" + "Power"
DON'T PRESS ANYTHING YET
after it reads the image it should show at the bottom, Action:yes, and then click trackball,
let that run all the way thru, and make sure you have enough battery juice, for this to run all the way thru.
when it's complete it will ask if you want reboot, then click Action for yes (trackball)
i believe that should unroot your phone but PLEASE PLEASE PLEASE
do as much research as possible and also question others about this method and see if you can come to a conclusion in which you are satisfied.
as always, i am in no way responsible for the Bricking or Exploding of your device...
here is a link that has great tutorials & and also you might want to check youtube, thats where i findout how to alot of things...
Um, you already have amon ra recovery on there. I assume you've already bought it rooted?
You can only check the firmware by booting up your phone and going into settings. Since you've wiped and aren't able to install a rom, you aren't able to use the phone right now, am i correct?
sanman1185, I'm glad you try to help but you gotta get more info from him first. Cause if he's already rooted, doing what you're telling him to do won't make much progress. Edit: Ok, he's already rooted. You're just telling him to do what he's already done? And he doesn't have any firmware because his phone lacks any rom right now.
Anyways, answer some of those and don't be too worried about bricking your phone. The main reason that people brick their phones is when they touch the radio and SPL.
Edit: Ok I just read that you rooted your phone so you don't need to "unroot" and root it again.
You also put on SPL 2005 instead, so post your boot info again. I assume it's an ENG SPL too, if you haven't found a solution, send me a PM and I'll help you on google talk / MSN or something.
Ps. You don't have to rename the roms to update.zip, his new recovery allows you to flash w/e zip you want. Try another SD card as well, maybe that'll help? but if not, yeah just pm me
KAwAtA - def. understand what your sayin, only reason i was thinkin to unroot and start fresh is cuz, when i started flashin roms, i ended up being stuck on the boot screen for over 30mins. pulled the battery, then read somewhere to partition sd card, then that wiped the zip from my card, lol...so what i did instead of placing another rom on the device, is "unrooted" and started fresh from the start. my theory is if you think your "Jack'd" then start from the beginning and find your mistake.
and if he did unroot and it ran Cupcake on device, and actually loaded wouldn't that have been making progress??? since he couldnt get it to load in the first place???
like i said just a thought, theory, or 2centz (sense)...
but again, i'm glad someone actually responded with a diff method or with additional ?'s, so this way he can get answers from all angle's ya kno...
and if you guys do figure this nifty lil'thang out, could you post what you guys did on here, so myself or future ppl'z that may run into this can have it as a ref??? thnx... Pce

Read this before starting a thread, Most Question Asked are Answered

Mods can we make this a sticky to stop further irrelevant threads
Please categorize your question accordingly, Anaylize which forum to post it
Development forum is only for development of phone OS related stuff
Q- My phone is stuck and the android loading or the second screen
A- your ROM flash went wrong or some system files are missing
Remedy- Flash the ROM again or try flashing some other ROM, check your SD card if its inserted properly(If you have Linux-swap or apps 2 sd activated)
Q- I cant go past the first splash screen and i cant move into recovery or bootloader
A- Say goodbye to your phone, it is bricked.
Remedy- PM me maybe i can help you get a new phone (already got a new phone after bricking)
Q- I cant go past the first screen but can enter recovery or SPL
A- Your ROM is not flashed properly or check your SDCARD maybe its not inserted (SDCARD step only if you have apps 2 sd , linux-swap or data 2 sd)
Remedy- flash a new ROM, use nandroid and and try reformatting the ext partition
Q- My phone is slow
A- Your phone is overloaded
Remedy- Try wiping, removing some apps and increase linux swap
Q- Home screen reloads after quitting Application
A- Your RAM is not enough, phone quits Launcher or Rosie to make some RAM free
Remedy- Use or increase linux swap or try increasing swappiness
Q- Sdcard says update.zip not found
A- maybe you renamed the update.zip as update.zip.zip .If you have enabled show file extensions for know file types then rename it as update.zip and if not then rename it as update
Q- Which ROM is best for me/ Which ROM is the best for 32A/B?
A- Take some time on the forums, look at the ROMs available for your device and individually assess what works for you by reading the various issues affecting them and make a decision. If that still doesn't work out for you, hey, that's what makes XDA great, try a different one and so on, till you find one that YOU'RE happy with. It's very subjective since what my needs are could be totally different from what yours are.
Q-What will/is released, When will be released, New is released
A- Post is General Forum, leave this forum for Phone Development by Developers
Any other questions or suggestions welcome
Q- Which ROM is best for me/ Which ROM is the best for 32A/B?
A- Take some time on the forums, look at the ROMs available for your device and individually assess what works for you by reading the various issues affecting them and make a decision. If that still doesn't work out for you, hey, that's what makes XDA great, try a different one and so on, till you find one that YOU'RE happy with. It's very subjective since what my needs are could be totally different from what yours are.
Q- ADB doesn't find or see my device?
A- I suggest reading the Sapphire Wiki as it contains a lot of information about troubleshooting when you're stuck
Q- I have no data/ 3G connection
A-Check under settings ->wireless controls->mobile networks->access point names, If you have no APN set then add your carrier APN settings from this list here
anybody with a new no thread start wiki
charnsingh_online said:
...
Q- I cant go past the first splash screen and i cant move into recovery or bootloader
A- Say goodbye to your phone, it is bricked.
Remedy- PM me maybe i can help you get a new phone (already got a new phone after bricking)
...
Click to expand...
Click to collapse
Not 100% correct: if you can still load in fastboot mode (vol DOWN+POWER) you can still boot a recovery image and flash it on the device:
1. fastboot mode
2. fastboot boot myrecovery.img
3. (in the recovery) adb shell mount /sdcard
4. adb push myrecovery.img /sdcard/recovery.img
5. adb shell flash_image recovery /sdcard/recovery.img
myrecovery.img: whatever the file is called.
Bootloader is same as fastboot mode
Hey...
How do I know if I have a 32a/32b phone?
I've got a myTouch 3g and I just got it a month ago.
Is rooting illegal? I know it voids your warranty but do you get apps for free and stuff?
juiceaccts said:
How do I know if I have a 32a/32b phone?
Click to expand...
Click to collapse
Boot your phone into fastboot mode:
Power phone off
Hold Back key and power phone on
It will bring up a screen which either says
SAPPHIRE PVT 32B SHIP S-ON G
or
SAPPHIRE PVT 32A SHIP S-ON H
There will be instructions on the screen to power the phone off so you can boot as per normal.
elegos said:
Not 100% correct: if you can still load in fastboot mode (vol DOWN+POWER) you can still boot a recovery image and flash it on the device:
1. fastboot mode
2. fastboot boot myrecovery.img
3. (in the recovery) adb shell mount /sdcard
4. adb push myrecovery.img /sdcard/recovery.img
5. adb shell flash_image recovery /sdcard/recovery.img
myrecovery.img: whatever the file is called.
Click to expand...
Click to collapse
Yeah but charnsingh says, if we CAN'T go into recovery.. You're assuming we can
The post is a bit misleading, cos we don't expect physical damage to the device (in which case, you get to the first splash, but can't reach recovery.. i.e. your Back/Vol. down buttons don't work)
Q: What's Goldcard? and how to make a Goldcard
minhzc said:
Q: What's Goldcard? and how to make a Goldcard[/QUOTE
damm - i understand all, but what is a goldcard and how to create?
Click to expand...
Click to collapse
Goldcard, a special sd card that ur phone spl accepts, search the dream forum
Whenever I flash a new ROM I backup my data and apps using either Backup To Root or MyBackup Pro. When I reinstall my apps it never puts the apps back into the Market under my Downloads so that if the app developers update their apps it shows that there is an update. IN fac the only apps shown are the ones I've purchased.
What do I need to do, besides reinstalling each one individually, in order to have the Market get all my apps in the Downloads the way I want them?
Thanks
can someone explain what SPL refers to?
and then i hear terms like perfected SPL, eng SPL....
ive flashed some ROMs earlier...without worrying too mmuch about this SPL business, and now with a mandatory rogers update out, people are talking about SPLs (see rogers thread)
cheers
So what is an SPL anyway? What does it do?
The SPL, or Second Program Loader, is essentially the Android bootloader. It's job is more than just loading the Android OS - it also offers several other boot options, including Recovery mode, Fastboot, and HBOOT modes, and ultimately it's the SPL that allows manipulation of the flash nand on your device. Part of the SPL's job is to ensure that the data flashed to the device is correct. Most of the current shipping SPLs (apart from the "Perfect SPL's) let us flash a complete ROM image, but don't let us flash a recovery rom or boot image as it checks the verification signature. Haykuro has modified the SPL's available to remove this check and this is what the Engineering SPL's available offer. As the SPL is so crucial to the handset though, you have to be very careful when flashing it as if it's updated incorrectly then you may be incapable of restoring it without specialised hardware and knowledge. You essentially have a very expensive brick
Click to expand...
Click to collapse
From the xda HTC sapphire wiki
remap "search" button on MyTouch
I have searched the forum and only found results for the G1 or remapping the soft keyboard...
Can the search button (magnifying glass) be ramapped as hard key to the camera?
If this has been discussed and i missed it, links are appreciated.
If it's a kernel-level issue, i'm on enomther's TheOfficial 2.5.1 AOSP.
Thanks in advance
[Sorry mods if this isnt the right place to ask this, tired, at work and pretty much I was asleep at the wheel. Please move this to the appropriate subforum if need be. ]
if i download a rom using my phone can i rename it and apply it or do i need a computer. im already rooted and ive got the requirements for the rom already on my phone. i just want to know if its possible or not.
it will work without computer
ROM Development
Hi, I have been Googleing for a while now and cant find any info on how to remove my current Android keyboard from my current ROM and replace it with the Hero keyboard – does anyone have any links relating to ROM modification. I a have come across how to download the Hero keyboard and load it into your current setup but I kept on getting FCs plus I want to learn how to modify any part of a ROM not just the keyboard.
Thanks.
Does my new mytouch with the more ram and 3.5mm jack have an actuall name?
Hello, I recently purchased my first smartphone. The mytouch3g with 288 ram and 3.5mm jack. For two weeks now I have been researching about rooting and roms. Most of the info that i am reading/viewing is on the oringinal mytouch3g...does this stuff still apply to mine? Will installing a custom rom give me more ram? Obviously I am completely new to all this but I am finding all this stuff to be quite fascinating...Any help would be greatly appreciated.
Thanks
As a solution to the brick issue and not getting past the bootscreen or not beeing able to load fastboot or recovery here's a solution which I had tried on my magic after I lost all hope and it worked ..Thanks to God and google
while on the bootlogo screen stuck, insert your datacable. it will show fastboot in red color on top corner.
run the android sdk cmd from dos prompt and enter "fastboot boot recovery_image_name.img" provided you can find the appropriate recovery image for your phone.
after updating, it will restart and you will bt good to go

MyTouch 1.2 (aka Fender, aka LE) w/3.5mm headphone jack

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?

Return Legend to stock OS [SOLVED]

Hi guys,
I've tried many ways to fix and hope that some light could be shed from you
- Trying to get back to stock build after downgrading to 1.31 via this process wiki.cyanogenmod.com/wiki/HTC_Legend:_Full_Update_Guide
- The ‘rooting tools’ in step 2 of 2nd section were not available anywhere so tried other avenues to root
- None successful
- After lots of playing around – I decided to try and get back to latest stock build
- Ran the uncracking.bat file which was installed during the Cyanogenmod process (which I hoped would restore things)
- Not successful
- I’m thinking that maybe the adb shell command from the Cyanogenmod process may have caused some issue: /data/local/flash_image misc /data/local/misc1-2.img
- Trying the HTC OTA system update (from Android 2.1 to 2.2) fails while trying to update and goes into the recovery screen (red triangle with exclamation mark, black background) <<<<<<<<<
- Then, when pushing vol up and power the following error is shown:-
----> E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
Any help would be greatly appreciated..
Doing a general factory reset does not seem to help.
I do not need to keep any apps or data, a complete wipe so I can start afresh would be great if possible!
Thanks
94 views and no replies.
Oh dear
I tried to return to stock rom by running the wwe rom from shipped-roms only got the error 155. Then extracted the rom.zip from the exe and flash that no go, couldn't work out a way to do it successfully.
Sent from my Legend using xda app-developers app
Cool.. It doesn't have to be stock. All I need is 2.2 or 2.3 (I was trying for cyanogenmod 7.2). At the moment it's stuck on a buggy 2.1!
I'm not sure of the current state, as I said I think going half way through the cyanogenmod kinda of changed something important ( eg. /data/local/flash_image misc /data/local/misc1-2.img via ADB).
Do you know of any way I could make either of these OSs work, with the minimum of hassle?
ranger4740 said:
I tried to return to stock rom by running the wwe rom from shipped-roms only got the error 155. Then extracted the rom.zip from the exe and flash that no go, couldn't work out a way to do it successfully.
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
1st thing 1st, unlock your bootloader.
2ndly, once unlocked, flash cwm.
3rd, download any ROM you want (lets pick cm 7.2 for starting point since you said no need for stock ROM) then put into your sd card.
Lastly, boot into cwm. Wipe all (data, cache, dalvik cache) then Flash(install) ROM.
Thats it (assuming your device is not usb bricked or hard bricked and you do all the steps correctly).
How?
To unlock, go to htc web site or google "unlock bootloader+htc dev"
Flash cwm? Go to dev section, theres a thread of cwm, follow "s-off" method (of course after unlocking your BL.
Boot into cwm? Shut down/turn off your phone. Once it off, press power button and volume down at the same time, hold it fow few moment before release it.
Once in cwm, install from sd card (you will know once you in it)
Then? Enjoy ur legend and flash any ROM once you got bored with cm7!
Sent from my Legend using xda app-developers app
Thanks for the response.
Firstly: -
- HTC Sync is not reading my (I think needed for HTCDev boot unlock)
- I did try just running the HTC Dev RUU - but it said I need to update the ROM(?) (from Build 1.31), which I believe is done by the HTC OTA update, which doesn't work
HBOOT 1.00
S-ON
Build 1.31
Not allowing update as loops into recovery with E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
feed3 said:
1st thing 1st, unlock your bootloader.
2ndly, once unlocked, flash cwm.
3rd, download any ROM you want (lets pick cm 7.2 for starting point since you said no need for stock ROM) then put into your sd card.
Lastly, boot into cwm. Wipe all (data, cache, dalvik cache) then Flash(install) ROM.
Thats it (assuming your device is not usb bricked or hard bricked and you do all the steps correctly).
How?
To unlock, go to htc web site or google "unlock bootloader+htc dev"
Flash cwm? Go to dev section, theres a thread of cwm, follow "s-off" method (of course after unlocking your BL.
Boot into cwm? Shut down/turn off your phone. Once it off, press power button and volume down at the same time, hold it fow few moment before release it.
Once in cwm, install from sd card (you will know once you in it)
Then? Enjoy ur legend and flash any ROM once you got bored with cm7!
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
Curveau said:
Thanks for the response.
Firstly: -
- HTC Sync is not reading my (I think needed for HTCDev boot unlock)
- I did try just running the HTC Dev RUU - but it said I need to update the ROM(?) (from Build 1.31), which I believe is done by the HTC OTA update, which doesn't work
HBOOT 1.00
S-ON
Build 1.31
Not allowing update as loops into recovery with E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
No, you dont need htc sync. i've never installed htc sync either. you only need the driver (which is logically will be installed along with htc sync but also can be installed separately and it is needed so that your device will be recognized when you boot it into fastboot mode) and no, you no need to upgrade ROM, you only need to upgrade your bootloader (that HBOOT 1.00) and it is not updated through OTA.
Seriously, it took me only 2 hours (including downloading and installing SDK, driver, waiting for unlock file from htc etc) last time i did it and i have done it twice which 2nd time (because i had usb soft brick) is much more shorter as i saved the unlock file and it seems can be reused. What takes longer for me at that time is to understand the whole process, reading and researching through multiple sites but now you have a guide, so all you have to do is to read the instructions carefully. Once you unlock your bootloader and flash cwm, everything will be super easy (assuming your device doesn't have any defects from the beginning.)
Ok, thanks very much feed3. Will try this again based your info and the mini guide I've just written myself.
But before I go ahead, I'd rather not touch it than to make it unusable.
What does USB Bricked and Hard Bricked mean?
Thanks
----------------------------------
My guide:-
After reading the latest reply at XDA decided to give the root another go:-
http://forum.xda-developers.com/showthread.php?p=29969951#post29969951
- Seems need to upgrade HBOOT (to use the HTC Dev boot unlocker)
o See here post 62 and poss (BEFORE THIS READ NEXT BIT) 74 http://forum.xda-developers.com/showthread.php?t=1498298&page=7
- READ HERE FIRST  Looks like other people have had issues using stock Vodaphone 2gb SD card for goldcard. Get another and try. Go post that states ‘EDIT: It seems the LEGEIMG is not getting loaded’ that and the few posts after explain what’s happening. http://forums.whirlpool.net.au/archive/1657826
- So neeed to have a gold card in to make the above work <<
o Looks like this can do an auto gold card for you https://sites.google.com/site/roothtchero/goldcard-2. Remember to format to FAT32 in windows as opposed to phone. SEE Hubdolt POST WHICH TALKS ABOUT FORMATTING VIA THE CMD LINE (FOR VODAPHONE LEGEND)
Curveau said:
Ok, thanks very much feed3. Will try this again based your info and the mini guide I've just written myself.
But before I go ahead, I'd rather not touch it than to make it unusable.
What does USB Bricked and Hard Bricked mean?
Thanks
----------------------------------
My guide:-
After reading the latest reply at XDA decided to give the root another go:-
http://forum.xda-developers.com/showthread.php?p=29969951#post29969951
- Seems need to upgrade HBOOT (to use the HTC Dev boot unlocker)
o See here post 62 and poss (BEFORE THIS READ NEXT BIT) 74 http://forum.xda-developers.com/showthread.php?t=1498298&page=7
- READ HERE FIRST  Looks like other people have had issues using stock Vodaphone 2gb SD card for goldcard. Get another and try. Go post that states ‘EDIT: It seems the LEGEIMG is not getting loaded’ that and the few posts after explain what’s happening. http://forums.whirlpool.net.au/archive/1657826
- So neeed to have a gold card in to make the above work <<
o Looks like this can do an auto gold card for you https://sites.google.com/site/roothtchero/goldcard-2. Remember to format to FAT32 in windows as opposed to phone. SEE Hubdolt POST WHICH TALKS ABOUT FORMATTING VIA THE CMD LINE (FOR VODAPHONE LEGEND)
Click to expand...
Click to collapse
in short, hard bricked means your phone is totally unuseable, usually because of hardware defects but also might be cause by flashing wrong ROM, for example flashing ROM that actually not built for your device. Usually, you cannot do anything with it, cannot enter fastboot, recovery etc. Soft brick is repairable, you still can boot to recovery or even to the OS. Might be caused by some partition corruption (in the case of usb bricked, it is /misc partition).
If you use htc dev path to unlock your bootloader, no need for gold card. Thats for sure.
If your phone is usb soft bricked (among the symptoms are you will be able to boot into the OS ONLY if your phone are pluged in into usb, and/or adb not working at all) then google or search in xda for "htc legend+usb brick" and fix it. I'm pretty sure only then you can update your HBOOT and therefore unlock your bootloader via htc dev.
Once done, go to HERE and flash cwm using s-off method (dont care about your s-on that you see in your bootloader, the "UNLOCKED" word in it is more important)
In response:-
Thanks for the clarification.
- when using the process here http://forum.xda-developers.com/showthread.php?t=1498298&page=7 - and trying to get the bootloader to run the LEGEIMG.zip file, it flashes up stating "no image or wrong image!", it runs too fast to read it exactly.
- then looking at the same error this guy was getting at (see the 'EDIT: It seems the LEGEIMG' post onwards) http://forums.whirlpool.net.au/archive/1657826 - they have the same Vodfone Legend as me, a gold card had to be used to do the above update process (which should update HBOOT).
- this is the only HBOOT update process I've seen, but isn't clear as they look like they're on 2.2 and HBOOT 1.01.
............................Good grief
feed3 said:
in short, hard bricked means your phone is totally unuseable, usually because of hardware defects but also might be cause by flashing wrong ROM, for example flashing ROM that actually not built for your device. Usually, you cannot do anything with it, cannot enter fastboot, recovery etc. Soft brick is repairable, you still can boot to recovery or even to the OS. Might be caused by some partition corruption (in the case of usb bricked, it is /misc partition).
If you use htc dev path to unlock your bootloader, no need for gold card. Thats for sure.
If your phone is usb soft bricked (among the symptoms are you will be able to boot into the OS ONLY if your phone are pluged in into usb, and/or adb not working at all) then google or search in xda for "htc legend+usb brick" and fix it. I'm pretty sure only then you can update your HBOOT and therefore unlock your bootloader via htc dev.
Once done, go to HERE and flash cwm using s-off method (dont care about your s-on that you see in your bootloader, the "UNLOCKED" word in it is more important)
Click to expand...
Click to collapse
Curveau said:
In response:-
Thanks for the clarification.
- when using the process here http://forum.xda-developers.com/showthread.php?t=1498298&page=7 - and trying to get the bootloader to run the LEGEIMG.zip file, it flashes up stating "no image or wrong image!", it runs too fast to read it exactly.
- then looking at the same error this guy was getting at (see the 'EDIT: It seems the LEGEIMG' post onwards) http://forums.whirlpool.net.au/archive/1657826 - they have the same Vodfone Legend as me, a gold card had to be used to do the above update process (which should update HBOOT).
- this is the only HBOOT update process I've seen, but isn't clear as they look like they're on 2.2 and HBOOT 1.01.
............................Good grief
Click to expand...
Click to collapse
EXACTLY the same error message that you got, HERE and the op solve it.
Btw, during unlocking my bootloader, i've never encounter (or did i forget already??) to requiring this zip file. Isn't bootloader RUU from HTCdev is all we need? I think thats the only file i have to get (apart from the unlock bin file of course) if my memory doesn't cheat me..
Sure - but as the guy mentions formatting to FAT32, that's usually associated with goldcard creation right.
I've ran the bootloader RUU from HTC Dev a few times, and it always says that the ROM (HBOOT, build(?)) needs updating. Thus trying the aforementioned process (post 62 http://forum.xda-developers.com/showthread.php?t=1498298&page=7) to try and get the Rom (HBOOT) updated, which didn't work, which then loops back round to dealing with the zip file read error.
feed3 said:
EXACTLY the same error message that you got, HERE and the op solve it.
Btw, during unlocking my bootloader, i've never encounter (or did i forget already??) to requiring this zip file. Isn't bootloader RUU from HTCdev is all we need? I think thats the only file i have to get (apart from the unlock bin file of course) if my memory doesn't cheat me..
Click to expand...
Click to collapse
I'm getting more confuse here. I've never use goldcard as i reluctant to "sacrifice" my one and only card but here i am with unlocked bootloader. The RUU file is the one that will update your bootloader. Read instructions at htc dev carefully.. good luck..
Sent from my Legend using xda app-developers app
You need to read this post by blay0, it instructs how to update hboot without going back to stock, using gold card or any other outdated method of rooting (unless your on hboot less than 1.00 then you should follow the s-off method of rooting)
http://forum.xda-developers.com/showthread.php?p=22613990
Sent from my Legend using xda app-developers app
I think the reason I can't do the blay0 method is because of the stock sd card I'm using. It's not picking up the rom zip file.
I've ordered another http://www.kikatek.com/P188409/SDC10-8GB-Kingston-MicroSDHC-8GB-Card-Class-10?source=froogle
Will try again, and if that doesn't work - try this other method (as the guy here has HBOOT 1.00 and a Vodafone Legend too) http://chrg.zxq.net/htc-legend-root.html.
Many thanks for all your help people.
Will report back any success for the benefit of others.
All the best
ranger4740 said:
You need to read this post by blay0, it instructs how to update hboot without going back to stock, using gold card or any other outdated method of rooting (unless your on hboot less than 1.00 then you should follow the s-off method of rooting)
http://forum.xda-developers.com/showthread.php?p=22613990
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
Hi guys,
Good news! I unlocked the bootloader with my 'new' SD card using the blay0 process (from the last post).
This is the first time I've done this though, and am just trying to figure out how to flash CyanogenMod 7.2.
ROM Manager doesn't work with 2.1 (installed) any more.
Can someone please briefly explain how I would flash.
Many thanks
Curveau said:
I think the reason I can't do the blay0 method is because of the stock sd card I'm using. It's not picking up the rom zip file.
I've ordered another http://www.kikatek.com/P188409/SDC10-8GB-Kingston-MicroSDHC-8GB-Card-Class-10?source=froogle
Will try again, and if that doesn't work - try this other method (as the guy here has HBOOT 1.00 and a Vodafone Legend too) http://chrg.zxq.net/htc-legend-root.html.
Many thanks for all your help people.
Will report back any success for the benefit of others.
All the best
Click to expand...
Click to collapse
SOLVED
Ah, done !! Woohoo!
That was lots of work. Well, easy via the HTCDev method <<
To get 7.2 on followed here:-
see s-off method to install recovery image http://forum.xda-developers.com/showthread.php?t=1290841&highlight=clockwork
To get into the recovery – use the col down + power button
Follow Method via Recovery here http://wiki.cyanogenmod.com/wiki/HTC_Legend:_Full_Update_Guide
Good luck everyone and thanks again XDA
Curveau said:
Hi guys,
Good news! I unlocked the bootloader with my 'new' SD card using the blay0 process (from the last post).
This is the first time I've done this though, and am just trying to figure out how to flash CyanogenMod 7.2.
ROM Manager doesn't work with 2.1 (installed) any more.
Can someone please briefly explain how I would flash.
Many thanks
Click to expand...
Click to collapse
Hello,
take the recovery-clockwork-5.0.2.0-legend.zip , put it on your SD-card and rename it to update.zip. Then use th S-ON-method from here and you will have no problem.
so there is no way to return the legend back to stock rom after all ?

Categories

Resources