Bricked.... - G1 General

I have the Android Dev Phone 1 and I had just gotten through rooting it following the wiki's instructions, I wanted to try to install Hero with the Rosie UI so I was following these directions to then flash it:
http://forum.xda-developers.com/showpost.php?p=3816278&postcount=3
But I was in the process of doing that, I had two micro SD cards with the proper updates on each, and when it came time to switch the cards(I didn't hit any buttons or anything by accident) I switched them, hit Alt +X, nothing happened. Nothing. I tried it a few more times and still nothing. All other combos of letters and trying to get it to respond in any way did nothing. So I pulled the battery out and now I cannot get past the G1 screen. It won't do the boot where you hit the camera button and power or the home + power boot. It just sits at the black screen with the G1.
I tried getting the ADB devices to recognize it and no dice. I can't get it to do anything other than go to the black screen. I tried searching the forum and I scoured google but all the things I could find were where you could get some kind of input beyond the screen.
I'm kinda mad as I just got this phone and paid $450 some bucks for it, can someone help me out? I'm on Vista X64 and Ubuntu X64. Thanks in advance to anyone who can help me unbrick my $450 paperweight.

you need to update the from the original recovery, which im guessing you still have to swithch to one of these. http://forum.xda-developers.com/showthread.php?t=455860 then you can update to the SPL H
Hard SPL is the recommended one. Which in turn will give you the list feature Alt-x

Truculent said:
I have the Android Dev Phone 1 and I had just gotten through rooting it following the wiki's instructions, I wanted to try to install Hero with the Rosie UI so I was following these directions to then flash it:
Click to expand...
Click to collapse
So is your phone a "PVT" or "DVT"? If it's a DVT and you tried to install Haykuro's SPL 1.33.2005, then you are almost certain to have a paperweight. I believe it's mostly consensus that the DVT phones brick if you go to that SPL. There are a bunch of threads here on it.

Truculent said:
I have the Android Dev Phone 1 and I had just gotten through rooting it
Click to expand...
Click to collapse
Aren't ADPs rooted out of the box?!
You have to install the new SPL and JF's recovery image before you to to Hero/Rosie.

ADP's certainly do provide root out of the box, so no need to go to the trouble.
@Truculent:
Sounds like this is what happened;
1) installed rc29 for tmobile branded dream (mistake),
2) rooted that and probably installed some older radio image (or left original radio),
At this point, though you wasted time and risked screwing it up, you were probably still OK. The fact that you would even attempt the previous steps says something though...
3) reversed the sdcards and accidentally installed SPL before radio upgrade.
Its bricked and nothing you can do for now. Most likely this will require a physical disassembly and reprogramming to repair.
Honestly, anybody who could make a bonehead move like rooting a prerooted device by installing a root-locked firmware shouldn't be messing with SPLs. In other words, you deserve what you got. Particularly since you DONT NEED the modified SPL for what you were attempting! There's a system/apps to SD approach to fitting it with the standard disk layout.... which you could have stepped to *directly* from a stock ADP1 without ANY risk of bricking.

lbcoder said:
ADP's certainly do provide root out of the box, so no need to go to the trouble.
@Truculent:
Sounds like this is what happened;
1) installed rc29 for tmobile branded dream (mistake),
2) rooted that and probably installed some older radio image (or left original radio),
At this point, though you wasted time and risked screwing it up, you were probably still OK. The fact that you would even attempt the previous steps says something though...
3) reversed the sdcards and accidentally installed SPL before radio upgrade.
Its bricked and nothing you can do for now. Most likely this will require a physical disassembly and reprogramming to repair.
Honestly, anybody who could make a bonehead move like rooting a prerooted device by installing a root-locked firmware shouldn't be messing with SPLs. In other words, you deserve what you got. Particularly since you DONT NEED the modified SPL for what you were attempting! There's a system/apps to SD approach to fitting it with the standard disk layout.... which you could have stepped to *directly* from a stock ADP1 without ANY risk of bricking.
Click to expand...
Click to collapse
I thought it was rooted when I bought it, but I was not able to install programs that needed root. They told me I needed root. I'm kicking myself right now. But yes, that sounds like what I did. This is my first time of doing anything with cell phones, I'm trying to learn. I didn't see anything regarding the ADP's so I figured the T-mobile G-1's were the same, my fault. I spent hours reading this forum and the wiki and didn't see anything concerning this kind of thing.
Is there any way I can do the disassembly and reprogramming? I did DD-WRT stuff on my routers, is there a way to JTAG or something similar to these phones? Oh, and this is a PVT phone.

