Database Develop

[Q] Phone is a brick after deleting framework-res, help?

K so like an idiot i deleted framework-res, and now my phone turns on to a black screen. I've tried to reflash it with odin and odin 1 click, but it always gets stuck at "file analysis". I don't get why because I used odin 1 click to install froyo in the first place so I know it works.
Anyway, I have no idea what to do, as I can't get any files on or off my phone because ADP will always say the device is not connected.

if its stuck at file analysis keep fiddling until it goes past that for instance plug in into download mode with it open and then unplug and replug it in. just keep trying.

i've been trying for hours... rebooting.. reinstalling.. everything. it won't get past File Analysis...

Are you trying to use the odin 1click to flash back to jf6? That might work.
Sent from my SAMSUNG-SGH-I897 using XDA App

droidal said:
Are you trying to use the odin 1click to flash back to jf6? That might work.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
nope, still hangs at File Analysis

i have done the same and now back up i used an old odin to go back to original stock and then updated to froyo after. If you can use sdk adb reboot recovery and fromat your sd card then try odin again this worked for me

maybe try restarting computer. make sure you dont have anything adb related running. pull battery. start odin one click. put battery back in. hold vol-up and down at same time(just the vol. buttons no power) plug in usb from comp. to your phone while you still have the vol. buttons held. should be in download mode. click start.
and if you wanna try pushing a new framework, i guess you could try to boot into recovery and adb should see it then as debugging mode is auto on in recovery mode. let us know.

sbtim said:
K so like an idiot i deleted framework-res, and now my phone turns on to a black screen. I've tried to reflash it with odin and odin 1 click, but it always gets stuck at "file analysis". I don't get why because I used odin 1 click to install froyo in the first place so I know it works.
Anyway, I have no idea what to do, as I can't get any files on or off my phone because ADP will always say the device is not connected.
Click to expand...
Click to collapse
Are you using 64 bit Windows 7? I am and had a similar problem. On my original attempts to flash my phone with earlier versions of Cognition, I learned that if you don't disable the lagfix, you can have a problem. Assuming you used one I hope you disabled it. I also used odin 1-click at the time and it didn't work terribly well, mostly due to the voodoo lagfix ext4 filesystem.
Secondly, I've also found that it's best to go into download mode using the following method:
I do a battery pull, remove sim and sdcard (if you have one), put battery back in. Make sure your USB cable is plugged into a USB port on the motherboard, not one of those front USB ports (they sometimes don't get enough juice, you wouldn't want the device to disconnect in the middle of a flash). Hold volume up/down and plug in the USB cable. Odin one click should recognize the phone is hooked up to a COM port. At that point, you click the start button and it flashes. It should not take more than 1-2 minutes to flash. If Odin looks like it it is not working, rather it sits at Verifying or does not actually move at a brisk pace, it's not going to work. You can let it sit for hours and it will never flash. If this happens, do the battery pull and try again. My first time doing this was rather nerve wracking as i thought i bricked my phone. Had the screen with the phone/exclamation mark/computer and the computer did not detect my phone via USB. I've seen people who say reinstalling the Samsung drivers or rebooting the computer or switching USB ports might help as well.
Ever since i figured out the above, i've been able to flash my Captivate on Win 7 64bit without a hitch. Currently running the latest build of Cognition 2.2 and loving it.

I've done all of the above and Odin hangs on Verifying, ADB gives the same error message on every "ADB" command : "error: device offline: (while in recovery mode)
My computer/Odin does recognize that it's plugged in, but it won't mount and let me into the SD card or format it, etc.

edit : fixed
weee

sbtim said:
edit : fixed
weee
Click to expand...
Click to collapse
You should post what you did to fix it in case someone has the same issue
Sent from my SAMSUNG-SGH-I897 using XDA App

Yes he should.

What did you do to fix it? Do tell.

10 bucks says he succeeded once he read the directions properly.
Reading is hard, that is why so few people do it.

Same exact thing happened to to me 2 days ago. All I did was:
1)take the battery and SIM card out, wait a few seconds,
2)run Odin3 on my PC and hookup the USB cable to the phone while still off
3) hold both Volume buttons down while phone is off and connected
3)at the same time, slide in the battery with 1 finger or have someone do it
4)keep volume keys held down as the battery is installed and my phone turned on straight into download mode
5) phone pops up in Odin3 and just click Start, flashed to stock JH6
I am 80% sure I wasn't holding the power button while holding the Vol keys. If that doesn't work above ^^^ hold all 3 buttons and it should go into download mode.

so.. I fubard framework.apk trying to get teh circle battery mod on my phone (it just hung forever and *poof* black screen o' nothing after I pulled the battery)
So.. I'm following the directions but windows keeps finding the phone as some type of crazy serial device and is asking for drivers ... so I'm fux0red methinks.
Any help is appreciated - but I think I did a real number on this thing.

Ok... these are the steps I've done.
Shutdown the device.
Pulled battery, Sim, SD Card.
Popped the battery back in.... didn't power it up.
Turned on Odin3
Popped the USB cable into the phone while holding both volume buttons.
I get the lil triangle.
... then I get a windows message stating "SERIAL GADGET" and the XP wizard comes up looking for drivers. It doesnt find anything of course.
So.. I rinse and repeat and it can't find the device.
So what am I missing o wise XDA folks?

avgjoegeek said:
Ok... these are the steps I've done.
Shutdown the device.
Pulled battery, Sim, SD Card.
Popped the battery back in.... didn't power it up.
Turned on Odin3
Popped the USB cable into the phone while holding both volume buttons.
I get the lil triangle.
... then I get a windows message stating "SERIAL GADGET" and the XP wizard comes up looking for drivers. It doesnt find anything of course.
So.. I rinse and repeat and it can't find the device.
So what am I missing o wise XDA folks?
Click to expand...
Click to collapse
Have you searched for the drivers and installed them on your xp machine?
I'm still a noob so I'm not sure of it will help.
Please though, once you get it sorted please post your solution here for the benefit of those whip comer after you.
Good luck!
Sent from my SAMSUNG-SGH-I897 using XDA App

http://forum.xda-developers.com/showthread.php?t=788093
Get the right drivers if you havent already and find the USB port that works. Post 8 above is very good. On my netbook, only one of the three usb ports works for the captivate, i've marked it since with a happy face.

Ok.. at home now on my Win7 machine - all is good in Odin restore land...
Except - I flash using the Odin 1 Click and still boot to a black screen.
I think because I had the Voodoo lagfix on it - it won't format correctly and load the rest of the ROM onto the SDCard

[Q] Bricked Verizon tab, black screen of death after trying to flash stock firmware

Well, I've bricked my three week old Verizon galaxy tab trying to flash the stock firmware back to the device to try and get the recent Verizon update working, which has been failing consistently. I've thoroughly read through every thread on the forum I could about the black screen of death, so I understand there's a good chance I'm pretty screwed here. I have a couple more questions on the subject, but I understand that I might not be able to get answers for them past the information that's already available.
I'll start by describing my setup and how the flashing process went wrong. I was using the stock Verizon ROM with Boushh's Voodoo Plus kernel v3, converted to ext4 of course. After the recent Verizon update failed to install on my Tab I followed through all the suggestions on the CDMA VZW Tab update thread, downloaded the update zip, put it on the sdcard, ran from rescue manager, unrooted, reflashed stock, wiped data and cache, re-ran from rescue manager at first boot... nothing worked. Things went really wrong when I tried flashing the entire ROTO backup of the Verizon stock ROM. I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
* I've seen it suggested that the tab be left to drain for days or weeks, but not many reports that this worked out in the end. My battery was at about 45% percent when this whole thing went down. Should I even bother waiting? My only alternative at this point is to send the thing to Samsung for repairs which breaks my heart. Verizon won't replace it as I've had it for over two weeks.
* Could a homemade USB jig help me in this situation? I have some soldering experience but I heard that it won't help if the screen won't turn on. Ideally I'd buy it online, but I couldn't find one for the Galaxy Tab on ebay.
That's it I guess, but any information you can offer pertaining to this problem would be appreciated. Thanks!

to be honest, i do not know why people think they can brick the tab.......the only way is to throw it from a building.
Just go to overcome forum and follow this (i 'bricked' my tab a 1000 times):
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
1.Get a stock rom package (any of Rotohammer's firmwares will work)
2.Get P1_add_hidden.zip attached to this post and extract the P1_add_hidden.pit file
3.Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
4.Put P1_add_hidden.pit in Pit slot
5.Check repartition box
6.Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
7.After this, the Tab will reboot normally. Shut it down and return to download mode.
you also get the link for the p1 file you need.......easy

This sounds like very useful information, thank you. I'll definitely do this if I can get the Tab to respond to anything I do, which I can't so far. It won't turn on regardless of what volume button I press or not press. I'm pretty sure I had it connected to the PC while trying to put it in download mode just to see if it would be recognized as USB device despite the screen not turning on, but I'll try again to make sure when I get home.
Edit: Yeah, no luck. Not recognized as a USB device, which makes sense seeing as the screen doesn't even turn on.

I am having the same issue... My daughter put my computer to sleep while I was flashing back to stock using heimdall. Any luck getting your Tab to power on?

nirslsk said:
I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
Click to expand...
Click to collapse
same problem

If your tab is showing any sign of life then you are not bricked and just need to keep at it until you find a solution. When you have exhausted all other resources you can send it off to get it fixed. I ended up bricking my tab when a flash was interrupted to the point that there was no sign of life at all. I found someone here who could fix it for $50 and had it back within the week working as it should. I highly recommend his service as a last resort.
His screen name is connexion2005 and here is a link to his profile.
http://forum.xda-developers.com/member.php?u=1602851

[Q] How to remove CM7 and install a rooted stock ROM on captivate?

Hi all,
I installed CM7 the latest nightly build on my captivate. How do i get to my old ROMs (cognition, serendipity...). I have read a lot of threads, and also have tired few solutions, but I have no clue why my odin hangs at "Donot Turn of the Target"
I waited for a long time, on that message, probably half an hour and then i had to pull out the USB cable. Now i am stuck at < phone + ! + computer > screen.
The one click odin i am using is from the following thread...
http://forum.xda-developers.com/showthread.php?t=731989&highlight=odin+one+click
Can anyone please guide. Thank you.

I have no idea, what happened. I have done this some 10s of times, and everytime it got hanged at <DO NOT TURN OFF THE TARGET>. But suddenly it worked.
What all i did --
0. Download 1 Click Odin from
http://forum.xda-developers.com/showthread.php?t=731989&highlight=odin+one+click
1. Took out the battery and wire of the soft-bricked phone.
2. Held power - and + button together, and inserted the usb cable.
3. Inserted the battery, and within a second phone entered <Download Mode>.
4. Removed the usb cable.
5. Started the Odin. (With NO administrator mode and NO windows XP compatibility). That is I just double clicked the ODIN in windows 7.
6. Attached USB wire back to the phone.
7. Phone detected on one of the COM Ports.
8. Pressed Start button.
This all I have done some 10s of time... but the only thing extra i did this time was --
9. Cross your hands, and genuinely pray... that it works.
and it worked.
It seems like 9 is the most important step.
I hope this helps others too.

Try odin again. The one you used should work. Get your phone into download mode and run odin. If you can't get download mode, try and see if odin recognizes your phone anyway with the phone ! computer screen. If it does, flash oneclick from there. That will give you stock eclair.
Sent from my SAMSUNG-SGH-I897 using XDA App

Phone should still be able to be flashed using Odin. I'd fire it up again and try. the phone-!-computer.. is another download mode, an "unofficial" download mode

bricked help

hey, i am posting this for a friend who bricked his phone and doesn't know much about it..
he was running serendipity 7 which is a jvo rom, and tried flashing the pauldiddy remix theme, which says is only meant for jvp and jvq roms. i used a jig, to get the phone into download mode, and the computer detected it when i plugged in the usb. but when i tried to use odin one click to go back to stock, it would get stuck at the "Do not turn off target". im not sure if anyone knows a fix for this, or if i should try using the method from this thread http://forum.xda-developers.com/showthread.php?t=1153310 instead, but i figured i would ask before i messed around with it too much
any feedback would be appreciated

how long do you wait before throwing in the towel? it does take a minute or two to finish it's task ? And are you opening Odin before you hook the usb to the phone ?

waited probably about 5-10 minutes. yeah i opened odin first, and it detected the phone and showed the Added! text

Just out of curiosity, what is the phone doing right now that you're trying to use Odin on it?
The reason I ask is that if you can get to CWM recovery, you might just be able to re-flash the rom (assuming it's a wipe package) and it would take care of the issue.

i cant get into recovery, but i can get into download (using the button combos). not sure if that means anything either

Well keep trying, and you might want to try the odin 1 click. I have a Cappy that got dipped in the pool, it would not go into recovery at all but I could get the download all the time, But it kept getting stuck at the i896 screen or the AT&T screen (odin 1 click) after 3 weeks of trying and having to wait 3 days for it to come out of it's coma it now works fine. If you try the odin 1 click it might work for you just make sure it's not ver 10.10 I think (look under battery). What screen does it go to once you press power IE: black screen rogers screen etc. ?

ive tried using odin 1 click.. like i said, the first time odin actually picked up the device, but it wouldnt get past the "do not turn target off" prompt. but i tried plugging it in again, and now it doesnt seem to even pickup the phone. when i when i try to boot the phone, its just a black screen. thanks for the input though

[Q] Stuck in a boot loop - now just stuck

Hi has uploaded ICS 3333, and it worked for a few weeks then today when it in airplane mode I took it out my pocket and it was in a bootloop mode.
Samsung --> Semaphore
So decided that I would retry installing ICS starting with 2.3.6 using ODIN but it crapped out, and now it's only allowing me to go into download mode. It said failed, retried a few times but I did not record the exact error (aaah)
As it is allowing me to get to download mode thought that would be ok, but when I connect it to the PC, it is not recognised at all now. So ODIN does not seem to work..
Im sure you are going to say just install a specific driver or something, but I don't what it would be. The PC recognised the mobile earlier, but just not now.
Update: Now the Phone is fully dead, and does not appear to be charging at all. So maybe dead because the battery is flat.
I've updated ROm's a few time's and always had the recovery mode to recover things and even have the USB item which should allow to move into download.
Any idea's folks.
thanks in advance... Bill
I was following this initially
1st Install this - this flashes Andoid 2.3.6 first
I downloaded I900XXJVU_I9000OXAJVU_OXA.rar
Disconnect your phone if it’s connected to PC. Then Switch it Off. Wait 5-6 seconds for vibration to confirm complete switch off.
Now, put the Galaxy S in “Download Mode” — press and hold these keys together: Volume_DOWN+Home+Power until a screen saying ‘Download Mode’ comes up.
Open Odin (from step 5) — Odin3 v1.7.exe.
Connect your phone to PC now. You should get the message “Added! !” under the Odin’s message box in the bottom left. If you don’t get “Added! !” message, than probably there is a problem with drivers. Make sure you’ve drivers installed (links given above under heading ‘Pre-Installation thoughts’).
Now, in Odin, select these files at respective tabs (for visual help, see the screenshot at step 11 below):
a) Click the PDA Tab, and select CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 (from step 3.1)
b) Click the Phone Tab, and select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5 (from step 3.3)
c) Click the CSC Tab, and select GT-I9000-CSC-MULTI-OXAJVU.tar.md5 (from step 3.2)
d) Click the PIT Tab, and select s1_odin_20100512.pit (from step 2)
Make sure the ‘Re-Partition’checkbox in ODIN is selected. Also, Auto Reboot and F.Reset Time checkboxes should be selected too. Leave everything else on Odin untouched.
Double check everything said in step 10 and 11 above. Your Odin’s screen, after selecting all the files and ticking and not-ticking the checkboxes, should look like this:
Screen capture can be found at weblink
Now, hit the START button to begin the flashing process. When it finishes, your phone will automatically reboot, upon which you can unplug the cable. Plus, you’ll get a PASS (with green background) message in the left-most box at the very top of the Odin. ***I got a fail here***

