Database Develop

Please, I really need some serious help...

Ok, here's my story: I dropped my phone in my toilet (yes it was clean). I immediately pulled it out and pulled the battery. I dried it over a seven day period with the rice in a bag method in a warm window. After I was completely sure that it was dry, I inserted the battery and proceeded to try and start my phone. It started up and I thought I was in the clear! Not quite... When it starts up, it boots to the normal AT&T screen and then proceeds directly to the Green Windows 6.0 screen. At that point it chimes (dead battery chime) and then dies.
I've tried flashing roms and radios to no avail. It will flash a new rom but, when I start it up, it does the same thing, goes to the Green Windows 6.0 or 6.1 screen, depending on the rom, chimes and then dies again.
Right now I'm running the stock AT&T rom with the stock radio (1.27.14.09). I can get into Bootloader mode (RGB screen) and I can do hard resets. Funny thing is, I can get into bootloader without using the soft reset button on the bottom. All I do is press the camera+power buttons at the same time and it goes into BL mode.
My BL screen has:
KAIS1*0
SPL-3.56.HARD (No, Not original)
CPLD-8
My Startup screen (first AT&T splash logo) shows:
R 1.27.14.09
G 22.45.88.07H
D 1.62.00.00
I can connect it to my pc via usb and the pc will recognize it as a CE storage device and loads the drivers for it but ActiveSync doesn't recognize it nor does Windows Mobile Center in Vista. All this is done in BL screen. My PC also recognizes it if it's turned on at the AT&T screen but does not have enough time to load ActiveSync before the phone dies. I can also connect it to the wall usb charger and the Amber LED light that states that the phone is charging comes on but NEVER goes green no matter how long I leave the phone plugged in. Same with the USB port on my PC. It never goes green.
I also ordered a new battery from AT&T to see if maybe that was the problem but that doesn't do anything either. So that ruled out the dead battery idea. I also tried the battery from my Wife's Tilt and it does the same thing.
Please, PLEASE help me! I am at a loss here and don't know what to do anymore. I even tried MTTY 1.16 and 1.46 and they do nothing but reboot my phone with CMD> task 8. It won't even format my phone with "task 28". It goes through the motions on the MTTY screen on the PC but it does nothing to the phone.
Again, please help me out here. I am willing to try anything just get some life back into my phone! Any suggestions are welcome and I hope that some of the wiser board members can hear my plea and help a guy out!
Thank you in advance!
P.S. I can't return the phone to AT&T due to the water sensor behind the battery being tripped. Says "VOID" in nice fuzzy pink letters...

in my eyes you don´t have a software problem but one with your hardware. so it´s useless to flash other roms. when you get a hardreset without pressing the reset button this button seems to be switched. put off the cover and clean the contacts in order to repait your device.
a manual how to open it you will find here in this forum
good luck!
matthes
gruiz1122 said:
Ok, here's my story: I dropped my phone in my toilet (yes it was clean). I immediately pulled it out and pulled the battery. I dried it over a seven day period with the rice in a bag method in a warm window. After I was completely sure that it was dry, I inserted the battery and proceeded to try and start my phone. It started up and I thought I was in the clear! Not quite... When it starts up, it boots to the normal AT&T screen and then proceeds directly to the Green Windows 6.0 screen. At that point it chimes (dead battery chime) and then dies.
I've tried flashing roms and radios to no avail. It will flash a new rom but, when I start it up, it does the same thing, goes to the Green Windows 6.0 or 6.1 screen, depending on the rom, chimes and then dies again.
Right now I'm running the stock AT&T rom with the stock radio (1.27.14.09). I can get into Bootloader mode (RGB screen) and I can do hard resets. Funny thing is, I can get into bootloader without using the soft reset button on the bottom. All I do is press the camera+power buttons at the same time and it goes into BL mode.
My BL screen has:
KAIS1*0
SPL-3.56.HARD (No, Not original)
CPLD-8
My Startup screen (first AT&T splash logo) shows:
R 1.27.14.09
G 22.45.88.07H
D 1.62.00.00
I can connect it to my pc via usb and the pc will recognize it as a CE storage device and loads the drivers for it but ActiveSync doesn't recognize it nor does Windows Mobile Center in Vista. All this is done in BL screen. My PC also recognizes it if it's turned on at the AT&T screen but does not have enough time to load ActiveSync before the phone dies. I can also connect it to the wall usb charger and the Amber LED light that states that the phone is charging comes on but NEVER goes green no matter how long I leave the phone plugged in. Same with the USB port on my PC. It never goes green.
I also ordered a new battery from AT&T to see if maybe that was the problem but that doesn't do anything either. So that ruled out the dead battery idea. I also tried the battery from my Wife's Tilt and it does the same thing.
Please, PLEASE help me! I am at a loss here and don't know what to do anymore. I even tried MTTY 1.16 and 1.46 and they do nothing but reboot my phone with CMD> task 8. It won't even format my phone with "task 28". It goes through the motions on the MTTY screen on the PC but it does nothing to the phone.
Again, please help me out here. I am willing to try anything just get some life back into my phone! Any suggestions are welcome and I hope that some of the wiser board members can hear my plea and help a guy out!
Thank you in advance!
P.S. I can't return the phone to AT&T due to the water sensor behind the battery being tripped. Says "VOID" in nice fuzzy pink letters...
Click to expand...
Click to collapse

Matthes42 said:
put off the cover and clean the contacts in order to repait your device.
a manual how to open it you will find here in this forum
good luck!
matthes
Click to expand...
Click to collapse
Ewww, I was afraid someone would say that... I'm not technically inclined to be able to do that. I WILL break something when trying to open it and that's the last thing I want to do.
I'll see what else I can try though. Thank you for the advice!

