Database Develop

[Q] Samsung galaxy S vibrant stuck on "S" screen at boot

To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.

I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.

Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.

Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.

Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.

I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.

called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.

[Q] Stuck at Samsung Logo... Repartition phone?

So, to make a long story, short, for the past couple of days my phone has been soft-bricked... It first happened when I attempted to flash dmodv6 in CWM. Everything looked good throughout the installation, however, when I rebooted my device, I got stuck in a boot loop where It would say "Samsung Galaxy S III GT-I8190" for a few seconds, the screen would go black, then say the same thing again... over and over and over...
After a lot of trial and error because of NOT making a nandroid backup via CWM (stupid, I know - I had made one via Titanium Backup and thought that might be good enough), I finally was able to boot. Thanks to xXPR0T0TYPEXx, I was able to flash another rom by puting my external sd card into another phone, loading another rom onto it, and putting it back in my phone. I now had Cyanogenmod10 and was able to boot back up.
I attempted to restore the Titanium Backup I had made with this new rom (stupid again, I know) and it made almost every service on the phone stop working... I desperately wanted just to get back to square one - to install stock firmware and go from there. I followed tys0n's guide on flashing stock recovery then attempted to install stock firmware... All seemingly went well - I booted up, got past the initial "Samsung Galaxy S III GT-I8190" logo and finally got hung up at the "Samsung" logo. I left it one while I went to sleep, just to see if it would eventually work... I woke up and it was still the same. I tried flashing different version of the same stock firmware but it all ended in getting hung up at the "Samsung" logo.
A major problem is that I absolutely CANNOT flash a custom recovery via Odin - it just will NOT work. Everything looks good on Odin's end - I PASS, get the (succeed 1 / failed 0) thing but am sent to stock recovery every time I do the 3 button combination. I've tried many version of CWM and TWRP.... NOTHING. I've even unticked the "Auto-Reboot" button in Odin and pulled the usb cable and battery upon completion but, but nothing ever works. The only way I was ever able to get CWM on my phone in the first place was by an in-phone app... Rom Manager, maybe? I can't remember. But, as it is, that method is out of the question.
I've learned a lot about what I did wrong so that's the only good part of all of this. Now, all that's left is to fix the thing so I can go about it right. I'm completely out of ideas, have spent almost a full 24 hours searching solutions to this problem and I am at wits end...
I just want to get back to stock firmware... Any ideas, guys? Should I go about re-partitioning my device at this time?
I have the PIT file... but I'm not sure as to which firmware to choose. I imagine a firmware that is 4.1.1 like my phone was... but I'm not sure about the region. I live in the US and there is no US or North American region firmware version.Can anyone shed some light on which one I should choose?
My SSN underneath my battery say "GTI8190GSMH".
I'm sorry this is so long, I just wanted to explain what happened as best as I could. So, should I go about re-partitioning my device at this point? If so, what firmware would you recommend for my model? Are different region versions okay for a this method?
Or is there another way?
Thanks, guys. :silly:

Some additional details (if it will help): I can, indeed, boot into both recovery and download mode. I just can't seem to flash a stock rom that will boot past the "Samsung" logo.
I've even attempted to flash the param file after the rom flash but it didn't help.