Root is hidden from programs for security reasons (keep programs from going nuts and messing up your system), but a little bit of "adb shell" would show it to you.
I really doubt that PVT or DVT matters. The distinction was guessed at by trying to follow the pattern of bricking BEFORE it was determined that the radio version was the common factor. Even then, there was really no conclusive info showing that DVT boards were more prone to bricking, I think there was a sample of about 14 devices bricked back then, of them 6 were PVT and 8 were DVT.... you see how weak the evidence is? It would make a statistician cringe. See this: http://forum.xda-developers.com/poll.php?do=showresults&pollid=1523 - only the number of PVT bricks has increased because everyone got scared of trying to write the bootloader to DVTs, but you can see that there are some DVTs that flashed fine. 2 at least.
As for hooking up a jtag... there was someone looking into that, but I haven't heard of any repair procedures yet. Note that though it hasn't been done yet, there is no question that it is possible since the chips must have been programmed by some means initially.

Related

How to intentionally brick your G1?

Here's my problem:
1) I had rooted my phone in the past.
2) I need to do a warranty return for a bad touchscreen and keyboard
3) I'm unable to flash back to stock because the home key is "stuck", so I can
only boot into recovery mode.
Is it possible to brick the phone so that it get stuck at the T-mobile loading screen before it default boots to the recovery screen?
If so, what is the most reliable way to brick my phone when all I have access to is the recovery mode?
fastboot flash a corrupt boot.img.
coolbho3000 said:
fastboot flash a corrupt boot.img.
Click to expand...
Click to collapse
That would be my first choice as well... except that I can only get to recovery mode, even when I hold down the camera button.
Closest thing I can do is flash an update.zip
my touch screen died today thank god for a trackball lol
g1junky said:
my touch screen died today thank god for a trackball lol
Click to expand...
Click to collapse
That's what I was thinking... I figure I'd just use my phone as-is until the replacement arrived, then I'd flash it back to stock before returning it...
If it's just a bad touch screen, they'll replace it without much fuss for next to free (just $10 shipping). Which is a very fair deal... unless you rooted your phone (boo!).
Then the home key got "stuck"... what bad luck... It's obvious when you turn it on that it's been rooted because of the custom recovery image... I'd rather make it a bit harder for them to determine my warranty's void instead of just having to turn it on.
@coolbho3000: I noticed that a boot.img file is included in some random update.zip (JFv1.3_RC8.zip) I just downloaded... Any idea what to hexedit on it to ensure it'll brick if I do an update through recovery mode? Or should I just pull the battery during the update (many times if need be)?
Update: I tried randomly screwing with the boot.img file using notepad++, but the damn phone won't use it for the update because the digest failed during the verification process. I also pulled the battery out during the part when it says it's writing the boot.img file (twice) without success -- although in this case, 'success' would be a bricked phone.
Why is this phone so hard to brick? Others just look at their g1 and can brick it...
I managed to brick my phone! It was harder than I thought (well, considering my many failed attempts), but here's how I did it:
I downloaded haykuro's 1.33.2005 special spl, renamed it to update.zip, and updated the g1 with it through the recovery panel. It's now permanently stuck at the T-mobile G1 screen. Worked for me, YMMV.
If that didn't work, my next two ideas were:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Hope this helps others in the same boat. I'll update with the bad news if they do, in fact, figure out I had rooted my phone anyways. I'm sure it's possible, yet probably unlikely. Otherwise, no news is good news.
Be glad you didnt have a custom spalsh image lol
Daemonjax said:
Here's my problem:
1) I had rooted my phone in the past.
2) I need to do a warranty return for a bad touchscreen and keyboard
3) I'm unable to flash back to stock because the home key is "stuck", so I can
only boot into recovery mode.
Is it possible to brick the phone so that it get stuck at the T-mobile loading screen before it default boots to the recovery screen?
If so, what is the most reliable way to brick my phone when all I have access to is the recovery mode?
Click to expand...
Click to collapse
Pretty simple. First do a recovery to factory settings using the camera and the start button. then copy the latest SPL from this website,
in the instructions it says that you have to flash the latest radio first, don't do that, just flash the SPL... reboot, voila, you have just successfully BRICKED ur phone..
Daemonjax said:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Click to expand...
Click to collapse
Magnets don't emit electromagnetic radiation -_-;;
A much easier way would just be to take a moderately high dc voltage (say ~48v) and fry part of the processor.
Daemonjax said:
I managed to brick my phone! It was harder than I thought (well, considering my many failed attempts), but here's how I did it:
I downloaded haykuro's 1.33.2005 special spl, renamed it to update.zip, and updated the g1 with it through the recovery panel. It's now permanently stuck at the T-mobile G1 screen. Worked for me, YMMV.
If that didn't work, my next two ideas were:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Hope this helps others in the same boat. I'll update with the bad news if they do, in fact, figure out I had rooted my phone anyways. I'm sure it's possible, yet probably unlikely. Otherwise, no news is good news.
Click to expand...
Click to collapse
You didn't have to hard brick it like that you know. There are other ways which will convince the warranty people just as well. Now it's really bricked.
hmmm well this was my idea....if my phone ever goes wrong or sumthing.... i will just crack the screen lol. so they cant see if what software was on my phone...
the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick
nephron said:
the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick
Click to expand...
Click to collapse
Or if you already have Haykuro's SPL just downgrade your radio hehehe
nephron said:
the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick
Click to expand...
Click to collapse
So if you have the danger/haykuro spl and want to downgrade that spl for w/e reason the phone will brick??? or are you trying to tell him to downgrade the radio?
turboyo said:
So if you have the danger/haykuro spl and want to downgrade that spl for w/e reason the phone will brick??? or are you trying to tell him to downgrade the radio?
Click to expand...
Click to collapse
If you use Haykuro's "Danger SPL" and will try to downgrade the radio, it should brick the phone for good.
Even if your camera button is broken you can still get to fastboot through ADB. Just open an adb shell (doesn't matter if it is recovery or not) and type:
#restart bootloader
and voila - you can get into fastboot mode and flsh whatever you want.
brian_v3ntura said:
hmmm well this was my idea....if my phone ever goes wrong or sumthing.... i will just crack the screen lol. so they cant see if what software was on my phone...
Click to expand...
Click to collapse
thats dumb as hell cuz if u crack ur screen u have to pay $130 deductable well at least in USA and if u send it back with out telling them the screen cracked u get to pay $370 restocking fee but ifd u just brick with spl u get free replacement just pay shipping which im about to do cuz my phone was ****ing up and i got replacement sent(20 bucks shipping thats it) but magically i fixed the phone but its rooted and fully working again so if new phone is PVT board then im bricking my phone and keeping new one.
I need help
Hey people I have a cracked G1 screen and a rooted firmware, I want to get a free warranty replacement by saying that the "Update Failed" and act like a total idiot to the tmobile people..
I also have Haykuro's latest radio and latest SPL, can someone give me clear guaranteed instructions on how to brick my fine cracked friend?
Oh, and I also want to make sure that the TMOBILE people cant go to cyanogens 1.4 Recovery image after this thing is bricked, so AANNY help would be appreciatede
housecat93 said:
Hey people I have a cracked G1 screen and a rooted firmware, I want to get a free warranty replacement by saying that the "Update Failed" and act like a total idiot to the tmobile people..
I also have Haykuro's latest radio and latest SPL, can someone give me clear guaranteed instructions on how to brick my fine cracked friend?
Oh, and I also want to make sure that the TMOBILE people cant go to cyanogens 1.4 Recovery image after this thing is bricked, so AANNY help would be appreciatede
Click to expand...
Click to collapse
Grab the RC29 file, name it DREAIMG.nbh, and flash via the bootloader. Since that will downgrade the radio to the 1.1 version, you will no longer have the 1.5 radio that 1.33.2005 requires
This has got to be the funniest topic I've read in awhile.
Good luck to all you seeking bricked phones. Haha.

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

Custom Rom Advice

I've been lurking in this forum for a while now, and given HTC's "We're not updating the Hero until we've milked the market for every last Desire/Legend upgrade" stance, I've decided to take the plunge and put a custom ROM on my unbranded GSM Hero.
There's just a few questions I wanted to ask before I go ahead, and was hoping some of you would be kind enough to help:
1) If I install a custom ROM, is it possible to go back to factory state? I know some of the FAQ's say its possible to go back to the stock ROM, but does that mean EVERYTHING returns to stock? I know this is apples and oranges but when I flashed a couple of PSP's you have a recovery mode at startup, is anything like this left behind when returning to stock?
2) Is it possible to brick my phone? If so, is it recoverable?
3) Can anyone recommend a fast, stable ROM? I was interested in Damage Control but obviously thats for CDMA Hero's not GSM.
4) I see a lot of people with quite complex issues like radio frequencies and battery problems, what are the odds of having something like that happen? Is it quite rare? Also are radio flashes undone by returning to stock?
Thanks for your time guys, I'll be updating here with my progress/Issues later this evening
Arceon said:
There's just a few questions I wanted to ask before I go ahead, and was hoping some of you would be kind enough to help,.....
Click to expand...
Click to collapse
1) If I install a custom ROM, is it possible to go back to factory state? I know some of the FAQ's say its possible to go back to the stock ROM, but does that mean EVERYTHING returns to stock? I know this is apples and oranges but when I flashed a couple of PSP's you have a recovery mode at startup, is anything like this left behind when returning to stock?
- Yes, you can return back to stock state. You are correct, we do use a 'custom recovery console' to flash custom ROMs but this is easily removed by applying one of the official RUU .exe files found at Official HTC Hero RUU ROM Links. Connect phone to PC, run .exe, DONE!
2) Is it possible to brick my phone? If so, is it recoverable?
- I personally have only heard of people bricking handsets when, (1) Installing CDMA ROMs onto GSM handsets (you already know the difference so this shouldn't be a problem now), (2) Interrupting the radio update process (when applying update, phone may reboot a few times, do not touch untill you get the lockbar to pull down to unlock).
Iv had mine for about 3 months now and started as a complete noob but my phone is still living.
3) Can anyone recommend a fast, stable ROM? I was interested in Damage Control but obviously thats for CDMA Hero's not GSM.
- Im using MCR3.2 since day one, its fast and stable, what more could I ask for (apart from android 2.1).
4) I see a lot of people with quite complex issues like radio frequencies and battery problems, what are the odds of having something like that happen? Is it quite rare? Also are radio flashes undone by returning to stock?
- I assume its quite rare, again, Ive had no issues whatsoever. I dont know if running the RUU .exe will roll back to a previous radio or not but you can manually rollback, just use the radio update.zip first, then run the .exe if you need to.
One thing I would recomend,... Make sure you'v charged your battery 100% via the mains adapter (not usb through PC) when applying the custom ROM.
ruu contains a radio upgrade. or downgrade, depends on what you have installed and what ruu you are attempting to install.
you can brick your hero by flashing either a wrong radio or a wrong spl, or by flashing the correct ones of either and interrupt it during flashing.
if it was recoverable it wouldn't be bricked, the definition of "bricked" is that it serves the same purpose as a brick. however in most cases there is the possibility of reviving it via jtag, which is a highly complicated process that involves opening the phone and manipulating with the components directly (you could say "solder in a new processor" to express it in laymans' terms). so usually not worth the effort.
@ddotpatel
Thanks for clearing all that up for me
One thing though, with the official RUU files you linked, do you always just pick the latest one? Also do I need to worry about the "No Driver" description, or is it just run and done?
@kendong2
What would consitute a "wrong radio"? Are they not region-free? Or do you mean if I install a lower version than the one I already have? Also I guess seeing as I don't know what an SPL is I don't need to worry about it?
As for the Bricked term, yes your right. Its just coming from the PSP scene they use the term bricked to describe when the firmware will no longer boot, but the hacked in recovery console will. Bad habits and all that
I dont think the nodriver thing is anything to worry about.
Check the ROM your currently on through the settings menu so you know which one to go back to should you need to. I suppose it would look odd if you tried to return a handset for repair and it had an older ROM than the one it shipped with.
If you use this link HTC Hero Radio ROM Links you will be fine. They aren't region specific, I just used the latest one.
I think what Kendong meant was to make sure its for the GSM Hero not CDMA.
And SPL is the ROM I think, so again, as long as its GSM you're good to go!
Thanks ddotpatel
One last question, on the Recovery ROM thread linked to in the "Complete Newbie Guide" it says in rather large red writing "This recovery is NOT yet fully compatible with the new apps2sd method!".
Does this mean if I install A2SD as in the newb guide it will cause issues/break?
Arceon said:
Thanks ddotpatel
One last question, on the Recovery ROM thread linked to in the "Complete Newbie Guide" it says in rather large red writing "This recovery is NOT yet fully compatible with the new apps2sd method!".
Does this mean if I install A2SD as in the newb guide it will cause issues/break?
Click to expand...
Click to collapse
No, no,... If you follow the instructions in BTDAG's guide to setup apps2sd all will be ok.
The warning is referring to CM5.0.7 which I think is a HTC Dream / G1 ROM so that doesn't affect us guys.
Oh good, bid red text has a tendancy to put me off somewhat!
I've plumped for SLIDEVILLAIN 1.1.0 RC, and have a shiny new 8GB class 6 card on the way, should help with the craving to upgrade to a new phone for a while
Thanks for all your help, I'm sure you'll see more threads from me in the not to idstant future
Arceon said:
Oh good, bid red text has a tendancy to put me off somewhat!
I've plumped for SLIDEVILLAIN 1.1.0 RC, and have a shiny new 8GB class 6 card on the way, should help with the craving to upgrade to a new phone for a while
Thanks for all your help, I'm sure you'll see more threads from me in the not to idstant future
Click to expand...
Click to collapse
Don't suppose you could send me a link of the memory card you'v ordered,... I think I'm gona start researching prices, speeds etc and get a new one myself.
Best I found so far was an 8gig Class 6 Transcend for £14 off Amazon but it doesn't state read/write speeds so am a bit reluctant.
http://www.amazon.co.uk/Transcend-m...USDHC6/dp/B001IAMME8/ref=cm_cr_pr_product_top
Yeah, Iv had mine 3 months, initially bought as a temp handset to replace my Nokia 5800. Was planning to sell it on again this month and get myself a Desire for my birthday. But you know what,... I'm still really really happy with it. I think I'll be keeping it for another 6 months or so, at least until we get something similar to the HTC Evo 4G or the HTC Incredible in the uk.
I ended up ordering the Samsung one:
Urgh I can't post links, search for "Samsung 8GB Micro SD PLUS memory card Class 6" on Amazon
The read write speeds are in the comments, but to be honest I didn't pay that much attention to them knowing that the class 4 was the recommended speed and that class 6 is 50% faster.
Pretty much the same here, I was happy with it until the boss ordered a Desire and I had to set it up for him. The screen size combined with 2.1 was seriously making me consider one, but I realised if I could just have 2.1 I could hold out another few months.
And yes the Evo is awesome, can't wait for something like that over here, If it doesn't come then I'll be holding out for Froyo instead
SPL is the secondary program loader. Think of it as the bootloader. You don't need to touch it unless you want to replace the initial static bootscreen image.

