Database Users

[Q] HELP!!!!!

I'm new for Galaxy S and I just rooted yesterday!
It was working fine and today I changed the system font styles.
And then problems have started!
I just rebooted the phone and then when the Samsung logo coming on, it stopped. so I did hard reset but nothing different.
So I searched google and found Odin way.
I followed the steps, it passed, then all I got were bunch of "force close" msg. like loop of force close!
so I tried Odin few more times, and then I was told to try with Vibrant Odin then I might get an error after that try Fascinate again.
So I did it.
Then more probems!!
When I turn on the phone, first thing I see is GT5000 something whatever for the Vibrant model name, and then I see Verizon Wireless.
Sometimes the phone just keep blinking( screen goes on and off and on and off)
so I turn off the phone turn back on, and then Im not able to make phone calls or network (airplane mode is on and I'm not able to turn it off)
I'm so stuck here.
Is there anyone who can help me??? PLEASE!! HELP ME!!! =[

Did you odin with phone or pda
Sent from my SCH-I500 using XDA App

I did it with PDA !!

sounds like you flashed vibrant firmware on your fascinate or vice versa...either way bad move

Yea, if you can somehow shoe horn the modem.bin, and falling up's fascinate images, you may be able to recover.
But if you flashed a rom from a different device, you may not be able to recover at all...
This is exactly how I would try to fix assuming that you didn't install voodoo.
1. Wipe in stock recovery (not in cwm, for some reason cwm recovery doesn't wipe)
2. Find a modem.bin for the di01. Flash that using odin.
3. Flash the system dump for di01.
4. Flash the kernel for di01.
5. Flash stock recovery as well just to be thorough.
If that works, then you should flash cwm recovery in odin and root again.

RacerXFD said:
Yea, if you can somehow shoe horn the modem.bin, and falling up's fascinate images, you may be able to recover.
But if you flashed a rom from a different device, you may not be able to recover at all...
This is exactly how I would try to fix assuming that you didn't install voodoo.
1. Wipe in stock recovery (not in cwm, for some reason cwm recovery doesn't wipe)
2. Find a modem.bin for the di01. Flash that using odin.
3. Flash the system dump for di01.
4. Flash the kernel for di01.
5. Flash stock recovery as well just to be thorough.
If that works, then you should flash cwm recovery in odin and root again.
Click to expand...
Click to collapse
good luck getting your phone to work again...^ that *should* work for you
but really people this is about the 500th thread on people flashing the wrong firmware on phones...geez

Yep, there are stickies for this. Maybe we should write a guide so that no one does it again. Wait, they already exist...

What's with all these threads? ..
How hard is it to read the instructions first before doing anything drastic?

http://forum.xda-developers.com/showthread.php?t=867648
This should help you. I fixed practically the same problem with this.
It's a magic wand, that'll take you back in time when you had your virgin unrooted fascinate

Soft brick trying to get into CWM Recovery?

I was wondering how it was possible to brick your phone (which somehow happened to me..) just by trying to get into CWM Recovery by doing the 3 button press.. As it is possible because it happened to me earlier today I was just wondering if it was a step that I did wrong.. Also I had nothing installed except flashing the Froyo EB01 modem which flashed successfully and than reflashed cwm recovery all which worked though I forgot I had to reboot fast or else samsung would replace cwm. So when I flashed a second time and than tried rebooting into cwm that's when it got stuck and bricked..
I got it solved earlier thanks to Adranalyne.
If anybody needs his thread for the all in one odin:
http://forum.xda-developers.com/showthread.php?p=9711053

Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App

Shadowchasr said:
Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Naw, it was stuck on the samsung logo screen for an hour-got bricked. But i fixed it .

Can someone explain how exactly you fix it? I am having that problem as we speak...

sengokubattosai said:
Can someone explain how exactly you fix it? I am having that problem as we speak...
Click to expand...
Click to collapse
Odin it back to stock. Either Dl01 or Eb01. Both files include everything for you to recover your phone ans be able to boot back up past the samsung logo.

Taking it back to EB01 every time can be a bit extreme. There are CWM tar files that you can use to just flash CWM with Odin. I've used them when my phone would not boot into recovery. Remember the best way to get to "Download" mode is to pull the battery and while holding the down vol button plug it into your PC. I know thats common knowledge but it's always good to put it out there. Other techniques can prevent Odin from establishing a connection.
I've even seen complete Super Clean tars up to 2.6. I don't remember where but when 2.7.1 bricked my phone I just used Odin to flash a 2.6 tar and my phone was back to normal. Now I use that ROM image instead of EB01 when an update fails.
I would stress that any ROM compiled by someone else is not going to be endorsed by the Dev that created the update. I just took a chance because I was already down and it worked great.

Stack after soft brick

Hello,
So I tried to help a friend with new vibrant that has soft brick,
After some tries, I have this the best situation that show this picture (attached)
But still the phone not boot and if i press reboot now the phone stack on infinity loop.
Thanks for the help

download AIO vibrant toolbox (the first pinned thread in developers forum) enter download mode and use odin to flash to stock (both are on that AIO vibrant toolbox).
To enter download mode, remove battery, connect the USB to your PC and your phone, press both vol + and - button and then put the battery while still holding the buttons. You will enter download mode and can use odin.

That looks like you're trying to go back from a voodoo lagfix setup. You need yo Odin jfd and ONLY jfd because it's the only released full Odin rom that will recover you from different partition formats.
Sent from my SGH-T959 using XDA App

tried flash this "T959UVJFD.tar"
after flash the phone is stack on vibrant and restart himself in 5 seconds

some one can help?

did you load the corresponding .pit file as well?

Sure, tried repartiton too.

At the same time?

yes, I think this is result of lagfix or something...

OP, you sound like you know what you're doing, so I can give you the short and sweet answer.
First, flash the Odin package from here: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Then pull your battery, reboot to dl mode, and flash the Odin package from here, selecting repartition this time only: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
That should get the phone back on a rooted, stock Froyo rom, with the modified recovery so you or your friend can then flash clockwork recovery, if you choose to do so.

Agree ^. Sounds like the best plan of action to me.

I think I have a 4g device,
anyone have solution for 4g phone?

Wwebmonster said:
I think I have a 4g device,
anyone have solution for 4g phone?
Click to expand...
Click to collapse
You should check over at the Vibrant 4g forums, you're currently in the Vibrant 3g forum.
Sent from my ZenDroid, meditating on the XDA App

okay that clears things up a little bit. My guess is you or someone else tried to flash either the update.zip or a rom from the regular vibrant forum. That will cause the issue that you are having, because the 4G is setup differently than the vibrant. Brick'd is right you need to head over to the 4G forum and see if they have stock files that you can odin to.

Thanks it was 4g, flashed 4g stock Tom and the issue fixed.
thanks again.
If someone have like this problem may be you got a 4g and not vibrant.
vibrant looks like 4g and from where I bought this device, the seller said that this is a vibrant.

HELP!!

So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?

You might have root but from the sounds of it the tab does not like the insecure kernel hence the yellow triangle on the logo screen. On a tab, I am not sure how to get around this.
Why not run stock and use TiBu to get rid of the bloatware until you can find a solution? Keep a Nandroid of bone stock then another for your custom settings...

Mardenator said:
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
Click to expand...
Click to collapse
What roms did u flash...?
Sent from my GT-P7500 using XDA App

Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.

ZangetsuNX-01 said:
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
Click to expand...
Click to collapse
Tried this, got the same result I've been getting..

I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.

Mardenator said:
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Click to expand...
Click to collapse
Next time please use the edit button.
I think I have an explanation as to why its crashing. The ISI-Galaxy Rom and P7500XWKK4 Galaxy Tab 10.1 / HC 3.2 ROM are for the P7100 model. Yours is the SCH-I905 model so the roms you tried to flash are incompatible.

Just realized that ZangetsuNX-01 is right, I've been flashing WiFi-only ROMs, not ROMs for the Tab 10.1 LTE. Downloading http://forum.xda-developers.com/showthread.php?p=17858660#post17858660 now, will flash and post results here asap.

UPDATE: got a leaked TW ROM to install via Odin and boot, posting this from the tablet. Added a screenshot for kicks.

BTW, for anyone with an LTE Tab, flash this via ODIN NAO!!!!
http://rootzwiki.com/topic/10463-ro...x-leak-build-for-vzw-galaxy-tab-101-lte-only/
It's unrooted, with stock recovery, but you can follow the directions on the page to get root, it's simple. Just Odin a recovery .tar file, go to recovery, flash SU zip, and voila. Running it at 1.4GHz max, 1GHz min, and it's awesome. TouchWiz is also a nice step up from stock HC.

@Mardenator
your screenshot a looke liek from my adwluncher from my tab...

Lol I'm using ADW Ex.

ok i dont untersant waht you with them post, sorry.

Conan179 said:
ok i dont untersant waht you with them post, sorry.
Click to expand...
Click to collapse
I'm not sure what the question here is, but I was suggesting that if you have an LTE Galaxy Tab 10.1, you should flash the ROM that I provided a link to. It's a good ROM, and I've been running it for 2 days now.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

[Q] Hung boot after font change

I must humbly ask for everyone's help. I bought a Galaxy S3 (Sprint) today and rooted no problem. I downloaded font changer and Rom Toolkit. I changed a font and clicked "reboot" and the phone hung on the reboot screen--after the sprint logo and says "Samsung" with the blue light going up and down in intensity.
I tried a cache clear and data wipe, neither of those worked. I also tied reflashing the root ROM. That didn't work.
My most recent steps were to flash the stock recovery and stock ROM. It still hangs. I can get to recovery and am able to flash with ODIN. What should I do next?!
If nothing else, is there a way to reset the flash counter so I can maybe get Sprint to fix it? The only way I saw is to download an app, which won't work.
Any help is appreciated, I've tried all that I could think of.

1. Wrong section. .
2. Do your homework, changing fonts on ics causes boot loops. Gonna a have to flash to stock with Odin sorry :/
3. Triangle away.
Sent from my GT-I9000 using xda app-developers app