Related
Android 2.0 (Eclair) for CDMA Diamond (DIAM500)
Instructions
Put the files from my zip file (zImage, modules, startup.txt) in the root of your Internal Storage
From this xda post, download the latest XDANDROID build.
From the XDANDROID 7z file, extract system.sqsh, haret.exe, initrd.gz, calibration, conf/, media/, and (optionally) AndroidApps/ into the root of your Internal Storage
From stinebd's rootfs autobuild site, download the latest rootfs, rename it to rootfs.img, and put it in the root of your Internal Storage.
If you are updating from an earlier version of Android or just want to clear your settings, you can delete data.img from the root of Internal Storage.
Run haret.exe and boot
Notes
Touchscreen calibration values are stored in the ts-calibration file in the root of Internal Storage. To re-calibrate, delete the file and restart.
The "end call" button takes the phone in and out of sleep.
Android's "Menu" button is mapped to the top-left/Home button. The 5-way pad and the scroll ring both work.
Android's "Home" button is mapped to the power button on top of the phone.
Wi-Fi is working, although Linux sometimes crashes when WiFi is turned off.
If you want to try Android 1.6: From this Android build, extract haret.exe, initrd.gz, system.sqsh, calibration, calibration_diamond, and the AndroidApps/, conf/ and media/ directories into the root of your Internal Storage.
ChangeLog
3-23-2010:
Touchscreen double-tap issue should be gone, big thanks to eval- and especially bzo
HTC wired headset and 3.5mm headphones both work
3-8-2010:
Hardware 3D is re-enabled (accidentally disabled it)
3-6-2010 Update:
Bluetooth now works, big thanks to bzo
Touchscreen should be improved
Power-off now resets the phone instead of crashing
2-25-2010 Update:
When WiFi is turned off the phone shouldn't crash
2-19-2010 Update:
Power collapse now works, so power consumption should be much lower when the screen is turned off.
WiFi should work, as long as you use a new rootfs from stinebd's autobuild site. If you tried to use WiFi in the last ~2 weeks and it failed, WiFi still may not work with this new rootfs and kernel. See this post for solutions.
2-17-2010 Update:
Microphone works without having to make a call in WinMo
WiFi still isn't working, but I'll post a patched rootfs soon to fix it
2-10-2010 Update:
Hardware 3D acceleration is working under Eclair
Brought in makkonen's fixes for battery status--they're rough, but better than being stuck at 5% all the time
WiFi is not working at the moment, but I'll lean on the XDANDROID guys to get my fix in.
2-3-2010 Update:
Linux is now using much more of the phone's memory: 180MB vs. 103MB, thanks to some patches from the Hero and Droid Eris kernel source.
Touchscreen calibration is now supported with the Feb. 2 XDANDROID build, thanks to makkonen and phh.
1-27-2010 Update:
Stability should be much improved
A new touchscreen driver is included that is a big improvement over the old one, thanks to makkonen and phh. A calibration utility is coming soon. Until then, calibration is stored at the bottom of conf/eclair.user.conf, and you can put your WinMo calibration in there with this guide.
The USB product ID has been changed in the hope that ADB will work on Windows. Try it out and post back if it works.
1-22-2010 Update:
The power button (on top of the phone) is now mapped to Home, and holding it down will show apps running in the background
Sound, data, and WiFi should all be working
1-11-2010 Update:
Tested and working with Eclair
Deep sleep should be working better (use less power)
12-26-2009 Update:
Kernel improvements:
The speaker and earpiece now work (but not the microphone)
Screen backlight control works
Rootfs improvements:
Thanks to makkonen's RIL fix, cell data works in Android without having to end the connection in WinMo first
I made a change to /init that might help mjb94, hackman238 and others that have partitioned internal storage. If you were getting a "cannot mount" error on boot, let me know if this fixes it.
12-16-2009 Post
We do have a Google wave for Android--right now it's a cross between a wiki-status-report and chat room. I'm not sure how to give a link to a wave, but it's open to everyone and called "Android on HTC Windows Mobile Phones (Diamond, Raphael, Blackstone, Rhodium, Topaz)". If anyone wants a wave invite, PM me and I have a few to give out.
Enjoy Android, and if you need help or have questions, PM me or post here
Donations are greatly appreciated , or help finding an engineering job in San Diego!
thanks mr. pippy for all your work. my wife is happy that once the microphone works i wont want to buy a new phone!
wow
you are definately making progress on the diamonds android
Is there any chance of the mic working anytime soon? I know this isn't an fast paced process but I'm just so sick of wm.
Can someone invite me to Google Wave please?
my gmail account is mike.cgy
bdusmc said:
Can someone invite me to Google Wave please?
my gmail account is mike.cgy
Click to expand...
Click to collapse
I just sent you one.
Awesome - I got it... Thanks a lot!
Wow, you're getting a lot done in a short period of time, Thanks!
Will donate as soon as I can!
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
For the latest version, it will boot for me, but as soon as I have a 3g connection it seems to reboot any time I touch anything.
Boots up fine
Latest build boots up and seems to run fine for several hours but after playing with it, it seems to get more and more unstable. I went 10 hours with it plugged in sleeping and then unplugged it and used it moderately for about 3 hours before it crashed. Now it's crashed 3 times within minutes of each other. Good stuff though, can't wait until it's stable enough to use full time. Diamond has plenty of nuts to run it pretty good. Sure would be nice to have a dual boot phone. No reason to upgrade and get the best of both worlds...
giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.
giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
rothgar said:
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.
Click to expand...
Click to collapse
Sorry, my kernels are only tested on DIAM500. The RAPH500 mtype (set in startup.txt) is 2182, you should have better luck with that. Also, this thread is for RAPH800 but there may be some RAPH500 people there.
mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting
mjb94 said:
mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting
Click to expand...
Click to collapse
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.
Willis111 said:
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.
Click to expand...
Click to collapse
I simply in disk utility clicked on restore and erased the disk restoring with ms-dos fat
is there another way to do this. i have access to linux and osx not windows
it only shows i have one partition so idk!
no dice. heres what i have done
ok i restore the disk in to ms-dos fat
no dice
i repartiton with a scheme of one partition
no dice
i change the partiton table no dice
i tried lavaders thing but i couldn't get the keyboard to come up
there is a new android version called eclair 2.0 here http://forum.xda-developers.com/showthread.php?t=601751 .
i also formatted from the phone
Possible fix for microphone
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.
MrPippy said:
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.
Click to expand...
Click to collapse
Yep, confirmed for me. Made a phone call with android and could talk just fine. Probably can just call voice mail with win mobile and launch HaRET. Trying that right now.
By now some of you are anticipating in getting one & have researched every known articles. But while reading all these wonderful articles, I kept asking myself, "how about dev'n these bad boys. Is it easy to root, load a new ROM & recover from a brick?"
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from an unbootable device.
Here's the basics on recovering from an unbootable device by booting into fastboot & re-installing
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
You can go into the Dev forum to learn how to root, install recovery & location of the Google N7 image.
I left out the screen, storage, & etc... because you can find it here or on the net.
EDIT:
will include the full instructions since I assume you had Android SDK installed on your system
1. Download & unrar Google's Android SDK
http://developer.android.com/sdk/index.html
2. use the SDK to download platform-tools
2. download Googles N7 image & unrar in the platform-tools folder
https://developers.google.com/android/nexus/images#nakasi
3. make sure N7 is in bootloader (hit power & hit vol down when you see the google logo)
4. plug to your Mac or linux box
5. open up terminal & CD into the folder that has the N7 image (.../.../platform-tools/N7 folder)
6. type ./flash-all.sh or sudo ./flash-all.sh
7. you are now back to stock
That concludes it, I'm just your typical geek, flash happy gadget dude.
Apps used in testing:
stock text/PDF reader, video & music player
MX Player w/ ARM7 neon plugin
Stick It player with plugin
Quick Office Pro
Root Explorer
Hardware used:
I/O Nexus 7
Belkin 2 Port USB powered hub
generic OTG
generic usb sdcard adapter
32gb microSD
Files used:
text & pdf file
MP3
MKV anime
AVI XVID
Formatting sdcard via
formatted FAT32 & NTFS using Win 7 pc
formatted EXT3 & EXT4 using G-Parted from linux (VMWare WS running Ubuntu)
1st testing:
FAT32 & NTFS: I copied the files from the PC to the sdcard.
EXT3 & EXT 4: I copied the files from linux (VMWare WS running Ubuntu) to the sdcard.
results from 1st testing:
FAT32 & NTFS: Unable to read PDF's & play the video files
EXT3 & EXT 4: Unable to read PDF's & play video files
2nd testing:
I copied the files from the PC to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards
results from 2nd testing:
FAT32: Unable to play music, video files & read PDF
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
3rd testing:
I used AirDroid to copy files from Linux to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards.
results from 3rd testing:
FAT32: Did not test
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
what about windows?
RMXO said:
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from a brick device.
Here's the basics on recovering from a brick device.
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
Click to expand...
Click to collapse
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
rcrd-pt said:
what about windows?
Click to expand...
Click to collapse
My advice for folks on Windows that don't have a Mac or linux box is to download & install Sun's VirtualBox & install Ubuntu. It's very easy to do & doesn't take up much space.
revmra said:
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
Click to expand...
Click to collapse
No need to apologize, I was wondering how long before I took me to brick & learn how to get it back to stock. I'm now more comfortable in messing around with the device since I know I can restore it back to stock within 5-10mins.
RMXO said:
reserved for my power hub & MHL testing later
Click to expand...
Click to collapse
yeah, that really begs the question of whether I can plug OTG into a powered usb hub to use peripherals and a mass storage device AND charge at the same time.
Will be interesting to see:highfive:.
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Hemidroids said:
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Click to expand...
Click to collapse
That is correct, I created a folder & moved files from the tablet using Root Explorer
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
doctahjeph said:
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
Click to expand...
Click to collapse
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
RMXO said:
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
Click to expand...
Click to collapse
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
aaronpoweruser said:
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
RMXO said:
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
Click to expand...
Click to collapse
Did the UI change when you put it to 160 or did it stay in the phone UI?
doctahjeph said:
Did the UI change when you put it to 160 or did it stay in the phone UI?
Click to expand...
Click to collapse
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
RMXO said:
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
Click to expand...
Click to collapse
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
doctahjeph said:
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
Click to expand...
Click to collapse
I'm completely redoing all my testing with hopefully less confusing test methods. Once, I get done with that, I will re-do everything in Tablet UI mode.
Thank you for going to such great depths with this testing RMXO - it's reassuring for all of us that don't yet have our hands on our ordered N7's that there is hope It's greatly appreciated.
Revised my testing methods & posted results in thread #2
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
danny8 said:
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
Click to expand...
Click to collapse
Yo're welcome & I honestly can't answer the downside of rooting because I love tinker & the only way to do that is to root. Actually, by rooting, you open yourself to bricking your device. That is the extreme case if you don't know what you are doing & can't follow directions properly. I've listed a way to recover from a bricked N7 device.
There is an app called "Voodoo OTA Rootkeeper" that allows you to unroot & go back to root when needed.
My tablet is unlocked, rooted & able to play movies from the Google Play Store.
Features
Code:
Enable loadable module support
- Module unloading
Forced module unloading
Multimedia Support
- Digital TV support
- DVB Network support
- Remote controller decoders
LIRC + all protocols
- Remote Controller devices
Windows Mediacenter IR
Loopback driver
Media USB adapters
- Dibcom DiB0700
File systems
- CD-ROM/DVD Filesystems
ISO9660 / UDF
- DOS/FAT/NT Filesystems
NTFS+write support
- Network File Systems
NFS v2/v3
CIFS + SMB2 + client caching
This is my first attempt at building an Android Kernel, last time I did it was for Ubuntu Gutsy, so please bear with me.
This is a stock AOSP kernel for Fugu, 3.10.20. All I did for now was a make menuconfig enabling some features I miss. I'm testing what I enabled, so far I've been able to mount an smb share from both windows 7 and my D-Link DNS-320 NAS running alt-f. Tried to mount nfs but it failed against my NAS. Haven't tested it yet with an NTFS formatted drive, will report back once I do. NFS mounting worked after I disabled SELinux enforcing, will try to figure what's needed to get it going without turning it off. I've been able to move apps to external storage using bind mounts over an ext2 formatted micro SD card, and on an NTFS formatted HD. This didn't work on a FAT formatted card, I'm mostly sure it's because of lack of extended attributes needed by SELinux.
All the features enabled on the kernel are built-in for now, but module loading is enabled in case you want to compile some.
I have a powered OTG USB hub, connected an old Microsoft MCE receiver and got the direction keys on the remote working, no other key worked, so I guess some kind of keymap is needed, will dig into it soon.
Also, I've built with support for my ISDB-T receiver (digital TV standard used in Japan and most of South America). It's seen by the kernel but fails to load firmware. My receiver is a Mygica S870, don't know how involved will be the process to get it working, it's not my main focus as I use it with a Raspberry Pi running tvheadend, but would be nice to get OTA tv on the nexus player with just an USB tuner. If you'd like me to add your tuner, let me know the HW / USB:ID.
For now, the kernel is provided as a zipped image, download, extract and test before flashing:
Code:
adb reboot bootloader
fastboot boot boot.kernelfox.img
If you decide to install it, you can do it with:
Code:
adb reboot bootloader
fastboot flash boot boot.kernelfox.img
or you can use TWRP to flash it. Remember, this is not an update zip, so you should copy the extracted .img file to your player (not the zip), and select Images... on TWRP to see it. There's a kernel.config file in the zip, it's what I used to build this one, if you want to try compiling it yourself, copy it as x86_64/.config on your git root.
I've been running it for the last few hours, but as my gf is using the player, I'm limited to testing from a remote adb. I'll be trying to build support for some type of unionfs for apps2sd, I'm evaluating the available options and would love suggestions about this, again, last time this was an issue for me was on the Motorola Milestone (ie Droid) days.
[Reserved]Really?
Since this is AOSP based, I'm assuming it won't work with CM?
Ambious said:
Since this is AOSP based, I'm assuming it won't work with CM?
Click to expand...
Click to collapse
I'm almost sure it shouldn't, but you can do a one time boot without flashing it, so I'd love to hear if it does. My player gets a lot of use here so I can't mess that much with it right now. I'm targeting rooted stock, as I really like it and would love it with just some tweaks.
@FaberfoX is this for 5.1.1
Toneman07 said:
@FaberfoX is this for 5.1.1
Click to expand...
Click to collapse
Yes, haven't had time to dig more into it, but I've been running it on LMY47V since I built it with no issues.
Thanks man going to flash it this week
We're back with an OTA update for 1GB and 2GB Remix Minis. Also, please know that if you are experiencing any type of streaming video issues, we've identified the problem, worked on a fix and are currently testing it now. If it passes, it'll be on the next update.
___________________________________________________
Remix OS on Remix Mini (1GB & 2GB) update version: 2.0.626
Release date: November 4, 2016
Release notes:
Updated Remix OS TV mode’s UI to the latest version.
IMPORTANT NOTE: For users who have NOT updated since version 2.0.307, all updates between 2.0.307 and 2.0.626 have been included. This is a critical update for the functions and usability of your Remix Mini. We strongly suggest you update to this version. This also means that this update may take a few minutes longer than regular updates.
__________________________________________________
Please continue to give us feedback here: http://support.jide.com/hc/en-us/requests/new
Thanks!
Do you have it as non ROM but as a firmware file to overwrite all partitions and have a fresh version of 2.0.626?
RemixOS_Jason said:
We're back with an OTA update for 1GB and 2GB Remix Minis. Also, please know that if you are experiencing any type of streaming video issues, we've identified the problem, worked on a fix and are currently testing it now. If it passes, it'll be on the next update.
___________________________________________________
Remix OS on Remix Mini (1GB & 2GB) update version: 2.0.626
Release date: November 4, 2016
Release notes:
Updated Remix OS TV mode’s UI to the latest version.
IMPORTANT NOTE: For users who have NOT updated since version 2.0.307, all updates between 2.0.307 and 2.0.626 have been included. This is a critical update for the functions and usability of your Remix Mini. We strongly suggest you update to this version. This also means that this update may take a few minutes longer than regular updates.
__________________________________________________
Please continue to give us feedback here: http://support.jide.com/hc/en-us/requests/new
Thanks!
Click to expand...
Click to collapse
How to exit TV Mode without restarting?
RemixOS_Jason said:
We're back with an OTA update for 1GB and 2GB Remix Minis. Also, please know that if you are experiencing any type of streaming video issues, we've identified the problem, worked on a fix and are currently testing it now. If it passes, it'll be on the next update.
___________________________________________________
Remix OS on Remix Mini (1GB & 2GB) update version: 2.0.626
Release date: November 4, 2016
Release notes:
Updated Remix OS TV mode’s UI to the latest version.
_______________________________________________
Click to expand...
Click to collapse
Can't find a way to close Tv Mode and back to normal desktop. How?
dinh_duy said:
Can't find a way to close Tv Mode and back to normal desktop. How?
Click to expand...
Click to collapse
press circle next to start button
kesmtk said:
press circle next to start button
Click to expand...
Click to collapse
Thanks. Gonna try it later.
Do you mean, you'd rather have a fresh copy of Remix OS on version 2.0.626 with none of your previous saved data and apps? Did you have your previous version rooted? I believe if you were just looking for a fresh start with the latest version of Remix OS, you can reboot your Mini, and then press F2 when prompted, and then do a factory reset. You may need to go through some updates, but I'm told you should restart in 2.0.626.
I hope this helps.
kesmtk said:
Do you have it as non ROM but as a firmware file to overwrite all partitions and have a fresh version of 2.0.626?
Click to expand...
Click to collapse
RM1C was rooted but unrooted cannot apply OTA
My device is RM1C. I Wanted to root on 2.0.512 version. but it autoupdated to some unstable version 2.0.622 with crashes after exiting fullscreen app. (I noticed there appeared an error messages on some missing file when connected via uart port. this is the message:
init: unknown magic init: unknown magic init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
) but 2.0.512 was most stable version for me no errors on the uart also.
I rooted 2.0.622 version and allowed an app that I bought "gamecontroller2touch pro" to grant superuser permissions. It works as mapping xbox360 controller buttons to touch games like a charm, where a jide keymap does not support xbox360 it only works for keyboard input.
Then I saw a version for RM1C 2.0.627 was dowloaded in autoupdater. I unrooted and made system partition as it was. but it detects that the system was accessed as R/W and OTA update aborts with error 7.
I just wonder if the new version will not have that error that makes crash the desktop after exiting from fullscreen(as I found workaround to reutn to desktop after crash is to click xbox360 "back " button ). I have the incremental OTA for RM1C version 2.0.627 on usb, but cant install it . need reflash system.img.
RemixOS_Jason said:
Do you mean, you'd rather have a fresh copy of Remix OS on version 2.0.626 with none of your previous saved data and apps? Did you have your previous version rooted? I believe if you were just looking for a fresh start with the latest version of Remix OS, you can reboot your Mini, and then press F2 when prompted, and then do a factory reset. You may need to go through some updates, but I'm told you should restart in 2.0.626.
I hope this helps.
Click to expand...
Click to collapse
Got it. I remember your issue. I'm trying to work out 2 solutions for you:
1. Downgrade as you asked for. I'm waiting for the Chinese ROM team to give me the package and tutorial to be translated.
2. Flashing the Global (English) ROM into your Mini.
Do you prefer either/or? I'll respond still in private message to you about this.
Thanks!
kesmtk said:
My device is RM1C. I Wanted to root on 2.0.512 version. but it autoupdated to some unstable version 2.0.622 with crashes after exiting fullscreen app. (I noticed there appeared an error messages on some missing file when connected via uart port. this is the message:
init: unknown magic init: unknown magic init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
) but 2.0.512 was most stable version for me no errors on the uart also.
I rooted 2.0.622 version and allowed an app that I bought "gamecontroller2touch pro" to grant superuser permissions. It works as mapping xbox360 controller buttons to touch games like a charm, where a jide keymap does not support xbox360 it only works for keyboard input.
Then I saw a version for RM1C 2.0.627 was dowloaded in autoupdater. I unrooted and made system partition as it was. but it detects that the system was accessed as R/W and OTA update aborts with error 7.
I just wonder if the new version will not have that error that makes crash the desktop after exiting from fullscreen(as I found workaround to reutn to desktop after crash is to click xbox360 "back " button ). I have the incremental OTA for RM1C version 2.0.627 on usb, but cant install it . need reflash system.img.
Click to expand...
Click to collapse
option 2 ; ) flash RM1C 2GB ram with RM1G firmware
..........option 2, I have pm'ed a message for you Thank You for help. :good:
RemixOS_Jason said:
Got it. I remember your issue. I'm trying to work out 2 solutions for you:
1. Downgrade as you asked for. I'm waiting for the Chinese ROM team to give me the package and tutorial to be translated.
2. Flashing the Global (English) ROM into your Mini.
Do you prefer either/or? I'll respond still in private message to you about this.
Thanks!
Click to expand...
Click to collapse
How and how long will this go on?
As a long time fan of Android-x86 I didn't really notice the Jide hardware until "The Merge"...
Now I see the Mini being sold off for half price and I wonder: Will it be obsolete on arrival?
I don't think I'd need Nougat on the device. I'd even think I'd be able to live with Lollipop.
But I can't operate a computer in my home network, that is unsafe to operate.
So I need the assurance that it will receive security updates until the end of its life cycle (3-5 years after purchase).
And I need the ability to control any computer I operate.
So will there be security updates until 2020?
Will you provide them or will you enable the community to provide them?
And will I be able to administer the system, de-activating services which have un-fixed vulnerabilities, blocking IPs, etc?
Generally that requires operating with root permissions on Linux systems, including those with an Android GUI.
$40 for a multi-media capable Linux systems running an attractive GUI is a great offer.
$40 for a potential IoT bot in my home network, which I can only throw away once somebody manages to subvert it, is a very bad investment, especially if it causes external damage.
So what will it be?
And will your future systems be any different?
BTW: Apart from 8 big desktops (Windows, Linux & Remix), 2 silent Atoms (Remix, Windows + Linux), 6 Notebooks (Windows, Remix & Linux), I operate 5 Android tablets and 10 Android phones (Canogenmod based Android, rooted by design).
Some of the PC hardware is 10 years old (3.4GHz Quad-Core Penryns work just fine with Nvidia GTX 1070), some of the Androids are still great after almost 6 years (e.g. Asus Eee Pad Transformer).
All of them run up-to-date operating systems with the latest patches. Typically not thanks to the vendor who produced the hardware but to the open source community which maintains Linux and Cyanogenmod.
If you treat the software on your hardware differently than Android-x86, you'll burn the brand very, very quickly.
usb boot
i have the remix mini rm1g with 626 is there a way to boot ubuntu via usb if i can boot into ubuntu can i install it and reinstall remix os on ubuntus root directory using grub customizer i know i can do that with remix os for pc
joeylikesubuntu said:
i have the remix mini rm1g with 626 is there a way to boot ubuntu via usb if i can boot into ubuntu can i install it and reinstall remix os on ubuntus root directory using grub customizer i know i can do that with remix os for pc
Click to expand...
Click to collapse
I don know, havent tried load linux on remix, I have rasbpberry pi and orange pi where they load everything from sd card.....remix mini loads from nand flash.
Maybe if you go to remix about screen and keep clicking build number to activate developer options.
Then dev options appear near about button in the options screen. Then enable usb debugging. select usb0 for debugging (the upper usb port)
install adb driver http://adbdriver.com/ . plug male - male usb cable PC-usb>remix upper usb port. Enter adb and enter root console. Maybe from root console it is possible to setup remix to load from sd card(where you linux kernel will be) by edidting uboot .
kesmtk said:
I don know, havent tried load linux on remix, I have rasbpberry pi and orange pi where they load everything from sd card.....remix mini loads from nand flash.
Maybe if you go to remix about screen and keep clicking build number to activate developer options.
Then dev options appear near about button in the options screen. Then enable usb debugging. select usb0 for debugging (the upper usb port)
install adb driver http://adbdriver.com/ . plug male - male usb cable PC-usb>remix upper usb port. Enter adb and enter root console. Maybe from root console it is possible to setup remix to load from sd card(where you linux kernel will be) by edidting uboot .
Click to expand...
Click to collapse
I don't think so. This is not a developer device, and not a traditional PC. It is a closed Android device (like Android phones and tablets), so would require custom bootloader/boot/etc. to loader other software. The Mini is made to show of Jide's bread and butter, their Remix OS software. They likely won't support officially installing any other 3rd party OS, since again, they are selling software and the hardware is incidental. Compared to the Raspberry Pi, which is open hardware designed for developing, and made to run various Linux releases and has broad support.
Now that it's EOL for the mini and no new updates are coming for it could we PLEASE have root?
4llerbuntu said:
Now that it's EOL for the mini and no new updates are coming for it could we PLEASE have root?
Click to expand...
Click to collapse
rooting easy, you must have uart to usb adapter. if you unscrew two screws under the rubber cover you will see 3 pins with GND tx and rx. Your usb to uart dongle shold have gnd tx and rx pins. 3,2 volt reading on the tx and gnd with multimeter. solder uart gnd pin to remix mini gnd. then uart tx to remix mini rx, and uart rx pin to remix mini tx. Open hyperterminal in windows. dial with com port setting 112500 none 8. and you have terminall root. from there you can cd to usb drive to install root
kesmtk said:
rooting easy, you must have uart to usb adapter. if you unscrew two screws under the rubber cover you will see 3 pins with GND tx and rx. Your usb to uart dongle shold have gnd tx and rx pins. 3,2 volt reading on the tx and gnd with multimeter. solder uart gnd pin to remix mini gnd. then uart tx to remix mini rx, and uart rx pin to remix mini tx. Open hyperterminal in windows. dial with com port setting 112500 none 8. and you have terminall root. from there you can cd to usb drive to install root
Click to expand...
Click to collapse
Looool:crying:
This is "easy"??
Seriously?
I always knew about this method. So there must be a reason I haven't tried it.
Anyways, id prefer rooting similar to what we have on numerous other Android devices, smartphones and TV boxes.
They usually don't require opening the device and a UART cable ......
re
4llerbuntu said:
Looool:crying:
This is "easy"??
Seriously?
I always knew about this method. So there must be a reason I haven't tried it.
Anyways, id prefer rooting similar to what we have on numerous other Android devices, smartphones and TV boxes.
They usually don't require opening the device and a UART cable ......
Click to expand...
Click to collapse
Well I had an old usb nokia adpter I tierd it appart and discoverd it has an uart interface with 3.2 volt communications sigal logic which is what is needed for remix mini. I soldered communications and boom I am as root user for remix mini . I copied supersu.zip and a instalation file from zip file inthe same foler. ran instalation file via sh command and root installed.
Maybe its possible to access root terminal from usb debugging.. I didnt try that.
You can install adb driver from adb.com. then click remix mini settings about. keep clicking version to get developer. enable developer. click settings menu again. click developer. click usb debuugging on. click usb0. then connect upper usb remix mini to pc usb. open pc cmd line and enter adb console. maybe from there you could do the stuff as root . I could
How do you install this? I'm currently on 2.0.203 and it says it fails trying to check for a new version. My internet is working fine though.
jbradshw said:
How do you install this? I'm currently on 2.0.203 and it says it fails trying to check for a new version. My internet is working fine though.
Click to expand...
Click to collapse
You must donwload phoenixsuit
https://www.dropbox.com/s/x7mnzui95c4459z/PhoenixSuit_EN_V1.0.8.msi?dl=0
adbdriver from
adbdriver.com
remix image
https://osdn.net/projects/remixos/downloads/66607/factory_image_rm1g_B2016110301-secure.img/
Warnining you will lose your all remix mini data.! games apps etc.
go to remix mini settings > abount. keep clicking on version number . the developer options will enable.
again go to settings>developer options > enable usb debuging , select usb0.
UNplug remix mini power cable.
Get a cliper and make a tool to push a "reset" button that is located in the hole in the back of remix mini. Try to for yourself by sticking cliper in the hole and feel the putton presses.
use usb MALE-MALE cable. connect remix mini upper usb port to laptop/PC usb.
I use windows 7 64bit
in laptop/PC:
1. Install the ADB tool
2. INstall PhoenixSuit. You will be guided through their installation instructions.
!let it autoupdate and restart it after updated
3. After the installation finishes, you can run PhoenixSuit by double-clicking the PhoenixSuit icon on the desktop.
4. Click ‘Firmware’ to enter the firmware flashing interface.
5. Click ‘Image’ to select the Remix OS img file.
!! click download one or multi partition to flash:
https://p5.zdusercontent.com/attach...Df0FXhMJxbcJLYkUku2_vQ.bLJYy1dgTWPhpfUCaIS3WA
6. Connect your Remix Mini to the PC via a USB-USB cable. NOTE: The cable must be plugged into the top USB port of remix mini.
7. Insert a straightened paperclip into the hole ar the back of your Remix Mini to press reset button.
8. while keeping clip inserted (reset button pushed) insert power cable to remix mini. Flashing image will start automatically, you can release the clicp holding reset button.
9. wait to complete, reboot mini.
Wow... what happened to the auto-update feature?
Was wondering if it's easy to root or unlock the bootloader on the new chromecast with google tv
Sent from my A0001 using Tapatalk
We should wait for a custom recovery first. But you might loose all the DRM keys when the recovery partition is flashed. So choose wisely.
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
dictorclef said:
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
Click to expand...
Click to collapse
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
xnamkcor said:
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
Click to expand...
Click to collapse
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/android-tv/chromecast/chromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
airwolf1544 said:
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/an...hromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
Click to expand...
Click to collapse
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
EsotericCleric said:
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
Click to expand...
Click to collapse
I've succeeded to format large USB sticks (64GB) on FAT32 with Rufus portable (free software). SD card is working only in an USB stick adapter on my hub.
Hi,
Did anyone succeed to write files on a second USB stick?
I have the first USB stick formatted to extend the storage, and a second one as an external USB storage.
The second stick can be read or write on a PC, can also be (only) read on Chromecast with Google TV, but cannot write on it on chromecast. It's a write permission restriction there.
There is an ADB solution or similar?
Thanks,
Any sign of being able to root the Chromecast with Google TV yet?
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
card13 said:
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
Click to expand...
Click to collapse
Dude, you're putting the cart before the horse. If you don't have root or equivalent*, you can't boot a twrp, assuming you even wanted to.
Technically, you need the ability to boot an unsigned boot/recovery image, which includes the ability to feed that unsigned image into the device. If you can do that, then take the original boot image, install magisk on it, feed it in, and tell it to boot it. There's your root, no twrp required.
EDIT:
card13 said:
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
Click to expand...
Click to collapse
This isn't a chicken and egg problem AT ALL. twrp is just a custom recovery image. Without already having root or equivalent, there is NO WAY TO RUN IT.
Let me give you a simple example of the process as it works on a pixel phone;
1) Developer options --> OEM unlocking
2) adb reboot-bootloader
3) fastboot flashing unlock
4) fastboot [boot|flash boot] boot-magisk.img
* where boot-magisk.img is the boot.img found in the factory package, after being modified by magisk.
Steps 1-3 are the barrier for this device. twrp won't help you with them because you need to COMPLETE STEP 3 before you can install or boot twrp, and by the time you've completed STEP 3, you've already achieved the goal.
There are 2 ways to get there;
1) figure out how to accomplish steps 1-3.
2) figure out a privilege escalation exploit, either through Android, or through recovery, or whatever else you can come up with.
Here is a very simple question that could help start this process off; IS THERE ANY WAY TO BOOT INTO FASTBOOT?
Delete
has anyone tried to boot off sd card? possibly running emuelec?
The real reason to root this thing has to be to bring support for HD audio passthrough.
Apparently the Amlogic S905D3G used to have HD audio passthrough on older firmware. If someone could figure out how to reenable it it would be the perfect streamer.
You can find twrp builds for the S905 but they are for older versions of android
blaze2051 said:
has anyone tried to boot off sd card?
Click to expand...
Click to collapse
wanna know if you found the answer.
What's the answer
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
npjohnson said:
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
Click to expand...
Click to collapse
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
urbanman2004 said:
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
Click to expand...
Click to collapse
Nope. Locked up tight.