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] i9000 galaxy s stuck on start up loop, factory reset, wipe cache, still loops

i've tried everything on the net, it still keeps continuously looping. It would initially go the home screen and start doing the memory scan and i'd have access to the screen and then all of a sudden restart.
then i did a factory reset by going into the recovery mode, now it loads up and asks me to fill in my details like a new phone, when it reboots again.
what else is left to try, i cant even access my data on the internal sd card as the stupid thing wont stay on long enough to copy my data over through usb. As it keeps booting within 10seconds of loading the home screen.
i can access recovery mode and download mode.
please help
P.S. is this problem with just the galaxy s or all android phones, as it frankly is ******** me off to the point i'm thinking of going back to my candy bar Nokia phones, instead of dealing with this pile of **** every few months.
P.P.S. i am on android gingerbread with voodoo kernal, both of which have been fine for the last few months.

articoceanic said:
i've tried everything on the net, it still keeps continuously looping. It would initially go the home screen and start doing the memory scan and i'd have access to the screen and then all of a sudden restart.
then i did a factory reset by going into the recovery mode, now it loads up and asks me to fill in my details like a new phone, when it reboots again.
what else is left to try, i cant even access my data on the internal sd card as the stupid thing wont stay on long enough to copy my data over through usb. As it keeps booting within 10seconds of loading the home screen.
i can access recovery mode and download mode.
please help
P.S. is this problem with just the galaxy s or all android phones, as it frankly is ******** me off to the point i'm thinking of going back to my candy bar Nokia phones, instead of dealing with this pile of **** every few months.
P.P.S. i am on android gingerbread with voodoo kernal, both of which have been fine for the last few months.
Click to expand...
Click to collapse
what rom r u on
---------- Post added at 03:31 AM ---------- Previous post was at 03:26 AM ----------
TIGER 123 said:
what rom r u on
Click to expand...
Click to collapse
this might help you go to darkyrom forum,flash 10,2 re,
this saved me a couple of times,you have to do it through odin theres a guide on the forum or checkout puggeruk on youtube"ref unbrick my sgs" hope it helps

articoceanic said:
i've tried everything on the net, it still keeps continuously looping. It would initially go the home screen and start doing the memory scan and i'd have access to the screen and then all of a sudden restart.
then i did a factory reset by going into the recovery mode, now it loads up and asks me to fill in my details like a new phone, when it reboots again.
what else is left to try, i cant even access my data on the internal sd card as the stupid thing wont stay on long enough to copy my data over through usb. As it keeps booting within 10seconds of loading the home screen.
i can access recovery mode and download mode.
please help
P.S. is this problem with just the galaxy s or all android phones, as it frankly is ******** me off to the point i'm thinking of going back to my candy bar Nokia phones, instead of dealing with this pile of **** every few months.
P.P.S. i am on android gingerbread with voodoo kernal, both of which have been fine for the last few months.
Click to expand...
Click to collapse
If you have important data on your internal card:
goto recovery mode, then mounts and storage,
connect your usb cable, choose mount usb storage in the recovery (dont choose the unmount usbcard!!).
Now you can access your internal storage.
Also you can try to flash the semaphore kernel from the development section.
After that do a wipe data/factory reset from the recovery.

articoceanic said:
what else is left to try, i cant even access my data on the internal sd card as the stupid thing wont stay on long enough to copy my data over through usb. As it keeps booting within 10seconds of loading the home screen.
i can access recovery mode and download mode.
Click to expand...
Click to collapse
go to recovery>mount option> mount usb option and get your data ..
As fas as rom is concerned try to flash a stock de-odexed rom using odin . Might help

having tried flashing 2.1 (eclair) rom? with pit files
hope this works
cheers

Have you tried recovery/backup and restore and made a backup? Then I would remove external sd and simcard, back to recovery/storage and format the sd card. (this will wipe the internal card AND the external if it is in!!) Then remove battery, boot to download and flash a stock rom using odin, boot the phone, remove batt flash a kernel then flash your custom rom.

thanks guys, didn't know about the mount usb storage thing in recovery mode, at least my stuff is safe.
Did 4-5 factory resets and every time it would stay on for longer before falling into the boot loop. as of last dozen hours or so it is working fine. (hope its not a hardware failure, but merely software, phones nearly out of warranty)
But if it keeps happening again, will take your advice, mount my phone, copy my stuff over and install another ROM.
happy and relieved chap for the moment.

well the boot loop is back, but some more info, this time it seems that whenever i try to turn on wifi or use wifi the boot loop starts. So long as wifi is disabled its fine.
From what i've read it seems to be specific to the three network rom.
anyone know of a stable rom, preferably the most stablest rom without any problems out there, that they can recommend?
or even better, if better the stock default unbranded goodle rom for this phone without any network changes, that wont give me any problems?
all i wanted was a simple fast phone without any problems, might be forced to go to the dark side and buy an apple if this continues.

[Q] Odd Problem - Soft Brick

Hi,
I installed Galaxian Soup 1.5.1 beta a week ago and all has been running fine. This morning the tab was blank like it had run out battery so I put it on charge and found it wasn't dead. Tried to reboot and it's just stuck at the "Samsung Galaxy Tab 8.9" screen. I was using it fine last night and haven't changed anything!
I've tried ODIN to restore Stock Recovery which said it passed and worked, but still the same problem. It has removed CWM though. When I try to do anything in Stock Recovery it complains about not being able to mount the /data directory.
Is there anything else I can try, do I need to use ODIN to flash a ROM again? If so, can you tell me which file to use as there are hundreds in the Galaxian Soup zip.
Thanks!