read that kies is different from usb drives. Not 100% sure that would be the issue as could connect previously with ODIN, which I think means the drivers are ok.
Next question that I have, if the battery has gone flat, and it does not appear to be charging either with USB or wall mounted, where do I go from here...
Im not a total newbie, and have been on DarkyRom for most of the versions, just this boot loop has got me big style... Can anyone give me a few idea's of what to try...

You might try a direct battery charger for which you won't need your battery to be in phone and one charged you can try the usual things as flashing through odin.

Try to install another driver..since i use ics for my sgs..pc wont recognise my phone..i install s2 or nexus driver ( mtb driver ) and it works perfectly as before..

If you have flashed ICS then you will need to install the GNexus drivers that are contained here
Try and get your hands on a external charger as erpurohit has suggested or borrow a friends battery
Flashing back to stock or Darky's 10.2 should get your phone going again

Thanks folks for responses (did the button as well).
Did not need extra charger / battery. Sat it on charger all night with no change... So tonight when I came in tried one more time to put into download mode and it worked..
Tried connecting it to ODIN and it worked fully so installed Gingerbread stock and away the baby went.
Not sure root cause, but was not drivers.
Won't be installing ICS until it becomes more stable and does not put phones into boot mode without a simple way out.. (never say never though)
Cheers Anyway..