Database Develop

[Q] Can't mount /dev/block/st19

My problem is really complicated. Things first: My phone didn't work for the last 3 months properly. I mean it booted and everything worked, but I could only update 3-6 apps and then I had a kind of lock (apps downloading, but no more installing). The solution for that was to go to CWM recovery and to clean cache, fix permissions and reboot. Now I could update the next apps until it locked again. Today I was really upset with that and tried some different things. I can go to download mode and CWM recovery (2.5.1.3) is still there but phone doesn't boot anymore. I can flash other firmwares with heimdall (using only linux) without errors, but the phone doesn't boot (stuck before the big S should come). If I go on CWM mount and storage I can't mount /system and /data, think thats my biggest problem right now. Is there any possibility to delete the whole SD card? I mean everything? Already tried flashing XWJS5 with repartition ticked, but it doesn't change anything. Tried now also to flash an old 2.1 firmware, no difference. Any idea how I can fix that problem (adb recognize the device)? Can't go to samsung centre because CWM is the recovery and they will know I rooted the phone...
Comprehension: Can flash other firmware with heimdall without errors, but the phone won't boot further then Galaxy S GT-I9000. The big S logo doesn't appear. In recovery can't mount /system and /sdcard
I tried already so many things, so I'm very happy for any advice!

Try flashing an older stock rom like jpy or js3 or your official rom, with repartition. As far as i know js5 rom is not a full package as jpy or js3 which also have the bootloaders. Those roms should also restore default recovery.
Sent from my GT-I9000 using Tapatalk

Reflash FULL firmware
*EDIT- rechecked the error code*
I'm pretty sure "can't mount /dev/block/mmcblk0" error = Bad SD Card
try to flash it back to stock so you get the I9000M splash and bring it back for service.
you can try, just make sure it's stock firmware:
flash a full firmware (pda/csc/phone/pit w/repartion), it might recognize the drive after re-boot.
good luck

flashed to JS3. updating now. Gonna see if it works again or if the installation bug is still there... Thanks for helping lilraindon
EDIT: Back on darky again. Problem is that my error still exist. Sometimes you can't update or install any new apps, needs to go to recovery and to wipe cache and fix permissions... Pretty annoying. Bought the phone in Germany and I'm now in Vienna Austria for studies. Do I need the warranty and bill (both in germany) or will they take it to repair without any of them? Can I sell this phone on ebay and buy from the money a Nexus S2?........ last one just kidding, just pretty annoyed my sd card is somehow broken. Any possibility (like an sgs tools script) to wipe cache, fix permissions and mount /data with phone on? With that I could live...

[Q] Convert SD partition??

hello all,
i recently tried dwnloading the F1 GS2 ROM, i havent got a custom recovery so i changed the kernel to support clockwork recovery, then after i tried to install the Rom, everything started up correctly and then when it came to the samsung logo, the robotic voice (that tells you that it is enabling lag fixes etc.) said that i have to convert sd card partition, after which it continuously kept bootlooping, so what do i do to convert sd card partition on galaxy s?(i have no idea what this means so an easy to understand detailed guide would be nice, lol (newb question, i know.....)
i have since reverted back to XXJVQ 2.3.4. and everything is stock again....

[Q] Old problem still without any solution - Fullwipe ICS

NEED HELP
I know that many people had the same issue with the galaxy note and ICS.
I did a fullwipe with ICS installed last night and as every body knows , the phone won't boot
I downloaded more that 20 custom & stock ROMS. Tried all kernels but still nothing.
It started by recovery problems
I could not mount /data
No i can mount data but my phone can not see the SDCARD , even the internal card is not visibile.
I can not try to code with adb because my phone is not rooted anymore and i can not root through CWM because my phone doesn nor recognize the SD card
Is there any alternative way to odin or something to flash the roms ?
Like all other friends who had the same problem with odin , it hangs on *.img data.
HELP

[Q] (Yet Another) Boot Loop Problem in Installing CM7 on GalaxyS I9000 [SOLVED]

YABLP (Yet Another Boot Loop Problem)
Hi,
I'm having a devil of a time installing CM7 on my GalaxyS I9000. Description of my procedure and problem below.
I've been beating my head against a wall for a week so any help GREATLY appreciated.
-John
Phone: Galaxy S "I9000"
Trying to Flash: CM7.2.0 using CWM Recovery
What I did:
Flash stock ROM w/ODIN v1.85 - OK
Wipe Data/Wipe Cache
Flash ChainFire (CF-Root-XX_OVA_JVU_2.3.6-v4.3-XWM3RFS.tar) w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.2.0-galaxysmtd.zip from CM site)
Flash completes in just a few seconds - much too quick!
Phone reboots automatically
Now stuck in boot loop
Screens in boot loop:
1. GalaxyS/GTI9000/Samsung
2. GalaxyS/Cyanogen(mod)
3. CWM menu scrolls by too quickly to read
Back to 1.
Tried Heimdall but complained about missing XML file
Tried installing "Datafix". Would not install (says not compatible with device)
Tried STFW: many reports of same problem but no solutions seemed relevant & appropriate
Clues:
After CF flash, disk use as follows
/system: used 27.3M, free 9.4M (97%) (seems pretty full)
/data: used 47M, free 1916M (2%) (seems pretty empty)
Me thinks maybe /system is too small/full to accept update?
This is the 3rd I9000 I've flashed. First 2 went Ok but this time it failed although identical files/procedures used (I think).
HELP!

