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] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.

Anyone have any idea?
Thanks

Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck

CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?

You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes

I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.

Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.

patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.

bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.

utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.

monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.

you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)

Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.

Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/

Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.

I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?

[Q] Can't use LGFlashTools to get back to stock, any ideas?

So I unlocked my AT&T D800 G2, and now it says that the model is D802. When I try to use LGFlashTools to go back to stock using the DLL and the TOT file, it says that the models don't match because the files are for D800 and D802. The D802 files don't work and give me a LAF memory size error. What are my options?
The reason I want to go back to stock is because I flashed TWRP 2.8.2.1 and then flashed the RessurectionRemix ROM, but then I encrypted the drive and then decided that maybe the ROM was a little too unstable for me. But in TWRP it says that it can't mount /data and I can't wipe or format /data, or mount it, so I can't clear everything and start from scratch. TWRP says that my internal storage is 0MB and that there are no files on the sdcard, probably because it's not mounted.

Welp... I think I might have ****ed up... I tried creating a data partition using mk2fs /dev/block/platform/msm_sdcc.1/by-name/userdata and TWRP was able to mount the /data partition, but after I flash a ROM and reboot, it goes into fastboot instead... Am I screwed? I still have access to TWRP and ADB, which is the only reason why I might not be totally screwed.

Ok, so the reason that it wasn't working was because I flashed the D802 version of ResurrectionRemix like an idiot (I had downloaded two versions in my folder and was using the wrong one). I flashed the D800 version and it worked. Ugh.

Just so that this thread isn't completely useless, I'll put some information here.
If you encrypt your internal storage because of some Exchange email policies or something, TWRP won't be able to mount your /data partition.
You can fix this by doing:
adb shell
mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
This will create a data partition for you. Then you'll need to go into TWRP and change the file system to ext4.
Now you should be able to mount the partition, flash a ROM, and do all that good stuff.

Gt i9506 10 gb used by system after flashing.

hello there!
some months ago i tried a custom firmware on my 9506 (i think that was the first version of arya mod) but i didnt kinda like it so i downloaded again the stock fw and flashed it back.
i did my typicall "download the basic apps" routine and on the 4th app an "insufficient storage available" message appeared on my screen and i was like "lol whats wrong?" i checked on and i found that 10.6Gb was used by system.
Well i thought that i downloaded maybe a bugged stock rom and i didnt have the free time at the time to check whats wrong so i decided to live with it till i find some spare time to check it again.
Yesterday i downloaded and flashed the lineage os fw and i was sure that this would fix the problem...but...well it didnt..still 10.6 used by system.
i tried wipe EVERYTHING (dalvik/cache/system/internal) and reflashed again but still nothing,i flashed again the stock rom,still nothing, i searched online but i didnt find a solution, i downloaded diskusage app to see where are those 10gbs but i couldnt figure out where they where.
So if anyone knows anything or had the same or similar problem it would be great if he/she write here and give a solution or some tips.
Thanks in advance

Try format data from recovery.

Pwnycorn said:
Try format data from recovery.
Click to expand...
Click to collapse
Thanks for your reply!
You mean the wipe option or am i missing something?
I did wipe everything via twpr recovery from the "advanced wipe option" and checked everything except my sdcard and still nothing.
is there any other way to completly format it ? if so,then how i can do it?

bakos360 said:
Thanks for your reply!
You mean the wipe option or am i missing something?
I did wipe everything via twpr recovery from the "advanced wipe option"
Click to expand...
Click to collapse
There's a format data option there too.

Pwnycorn said:
There's a format data option there too.
Click to expand...
Click to collapse
lol i didnt see it and it was in front of my eyes!
i tried that too today but here is what is happening
Updating partition details...
...done
Full SELinux support is present.
Running boot script...
Done.
MTP enabled
E:unable to wipe '/data' -- unknown file system ' auto enable to format to remove encryption.
Mount media patd for recreate TWRP settings. /data/media/o
TWRP settings saved
Updating partition details...
...done..
for some reason it seems that its enable to format '/data'
any other option ? =/

bakos360 said:
lol i didnt see it and it was in front of my eyes!
i tried that too today but here is what is happening
Updating partition details...
...done
Full SELinux support is present.
Running boot script...
Done.
MTP enabled
E:unable to wipe '/data' -- unknown file system ' auto enable to format to remove encryption.
Mount media patd for recreate TWRP settings. /data/media/o
TWRP settings saved
Updating partition details...
...done..
for some reason it seems that its enable to format '/data'
any other option ? =/
Click to expand...
Click to collapse
Try flashing the stock ROM together with a PIT file

i fixed it guys
i flashed again cwm recovery and i formated EVERYTHING from there and then reflashed again the rom and gapps and that fixed the problem.
Thanks for your help !

For the record, CWM's incremental backup feature was what I believe was stealing your space. If you still have CWM on that device, make sure to set the default nandroid backup format to ".tar" instead of ".dup", clear out your nandroid backups, clear all the allocated space, and then upgrade to the latest version of TWRP.
CWM hasn't been updated in a few years now and has difficulty installing modern ROMs.

you are right i think.
if i recall corectly when i flashed that rom back then before the problem appeared, i used cwm recovery so yeah maybe thats the main reason that this happened.
i allready set the default backup to .tar and cleared out all the nandroid backups and i allready use TWRP now.
thanks for the tip mate!

Bricked partition messed permission

Hi here is my problem I can't flash any rom i tried TWRP and cwm and the Phil's edition the problem that after TWRP wipe the system to install the rom I get "couldn't mount /system partition rw. I tried to mount it manually and I can see the files so I moved to odin and flashed a stock rom and here came the same problem again I can't save or download anything even I can't take photos i tried to fix permission and nothing worked
Please ? help