Holy hell... a lot of work

Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...
Whiterin said:
Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...
Click to expand...
Click to collapse
I guess that I should be moving this to General since this is a Q&A and not a means to simplify what you are trying to accomplish.
Moving to:
Magic General
Discussion about the T-Mobile myTouch 3G, HTC Magic (general Q&A, tips & tricks)
Wow, do I know how you feel.... I recently got a Vibrant (galaxy s). So sine I got a new phone I unrooted my MT3g and sent it in on warranty since it was kinda scratched, so I can give it to my wife. Well with my first phone I was able to do the on click root since it came originally loaded with cupcake.... Well as it turns out if it comes pre loaded with donut you can't downgrade any more...lol So I had to do the gold card method.....it sucked.....
I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.
Whiterin said:
I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.
Click to expand...
Click to collapse
No, its not.... A good example is to root the vibrant you just flash a update.zip file...lol. But the sapphire/magic/mytouch is a great phone with allot of development support. But from what I understand one of the hardest roots..
Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?
Whiterin said:
Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?
Click to expand...
Click to collapse
the CID error tells me your gold card creation failed.
Check the process description at theunlockr.com. that worked for me.
My first mistake was formatting FAT and NOT FAT32. It must be formatted FAT32.
I used a 2GB PNY and it works great.
yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.
Yes, the zeros are critical but as I recall theunlockr link above (paste and cut) takes care of that for you. The gold card is the hard part to get right.. The rest is very straightforward.
Thanks for the input guys. Going to try a few more things.
Alright. Following the instructions. Step by step, I am still getting "CID Incorrect! Update Fail!"
This is very frustrating as there isn't any reason it shouldn't be working...
Darklordzim said:
yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.
Click to expand...
Click to collapse
Not to thread jack, you know you can use any GoldCard with any phone, as long as it was made properly.
Any ideas on why this one isn't working then? Saying "Incorrect CID" when I try to flash anything with it.
Not sure. I know it took me 3 tries to get mine working right.
Sent from my HTC Magic using XDA App

