Database Develop

[Q] Pretty sure I bricked.

So the story goes I installed Assonance on my Captivate from Official 2.2. Started having problems with the phone being stuck in Landscape mode. This problem followed when I installed Firefly. So I decided to try to go back to JF6 and clear everything. Couldn't get into download mode so downloaded a CMW flashable zip of JH7 and after installing the phone just sits at the AT&T World Phone screen. Can't get into Download mode with volume down + power or volume up down + usb. Need advice to try to get phone fixed/replaced, i'm stuck using a BlackBerry Bold. Any help please?

Google usb jig
CM7

Figured
Yeah that's what I figured. The only thing I'm curious about is the landscape mode issue following me around on different ROMS. After I hopefully unbrick the phone do you think it would be worth taking it to ATT?

Go to radioshack, 99 cents, use the video below for reference. You need 3 100k OHM resistors, and they run .99 cents for 5 of them. Use that to kick it into Download Mode and reflash. As for returning it to AT&T, if the orientation problem continues, I would if this doesn't fix anything.
http://www.youtube.com/watch?v=D0aoabVtPJ8

What Kernel did you flash before everything went haywire? This is a classic sign of an i9000 kernel being flashed to a Captivate.
Forget download mode for the moment, can you get back into recovery?

It's true. But, theres no reason the kernel wouldn't flash over during CWM. Not to mention, if that were the case it would also almost certainly display other i9000 kernel issues, like external SD mounting and headphone logic. I think something else is the culprit here.

geokhentix said:
It's true. But, theres no reason the kernel wouldn't flash over during CWM. Not to mention, if that were the case it would also almost certainly display other i9000 kernel issues, like external SD mounting and headphone logic. I think something else is the culprit here.
Click to expand...
Click to collapse
Sounds like lagfix present in Firefly was not disabled before flashing to stock, hence an ext4/jfs file conflict. OP, please let me know if you can reboot to recovery.

clemmie said:
Sounds like lagfix present in Firefly was not disabled before flashing to stock, hence an ext4/jfs file conflict. OP, please let me know if you can reboot to recovery.
Click to expand...
Click to collapse
hmmmn I agree. too many bricked phones not disabling lagfix and clock default values in their kernel when flashing back to stock. seems many forgot that procedure. every dev always states here to disable lagfix when flashing new rom and set back default clock values in current kernel. the very first step neglected PITA to troubleshoot.

Before you go and buy anything, did you try this method (sorry, if you said you did)? It always works for me, especially at the "Phone--!--Computer" screen.
FROM: How to unbrick the totally bricked captivate. [Click the > after "Originally Posted by thekurrgan" for the full source.]
thekurrgan said:
So far this has been the only sure fire method I've found to 100% get around any brick situation regardless of firmware, etc. This only works for the captivate, not any other galaxy s variant.
Situations: phone-!-Computer / no download mode
Black Screen / RST_STATUS 0x0
Procedure:
1. Remove the battery, external SD card and SIM card.
2. Wait 10 seconds.
3. Open odin3
4. Connect usb cable.
5. Hold volume up + volume down + Power.
6. Insert battery.
7. Release POWER BUTTON ONLY.
Click to expand...
Click to collapse

If he was using odin one click it repartitions automatically. If full version as long as repartition is clicked odin gets rid of the lag fix.
My point is that as long as repartition is enabled the lag fix is not his issue
CM7

mcord11758 said:
If he was using odin one click it repartitions automatically. If full version as long as repartition is clicked odin gets rid of the lag fix.
My point is that as long as repartition is enabled the lag fix is not his issue
CM7
Click to expand...
Click to collapse
It says nowhere in the OP that he used one click; as a matter of fact:
jonp92 said:
Couldn't get into download mode so downloaded a CMW flashable zip of JH7 and after installing the phone just sits at the AT&T World Phone screen.
Click to expand...
Click to collapse
I've seen this many many times, and it is usually a result of a non-disabled lagfix or OC kernel. I've been down this road with a few people. He may be trying to use one-click now, but without being able to get into DL mode he's stuck. I'm trying to help him get into DL mode, as are other posters. Let's just focus on getting him to DL mode.