youre spl is FU, best thing todo if you cant revert is go here and call out for jockyw2001

Lol i was hoping that maybe jockyw2001 or GSleon would see this thread...

gruiz1122 said:
Lol i was hoping that maybe jockyw2001 or GSleon would see this thread...
Click to expand...
Click to collapse
PM jockyw2001 one of them and make them aware of youre trouble. I belive thats okey since they say so in tread. I dont think you are in deep at all.

I guess it won't hurt?

Might anyone else have any insight as to what might be going on or what I can do?

The powering off problem sounds like dirty contacts to me. Have you tried a Qtip/Cotton bud and some specialist contact cleaner (an electronics hobby shop can supply this) on the battery contacts of the phone? It doesn't take much for the connection to be a problem even though they may look clean, the sightest bit of tarnishing can do it. If anything further is needed then if you're not technically adept, either find a friend who is and reward them appropriately for their time or take it to a phone repair shop. It's important for the phones longevity that its properly decontaminated/cleaned as even if it's dried off as described, corrosion can still set in over time and that'll cause problems. Time and/or money spent cleaning it properly now, will likely save you much more on component replacement down the track.

i've got the same problem, except no hardspl installed but can and have reflashed. i dont know if this phone went into water, i got it from someone.

using "info 8" command on MTTY, i turned up this result:
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 778 (0x30A) is bad block
BLOCK 908 (0x38C) is bad block
BLOCK 1012 (0x3F4) is bad block
BLOCK 1377 (0x561) is bad block
BLOCK 1568 (0x620) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x8940
Partition[3], type=0x4, start=0x96C0, total=0x11C00
CE Total Length(with sector info) = 0x4BAB600
CE CheckSum Length(without sector info) = 0x4B60000
the "task 28 55aa" command shows this:-
Format start
Storage start sector=0x96C0, total sector=0x11C00
Storage start block=624, total block=1136
Total Bad Block in CE: 0
Erase physical block from 914 to 2048
formatstorage Bad block found: 1066
formatstorage Bad block found: 1196
formatstorage Bad block found: 1300
formatstorage Bad block found: 1665
formatstorage Bad block found: 1856
Format end
nothing happens on the phone, even after several attempts and boots.

Touch Diamond Repeatedly Restart Itself

Yes, it restart itself every few minutes.
I got this problem since the day I bought it about 2 weeks ago. I sent it back to the seller and they did something to make it work fine till now.
The same problem comes back.
I observed the problem and here are the facts.
1. It restart a few seconds after it turn off the screen. That's the power settings.
On batter power: Turn off device if not used for = 40 sec
So about 5 sec after the screen is off, it restart.
If I plug it to USB charging mode or sync mode, it get extremely hot but never restart, because it never turn off (not on battery power).
If I untick "Turn off device if not used for"... it also get extremely hot but never restart. It does drain too much battery, of course.
2. It's abnormally slower than other devices. My father bought 3 HT Diamonds at once. 2 works fine so I can compare them. They have the same firmware, same model, everything is the same, but this one got this problem.
3. It happened like this for both Chinese firmware and English firmware. But when the seller fixed it, they did installed Chinese firmware.
Device information:
Version:
ROM version: 1.93.831.1 WWE
ROM date: 07/18/08
Radio version: 1.00.25.05
Protocol version: 52.29.25.12H
Hardware
CPU: QUALCOMM(R) 7201A
Speed: 528MHz
RAM size: 192 MB
Flash size: 256 MB
Internal Storage: 3823.48 MB
Data bus: 32 bits
Storage size: 82.31 MB
Display resolution: 480x640
Colors: 65536
Bluetooth version: 2.0/2.0+EDR
Bluetooth address: 00: 17: 83: D4: E7: 56
Does anyone know how to deal with this?

Still Restarting
Does anyone have answer to my previous question? So sad that the phone keep restarting itself like this. Is there a new ROM that fix the problem?
Thousands of thanks to person who shred some light. Thanks.

Did you try a hard reset?

Yes
pedmond said:
Did you try a hard reset?
Click to expand...
Click to collapse
Yes, kinda tried that many times.
Did reflashed the ROM 2 times too.
Did tried 2 different language ROM too, 1 English and 1 Chinese.

It looks like you have a defective unit then

I had same problem with O2 Neo then I sold it ASAP

I have also got the same problem, I have tried many ways, Installed dutty's roms also, but the thig is, its not rom fault. its internal storage problem. You have to hard reset all, clear all data in internal storage too.
go to setting > sytem > clear storage

has this problem been SOLVED????

go to setting > sytem > clear storage
Click to expand...
Click to collapse
that didn't work for me.
This fixed my problem after much troubleshooting. I though it wouldn't work, assumed it was hardware problem.
flashed to newest stock rom twice.
flashed to custom rom (mighty) twice.
Don't forget to unlock where need be.