Help: Stuck at the G1 logo screen after flashing SPL

Ive rooted before but im trying to root a friends device...It's been a while since ive rooted mine so I was freshening up how to do it again. I followed the steps all the way to flashing the SPL...My friend was on android 1.6 with build number DMD64. I reverted to RC29 to root and when flashing the SPL...i flashed dangerspl in recovery. I rebooted and now it does not go past the G1 logo...i tried fastboot and boot into recovery but unsuccessful. Is this a brick? I'm really hoping not...any help would be appreciated, thanks.
Did you make certain the radio was up to date? Old radio with danger spl = brick. Sorry. If that's the case, your only option will be JTAG, which is a rather complex procedure.
I could have been certain that the radio was 2.x but not 100%. My friend's phone was at 1.6 before the reverting to rc29. Does reverting rc29 also revert the radio to 1.x?
Deadbolt said:
I could have been certain that the radio was 2.x but not 100%. My friend's phone was at 1.6 before the reverting to rc29. Does reverting rc29 also revert the radio to 1.x?
Click to expand...
Click to collapse
No it shouldnt, can you get into recovery mode? if you can then just flash the rom again and it should work just fine.
As far as I know, DREAIMG.nbh contains ROM, radio, recovery, SPL and splash screens. So yes, I'm 99% percent sure it downgraded your radio.
If that's a case, then you have nice brick.
Why do you ppl still bother with Haykuro? SafeSPL + MTD Partition Hack is the way to go!
raven_raven said:
As far as I know, DREAIMG.nbh contains ROM, radio, recovery, SPL and splash screens. So yes, I'm 99% percent sure it downgraded your radio.
If that's a case, then you have nice brick.
Why do you ppl still bother with Haykuro? SafeSPL + MTD Partition Hack is the way to go!
Click to expand...
Click to collapse
If the dreaimg.nbh file does downgrade the radio then i'm probably sol. It was my fault as I should've gone with the original hardspl before flashing the dangerspl right away. But I didnt think rc29 would downgrade the radio, thought it'd be safe.
Anyone know or know anyone that can do the jtag hack and try to recover the bricked G1? I looked up jtag and it sounds quite complicated to do myself. If anyone can do it, ill even pay a small fee for someone to do it. Thanks.
I have a question about this too. I too find myself in the same situation but i did not try to flash the dangerSPL. I was rooting and after i flashed hard spl and rebooted i got stuck on the G1 screen...I cant load into recovery or normal or even fast boot. Did i really just brick my phone? any help would be cool
Bottom Line....
Out of all the post, no one seems to give a straight answer. HTC G1 frozen on the bootup screen (T..Mobile G1 screen). Can the phone be fixed or NOT? If it can, how is this done? (factory G1)
If you can boot into Recovery (Home + Power) or Fastboot (Camera + Power) you can recover your phone. Otherwise you need to use JTAG, which with the right knowledge can recover just about anything. I'd search craigslist or similar sites for people that offer JTAG services. Every now and then an XDA member might offer it, but that would be in special circumstances, considering that there are a lot of people who might need it done.
funkeee said:
If you can boot into Recovery (Home + Power) or Fastboot (Camera + Power) you can recover your phone. Otherwise you need to use JTAG, which with the right knowledge can recover just about anything. I'd search craigslist or similar sites for people that offer JTAG services. Every now and then an XDA member might offer it, but that would be in special circumstances, considering that there are a lot of people who might need it done.
Click to expand...
Click to collapse
is it possiable for one to purchase said jtag hardware, and run the software on ones computer??
xxcrashxx said:
is it possiable for one to purchase said jtag hardware, and run the software on ones computer??
Click to expand...
Click to collapse
You'll also need to open up the phone and solder wires to the circuit board.

Categories

Resources