I started to encypted my phone and it failed, then i was getting system boot errors
I was running omega 36 Rom, i flashed using odin my stock Rom, recovery etc as phone was giving erros during oot. i already tried the format in TWRP that i was using with omega but still didnt work.
Now ive flashed with Samsung Rom using odin and it boots but i get system crashes constantly.
How do i fix this, i imagine i need to restore the phone and partitions back to stock, including probably another format.
Id be most grateful for help.
Related
So I was going to try the new Sense ROM for my I9000 and this is what happened:
I flashed the Speedmod kernel via ODIN, got into recovery - then flashed efs-backup.
After that I flashed the CM7 kernel via ODIN, did a system, cache and data format and installed the rom itself.
Now every time I turn on the phone, it gets into recovery... same happens if i press reboot system now in clockworkmod recovery
Is there still hope for me? All your help is appreciated!
this has happened to me too.
what happens is when you format system you actually format the OS on the phone. meaning that the only thing installed on the phone is the kernel.
resulting in a loop of recovery mode.
flash the rom again through recovery and see where that takes you.
if problem still persists. start whole process again
azzledazzle said:
this has happened to me too.
what happens is when you format system you actually format the OS on the phone. meaning that the only thing installed on the phone is the kernel.
resulting in a loop of recovery mode.
flash the rom again through recovery and see where that takes you.
if problem still persists. start whole process again
Click to expand...
Click to collapse
Yeah, but I did that before I flashed the ROM... Tried it again, still the same thing. (And I tried the whole thing from the beginning over and over again)
have you flashed back to froyo with 3 files and pit ?
what rom was you on before this happened, as it could be down to gingerbread bootloaders
I was on Froyo, Voodoo kernel
well just try 1 last time, make sure the FW comes in all 3 files, use 512 pit and check repartition in odin.
then take the necessary steps to get back to the sense ROM
ok, I am using a GT-19505, root with CF-Auto-root, using TWRP recovery
the problem is, when I put a rom in sd card and try to flash it, it will usually says fail (I am sure I get the right version for my device, and I tried many different rom), no matter how many times I re-download the rom, it will says it failed. Even if it success (i.e. omega 7.1 rom), it got stuck in the boot screen forever. I tried to use odin to flash a stock rom, but it also got stuck in boot screen for half an hour before I pull battery.
so far the only successful flashing is a cyanogenmod nightly on 7/14 (I tried other days one, but they all failed to flash). I tried to restore that rom after attempt to flash another rom (omega 7.1), but find out it was factory reset after boot up. I got into the recovery and see that my data partition has 1016154 MB of stuff through the backup option.
I have no idea what had happen, and how to solve it, can someone help?
TWRP can't mount /system. Phone is a SM-G900T 16GB
- Running the latest version of TWRP I tried:
- Wiping, repairing, and reformatting from TWRP, also tried formatting data. I get a unable to mount '/system' error message every time.
- Using Odin and Heimdall to reformat using a downloaded .pit, neither works. I ran Heimdall in Windows and Linux (ran as sudo and admin). I re-downloaded the .pit multiple times and tried a couple different sources.
- Installing CWM using Heimdall, and ADB. In ADB and Heimdall I still have TWRP and in Odin it removes the recovery completely.
- Fix permissions gives the unable to mount '/system' error message.
- Installing ROM from Heimdall and TWRM
- Mounting /system with or without MTP
How it happened:
I was running Cyanogenmod 11 with encryption and updated to 12. CM12 was running great, flashed GApps, still running good. I signed in to my Google account and downloaded IPcamera. While running IPcamera I got an email, the screen started going crazy flashing between the alert and IPcamera screen, I couldn't do anything so I pulled the battery. When I rebooted it was stuck in a boot loop. I booted into recovery, it asked for my encryption password as usual. The password didn't work. I tried several times. I rebooted and tried again, still nothing. I rebooted again and this time hit cancel when asked for the password. I wiped everything and got the can't mount /system error. I tried everything above, nothing works.
I can't download my .pit so there is more wrong than just the data partition.
Any ideas? I would love this thing to no longer be a really expensive paperweight. I really can't afford to replace this thing right now
Thanks for your help.
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
That worked!! I don't know why the stock recovery can fix it when TWRM couldn't. It worked though. Thanks a ton!!
Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either
egyptshun said:
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either
Click to expand...
Click to collapse
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,
Commodore 64 said:
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,
Click to expand...
Click to collapse
I have a G900W8, there's no lollipop version for me. What phone FW can I flash and retain phone signals etc.
Captian Double post Double post here.
I'm going to snap my phone in half, it's been over 13 hours of trying to fix this. How does no one else have this problem?
EDIT: YAAAAAAAAAAAAAAAAAAAASSSSS I FINALLY GOT IT TO WORK > I HAVE NO CLUE HOW <
Hello everyone,
A couple of days ago I've tried to switch a N910C from CM 13.1 to SimplRom. To my surprise, that resulted on bootloops on any possible scenario.
This was not different when flashing the latest stock for it, N910CXXU2DPG8_N910CZVV2DPI1_N910CXXU1DPE4_HOME.tar.md5, and even fully formatting/repartitioning the phone, using TRELTE_EUR_OPEN_SEA.pit, the right PIT file for it.
All flashing processes done by TWRP and Odin were successful.
I was able to use the phone again only after a restore of the nandroid backup of the CM 13.1 on TWRP.
So, I have a few questions, please:
1. Is there a possibility that, even doing all of this, some corrupted/incompatible settings were still present on the phone, avoiding any rom to boot?
2. Is possible that the EFS partition could be causing the bootloops? When I try to access some subfolder of /efs using Total Commander I get reboots on CM 13.1. The same happens when trying to access the Hardware tab of Samsung Phone Info app.
If this partition is corrupted, how repair it?
Solved using https://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132.
I hope that this info could help someone else.
my n910c currently stuck on samsung galaxy note 4 screen, is it a bootloop ? i tried to flash rom via ordin but it stop at cache. then i tried with kies it load very slow and stop at around 65%, i can't connect adb with twrp even got driver installed. i even flash stock with pit file.. i guess i tried everything but still no way to restore my phone ! can anyone help ?
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