TechTablets › Forums › Cube Forums › Cube iWork10 Ultimate › Unable to boot Android, Win10 boots ok
- This topic has 4 replies, 4 voices, and was last updated 10 years ago by
Hans Sprungfeld.
-
AuthorPosts
-
July 30, 2016 at 1:24 pm #45093
Hello,
I have a weird problem with my USB Type-C iWork10 (i15TCL). Both Android and Windows worked fine, then I got a MicroSD Card, formatted it to Ext4 (on my PC), installed Ext2fsd, so that I could share the data on MicroSD between Windows & Android, did not mount Android partitions in Windows (so I don’t think I corrupted any files), but mounted the MicroSD card, wanted to restart to Android but am stuck as Android won’t boot (btw, does anyone of you have ext2fsd 0.6.9. correctly working? I get it to mount the partition and am able to use it, but the volume manager just won’t run – it shows in running processes, but doesn’t actually show up the main window and is impossible to kill from task manager).
What happens is this – when the tablet boots, I can choose between Windows and Android as usually, but only Windows boot. Android only gets to the point where the Cube logo turns blue and then hangs there and doesn’t react at all. I can get to Android recovery, tried factory reset but to no avail. I also tried to connect the tablet to my PC (running Arch Linux) but adb just doesn’t detect it – not in the “pre-recovery mode”, where I can select what I want to do (eg normal boot, crash mode, recovery, etc.) or the real recovery (where I can actually wipe /data and/or /cache). I don’t think it’s a problem with my setup as adb correctly detects my Android phone. In the pre-recovery mode, it seems that the system is set to fastboot and that secure boot is disabled (this is the first time I actually tinker somewhat deeper with an Android system so I’m not sure it’s relevant).
Does anyone have a clue as to what should I do? I was thinking maybe there could be a way mounting the Android partitions from windows and unpacking an image there or something like that?
August 1, 2016 at 8:17 pm #45283same exact problem here.. android is not booting.. and also i also have ext2 volume manager installed.. i didnt think it might be the broblem
August 5, 2016 at 5:50 am #45677i figured out how to boot android.. you need to unlock bootloader.. see laura thread of how tos
August 5, 2016 at 8:27 pm #45769If android stops booting unless the bootloader is unlocked then something you guys have done has modified the boot partition in some way. My guess is that ext2fsd mounts the boot partition and updates the mount time fields and stuff in its super block, causing the secure boot to fail.
August 5, 2016 at 10:10 pm #45791Yepp. Thats why I asked him about if he rooted. Then I was like, did the stupid Ext2fsd he installed under Windows change something on those partitions? Seriously? I guess mounting them on Windows means Ext2fsd does at least one write task to them, or he wrote something to them. Meaning the bootloader detected a change to the partition and didn’t boot Android because of security reasons.
-
AuthorPosts
- You must be logged in to reply to this topic.

