So, I was about to give my phone to someone else so I flashed the Xtrasmooth ROM, and after boot I went to recovery to wipe the Internal Storage. Well, after doing that, the ROM took a crap and the Nav Bar and Status bar just disappeared. So, I decided to reflash the ROM, but no dice, same issue. So, I decided to flash the stock Lollipop image from Google, which flashed all fine but didn't boot. It got to the boot animation screen and sat there for an hour. So, I went back and flashed TWRP and tried to flash a new ROM but nothing is working. I can't access any partitions because of SELinux. Everything says "unable to mount /data" or "unable to mount /cache" and I feel like it's because of SELinux. It also says "Full SELinux support is present." What can I do? I really want to get this phone up and running again.
Try flashing a fresh recovery from fastboot, going to the repair partition section and reformatting everything to ext4 then try reinstalling your ROM/Kernel/GApps combo!
Beans
Related
Hey Guys,
i have a big problem with my new S4 (i9505).
Ive rooted the Stockrom with Odin and then i flashed the Recovery, thats works well.
After this step ive tried to flash CM10.1.
The first boot works well, ive setup my phone, take a reboot and then i have a bootloop.
Ive go to the Recovery and i see that /data is destroyed.
Ive formating /data, flashed CM10.1 again, first boot works, second boot, /data is destroyed.
Then i flashed the prerooted XXUBF8-Firmware, flash the recovery, all works well. Then i flashed a alternative Kernel, my /data will be destroyed again. I have to format it, and to reflash the stock firmware.
My last try was to flash the minit-Framework. After this flash, i cant boot in my system, becaus my /data was destroyed.
I dont thought that my device is destroyed, because the Stock prerooted F8-Firmware (with custom recovery) works 2 weeks long without any problems (ive rebootet many times in the 2 weeks).
What i doing wrong?
And sorry for my bad english
Best regards
Just to follow you : what do you mean by "destroyed" ? Formatted partition ?
If so, try to do the following : flash stock ROM, then the recovery (I personally use Philz Touch based on CWM), do a factory wipe and then install the rom you want.
Hey,
thanks for answer.
When i have a bootloop and go to the recovery and want reflash a rom, the installer say: cannot mount /data, unknow partition. and then the setup breaks up.
After a format of the /data-Partition via Recovery, i can reflash the rom, and boot onetime.
Ive go "your way" and i have the some problem. After one Reboot my /data is destroyed.
Mmmm...in the Philz Touch recovery (based on ClockWorkMod but with a lot of improvements), there is an option called "wipe data for new rom install" or something similar... give it a try !
I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later
androidnoobi said:
I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later
Click to expand...
Click to collapse
Good luck ! As you can normally flash stock rom, you don't seem to have hardware issues so don't worry
omg Oo
I dont believ it -.-
All the trouble are only fail from CWM and TWRP??
Now with Philz it works perfectly.
Ive installed Bobcat, reboot, flashed minit, reboot, flash another Kernel, reboot .. and it works Oo
Great )
Thanks
ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).
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 <
So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.
Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.
I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.