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
first of all I'm sorry to create a new thread and it is different from other's problem.
first I'll tell what I have done.
flashed f2fs recovery by bugerXXX
formatted data, cache partitions to f2fs
flashed lineage os by harsh
rebooted to system & it was booted.
(no problem till here)
then I again rebooted to recovery
backup system& it just rebooted in the middle of the process
and that's it it never rebooting to system.
it always rebooting to splash screen infinite times when I try to power it on.
recovery works
fastboot works
download mode works
tried flashing different ROMs
reformatted data cache partitions to ext4
it always rebooting to splash screen infinite times.
even I flashed ROM (kk&lp) with QFIL and results are same.
but after flashed kk it completed boot animation and entered setup wizard, then again it started to rebooting
I think it has some problem with partitions or emmc
is there any thing that I can do to revive my phone?
senthamizhan said:
first of all I'm sorry to create a new thread and it is different from other's problem.
first I'll tell what I have done.
flashed f2fs recovery by bugerXXX
formatted data, cache partitions to f2fs
flashed lineage os by harsh
rebooted to system & it was booted.
(no problem till here)
then I again rebooted to recovery
backup system& it just rebooted in the middle of the process
and that's it it never rebooting to system.
it always rebooting to splash screen infinite times when I try to power it on.
recovery works
fastboot works
download mode works
tried flashing different ROMs
reformatted data cache partitions to ext4
it always rebooting to splash screen infinite times.
even I flashed ROM (kk&lp) with QFIL and results are same.
but after flashed kk it completed boot animation and entered setup wizard, then again it started to rebooting
I think it has some problem with partitions or emmc
is there any thing that I can do to revive my phone?
Click to expand...
Click to collapse
Revert back your partitions to ext4
Wipe them
Fix them using fix option
Flash lollipop stock ROM
And see if it boots up
And next time be sure to ask for help before doing anything so that you don't end up like this
And contact me if it does not help
Don't forget to fix partitions
still same problem
The Hard Gamer said:
Revert back your partitions to ext4
Wipe them
Fix them using fix option
Flash lollipop stock ROM
And see if it boots up
And next time be sure to ask for help before doing anything so that you don't end up like this
And contact me if it does not help
Don't forget to fix partitions
Click to expand...
Click to collapse
you mean " repair file system " in twrp??
I have formatted system, data, cache to ext4
and repaired them using "repair file system" in twrp
flashed s061 stock ROM
but the problem still present.
and I wanna know what is " validated_emmc_firehouse_8916.mbn". can I use it instead of "prog_emmc_firehouse_8916.mbn" in QFIL ??
senthamizhan said:
you mean " repair file system " in twrp??
I have formatted system, data, cache to ext4
and repaired them using "repair file system" in twrp
flashed s061 stock ROM
but the problem still present.
and I wanna know what is " validated_emmc_firehouse_8916.mbn". can I use it instead of "prog_emmc_firehouse_8916.mbn" in QFIL ??
Click to expand...
Click to collapse
The sequence of flashing files is written in scatter file so even of you change the file and it is not meant to be flashed it won't flash
I don't think there might be a hardware fault
i am also suffering from this same problem
Hi guys, i'm stuck in Rock and a hard place here and couldn't figure this one out. I've installed CyanogenMOD previously but that was a while ago and different process. What happened is I installed LineageOS 2 days ago and everything worked fine except No Sim Card is detected so I can't make phone calls and log into my Google account to sync.
Hence to resolve the Sim Card issue, what i did is to attempt to flash Bootloader, System , Radio images but it didn't work when i try to flash and also install LineageOS zip file. And in order to try resolving Mount issue, I proceed to Advanced Wipe -> checked System, Data, Cache -> Repair and Change File System -> changing ext4 to ext 2 . This formated all my User data which includes the ROM zip file i needed to install and load. I tried using Nexus Root Toolkit to restore into stock but it says no Fastboot/ ADB detected. And my computer couldn't detect my Nexus 6p.
Please provide solutions. Desperate here.
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Exodusche said:
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Click to expand...
Click to collapse
Thank you for replying Exodusche. But i have switched back to EXT 4 and finds the system formatted and user data deleted! Plus my computer is unable to recognize my phone while i'm stuck at Bootloop =( Talk about difficult situations. So i'm unable to test your no sim solution at this point. Need to retrieve deleted files or at least push files from Desktop to Phone.
Any ideas?
So I'm having a weird issue. Whenever I flash any kernel other then stock it stays stuck at the LG logo. I have to pull battery and then restore the stock kernel backup. I have no idea why I'm having this issue. I've also noticed that TWRP sometimes says cannot mount system (probably not the culprit but just adding more info).
Model: T-Mobile (h918)
When I had the "cannot mount" issue, a system partition format was needed from within TWRP. I took a backup of system (not a system.img backup), then formatted system only, then restored the system. It's been fine ever since.
I'm not sure if any special pocedure is needed for the h918 in order not to brick anything. I'm on US996.
I hope that made sense. Please wait for a second opinion before trying anything.
pistacios said:
When I had the "cannot mount" issue, a system partition format was needed from within TWRP. I took a backup of system (not a system.img backup), then formatted system only, then restored the system. It's been fine ever since.
I'm not sure if any special pocedure is needed for the h918 in order not to brick anything. I'm on US996.
I hope that made sense. Please wait for a second opinion before trying anything.
Click to expand...
Click to collapse
Yea. Seems like I have to format system all the time. Also have to format my internal storage all the time. My backups never seem to restore correctly. I can't flash a new ROM because it wont boot with a different kernel. I might just flash KDZ and root all over again.
Hello guys,
I had Lineage OS installed on my Galaxy S10+ and it got into boot loop after my phone lost power a few times because of low battery. The system halts at the Lineage Logo animating forever.
The problem is I canont access encrypted files on /data partition as it seems default Samsung encryption is used (and I have not disabled encryption when I was installing Linaage - I know - my mistake...) What I'm thinking to do is to do a dirty flash of the same system or an upgrade.
But before I will do it, I would like to do full backup of /data partition - sector by sector, so if my dirty flash won't work I can restore /data partition again and try to fix it again without loosing my data.
So my question is: How can I backup whole /data partition as an image? And how can I restore it?
My system is going into boot-loop, but I can get into recovery.
Thank you very much!!!
Encryption keys not withstanding it's the user partition that's likely been corrupted. You see where I'm going with this?
You try safe mode?