So just wanted to share this in the event anyone else runs into the problem. I was running CWM 2.5 and CM7 RC2 just fine for a while now and I decided to clean my SD card yesterday since I have tons of empty folders from prior app/rom installs. After deleting some folders, my SD card would not be read by the phone. I rebooted and it sent it into a bootloop. Tried to format SD card in recovery and the settings menu, no avail. Tried to partition in adb to correct the issue and /DATA would not mount for the life of me. I could get it to mount via adb, but not in recovery. Any time I tried to factory reset or format DATA, it would say it cant mount the partition.
Anyway, I tried the latest version of CWM (3.8) and it managed to format each partition without any issues. I could then install CM7 without any issues and it booted right up.
So if anyone is experiencing SD card issues when altering the filesystem in any way, try upgrading the recovery image. It would have saved me a good number of hours troubleshooting, but hey at least I learned adb better lol
I am having the same exact problem, bootloop with no way to access card. How did you get CWM updated?
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
Hello,
I wanted to revive my old samsung galaxy J1 and try to install a ROM on it. I found a compatible cyanogenmod12 ROM for it.
At first i just wanted to get the phone back to boot up correctly but it was stuck on the Samsung loading screen. With no other option, i flashed TWRP recovery and found out the files were kinda corrupted. The log showed it was unable to mount data, cache and system. So i went online looking for fixes.
All said i had to repair them by going to "wipe" then "advanced wipe" and one by one re-formatting the files to FAT4 OR exFAT. and that's when i found out all the files were gone since none of the 6 options (EXT1, EXT2, EXT3, ntfs or FAT) worked.
I thougt installing the ROM would fix this by creating new files but since it was unable to mount system, cache or data., i couldn't do anything.
MY QUESTION: is it possible to recover anything or to manually create the folders and files since it's (unpossible) to install a ROM on it?
There's gotta be a way the files have been put on it for the first time....
Hi
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.
After doing the Tmo to international conversion, I downloaded a new rom and appropriate files. They show in ES File Explorer, but I am unable to locate them in TWRP. Anyone have this issue, I have to be missing something. Thanks in advance.
just put them in downloads and go there in twrp
Downloads folder literally doesn't exist in TWRP for me.
The whole file system looks different at / in TWRP than in ES explorer.
You need to mount sdcard/storage in TWRP
I have tried with no success. Under mount it won't even allow me to click the option to mount sd card. When I click sd card in the list I get a slew of folders with random character names (ie- ggDjkk7hFJJgGvV)
I have noticed in my oos system settings my phone shows encrypted. Could this be why? Is there a way to turn off encryption that I'm not seeing, if this is the cause?
Floridaplur said:
I have tried with no success. Under mount it won't even allow me to click the option to mount sd card. When I click sd card in the list I get a slew of folders with random character names (ie- ggDjkk7hFJJgGvV)
Click to expand...
Click to collapse
That means it's still encrypted. What version of TWRP are you using? My guess is you are using the wrong TWRP. You can try booting back into OOS and removing your PIN / Password / fingerprints.
Otherwise you may have to boot back into OOS, backup your data, and format the data partition. Reboot to recovery again, then transfer whatever you need to TWRP, flash, and it will re-encrypt on the next boot. Again though, make sure you have the correct TWRP first before you go through all this trouble.
I am using bluespark TWRP that was in the guide to Tmo intl conversion.
Floridaplur said:
I am using bluespark TWRP that was in the guide to Tmo intl conversion.
Click to expand...
Click to collapse
have u tried the other twrp builds that may be more up to date?
Floridaplur said:
I am using bluespark TWRP that was in the guide to Tmo intl conversion.
Click to expand...
Click to collapse
Yes, that one will give you the issue. The encryption did not seem to be working in it.
You should use the latest version of this recovery to resolve your issue: [RECOVERY][3.3.0-2][fajita]Official/Unofficial TWRP recovery for OnePlus 6T (Stable)
So after updating to twrp 3.2.2, I was successfully able to clean install havok and have everything working. What I have noticed though, is that after booting into the rom, it is encrypted again.
The first go I realized I had the wrong gapps, so I downloaded the correct one, and rebooted to recovery. At this point it was encrypted and I couldn't see downloads again. I decided to do a data and cache wipe and installed everything via adb sideload and it went perfectly. I guess this phone just wants me to only load roms when I have my laptop with me. Either way, I'm up and running. I miss how easy things we're back in the HTC Evo days.