i tryed to flash a new radio (rogers_radio_3.22.26.17_update.zip) and after it restarted my phone, my phone wont get past the g1 boot screen iv left it running for over an hour now and still no luck iv turning off the phone and holding home and the power button, but that doesnt work...
can anyone help ? or is my g1 bricked ?
If none of the button combos work, your bricked.
*houston, we have a brick*
yep i have a nice new paper weight
blackcell1 said:
yep i have a nice new paper weight
Click to expand...
Click to collapse
That's what happens when you don't do research.
Have you tried camera and power? Menu and Power?
Bricked!
Did you call HTC and find out if it is under warranty still? If its not you can always get a rough G1 that boots and swap out your motherboard. I hope you get it fixed. I know exactly how you feel because I bricked a Rogers Dream when I flashed the G1 radio. I have a G1 on eBay right now if your interested.
Was this because his spl wasnt compatible with the radio he flashed???
I bricked an HTC Magic. When I got it I couldn't wait to upgrade the firmware. Followed all the instructions, upgraded spl, radio hboot etc. but it started giving strange errors and refused to recognize the sd card from recovery. Eventually it refused to boot. Bricked in less that 24 hrs!
It's so damn easy to brick these android phones! I wish they were as easy to flash as WM.
Have tried flashing a proper RUU to see if it will even recognize the phone? It's worth a shot even though you can't access the recovery menu or fastboot. Since it turns on you may have some luck.
vwauditech said:
Did you call HTC and find out if it is under warranty still? If its not you can always get a rough G1 that boots and swap out your motherboard. I hope you get it fixed. I know exactly how you feel because I bricked a Rogers Dream when I flashed the G1 radio. I have a G1 on eBay right now if your interested.
Click to expand...
Click to collapse
No G1 is under warranty any more from HTC, the manufacturer warranty expired I believe.
Related
Well I guess I bricked mine ulness someone knows something I don't. I was doing a flash, running nothing else and XP did a memory dump and blue screen of death while 8125 was 54% done. Guess I have a paperweight now.
I am sure I'll get flamed for my post but thank God the Cingular ROM doesn't need an actual Active Sync connection. As long as you are in RBG bootloader screen and the USB comes on when you plug into the PPC, the factory ROM can repair the unit.
Possible Reviving Techniques For (appeared to be) bricked Wizard
See the following link and read, read, read.
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
Very good I do remember reading that post from when I first joined here, guess I just panicked. I must mention however that none of the WM6 ROMS i have would flash only the stock one would.
When you have a bad flash you ALWAYS should go back to an official rom. This will guarentee that you get back to a complete IPL/SPL and Extended ROM. If a flash goes bad, any (and all of them) could be corrupted and flashing a custom rom won't help (since most all of the custom roms don't include any of those pieces).
n3rxs said:
Well I guess I bricked mine ulness someone knows something I don't. I was doing a flash, running nothing else and XP did a memory dump and blue screen of death while 8125 was 54% done. Guess I have a paperweight now.
Click to expand...
Click to collapse
Reboot your pc....
Your device should be in bootloader mode still
Connect and flash the same ROM....it should pick up right where it left off
If this doesn't work, flash your factory rom
As long as your device powers up....it's not bricked
The same thing happened to me once on my wife's laptop
Yeah this was on my company laptop. I was flashing Faria's RealThing for the 1 hundredth time.
Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.
*Saved for future posts*
Edit:
Thanks! Updated.
I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha
it's possible you flashed the radio prior to the SPL, only a loooong ways back.
Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .
Duplicate post...
thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.
youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...
youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?
I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).
digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?
not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info
bump
hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz
You aren't going to get any help with sentences that atrocious. Can you be more clear?
My brother bricked his BRAND NEW Fender mytouch3g.. apparently, he tried the Sapphire hack and it will start up and go to the HTC MAGIC screen.. but doesnt go anywhere else...
He tried to boot into recovery mode.. and its the same..
i would look for the sappimg and boot into hboot holding volume down and power at same time....place file root of sdcard
will that put it back to its normal state?? and where do i find the 'sappimg' ?
Perhaps this thread would be of help:
http://forum.xda-developers.com/showthread.php?t=622530
mayormullet said:
Perhaps this thread would be of help:
http://forum.xda-developers.com/showthread.php?t=622530
Click to expand...
Click to collapse
NOO. lol.. Dont send him there. Because if he already has no idea what hes doing then I have to listen to it.
Try to get into fastboot or recovery. If you dont know how to do this STOP MESSING WITH IT.
I cannot understand how people can buy things without any research for what they want to do with it.
If you didnt make a goldcard, then right there you didnt get anywhere on the phone. If you didnt use the FIXed spl rom I said to use on the goldcard you didnt make, then you really didnt get anywhere.
But if you see an HTC magic screen rather then the Fender mytouch screen I assume you got at least that far.
Hold volume down and power and ses if you get a white screen with 3 androids on bottom. From there we can fix it.
but you didnt read my thread on the fact that ONLY the stock everything wil
I Have the same problem!
Am I covered by guarantee if i will not solve the problem?
As done some weeks ago for the G1 now there is a success in de-bricking a Magic 32A
http://forum.xda-developers.com/showpost.php?p=6260574&postcount=510
Cheers,
bart99
woow! great job! cheers ; ))
Very good news, congrats bart99 and ezterry for de-bricking both Dream and Magic
could it be a way to break Perfect SPL?
sychie said:
could it be a way to break Perfect SPL?
Click to expand...
Click to collapse
That was the first thing i tought when started to read this thread!!! Hope so!
yes it should work, with jtag its possible to load a different spl to ram and then execute it
for mor info post on the other topic, ezterry did something similiar
bart99
Wow you guys are actually considering doing this to a functioning magic just to get root? daredevils
Anyway, great work!
Well if the goldcard method is not working for someone, this could be their solution(if they have enough knowledge of course ).
eyegor said:
Wow you guys are actually considering doing this to a functioning magic just to get root? daredevils !
Click to expand...
Click to collapse
and here I have jtaged other peoples working dreams to give them root
not yet tried a magic.. but will likely in the near future
I like to send my MyTouch Fender to someone to have it unbrick it; If anyone can please let me know. I live in the US but can mail it anywhere.
ezterry said:
and here I have jtaged other peoples working dreams to give them root
not yet tried a magic.. but will likely in the near future
Click to expand...
Click to collapse
i would love to try it on the htc magic 32A.
cmarti said:
I like to send my MyTouch Fender to someone to have it unbrick it; If anyone can please let me know. I live in the US but can mail it anywhere.
Click to expand...
Click to collapse
lol. be careful with that. you might not get it back.
anyways, i'd be scared to try this. it seems like a few things could go wrong and you might just end up being out of one phone. probably need REAL steady hands.
r3s-rt said:
lol. be careful with that. you might not get it back.
Click to expand...
Click to collapse
heh
It is also assuming (seems likely but I don't think we can promise it) that the fender has the same jtag ports as the 32a/32b phones..
Also since there is so much problems rooting these things.. (And even the root now seems to be with the original kernel only) what will happen when it meets my jtag hack?
basically:
* If you are lucky it will just become a 32a/EBI1 w/ headphones.. [no I don't think I see a problem with that]
* a bit less lucky it will become a 32a/EBI1 w/ useless headphone jack
* even less lucky whomever is rooting it gets to chase down the fender firmware to make it go.. and additional radio hacks
* and unlucky damages a trace removing glue from the magics main board. (the rogers magic 32a has some brown epoxy that is hard as a rock filling the gap between the processor and ground shield over the jtag points.)
r3s-rt said:
lol. be careful with that. you might not get it back.
anyways, i'd be scared to try this. it seems like a few things could go wrong and you might just end up being out of one phone. probably need REAL steady hands.
Click to expand...
Click to collapse
Honestly I don't mind if it gets lost, It's paper weight anyway now...
cmarti said:
Honestly I don't mind if it gets lost, It's paper weight anyway now...
Click to expand...
Click to collapse
Same situation here as well. I'd love for someone to help me unbrick - it just goes straight to trying to update the radio but then the screen fades out and it hangs. Sigh.
Tereno said:
Same situation here as well. I'd love for someone to help me unbrick - it just goes straight to trying to update the radio but then the screen fades out and it hangs. Sigh.
Click to expand...
Click to collapse
So via some experimenting on my JTAGed dream I think I understand where the issue some people are having with the radio flashes on the 6.x radio.
When you flash a radio the SPL loads the radio image file into ram and calls a 'radata' command in the radio bootloader. The exact location and size are passed to the radata function.
* The 1.33.* SPLs load the radio image this near 0x103B5300;
* The 1.76.2007 SPL loads the radio image near 0x19500000
This major change in memory location appears to be important. The 6.x radio will loop forever validating the image when it is loaded at the lower memory address.. while flashes as usual at the higher address.
This means if you still have 1.33.2010 installed and flash a radio it will fail.
Flashing via fastboot this will get stuck (maybe fade the screen) until you pull the battery/usb; then boot the device as normal.
However if you do this via recovery: recovery will set the SPL boot mode to flash the radio from cache; and since the radio flash fails to ever return this setting is never cleared. Thus every time you boot the radio attempts and fails to flash.
(This appears to be many peoples problems if you really have 1.76.2007 and stuck in radio flash mode [boot mode 4] my guess is the radio.img has some bit errors or newly formed bad block in /cache.. causing the signature check to fail [despite the radio.img being validated when the zip file was opened via recovery].. I have seen this on one Dream I de-bricked)
-------
PS: the 6x radio is a no go on the dream.. blue light mode goes.. and with some prodding via JTAG I can softboot a SPL or re-flash a 3x or 2x radio.. but that is about the extent of what appears to work.
anyone willing to give my tmobile mytouch 3g a shot?
Not sure the radio/spl that is on it now since its bricked only get splash screen
But when I got the phone it was
spl: 1.33.06 30000
26i
willing to send it to anyone
Press and hold volume down and press Power. Can you get into fastboot? If so, you're not bricked.
Me too Success unbrick my touch 3g 1.2
Ezterry you are genius, as i follow your guide,with a lot of pain process,trial and error, i built my own JTAG wiggler interface and with a little mods.
everything has working..Good Job Ezterry..
now i can smile .
good job brother
bart9984 said:
As done some weeks ago for the G1 now there is a success in de-bricking a Magic 32A
http://forum.xda-developers.com/showpost.php?p=6260574&postcount=510
Cheers,
bart99
Click to expand...
Click to collapse
I am success too with Tvalls Mytouch 3 g..but cant send it back ,cause shipping so expensive here in Indonesia,,
Really sorry
I flashed a new htc touch pro 2 verizon with hardspl, and it was fine - rebooted happily and was fully functional. Then I flashed it with a ROM, and it doesn't boot further than htc logo. I can load a menu with choices to go back to original settings, etc. but nothing can reverse a damage. I tried flashing it from sd card with whatever ROMs - it didn't help. From what I read as long as you use right spl, a phone is not a total brick, but it looks like it is. Any advice is appreciated.
Thanks!
PS. In case you are wandering which ROM killed it: it was an unofficial russian version. I tested it on my t-mobile htc, and it was functional. Then I reversed back to energy rom. I bought htc verizon for my dad, but he asked me to flash it with a russian rom. It didn't go well as you see.
Gorlum_ said:
I flashed a new htc touch pro 2 verizon with hardspl, and it was fine - rebooted happily and was fully functional. Then I flashed it with a ROM, and it doesn't boot further than htc logo. I can load a menu with choices to go back to original settings, etc. but nothing can reverse a damage. I tried flashing it from sd card with whatever ROMs - it didn't help. From what I read as long as you use right spl, a phone is not a total brick, but it looks like it is. Any advice is appreciated.
Thanks!
PS. In case you are wandering which ROM killed it: it was an unofficial russian version. I tested it on my t-mobile htc, and it was functional. Then I reversed back to energy rom. I bought htc verizon for my dad, but he asked me to flash it with a russian rom. It didn't go well as you see.
Click to expand...
Click to collapse
well i dont think it is considered a "brick" unless it wont boot, thats where the term brick or paper weight came from (because thats all it can be used for lol). so with it still starting up, i think there is still hope for you and your device. first off, did u SD flash it in the first place, or is that you attempt at fixing it? cause i think u just got a bad flash. so if you havent tried it, i would try and do it the original way. worth a shot
try finding someone who has a modified version of task29, basically that should take the "bad" rom off of it and only have the boot screen.. i think its an option needing looking into.. hopefully it will work for you.
are you sure its a cdma rom? or else ur phone wont go past boot...check the sticky for cdma roms