Flash stock rom with Odin. Unfortunately you also need to wipe data in stock recovery for this to work, so you will loose everything.

Thanks for the reply. Unfortunately this hasn't worked, it passes in Odin but then on the tablet it says E:failed to mount /data, and "your storage not prepared yet, please use UI for format and reboot actions.
Trying to factory reset fails.
Any other ideas?

OK, a bit more detail. I use ODIN to flash the stock rom found here - http://forum.xda-developers.com/showthread.php?t=1483168
It passes and goes into recovery but complains in red letters about not being able to mount /data, can't access /system/csc/XEU/system in yellow and can't mount /cache or a few other subdirectories.
I select wipe data which appears to work although it complains about make_extf4fs failing on /dev/block/mmcblk0p8. It then complains about not being able to mount /cache and other subdirectories again.
I then select reboot, it complains again about not being able to mount /data and /cache and switches off, not reboot. If I turn it on again I'm straight back to recovery.
Got to be something I'm missing here!
Any input appreciated.

It seems your partition tables are messed up, but i have no idea how this could happen if you didn't flash anything that could cause this, maybe a hardware problem?
There is a way to repartition the tables, you need a PIT file for this. I have not done this myself, so unfortunately i don't know much about it. Try to search for a PIT file, but make sure it's for your tab model, otherwise you can mess it up completely.

Many thanks - that fixed it! For future reference and for anyone searching this thread I found the pit file here - http://forum.xda-developers.com/showthread.php?t=1406137&page=9 and flashed it with ODIN together with the standard firmware I mentioned in the earlier post.
It's not all good news though. The tablet now keeps freezing. Even in recovery while I was trying a factory reset for the freezing. This leads me to believe it may be a hardware problem that caused the original brick and ongoing freezing issues. What do you think? Does it save a dump anywhere when it crashes?

Glad to see it worked. Maybe try to flash the stock rom again, now without the pit file. Also try factory reset in stock recovery. If you are still having problems, then im afraid its a hardware problem.

Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!

Mbuxton said:
Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!
Click to expand...
Click to collapse
I have been flashing different roms, kernels and recoveries on my tab for more then 200 times probably. And i have been using Galaxian-Soup AOSP ICS rom with molteys kernel for almost two months. Never had any problems (that i didnt create myself). Never used overclock, but havent heard of anyone who has had problems with it either.

Keep phone on long enough to transfer files?

I have had a ATT captivate for almost 2 years now. It falls in the IMEI range specified by ATT. But it wasn't really a problem until very recently.
It got much worse about 3 weeks ago when the phone kept constantly rebooting. It would load the OS, begin media scanning, once that concluded, it would immediately reboot (almost every 20 seconds). Only way to stop the reboot cycle is to take out the battery. No new apps were installed, no system changes were made when this happened.
I am able to get the phone's menu which allows me to wipe and I am able to get the phone into download mode.
I have read (4) of this article regarding sleepdeath and all corresponding articles referenced.
This is what I did...
1) Performed hard reset, cleared storage. This eliminated all third party apps, returned the phone to stock (I think), but the phone is still rebooting.
2) Attempted to install a brand new rom (CM) via CWM = Problem got much worse. Still rebooting but this time, after the ATT logo appears, the screen changes to static (noise) and reboots. Followed instructions and diles from here.
3) Since the phone became useless, I hunted around to return it to stock again and used this. The phone now boots up into the OS, but now it's back to rebooting.
I repeated steps 2 and 3 just to make sure I didn't miss a step, but same problem.
I have 2 goals:
1) Get the phone working, if at all possible!
2) If that's not possible, recover the 300 pictures that are on the device.
My challenge is that since the phone keeps rebooting every 20 seconds, by the time it connects to my PC via USB as external storage, it reboots! This ofcourse is also preventing me from loading a ROM directly on to the SD card.
So if anyone can help me to do the following:
1) Point me in the right direction to how I can keep the phone in a certain mode or setting (download mode doesn't work) where I can transfer files, recover my pics, and perhaps load a custom ROM?
2) Next steps?? Am I even on the right track? Since the stock rom keeps the phone rebooting, will a custom ROM solve the problem (have not been able to get a conclusive answer on this on the threads referring to sleep death (which this is an exaggerated version of) or is the phone a lost cause?
I know I can call ATT and try to haggle a replacement (since the phone is out of warranty), the only benefit being they don't renew my contract, and I don't have to upgrade.
Any help or guidance is much appreciated.

Wow, bummer
Well i don't know if you can mount the sd card in stock recovery (never used it) but if you can't then you could flash one of the stock one click roms with cwm recovery from this thread.... http://forum.xda-developers.com/showthread.php?t=1300843
In cwm recovery there is an option to mount sd while connected to pc so you can backup your stuff.
For the reboots, could it be your power button? Mine is acting up, and often seems to cause reboots. There are threads about fixing that. Idk just a thought.
Hope that helped a bit
Sent from phone with app

Like the previous post says, maybe try a custom recovery, go to mounts and storage, and mount USB storage. While you're at it, try flashing a compatible ROM through that recovery i.e. GB rom if its a GB kernel with CWM recovery or ICS rom if its an ICS recovery.

Did you try to do a dump of SD card data with adb?
Sent from my GT-I9000 using xda premium

The static issue is because you flashed a gingerbread kernel but you don't have gingerbread bootloaders. You can fix this by flashing an AT&T stock one click with bootloaders.
Once there, you can flash corn kernel and use recovery to mount the sd card.
Or I guess you could flash a froyo kernel.. there's a number of ways to do this.
Sent from a jelly bean

please help a person who doesn't know much about ROMs, kernels, root and so on.

i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.

also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying: