Database Users

Broken screen - how do I reflash back to OTA keys?

Title pretty much says it all... I don't want to send a rooted phone back and I have about a week before I have to return the old phone to figure it out.
Any ideas? I'd really appreciate it.

http://forum.xda-developers.com/showpost.php?p=3280729&postcount=3
search is hard

You missed the part about the screen that displays no picture.
Doesn't matter, I think I wiped the phone and rebooted during the reflash.

Download the DREAIMG.nbh file and put it on the sd card. Boot up your phone by holding the camera button and power button. The phone will find the file and verify it i think. Then you need to press the power button to initiate the flash. Once its done you need to press the action button(depress the trackball) that either reboots the phone or just finishes the process. Might need to pull the battery to reboot.
Since you cant see anything on the screen Id give it 30 mins for each section, power it up, wait 30 mins, hit power button, wait 30 mins, hit action key, wait... etc.

i had my tmo g1 home and back button key broken but my other button worked, it was a rooted custom theme called 611(customer care) and they said i still had my warrenty. had the phone for 2 weeks took it to tmo and they gave me a new one.. no question asked.. this happened 2 days ago

SoftBricked Tmobile UK G1 ?

Firstly i would like to say hello and happy new year.
Now to the point,
Yesterday I dropped my phone in the snow and it got a bit wet
I assumed it would be ok.
Few mins after this a received a call and couldn't hear the caller so i suspected that there was water in the receiver so i took my phone apart and tried to dry it out (even though i couldn't see any water in it)
The thing is when i put the phone back together it came to the bootloader and said no image file on a gray screen
I assumed that it was looking for a Dreaimg.nbh file
I put one on my sdcard and attempted to recover the device.
This looked to have worked initially but when i restarted the phone i was presented with a bootloader screen again with the red, green and blue bands saying "serial0".
I assumed that the device was looking for a ROM and couldn't find it so it took me back to the bootloader.
I went online and downloaded a rc8 update.zip
I restarted the phone again and went in to recovery mode (where you update with the update.zip) pressed "alt+l" then Alt+w and then alt+s to flash with my latest update. and tried to reflash the phone from recovery by pressing Alt+s this seemed to work initially but failed after the 2nd restart the process went like this.
Turn on phone press home key
I get a triangle ! and a phone so pressed Alt+l (to bring up the options)
pressed Alt+w to wipe the phone
pressed Alt+s to apply the update.zip
waited,
phone said it was done and press Home+back to reboot.
when i pressed Home+Back before the phone rebooted a message came up saying that it was flashing the radio (is this normal)
Phone rebooted to the G1 screen ]
Then on to a screen with the Microchip on it with a yellow and orange arrow stayed on there for a while and then rebooted again to the g1 screen then on to a screen with a status bar and a package with an arrow within a second the phone reboots and we go back to the bootloader.
This is all my phone will do
Please can some one help me with this I am an IT professional but this has me beat.
Thanks in advance Emove

I am stuck with the same issue. This happened a day after i split some soda on keyboard.
The G1 is auto powering in fastboot mode even though the camera button isnt stuck.
Sometimes I manage to turn on the phone it works fine until it has the problem again and it drains the battery.

Mine in other respects is fine I was hopeing that my problem was fixable but no one has replied with any real comments that may help so i suspect that that no one knows what the problem is.
I would suspect that you have a short somewhere on the board. Soft drinks leave a residue on the PCB when they dry so maybe thats your problem.
your options are to deal with it as it is.. have it cleaned professionaly (t-mobile/htc) or if your brave/stupid like me try and service it your self. cleaning with alcohol should do it no harm if its already on its way out.
i do have the service manual if you need it.

help i9000 after flash, doing loop of at&t logo, can not enter download mode,

help i9000 after flash, doing loop of at&t logo, can not enter download mode,
when plugged in screen goes black.
!! if anyone can help please do not hesitate, mostly appreciated.

Try to hold the Down+Menu+Power combination while INSERTING the battery into the device.

i try that seem to have no response and when unplugged from usb it loop at&t logo
or plugged in usb screen goes black and no response seem from pressing buttons

I had a similar problem as most phones in Canada seem to have Download/Recovery mode disabled, and here is what worked for me.
Grab something like One Click Un Root (all models), and click one click un root (obviously phone has to be on and plugged into the computer).
This should automatically reboot you into Recovery Mode!
All you have to do is "wipe data/factory default" or something like that (should be the third option).
As it states, you will loose all your data, but at least you will have a functionning phone!

did it work?

Hi. I have similar problem. Can anybody give instruction what can I do?

I have this problem too. Please help somebody

Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. ****[email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY

This is not working. Probably because the phone is not in USB debugging mode as I can't change it... Is there any other way to get the phone into recovery mode?
**** me

i had the same thing happen to me the other day with my bell galaxy s and my phone wont do the 3 button combo trick. i left my phone plugged in to a wall charger for a while until the back of the phone became a little warm. i pulled the battery and then left the power cord plugged in and put the battery back in. i held the volume down and enter button until the battery charging indicator showed up, then i also pressed and held the power button until the boot animation started (this is the blue moving swirl and music, not the galaxy s splash scree) and then i let go of the power button. it took a few attempts at this before it actually worked, but eventually it will go into download mode at which time you can open the odin app, then plug in the usb cable and flash your phone that way. it did seem to make a difference if the back of the phone (around the camera area) was warm. if i let go of the power button while the music was playing and the phone did not enter download mode i would keep all 3 buttons pressed until it shut down again, then i would only let go of the power button while the phone initiated the charging screen, then once the battery logo was displayed i would hold the 3 buttons again and would just keep doing this until it went into download mode. i have flashed it at least 5 times today and i have been able to do this each time.
i also had an issue where odin would not recognize my phone was plugged in and windows would show a message saying the usb device was not recognized. i left the phone plugged in and while in download mode i pressed the volume up, enter button and power button until the phone went blank and when the galaxy s logo showed up i let go of the power button and the phone would go into recovery mode and then the usb drivers would be installed. i would then do the 3 button combo for download mode and odin would work fine. it took several attempts but it does work. i hope this helps you guys

If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....

xZeDgEx said:
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
Click to expand...
Click to collapse
That's what mine did too, several times in a row and then it worked. For some reason it only works after the battery is charging for a bit and the back becomes warm. then it works at will

No luck. I am probably screwed getting it exchanged now too as I am passed the 14 days from Best Buy.

the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
xZeDgEx said:
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. [email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
Click to expand...
Click to collapse

AllGamer said:
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
Click to expand...
Click to collapse
Its my fault??
I did not hack my phone. Its not rooted, I did nothing to it.
By "unlock" I meant exactly that, unlock as in swiping the screen to unlock it.
The more I search the net the more posts I find of Galaxy S phones randomly bricking...

on the original message sounded more like you went to Unlock the phone, as in SIM unlock the phone using any of the tools available out there, and there has been already several people which had the same problem.
if you go back to Bell for an exchange, you better not use the word "unlock" rather use Swipe
as the message on the phone "swipe the screen to unlock"
there are no known issue about this causing the phone to brick.
if that is what happened to you, you should have started a new topic for people to help you, instead of hijacking the topic from the OP, as your issue is different from OP, the OP actually screwed up because he/she flashed the wrong ROM to the i9000
... anyways, Does it work if you reboot the phone?

I have rebooted the phone about 100 times. The phone crashed when I unlocked it to check a text I received. (not hacked). Has not booted up properly since. I have found many others with the same issue who have also not hacked/rooted/unlocked/ their phones.
Waiting on Best Buy to call me back. I am so pissed right now, I have been bragging to my friends and co-workers how awesome this phone is, one has already picked one up, I hope his doesn't brick too. Not recommending it to anyone anymore..

did you load a lot of MP3 to the phone?
can you boot into Recovery Mode?
in the recovery mode you can wipe the Cache and wipe the data
that should make your phone work normal again
it'll be best to open a topic to help you trouble shoot your interesting issue, as it's the first i've hear that you get a black screen after Swiping out of the lock screen

I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.

xZeDgEx said:
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
Click to expand...
Click to collapse
on the other topics relating to the 3 button not working.
have you tried the heating up method?
or the plugging the battery in, when all 3 buttons are pressed? (of course for this one you will need help from a friend, unless you are very skilled at keeping the 3 button on hold meanwhile able to slide in the battery in with out a 3rd hand)

Possibly Hard-bricked?

Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?

Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.

FluffyMittens said:
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
Click to expand...
Click to collapse
I think you've got your terminology mixed up. Bootloader is the mode that comes up by pressing both volume keys while powering on. This is where you flash stuff through RSDLite or use adb server to push and do hacker stuff.
Recovery is the phase where you can do factory wipes and data formatting. I can't get into recovery.
When you flash an SBF, it should be flashing a new recovery. I think the phone is hosed.

If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App

infazzdar said:
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You've got to be ****ing kidding me.

Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse

FluffyMittens said:
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
ADB isn't working. I don't think ADB works in bootloader.
You ask me what I have done so far, but I already put all that information in the OP. That is why I was so frustrated with that second guy. If you guys would take time and not skim over my post that I actually thought out and typed ****, you wouldn't have to waste your time asking me what I have done.
I appreciate the ADB suggestion.

Just trying to collect some information. I'm someone that doesn't let a phone just be deemed as bricked. How charged is the battery?
-Edit: Just checked, ADB doesn't work in bootloader. Confirmed by having RSD open and making sure it sees it, and then tried adb devices. Also as a supporting confirmation for the fun of it, ran the one click root.
-Edit: Further thinking about it, was this phone submerged in water or just had moisture in there? There could just be some minerals formed up on the board that a toothbrush would get rid of. I've fixed phones a dozen times. Some phones will turn on and get stuck. Some wont turn on. Some the backlight comes on but no video signal.

Deoxit
My guess is that the buttons aren't working. There's no way to test that since you can only get to the bootloader, but if you can successfully SBF the phone the odds of any of the solid state gear being bad are pretty low. It does seem odd though that you can't make it to the boot animation and get stuck at the boot logo.
I would suggest getting some deoxit (tv tuner cleaner) and spraying it in around the hardkeys on the bottom of the phone. You don't need too much (especially since it might end up behind the screen). Spray that in there and then work the buttons a few dozen times. That should loosen up any corrosion on the switches and let them close the circuit again. If that doesn't do it, I'm out of ideas, but at least you'll have some deoxit lying around (stuff is great for static-y radio/stereo volume control knobs, etc).

The battery is pretty well charged. When I got it in the mail, there was no charge. I cut a USB cable and hooked it up to power. After about 2 minutes, I tried it. It got to bootloader but said battery was too low. I used the cut USB cable and hooked it around the battery pins in the phone and put the battery in, so it charged it at the same time it was tricking the phone into thinking the battery was full.
Also, if you go into Bootloader and then power off the phone, the green LED comes on. I'm assuming that means it's charging? I was skeptical since all we hear is that you're ****ed if your battery runs out at this stage of the game. It was off this morning and had been plugged in with the green LED all night (no USB cable hack).
As for trying adb while RSDLite is open, no go. adb devices shows blank. Motorola OneClick root didn't work either. It just sat there waiting for my phone. I didn't have the balls to plug in my Bionic to see if Motorola OneClick would work (and therefore the problem is with the Droid X).
As for the water damage, who knows. The lady I got it from was surprised when I told her there was moisture under the screen. I'm not her mommy so she didn't have any reason to withhold information from me. I just thought a bag of rice, a $12 battery off Newegg (free shipping, too), might just get me a sellable Droid X out of the deal.
As for the hardware buttons - they feel like they're clicking, but I know that obviously isn't the 100% test whether they're functioning properly or not. The volume buttons and power button obviously do function, since I can use those to get into BL.
Another brain jog idea: Is there an SBF out there that wipes the data and cache, along with all the other **** it puts on? This probably won't work because I still should be able to get into Recovery - something is FUBAR.
Please give up if you feel like giving up. Bricks exist. This may very well be one of them.
P.S. The girl that gave me this dropped her new iPhone 3 days into ownership. It only cracked the back glass, but the point still remains: she may not be the most graceful phone owner on the planet. Who knows what this DX has been through.
Thanks for all your help, guys.

I would try cracking that thing open and seeing if there are any mineral deposits and cleaning them. This means those weird clips and stuff too, just take a toothbrush to the whole thing and see where that gets you.
As with giving up, I'm a pretty bored guy and finding something to do is better then sitting around and watching Star Trek.
I haven't lost a phone once
Edit: Except for this [email protected]*% of an ACN voip phone that I buffer overflowed in attempt to gain root.. That ended badly.

Same problem
I had the same problem with my dx trying to sbf to .602 I ended up flashing the stock stock froyo sbf and upgrading to gingerbread by rooting and flashing CM7 or any other gingerbread rom. You didn't specify whether or not you tried froyo sbf. No idea if this will work for you but its worth a shot if you haven't already tried it. I also had to use RSD lite 4.9 or 4.8 to get the sbf file to work right.

I'd like to toss my problem into this thread if it's alright. The OP is the closest description to my situation I've read. A co-worker brought his phone to me and it would only get to the round red logo and stop there. No bootloop just a freeze at the red logo.
I tried different ways to get to recovery but was only able to get it to the white bootloader screen. (30.04) So I flashed .340 using RSD and it completes and tells me to manually start the phone. But the phone is already at a white logo (not a red one). I do a battery pull to restart the phone and I still can't get the phone to a recovery by holding down home or any other key while powering on. Battery charge is near full.
The owners explanation of how the phone got this way is that he woke up one morning and there was a 'protection mode' transparency on the screen so he rebooted and had the red logo from then on.
So, I can RSD flash just fine but the phone won't get past the black screen with the white and black M logo.
I would try flashing other files or even the Linux CD option but I can't find anything downloadable since mega got shut down.
Any advice would be appreciated.

Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.

NType3 said:
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down together gets buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
Click to expand...
Click to collapse
1. Would be happy to try .602. Do you know of a working link?
2. It never gets to the eye.
Edit... I found a 602 iso to make a CD boot disk from and used that. The install went perfect but the phone still just boots to a red M logo and freezes there. It doesn't get to the red eye and no button press combo can get it to the recovery screen. I can only get it to the bootloader or let it go to the red logo. The buttons don't feel sticky or anything and the batt is fully charged.

The Fix
Skyroket said:
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Click to expand...
Click to collapse
This will have all sbf working files and linux operating systems along with everything you will need try to sbf one of those preff linux. If this doesn't work and your still stuck! Go to this web page you will need.
Motorola Droid X Motherboard Flex Cable Replacement
Motorola Droid X Keypad Flex Cable Replacement
http://www.repairsuniverse.com/motorola-droid-x-replacement-screens-repair-parts.html
Finally here is how you take it apart with out damaging it.
http://www.youtube.com/watch?v=wo7dXyJhL1U
GL to you enjoy your droid x once ya get it working!

I always have to sbf my dx twice, I always boot loop the first time.

Just fyi, if you bootloop after an sbf, you can pull the battery, boot into stock recovery with the usual key combo format data and you'll be all set: no more bootlooping (or double sbfing!)

M30s does not boot - stuck at very first screen

Hi all,
my Gylaxy M30s rebooted itself yestarday, and now is stuck at the very first screen (the one showing "SAMSUNG Galaxy M30s" in the center and "Powered by android" at the bottom).
Vol down + power results in a reboot attempt (screen goes black, vibration), but the phone is stopping at the same screen again.
I am not able to turn the phone off.
Switching from Vol down to Vol up immediately when screen goes black does not enter recovery mode.
Vol down + power while charging sometimes leads to the charging symbol being shown on the screen, but without the percentage in the middle.
Charging over night did not help.
The phone cannot be connected to a Win PC.
Any suggestions what I can try?
Thanks,
Alchemist

Try volume down+volume up and while pressing those buttons, plug your phone into your computer. Tell me the results of that.

Nothing happening...

I mean trying those combinations immediately after using power+ volume down to reboot.

What did you do with your phone? Died suddenly when normally using?

Yes, phone died during normal usage.
Ah, I see - a screen comes up warning me that downloading a custom OS might harm the phone.
Also, the PC makes this "USB connected" sound when I then press Vol up, but I do not see a new drive connected, I think.
I am slightly optimistic now?

Press volume up.Then install Samsung usb drivers(search on Google)

Ugh, just wanted to do this, but now the phone is completely dead. No response to any button or charging. Will hang it on the charger for a few hours, but my optimism is gone...

OK, now it works again. I am in the screen with the colourfull stuff and the phone waits for some download.
Driver is installed on PC. Is there anything supposed to happen - the phone is still not accessible via PC, or is it?

Install Odin (search in Google 'odin samsung' and download)
Download stock firmware(android os) at www.samfw.com , after downloading you will see files like AP-M505xxxxxxx.tar.
Select, from the stock ROM AP-M305xxxxx.tar for AP in odin CSC-M305xxxxx.tar for CSC, and so forth then click start .

OK. All data will be lost, right? Is there some way to access the internal storage to rescue some files before flashing the new firmware?

Sorry to tell you that you cannot have data restored bad news for you sorry

Sorry. If you only see one file(make sure it is .tar or .tar.md5 file) after you extracted the .zip firmware, install it to the AP slot.

Any chance I could fix this issue with tools like dr.fone, UltFOne, ReiBoot?
I do not have any experiences with these - no idea if the just want to make money with desparate customers? ...

These could possibly brick your phones even more ( anyways flashing with Odin could also brick your phone). However, it in some cases can fix your device.
If you HAVE to have your data back and you don't mind paying, visit a service center and tell them: 'Hey my phone died and i HAVE to have the data back '.(I know, your warranty is expired probably, but they might still do the things for you with paying.)(if those stores closed during lockdown then I don't know any way to fix it.)

OK, another thing I have observed: The screen goes black after about 30 sec to 5 min when not charged - the shorter it was charged, the quicker the screen goes black. Buttons do nothing when screen is black. When reattached to charger, phone tries to boot and is then stuck at said screen - no button pressing needed for the phone to try to start. The longer the phone has been without charger, the longer it takes until the phone tries to boot.
Maybe it's just the battery that is dead - or would the phone with a dead battery boot normally when attached to charger?

If that is the case, open up your phone, put in a replacement battery, and try to boot up(yes, you need to. it will be a frustrating process.). Your phone could be having a faulty battery and nothing else, to cause this issue.

Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..

Mystic_Jamdam said:
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Click to expand...
Click to collapse
Truth to be told: The guy in the repair shop opened the phone and wanted to change the battery - when he saw that water must have come into the phone, corroding the motherboard. So yeah, all data lost, but... no backup, no mercy. I now have set up a NAS for all computers and devices in our family... ;-)

If it really is a hardware problem then the quality must have been really bad.