Hi I was wondering if someone could help me.
My dad's phone which is a S3 somehow soft bricked itself. It was on a stock rom before.
It turns on and then gets stuck on the Samsung Galaxy SIII screen.
I am able to boot into download mode as well as recovery.
I was able to flash a stock ODIN file UVUEMJC as well as the PIT file and everything went smoothly and it passed.
However, the same problem remains, it is still stuck on the Samsung Galaxy SIII screen when I boot it.
Also went into recovery and tried to wipe data, but it is unable to mount any partitions, e.g. can't mount cache, can't mount data, etc.
I was able to throw on TWRP and boot into that, and it gives me similar errors as the stock recovery. TWRP also says that my internal storage is 0 GB and I can't put any files onto the phone.
I am quite confused because if NAND was corrupted then I shouldn't I not be able to boot into recovery at all?
ADB is also working...can't push/pull anything though.
If someone could help me I would really appreciate it. Thanks.
So I flashed CWM cause I read on XDA someone said that formatting data through CWM works, now...it says there is no pit partition and there is a flash read failure whenever I try to flash a stock tar with odin w/ pit. Also tried flashing pit by itself, doesn't work.
Try installing cwm or twrp again, boot into recovery, mount sdcard0, connect to Windows machine, and try to format the partition using fat32.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
Hi.
I'm having problems with booting my phone. I unlocked my phone via Mi unlocker, put twrp on phone and via twrp Factory reset my phone.
Now it says '0 MB internal storage'
I tried to flash ROm via abd sideload, but it didnt work. It stuck on Mi logo. In twrp, when I want to make another factory reset, say 'Failed to mount /data (invalid argument)'
How can I make this phone work again?
Thanks..
Fortis10 said:
Hi.
I'm having problems with booting my phone. I unlocked my phone via Mi unlocker, put twrp on phone and via twrp Factory reset my phone.
Now it says '0 MB internal storage'
I tried to flash ROm via abd sideload, but it didnt work. It stuck on Mi logo. In twrp, when I want to make another factory reset, say 'Failed to mount /data (invalid argument)'
How can I make this phone work again?
Thanks..
Click to expand...
Click to collapse
You may be using twrp that's not compatible with oreo roms, I can't look for the link right now, just look around.
Try FORMAT DATA (not wipe) in TWRP, then reboot to recovery.
Fortis10 said:
Hi.
I'm having problems with booting my phone. I unlocked my phone via Mi unlocker, put twrp on phone and via twrp Factory reset my phone.
Now it says '0 MB internal storage'
I tried to flash ROm via abd sideload, but it didnt work. It stuck on Mi logo. In twrp, when I want to make another factory reset, say 'Failed to mount /data (invalid argument)'
How can I make this phone work again?
Thanks..
Click to expand...
Click to collapse
Use an oreo compatible twrp
https://androidfilehost.com/?fid=889964283620778448
If it still doesn't work, press wipe, Format data, and type yest to confirm. Then flash
Thanks guys!
Formating data and putting a new ROM worked!
Thanks again! Have a nice day.
I was on pixel experience rom and wanted to try out other pie based roms on my device. So i backed up all the partitions from twrp recovery and went on with flashing arrow os. But when i wanted to revert back to pixel experience by restoring the previously made backup, it showed that system partition mount was failed during the restore process. So i tried booting into twrp again but the device just bootloops. I tried entering recovery mode by using volume up and power combo. But twrp starts bootlooping after the logo appears on the screen. I also tried flashing redwolf twrp but it also fails to boot. Any help would be appreciated.
Enter fastboot, and boot twrp from adb then try again to flash it
Destinyg133 said:
Enter fastboot, and boot twrp from adb then try again to flash it
Click to expand...
Click to collapse
I already did that. But the result was the same.
Rahul Choudhury said:
I already did that. But the result was the same.
Click to expand...
Click to collapse
Try this:
Go into twrp, wipe, advance wipe, select system filesystem only and the option to repair/resize file system and repair it...
can u factory reset it? Using stock recovery
luck2ang said:
can u factory reset it? Using stock recovery
Click to expand...
Click to collapse
I flashed the fastboot rom. It is working fine now
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
i am in the exact situation please someone help me.i tried to reboot twrp with pc as well the same thing happens. please tell me how you did it
---------- Post added at 02:15 PM ---------- Previous post was at 02:02 PM ----------
YasuHamed said:
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
Click to expand...
Click to collapse
i cant find orange fox img file everytime i end up with zip file which can be flash in twrp. plz can you help me asap
---------- Post added at 02:27 PM ---------- Previous post was at 02:15 PM ----------
YasuHamed said:
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
Click to expand...
Click to collapse
i backed up my pixel experience rom in twrp then installed liquid remix. but i did not like it so i went into twrp wiped the phone, not inernal and all, but everything we wipe before installing rom, then i went into restore and restored my backup and reboot after that im stuck in bootloop and everytime i try to go into twrp the 1st twrp bootscreen shows up then goes back into bootloop. please help me i would be really greatful
Rahul Choudhury said:
I was on pixel experience rom and wanted to try out other pie based roms on my device. So i backed up all the partitions from twrp recovery and went on with flashing arrow os. But when i wanted to revert back to pixel experience by restoring the previously made backup, it showed that system partition mount was failed during the restore process. So i tried booting into twrp again but the device just bootloops. I tried entering recovery mode by using volume up and power combo. But twrp starts bootlooping after the logo appears on the screen. I also tried flashing redwolf twrp but it also fails to boot. Any help would be appreciated.
Click to expand...
Click to collapse
I experienced that too.. i think some ROM does something to vendor partition, example:
1. You backup data,system,boot etc...lets say u do that on "A" rom..
2. then u install "B" rom, and u like not satisfied on that..
3. Then u wipe everything and restore your "A" backup..
if you do that like what i said.. you will ended with bootloop or just stuck on mi screen..
I found a workaround ..
You just need to re-flash the "A" rom (clean install), then wipe everything again , and restore your backup..
? Sorry for my english btw
In my 16GB model, when I did a recovery through TWRP, I had a bootloop problem.
However, 'OrangeFox Recovery' does not cause this issue.
And, SD card with 'exFAT' format is recognized as normal.
I strongly recommend.
https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3900471