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.
Related
Any ideas?
I tried to flash a new SPL.. probably a stupid idea on my part, and it loops at the G1 screen.
I was going to install the SPL, then install SuperHero v2
I press power+home to go to recovery, and it does nothing. I try to access bootloader, and it does nothing.
Is it officially bricked?
is the phone plugged in when you are trying to do this?
if not, then try reflashing your rom.
mrcrs said:
is the phone plugged in when you are trying to do this?
if not, then try reflashing your rom.
Click to expand...
Click to collapse
Well I can't boot into recovery mode =/
So I can't reflash a rom
It just stays at the G1 screen
Did you verify if you had a pvt board or not?
can you get into bootloader mode?
I did verify, and it had a compatible board. I believe it was PVT, but atm I'm pretty pissed that I can't remember. I just know for fact it was compatible, otherwise I wouldn't of even thought of going through the process.
To recap:
I cannot get into bootloader.
I cannot get into recovery mode.
It stalls on the G1 screen. It apparently is stuck in a loop.
I can get to the blue LED thing though. (Which apparently is worthless)
This is lame. (I'm an idiot)
Unless some miracle can happen, which I am very much hoping, I am going to declare it bricked.
Which means I'll have to either use my lame iPhone, or ditch out $200 for a new G1.
okay i'm sure you did this already but i gotta ask, did you try removing the battery for a few seconds then try booting into recovery?
Sooooooo....
You had a compatible board, but did you think to update to the latest Radio....?
If you didn't have the latest radio then that's what bricked your phone..
If you did then your phone shouldn't be bricked......
Did you have the latest Radio?
mrcrs said:
okay i'm sure you did this already but i gotta ask, did you try removing the battery for a few seconds then try booting into recovery?
Click to expand...
Click to collapse
Yeah, and no avail
I think I'll just remove the battery for the rest of the day, and pray that somehow it'll fix. lol
imnothimm said:
You had a compatible board, but did you think to update to the latest Radio....?
If you didn't have the latest radio then that's what bricked your phone..
If you did then your phone shouldn't be bricked......
Did you have the latest Radio?
Click to expand...
Click to collapse
Ah!
Found the culprit. You see, there aren't any guides that I could find that properly told me which order to do it, and how.
I thought it was SPL, then Radio, then ROM. But it's actually Radio, SPL, then ROM.
Well then I do have a brick. My first brick, woo.
Yup
Your Phone is indeed bricked...
HTC will repair it for 150...
Sounds like your only option
so if it was the saphirre or H's special spl you tried to flash but didn't upgrade the radio, then yeah... you most likely got a brick.
but what makes me wonder is that when i flashed H's special spl, i ran into the constant relooping of the g1 splash but i was still able to get into recovery mode. so i just reflashed my rom, and all was gravy.
They really will? Because $150 is $50 cheaper than I can get a new G1 (from craigslist)
But, if it's still a new phone, does it come with a 1year warranty from T-Mobile?
I know on my AT&T Tilt, at one point I messed it up, and they have a Warranty store locally, and I took it in and they tried to fix it but they couldn't, so they replaced it. Does T-Mobile have one of these anywhere?
hmmm
I sent mine into T-mobile and they replaced it for free, although I'm about 98%sure you need to have an account with T-Mobile for them to do that...
I'm pretty sure HTC is your best bet atm
Though I do have a t-mobile account. My mom and dad are with t-mobile, and I am with at&t.
if you are with tmo, then just call them.
Alright well I'll give them a call.
Maybe they will be nice
Well this sucks lol.
T-Mobile wont replace the phone because it's not purchased by me. It was purchased by someone locally on craigslist. So I would have to get in contact with that person and have them get me an exchange.
Yet another reason why I dislike T-Mobile. AT&T will just verify the IEMI, and if it shows that it's less than a year, or still under warranty, they will replace it.
I guess there's no failsafe way of fixing the G1, even after you messed up the first way to fix it?
I know in GPS navigators and stuff like that have their own failsafe mode to fix a brick. Then will force itself to connect to a computer so you can edit the whole filesystem.
Or a way to replace the system.. aka JTAG.
Recovery mode has to be accessed after a bootup. How stupid
I got my magic and bricked it today.Any thoughts to unbrick i am crying please somebody help. i cant face my parents or any person at my place.
advise on what u did before it got rooted..
step by step
I followed the mytouch guide and saw my device was 32b and went ahead for 32b (dont know if it was necesarry) and applied radio as update and i am fked up. fk me
charnsingh_online said:
I followed the mytouch guide and saw my device was 32b and went ahead for 32b (dont know if it was necesarry) and applied radio as update and i am fked up. fk me
Click to expand...
Click to collapse
The same thing happened to me. I completely bricked it. Couldn't get into fastboot. Phone wouldn't even turn on, computer wouldn't recognize it, LED's would not come on when plugged into charger or phone. It was that bad. I just went to the T-Mobile store and said that it got like that over night when I left it charging. They sent me a new one under buyer's remorse. It worked out great for me. As for how it did it, I did it the same exact way you did. When applying the 32B radio I didn't flash the radio right. Idk if you read Amon_Ra's guide on how to root it. He didn't specify at first how to flash the radio so when guessing I broke it. Then a few hours later he then posted how to flash it. Just my luck! But I now have a new mytouch and when I followed his directions exactly for the 32B, it went off like a charm. 32B is necessary if you are going to run Hero roms because it is expecting the extra RAM to push it harder. Not so sure about Non-Hero Roms but I believe it might be the same thing. If your phone is as bad as mine, just use the same excuse. They will think it is a defective handset and send you a brand new one, not a refurb. I tried everything to get back into fastboot but I couldn't get the damn thing to start up. It was a sad day. We now have 3 rooted myTouch's that are working great. Hope this helps.
try removing battery for 1 hr and power it up again
You should PM that bloke who's got "have a problem with Android? PM me" in his sigfile. I'm sure he'll fix you right up.
(sorry mate, I couldn't resist! )
Loccy said:
You should PM that bloke who's got "have a problem with Android? PM me" in his sigfile. I'm sure he'll fix you right up.
(sorry mate, I couldn't resist! )
Click to expand...
Click to collapse
haha how ironic
if you have insurance on the phone...smash it and send it back. make sure the mobo is broken though and not just the screen. if not, well...sorry to hear about your new paper weight.
trying my hardest not to flame here, but.....
specify the guide you followed... a link to it would be a good start
state exactly what steps you did
state what conditions have occured (eg. stuck on logo, wont even power, etc)
state the actions you have taken to try to repair (sometimes you can make things worse but at least we'd know what you've done)
it's rather inconsiderate to not take the time to post these essential points.
you are expecting us to spend more time thinking and explaining your problem then you have bothered. not cool.
i concur..i try my best not to flame people, but in some situations, such as this one, a flame is appropriate....
i have bricked my HTC Magic while i was trying to flash this ROM (http://forum.xda-developers.com/showthread.php?t=549591)
but i guess i missed/skipped and had the wrong radio, so then after that all i get is a HTC Magic boot up screen and nothing else.
non of the button combinations work, i cant get to fastboot or recovery using the buttons.
is there anything i can do? any suggestions?!
P.S I DO have a Nandroid Backup (if that can help)
zidane said:
i have bricked my HTC Magic while i was trying to flash this ROM (http://forum.xda-developers.com/showthread.php?t=549591)
but i guess i missed/skipped and had the wrong radio, so then after that all i get is a HTC Magic boot up screen and nothing else.
non of the button combinations work, i cant get to fastboot or recovery using the buttons.
is there anything i can do? any suggestions?!
P.S I DO have a Nandroid Backup (if that can help)
Click to expand...
Click to collapse
Nandroid backups are useless unless you can get into recovery, or perhaps fastboot through a PC. But if you're bricked like these guys...then that's not possible.
korndub said:
i concur..i try my best not to flame people, but in some situations, such as this one, a flame is appropriate....
Click to expand...
Click to collapse
I don't think a flame is necessarily appropriate... Obviously the guy is distraught and doesn't know what else to do and is looking for support - not the time to get on him for not following the right protocol.
I understand your frustration, but try to understand his as well... if you don't want to help, then just let it go - somone else most likely will.
I bricked in the first hour, just think how i feel looking at the phone. $600 for a phonedummy
you gonna tell us what you did to brick it? what radio you applied? What methods you used?
ok now that you say my nandroid is useless
is there anything else i can do to get my phone working again?
if you replaced battery you cant relsoved becoz phone bricked is bricked
farbird said:
try removing battery for 1 hr and power it up again
Click to expand...
Click to collapse
if you replaced battery you cant relsoved becoz phone bricked is bricked
Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Ok, here's what you did wrong:
The first steps are good... You've installed the 1.6 update, then applyed the cyanogen rom... After that I've seen that it was installed a new radio... That might have killed your phone...
At least that appears to be the problem... But why a new radio was installed, no idea... (I don't think you did it on purpose)...
the phone you have there is a magic not a dream.For a start that dosnt help!! Other than that i think yiou have put Dream radio on the device, It not being a dream is the problem as when it detects its the wrong radio the phone goes into a safe mode where it wont turn on to save breaking it.
HTC might fix it under warranty as they did me but it WILL come back with perfect spl on.I have flashed the wrong radio on 2 phones yes 2! now i learn from my mistakes Oh and when/if it gets fixed and you bypass perfect spl, You cant put any ROM Other than donut based ones so no hero takes the fun out of flashing
All bricks I've seen are because you guys install new( in most cases wrong radio- from different phone or MotherBoard version) or changing SPL (exception: people with perfect SPL). I'm asking WHY you do this , WHAT FOR ? Putting different rom /rooting etc does NOT require changing anything and is simple as bread and butter, and you CAN'T damage the phone !! Sorry to see this I'm not 100% sure but it looks like you have flashed with wrong radio. As my predecessor said I think only HTC can fix it... To all people DO NOT TOUCH SPL AND RADIO IF YOU JUST WANT TO PUT HERO ROM OR ROOT THE PHONE (exception ppl with perfect SPL)
i accidently flashed the radio for ION on my 32A last week. got my phone fixed under warranty thank god. but i got the perfected SPL.
if you do get the perfected SPL, you dont really need to change your SPL to flash stuff on your phone.
just replace your recovery using the recovery flasher apk a.k.a the one click root.
reboot to recovery, flash a new ROM that is rooted.
then using the adb shell method, flash a new recovery permanently to your phone.
i have had no issues using that method since i got my perfected SPL.
whalesalad said:
Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Click to expand...
Click to collapse
after applying the 4.1.999 update you pressed the trackball to reboot your suppose to hold the home key while its rebooting on that step till the mytouch screen shows up also you need to wipe the ext. redo the last step then the my3g should be fine in other words reflash the cyanogen
u install wrong recovery
Install instructions for an HTC Magic (32B ONLY!!!)/ION/MyTouch3G
Same as above if you are using CM-Recovery 1.4.
OR
Same as above EXCEPT step 2
Download HTC ADP 1.6 DRC83 http://www.androidspin.com/downloads...ooted_base.zip
*You have to manually reboot MT3G and hold home.
he can use the ra recovery image it works because i used it on mine
Turns out I used the wrong recovery image before doing the cyanogen flash.
I followed this guide on my second phone (swapped out my old white one for a black mytouch) and am running 4.1.999 right now - http://forum.xda-developers.com/showpost.php?p=4666075&postcount=282
Ok so here's the problem...
I was able to root my Rogers Dream but then I messed up with trying to partition the sd card. It was then that it would not go past the rogers screen. After A LOT of reading I downloaded what I thought would the files I need to simply restore the phone to factory. Long story short, if I just turn the phone on it sits at the Rogers screen, I no longer have recovery mode and my fast boot goes to a RGBW screen with Serial0.
Also on the FastBoot screen it states:
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.2.19.26I
I really just want to return the phone to the state it was before rooting it (store bought state). But because I can't access the fastboot through USB or even get to the Engineering SPL I'm really..really stuck!!
If I can get the proper FastBoot loaded somehow I think I can restore the rest.
Any help would be greatly appreciated.
no it is not bricked, try removing the sdcard
Still nothing.
Also if I press Home+Power or Camera+Power it still ends up at the same RGBW screen.
No, it isn't bricked
You are stuck at the stock SPL. I'm not sure about rogers but for tmobile you would want to put dreaimg.nbh on the root your SD card, load up the SPL. Flash dreaimg.nbh. Then it should boot into rc29 (I believe). Get root access, flash whatever flavor of recovery you want. Then boot into recovery and flash whatever SPL you want. Then you can get back into the SPL and restore whatever nandroid backup you had.
Again, this is what I would do on tmobile. Not sure about rogers, but I would assume since you would be loading your own backup everything will be peachy.
Ya I hear what you're saying. The problem is I can't seem to find an original Rogers DREAIMG.nbh file anywhere. I think I might be SOL and have to take into Rogers to get it fixed. I'm just not sure if I've voided the warranty or not.
I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.
try here >>>>>> http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream/Magic32B_Firmware_to_CyanogenMod
dl the rc7 for europe and see if the fastboot recs it. if not try and find the system.img for rogers and ill tell you how to flash it via fastboot. if you had the system img it would already be good. no use of the nbh. also what is dif from dream and g1 besides apns and a small other few things?? if nothing then why not flash the g1 dreamimg?? once thats good then root and get it finalized? just wondering.
EDIT: I searched more for you. dont try my idea. im kinda dumb lol. i forgot that rogers and tmobile have dif boards. so this wont work and might brick you. so dont listen to me. sorry for missleading. im use to g1's in the usa sorry. ill keep searching for anything for you thou.
EDIT2: in fastboot can you >>>>> fastboot boot "name_of_your_recovery.img" ???
try that in fastboot to see if you can get into recovery. if you have no idea what i mean let me know so i can give some sdk instructions.
Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.
losingmyself said:
I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.
Click to expand...
Click to collapse
I know! I can't believe out of every bit of information on how to root an Android phone there is basically nothing on how to fix it. At least for anyone using Rogers.
DO what I did, I had the same issue (T-mo) I used a micro Sd "converter" if you will...........and plugged it into my laptop's SD reader, copied the files over, and VIOLA!
I actually thought I bricked it 5 times.
TinBasher77 said:
Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.
Click to expand...
Click to collapse
I think you've misunderstood.. fastboot mode on the phone enables you to use the fastboot program on your pc to send commands. You can use it to boot a recovery image and flash the files you need to fix this. There's a sticky thread detailing how to set up and use fastboot in Q&A.
Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.
TinBasher77 said:
Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.
Click to expand...
Click to collapse
there is no rogers dreaimg.nbh
Hi,
How did you root your phone?
can you still boot into the recovery img? (home+power)
If you cant, try get back the recovery img (e.g. cm-recovery-1.4.img) and then home+power again. From there you should be able to update your spl to hardspl
Unfortunately I can't boot into fastboot any longer I just get the red/green/blue/white screen. This happens with both Home+Power or Camera+Power so I can't even use adb to force the images onto the phone.
Thanks for the help though.
Well problem solved (sort of).
I contacted Rogers and they're going to send me out a new phone and have me return the "defective" one.
Thanks for all your help and suggestions.
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.