Database Users

[SOLVED] Galaxy S I9000B not booting, no recovery mode

I rooted and installed CM7 on my SGS i9000B about 1 month ago. Everything was going fine and I was in love with my phone.
This afternoon, suddenly and with no apparent reason, it started giving me infinite "Force Close" messages to all apps I tried to open, making the phone pretty useless. Whe this happened I tried repairing permission from within Rom Maanger but the problem persisted. So I booted in recovery mode (Clockwork Mod Recovery) and tried fixing permissions there, but force closing problem was still there.
I had an Nand backup from the day I installed CM7. So I went to recovery mode again and tried restoring the backup, but it gave me an error (I believe it was somwthing related to disk space, but I'm not sure about that). So I did another backup (just in case) and tried to reboot the phone to try restoring backup again.
The problem is, now I can't get to recovery mode again. When I rebooted I was not able to go back to recovery mode anymore. I am still able to get to Download mode though. So I was thinking about flashing some rom/bootloader or something back in from Odin, but as I have no experience doing this, I believe it's safer to ask for help here before doing anything to the phone.
I believe it's not bricked yet, since I can still get to download mode.
Can anyone give me some detailed info about what I should do?

Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.

evernet21 said:
Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.
Click to expand...
Click to collapse
Sorry but I have very little experience with this and I want to be sure about what I'm supposed to do. What do you mean by flash kernel again? Is it flashing CyanogenMod 7 again via Odin?

I flashed the kernel again using Odin. Used the same file that I used before (when I fisrt rooted the phone a month ago - speedmod k13C). Now I can get into Recovery Mode.
But now I have a different problem. I tried to do a nandroid restore (backup and restore - restore ALL) but I have some errors related to mounting errors:
Code:
Checking MD5 sums...
Restoring system...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Error mounting /system/!
Skipping format...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Can't mount /system/!
I have no idea what that means.
Any help?

While searching for help on this error I found some people saying that flashing stock rom back intro phone could solve the problem. So this was what I did. Flashed stock samsung rom back i using Odin but when phone rebooted the following error appeared:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
[some recovery options]
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
So I have a very similar error - "can't mount /dev/block/SOMEFILE". It looks to me like a problem with the internal sd card. What do you guys think?

Solved
I could solve the problem using the method described in this thread.
http://forum.xda-developers.com/showthread.php?p=14732179#post14732179

[Q] i9505 TWRP Bootloop

I flashed the Team Win Recovery Project 2.5.0.3 on stock rom yesterday and now android begun to lag, so I tried to reboot It an now I'm stuck on the bootscreen with the Galaxy S4 logo...
Recovery and download mode still works. I also tried a full wipe but there I get this error:
Code:
E: error: opening /data/data
E: error: I/O error
Maybe caused by FolderMount or such apps, which I tested some days ago?
Does someone know a solution?
I'll try to flash the stock rom again with Odin, as soon as the rom is downloaded...1.6gb

Perhaps you deleted or edited something by accident. So if you boot into recovery and try wipe data/factory reset you get an error? Usually with a bootloop wiping the data and reflashing a stock ROM worked well. Try flash the stock ROM and then try wipe data/factory reset then see if you can boot fine.
Sent from my GT-I9505

one onlesVi
Well, I flashed now the stock rom and first I did a data wipe, which worked fine and then I tried to wipe the cache, but the process crashed with a dead droid(?). The phone has automaticly rebootet now and android seems to work fine. Is this a good or bad sign? ^^

[Q] Please help, TWRP will not flash/ wipe/ restore anything

I was running CM10.1, I was switching to Google Rom, wiped data/ factory restore, flashed zip, but forgot to flash Loki.
Went back, tried to flash loki, but it comes out as failed. looking through logs, I get
E:Unable to mount /data
E:Unable to mount Internal Storage.
I tried to do wipe of system, data, cache, and nothing wipes.
When I was rebooting 2nd time, I got a prompt to install Root as I was not rooted, but I did root weeks ago, when I went to CM.
Any help/ advise/ suggestions are welcome.
I would really rather not ODIN to stock, but will if I have to, is there a way to snatch internalSD files before the flash?

Dimon1990 said:
I was running CM10.1, I was switching to Google Rom, wiped data/ factory restore, flashed zip, but forgot to flash Loki.
Went back, tried to flash loki, but it comes out as failed. looking through logs, I get
E:Unable to mount /data
E:Unable to mount Internal Storage.
I tried to do wipe of system, data, cache, and nothing wipes.
When I was rebooting 2nd time, I got a prompt to install Root as I was not rooted, but I did root weeks ago, when I went to CM.
Any help/ advise/ suggestions are welcome.
I would really rather not ODIN to stock, but will if I have to, is there a way to snatch internalSD files before the flash?
Click to expand...
Click to collapse
If you can't boot into system, and TWRP will not restore your Nandroid I think ODIN to stock is inevitable. It really doesn't take too long. ODIN stock, re-root, install TWRP/CWM and restore your backup or flash Google Rom and LOKI this time.

blyndfyre said:
If you can't boot into system, and TWRP will not restore your Nandroid I think ODIN to stock is inevitable. It really doesn't take too long. ODIN stock, re-root, install TWRP/CWM and restore your backup or flash Google Rom and LOKI this time.
Click to expand...
Click to collapse
Thank you, from what I read, ODIN does not wipe our internalSD, is that correct or am I misreading it?

[Q] Failed to install KitKat

Hi guys. I wanted to install Kit Kat on my defy, follow instruction entered TWRP, nandroid backup, wipe everything except sdcard, install recovery, reboot and now I'm stucked in Android system recovery (3e) and dont know how to proced from here. I only have theses options:
1. Apply sdcard:update.zip
2. Wipe data/factory reset
3. wipe cache partition
Under these it says:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/caller
E: Can't mount CACHE:recovery/log
When I apply sdcard:update.zip it says Faild to open /sdcard/update.zip (No such file or directory), which is normal as my update.zip is on /sdcard/ROM/update.zip.
I also tried to wipe cache partition but nothing happened.
Could someone help me?

brendza said:
Hi guys. I wanted to install Kit Kat on my defy, follow instruction entered TWRP, nandroid backup, wipe everything except sdcard, install recovery, reboot and now I'm stucked in Android system recovery (3e) and dont know how to proced from here. I only have theses options:
1. Apply sdcard:update.zip
2. Wipe data/factory reset
3. wipe cache partition
Under these it says:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/caller
E: Can't mount CACHE:recovery/log
When I apply sdcard:update.zip it says Faild to open /sdcard/update.zip (No such file or directory), which is normal as my update.zip is on /sdcard/ROM/update.zip.
I also tried to wipe cache partition but nothing happened.
Could someone help me?
Click to expand...
Click to collapse
Wich ROM are you using?

brendza said:
Hi guys. I wanted to install Kit Kat on my defy, follow instruction entered TWRP, nandroid backup, wipe everything except sdcard, install recovery, reboot and now I'm stucked in Android system recovery (3e) and dont know how to proced from here. I only have theses options:
1. Apply sdcard:update.zip
2. Wipe data/factory reset
3. wipe cache partition
Under these it says:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/caller
E: Can't mount CACHE:recovery/log
When I apply sdcard:update.zip it says Faild to open /sdcard/update.zip (No such file or directory), which is normal as my update.zip is on /sdcard/ROM/update.zip.
I also tried to wipe cache partition but nothing happened.
Could someone help me?
Click to expand...
Click to collapse
Flash sbf. Root phone. Install cm10.2. Install update-recovery.zip. Install KitKat
Sent from my MB526 using Tapatalk 4

Thank you for answers.
@leandrolutz - It was one that Quarx built, from 02.12.13 CM.
@thekguy - I had to flash SBF, now I'm on Android 2.2.2. I'll follow your instructions. Just have one question, should I install CWM or TWRP? I follow guide, in which I installed update-recovery.zip from TWRP after wiping all date except those on sd-card. then After that, I couldnt get into new recovery. Is this right order to update to KitKat?

brendza said:
Thank you for answers.
@leandrolutz - It was one that Quarx built, from 02.12.13 CM.
@thekguy - I had to flash SBF, now I'm on Android 2.2.2. I'll follow your instructions. Just have one question, should I install CWM or TWRP? I follow guide, in which I installed update-recovery.zip from TWRP after wiping all date except those on sd-card. then After that, I couldnt get into new recovery. Is this right order to update to KitKat?
Click to expand...
Click to collapse
SBF, root, 2ndinit. Then you install CM10 (4.1), reboot, install CM10.2 (4.3), reboot, install update-recovery.zip, REBOOT (without any wipe), install CM11 (4.4).
DO you want to use ART or DALVIK? :highfive:

brendza said:
Thank you for answers.
@leandrolutz - It was one that Quarx built, from 02.12.13 CM.
@thekguy - I had to flash SBF, now I'm on Android 2.2.2. I'll follow your instructions. Just have one question, should I install CWM or TWRP? I follow guide, in which I installed update-recovery.zip from TWRP after wiping all date except those on sd-card. then After that, I couldnt get into new recovery. Is this right order to update to KitKat?
Click to expand...
Click to collapse
You will need to use twrp, the one included with the respective build. From 4.3, you should flash recovery zip, reboot without wiping, and from recovery you should be able to flash kk
There's a button dedicated to thanks
Sent from my MB526 using Tapatalk 4

Thanks all for your help. I installed 4.3 and after that flashed recovery where I made a mistake and wipe dalvik cache after instaling (did this before yours answers):crying:. After restart, I couldnt enter twrp recovery (as soon as I enter defy restarts), only bootmenu and stock recovery from there. Luckily I havent wiped system so I still have 4.3 installed. Then I tried to install recovery from GooManager (didn't make it), stock recovery where I get message: "Failied to verify whole-file signature. Signature verification failed. Installation aborted".
Is there any way to install twrp without having to do all from the begining (sbf, root...)?

Hey guys, problems again. Didnt find way to install recovery so I decided to do all steps (sbf, root, 10.1...) again.
First I entered bootloader, connected usb, RSD lite and flashed same sbf as I did few days ago. Unlike last time, this time it wont flash, RSD did his job (erasing flash memory, flashing code group...) and when it comes to reboting, in RSD is written finished, but defy didnt turn on, not even motorola logo on screen. Take out battery, try to get into stock recovery and bootloader (volume down and up+power on), but still nothing. Then tried other sbf, 3 od them (retail French) but same thing happened every time, dead screen). Only thing that points that tel.is alive is white led that turns on when I connect it to PC.
I cant understand why 2 days ago when I flashed sbf, everything was fine and this time it refuses do complete. Only difference is that this time it was installed Android 4.3 and last time 4.2.2.
Any suggestions.

If your current sbf isn't working, try dfp 231 or a sbf newer than your current one. It should get you at least to stock recovery, from where you can wipe data and revive your defy.
From 4.3, just flash update recovery, don't wipe or flash anything else. Reboot, and enter recovery once again. Now install 4.4 and it should work
Although, that should not have occurred just by dalvik wipe. Make sure the 4.3 build you use is recent
FYI you could have fixed recovery by extracting and overwriting bootmenu folder from zip
Sent from my MB526 using Tapatalk 4

Hey thekguy, thank you very much. I managed to revive my defy with 4.5.1-134 DFP-231 Retail.en.EU CEE and now I'm using Android 2.3.6. I'm reading another topic http://forum.xda-developers.com/showthread.php?t=1820282 where it says that after flashing 4.5.1-134 DFP-231 Retail.en.EU CEE, it should than be flashed with rooted SBF 4.5.1-134 DFP-231 Retail.en.EU CEE Rooted SBF.
Should I also flash this second SBF or go directly to 4.3?
Thanks again.

Root with framaroot, no need for 2nd sbf
Sent from my MB526 using Tapatalk 4

Got stuck at formatting cache in the latest TWRP (I9505 - jfltexx)

Phone is working, I suppose doing his job in the process. The problem is that I am waiting already 20 minutes. I am afraid of getting CPU burnt (it is at 51 grades of Celsius).
I have read about the issue and about also the solution [enabling rm -rf in the twrp settings]... But now I am in the process, so not sure if I should shut the phone down or not..

Did you do a factory reset or advanced wipe?

I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?

binuralka said:
I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?
Click to expand...
Click to collapse
No. Your bootloader is already unlocked, otherwise it wouldn't have let you flash TWRP.
Have you tried factory reset? Or mounting system manually?
You can also try to mount system by using TWRP's built-in terminal emulator.

Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?

binuralka said:
Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?
Click to expand...
Click to collapse
Error 7 means the ROM is not compatible with your model.

Have you tried different version of twrp?

That was a really terrible testing day... I tried every twrp till version 2.8.6 that worked after odin flashing. I managed to mount system and do all wipes. I flashed ROM and gapps, everything went smoothly... But the thing was that the phone started to shut down by itself. Without a message, simply black screen and restart and bootloop after samsung logo. I decided to load 4.4.2 stock with repartitioning (pit file)... 10 hours ok and then again shutting down by itself.
Have you experienced this kind of behaviour?