binh said:
Yes, it restart itself every few minutes.
I got this problem since the day I bought it about 2 weeks ago. I sent it back to the seller and they did something to make it work fine till now.
The same problem comes back.
I observed the problem and here are the facts.
1. It restart a few seconds after it turn off the screen. That's the power settings.
On batter power: Turn off device if not used for = 40 sec
So about 5 sec after the screen is off, it restart.
If I plug it to USB charging mode or sync mode, it get extremely hot but never restart, because it never turn off (not on battery power).
If I untick "Turn off device if not used for"... it also get extremely hot but never restart. It does drain too much battery, of course.
2. It's abnormally slower than other devices. My father bought 3 HT Diamonds at once. 2 works fine so I can compare them. They have the same firmware, same model, everything is the same, but this one got this problem.
3. It happened like this for both Chinese firmware and English firmware. But when the seller fixed it, they did installed Chinese firmware.
Device information:
Version:
ROM version: 1.93.831.1 WWE
ROM date: 07/18/08
Radio version: 1.00.25.05
Protocol version: 52.29.25.12H
Hardware
CPU: QUALCOMM(R) 7201A
Speed: 528MHz
RAM size: 192 MB
Flash size: 256 MB
Internal Storage: 3823.48 MB
Data bus: 32 bits
Storage size: 82.31 MB
Display resolution: 480x640
Colors: 65536
Bluetooth version: 2.0/2.0+EDR
Bluetooth address: 00: 17: 83: D4: E7: 56
Does anyone know how to deal with this?
Click to expand...
Click to collapse
Hi binh,
My Touch Diamond does the same. It has the same Radio and Protocol version, but the ROM is 1.93.00.0.
My Problem occurs after the instalation of the IGO navigation software. Untill that it was o.k. After a hard reset is everything o.k. untill the instalation of the IGO. Just tell us if You are using any navigation software?
Thank You in advance.

This should work
Have a touch pro and faced a similar issue . Did a lot of googling and finally found a solution that works . Apparently this happens if the batttery contacts (the small golden colour pins which come in contact with the phone battery ) at the backside are either bent or crimped . Straighten them and it should work like a charm . This is because of faulty battery contacts the phone goes into a restarting loop.
Hope this helps

