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
I was trying to fix an annoying error in which my phone would power down and go into a boot loop out of nowhere by installing a custom rom. I've installed new roms on plenty of phones, so it usually isn't any problem.
However, upon using the app AutoRec that was recommended by many to install a custom recovery (and yes I did make sure I used the Lollipop version for my Lollipop phone), my phone was wiped and now has no OS. I can get into TWRP, so I can use ADB and push files, but there's no file system to install to if I decide to flash. Programs like LGUP and LG Flash Tools can't communicate with the unmounted storage.
Repairing, wiping, and reformatting the file system from within TWRP only produces the "Unable to mount '/data'" error. I can't mount the partitions manually. Commands to format the system don't work either. I've been stuck on this for days. Please help.
Hey,
i have TWRP installed and had the samsung galaxy s8 port running for about 1 year without problems. Since a couple of days it doesnt boot into the ROM anymore. So i went into TWRP and tried a restore of a backup. The backup process just freezes somewhere and i have to restart the phone. I also tried clean flashing a couple of ROMs but every installation is crashing.
TWRP has never crashed before so i'm guessing Hardware is broken?
Or is it possible that it ****ed up my partition table? it always crashes when trying to install or restore system partition. Also repairing the file system fails with error 4.
Any help is welcome, thx!
flash newest twrp again, partition, full wipe and install rom. of that doesnt help thsn flash stock with odin and go all the way to custom
Hi guys,
I'm not newbie with flashing but this one I don't understand.
Probably I've done some mistakes with flashing/install/uninstall of roms/magisk/twrp.
Now I'm stuck with TWRP and can't boot into system because of something.
Every time I run TWRP and try to install all my files are encrypted, no matter I install TWRP by .img or .zip. Only working TWRP with decryption is temporary one, by "fastboot boot twrp-3.3.1-6-fajita.img" command. But when I flash it by regular .img file by this tut (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), after reboot it's back like 3.3.1-6-fajita version, BUT without decryption skills.
I thing I done some mistakes with uninstalling magisk ect. but I think it doesn't matter.
I tried to uninstall magisk by Magisk-uninstaller-20190204.zip on both slots, I tried install all again in regular way (install temp TWRP through fastboot command, install TWRP through this temp TWRP, install full newest OTA .zip, install TWRP again (I know I shouldn't but I tried both combinations - .zip and .img) and install Magisk and at least system reboot. But when I rebooted between OTA and Magisk (like guide tells) TWRP can't decrypt files. No matter what I've done nothing helped.
What can I do that I have not done yet? Of course, all is about I don't want format my data and re-install all from the scratch...
So... tell me, is possible to make TWRP great again?
Is everything only showing as encrypted when you try to restore a backup? I've been booting the img via fastboot then flashing the zip as it seems you have and it's been working fine as far as it staying installed and not showing all my files as scrambled, I also made the mistake of using Magisk uninstaller at one point, that didn't end well. Seems these A/B phones are temperamental as hell. I read somewhere else that doing backups to USB storage my be more reliable for a backup restoration, not sure if that would effect the encryption issues or not but I may have some time to test that tonight.
I've done that too - not helped. I restored my full nandroid backup by fastboot temp recovery (as I wrote, only this one can decrypt my files) but I've got "You device is corrupt"... and of course TWRP can't decrypt my files.
Hi,
so i've tried to root my phone and then to install a custom rom. the root went without any problem. After the root, i tried to install lineage OS 16.0 and followed this guide:
https://forum.xda-developers.com/redmi-note-7/development/rom-lineageos-16-0-t3923203
i downloaded the rom and gapps, put them on my root directory of my phone and then i wiped System,Cache ,Data, Internal Storage and Format Data. After wiping, the roms were gone, so i rebooted and transfered them again into the root directory. Then, i went onto installing (just like i did with magisk) but an error occurred saying:
E: String resource 'zip_compatible_err' not found. Using default value.
Zip Treble compatibility error!
Invalid zip file format!
Error installing zip file '....'
Updating partition details...
...done
Ok. So then, i tried to install another Custom Rom so i went for Oxygen OS, it actually did install but then i couldn't boot into it because it was telling me there was an 'Android System Error'. Ok, back in TWRP, i wiped everything and then i tried to install the Original ROM but i got the same error as above.
For now i tried to download the miFlasher tool but it only wants to download some driver and it literally takes forever.
Hope you can help me...
Download Fastboot ROM for your device and do this Fastboot Method
marcopast said:
Hi,
so i've tried to root my phone and then to install a custom rom. the root went without any problem. After the root, i tried to install lineage OS 16.0 and followed this guide:
https://forum.xda-developers.com/redmi-note-7/development/rom-lineageos-16-0-t3923203
i downloaded the rom and gapps, put them on my root directory of my phone and then i wiped System,Cache ,Data, Internal Storage and Format Data. After wiping, the roms were gone, so i rebooted and transfered them again into the root directory. Then, i went onto installing (just like i did with magisk) but an error occurred saying:
E: String resource 'zip_compatible_err' not found. Using default value.
Zip Treble compatibility error!
Invalid zip file format!
Error installing zip file '....'
Updating partition details...
...done
Ok. So then, i tried to install another Custom Rom so i went for Oxygen OS, it actually did install but then i couldn't boot into it because it was telling me there was an 'Android System Error'. Ok, back in TWRP, i wiped everything and then i tried to install the Original ROM but i got the same error as above.
For now i tried to download the miFlasher tool but it only wants to download some driver and it literally takes forever.
Hope you can help me...
Click to expand...
Click to collapse
Those recoveries are old.. Use orange fox recovery 10.0-2 it will work and format data then install rom.
title?
@BlackGarnett
Thanks, that help me on a quick one!
@loseyourself
Also thank you for this advice, i'm new to rooting smartphones and install cfw since i was using iPhone for the past few years.
But now i got another new question: if i use orange fox recovery and i run a backup with it (i think there will be an option to do a backup), then i format all data and internal storage, can i still recover from the backup or will it be deleted?
thanks again!
marcopast said:
@BlackGarnett
Thanks, that help me on a quick one!
@loseyourself
Also thank you for this advice, i'm new to rooting smartphones and install cfw since i was using iPhone for the past few years.
But now i got another new question: if i use orange fox recovery and i run a backup with it (i think there will be an option to do a backup), then i format all data and internal storage, can i still recover from the backup or will it be deleted?
thanks again!
Click to expand...
Click to collapse
When u make a backup to internal all is lost after format it. Orangefox put files on the internal sd. After format reboot recovery in the option section and flash again Orangefox.
Help me ,i need efs backup for unbrick my decices please