I've seen a similar problem on my I9000 - I think the CWM scroll complains about "can't mount /data".
I'm in a similar position, I can't get anything to flash and boot though : http://forum.xda-developers.com/showthread.php?t=1967982

This happens pretty much every time you flash any kind of CM rom from stock. All you need to do is flash CM7, it will go in to bootloop with various text scrolling through thats too fast to read. You just pull battery while in the bootloop. Then replace battery, three button combo to recovery and flash the same CM7 zip again. This time the install will take a while longer. Afterwards flash gapps and reboot and you should be good to go.

I tried this - but same result, just spins round on the CM boot screen
Where do the wipe data and wipe cache commands fit in to this? Before/after both installs?
I don't normally bother with gapps - just trying to get it loaded. Does that make a difference?
Also, no SIM card in at all during all this...

IT WORKED!
Bless you BandiBp!
I'll be sending my first-born by return mail (please don't tell my wife

Yeah that happens because its flashes a kernel with a new partition system. Dunno why only a few roms warn people about this.
Sent from my GT-I9000 using xda premium

You're welcome mate, yeah the reasons are the new partition changes on different roms. I agree that rom flashers should be warned in advance about this. Would reduce problems A LOT. My general rule is if a Rom installs in under 5 secs, then you should always flash again.
Anyways have fun.

[solved] Just another Bootloop - but this time with other complications

Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan

gebauer said:
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
Click to expand...
Click to collapse
I suspect that your device is boot-looping on custom ROMs because there is incompatible stuff on your /data partition. The data partition needs to be wiped and you can't really do that with ODIN. You need to find a custom recovery that allows you to flash using ODIN and that is compatible with the custom ROM you are trying to flash. You also need to wipe /data (format it) before your first boot. You will loose all your info, even the stuff that was in your internal sd but the device should boot.
BUT:
I note that you said your HOME button is not working and that is required to manually boot into recovery. Additionally, with out a booting ROM you can not issue the "adb reboot recovery" command which would do it for you. There is a trick that I have learned but I only know how to do it with "heimdall" in the Ubuntu Terminal.
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
The partitions for the kernel and recovery on this device are typically kernel and kernel2 respectively.
kernel -> kernel
recovery -> kernel2
So:
recovery -> kernel ( Will boot recovery on a normal boot ).
I hope I have explained this well enough. You are going to have to do some learning if you want to get this working. Good luck.
P.S. If you are thinking of asking follow questions, don't, Google it instead.
Heimdall: http://glassechidna.com.au/heimdall/

Meticulus said:
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
Click to expand...
Click to collapse
Dear Meticulus,
thanks a lot for your help. I was away for the week-end; thus the late reply.
With your help it took me only an hour to get my smartphone working again. The main tipps, which helped me was the Heimdal tool, which I wasn't aware off and the possibility to flash the recovery directly into the kernel...
It worked like a treat. The smartphone booted into TWRP directly, which finally gave my access to wipe the data partition.
It took a couple of trials before I was able to flash an android image back to the kernel/system but this also worked nicely.
So thanks again and this brick is solved :good:
Jan