I have two nook tablets for my kids, model BNTV250. I boot them from SDcards made using the image cm_acclaim_10.1_21APR2013_HD_SDC_IMG provided at iamafanof.wordpress.com /2013/04/16/cm10-1-android-4-2-2-jellybean-sdcard-img-for-nook-tablet-0416/ . They work great for a while - in fact there are no problems until one runs out of power. After that happens, and I charge it fully, it will no longer boot - it stays stuck at the spinning cyanogenmod logo - I left it spinning for 2 days once and it still got no further. It will boot into recovery and I have tried wiping the cache and the dalvik cache. The only way I have been able to get it working again is to reburn the image which means they lose all of their apps and the progress of any that aren't in google. The experience is identical with both nooks.
I created a CentOS 7 virtual machine so I could mount and access all four partitions there. I can't find any log files to explain what's happening although there is a file called traces.txt under DATA/anr which I can paste in here if that would be helpful. I can see that the BOOT partition and the system partition are unchanged - at least all files and directories are dated 2013! Does anyone know of a file I can change or any other repair I can make to avoid having to reimage the card again? Any help greatly appreciated!
Maria
Hi XDA community, since I don't have enough power to land this on other forums I choose here.
First, this is my disclaimer:
Please try this at home at your own risk, the steps performed on this guide worked for me and may work for you.
Click to expand...
Click to collapse
But come on, this is XDA, you will figure it out without problems.:fingers-crossed:
Second, the good thing about this is you only need 3 ingredients:
Old tablet, The HP Stream 7 tablet SPECS
Precious Disk Space :victory:
Sweet Internet
W00t? no USB or Keyboard required? Yes, that's why it took me a while to glue the pieces together. Now, here we go:
I suggest to download PhoenixOS (November Release v1.1.2-226), because it worked for me immediately, I have an issue with RemixOS that I didn't try to fix it yet, I got stuck on the "Select Language" screen, but the steps may work for you.
Now, free disk space on your tablet, I did the upgrade to Windows 10 a while back and I had almost 1GB left on C, that's ridiculous because the drive has 20GB-ish, so, I google (yes, you need to do your homework too because I did the steps on the fly) how to recover space from the greedy Windows 10 OS, I removed a lot of useless info/cache/downloads/apps/etc and even compressed the Windows binaries (yes, you can do that). Concerned about Windows performance? be not, it works faster than ever. After the next steps this may seem useless but free space is free space, you'll need it later on life.
After all that dark magic, I was able to reclaim 10GB-ish, yeah!, but then realized I had 8GB more on the tablet "lost", this is the recovery partition for Windows 10, now, this is something that you may think of because you can get rid of all that info and reclaim what is yours, that partition is for you, but maybe you wont so this is one of these life choices. I did, I don't care about recovery stuff, most of my gadgets have custom ROMs or OSes. Used Minitool Partition Wizard Free and managed to reclaim the precious Disk Space.
Important thing here, some users Shrink the drive C to create a new partition, I didn't, used the 8GB partition instead.
We have Disk Space available, now, we prepare the operations table:
Disable Bitlocker on the drive you want to install the new OS.
Disable Secure Boot, power off the device and press Power+VolDown for a few seconds until you're on the BIOS.
Boot on Windows and install the Android OS flavor you want, I'll split the installation in two because for RemixOS is harder.
NOTE: Remember that grub doesn't support touch and both Android OSes grub have Windows as first OS to boot and kids, there is the key.
PhoenixOS
Download the OS
Extract it and run the installer
Select install to Hard Drive and install it on the Drive desired (I did that on E: which is the 8GB partition).
Restart and let the system do the job, you'll land on Windows again.
In Windows, as you read on the NOTE, we need to change grub.
Open Windows Powershell ISE in Admin mode (yeah yeah, yo can use whatever you want)
Then execute the command
Code:
mountvol B: /s
With this you'll be able to see the contents from the UEFI partition
Now, remember to select view all files, with WPISE open the grub.cfg file located on
Code:
B:\EFI\PhoenixOS\
Put the Windows entry below the PhoenixOS entry, change the grub timeout to 3 or whatever timeout you want, this change is for faster boot, save the file and you're ready to go.
Restart the system, press Power+VolDown -> F9, Select the PhoenixOS, let grub do the magic and you win
Notes about PhoenixOS
Phoenix OS installation, straight-forward on the 8GB partition
Needed to change Grub but friendlier than RemixOS
Keyboard behaves weird, you need to be accurate when using your fingers
When using browser and playing videos the tablet heats up hard
Rotation is wrong, I selected not to use rotation so I can use the UI without problems
Is fast, Wireless work
Something I saw one time is it got stuck when showing my user recently booted, restarted the device and then it worked again.
Video after the break.
Veredict: It works for me and can play with Android in a tablet without the need to buy another.
RemixOS
It supposed to have more support for things but looks like PhoenixOS has more . Not going to start a war here, I always try to find what suits best for me .
RemixOS is a pain on this tablet with the newest November 2016 version, I need to play more and harder.
You do almost the same as PhoenixOS, the installer is easy as well but it shows you an installation issue the first time, you need to restart the device and try the installation again. After that it was a game of try and fail but I sorted out the pieces.
Restart and you'll be on Windows again, well, let the system land on Windows and modify grub, kind of same as PhoenixOS:
Open Windows Powershell ISE in Admin mode
Then execute the command
Code:
mountvol B: /s
With this you'll be able to see the contents from the UEFI partition
Now, with WPISE open the grub.cfg file located on
Code:
B:\boot\grub\
Remember to select view all files
Put the Windows entry below the RemixOS entries, save the file, change the timeout and you're ready to go.
For RemixOS you also need to change the timeout for the theme.cfg file on
Code:
B:\EFI\RemixOS\
Restart the system, press Power+VolDown -> F9, Select the OS Bootloader, let grub do the magic (after some errors, just let it be) and you win (see, no hands mom!), well, sort of because it freezes :silly:.
I'll try to do more tests with RemixOS and see what happens.
Is this guide enough for you, not? blame the Internet or leave your comments.
Enjoy.
Thanks for the info.
I'm not getting any sound with PhoenixOS. WiFi is OK but sound & Bluetooth is not functional. Any suggestions ?
I've experimented with RemixOS as well...... sound works but it's very laggy and touch-screen / rotation is unresponsive. PhoenixOS is very stable and far far better but no sound :crying:
android x86 nougat on hp stream 7
Try this ISO of Android Nougat on the Stream 7, Wifi Bluetooth & Audio work. touchscreen is a little sensitive
Search youtube for HP Stream 7 for a link to the ISO.
I'm not aloud to post links on hear
mlckchip said:
Try this ISO of Android Nougat on the Stream 7, Wifi Bluetooth & Audio work. touchscreen is a little sensitive
Search youtube for HP Stream 7 for a link to the ISO.
I'm not aloud to post links on hear
Click to expand...
Click to collapse
Could you please explain the installation instructions?
Any news? I tried newest phoenix, but it´s way too heavy for it. Runs very slow. The older lollipop works better. The touchscreen is more a problem, it´s like a tablet from hell, very bad sensitivity.
The "Trekstor Surftab Xintron i 7.0" should be the same hardware and has android, so there could be a way to install this or at least use the touchscreen drive in phoenix. But I´m afraid of bricking it.
Hello.
On a Chuwi Hi12 dualboot tablet, loaded on Windows 10, I reduced the partition "Windows", by telling me that it was the first stage to pass place of Windows (that I use little) to Android (which misses it).
I used EASUS. The manipulation was made well, in the sense that Windows always works and when I have well a free place on the memory.
Other partitions, EXT3, are always there, and nothing strange under Windows. But I cannot any more booter on Android: logo Chuwi one moment then black screen.
I can switch off and reload Windows.
It seems that the table of the partitions or one of the partitions which interest Android was modified.
Attempt to reinstall Android. Using ROM of Hackerjac (http: // forum.chuwi.com / forum.php typeid%26typeid%3D6). With Phone flash Tool Intel with flash-no-erase.json, config Recover).
Many failures (fragility driver USB? Reinstalled). At the end and at best: failure repeated on the installation of the bootloader, with message on the tablet " Failed to get partition bootloader2: Not found ". Rather clear but disappointing: the partition is not recreated?
Thus I am there to try to understand what is made by flash, and how have a gpt.bin which corresponds to a chosen distribution (editor of gpt.bin).
Thank you for your help.
Hello, the other day I installed RemixOS and it worked perfectly. On boot up, it gave Windows Boot Manager popped up and gave me an option to choose RemixOS and everything launches smoothly. On the next day, it stopped giving me the menu to choose RemixOS, but instead just launches straight into Windows 10. Uninstalled and reinstalled, nothing works.
Just some info before I installed the OS:
I created a new partition on disk 1 with about 28gb. All the partition settings should have been set up correctly, so I installed Remix onto that partition. Note that I only have one disk.
Also tried to access Boot Manager manually by pressing ESC upon boot and did eventually find RemixOS, but when I launch it, it couldn't read my write/read speed. It couldn't find this "mkf4" (I think it was that) file and just freezes on screen with Android-x86 and flashing A N D R O I D at the bottom. Does anyone know a solution for me to fix this and make Remix work again? Thank you!!
PS: I'm not a very tech-savvy guy, so please use layman's terms for me to understand!!
Anyone? T_T
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
xxXPANDER said:
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
Click to expand...
Click to collapse
GRUB bootloader installed?
Complete guide here.
jwoegerbauer said:
GRUB bootloader installed?
I saw the link. Followed the steps. Stuck after step 5 in the link and cant proceed to step 6. I dont think grub is the issue here?
Click to expand...
Click to collapse
I'm having the same/similar problem (no choice to install is presented)
Context: I use a USB stick with refind to find and boot an android-x86_64-9.0-r2.iso that I have already imaged onto /dev/sda8 (imaged using the linux dd command).
When I use refind and select to boot /dev/sda8, android-x86 boots to the console shell prompt, and then seconds later starts a live run GUI screen. The boot process never stops to present me with a choice of install versus live run, as it should do. And that is my problem.
I'm looking for a workaround. I can switch between console and live GUI using Ctrl-Alt-F1/F7, so I can do command line stuff as root . Anything I can do to kill the live GUI and start the disk installer mode from the console? Name of installer program? Name of GUI is not Xorg or X or anything usual, it seems .
PS: If I knew which distro is underlying android-x86_64-9.0-r2.iso , maybe I could look up some keyboard salute to select installer mode during the boot?
one workaround found
@xxXPANDER, the following may be of interest to you, and @jwoegerbauer, too:
I managed to get the installer going by booting the iso from refind with one trick applied. Details: From refind gui boot, select the iso partition, and then use the hit-key-F2-twice method to edit the refind command line and append the phrase INSTALL=1 and then hit ENTER to boot.
At that point the installer mode came up, rather than the android live GUI mode, and I selected to install according to my plan, onto the empty partition /dev/sda9 with ext4.
I had a surprise that the installer put the data section of the installation on sda6:/android-9.0-r2/data/ (about 180MB), but the rest of the installation on /dev/sda9. Not sure how the installer figured out that I had tried before to do an alien-rpm-based install onto an existing ub18 on sda6. The image I booted was on sda8, and the destination I set was sda9. But still /data ended up on sda6:/android-9.0-r2/data/ . Weird.
Upshot: you need to shoehorn INSTALL=1 into the boot recipe, one way or another. I think the whole problem we're having should be considered a bug, though. It is almost as if the iso checks whether it is being booted from grub2 or not, and if not, jumps straight into live mode. This certainly caused me at least two full days worth of trouble so far, and I see no documentation of this strange behavior. At the very minimum there ought to be some documented keyboard salute that prevents this behavior during a standalone (non-grub2) boot. Maybe someone will disagree, but AT LEAST there should be prominent documentation, say on page https://www.android-x86.org/installhowto.html