Database Develop

my Dream have a big white "G1"

Was updating my G1 and bricked it when I installed the SPL from http://code.google.com/p/sapphire-port-dream/
This had root access before I messed it up.
I've tried all booting methods. Camera and Power, Home Power, etc. and nothing gets me out of the T-Mobile G1 screen.
Please advise if this can be fixed.

congratulations if you cant do anything with those buttons you have now bricked your phone, it makes a nice looking paperweight tho, there is no way to fix what you have done

I REALLY hope you flashed the Radio first like it said so in the instructions... But I guess it doesn't matter now, you are bricked sir =/. I hope you still have the warranty or insurance...?

There is a thread some where on here claimong some type of method to get a new one or something you should look for it n see if it helps u n any way

if you still have a warrenty....say this
"after months of waiting i finally recieved the 1.6 update. but after the phone rebooted it wouldnt start up. i have tried everything the guides on the internet say about how to get it working again and nothing worked. the guides all said that if you cant get to the 'recovery screen' or something like that then you cant fix it..."
wing it along those lines....it works
and next time please post in the correct section - questions go in the QnA section

sidenote - if its a tmobile UK or USA one this will work
if its rogers Canada it wont as there is no 1.6 for rogers dream

did you remember to back it up before you done anything - if so do try the following as this fixed mine when i had that issue
remove and replace battery
boot into recovery mode
use the restore option and restore from backup
if you can get into fastboot then you maybe able to push a new recovery and spl but not sure so you will need to search the forums

as stated, they cant get in, unfortunately

I would say act more innocent than what you say.
Guides, recovery, 1.6 update etc.. would all ring alarm bells for me if I worked for tmobile.
Just say it said something about an update, you clicked ok, it restarted and then wouldnt come back.
Dont mention recoverys, 1.6, guides online etc....

i found that acting intelligent worked better coz 'an intelligent person would never **** up their phone'
and edited version:
"i woke up yesterday and my phone said 'update available' so i hit ok. once it was finished my phone wouldnt turn on - it just got stuck at the G1 screen"

Short Story: GPS didn't work on my G1 so I unrooted for warranty return. After dropping to RC29 my update came and it bricked the phone.
Garok89's statement below is almost verbatum what I told the rep. New phone 3 days later.
garok89 said:
"i woke up yesterday and my phone said 'update available' so i hit ok. once it was finished my phone wouldnt turn on - it just got stuck at the G1 screen"
Click to expand...
Click to collapse

btw.....
i live in Asia....God

well i would try to act dumb first, but then if they start trying to give you hassle, little by little pile on your knowledge of the phone, if you live in asia and cant do anything about it, just make a call to the corporate office and handle it with them, the minute a business this big hears the words "corporate office" im sure they will find a solution for you.

[Q] Galaxy S not booting, black screen!

Firstly, may I apologise, I know this has been covered, I've trawled the internet for hours but just can't seem to get an answer.
I recently updated my UK, unlocked Galaxy S to Froyo via the registry hack, all was fine (ish). Because Froyo had been delayed in the UK and wasn't as great when it was running on my phone I thought it would be safer to revert back to 2.1 and wait until the official UK release came out (I know some will ask me why I did this, I just felt that Froyo was held back for a reason and I couldnt get an answer as to if I could update to the UK version if I already had the Scandinavian one). So I did the reg hack again and was offered 2.1. Everything seemed to go smoothly until the phone rebooted after downloading from Kies. Now the phone's animation starts then the flashing S symbol displays for an extended time. After that, the screen goes black. If I touch the two touchscreen buttons they stay on but do not go off. If I hold the power button the phone turns itself off and when the phone is powered off and I plug it into my PC with a USB, the battery charging sign comes on.
The phone was rooted and I did have the OCLF on but uninstalled that and un-rooted before changing the firmware so it was back to stock.
Before I get 20 people telling me to put the phone in download/recovery mode I must tell you that I can't. My phone has never been able to do it. I've tried every single way and button order suggested. I'm not the only one who's phone won't do it either so it's not just me. The only way I ever saw recovery mode on my phone was when I used the one click root on the PC.
I'm at a total loss. Debugging was turned off because Kies won't let you do anything with it turned on and so ADB recovery is out also.
Please help if you can.
Many thanks,
Ryan

Boot to download mode, do a repartition with Odin and 512 pit flash, remove battery and boot again to download mode and then do a odin firmware flash to which ever firmware you want.