buy this:
http://cgi.ebay.com/ws/eBayISAPI.dl...69781&ssPageName=STRK:MESELX:IT#ht_623wt_1139

[Q] Scrambled TV-like screen during boot or in CWM Recovery

Hello everybody. First of all, I'm quite new to the whole android world as I got my Galaxy S only three months ago. But I want to take full advantage of it's power so I decided to root it quite quickly. And now I had stumbled upon a problem and had no luck in finding a solution. That's the reason for this thread.
I went through other topics in this forum and it seems no one ever had a problem like this.
I've installed a RomKitchen custom XXJVB rom with Chainfire's kernel (CF Root XW XEE JVB v3.1 CWM3RFS) according to the instructions provided there - I flashed CWM 2.5 with Odin, then updated from CWM Recovery to Gingerbread.
In general, after doing this, everything works fine, the phone got super-fast, no issues there. However, now, during boot the screen displays a TV-like scrambled signal (like white noise... only it isn't white). It's hard to explain so I attached a picture.
It's like the whole screen is covered in coloured pixels. Sometime's a line of pixels moves. A similar thing happens when I try to boot into recovery - it boots but the display is all scrambled. The recovery menu works (when I use the volume buttons the pixels on the screen change their position) but I can't see a thing.
I tried virtually every solution I could think of - I wiped everything, did a factory reset, installed everything again. Still the same. When I revert to stock Froyo 2.2.1 this doen't happen anymore. But I prefer Gingerbread over Froyo.
So, have anyone here seen a similar problem and knows how to fix this? I would be very grateful for any pointers
EDIT: Silly me, guess I haven't searched hard enough :/ It seems I'm missing the new bootloaders.

hardoc said:
EDIT: Silly me, guess I haven't searched hard enough :/ It seems I'm missing the new bootloaders.
Click to expand...
Click to collapse
Yeah, that's it.
Flash JVB stock with bootloader. Load your cooked rom onto internal sd card. Then flash the speedmod kernal in Odin with auto reboot unchecked. Pull the battery, then boot the phone into recovery, and flash your cooked rom.

electrotune1200 said:
Yeah, that's it.
Flash JVB stock with bootloader. Load your cooked rom onto internal sd card. Then flash the speedmod kernal in Odin with auto reboot unchecked. Pull the battery, then boot the phone into recovery, and flash your cooked rom.
Click to expand...
Click to collapse
I am getting this scrambled screen at the beginning of reboot after flash to serendipity VII. My phone will come up fine after the scrambled screen. But I cannot see the cwm page if I selected "recovery". Any help? Is this the bootloader being corrupted? Thx.

hi i do have a same problem in my htc desire hd its not only in boot menu its also have a problem while phone is booted. if i press hardly in the side of the phone its became scrambled,
please help me how to solve this?
htc desire hd
rom - rcmix 3d kingdom v2.0
clockwokmod recovery v.3.0.2.6

Hi guys I'm having similar problem with my galaxy s but my scrambled screen looks different but same thing, phone works but I can't see anything on recovery, please help us out tech God's
Sent from my GT-I9000 using XDA Premium App

steve57925 said:
Hi guys I'm having similar problem with my galaxy s but my scrambled screen looks different but same thing, phone works but I can't see anything on recovery, please help us out tech God's
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Flash this bootloader through odin/heimdall, tick Update Phone Bootloader and click FLASH
http://www.chameleonwebhosting.com/galnetmiui/EZboot-GingerBread-1.0.tar.md5

[Q] Tab totally unresponsive.

I have a Verizon Galaxy Tab 7-inch with WiFi and 3G running Android 2.2 (Froyo). I mistaking tried to flash the new Android 2.3.3 before realizing it was only for GSM phones. I followed all the instructions using Odin3 (1.7) and everything looked like it worked except it never rebooted and I never got it into the Recovery Mode. I was still able to get in Download Mode so I tried to find a compatible 2.2 ROM to flash. I flashed the Roto JME rom, it didn't reboot. I flashed P1000NUBJM2_P1000NUBJM2_P1000NUUBJM2_HOME and it didn't work. Odin3 seemed to install these, I always got PASS. Now my Tab is totally unresponsive. Odin3 acts like it's installing but I can't get the Download Mode screen anymore. How do I get it back to factory or some working system? I don't expect to save anything I've loaded, I just want it to work again. HELP. Thanks.
P.S. If I can't fix this, who do I take it to to re-install the system? I got it from Verizon.

Can you get it into recovery mode? (Turn off, then Power + Volume UP)

No success
No, nothing I do will show anything on the display. I can't get into Recovery Mode or Download Mode. However, when I'm hooked to the computer and press the correct buttons to turn on/off or Download Mode, I hear the computer beep indicating it sees the USB and the yellow COM widget in Odin3 lights up and says it's up and in Download Mode. I can then flash it and it says PASS. I also just tried Heimdall and it also seemed to successfully flash the original Verizon SCH-I800_VZM firmware. Nothing displays when I try to go into Recovery Mode. I don't even see the picture of the battery when I plug it into the wall. Have I somehow trashed by screen?

Hi ! I got the same problem and now my Tab totally bricked...

Samsung just needs to give us the files and software to load these tabs back to stock! That would end the return issue for the carriers and let us unbrick them. Like any other device, there is a way to fix it without having to send it back.
Sent from my ADR6400L using XDA Premium App

[Q] Darky's 10.2 RE causing softkeys to screw up.

I just used Odin to flash Darky's 10.2 RE (with plans to flash 10.2.2 and DarkCore 4.1 over it) from the Stock 2.3.5 with Bootloaders and before I did anything else to the phone, I checked to see if the softkeys are acting the way they should. This is because I tried to do it straight from Darky's 9.5 ROM and it caused the Home key to act like the back button, the Back key to act like a left arrow button, and the Search key to act like a right arrow button. The menu button is acting normally. As I said i used an Odin One-Click to flash back to stock and it fixed the softkeys. After trying AGAIN to flash to 10.2 RE the softkeys are acting EXACTLY the same as before.
Has anyone else experienced this, and is it a bug or am I doing something wrong here?
I thought possibly i need to use Odin to flash 10.1 first.
I'm going to use the One-Click to flash back to stock until I get a solution.
Thanks in advance everyone!

kevnuke said:
I just used Odin to flash Darky's 10.2 RE (with plans to flash 10.2.2 and DarkCore 4.1 over it) from the Stock 2.3.5 with Bootloaders and before I did anything else to the phone, I checked to see if the softkeys are acting the way they should. This is because I tried to do it straight from Darky's 9.5 ROM and it caused the Home key to act like the back button, the Back key to act like a left arrow button, and the Search key to act like a right arrow button. The menu button is acting normally. As I said i used an Odin One-Click to flash back to stock and it fixed the softkeys. After trying AGAIN to flash to 10.2 RE the softkeys are acting EXACTLY the same as before.
Has anyone else experienced this, and is it a bug or am I doing something wrong here?
I thought possibly i need to use Odin to flash 10.1 first.
I'm going to use the One-Click to flash back to stock until I get a solution.
Thanks in advance everyone!
Click to expand...
Click to collapse
You need a reoriented kernel. It's acting as though you have an i9000. If auto rotation works, then you do have one but need to remap the button keys. I made a thread a while back on how to do it -- http://forum.xda-developers.com/showthread.php?t=1325867
Edit: after reading your post again it sounds like you're saying this happened before you flashed anything over the RE? If so, no wonder. You still need to flash the captivate kernel which should be reoriented and have the button fixes

mikel.canovas said:
You need a reoriented kernel. It's acting as though you have an i9000. If auto rotation works, then you do have one but need to remap the button keys. I made a thread a while back on how to do it -- http://forum.xda-developers.com/showthread.php?t=1325867
Edit: after reading your post again it sounds like you're saying this happened before you flashed anything over the RE? If so, no wonder. You still need to flash the captivate kernel which should be reoriented and have the button fixes
Click to expand...
Click to collapse
I kinda suspected it was a kernel issue. Since my old boot screen displayed I9000 then I897 afterwards. So I should ignore the button issue until I flash 10.2.2 over it..or would that be darkcore, THEN 10.2.2? I think the autorotate did work btw. I'll try it thanks.
PS If that's the case the instructions need to be changed to tell people to flash a cappy kernel after the 10.2 RE base right?
Sent from my SAMSUNG-SGH-I897 using XDA App

kevnuke said:
I kinda suspected it was a kernel issue. Since my old boot screen displayed I9000 then I897 afterwards. So I should ignore the button issue until I flash 10.2.2 over it..or would that be darkcore, THEN 10.2.2? I think the autorotate did work btw. I'll try it thanks.
PS If that's the case the instructions need to be changed to tell people to flash a cappy kernel after the 10.2 RE base right?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The reason it showed i9000 then i897 is because you have i9000 bootloaders which is okay and shouldnt affect button mapping. You should flash 10.2.2 then the kernel

Okay so..i kinda goofed up a little cause i pushed the kernel with Odin after 10.2 RE. I went ahead and tried this before checking for another post. I decided to flash 10.2.2 over that and pushed the kernel again with Odin. Only key that doesn't work now is the home key. I'm going to start from scratch tomorrow and do everything in the right order.
Thanks for your help!
Sent from my I897 using XDA App

Well it sounds like everything is working but that I think you should just try remapping the home key it's not too hard and will save you the reflashing trouble

Ok, is there a thread that shows how to do that?
Sent from my GT-I9000 using XDA App

Yes. The thread I posted above. Or i might also suggest reflashing the rom but wiping data amd cache in cwm before flashing the rom.
Also dont forget to press thanks if ive helped you

I would have already but there's no thanks button in the xda app
Sent from my GT-I9000 using XDA App

mikel.canovas said:
Yes. The thread I posted above. Or i might also suggest reflashing the rom but wiping data amd cache in cwm before flashing the rom.
Click to expand...
Click to collapse
Also I thought I'd mention that I can't go directly from recovery mode to download mode. The button combos to get into download mode from the phone being turned off aren't working, probably for the same reason everything else is screwed up. I have the reboot the phone and use the enhanced power menu to reboot into recovery mode and download mode. Not sure if that messes with clearing the cache and/or doing a factory wipe/reset or not..not being able to go directly from one to the other, that is.

Try flash the new rom with Darky rom tool. The tool can be downloded from market.
Darky's rom is a combination of Captivate and I9000, the installder will check the model by original build.prop file.

Recovery Mode, Download Mode and Bootloader wont boot

Hi,
I am fairly advanced in this stuff and generally i know what im doing, i used to have a HTC Desire HD and was always changing roms etc.
I have had a Galaxy S I9000 for a month or two now and recently i flashed Vanilla Rootbox ( http://forum.xda-developers.com/showthread.php?t=2122727 ) just like any other rom using CWM recovery as i always have done.
After finding i want to change roms, i am unable to boot into recovery mode, download mode and even bootloader.
I have tried using the key combinations to access all of these modes, ive tried using adb to access all three and whatever i try and do it just boots up normally to vanilla rootbox as if i had just booted up normally.
Just incase it means anything, when i try and boot into these modes, the Samsung Galaxy S I9000 Screen (the boot screen before the Vanilla Rootbox one) shows up for about 4-8 seconds and then disappears for not even a second (the screen just goes black almost like it tries to load the mode but then redirects itself to a normal bootup) and then shows the same screen again for a further few seconds, before going to the Vanilla Rootbox boot screen, from there it just loads up normally.
I have searched all over the internet for a solution and there isnt even any posts with the exact same problem.
I really would appriciate any help with this as i am stuck with this rom which in my opinion is awful and drains the battery on my device.
Thanks, Jake:fingers-crossed:

have a read here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1

slow--welder59 said:
have a read here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
Click to expand...
Click to collapse
nope, still no luck
i think it has something to do with the rom as i have had no trouble with other roms, do you know if there is a way to flash a rom without using bootloader, download mode or recovery?
thank you very much for the response by the way

Mate you tried a USB jig?

Sorry for late reply, bought a Jig in the end as they were down from £10 to £1.60 on amazon! worked like a charm, straight into download mode, back to stock rooted and now back up and running rooted with cyanogen 10.1 nightly, very nice!
Close Thread, - JIG IS THE ANSWER.