Database Info

SGS bricked! Please help or mom will kill me

Dear Friends,
I happened to have a perfectly working rooted SGS running JPK on Froyo until a while ago. When I tried installing fonts with typefresh. This is where everything went haywire. The phone now doesn't want to boot. It says SGS I9000 and vibrates there 4 times and repeats the vibrating cycle. I want the phone to be working again else my mother will murder me. I tried going to the recovery mode and tried to do a factory restore but that didn't help. Tried to reflash the custom ROM I downloaded from this site (can't find that link) using ODIN but it doesn't work either. While reflashing I did not check the repartition tab. What are the possible solutions here?? KIES doesn't detect phone in download mode. Is there any link from where I can download the factory shipped froyo rom and try reflashing the same via ODIN.

Guys please help it has now turned into a Black Screen Of Death. Though I can still go back to Download mode....please help guys this is getting from bad to worse....
Update: The phone now only goes to download mode...

BUMP! Please guys a few hours before mom comes home from work...

Try flashing a 2.1 firmware with Odin.
Google samfirmware.
Sent from my GT-I5700 using XDA App

You could also try flashing
Froyo that does not brick
and then flash to JI6
EDIT:
Do you have the drivers set up for your device?
Also, What device are you using? The SGS line has many phones. My advice above was dependent on it being a Vibrant

Yes I do have the drivers for my device. I'll be trying 2.1 in a while. What are the chances of Samsung giving me a replacement for the device??
I live in India. We don't get the Vibrant here. It's just plain old Samsung Galaxy S GTi9000

pramathesh said:
Yes I do have the drivers for my device. I'll be trying 2.1 in a while. What are the chances of Samsung giving me a replacement for the device??
I live in India. We don't get the Vibrant here. It's just plain old Samsung Galaxy S GTi9000
Click to expand...
Click to collapse
If you can reach download mode, find you favorite firmware in one of the guides on XDA, and using Odin flash it.
If you know what firmware you were on, you can also just reflash the PDA file of that firmware. The PDA file is Packages inside the rar file you download from samfirmware.com
Best thing is to find a guide, and follow it.

I'd JPK before things went haywire. I'm wondering what's the difference between JPK and JPM. Which one should I go for??
I'm planning to flash to JM8 then doing either JPK/JPM. Is this fine?? Or should I directly flash with JPK/M and forget about JM8? Which one is better K or M? Anything else I need to be aware of before I take the plunge??

pramathesh said:
I'd JPK before things went haywire. I'm wondering what's the difference between JPK and JPM. Which one should I go for??
I'm planning to flash to JM8 then doing either JPK/JPM. Is this fine?? Or should I directly flash with JPK/M and forget about JM8? Which one is better K or M? Anything else I need to be aware of before I take the plunge??
Click to expand...
Click to collapse
Hey pal.
It really doesn't matter which firmware you flash. Over the time, I realized that what works for one does not necessarily work for the other. It really is a very subjective thing.
Between JPK and JPM, the later (JPM) is the latest release. If froyo excites you, go for either JPM or even JP6 (JP6 being a day newer than JPM and recommended i suppose). If eclair suits your use, I would suggest JM9
Links:
Eclair - JM9: http://forum.xda-developers.com/showthread.php?t=802909
Froyo - JP6: http://forum.xda-developers.com/showthread.php?t=807351
It really is not difficult flashing firmwares on the i9000. Just follow the instructions from the thread to the dot and you are all set to go. In the same breath, I would also go as far to suggest that you stay away from custom ROM's till you get familiar with the process of flashing ROM's and troubleshooting (in case anything goes wrong). Stick to the stock ROM's and you should be good to begin with.
Do update on your progress.
Cheers.....

Fixed it. Flashed JPK everything working now! Thanks for all the tips and inputs!

[Q] Samsum Galaxy Fit No Boot

Greetings.
It doesn´t boot.
First details:
Galaxy Fit rooted and 2.3.4 Gingerbread (worked fine)
I downloaded rom-manager and wanted to change to custom roms.
So far.
As I tried to install clockwork I found this in your forum:
http://forum.xda-developers.com/showthread.php?t=1339640
and did everything exactly written there
then restartet, started rom-manager and chose the first option (Clockworkthingy).
As there was a choice of the device, I didn´t find my device and chose the last in list (which did´t work and then I picked the first in list and accepted.
downloaded syanogen 7.0 and after download and backup-chose it told me it would reset and start in recovery ... that was the last I´ve seen from my galaxy ...
Is it broken now.
Please help!
note: tried to start recovery with vol+, home and power as well as usual way to start it. without success

Come on. Some of you Guys are able for sure to tell me, if it is hopeless or there IS something I can do to get it working again.
I know nearly nothing about Smartphones and stuff so
Please!

Rodsengard said:
Come on. Some of you Guys are able for sure to tell me, if it is hopeless or there IS something I can do to get it working again.
Please!
Click to expand...
Click to collapse
Sorry to say that your phone is bricked.
First, rom manager doesn't support your device.
Second, you are an idiot that you selected unknown device from list to make it work.
Third, the thread doesn't have any tutorial about rom manager it is CWM that is meant to be flashed using odin.
Fourth, I probably this is hard brick and nothing can be done.
IN MY VIEW GO TO THE SAMSUNG SERVICE CENTER AND TELL THEM THAT YOU LEFT YOUR FOR CHARGING OVERNIGHT AND ITS NOT BOOTING.
THEY WILL SURELY HELP FOR FREE AS THEY DON'T KNOW WHAT YOU DID AND THIS IS AN APPROPRIATE REASON.

Thank you for your honesty.

Your phone still can be fix up. Your phone not brick yet.. Your phone might get bricked if it running out of battery during flashing, like a half way flashing, then you are in the worse case scenario.
Recovery mode unavailable? Forget about recovery since it has been.broken. What important now is to get access to download mode by pressing vol down + power + home key. If you can access download mode, then your phone can be fixed in 5min.
Read this, before you go any further, if you sure that you already successfully flashed any rom before it went brick. Just do this simple step, for cm7, u need siyah kernel, go download (siyah 2.1.1 .tar)... Not .zip.
Remove your battery then put it back, get into download mode then flash siyah 2.1.1 with Odin 1.85.if your phone already flashed cyanogenmod7, then your phone should boot up and work properly.
If it doesnt work, click the link on my signature, follow all steps provided tp get back your to work as stock. Then start flashing again.
Ps : dont use backup, dont use romanager.
Sent from my GT-I9100 using xda premium

My guide is for SGS2 International. Not ATNT, please find stock rom for your phone version. But the flashing method are just the same..
Sent from my GT-I9100 using xda premium

Thank you for your efforts neobirdrio, but as I wrote above, nothing works.
No combination with vol+ or - and the 2 other HW-Keys.
But if we are still in Topic, what exactly do I have to do with an intact Galaxy fit to flash it to a custom ROM.
What Custom ROMS would run with it?
Where Do I get the Newest Version?
And is it worth changing it?
I wanted something special, something faster than Gingerbread and (of course the original Froyo on it), including something needs less Space.
Could you advice me?
(I ordered a new one swince it happened)

Try read this post,
http://forum.xda-developers.com/showthread.php?t=1120880
Latest stock firmware for galaxy fix is 2.3..which is gingerbread.
Sent from my GT-I9100 using xda premium

Still trying this out.
Did it in this way press three Keys, push batery in and so on ... One time on my netbook it came to life by meaning system told me, that it installs driver (seemed to be recognized right) and ODIN told, there is a connection. I started ODIN (which was prepared to do Gingerbread onto it) But it did nothing. I am not sure if I startet Odin with Adminrights, soooo ... Do now backup of the partition, put a much earlier backup on my PC and try it again (I am running out of PCs, so I simulate, that this is a new Computer )
I keep you informed.
Thanks again so far.

Tried it again, but it didn´come back to life
So Thanks to all ppl helped me.

help would be awesome even if your help is hey dont try this agin

I tried to root through the odin method and I can get into CWM but when I install zip then reboot it stops at the SAMSUNG screen...any help will do I need my phone by tomorrow at the latest also Im with Best buy warranty so should I just break my phone and get another ?

Boot into recovety try data/cache wipe 3 times each then reboot.
---------- Post added at 03:50 PM ---------- Previous post was at 03:50 PM ----------
Also which rom are you trying to install?

What u running 2.3.5? Or 2.3.6?
IF 2.3.5 than i would unroot it and run 1click root.
GeezyF.Ladies said:
I tried to root through the odin method and I can get into CWM but when I install zip then reboot it stops at the SAMSUNG screen...any help will do I need my phone by tomorrow at the latest also Im with Best buy warranty so should I just break my phone and get another ?
Click to expand...
Click to collapse

stock one from http://forum.xda-developers.com/showthread.php?t=1340526

appdroid said:
What u running 2.3.5? Or 2.3.6?
IF 2.3.5 than i would unroot it and run 1click root.
Click to expand...
Click to collapse
2.3.6 yeah I've heard one click is awesome

Your able to get into recovery? So as i said boot into recovery wipe data/cache 3 times then reboot. If still no go flash the stock tar with odin again and reroot. You could also try just flashing the stock recovery.tar and boot into it. Then wipe data, and cache. Then reboot

silver03wrx said:
Your able to get into recovery? So as i said boot into recovery wipe data/cache 3 times then reboot. If still no go flash the stock tar with odin again and reroot. You could also try just flashing the stock recovery.tar and boot into it. Then wipe data, and cache. Then reboot
Click to expand...
Click to collapse
k tried the data/cache 3 times each and rebooted and nothing. well how do I put stock tar on my sd card if I cant get my phone on to connect with my pc storage ?

The stock tar you need to put on your pc. And you need to get your phone into download mode. You use odin on you pc with your phone in download mode. To flash the stock recovery tar. To be honest you need to just use odin to reflash the stock tar. Again. Go to the thread woth the stock tar and follow the instructions again

haha duh on my part I was just so scared that I panicked but its downloading now and im going to try and flash back to stock when it is done. thanks for your patience/help slvwrx.....upon more research I think I got a bad recovery tar bc I cant open it its just a white page with a folded corner and I think I saw someone with this problem in the thread and said you have to extract zip

any other ideas ?
anyone get tar files from another site because when I try to open mine they all say cannot open file does not seem to be a valid archive.

You cannot be serious with these questions? You don't open the tar file you put it in Odin. You really need to put some effort into researching what you are trying to do with your phone. Your lack of prior research is why you are having problems. Not trying to be an ahole but you really need to READ everything in these forums before you try to do anything to your phone or you seriously risk bricking it and not being able to recover it. It is nearly impossible to brick these phones but if you have not done the requisite research here then you will end up in essence with a brick because you have no clue how to recover it from your own mistakes. I read these forums for a solid week before I even connected my phone to my laptop and I am an IT Engineer but that doesn't make me an Android expert so I learned from the awesome people here that know more than I and are freely willing to share their knowledge. Take my word for it any/all information you would ever need to fix your phone is all right here for the reading courtesy of the great devs and enthusiasts here on the site.
Sent from my SAMSUNG-SGH-I957 using XDA App

Blackberrynomore said:
You cannot be serious with these questions? You don't open the tar file you put it in Odin. You really need to put some effort into researching what you are trying to do with your phone. Your lack of prior research is why you are having problems. Not trying to be an ahole but you really need to READ everything in these forums before you try to do anything to your phone or you seriously risk bricking it and not being able to recover it. It is nearly impossible to brick these phones but if you have not done the requisite research here then you will end up in essence with a brick because you have no clue how to recover it from your own mistakes. I read these forums for a solid week before I even connected my phone to my laptop and I am an IT Engineer but that doesn't make me an Android expert so I learned from the awesome people here that know more than I and are freely willing to share their knowledge. Take my word for it any/all information you would ever need to fix your phone is all wright here for the reading courtesy of the great devs and enthusiasts here on the site.
Sent from my SAMSUNG-SGH-I957 using XDA App
Click to expand...
Click to collapse
any criticism is good criticism to me thanks for giving me the cold hard facts and to be truthful I did jump into this early coming from an iphone 4 and all the ones before that and jailbreaking them I thought it'd be easy and it was I just 2nd guess myself all the time. my mistake was following the vid a ruebarb posted in the thread and I followed it to a T .it wasnt till he updated his video and said that his method was for ''already'' rooted users so after getting konane's stock tar flashed in odin I was back to stock re-did the 2.3.6 method got it done stayed stock rooted for 2 days then just about 30 mins ago I went head and jumped on RED SONIA!
again thanks for your input and to care enough to set a noob stright
also Cdshep pretty much found the problem after having a personal chat with me he saw what I was trying to say I'm just not really good with wording or spelling I just recently winged myself of of concerta(ADHD pills) and so my mind moves faster than I can type or right and I confuse myself but its better than the life of a zombie!

[Q] PLEASE HELP. Soft Bricked My Verizon Galaxy S4.

Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.

muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped

[Q] Tab 2 10.1 touch screen stops after a couple minutes

Ok guys, almost first post here, now that its in the right spot. My galaxy tab 2 10.1 model GT-P5113TS is having an issue that I can't seem to find on any site including this one.
Little background, this problem first started several months ago. My wife ran the battery completely dead on the tab, we didn't have a "samsung" charger and couldn't get it to charge up. Bought new charger, got it charged, and ever since then, the screen will work for anywhere from 15-20 seconds to 3 or 4 minutes, then just stops working. Hitting the power button will turn the screen off, hitting it again brings up the lock screen, but the screen will still not recognize any touches. The side buttons still work, just not the touch screen.
Letting the tab sit for a couple hours is the ONLY thing that gets the touch screen working again. But it will only work for a minute or two again before it stops working... again... I tried a soft reset several times to no avail. Kind of forgot about the tab, left it for a few months. Picked it up yesterday after charging it and still no different than a couple months ago. I tried the factory wipe/reset several times using the power and volume buttons and it made no difference. Usually the screen won't stay responsive long enough to make it through the whole set up process.
I'm pretty new to digging into these things. I'm not afraid to give it a shot, since the thing is useless in its current state. But most of the lingo and abbreviations are new to me. If anyone can point me towards a solution, I'd be VERY grateful! I'll do my best to answer any questions to help as well.
PS, we bought it used off ebay, so no warranty. It worked fine for almost a year before this started.

Bump for a little help? Thanks in advance! :good:
Edit: Should also mention that it's 100% unmodified/stock. I haven't rooted it or been inside it or anything. Very open to trying about anything since like I mentioned, it's useless to me as it sits currently.

You can't do much with the screen the way it is, your best bet is to root and flash a custom rom.
Look in development for a root method and install a custom rom using Odin. Check out You tube for videos on the matter you should find several.
Pp.

Help!
PanchoPlanet said:
You can't do much with the screen the way it is, your best bet is to root and flash a custom rom.
Look in development for a root method and install a custom rom using Odin. Check out You tube for videos on the matter you should find several.
Pp.
Click to expand...
Click to collapse
For me th einstalled custom CM11 rom nighlty boots but seems to drop all kinds of android processes. Ik keeps showing all kinds of zip files in the download area. Installed apps can be deeted but are back after reboot. Can't find sd-ext.
Installing stock of custom rom with Odin goes ok for a while but fails all te time.
Is there a low level kind of remedy?
Thanks!

Can you get into recovery?
Use any previous nandroid.
You do have nandroid b/u's ?
Pp.

PanchoPlanet said:
Can you get into recovery?
Use any previous nandroid.
You do have nandroid b/u's ?
Pp.
Click to expand...
Click to collapse
Yeah, I can boot into recovery where it gives me the options to install from SD card etc. And I have to use the power and volume buttons to navigate the options. Thats how I tried the factory reset the first time, to no avail.
I don't have any other backups or anything to try. Where would I go about finding something to use?

Your only option is to reflash your rom or the stock firmware in order to fix the issue.
Use Google to search for the stock firmware, you will have to root again and install CWM.
Pp.

PanchoPlanet said:
Your only option is to reflash your rom or the stock firmware in order to fix the issue.
Use Google to search for the stock firmware, you will have to root again and install CWM.
Pp.
Click to expand...
Click to collapse
Is there an easy to follow how-to for rooting it somewhere? Ideally a way that doesn't involve using the touch screen, since mine is obviously on the fritz.
I'm assuming to reflash the stock files, I'll need to (figure out what files) save them to the SD card then select the restore from SD card option in the recovery menu?
I'm a noob to this stuff, so not familiar at all with the abbreviations and what not. (What is CWM?) But I'm fairly competent if things are broken down to the basic steps and what not.

Well looks like I'm answering my own questions a little bit, but it looks like I can download the VRoot program onto my computer, along with the Samsung USB drivers, and use that program to root the tablet..... correct?
Then download Odin to flash the files?

Not familiar with Vroot, need to look it up.
The first thing you need to do is flash the stock Samsung firmware in Odin (using download mode ) . Afterwards you run your tablet for a while, 2 to 3 hours and make sure it's OK (touch screen wise) , then you can root and flash roms.
Pp.

So I don't need to root it to flash in the firmware, just if I were to flash a rom? Sounds simple enough.
Next (noob) question. Does the firmware have to match with the version of android running on the tablet? I'm not sure what version is on it, I'll have to look after work. Or can I just get the latest firmware update for my model and use that? Looks like for my model there's a version 4.2.2 that says Canada. That seems to be the newest one out there. Is that what I'll want to use?

Follow this video and you should have success. They have an apparent source for the firmware, otherwise you have to download from Samsung and that can take days.
Pp.
http://m.youtube.com/watch?v=A40XVvPPbe0

After watching video there are further steps to fully wipe and factory restore , you don't have to go this far unless you want to make tab new like out of the box.
Pp.

Over the weekend I found a site that had the correct factory firmware, and I was able to download it, install Odin, and flash the firmware into my tablet. I followed the steps for the beginning portion of that video posted and was able to get it done. I then wiped all data and the cache and now I'm happy to report that its back to working like it should! Basically saved me from trashing a $200+ tablet!
Thank you guys so much for the help! And thanks to everyone that makes this site possible. Awesome to have people with this level of knowledge in one place and so willing to help!
:good::good: