I have a Galaxy S duos 2 which isn't booting, and, when it rarely does boot, it shows "Device memory damaged", in recovery mode it displays "E:Failed to mount /data"; Factory reset did nothing, neither did flashing it, I tried installing CWM and TWRP, however, I failed at both of them, it keeps coming back to stock recovery. It isn't rooted or unlocked in any way, I also tried a full flash and, well, also nothing, and I am a little stuck now.
A few more things I tried:
— Re-partitioning;
— Removing battery after flashing
— Using another Odin version
— Using other ROMs
— Changing the recovery.img in the ROM for the TWRP's recovery.img
After a few tries I can't get it to completely boot, and it freezes anywhere except for the download and recovery mode, even the "charging" animation freezes. It also sometimes shows "No command" in recovery mode, or "Error", and it requires me to remove the battery and restart.
I truly don't know what else to do.
Obs: My phone model is GT-S7582L, I don't know if it actually changes something.
Obs: I don't really care about the data, it isn't my main concern, if it works, it's already great!
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
I'm still stuck in this situation...
Any help plz?
IYaWonaRoo said:
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
Click to expand...
Click to collapse
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
savagevegeta said:
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
Click to expand...
Click to collapse
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
IYaWonaRoo said:
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
Click to expand...
Click to collapse
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
savagevegeta said:
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
Click to expand...
Click to collapse
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
IYaWonaRoo said:
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
Click to expand...
Click to collapse
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
savagevegeta said:
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
Click to expand...
Click to collapse
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
IYaWonaRoo said:
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
Click to expand...
Click to collapse
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
savagevegeta said:
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
Click to expand...
Click to collapse
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
IYaWonaRoo said:
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
Click to expand...
Click to collapse
The steps to fix storage 0mb are clearly posted in the TWRP thread.
ashyx said:
The steps to fix storage 0mb are clearly posted in the TWRP thread.
Click to expand...
Click to collapse
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
IYaWonaRoo said:
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
Click to expand...
Click to collapse
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
ashyx said:
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
Click to expand...
Click to collapse
I probably was doing it wrong lol. But its fixed now so dont worry
IYaWonaRoo said:
I probably was doing it wrong lol. But its fixed now so dont worry
Click to expand...
Click to collapse
Your data partition will still be unmountable and remain 0mb, which means you are unable to make a backup.
However if you're happy with it in that state...
Re: bootloop
have you tried grabbing the no verity/encrypt form the rooting forum, this solves seandroid problem
Trying to root my phone. Flashed TWRP in Odin, then installed SuperSU through TWRP. At the end it gives me the error in the title, and I get a 'failed integrity check' when booting into the system.
Help?
I've always read you have to do a factory reset after TWRP installation due to encryption, but apparently you don't have to
It still says you lose your OS though.
https://forum.xda-developers.com/galaxy-s7/help/root-twrp-flashing-t3535545
AzzyC said:
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse
It's a brand-new phone so I don't really care about the OS.
Also I tried restoring my Nandroid backup, but the drive appears empty when I go to the "Restore" option in TWRP. Not sure if I need to fix the data thing first anyway, but surely it should show up?
EDIT: Now that I think about it wasn't there some requirement to clear a cache at some point? I vaguely remember that from the last time I rooted an S7.
I've tried formatting, and the readout says "formatting" and then "Done.", but there's still a progress bar and the title area still says "Formatting...".
EDIT 2: It's plugged in but the battery is still dropping, and it only started at 8%. So it might just die anyway.
I recently went back and forth between Oreo and a TWRP Nougat backup, and was flashing TWRP each time I went up to Oreo because I was installing it via Odin which was blowing away TWRP.
I must have had to factory reset and flash the dm-no verity.zip a few times each TWRP install before I got /system and /data to not return an error. I was probably doing something out of order, but it always seemed finnicky.
How does one do the factory reset?
TWRP still reckons it's formatting, even though it says "Done.", but the battery has just hit 0% so it won't last much longer anyway.
EDIT: Or not...battery still going strong at apparently 0%. But it's been formatting for over two hours now.
Advanced wipe with data, cache, and davlik cache checked should be enough
When was I supposed to do that step? It rings a bell but it isn't in the instructions I found.
The phone finally died, and now I cant' seem to get past the TWRP splash screen.
EDIT: Just plugging it in results in the TWRP splash screen. None of the buttons seem to do anything, so I can't get into download mode and reflash TWRP or anything...
Okay, so I left it on the charger for a couple of hours.
Pressing and holding the power button turns it off. A few seconds after plugging it in, I get the Galaxy splash screen followed by the TWRP splash screen, and then the latter just stays there. Forever.
Once I turn it off, I'm unable to turn it back on at all - standard boot, recovery or download. I pressed and held the buttons for a full minute, made no difference.
EDIT: Leaving it off the charger results in the screen turning off a few minutes later. Again, no amount of pushing the buttons will do anything.
EDIT 2: Got it into download mode by plugging it in and holding the buttons down while waiting for it to automatically boot. Next step? Flash a bootloader, or reflash TWRP, or both?
Tried reflashing TWRP, changes nothing. Also tried flashing a BL and CP from the last time I installed SupermanROM, but it failed in Odin. Not sure if they're just too old or something, I have no idea how that stuff works or how updated my software is or anything.
It's the same handset I had before, but it had to go back to Samsung for repair because the battery blew up, so they very kindly wiped everything, reset Knox, etc.
Hello all, posted this question in a Facebook group and was recommended to bring it here.
I've got a Samsung Galaxy A42 that recently ran a software update and wouldn't properly restart afterwards. It would load up with the normal "Welcome" screen from Verizon, but would freeze during this part of the loading, shut off, then try to restart itself again, and would continue this endlessly until it ran out of battery. The only thing I was able to do was access the safety mode menu, but I've tried everything save for factory resetting to no avail. I attempted downloading a SM-A426U_CCT_A426USQU4DVL2_fac.zip file and installing it from an SD card, but I receive an installation failed message from the safety menu when I do, stating "E: Failed to read 6 bytes of data at offset," "E: Failed to read footer," "E: Signature verification failed," and "E" error: 21." I've also tried recovery software, but none of them recognize my phone being plugged into the USB socket on my computer, nor does my computer recognize it in this state.
I've since gotten a new phone, but I've got some pictures, documents, videos, and other things on this phone that I'd like to get off the A42 if possible before turning it in to my Verizon store, so any suggestions or advice would be very much appreciated. Thanks for reading!
Clear system cache.
Try to boot into safe mode.
If that fails you're probably boned... a data recovery service may be able to help.
Always redundantly backup critical data especially before playing with the firmware. If you fail to backup critical data redundantly it's only a matter of time before you lose it.