Hello all
I'm having a problem here, Wanted someone to help me
I want to format my Data (wipe data/Factory reset)
I'm using ClockworkModRecovery v3.0.2.8 with HC 3.0.1
Now in the process of formatting data after a loooooong time it stops and says
Formatting /Data..
Error removing /data/misc/vpn/profiles/460173684741634006
Formatting /sd-ext
Formatting /sdcard/.and_secure
Data wipe Complete.
And System is not working very well. so Any help is appreciated
*EDIT: After reading the message, I tried to take a look at VPN Settings, but surprisingly enough when I click the VPN settings device hangs.
So there must be something wrong with the file system, Can anyone help me for Zero Flashing or formatting this Partition??
-I have tried Fastboot, it says Process was successful but nothing seems to have changed.
-And Although I dont have a Root access I dont think ADB is the answer but can I do it with?
you are using the wrong recovery
use this
http://forum.xda-developers.com/showthread.php?t=1074979
or
http://forum.xda-developers.com/showthread.php?t=1235170
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
After installing Quarx's CM 10.2 october 30th nightly (defy, not plus) the device seemed to be working normal but I then soon noticed that no internal storage is detected. (meaning I also could not install apps from the play store) Upon restarting, I go through the entire 'first time' sequence again and any thing I did before I restarted was not saved. I think this is because, when entering TWRP and going to mount, data is the only partition that it will not allow me to mount. Attempting to wipe the data partition yields the result 'unable to mount /data'. Is it possible to mount somehow in adb or terminal? Is anyone else having this issue? And is there any known fix?
InhibitorIota said:
After installing Quarx's CM 10.2 october 30th nightly (defy, not plus) the device seemed to be working normal but I then soon noticed that no internal storage is detected. Upon restarting, I go through the entire 'first time' sequence again and any thing I did before I restarted was not saved. I think this is because, when entering TWRP and going to mount, data is the only partition that it will not allow me to mount. Attempting to wipe the data partition yeilds the result 'unable to mount /data'. Is it possible to mount somehow in adb or terminal? Is anyone else having this issue? And is there any known fix?
Click to expand...
Click to collapse
Well , I had this problem too , but not with this ROM , enter in Motorola stock recovery , and make a wipe , after that , you should flash again a SBF , and put it again.. , or if you can still flash something , try to flash the 10.2 CM again.
Danarkin22 said:
Well , I had this problem too , but not with this ROM , enter in Motorola stock recovery , and make a wipe , after that , you should flash again a SBF , and put it again.. , or if you can still flash something , try to flash the 10.2 CM again.
Click to expand...
Click to collapse
But it won't let me. :/ Like I said before, attempting to wipe the data partition just gives me 'Unable to mount /data'. Does that mean the partition is corrupted, or can it be mounted somehow in the terminal? This has really become a headache...
As an update, I actually was able to wipe in the stock recovery, but going back to TWRP now shows that both my data and cache partitions cannot be mounted (or still corrupted). Would flashing a new sbf fix that? I can still access cyanogen if I boot normally but it is the same as before, no internal storage and nothing is saved after reboot.
InhibitorIota said:
But it won't let me. :/ Like I said before, attempting to wipe the data partition just gives me 'Unable to mount /data'. Does that mean the partition is corrupted, or can it be mounted somehow in the terminal? This has really become a headache...
As an update, I actually was able to wipe in the stock recovery, but going back to TWRP now shows that both my data and cache partitions cannot be mounted (or still corrupted). Would flashing a new sbf fix that? I can still access cyanogen if I boot normally but it is the same as before, no internal storage and nothing is saved after reboot.
Click to expand...
Click to collapse
Did you try to wipe data and cache in stock recovery ? I don't know if you will flash a SBF will fix that , try to wipe data and cache too , and after that if you can't boot , flash a SBF.
Hello,
my s4 doesn't boot anymore and something weird happens all the time. I already tried delete system and caches, then flash rom (aosp) but this doesn't help.
I think my data partition is corrupted, but I don't want to wipe it as it contains all my stuff.
PS: the screenshot shows files that aren't there, I checked in the filemanager and they are there.
filesystem repair gives:
/sbin/fsck.f2fs /dev/block/mmcblk0p29 process ended with error 139
Even backup fails:
createTarFork() process ended with error 255
What if you use the xposed uninstaller zip?
If the zip doesn't help then I'm pretty sure the only solution is to wipe data.
Happened to me too several times, randomly, during reboots. Sometimes my data would get automatically wiped, and other times my phone wouldn't boot unless I wiped the data partition.
I believe it has something to do with F2FS, because, since I changed back to ext4, I haven't had this problem.
GDReaper said:
What if you use the xposed uninstaller zip?
If the zip doesn't help then I'm pretty sure the only solution is to wipe data.
Happened to me too several times, randomly, during reboots. Sometimes my data would get automatically wiped, and other times my phone wouldn't boot unless I wiped the data partition.
I believe it has something to do with F2FS, because, since I changed back to ext4, I haven't had this problem.
Click to expand...
Click to collapse
I flashed stock and then started over. Somehow my rom zip got corrupted and I got the same problem. So I redownloaded and flashed, everything is good now
Sent from my GT-I9505 using Tapatalk
Is there a known bug with philz and wiping partitions? I cant wipe the cache partition or any partition, The screen continues to load but makes no progress. When I turn off and reset the phone, the cache cant be mounted again due to 'last logs' missing. So If I flash back to TWRP, the cache partition is empty 0mb instead of the usual 4mb residual. Re-formatting fixes the issue but it renders CWM-Philz a little useless when you cant even wipe the cache without issues.
Does anyone know a workaround for this?
Move to TWRP as a custom recovery. CWM/Philz has not been updated for a long time.