Well... try this and let me know:
Replace your phone's battery with a genuine new htc battery..
This restarting issue had occurred with my Sony Ericsson w800
The thing is that every li-ion battery has a safety cut out circuit embedded in it. It is there to protect the battery from heating up in case of short circuit. It breaks the power for a few micro seconds and turns it back on. That circuit gets weak with time and eventually it assumes even a little load as a short circuit. So when you use your cellular radio [phone's communication system], it puts an immense load over the battery and the cut out circuit assumes as if the battery is being short circuited. So it cuts out the power for a few micro seconds and turns it back on. The phone, on the other hand, assumes of it as a short power failure so it reboots.
:::::::::::::::::::
I am very eager to know if thats the problem with your device.
Also if you have a non genuine battery, then it would be having a weak cut-out circuit.

What's In This Directory

So, i've been working tirelessly to get my camera going again, a number of people have had this same problem, so, I'd like to fix it for them as well. I've finally found my starting point, so, first off, could someone with a working camera please tell me what's in this directory
/dev/msm_camera/control0

Well in the /msm_camera/ folder I have 3 files:
config0
control0
frame0
each with a size of 0, and no extension... and I am unable to copy them anywhere... hope it helps somehow...

Those are device files. Pipes into or out of the HARDWARE DRIVER.
Pipes don't take up space. They can be READ if your device is pumping data out, and the driver can READ data that you send into them.
If you don't know what they are for, chances are good that you should just IGNORE them. In fact, I can guarantee that you should just ignore ***EVERYTHING*** in the /dev path.
dev = short for "device", which is another word for HARDWARE.
EDIT: judging from the file names, the frame0 file is an output -- take a picture and it shows to be read from frame0. The other two appear to be inputs -- configuration (i.e. resolution, mode), and control (i.e. focus, aperture, etc.).

thaquestion said:
So, i've been working tirelessly to get my camera going again, a number of people have had this same problem, so, I'd like to fix it for them as well. I've finally found my starting point, so, first off, could someone with a working camera please tell me what's in this directory
/dev/msm_camera/control0
Click to expand...
Click to collapse
I just want to say I was having camera problems and decided to send it in under warranty. It took me less than an hour to unroot and get Donut back running. They sent me a new (or refurb) one, I put mine in the box, and done. If you still have warranty left, I recommend that path.

Varying Levels of Repair Despair - Kinds of Bricks

Hi there,
I've been reading through this forum very carefully and it's becoming evident that there are many different definitions of "Bricked" for Galaxy Vibrants, and Galaxy phones in general.
My main goal is to try and fix my phone, but I'd also like to get some collective wisdom on here to help others determine the best course of action for their phone. I've kind of guessed what the best definitions are... please feel free to correct me:
The "DEAD BRICK - or HARDLOCK":
This is my phone. It does not turn on, and by that, I mean, the screen stays black. NOTHING. I've tried all the key combinations. I've done the ODIN thing. I've pulled the USB cord out, and in, and same with the battery. It has NO intentions of turning on.
Remedy: Can anyone help me here? Is this where the JTAG RIFF box is needed?
The "HARD BRICK":
The phone doesn't appear to turn on. When attempting to put it into download mode, you instead get a little Icon with question mark and a USB cord.
Remedy: Sometimes, it appears that the phone can be flashed here from ODIN. Other times, it's a no-go. If that doesn't work, then you need to search the boards for using the 301K resistor method (Jig) to put it back in Download mode.
The "SOFT BRICK":
This seems to be 95% of all cases: The phone does not appear to turn on, or gets stuck at various points such as the infamous "S of Death" or gets stuck at various points in recovery mode.
Remedy:
In almost all of these cases, you have some options for restoring your software, or if you just want to get on with it, the fix-all is a re-flash with Odin, for which there are a multitude of excellent instructions on these boards. Ie:
http://forum.xda-developers.com/showthread.php?t=954509
Does that pretty-much sum it up?
I'm currently pulling my hair out because my phone just WILL NOT turn on...at all. Which makes it Very difficult to receive calls. Should I attempt the 301K method, or is this a job for the JTAG RIFF box at this point?
cheers

Please don't post such horrible information.

Allow me to elaborate.
1. Never recommend that ANYONE use Odin for ANYTHING. Heimdall is much better. Odin causes bricks
2. There's 2 types of bricks. Hard brick and Soft brick.
Hard brick acts like it does not have any battery. It does not respond to buttons or button combos. It cannot be turned on in any way shape or form past it's PBL. USB is not recognized on the computer. It does not respond to a 301Kohm resistor
Soft brick- can be fixed using software. It's recoverable and a 301Kohm resistor will put it into download mode, even if the screen shows nothing.
A hard brick will get this or less when viewing UART output
Code:
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
-----------------------------------------------------------
+n1stVPN 2688
+nPgsPerBlk 64
PBL found bootable SBL: Partition(3).
Set cpu clk. from 400MHz to 800MHz.
OM=0x9, device=OnenandMux(Audi)
IROM e-fused version.
A soft brick will get more then that.... up to this
Code:
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
-----------------------------------------------------------
+n1stVPN 2688
+nPgsPerBlk 64
PBL found bootable SBL: Partition(3).
Set cpu clk. from 400MHz to 800MHz.
OM=0x9, device=OnenandMux(Audi)
IROM e-fused version.
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Board Name: ARIES REV 03
Build On: Jun 8 2010 16:35:37
-----------------------------------------------------------
Re_partition: magic code(0x0)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
Now Read Images - ID : 1
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EFS (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SBL (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL2 (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARAM (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNEL (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVERY (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYFS (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAFS (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 140
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1954
NO_UNITS : 50
===============================
loke_init: j4fs_open success..
load_lfs_parameters valid magic code and version.
load_debug_level reading debug level from file successfully(0x574f4c44).
init_fuel_gauge: vcell = 3998mV, soc = 101
check_quick_start_condition- Voltage: 3998.75000, Linearized[74/89/100], Capaci0
init_fuel_gauge: vcell = 3998mV, soc = 101, rcomp = d01f
reading nps status file is successfully!.
nps status=0x504d4f43
PMIC_IRQ1 = 0x0
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x14
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x40
PMIC_STATUS2 = 0x2c
get_debug_level current debug level is 0x574f4c44.
aries_process_platform: Debug Level Low
keypad_scan: key value ----------------->= 0x0
CONFIG_ARIES_REV:48 , CONFIG_ARIES_REV03:48
check_download: micorusb_status1 = 400, key_value = 0
aries_process_platform: final s1 booting mode = 0
DISPLAY_PATH_SEL[MDNIE 0x1]is on
MDNIE setting Init start!!
vsync interrupt is off
video interrupt is off
[fb0] turn on
MDNIE setting Init end!!
Autoboot (0 seconds) in progress, press any key to stop
get_debug_level current debug level is 0x574f4c44.
get_debug_level current debug level is 0x574f4c44.
boot_kernel: Debug Level Low
FOTA Check Bit
Read BML page=, NumPgs=
FOTA Check Bit (0xffffffff)
Load Partion idx = (6)
..............................done
Kernel read success from kernel partition no.6, idx.6.
setting param.serialnr=0x393176a8 0x828e00ec
setting param.board_rev=0x30
setting param.cmdline=console=ttySAC2,115200
Starting kernel at 0x314dc000...

I do not know what the second poster here is on about.
First of all I feel that odin is reasonably safe when you are careful with the boxes you check and have made sure to educate yourself before attempting to flash something. I actually think i have seen more posts about heimdall disasters then I have odin mishaps....and far, far more about Kies.
Remember any time you flash anything there is a certain amount of risk and move on.
Secondly all that output from the second poster is very pretty and I am sure quite accurate and informative but unrealistic and useless for 99.999 percent of all sgs users.
The op's description of hard brick and soft brick may seem simplified to an engineer but it is pretty accurate to what I have seen and read, even though the term brick is badly overused. If you can save it, it is not a brick...and almost all phones can be saved.
If you cannot get into download mode AT ALL with the handset, you need a jig which will get almost all devices into download mode. If a jig fails to do so you either have a serious hardware problem or have found a way to remove/corrupt your bootloader. In either case a service center is your only hope.
If you phones DOES go into download mode or is able to respond at all, then it can almost certainly be saved. It isn't bricked at all, just a bit messed up. There are plenty of threads describing what to flash and how to get back to a usable state.
It sounds like the op needs a jig as the next step in trying to fix their phone.
As for the second poster....stop scaring the noobs.
Sent from my GT-I9000 using XDA Premium App

Thank you rshenck and AdamOutler,
I appreciate both the positive and negative critiques, both have their place.
For sure, I'm approaching this as an attempt at a Noob's troubleshooting guide. As such, the expense and skills involved in getting output from the Samsung Primitive Boatloader make the results of limited value...However it is quite nice to have Both definitions in the same thread....and it's a much more plausable description than mine, which would be that the phone died on May 21st in a foreseen Apololypse-related event...
I AM impressed/fascinated with the technical definition provided and...I'll say it...a little jealous too. If I had an extra phone kicking around and $300 to blow on equipment (maybe sometime soon), I'd like to learn more about it.
I am also very encouraged, rschenck, by your suggestion that I should try a Jig. I appreciate that Almost as much as I appreciate you sticking up for inferior life forms such as myself
I will try the Jig, and report back. My hopes are low, but I'll pick up some resistors tomorrow and see how it goes.
Thanks again....
So....if the Jig doesn't work, what do I have? A "Hardlock"? Is it like an update.zip issue? Or Viagra?
cheers

jjgallow said:
Thank you rshenck and AdamOutler,
I appreciate both the positive and negative critiques, both have their place.
For sure, I'm approaching this as an attempt at a Noob's troubleshooting guide. As such, the expense and skills involved in getting output from the Samsung Primitive Boatloader make the results of limited value...However it is quite nice to have Both definitions in the same thread....and it's a much more plausable description than mine, which would be that the phone died on May 21st in a foreseen Apololypse-related event...
I AM impressed/fascinated with the technical definition provided and...I'll say it...a little jealous too. If I had an extra phone kicking around and $300 to blow on equipment (maybe sometime soon), I'd like to learn more about it.
I am also very encouraged, rschenck, by your suggestion that I should try a Jig. I appreciate that Almost as much as I appreciate you sticking up for inferior life forms such as myself
I will try the Jig, and report back. My hopes are low, but I'll pick up some resistors tomorrow and see how it goes.
Thanks again....
So....if the Jig doesn't work, what do I have? A "Hardlock"? Is it like an update.zip issue? Or Viagra?
cheers
Click to expand...
Click to collapse
If the jig doesn't get you into Download mode, then take it to a service center and say you have NO idea what happened, it just stopped one day.

rschenck said:
If the jig doesn't get you into Download mode, then take it to a service center and say you have NO idea what happened, it just stopped one day.
Click to expand...
Click to collapse
Tell them you where updating through Kies if they query anything and it stopped working .
jje

rschenck said:
I do not know what the second poster here is on about.
First of all I feel that odin is reasonably safe when you are careful with the boxes you check and have made sure to educate yourself before attempting to flash something. I actually think i have seen more posts about heimdall disasters then I have odin mishaps....and far, far more about Kies.
Remember any time you flash anything there is a certain amount of risk and move on.
Secondly all that output from the second poster is very pretty and I am sure quite accurate and informative but unrealistic and useless for 99.999 percent of all sgs users.
The op's description of hard brick and soft brick may seem simplified to an engineer but it is pretty accurate to what I have seen and read, even though the term brick is badly overused. If you can save it, it is not a brick...and almost all phones can be saved.
If you cannot get into download mode AT ALL with the handset, you need a jig which will get almost all devices into download mode. If a jig fails to do so you either have a serious hardware problem or have found a way to remove/corrupt your bootloader. In either case a service center is your only hope.
If you phones DOES go into download mode or is able to respond at all, then it can almost certainly be saved. It isn't bricked at all, just a bit messed up. There are plenty of threads describing what to flash and how to get back to a usable state.
It sounds like the op needs a jig as the next step in trying to fix their phone.
As for the second poster....stop scaring the noobs.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Let me tell you how it is. A noob has no reason to write technical documentation. Also, noobs should be scared.
Personally I've hard bricked 3 phones during flashing PBL/SBL, and 2 phones while looking for hardware recovery entry points. I've soft bricked those phones about 30 times during development.
If samsung had programmed in a protected area of memory to reset the PBL/SBL upon button combination, then we would not have this problem.. But they didn't. They chose to ignore the fact that the PBL/SBL can be overwritten and brick the phone.
Be scared. Don't get into something you don't understand. read the threads in this post before flashing, because if something goes wrong, you'll need the knowledge
http://forum.xda-developers.com/showthread.php?t=999302
http://forum.xda-developers.com/showthread.php?t=1065318
http://forum.xda-developers.com/showthread.php?t=1000175
http://forum.xda-developers.com/showthread.php?t=1081892
Let me school you on what causes bricks. It's not flashing..... It's flashing two speciffic files.. The PBL.bin and the SBL.bin. Those are the only two files capable of bricking the phone. There is no risk while flashing a rom, kernel, or modem. I don't really trust the PIT because it can cause damage to the PBL/SBL partitions. I don't really trust the params.ifs because the PBL and SBL pull data from the param.ifs. It's been said that PIT and param.ifs are safe, but I have come up with several scenarios where they are not.
So, Sticking to safe... Flash modems, kernels, and FactoryFS's all day long and you won't brick. As for flashing PBL and SBL, the options for recovery are listed in this thread: http://forum.xda-developers.com/showthread.php?t=1065318
Btw... you should specify 301kohm jig. There's several resistor values which will activate the FSA-9480(USB switch) chip's JIG output line. 301K will boot the phone and cause it to go into download mode. Personally I say "301Kohm between microUSB pins 4 and 5".

double post

AdamOutler said:
Let me tell you how it is. A noob has no reason to write technical documentation. Also, noobs should be scared.
....
So, Sticking to safe... Flash modems, kernels, and FactoryFS's all day long and you won't brick. As for flashing PBL and SBL, the options for recovery are listed in this thread: http://forum.xda-developers.com/showthread.php?t=1065318
Click to expand...
Click to collapse
Thanks AdamOutler,
I do have to point out again that I hard-bricked, or hard-locked my phone doing a standard stock update with Samsung Kie.
Previous to that, I had tested out about 6 different ROMs in Odin out of curiousity, with no trouble. As soon as I played it safe, I ran into massive trouble. Bad connection during the update? Maybe. I dunno.
I agree with you, one would think it could be designed in such away that the Software stays Soft.

Then take it to a Samsung Service Center.
You upgraded the firmware through Samsung approved software.
Don't even mess around, they will fix it for you.

For others that may encounter a similar problem, I was able to solve this through connexion2005 from mobiletechvideos.com. connexion2005 was highly professional and had the expertise to give me the solution I needed.
http://forum.xda-developers.com/member.php?u=1602851
He JTagged my phone, and now it works perfectly. It's like a new phone, as if I'd never foolled around with it.
Not only that, but he loaded it with Simply Honey, which is just an awesome, stunning, fast and stable operating system:
http://forum.xda-developers.com/showthread.php?t=1021383
I was able to choose from any OS I wanted, and based on some of his advice we came up with this OS. It turned out to be exactly what I was looking for.
For now, I have a brand new OS, and my phone is better than it ever was. I plan on leaving it that way
At some point down the road if I decide to upgrade my phone, I can go ahead knowing that if I somehow manage to hard-brick it, there is a solution.
Thanks for all your help, connexion2005!
ps...I bought this phone from someone who had already modded it...I never had any interest in the standard Samsung Vibrant software setup. I should also mention that my cell phone provider does not sell Vibrants, so getting one out of their store was never an option.

AdamOutler said:
Btw... you should specify 301kohm jig. There's several resistor values which will activate the FSA-9480(USB switch) chip's JIG output line. 301K will boot the phone and cause it to go into download mode. Personally I say "301Kohm between microUSB pins 4 and 5".
Click to expand...
Click to collapse
Wroong, mate. As a chemist, I'd say: you have to put the material with electrical conductivity limited to 301kOhm, and CONNECT it to copper material on 4 and 5 pins of the microUSB plug ON THE phone (not on the e.g. camera).
And, my description would be same useless for 99.9999% of the readers as yours.
Please wake up, you can buy a 301kOhm jig directly from eBay..
But, I respect opinion of the PLY. I love when somebody tells me: you have to put the capacitor output charge to the electric motor, same time giving the current to the ignition coils in proper sequence by using the security device.
Personally, I prefer the description: turn the ignition key on, but this is my personal feeling only.

Droid 4 problem - no screen or white scrambled screen

Hey so just recently I have been having a hard time trying to get my phone to work again. This one morning I wake up to find my Android screen with a grey and white screen (picture in attachment) it looks somewhat like that but vertical.
Anyways I have tried turning off the phone but still get this screen. I can however get back to both the AP fastboot screen just perfectly. My warranty JUST ran out a month ago and they say I can send it in for 187 bucks but honestly, it seems as though its not a hardware problem and more of a software issue. Please help, I dont want to have to give Verizon my money for a software issue i can fix myself lol

ShnbFire said:
Hey so just recently I have been having a hard time trying to get my phone to work again. This one morning I wake up to find my Android screen with a grey and white screen (picture in attachment) it looks somewhat like that but vertical.
Anyways I have tried turning off the phone but still get this screen. I can however get back to both the AP fastboot screen just perfectly. My warranty JUST ran out a month ago and they say I can send it in for 187 bucks but honestly, it seems as though its not a hardware problem and more of a software issue. Please help, I dont want to have to give Verizon my money for a software issue i can fix myself lol
Click to expand...
Click to collapse
If you can get to the fastboot screen have you tried fastbooting the stock firmware? Try using this utility: http://forum.xda-developers.com/showthread.php?t=2207384. Use option 2 if you don't want to wipe out your data.

kwyrt said:
If you can get to the fastboot screen have you tried fastbooting the stock firmware? Try using this utility: http://forum.xda-developers.com/showthread.php?t=2207384. Use option 2 if you don't want to wipe out your data.
Click to expand...
Click to collapse
Si I tried that option and I still get the same screen x_x

It seems I got the exact same problem as described in this post, and the issues started only recently. To give some more information, these are the phases the phone went through.
It started with the phone acting like the proximity sensor was activated, the screen would go out at random times or turn off and on. I got the idea it was the sensor next to the right of the Motorola logo, there actually was a scratch right on this sensor and I thought this was the problem. When I would put my thumb over this sensor the phone would work normally as long as I kept it covered, alternatively the phone would work normally when I would slide open the phone.
The next part was that the screen no longer would come on when I pressed the power button, it would activate some part of the backlight, but the screen would stay black. Rebooting the phone would help, the Motorola logo showed fine, then the Droid logo came on fine and also made sound. But the moment where it should show the SIM lock screen in Portrait mode it did not show anything at all anymore. Sliding the keyboard open resulted in showing the SIM lock screen, however it would not take any input from the keyboard at that moment, so I could not unlock the phone.
When trying the [email protected] application I could view the screen perfectly on my laptop, so the phone was still working, but it would simply not show anything on the screen. Touching the screen on the phone would results in buttons pressed on the [email protected] screenshots, so I could unlock my phone this way. So even though the screen would not show anything the touchscreen would still work.
Sadly enough the current status is that the screen gives the same image as shown in the first post of this thread (it doesn't even show the Motorola logo anymore), so I can no longer use the phone and also [email protected] does not show any screenshots anymore. However the phone is still being recognized by the program (and I guess ADB).
I got the feeling the problems are a combination of some hardware problem and the software reacting very badly on it. I originally had the idea to disable the proximity sensor somehow by flashing a different rom (running stock now). I am not sure if that is still possible, but I will look into it. Any advice would be appreciated.

Alright guys, I have the same exact problem. Except I am not able to even get to the Motorola screen. I have some pictures that I am wanting to get off the phone. When I plug it up to my computer, I get the little ding that the phone is connected, but it doesn't show up under my drives. I'm not sure what to do at this point. I have my old D3 I can use, but I'm more concerned about trying to get my information off the D4. I can't get into the boot menu at all. As soon at I plug the phone up from being dead it goes to the static screen.

At this moment my phone went on to the next stage, it doesn't show anything at all anymore. Some boots I get the white scrambled screen from the start, but now it is just a black screen. However, I can still connect to it through adb, but the phone is not rooted so I am limited with what I can do with it.
Code:
> adb shell getprop ro.build.description
cdma_maserati_mmi-user 4.1.2 9.8.2O-72_VZW-18 19 release-keys
Code:
[email protected]_maserati:/ $ lsmod
lsmod
pvrsrvkm_sgx540_120 321639 0 - Live 0x00000000
btwilink 3478 0 - Live 0x00000000
wl12xx 136026 0 - Live 0x00000000
mac80211 220250 1 wl12xx, Live 0x00000000
cfg80211 163432 2 wl12xx,mac80211, Live 0x00000000
compat 2546 0 - Live 0x00000000
evfwd 4666 0 - Live 0x00000000
cifs 254412 0 - Live 0x00000000
moto_crypto 95621 1 - Live 0x00000000
The log file (adb logcat -s *:E) shows me the following:
Code:
--------- beginning of /dev/log/main
12-07 01:22:58.125 7534 7535 E FramebufferNativeWindow: couldn't open framebuffer HAL (Not a typewriter)
12-07 01:22:58.125 7534 7535 E FramebufferNativeWindow: couldn't open gralloc HAL (Not a typewriter)
12-07 01:22:58.125 7534 7535 E SurfaceFlinger: Display subsystem failed to initialize. check logs. exiting...
12-07 01:22:59.671 7554 7554 E PhonePolicy: Could not preload class for phone policy: com.android.internal.policy.impl.PhoneWindow$ContextMenuCallback
12-07 01:23:03.289 7555 7556 E FramebufferNativeWindow: couldn't open framebuffer HAL (Not a typewriter)
12-07 01:23:03.289 7555 7556 E FramebufferNativeWindow: couldn't open gralloc HAL (Not a typewriter)
12-07 01:23:03.289 7555 7556 E SurfaceFlinger: Display subsystem failed to initialize. check logs. exiting...
12-07 01:23:04.828 7572 7572 E PhonePolicy: Could not preload class for phone policy: com.android.internal.policy.impl.PhoneWindow$ContextMenuCallback
Snippet from adb logcat -s *:I):
Code:
12-07 13:18:19.093 6237 6237 I ServiceManager: Waiting for service SurfaceFlinger...
12-07 13:18:19.093 5822 5822 I ServiceManager: Waiting for service SurfaceFlinger...
12-07 13:18:19.117 5799 5799 I ServiceManager: Waiting for service SurfaceFlinger...
12-07 13:18:19.125 5741 5741 I ServiceManager: Waiting for service SurfaceFlinger...
12-07 13:18:19.125 6064 6064 I ServiceManager: Waiting for service SurfaceFlinger...
12-07 13:18:19.140 4752 4752 I ServiceManager: Waiting for service SurfaceFlinger...
I do know it is a phone and not a typewriter The SurfaceFlinger error might be where the problem is. I am however out of idea's at this moment. If I could get root access somehow I could recover my data by imaging the 'disk'.

Like suggested in this thread I tried fastbooting to the stock firmware (http://forum.xda-developers.com/showthread.php?t=2207384, option 2). This did not fix the issue for me neither.
Before trying the fastboot stufff, be sure to have a full battery (the battery might keep draining because of the constant white scrambled screen). To check the battery status with adb use:
Code:
adb shell cat /sys/class/power_supply/battery/capacity
I looked in to using the exploit by Dan Rosenberg on this device (http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/ ) However this exploit needs a device which actually boots. Which in this case is not happening, so this exploit does not give root permissions.
It seems that the Droid 4 is running Linux Kernal 3.0.8
Code:
Linux localhost 3.0.8-g473e586 #1 SMP PREEMPT Fri Feb 8 13:28:58 CST 2013 armv7l GNU/Linux
We might want to look in to finding a kernel exploit to escalate privileges on the adb shell.

Since the phone was not working anymore my focus was to recover my data from it. However, the problem I was facing was that I could not access the user files on the phone since I did not have root rights. The solution I sought for was getting root access on the Droid4 by exploiting a vulnerability. Because I only had adb access to a not fully started system the exploit named earlier in this thread did not work so I had to look for something like a kernel exploit. I luckily had some help from some friends, and they pointed me to the following exploit which worked: h t t p s : / / github.com/android-rooting-tools/android_run_root_shell (since I have less than 10 posts, I can not post links)
To use the exploit, compile the source code and copy the file to the Droid4 (also copy the device.db file):
Code:
adb push run_root_shell /data/local/tmp/run_root_shell
adb push device.db /data/local/tmp/device.db
You can copy the files to the /data/local/tmp directory on the phone (you can write here as a user without root rights), make sure to make the file executable and then run the exploit. The exploit can find all the values it needs itself (slow) or get them from the device.db database (fast), for a single use root exploit the slow approach will do, but if you need to use the exploit a couple of times I recommend to use the device.db. The current device.db on the site does not contain the Droid4, but this information will be submitted to the git system, so it will be included in the near future.
In the mean time you can insert the following information in to the device.db file yourself.
Code:
insert into supported_devices(device_id, device, build_id, check_property_name, check_property_value) values(185, 'DROID4', '9.8.2O-72_VZW-18', null, null);
insert into device_address(device_id, name, value) values(185, 'prepare_kernel_cred', 3221997068);
insert into device_address(device_id, name, value) values(185, 'commit_creds', 3221995156);
insert into device_address(device_id, name, value) values(185, 'remap_pfn_range', 3222276972);
insert into device_address(device_id, name, value) values(185, 'ptmx_fops', 3230673008);
Output of the slow version of the exploit (without the information added to device.db):
Code:
127|[email protected]_maserati:/data/local/tmp $ ./run_root_shell
./run_root_shell
Device detected: DROID4 (9.8.2O-72_VZW-18)
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x80008000 form iomem
Failed to open /dev/graphics/fb0 due to No such file or directory
You need to manage to get remap_pfn_range addresses.
Try copying kernel memory... It will take a long time.
Attempt get_user exploit...
Search address in memroy...
Using kallsyms_in_memroy...
prepare_kernel_cred = 0xc00bc60c
commit_creds = 0xc00bbe94
ptmx_fops = 0xc0902870
Attempt acdb exploit...
DROID4 (9.8.2O-72_VZW-18) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
[email protected]_maserati:/data/local/tmp # id
uid=0(root) gid=0(root)
The fast version of the exploit (with the information added to device.db):
Code:
127|[email protected]_maserati:/data/local/tmp $ ./run_root_shell
./run_root_shell
Device detected: DROID4 (9.8.2O-72_VZW-18)
Attempt acdb exploit...
DROID4 (9.8.2O-72_VZW-18) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
[email protected]_maserati:/data/local/tmp # id
id
uid=0(root) gid=0(root)
Now we have root access we can access the partitions we want, to easily download the partitions through adb (on Linux) you can change the rights to the partitions with the following command:
Code:
chmod 777 /dev/block/mmc*
With the non-root user now having access to the partitions, you can download them with the following commands.
For the userdata partition:
Code:
./adb pull /dev/block/mmcblk1p24
For the full disk inside the phone:
Code:
./adb pull /dev/block/mmcblk1
For the sdcard it will be:
Code:
./adb pull /dev/block/mmcblk0
This pull request will take a while, statistics from downloading the userdata partition and whole disk on my machine:
Code:
755 KB/s (3279945728 bytes in 4239.895s)
414 KB/s (15938355200 bytes in 37526.406s)
To read the information from the partitions you downloaded you can, among other things, mount them in Linux or use a tool like FTK Imager on Windows.
I would like to thank and credit both blasty and ius for helping me out and finding the right exploit plus device.db values. In case anyone needs the compiled exploit and updated device.db file, just send me a PM and I will provide it to you.

Has someone found out what created the trouble?
Hello Guys, im also a Droid 4 user. I have seen such problems already before on a Xperia Mini Pro. I think this is a slider issue or a bad manufacturer thing. When i inspected the issue of the Mini Pro, I have found that the flex cable between the device and screen was broken. Probably because it was carried in the trouser pocket (The space between screen and main device where to low an the force broke the LCD Flex Cable between them). This can't happen on the PopUp sliders like the N97 / E7 and N950 because the flex cable dosen't need to move that much and is way better folded.
Maybe because the phone dosen't see a screen it also cant initialise the Frame-buffer with the screen size (the screen is not telling the size anymore).
I would have a look at the flex cable, a new costs about 20 $ at ebay but as you see on ifixit.com the Droid 4 is not that good repairable.
Success!

The broken flex-cable theory actually makes sense, I had this problem in the past with Samsung clamshell phones, and I actually hoped this issue would not exist anymore in the current day. It might also explain the phone slowly degrading more and more until it doesn't do anything at all anymore with the screen, it would fit in with the cable slowly wearing more and more.
I will try to check the cable to see if anything is wrong with it, however I would expect more people to run in to this problem, and till now I only counted 3 people who are all in this thread.

To give a better overview of the problem for people who might face this in the future, here is a photo of what the screen shows:
My next step is to take the Droid4 apart to see if the flexcable is ripped.

Hawkje said:
I will try to check the cable to see if anything is wrong with it, however I would expect more people to run in to this problem, and till now I only counted 3 people who are all in this thread.
Click to expand...
Click to collapse
Did this fix your problem? I've got exactly what your picture shows! Thanks for you help.

sprouty73 said:
Did this fix your problem? I've got exactly what your picture shows! Thanks for you help.
Click to expand...
Click to collapse
I still have to take the phone apart to see if the cable is actually ripped. I switched to a temp phone for the moment till I got the time to look at this again. Since there does not seem to be any other good qwerty phone I will try to fix my Droid and not replace it.

Took my Droid apart tonight, however the LCD cable did not have any clear rips in it, only some really small marks, which might as well have been the result of taking it apart.
Not sure what to do next, I will probably order a new LCD cable to see if replacing it will help. Till then my Droid will look like this...
https://twitter.com/ThiceNL/status/423243176149676033/photo/1

Courtesy update: Never bought the LCD cable, because it was almost 50% of buying a new (2nd hand) phone (from Ebay), so I went with that option. I do got a lot of spare parts now

Any Luck?
I have the exact same problem, has anyone figured out how to fix this white screen of death for the Droid 4? I'm guessing it's chipset related.

pjpjammer21 said:
I have the exact same problem, has anyone figured out how to fix this white screen of death for the Droid 4? I'm guessing it's chipset related.
Click to expand...
Click to collapse
If your screen looks like this
50% chance it's the LCD Flex cable
40% chance it's the LCD
10% chance it's something else

Thanks for the quick reply. I have a spare phone that is bricked but the screen works so I could do some parts swapping!

Same exact problem
I have ordered a refurbished droid 4 ($33!) and will put my old motherboard in that. If it works, it was the LCD cable, if it doesn't motherboard/ kernel issue.... I have not been able to figure any other way to get my data. PC recognizes the drives, but says they are empty, data recovery tools can't even see the droid, and I am not smart enough to figure out ADB... Will let you know how it goes...

I'd just use the refurbished droid unless you have a particular value of your current board. Mine works well.
Sent from my XT894 using Tapatalk
My comprehension skills failed me momentarily. Your data is valuable. I wish you the best outcome