Phone is working, I suppose doing his job in the process. The problem is that I am waiting already 20 minutes. I am afraid of getting CPU burnt (it is at 51 grades of Celsius).
I have read about the issue and about also the solution [enabling rm -rf in the twrp settings]... But now I am in the process, so not sure if I should shut the phone down or not..
Did you do a factory reset or advanced wipe?
I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?
binuralka said:
I used advanced wipe, I got really angry with formatting so I removed the battery ... but now I have a problem: failed to mount system... I installed the twrp through odin... And before that I did not do anything, do I have to unlock bootloader or something like that?
Click to expand...
Click to collapse
No. Your bootloader is already unlocked, otherwise it wouldn't have let you flash TWRP.
Have you tried factory reset? Or mounting system manually?
You can also try to mount system by using TWRP's built-in terminal emulator.
Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?
binuralka said:
Now I flashed 4.4.2 with and Odin, phone was ok. Then I flashed latest twrp and now the system was mounted. I did a backup and wiped all again with advanced wipe. Then I tried to install ROM but it fell again to a error 7 - system not mounted. How can I mount it manually? what command is that?
Click to expand...
Click to collapse
Error 7 means the ROM is not compatible with your model.
Have you tried different version of twrp?
That was a really terrible testing day... I tried every twrp till version 2.8.6 that worked after odin flashing. I managed to mount system and do all wipes. I flashed ROM and gapps, everything went smoothly... But the thing was that the phone started to shut down by itself. Without a message, simply black screen and restart and bootloop after samsung logo. I decided to load 4.4.2 stock with repartitioning (pit file)... 10 hours ok and then again shutting down by itself.
Have you experienced this kind of behaviour?
Related
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
Trying install this rom:
http://forum.xda-developers.com/showthread.php?t=2494756
Went to CWM and started full wipe/reset and it got stuck on:
Formatting /cache
had to hard reboot with long press on power button then my stock room booted up, so means nothing formatted...
What to do next guys?
Thanks!
Install twrp, and in preferences check format method -r, fs. Somthing like this. Or wait longer, with standart formating it takes up to 20-30min!
Melodycd said:
Install twrp, and in preferences check format method -r, fs. Somthing like this. Or wait longer, with standart formating it takes up to 20-30min!
Click to expand...
Click to collapse
Why does the cache take forever to format on the G2?
ditto
same thing happened to me during a rom install
as i have only had the phone a week i was a bit flustered
i did what they recommended
went into twrp settings and checked <<use rm - rt>>
and then reinstalled the rom, reboot was ok this time
so far so good
yeah i have the same question about wiping cache - on my samsung note 2 using twrp it was so fast
This is a problem in twrp i think, i was using twrp on many devices before, but didn't have any problems with wipe.
Hello. I tried doing the 5.0 update to my tablet using the factory images. It failed on sending /system and now the whole tablet isn't working. I loaded Philz, to wipe the whole tablet, and it errors mounting /data and /system when attempting to wipe. I have tried wiping everything in every way, and nothing. I cannot get anything to flash on the tablet. Any help?
Yoyodude1124 said:
Hello. I tried doing the 5.0 update to my tablet using the factory images. It failed on sending /system and now the whole tablet isn't working. I loaded Philz, to wipe the whole tablet, and it errors mounting /data and /system when attempting to wipe. I have tried wiping everything in every way, and nothing. I cannot get anything to flash on the tablet. Any help?
Click to expand...
Click to collapse
Ya man, its the same with me . Hope someone, reply's with a solution for it.
Maybe try with latrst version of twrp instead of Philz.
Flash TWRP
Wipe
Advanced wipe
Select system
Repair or change file system
Repair
Let it do its thing, then flash your ROM.
Send your thanks to @Paramesh96. He gave me this advice on my thread. Still haven't been able to flash factory images. But I can get my tablet up & running again with this guide
I could do this, but I have no way of moving a zip file to the tablet.
Yoyodude1124 said:
I could do this, but I have no way of moving a zip file to the tablet.
Click to expand...
Click to collapse
I flashed TWRP, went through the process, rebooted to bootloader, reflashed TWRP, reboot to recovery & mtp was enabled to access the sdcard
Hello Guys am facing a problem in twrp since 3 days.. I flashed twrp-3.0.2-4-hero2lte.img.tar using odin and everything was ok when I booted to recovery it asked me to allow modification (everytime I boot to recovery)then flashed supersu and got an error cannot mount data Then I tried to wipe data I got error cannot mount /data
I changed Data partition type to FAT ,wipe data was ok it worked but when I flash the rom and start the phone I get an error Encryption failed reset device needed .
Any Help
I flashed stock firmware 4 times and nothing changed
Need Help
mrad4tech said:
Hello Guys am facing a problem in twrp since 3 days.. I flashed twrp-3.0.2-4-hero2lte.img.tar using odin and everything was ok when I booted to recovery it asked me to allow modification (everytime I boot to recovery)then flashed supersu and got an error cannot mount data Then I tried to wipe data I got error cannot mount /data
I changed Data partition type to FAT ,wipe data was ok it worked but when I flash the rom and start the phone I get an error Encryption failed reset device needed .
Any Help
I flashed stock firmware 4 times and nothing changed
Need Help
Click to expand...
Click to collapse
Flash hydra rom and done
umijani010 said:
Flash hydra rom and done
Click to expand...
Click to collapse
Really man??what makes this rom solve the problem I heard many things about this hydra rom
mrad4tech said:
Hello Guys am facing a problem in twrp since 3 days.. I flashed twrp-3.0.2-4-hero2lte.img.tar using odin and everything was ok when I booted to recovery it asked me to allow modification (everytime I boot to recovery)then flashed supersu and got an error cannot mount data Then I tried to wipe data I got error cannot mount /data
I changed Data partition type to FAT ,wipe data was ok it worked but when I flash the rom and start the phone I get an error Encryption failed reset device needed .
Any Help
I flashed stock firmware 4 times and nothing changed
Need Help
Click to expand...
Click to collapse
You need to wipe the data partition in TWRP in order to decrypt it.
wipe/format data/type YES
TWRP doesn't yet support samsungs encryption.
wiping data will obviously remove everything, so backup first.
immediately after wiping data, flash an updated supersu, or dm-verity disable
Flashing a rom over an encrypted data partition will do nothing to solve it unfortunately.
im having big problems about vendor. for start im giving some info:
device: mi a1 (tissot)
current os: lineage OS 17.1
root: yes
twrp: can install or use just booting .img
i unlocked my device and installed twrp. there is no problem.
i wanted flash lineage OS and i wiped my device. gives error about cannot mount /vendor
i installed treble supported twrp and installed lineage OS. flashed magisk. installed microg...
then i tried flash mapsv1.zip which is recommended for microg. then booom. another /vendor error.
now i can boot device. i can use everything except gps. google maps app cannot found location. yandex maps can found and i can use it until lock screen or going main screen (or another app). then it starts stopping everytime until i clen its data and cache. then again... in chrome when i open google maps and try found my location chrome stops.
i tried to change /vendor/etc/gps.conf. its still same.
what to do now guys? im worrying about if i try re-flash rom it doesnt flash and device bricked. any solution without re-flash rom? what causes to cannot mount /vendor after solved it?
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
KaaMyA said:
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
Click to expand...
Click to collapse
Dalvik cache , system, data, and cache. My device is not rebooting too much. Sory if i couldn't explain. Everything working fine except when an app tries use my location, app stops running, i cant flash anything right now.
İ thought anyone knows mapsv1.zip file(microg.org) and which files are replaced or added by this file when flash it. And can i do it manually? Btw i can read and write /vendor file with solid explorer
İf needed to re-flash rom thats ok but i think lineage OS was perfect for me until this error. And a last thing: can i backup my settings. (İ already took backup of everything in stock when unlocked bl)
Thank you for help
Edit: gps problems started when i tried flash mapsv1
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
KaaMyA said:
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
Click to expand...
Click to collapse
Okey ilk try it and share the result night. But is it possible to backup settings of phone?
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
KaaMyA said:
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
Click to expand...
Click to collapse
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Nurullah44 said:
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Click to expand...
Click to collapse
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
portox said:
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
Click to expand...
Click to collapse
Are you sure? Bcs i can view and change /vendor in root path. Treblizing is updating and repairing system partitions right? İ am using treble support twrp, flashed stock rom via mi flash(said error but worked fine) then how to treblize a device? And is this required for anything(like a rom, an app)?