I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
remus1101 said:
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
Click to expand...
Click to collapse
I've had problems with Aroma installers and TWRP abode the last 2.x.
Regarding system, try to format it via TWRP.
I know there are issues with Aroma installer. LineageOs does not require it so I think this is not the problem. Anyway I used TWRP 2.3 but I have the same problem. Installing process does not success.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Inviato dal mio SM-G900F utilizzando Tapatalk
remus1101 said:
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
Click to expand...
Click to collapse
TWRP getting a fail on mounting the system partition is strange. So I suggest you re-flash a stock samsung rom first and make sure it is working properly. Meaning it boots up ok and does not hang / freeze whatever during a good few minutes of use (maybe 15 min or so).
Then I would flash the img.tar of TWRP 3.0.2-0 from here. That is the version I use. It works just fine (with aroma too). Reboot to recovery and go from there.
Thanks for your response.
After a system wipe the mounting fail is gone.
I already flashed the stock ROM with Odin and it works fine. Then trying to install lineage from recovery (making the for wipes) I got the same results.
So I decided to flash a ported ROM (that uses Aroma installer) and installation was fully functional.
So I think this problem shows up only with LineageOs and also RR.
Is it possible that there are still some files from a previous installation of LO that cause a conflict and make the installation just not to continue?[emoji28]
Related
Hi,
Today I was trying to root my Nexus 10 (android 4.4.2), following this tutorial I had found earlier: au.ibtimes.com/articles/530367/20131216/root-android-4-2-kot49h-kitkat-install (add .htm, can't post urls yet).
Everything went fine until I tried to backup my system to the SD card with CWM. In CWM I got the message that several points in the filesystem could not be mounted. Not knowing how to proceed, I tried to reboot - since then I am stuck in a loop and would like to at least be able to boot into my stock rom again. Googling around for a while, I found several posts suggesting a factory reset might do the trick, however, since CWM is unable to mount anything, I can't perform such a reset. I tried wiping cache and all that, did not work.
Then I flashed TWRP (2.6.3.1 for nexus 10) using the fastboot flash recovery command. Again, I tried to perform a factory reset, which fails (the log just says
updating partition details...
Formatting Cache using make_ext4fs function.
So, I don't quite know what to do. Could anyone tell me how to best proceed? How can I get the Nexus 10 to boot again?
Thanks in advance!
EDIT: Ok, just fixed it by flashing the re-flashing the stock rom from the google page. So, how do I root the device now without running into the same troubles once again?
Wugfresh nexus root toolkit has always worked for me:
http://www.wugfresh.com/nrt/
tjupille said:
Wugfresh nexus root toolkit has always worked for me:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
+1 safe and easy
Thanks, that worked great!
Seems that same issue happened to me, but even after restoring Factory Image and re-flashing custom recovery I still have this problem:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried also on TWRP with no luck..any suggestions?
Inviato dal mio LG-D802 utilizzando Tapatalk
AleCai said:
Seems that same issue happened to me, but even after restoring Factory Image and re-flashing custom recovery I still have this problem:
Tried also on TWRP with no luck..any suggestions?
Inviato dal mio LG-D802 utilizzando Tapatalk
Click to expand...
Click to collapse
Hi,
I will suggest you to try formatting cache again, as it is the problem there. If it doesn't work, and you don't mind refashing the stock rom, then I'd like to ask you trying wiping every partition and install the after this.
I had a similar issue with Xoom, I needed to reboot several times in recovery and after some many times it finally mounted system (I had a bootloop) and I formatted it.
Good luck,
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
k1ng0fqu33n5 said:
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
Click to expand...
Click to collapse
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
TheSproker said:
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
Click to expand...
Click to collapse
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
k1ng0fqu33n5 said:
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
Click to expand...
Click to collapse
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
TheSproker said:
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
Click to expand...
Click to collapse
If i do a factory reset with TWRP, will it wipe any of the internal data? (pictures, messages etc.)
because the factory reset screen says that it's not included:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, i just tried a factory reset and that fails too. Unable to mount /data.
k1ng0fqu33n5 said:
Well, i just tried a factory reset and that fails too. Unable to mount /data.
Click to expand...
Click to collapse
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
EasyAndroidPro said:
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
Click to expand...
Click to collapse
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
k1ng0fqu33n5 said:
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
Click to expand...
Click to collapse
I see.. if that file did not fix the bootlooping then I'm afraid the only fix is like the previous poster said
Either flash stock again with Odin
Or format data in twrp
Ok, i somehow made it so the phone booted up and initialized. Now i got the problem that the google play store keeps crashing.
Edit: I also can't download my whatsapp backup data (says insufficient storage, which is not the case)
I also can't download files with the chrome browser (it says no sd-card found). If i use the stock samsung browser it works though.
Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Tre916 said:
Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Click to expand...
Click to collapse
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
Thanks, that worked. I appreciate your help!
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Tre916 said:
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Click to expand...
Click to collapse
in oreo you must decrypt data with 3.2.1-8 thats it ( if you are encrypted )
Since the last beta OnePlus (Pie 9 for OP5) have been released, I have continued blocking and rebooting the system (using custom rom principally, but also stock rom).
Recently, I was able to replicate the problem I have with all the new pie rom (I tried LineageOs, Dirti, Omni and even stock); in practice, by opening more applications (8/10 or more) and then turning off the screen, the system freeze (with blue LED on); at other times, reboot instantly.
Can someone help me understand what the problem may be? Eventually, do you have any suggestions?
I state that I format/wipe each partition; here the complete sequence I use to format and install custom roms (a real madness!):
*Format Data and Wipe all
Flash 5.1.3 Full
*Wipe Davilk and cache
Boot OS (to create Vendor Partition)
Bootloader - fastboot flash recovery recovery.img
*Wipe Davilk and cache
OpBeta 22 firmware + vendor
*Wipe Davilk and cache
OpBeta 23 firmware (o latest)
*Wipe System, Data, Davilk and cache
Bootloader - fastboot format userdata - fastboot erase cache - fastboot flash recovery recovery.img
*Wipe Davilk and cache
Flash custom rom
*Wipe Davilk and cache
Flash OpenGapps
*Wipe Davilk and cache
Flash NoVerity
Flash Magisk
*Wipe Davilk and cache
Boot OS (finally )
I also attach some tests done with GFBench (the hardware does not seem to have problems)
Thank you, very much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I could not understand what the problem was; anyway and for now, I solved installing the ROM stock without Magisk (among other things, I had tried different versions: 17 / 17.2 / 17.3 / 18 ... I have always had problems).
You made this way too complicated. Download the newest beta on to phone. Get total commander from play store, use it to enter(not extract) the firmware zip and delete the compatibility zip inside. Ensure magisk is on your device. Boot to twrp. Wipe EVERYTHING except internal. Now flash newest one beta, once it finishes flash magisk. It might fail. Just try again and it will work. Reboot. Now you are on pie with magisk and kept twrp. Also magisk is no verity. But you should flash decrypt before first boot if you are gonna go in and play with stuff.
Thanks, but I did that procedure just to figure out what the problem was. Magisk gave me several problems, in the meantime I try for a few days ... then I'll try.
Merry Christmas
mascian said:
Thanks, but I did that procedure just to figure out what the problem was. Magisk gave me several problems, in the meantime I try for a few days ... then I'll try.
Merry Christmas
Click to expand...
Click to collapse
OB23 with magisk 17.1 is working fine for me.
strongst said:
OB23 with magisk 17.1 is working fine for me.
Click to expand...
Click to collapse
LOL... that version is the only one I have not tried ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for your twrp to recognize your internal memory and the available memory that is in it since we all face this problem that presents twrp in internal storage.
Warning: This procedure will erase all the data of your device such as google accounts, messages, root, that is to say it will remain factory mode, so you will need to reconfigure the device, I add images of the steps so that it is as comprehensible as possible to understand.
When you install twrp and start it for the first time we will get the following information we just need to confirm the action Swipe to Allow Modifications.
So we visualize the following menu with the options offered by twrp, we will only focus on the option Wipe.
We choose the option Advanced Wipe.
Check the Data box and we choose the option Repair or Change File System
We choose the option Change File System
We choose the option EXT4
We choose the option Swipe to Change, When confirming the action your device will erase all your data stored in the internal storage
Twrp will recognize your internal storage and capacity
Warning: You must re-flash Drm-fix.zip. magisk.zip to be root on your device
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
omaison said:
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
Click to expand...
Click to collapse
No you have do it again after fresh installation
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
omaison said:
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
Click to expand...
Click to collapse
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
awadnisar said:
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
Click to expand...
Click to collapse
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
omaison said:
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
Click to expand...
Click to collapse
Means updating OmniROM is wiping data partition?
awadnisar said:
Means updating OmniROM is wiping data partition?
Click to expand...
Click to collapse
Not automatically. But it seems that I don't have the choice to format it manually to have the possibility to flash the new version of the ROM.
Otherwise TWRP generate an error with saying that the data partition is encrypted.
I will try again on the next week when the new version of the OmniIROM is released.
redundant