Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
leggoman said:
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
Click to expand...
Click to collapse
I can boot into twrp but i cant flash stock frimware with odin. It's giving FAIL error to me immidietly when im trying to do. And yes, OEM was open before
Now i flashed stock rom via odin, but when i install twrp again on my device it stucking at boot loop. Why?
Then i realized something that whatever i flash something via odin or something else, its stucking at bootloop
sdiown said:
Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Click to expand...
Click to collapse
Format all with ext4 (in twrp). Especially the system. Because all touchwiz cusrom can only run on ext4. After all normal, you can just format to f2fs for data and cache
Related
Why Do I keep having issues when Im trying to flash ROM updates. Once I boot into recovery the tablet always gives me errors that it cant mount cache, etc.. so the only way I can get the system to ever boot again is to flash back to stock and start from scratch.
Ive had this issue with multiple roms
yamaha_wins said:
Why Do I keep having issues when Im trying to flash ROM updates. Once I boot into recovery the tablet always gives me errors that it cant mount cache, etc.. so the only way I can get the system to ever boot again is to flash back to stock and start from scratch.
Ive had this issue with multiple roms
Click to expand...
Click to collapse
Which recovery are you using? TWRP, CWM? And what version of said recovery?
philz touch is what its called im pretty sure. Ive been updating the omni rom a few times now. this made about the 5 update before it happened again.
You could try TWRP. Its what I've used as long as I've owned my Nexus 10.
I've attached a flashable copy if you want to give it a shot.
thanks. I'll give it a try.
Hi!
I made a terrible mistake. I do not know how to solve it. I have been browsing dozens of pages and I am completely stuck.
I flashed a rom with odin and I ticked “Nand Erase All”. Yes, I know what I am, but don’t tell me. Well, after flashing the rom the phone is stuck on Samsung logo. And no matter what you do, it is always stuck on Samsung logo.
I have re-flashed several stock roms and in all possible ways (repartition, pit…), according to what I have read.
And I can’t boot into recovery, only into download. I have read that from recovery, a system format and wipes could solve this problem. But I can’t get into recovery. I have flashed different recoveries: Philz, CWM, TWRP. And no way, it is impossible to boot into recovery.
Please any help appreciated.
perevales said:
Hi!
I made a terrible mistake. I do not know how to solve it. I have been browsing dozens of pages and I am completely stuck.
I flashed a rom with odin and I ticked “Nand Erase All”. Yes, I know what I am, but don’t tell me. Well, after flashing the rom the phone is stuck on Samsung logo. And no matter what you do, it is always stuck on Samsung logo.
I have re-flashed several stock roms and in all possible ways (repartition, pit…), according to what I have read.
And I can’t boot into recovery, only into download. I have read that from recovery, a system format and wipes could solve this problem. But I can’t get into recovery. I have flashed different recoveries: Philz, CWM, TWRP. And no way, it is impossible to boot into recovery.
Please any help appreciated.
Click to expand...
Click to collapse
Take a look: HERE.
Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.
osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.
osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?
osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.
The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?
Hi everyone,
I hope that you all had/are having a lovely christmas. Unfortunately for my S4 christmas has been terrible. The phone has had low storage for a week now and was crashing as a result and I didn't have time to fix it. Yesterday the phone was running horribly and wasn't doing anything that I touched. So I rebooted which took way too long and when I did it again the phone now does not pass the galaxy s4 screen and also TWRP recovery will not pass its boot screen either.
I have attempted flashing stock recovery which said error mounting all partitions, afterwards a reboot allowed me to wipe cache thinking it would allow the phone to boot, but no change.
I am thinking to flash stock samsung rom through download mode since it is still functional so I can recover my data before moving to my new phone. Will this be a good idea considering that the Lineage OS rom is significantly smaller than the stock samsung rom or will it not worsen the situation?
Thanks for your help!
Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?
audit13 said:
Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?
Click to expand...
Click to collapse
Thank you for your response! I have tried flashing flashing both the same TWRP and different version which was in fact smaller. This saw no improvement in the condition and I still can not pass the TWRP boot screen.
What else do you suggest I try?
Thanks for your time!
Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.
audit13 said:
Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.
Click to expand...
Click to collapse
I am actually unable to flash anything without odin because I can't boot into my recovery which hangs on its twrp screen. Also if I have set my partitions to f2fs will this interfere with flashing the stock rom?
I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.
audit13 said:
I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.
Click to expand...
Click to collapse
Do you think it could possibly be a bootloader or kernel issue? Perhaps I could try flashing those first before a full factory firmware?
I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.
audit13 said:
I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.
Click to expand...
Click to collapse
So I took the plunge and installed the stock firmware now the phone boots and I'm greeted with a message asking to factory reset because encryption failed. I reinstalled TWRP and for some reason that still can't fully boot. I want to get it working so I can access the storage to remove the important files through either mtp or adb. There is some form of adb working whilst TWRP is booting but it can't access or see anything in the partitions or mount them even running as root.
Any ideas to get TWRP or any other recovery working on the phone? (The stock recovery booted just fine before I flashed TWRP)
Any help is much appreciated!
Kind Regards,
Crapping_Bricks
I think the stock Rom doesn't recognise the file system and thinks the encryption failed.
I'm not sure what else to suggest other than a factory reset since twrp doesn't allow pulling the data via adb or mounting the data partition.
So, even after I flash the stock rom with odin, it starts then at setup a bunch of "this app has stopped working" errors and cant access the system, I even tried flashing a bunch of custom roms(through TWRP since I can use odin no problem) and they all get stuck on the logo(waited for an hour before flashing a different one) Dont know what to do.
After flashing the stock rom and accesing the stock recovery i get a "Unable to mount /efs Invalid comand" error
Has anyone faced a similar problem
EDIT: after about 20 mins, the boot logo animation gets really slow (for any custom rom) but it never gets passed that
aaronus23 said:
So, even after I flash the stock rom with odin, it starts then at setup a bunch of "this app has stopped working" errors and cant access the system, I even tried flashing a bunch of custom roms(through TWRP since I can use odin no problem) and they all get stuck on the logo(waited for an hour before flashing a different one) Dont know what to do.
After flashing the stock rom and accesing the stock recovery i get a "Unable to mount /efs Invalid comand" error
Has anyone faced a similar problem
EDIT: after about 20 mins, the boot logo animation gets really slow (for any custom rom) but it never gets passed that
Click to expand...
Click to collapse
What is the model of your phone?
aaronus23 said:
So, even after I flash the stock rom with odin, it starts then at setup a bunch of "this app has stopped working" errors and cant access the system, I even tried flashing a bunch of custom roms(through TWRP since I can use odin no problem) and they all get stuck on the logo(waited for an hour before flashing a different one) Dont know what to do.
After flashing the stock rom and accesing the stock recovery i get a "Unable to mount /efs Invalid comand" error
Has anyone faced a similar problem
EDIT: after about 20 mins, the boot logo animation gets really slow (for any custom rom) but it never gets passed that
Click to expand...
Click to collapse
Flash official frimware through odin them open recovery (official recovery) wipe cache then wipe data / factory reset then restart the phone
tasnim_tamim said:
What is the model of your phone?
Click to expand...
Click to collapse
Hi!, its a SM-G531h
ealam said:
Flash official frimware through odin them open recovery (official recovery) wipe cache then wipe data / factory reset then restart the phone
Click to expand...
Click to collapse
Tried, still same results
aaronus23 said:
Hi!, its a SM-G531h
Click to expand...
Click to collapse
I think you did some changes to your device that made the efs partition corrupt. I think the only thing you can do is take your device to Samsung to get it fixed. I am sure that the efs partition is causing the issues.
tasnim_tamim said:
I think you did some changes to your device that made the efs partition corrupt. I think the only thing you can do is take your device to Samsung to get it fixed. I am sure that the efs partition is causing the issues.
Click to expand...
Click to collapse
yeah, I figured as much
Hey, look
Install the official firmware (stock firmware) via Odin, then turn off your phone
Then, go to the stock recovery and wipe cash and data
And finally, turn on youe phone
If it doesn't boot up (stuck at bootloader)
Remove your battery and try again
You're welcome