TLDR; After installing Remix OS for PC 3.0.207 on USB and booting in Resident mode, subsequent boots result in REMIXOSDATA partition corruption, and turning off 'Enable disk partition mount' under Experimental Features doesn't help.
Does anyone have a solution?
I realize this problem has been mentioned in several places like here, here and here, but the only solution proposed (turn off Enable disk partition mount under Experimental Features) doesn't work for me. Even if I turn it off on first boot, on subsequent boots the system still reports a USB corruption, and Windows shows the partition as Raw.
Ignoring the error message seems to be one way to live with it, but I feel like it's a shame to waste the partition disk space by leaving it unused.
I know Jide has stopped development on Remix OS for PC, but I am still keen to get Android running on my Windows 2-in-1 if possible.
Does anyone have any solutions?
Assuming you have installed to an ext4 partition, you might want to try 'sudo e2fsck -fv /dev/sdxy' in a Linux terminal. (change sdxy to your partition designation)
Thanks for the reply. I formatted my USB stick with Fat32. I've never tried formatting it in ext4 - I'll give it a go and report back. Do you think ext4 will avoid the whole corrupted partition problem altogether? Or does the 'sudo e2fsck -fv /dev/sdxy' command need to be done to fix the corrupted partition every boot?
Think I have misunderstood. Thought you installed from the USB to a partition on the PC. The command is to clean a dirty ext partition, often created when you force the shutdown, not every boot. I always use ext4, so I have no experience with running RemixOS on fat32.
Okay - no worries. Do you have Remix OS for PC installed on an ext4 partition on your PC? Does it work fine?
Yes I have RemixOS on one of my PC's partitions and it works well https://goo.gl/BJjB0X
Related
Sorry if i sound like a noob but can i take advantage of the ext3 partition on my SD using this version of CM?
I partitioned my SD using clockworkmod, which is why it's ext3.
only app i've tried is Link2SD but when i tell it there is an ext3 partition on the card it creates a script and asks me to reboot.
Once that's done and i access the app again it goes through the same motions and informs me that - "if im seeing this message then the partition is unable to be mounted during boot"
Appreciate any help
Here's a quick way to install Link2sd.
I preassume that your device is rooted and your sdcard data is backed up.I think,the mount script didn't work because of inappropriate attributes..Ok heres,how i installed Link2sd...
1.First of all download and install MiniTool Partition Wizard in your windows PC.
Connect your handset to the PC via USB.
2.Launch MiniTool Partition,you should see your SDcard mentioned in the list Under Disk 2 probably.
3.Right click your SDcard mentioned in the list, press "Move/Resize Partition"
4.In the Partition size,allocate bigger chunk of partition for primary partition.This is the partition your phone will access for general purpose.Say you allocate 7GB from your 8GB memory card.
Click OK.
5.Now Under disk 2. you will see and unpartitioned space of about 1GB.This partition will be used by link2sd.You may allocate your sdcard as you may wish.
6.Right click the upartitioned space to create a new partition under "Create As".If a warning popup asks for permission click YES.
7.Under New window Create As,choose "Primary".For File System type choose 'FAT32'.though you may choose among ext3 or ext4,either is supported by link2sd.NTFS is not supported by Link2sd or android OS.For partition size take whole unallocated space.Click on OK
8.Click Apply button<upper left corner in the screen>.
9.Restart your phone.
Again use your Link2sd app to create mount script.Now your app should work fine.
Don't forget to hit THANKS if i helped you.
I would not suggest you to create the Link2sd partition as a FAT32 one: this way when you will connect your phone to a PC through the USB cable Windows will mount all the 2 partitions automatically (with all negative consequences you can imagine); this issue will not happen on Linux, however; while with the Link2sd partition formatted as extX you will be able to use your linked apps while the phone is connected to your PC and the first partition is mounted, it doesn't matter if you are on Linux or Windows (tested )
Regarding your problem: try to tell the Link2sd script activator that your partition is an ext4 and see if it works.. I hope so, anyway let us know..
@brainvision
yeah thanks,extX would be better..bt i think windows doesn't mount two sdcard Fat32 partition at a time.i may be wrong in this term, bt sometime back,when i used to use rooted android 2.1,windows would mount only my 1st primary partition of sdcard..however under ubuntu..both partition would load bt without affecting the phone apps.
thinkfreedom said:
@brainvision
yeah thanks,extX would be better..bt i think windows doesn't mount two sdcard Fat32 partition at a time.i may be wrong in this term, bt sometime back,when i used to use rooted android 2.1,windows would mount only my 1st primary partition of sdcard..however under ubuntu..both partition would load bt without affecting the phone apps.
Click to expand...
Click to collapse
oh sorry I'm not a winZoZZ user since a lot of time!! I'm a slacker now!!
Regarding Linx OS: I set up my Slackware so that it doesn't auto mount external disk, so i can plug in the phone and activate the USB Mass storage without still mounting it: this way I can mount only the first partition; but in a auto-mount situation I fear that the the phone apps would be affected by USB Mass storage activation!
SOLVED! See 2nd Post
Hi,
Galaxy S II 16GB 2.5 Years old.
I friend came to me with a problem : Waze can't start because it complains no access to sdcard (internal, no external present)
A bit fiddling and I see /storage/sdcard0 is mounted as RO!
I remount as RW, and I can now start waze, but as soon as I use the phone further, the mount reverts to RO.
I try to format it via recovery (philz) but it fails deleted odd named files in DCIM/Camera/cache.
So I try to delete the files myself but it fails.
Next up, I mount usb storage in recovery, and run windows Checkdisk, it finishes while fixing some stuff, the format still doesn't work.
Eventually using Minitool I am able to format it. BUT, now, when I boot android, it says the internal storage is damange, and attempt to format it via Android fails always.
Still, when I boot into philz, and mount usb storage, i can browse it via my W7 PC, copy and delete files freely. So I guess something is not mounted or formatted correctly. I decide to reinstall stock rom with Odin + repartition.
So I take pit file from a thread that aims to increase /data at the expense of internal storage, and I find the stock pit there and use it.
Rom flashes fully, but sdcard still not working.
What I want to do is :
Boot into Recovery and use Android commands to properly mount/map this so the phone recognizes it.
I have linux knowledge, I know how to get around a linux shell and use VI and permissions etc. I also messed sometimes with fstab on a pc to set up mount points, so I am not a complete stranger. I am rooted and need help
Any help would be appreciated.
So, I searched the net for quite a few hours, and found this post :
http://forums.whirlpool.net.au/forum-replies.cfm?t=2147315&p=-1&#bottom
Which solved my problem
I registered on that forum to thank the dude!
This command solve my problem :
newfs_msdos /dev/block/vold/259:3
I knew it will work the moment I saw the 259:3 which I saw in logcat that android cannot format.
Good work finding a fix yourself Hopefully other people in the same situation will find it useful
Hello all,
I'm hoping someone can help me with this. Long story short, I've bricked my Prime. I was running TWRP recovery (AndroWook, so 2.6.something?) and KatKiss v30 when things went south... but unbricking is for another day.
I'm more interested in getting some data that didn't make it into my last backup off the /sdcard. I don't have access to the device itself (adb or fastboot, haven't tried APX yet), but I did managed to take an image of /dev/block/mmcblk0p8 via the dd command.
The problem is I can't mount it as a loop device in Linux. The problem that started all this was that KatKiss wouldn't boot... the output of "fdisk -l /dev/block/mmcblk0" suggested that its partition table was corrupted or gone.
Various suggestions on XDA and elsewhere (xmount, kpartx, etc.) haven't allowed me to mount this backup image... I'm wondering if the missing partition table isn't the issue.
[email protected]:~/prime_backup_microsdcard_32G_20151227$ sudo mount -t auto -o
loop tf201-mmcblk0p8.img /mnt
NTFS signature is missing.
Failed to mount '/dev/loop3': Invalid argument
The device '/dev/loop3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
So my thought is to try the following:
1. Create a virtual HD of >27.GB (the size of the backup image).
2. Create a partition of the exact size/dimensions as the backup I have, and ensure I'm able to mount it.
3. Restore the backup to this partition using dd.
4. Profit.
Does this make sense, and if so, what format is /dev/block/mmcblk0p8? Based on the steps to install KatKiss I would have guessed f2fs, but the mount error above makes me think otherwise.
Thanks in advance for your help.
ACP
Hi folks I'm trying to test the BETA of Remix OS but I'm stuck in "Format Data Partition... ANDROID"
My secure boot is deactivated and I have a 3.0 USB.
Also, it says Failed to find cpu0 device node
What can I do?
"Failed to find cpu0 device node" is not the reason for failed booting, I get this message too but can start without any issue.
Did you try to start in guest mode?
EDIT: from other thread: "boot with DEBUG=1 on the grub menu "
Hi
You may did some thing, try from download the .iso > Extract file > use provided .exe to make usb bootable > reboot pc > Boot from USB
This may help if you want to test Remix on VM
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Press thanks if help!
user0815f said:
"Failed to find cpu0 device node" is not the reason for failed booting, I get this message too but can start without any issue.
Did you try to start in guest mode?
EDIT: from other thread: "boot with DEBUG=1 on the grub menu "
Click to expand...
Click to collapse
Nothing, it, doesn't boot I tried DEBUG= 1 & 2
Possible solution...
Hi dude.
I think that you did what i did...
Probably you run disk dump from a RemixOs image to a secundary HDD. (I did this to a mistake, with sdb and sdc sux!!)
So I discovery that the Android X86 built in Remix OS check a kind of MBR sector in the HDD, so even if you format and create a new partition, the trash left by the oldest Remix OS disk dump still there...
Try to do this:
Check your start sector with fdisk /dev/sdX and list the partitions.
Erase the first sectors with this command:
sudo dd if=/dev/zero of=/dev/sdb bs=1048064 count=1 (Mine starts with 2048, so I erase the first 2047 sectors: 2047 * 512 = 1048064)
Of Course this broke my partition, which I had recover with testdisk
Cuervoazulado said:
Hi folks I'm trying to test the BETA of Remix OS but I'm stuck in "Format Data Partition... ANDROID"
My secure boot is deactivated and I have a 3.0 USB.
Also, it says Failed to find cpu0 device node
What can I do?
Click to expand...
Click to collapse
Solved with fat32 partition
I'm sure this thread is long since ignored now but I found myself having this problem today and the only fix was installing remix to a 25gb fat32 partition, worked like a charm, even though it gives you the option for ntfs and exfat, this ultimately fixed it
Back in the day I had my phone encrypted with data as a ext4 partition, I switched to using f2fs for a long time.
Now that I've tried to go back to using data as a ext4 partition while booting android asks for a invalid decryption password
using a really old pin number (I've had it encrypted several times since then using f2fs with different pin numbers) from the first
time I encrypted my partition while it was ext4.
Now when ever I wipe my data partition and try and use it as ext4 while booting android asks for a decryption pin which I can enter
but then complains that the filesystem it is trying to decrypt is corrupt.
I've tried doing a data format in twrp but it automatically formats it f2fs which doesn't solve the problem since
the problem only shows up while data is formated ext4.
I've tried every piece of wisdom I can find on the internet.
factory reset,
formatting all partitions,
dd front and back of userdata and then make_ext4 on userdata,
twrp format data,
recovery --wipe_data --set_encrypted_filesystem=off (from within twrp with the partition formated ext4),
format f2fs then boot up and reset and format ext4,
etc.
How do I give data the ultimate clean slate for being formatted ext4?
Or where is the remnant of the old encryption info stored from the first time I encrypted my phone?
I can format my data partition f2fs but frankly I was a little stunned when I saw the kind of overhead that filesystem has,
its space using overhead is way more then I want to have in a filesystem, or any filesystem I've ever seen.
Also is the problem not what I think it is?
Faced the same behaviour on my xt1524. Would be interesting to know if there is a solution for this
Is there a way to generate a new encryption from within the recovery?
Since it won't boot with data formatted as ext4.
Formatting it ext4 and then putting a new valid encryption on it?
From what I've found it, if the UI to unlock the partition on boot had a cancel button the system would boot as normal.
Unfortunately there is no cancel button on the unlock encrypted partition screen on our device. =/
Tried flashing a different recovery and using it wiping tools on data.
official twrp-3.0.2-0-surnia.img.
mkfs-f2fs -t 0 /dev/block/mmcblk0p44
process ended with ERROR:255
Unable to wipe Data.
Unable to format to remove encryption.
Also data wiping on TWRP is defaulting to trying to format data as F2FS which isn't even the default,
and while the partition has been switched to ext4.
I'd like to fastboot erase userdata and then fastboot format userdata.
But its giving me this error message.
fastboot format userdata
(bootloader) has-slot:userdata: not found
Formatting is not supported for file system with type 'raw'.
I've already done a lot of looking around on this issue, I'm normally not worried about this but
formatting internal system partitions that I don't understand how its different from a standard
desktop computers layout does worry me.
Should I be doing a full wipe and format everything to stock and then back to a custom rom?
God I wish this was a desktop computer right now, wipe the hard drive and reinstall the operating system,
there is something to be said for being simple and straight forward.
WTB cellular modem support in standard operating systems, and handheld devices that
can run standard operating systems.
I'd ditch this overcomplicated vendor locked sht so fast and never look back.
Following this guide to setup a new system encryption with rom in one go from the start with data as ext4 to see if I can bypass it this way.
But I'm getting a cannot find libraries error running cryptfs format command from adb shell or twrp terminal. b(>.<)d
http://android.stackexchange.com/questions/33398/cannot-factory-reset-after-encrypting
All this because someone thought it would be a great idea to take off the cancel button on data decryption
during boot.
This is why god invented beer and soaking you're brain in alcohol.
Damn been at this thing all day and still no luck.
Can I smoke the whole userdata partition with DD without bricking the phone?
In fact what can I effectively zero on a android phone without bricking it?
Am I miss reading this problem? Is the new inbuilt ext4 encryption (ext4 filesystem now has built in encryption support on newer kernels) support assumed to be on?
Never mind not as solved as I thought, But I just found another way to have my partition set to F2FS with letting me know. (^.^)
God this illustrates why formatting utilities that take shortcuts and 'ghetto erase' stuff are bad.
*Edited*
Default filesystem from the factory was F2FS (I have a bad memory : ) looks like it doesn't support putting data on Ext4.
Editing this post because I did a lot of post updates on what I was trouble shooting, but that might have
pissed people off because it does 'bump' the thread.
Sigh I'm throwing in the towel and formatting F2FS and moving on, F2FS is a one way door one which you never get back to ext4 from. > : (
Or ext4 formatting utilities suck balls and don't do their jobs.
Format all partitions to f2fs reboot to recovery again and format system and cache to ext4 now make a factory reset and reboot.