AffectiveEffect said:
Some additional details (if it will help): I can, indeed, boot into both recovery and download mode. I just can't seem to flash a stock rom that will boot past the "Samsung" logo.
I've even attempted to flash the param file after the rom flash but it didn't help.
Click to expand...
Click to collapse
Do you have the stock recovery now instead CWM? If yes do (if you didn't try it) a factory/data reset and wipe cache but it will delete your pics, music etc on your internal storage too.

xXPR0T0TYPEXx said:
Do you have the stock recovery now instead CWM? If yes do (if you didn't try it) a factory/data reset and wipe cache but it will delete your pics, music etc on your internal storage too.
Click to expand...
Click to collapse
Yeah, I have stock recovery now and I have tried that many, many times... Even if I install something like CyanogenMod, it still gets hung up on the CyanogenMod boot screen... And if I boot a stock firmware, it gets hung up at the same place at the "Samsung" logo...
I have an idea that one of the only options left is a PIT re-partitioning... If so, how would I properly go about that? Load the PIT file and the stock firmware in odin? Or only the PIT as PDA? I've heard a couple of different things and am unsure.

AffectiveEffect said:
Yeah, I have stock recovery now and I have tried that many, many times... Even if I install something like CyanogenMod, it still gets hung up on the CyanogenMod boot screen... And if I boot a stock firmware, it gets hung up at the same place at the "Samsung" logo...
I have an idea that one of the only options left is a PIT re-partitioning... If so, how would I properly go about that? Load the PIT file and the stock firmware in odin? Or only the PIT as PDA? I've heard a couple of different things and am unsure.
Click to expand...
Click to collapse
I don't know about PIT files but some people got this message : "CUSTOM PIT BINARY" in recovery mode after flashed a PIT file (maybe they used a other PIT file that wasn't compatible). So make sure you use a PIT file that is GT-i8190 compatible.

I tried flashing the PIT file for the hell of it because I am completely out of ideas.... It failed repeatedly in Odin.
I have no clue on how to fix this... I've tried countless roms and they all get stuck on their respective boot screens. The only one that gave me a glimmer of hope was Cyanogenmod10.2.... It went as far as saying "Android is upgrading" and showed "starting apps" but it got hung up there.
I don't know what to do, guys. Someone help!!!

AffectiveEffect said:
I tried flashing the PIT file for the hell of it because I am completely out of ideas.... It failed repeatedly in Odin.
I have no clue on how to fix this... I've tried countless roms and they all get stuck on their respective boot screens. The only one that gave me a glimmer of hope was Cyanogenmod10.2.... It went as far as saying "Android is upgrading" and showed "starting apps" but it got hung up there.
I don't know what to do, guys. Someone help!!!
Click to expand...
Click to collapse
Use a custom ROM to see if it will fix the problem .Try to flash CyanogenMod 10.2 by NovaFusion via odin or if you flash CyanogenMod 11 then you will automatically get the TWRP recovery. NovaFusion Team Homepage : novafusion.pl. I know you want the stock ROM but try other ROMs to get a booting phone again

xXPR0T0TYPEXx said:
Use a custom ROM to see if it will fix the problem .Try to flash CyanogenMod 10.2 by NovaFusion via odin or if you flash CyanogenMod 11 then you will automatically get the TWRP recovery. NovaFusion Team Homepage : novafusion.pl. I know you want the stock ROM but try other ROMs to get a booting phone again
Click to expand...
Click to collapse
I have... I've tried numerous stock roms and numerous custom roms... all versions of Cyanogenmod, Chameleon, Carbon, Slim mod, etc... They all get stuck at their respective logos.
I even tried the Cyanogenmod with TWRP but, as I explained earlier, I absolutely CAN NOT flash a custom recovery unless I use what ever app I used.... It doesn't work with Odin or with a rom. I don't know why.
I wish someone had more info on repartitioning my phone and if it would help.

NEED HELP?
AffectiveEffect said:
So, to make a long story, short, for the past couple of days my phone has been soft-bricked... It first happened when I attempted to flash dmodv6 in CWM. Everything looked good throughout the installation, however, when I rebooted my device, I got stuck in a boot loop where It would say "Samsung Galaxy S III GT-I8190" for a few seconds, the screen would go black, then say the same thing again... over and over and over...
After a lot of trial and error because of NOT making a nandroid backup via CWM (stupid, I know - I had made one via Titanium Backup and thought that might be good enough), I finally was able to boot. Thanks to xXPR0T0TYPEXx, I was able to flash another rom by puting my external sd card into another phone, loading another rom onto it, and putting it back in my phone. I now had Cyanogenmod10 and was able to boot back up.
I attempted to restore the Titanium Backup I had made with this new rom (stupid again, I know) and it made almost every service on the phone stop working... I desperately wanted just to get back to square one - to install stock firmware and go from there. I followed tys0n's guide on flashing stock recovery then attempted to install stock firmware... All seemingly went well - I booted up, got past the initial "Samsung Galaxy S III GT-I8190" logo and finally got hung up at the "Samsung" logo. I left it one while I went to sleep, just to see if it would eventually work... I woke up and it was still the same. I tried flashing different version of the same stock firmware but it all ended in getting hung up at the "Samsung" logo.
A major problem is that I absolutely CANNOT flash a custom recovery via Odin - it just will NOT work. Everything looks good on Odin's end - I PASS, get the (succeed 1 / failed 0) thing but am sent to stock recovery every time I do the 3 button combination. I've tried many version of CWM and TWRP.... NOTHING. I've even unticked the "Auto-Reboot" button in Odin and pulled the usb cable and battery upon completion but, but nothing ever works. The only way I was ever able to get CWM on my phone in the first place was by an in-phone app... Rom Manager, maybe? I can't remember. But, as it is, that method is out of the question.
I've learned a lot about what I did wrong so that's the only good part of all of this. Now, all that's left is to fix the thing so I can go about it right. I'm completely out of ideas, have spent almost a full 24 hours searching solutions to this problem and I am at wits end...
I just want to get back to stock firmware... Any ideas, guys? Should I go about re-partitioning my device at this time?
I have the PIT file... but I'm not sure as to which firmware to choose. I imagine a firmware that is 4.1.1 like my phone was... but I'm not sure about the region. I live in the US and there is no US or North American region firmware version.Can anyone shed some light on which one I should choose?
My SSN underneath my battery say "GTI8190GSMH".
I'm sorry this is so long, I just wanted to explain what happened as best as I could. So, should I go about re-partitioning my device at this point? If so, what firmware would you recommend for my model? Are different region versions okay for a this method?
Or is there another way?
Thanks, guys. :silly:
Click to expand...
Click to collapse
i got same problem with you before im wayback dmod v6 before and stuck at samsung logo i just try hard reset
1. open your phone
2. remove battery and put the battery try and try til u get in recovery mode (CWM) maybe just tried almost 20x restarting in logo til u in CWM :victory:
3. re-Flash your dmod v6 this way for dirty rom like what i said (softbricks)
4. just flash another new rom whatever u like or dmod v6.
5. I HOPE IT HELPS DONT FORGET TO THANKS <3 :highfive:

[Q][HELP]How To Flash Custom Recovery???

So I tried two ways one was directly from Odin and my watch rebooted into standard recovery and then wiped something then rebooted and I had to activate and pair it all over again, then I tried SkipSoft's method and it just led me around in circles, because of the reboot to recovery flash permanent-recovery zip and not actually in TWRP just in standard recovery again.
Someone help or point me to another method if there is one, I wanna flash Null_ rom and fully unlock this watch.
Once I got custom recovery installed and sticking I could root and everything else on my own.
On firmware version V700XXUAMK7

Did you run the adb command from the little box thingy underneath 'note 2' in the instructions?

The adb cmd line? Don't think tried that yet, but it was rooted beforehand, so I thought I'd be safe it did say it happens if ya aren't rooted, now I'm fighting tooth and nail after custom recovery failed to connect it to my phone again, sadly you'd have thought samsung would've made pairing easier than this crap, I might as well be trying to pair a iWatch to a Samsung that's how full of fail their pairing procedure is. It shouldn't take 30 damn minutes of trying and fails and a few reboots of each device to do this.

That's the one! I think I thought the same as you when I flashed twrp. The install bit of the statement must refer to twrp not root and it should read probably won't install if you don't run this command.
Gear manager is, in my opinion, a POS. From reading it doesn't like being updated. I think that there's some corruption in the data or cache of one of the components that make up gear manager when it updates which can cause problems like connection and massive battery drain. The method I've used before is to use es file explorer to clear the cache and data of all gear component apps (9 on my phone) and delete them, leaving gear manager proper to last. Then reinstall gear manager again. This is a big pain on null because it wipes a lot of stuff of the watch so it's a good idea to have titanium backup on your watch.

Although I'm about ready to give up on this POS and resell it I've never seen something so dammed complicated to pair up and sync I'm still trying and the monkey developed thing is so behind its giving me old pair codes minutes after trying to pair then reporting incorrect pair code, well no duh.
Sent from my SM-N915T using XDA Premium 4 mobile app

Rather wait till the end of the year and get the Rufus Cuff, at least it wouldn't be ruined by Samsung failed coding.
Sent from my SM-N915T using XDA Premium 4 mobile app

Now it seems as though I'm stuck decided to try the latest UK Version of Tizen OS loaded it in Odin 3.09 into the AP Slot pressed started and then damn Odin decided to pop up with a error and close out in Windows, now if I try anything still download mode and reopened Odin 3.07 or 3.09, but it never fully installs I'm in the emergency download kies recovery screen.
Is it possible to install a Odin'ed firmware from here, from what I've learned of the screen/area of recovery, it's the same thing as download mode. I tried the latest Tizen OS again and all it did was sit forever at zImage area of flashing.

Just TWRP installed and to stick, dunno how, but I sideloaded SuperSU since I was already rooted and had KingUser then I tried ADB which didn't appear to work so I tried SkipSoft's custom recovery method and I guess that seemed to work for me, cause now I'm happily on Null_ 23.

Phone wont start up, has anyone had this problem?

So I decided to flash a rom. I haven't done so on this galaxy s6 edge. I've always done it on my previous galaxy phones. The phone already had all the pre-reqs for EXTREME SYNDICATE. Once the phone rebooted to download, I used odin to push out the new OE2 FLASH ME. After that was done the phone just went into a boot loop. I double checked and made sure all the files were correct.
Now I am at a point where even using odin with stock image just goes to samsung splash screen and song then just gives me a Startup Failed - Please connect verizon repair etc.
Is there anything I can do on my end or am I screwed with this phone now. I can still go to download mode and the recovery mode that lets me wipe, reboot etc. But nothing seems to work. Unless I am missing something here.
All help is appreciated, thanks!

Mods can close this thread. I tried everything. Eventually flashing different OE2 and OF1 finally got it working even though I flashed the stock ....

Stuck on boot loop, cant flash firmware, have exhausted all options

Phone has been in the ****ter for the past day. Stuck on boot loop. I tried flashing the most recent stock firmware. It would not do it and kept throwing auth failed signs at me. I tried other stock firmwares for tmobile with no sucess. I Tried throwing them on my sdcard and installing through there in TWRP, but I keep getting md5 auth failures. I have wiped, factory reset, and cleaned house many times. Nothing works. Im at my wits end. Someone please help

I'm a guest to this forum..but same thing happened to me about 5 days ago. Last thing I remember seeing is the 5. update trying to take place and I was just about OUT of Internal memory (with NO microSD card). Phone just kept rebooting. I was able to do a Factory Wipe (Both in the OS and in the Recovery Mode)....Neither worked even though they appeared to be successful. Phone just came back with ALL of my data still intact. The other weird thing...I had about 60 seconds before phone decided to reboot each time. During those 60 seconds I was able to delete files, pictures, etc. to save space. As soon as the phone rebooted those same files were back! Very frustrating. Still having the issue.

im not sure what states either of you guys are in, but you can look on craigslist for people that do flashing. you make need to do a odin rebuild because the partitions are ****ed.
you can repair it yourself but with pure caution.

Have you tried flashing in download mode with your computer through ODIN? If twrp doesn't work, that's what I go to next.
You could also try flashing the firmware without the MD5 file and I believe twrp will skip the check. (not positive on this one)

Figured it out on my own. Flashed CF autoroot. Then flashed 5.1.1 which is the most up to date firmware. Im not sure if the issue was because I was doing 5.1.0 and didnt realize that was the most UTD version, or if CF to 5.1.1 was the trigger. Either way, it worked.