thanks intratech but I can't boot the phone into recovery or download mode (sorry should have stated that). Believe me, I have tried every combination. I did a lot of research and discovered that there are quite a few people for whom that feature was disabled.

if the 3 button combo is not working on your phone, you should not do these risky stuff actually
take a look at this thing
http :/ / forum.xda-developers.com/showthread.php?t=819551
remove spaces

thanks Noobproof. I remember coming across that thread last night. Although I consider myself ok with software, soldering and slicing just isn't my forte. I haven't got a clue about soldering, etc. I've just come back from the Carphone Warehouse (Samsung suggested I go there as they are the service centres listed on the Samsung UK website). The engineer had the phone for half hour and said that the "board was faulty". Haven't got a clue what he meant by that, unless he meant the internal SD which a few people have had go on them. Anywho, he told me to ring Samsung and send it in for a repair. I did that and need to send my phone special delivery to a company called regenersis in Scotland.
I knew rooting and flashing custom roms was a risk, that's why I never touched Odin,etc. I used Kies to upgrade to Froyo and Kies to downgrade back to Eclair. You would think that sticking to official Samsung software would be safe. I must admit, when it was going well I loved my Galaxy but more and more I'm starting to wish I'd opted for the Iphone.It just seems that there have been so many glitches and bugs, I mean, why should there ever be a need for lag fix in the first place? I often found myself keeping my fingers crossed when downloading simple apps as that was usually touch and go!
Feeling a bit deflated now. Was hoping some clever boffin had designed a software solution that would recognise the phone and force it into download/recovery mode.
Ah well, thanks for taking the time to respond anyway.
Best wishes,
Ryan

You know i was very happy when i for the phone for the first time and while i was doing a research (i live in turkey and there is no stock android market here) i came along this forum. And i have learned that i havent got the 3 button combo. I downloaded the 3 button fix abd took the phone to samsung centre.
They told me that they cannot flash it and i made a huge fight then they accepted and i have my 3 buttons. Never give up your phone. I dont think the internal sd is faulty it is just corruppted if you can access the recovery menu you could fix it. Any way you have to find a service centre that has an anyway jig box other a jtag box otherwise they will have to replace the motherboard. Good luck
Sent from my GT-I9000 using XDA App

I had the same problem all i did was use a different firmware .. didnt choose anything in pitfile and did not check on repartition but checked only F reset and Auto reboot and flashed my phone and voila it booted perfectly fine
Hope it helps others with black screen problem after booting
thanks
mike

I had the same problem too. This method really works.
Wysłano z GT-I9000 z użyciem Tapatalk

Phone is Bricked

So, I flashed back to stock and master cleared using Odin. Then I went and did the OTA update from ATT and it said your phone will reboot in 5 secs. Well it turned off, like expected, and never came back on. Now it will not turn on at all. I get no response from anything I do. All button combos that I know of and nothing. I have no clue what happened. The OTA update screwed me phone up. Anyone have any suggestions or do I need to go to a warranty center or ATT store? Thanks.

Wow, this is where search could have helped. OTA was known to brick phones, Mini Kies would have got you to JH7 or designgears CWM zip.
Looks like a replace to me.
Sent from a phone somewhere in the universe

Well, sorry I didn't search for it. I had no idea the OTA bricked phones. I did look at other bricked phones threads before I posted. Anyways, I got my replacement already from local support center. She said it was a new phone but it has just as old of an IMEI number and is a 1007. But I tried out the GPS on the way home and it was absolutely perfect. Makes me think it was a hardware issue because the software is the exact same, of course. Anyways, happy that it works now. Just hoping that it really is a new phone and that the shutdown problem doesn't happen again.

[Q] * Question about a OTA Hard Brick*

Hey All,
I decided to flash back to stock using the odin 3 method. Basically I was planning on getting rid of the phone soon. I cleared everything off the internal "SD" card, wiped all user data and cleared the cache. Booted back into the stock OS, everything looked fine. Checked the internal card again and it had written some new files. I assume these are just operating files for the stock OS.
So I power down the device correctly, pull the battery and install the sim card and 8 gig flash micro sd card. The micro card is completely clear. I boot the phone back up with no issue, it hits the network with no issues. I start looking though all the bloatware and go back into setting and turn the USB setting from Kies to USB storage. Then a get an odd alert telling me an update for my phone is available. So, I figure a stock update couldn’t hurt and let it download and install. It downloads to 100%, and advises it needs to reboot to install the update... Ok, so I let it... the screen come back with a progress bar and not much else. At 50% the progress bar stops and a message telling me the update has failed pops up... The phone then shuts off.......
Bricked..... I mean bricked bricked. 3-button doesn’t work, Jig doesn’t work. the 3 button battery pull doesn’t work. 2 button while putting in the usb cable with odin loaded doesn’t work. 3 button with battery out, usb in and then put the battery in doesn’t work.. This thing is dead....
Now my question....LOL... since I had cleared out any and all data, will AT&T give me crap saying I voided the warranty by flashing my phone?
Do they look at what’s stored in ROM? Because before the phone died I had flashed it to stock... I know how to call XBM (their exchange program) and I know they will send me out a refurb phone, to questions asked. But my concern comes in when I ship them back my device and start snooping around... what are they looking for? No liquid or physical damage. Normally I don’t try to get one over on the man, but it was their crappy update that bricked the phone, not my tampering….
any thoughts or experience with this matter?

Did you flash back to JF6 or something? That OTA was probably the busted JH2 they pushed out to all our devices last year, resulting in tons and tons of bricks. They shouldn't give you any crap over it - it was their own fault that your device got damaged - and if you flashed everything back to stock and formatted the internal SD, then technically your phone WAS at factory defaults, so they wouldn't be able to tell what you've been doing with it prior to that anyway.
Edit:
Also, if ATT gives you **** over it, mail it to Samsung. Tell them you were on eclair, got an OTA notification and it bricked your device. They'll ask you to mail it in without the battery and back cover, and swap the board for you. Takes about a week, but whatever.. beats having to deal with some dumbass ATT rep.

this is just good to know....dont flash to stock and try an OTA update.

This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.

jack man said:
This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.
Click to expand...
Click to collapse
Well I thought they do like a jtag, or am I wrong?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

nope, no JTAG, just a new motherboard

Brand New SGH-I537 Spontaneously Bricked After 6-10-2014 Update

I have a brand new S4 Active-aout 2 weeks old. Not rooted, only a few apps installed. Phone was working after update for a few hours anyway. Pulled it out of my pocket to make a call and it was dead. No screen, no sounds. I thought maybe the battery somehow drained out all of a sudden. I popped in a back up battery, still dead can't get any boot sounds or screen flashes.
Plugging into laptop, the phone is recognized as a QHSUSB_DLOAD but missing drivers. Downloading Kies now to see if that resolves it. ANyone have any similar issues or experiences with QHUSB?
Just wanted to post this as I had heard the last AT&T update, the NC9 which my phone had, was pulled because of issues...well maybe this one has issues too. I've had other S4 Actives that were rooted, but this was a brand new retail phone.

posted help request for you here:
http://forum.xda-developers.com/showthread.php?p=53776819

ChristopherXDA said:
I have a brand new S4 Active-aout 2 weeks old. Not rooted, only a few apps installed. Phone was working after update for a few hours anyway. Pulled it out of my pocket to make a call and it was dead. No screen, no sounds. I thought maybe the battery somehow drained out all of a sudden. I popped in a back up battery, still dead can't get any boot sounds or screen flashes.
Plugging into laptop, the phone is recognized as a QHSUSB_DLOAD but missing drivers. Downloading Kies now to see if that resolves it. ANyone have any similar issues or experiences with QHUSB?
Just wanted to post this as I had heard the last AT&T update, the NC9 which my phone had, was pulled because of issues...well maybe this one has issues too. I've had other S4 Actives that were rooted, but this was a brand new retail phone.
Click to expand...
Click to collapse
Any luck on fixing this? My GT-I9295 just did the exact same thing today. Using it at lunch time, no problem. Chucked it in the top pocket of my overalls and went back to work. Grabbed it out again at afternoon tea and nothing. I've tried pulling the battery and waiting a minute, tried different key combinations and nothing. Plugged it into the computer and good old QHSUSB_DLOAD pops up, which led me to this post. I havent rooted the phone or anything, downloaded the update a month or two ago and its just done this
I did read on another forum that QHSUSB_DLOAD stands for Qualcomm High Speed USB Download, which basically equates to the phone being a fresh bit of silicon from the factory waiting to have all its software loaded onto it. Anyone else able to confirm this?