Related
I have a massive headache trying to figure all this stuff out.
I have a t-mobile hd2
RAM of 576 and Speed of 1024MHz and Flash of 1024MB
when hold the volume and power button, it reads the following:
PB81120 SS-B3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
I downloaded the andriod installer on my computer, along with HSPL, HSPL2, and HSPL3.
My objective is to hopefully get android on my Leo.
Ive read all the threads and im just really confused...I ran HSPL2 and i get an error screen that says i have a bad Model ID.
PLEASE HELP ME...IM SO LOST!!
You have some options:
1. Use search function of the board. (recommended)
2. Try to get the answer is the Android porting thread. I suggest to search the thread first (recommended, too)
3. this one
Ulti
i tried all of that and i get so confused...can someone actually help me?
I'm going to help so many next time you will help yourself and look a little more.
First of all you dont need to flash and thing to run android. It is in beta currently and is ran buy haret which is kinda like a emulator. When you read the link below you will realize that it has all kinds of problems. Those problems are known.There is also a Faq about those problems and what you can do to help solve them.
there are not instructions on how to operate android. By trying this we assume you know a little bit about android.
It looks like you already have the hslp but I am also going to provide a link on how to flash rom's and radio's.
http://forum.xda-developers.com/showthread.php?t=621930
This is direct information on forum for installing android.
http://forum.xda-developers.com/showthread.php?t=719646
This is the spoon fed version
>INSTALLATION INSTRUCTIONS FOR DIFFERENT BUILDS<
DarkStone1337 - HTC Sense (Desire build)
1. Download from one of the above sites and extract the contents to your pc
2. Copy all files to the ROOT of your Storage Card
3. Using a File Manager goto your Storage Card and run clrad.exe (it wont do anything but it has run) followed by haret.exe
4. Wait for Android to boot (may take upto 5 minutes)
dan1j3l - Froyo build
1. Download from one of the above sites and extract the contents to your pc
2. Copy the Android folder (including all files within the folder) to the ROOT of your Storage Card
3. Using a File Manager goto your Storage Card, Android folder and run clrad.exe (it wont do anything but it has run) followed by haret.exe
4. Wait for Android to boot (may take upto 5 minutes)
Or...you could try this...I've been using it for the last two days and everything seems to work on it
http://hotfile.com/list/600926/774f186
Download the Sense Droid and follow the istructions attached on file
No disrespect ment to you as I do know you have been around for a while. But it seems as though he doesnt have much experience in doing this.
That would seem like its just gunna cause more problems. there is still problems with power management. So its gunna eat away at his battery. This I know because I run android almost full time and thats a risk i'm just willing to deal with.
Secondly it boots right into android no stopping at windows. So if something goes wrong he is stuck. And will have to reflash.
I tried it and couldnt tether and had to go right back. Maybe he doesnt need to tether so it could be fine but I really think he should start off slow.
hazard99 said:
No disrespect ment to you as I do know you have been around for a while. But it seems as though he doesnt have much experience in doing this.
That would seem like its just gunna cause more problems. there is still problems with power management. So its gunna eat away at his battery. This I know because I run android almost full time and thats a risk i'm just willing to deal with.
Secondly it boots right into android no stopping at windows. So if something goes wrong he is stuck. And will have to reflash.
I tried it and couldnt tether and had to go right back. Maybe he doesnt need to tether so it could be fine but I really think he should start off slow.
Click to expand...
Click to collapse
Non taken mate...I was not thinking about what you said
If that's the case....he'll read both of your posts and make the proper desition.
Have a great day!
http://forum.xda-developers.com/showthread.php?t=732380
which one do i chose, The Energy.Leo.21911.Sense2.5.(Jul.21.7z) OR THE
Energy.Leo.23121.Sense2.5.(Jul.21.7z)????
i downloaded sense, but no android market...whats up with that?
Android
Why do you want Android on your WM phone???
The builds you downloaded are still windows mobile. You really need to read the htc-Linux thread
Sent from my HTC Desire using XDA App
all i want is the android app store on my phone...thats it. how do i do that without having to boot it up from my phone through haret.exe?
Android is a completely different operating system than windows mobile. The android app store and the apps will not work in windows mobile!
If you try to install a windows application on linux OS you will fail too.
Everything you need to know is in this post
This Thread tells you step by step how to do it want what you need to do it forum.xda-developers.com/showthread.php?t=893948 it work fine for me i had no problems at all doing it the market great and my phone is running just fine
ITZMACMATIC said:
This Thread tells you step by step how to do it want what you need to do it forum.xda-developers.com/showthread.php?t=893948 it work fine for me i had no problems at all doing it the market great and my phone is running just fine
Click to expand...
Click to collapse
Please look at dates of threads before you reply to them. This thread is 6 months old. It was made before Android was finished being ported. I'm sure the people in this thread already know about Android.
Sent from my HTC HD2 using XDA App
Sorry I saw it there didn't think to check the date my bad
Sent from my HTC HD2 using XDA App
This is not my work thanks [tytung]
This is just and edit to make boot with WP7 under MAGDLR SD
Installation
1.Copy android folder to root of sd card
2.Select boot AD SD viola
This is the only room that work for me flawlessly nothing bad.
http://www.megaupload.com/?d=DMB6N2UA
Intel_x said:
This is not my work thanks [tytung]
This is just and edit to make boot with WP7 under MAGDLR SD
Installation
1.Copy android folder to root of sd card
2.Select boot AD SD viola
This is the only room that work for me flawlessly nothing bad.
http://www.megaupload.com/?d=DMB6N2UA
Click to expand...
Click to collapse
I've got most SD builds working flawlessly... If there's any build you need, pm me. I'd be glad to help or share.
The stickied thread above also has the edited files for a lot of builds... I don't really think a new thread was needed about this. This probably should have been posted in the original build thread.
Help Hopefully
Hi Zarathustrax,
I am hoping you can help me I am just returning to flashing after about 4 months and see that NANDing is being done it was a theory when I last flashed and now see something else MAGDLR. Well at this point all I know is flashing to SD if i'm correct nand is the rom becomes your main rom when turing phone on no more WM bootup? What is the MAGDLR? Which way is best? If it's other than SD how do I do it? Where do I start?
I tried a MY Touch rom and really liked it but because so much has changed couldn't get it working fully and no one would give me any help (no response).
If your able to help I appreaciate it.
Magldr is the tool you flash to the phone first that allows your phone to flash android or wp7 to your nand, the internal memory. Yes, nand roms will replace winmo on your phone. Magldr also allows is to have wp7 or android on our nand and also still boot different sd android builds from the sd card also, allowing us to dualboot wp7 and android. The thread about magldr is in the nand android development section, and there are sticky threads about how to flash and install nand builds.
Sent from my HTC bravo using XDA App
zarathustrax said:
I've got most SD builds working flawlessly... If there's any build you need, pm me. I'd be glad to help or share.
The stickied thread above also has the edited files for a lot of builds... I don't really think a new thread was needed about this. This probably should have been posted in the original build thread.
Click to expand...
Click to collapse
There was an awesome Sense ROM that was NOT HD/Z but had a flip clock. Do you remember/know what that was? I would love to boot that Via AD SD
otherwise just any regular Sense ROM (Desire port) that everything works in. The Z/HD ports always have some funky lag and serious battery drain, so can't really use as daily.
also FYI, this ROM freezes on startup every time (MAGLDR SD), seems like a bad rootfs.img or something...
Very Important Information For Beginners
/Introduction to Android for SD Cards
Okay, firstly I made this thread because pretty much every new person to this section of the forums is completely lost and unsure what things are or what to even do. We are also sick and tired of threads saying 'how do I get stared' or 'which is the most stable' etc.
----------------------
Download your files from here:
You will be accessing these websites quite often so it might pay to bookmark them
Kernel downloads, almost always download the top one, they are updated often (needs extracting): http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Rootfs downloads, download the top one, they aren't updated as often as the kernels above but still quite regularly (also needs extracting): http://files.xdandroid.com/rootfs/
Initrd downloads, rarely updated (don't extract, just rename to initrd.gz) http://files.xdandroid.com/initramfs/ People almost never need to download one of these separately.
----------------------------------
Basic need-to-knows:
Kernel: Your modules/zImage. Your zImage always needs be in the root (first folder) of your android folder on your SD and ALWAYS named zImage, your modules should also be in the root of your android folder named modules-LOTSofNUMBERSandLETTERS.tar.gz never rename your modules. It should always be in .tar.gz EG: modules-2.6.27.46-01276-g6a6a1c1-dirty.tar.gz
Rootfs: Must be in the root of your android folder named rootfs.img
Initrd: Needs to be in the root of your android folder named initrd.gz
Data.img: Generated on the first boot of android and placed in root of android folder. Is a virtual memory file that acts as the phones internal memory for android. Holds all your settings etc. May have to be recreated some times (just by deleting it)
Haret.exe: the file executed by your Windows ROM to kick Windows out of memory and boot android.
system.ext2: Main android file, must be in the root of your android folder. Holds all of your build.
startup.txt: File that instructs android how to start up. Needs to be in the root of your SD. (I will cover this further down)
ts-calibration: A file in the android folder that holds calibration information of the touch screen.
Various Folders: You will see/have/need other various folders created in the root of your SD and in the root of the android folder, such as conf, cache, data, media etc. You usually don't want to delete these.
Root: The root folder of any partition is the "highest" folder in the hierarchy. The root folder contains all other folders and can also contain files. For example, the root folder of the main partition on your computer is probably C:\. The root folder of your DVD or CD drive might be D:\.
Also Known As: "the root"
RIL: Radio interface layer: basically controls your radio (GSM/CDMA network)
------------------------------------------------
startup.txt
VERY IMPORTANT, your startup.txt must be customized to your device. (mine is a rhod110). You can find your model number under your battery. This file belongs in the folder with your android.
My startup.txt looks like this
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 rel_path=FRX07 physkeyboard=rhod100_uk acpuclock.oc_freq_khz=710000"
boot
Now I believe you should be able to copy and use this as yours with a few slight modifications. Change rel_path= to wherever your android is stored on your sd, for example when I go to my sd inside the folder frx07 (the root of my android folder) all my android files are there. If your folder was called andboot it would be rel_path=andboot. (without that full stop) Now change your physkeyboard= to your model of your phone, mine is rhod110 but the rhod100_uk keymap is EXACTLY THE SAME AS THE RHOD110 so that's why I use rhod100_uk instead of rhod110 (rhod110 isn't recognised by frx07), this is important to make sure your keys are assigned properly.
------------------------------------------------
Models of rhod:
From what I know that exists. If you find one not listed, make sure you tell me so I can update the list
rhod110 uses rhod100_uk and it works as it should
These can be used for physkeyboard= in startup.txt (needs updating, some may no longet be supported because F22 hasn't commited old changes)
rhod100_de
rhod100_es
rhod100_fr
rhod100_it
rhod100_nl
rhod100_nordic
rhod100_uk
rhod210
rhod300 (tilt2)
rhod400
rhod500
Getting set up:
Go to http://forum.xda-developers.com/showthread.php?t=1171052 and download the FULL BUNDLE
Other builds exist such as gingerbread but this guide only covers froyo frx07.
Replace/add the Kernel from the downloaded build with the latest one (remember this is the zImage and modules-NUMBERS.tar.gz). Updating is as simple as this, do it often - there is no data loss. See links mentioned above for links. Making sure that the (if there were) old kernel files are all deleted and the new ones are called zImage and modules-NEWdifferentNUMBERS.tar.gz
Replace/add the rootfs.img with the latest one from the link above it should be named rootfs.img.
Remember that the rootfs and kernel are updated quite often and that you should check and update every few days.
Make sure your startup.txt is correct and make sure everything is where it should be in a folder on your computer, then copy the folder to the root of your sd card.
Navigate to this folder using the file explorer in your Windows ROM (YOUR PHONE) and run the Haret.exe
It will then have some writing running down a black screen before booting android (it's just preparation to booting) read it if you want
Android will start and you should leave it about 2-5 minutes before touching anything, it has things running in the background and it will be slow, still setting itself up. Navigate to settings and set up your phone. If anything goes too badly wrong you can always delete data.img and start again! Data.img is the internal memory of the phone, remember? Well, until we get android working on the real internal memory...
---------------------------
Structure:
My SD card. (with android on it)
I'm running:
kernel: 20110819_183957 http://glemsom.users.anapnea.net/android2/htc-msm-linux/
build: Froyo FRX07http://forum.xda-developers.com/showthread.php?t=1171052
rootfs: rootfs-20110816-7e04198.zip from http://files.xdandroid.com/rootfs/
Code:
EncFiltLog.menc
kbd_info
Android
cache
download
tmp
Private
Games
Installs
DCIM
Others
Videos
Images
Sounds
media
frx07
rhodimg.nbh
My android is in frx07
inside my frx07:
Code:
data.img
ts-calibration
startup.txt
modules-2.6.27.46-01348-g9de837f.tar.gz
zImage
haret.exe
initrd.gz
system.ext2
AndroidApps
conf
media
rootfs.img
-----------------------------------------
Backup/Restore
when you have the need to backup and restore data, look for an app called Titanium Backup. I have never used it but heard it works brilliantly, even backing up your apps! There is a 'donation' version and a free version with not many differences. I suggest you go check it out!
-----------------------------
USB CONNECTIVITY
When your phone is in Android you can not use it like a USB, HTC's drivers will not work and you have to use certain programs until this is implemented.
Windows: Install DroidExplorer this lets you open a terminal (like command prompt) on the phone, lets you browse device adding/deleting files, among other features that are very useful. If that DroidExplorer doesn't pick up your phone (when picked up it will be called 0000000000) install PDAnet on your phone and pc. PDAnet provides the drivers needed to connect the phone. It also lets you use your phone as a modem and you can send SMSs using your computer. Do NOT run PDANET at the same time as DroidExplorer. When PDANET is connected it WILL use your phone for data connections - this is the only warning. The phone is not used for any networking when DroidExplorer is connected.
Mac: Unknown to me (can someone post?)
Linux: Never tried, it is easier than windows (can someone post a method?)
---------------------
Overclocking
Do NOT overclock WINMO.
If you want to overclock your device do so at your own risk.
it is as simple as adding "acpuclock.oc_freq_khz=710000" without quotes to your startup.txt cmdline. 710000 (approx 710 mhz) can be swapped for any number but this is practically the highest stable speed achievable. I use 710000, works fine for me.
-------------------------
Known problems across ALL BUILDS:
Media Player Some tracks might have playing issues. FIX: HERE
Bluetooth is experiemental
Speakerphone static : seemingly random issue
USB plugging the device into a computer, it will be recognised, but not by HTC drivers. FIX: You must use something like DroidExplorer and PDAnet to browse the device and ADB (android debug bridge). See above ^^ (USB tethering is being fixed/has been fixed)
FN LED On keyboard the caps LED works but the FN LED currently does not. FN still works fine
No deep sleep: FIX: disable GPS (or kill the running app causing phone to not sleep)
Failure booting Android: Phone fails to enter android after running haret.exe FIX: Make sure your winmo is NOT overclocked before booting android.
Booting or SD Card related problems: Make sure your card is formatted as FAT32 (reformat as Full Format if it is not working)
More information is available on the wiki, there is also information there if you want to get into development. There is a pretty good FAQ on that wiki too
Remember XDAndroid is not just for this device.
If any of this is wrong or you think something should be updated/changed, please tell me
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
AkumaX said:
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
Click to expand...
Click to collapse
Indeed, there is no "is_gsm" command .
arrrghhh said:
Indeed, there is no "is_gsm" command .
Click to expand...
Click to collapse
Thanks to both of you, not bad considering I don't even have a cdma phone eh?
anything I need to add? I will tidy it all up soon
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
the.decoy said:
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
Click to expand...
Click to collapse
I thought this was squashed in recent kernels?
arrrghh said:
saneksem said:
add that to startup,helped me on 2 gb card
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
You don't need this if you're on a newer kernel!!!!
Just update your kernel folks, no need for this in the startup!
Click to expand...
Click to collapse
Oh, ok. I must have missed that. I only needed it on my older SD which I haven't tried using for a month or so.
I guess the only thing I would suggest (all minor things) would be maybe to bold/underline keywords, like "kernel", "rootfs", etc.. to differentiate things that may change over time; ex: I'm running FRX05 system.ext2, 3/1/11 rootfs from F22, 3/1/11 zImage/modules (kernel) from arrgghh, etc... And, I guess you "could" be nice and show people what they could edit in the startup.txt, depending on their phone; ex: I'm Sprint, so I would do kb=rhod400, cdma=1, etc..., but for each phone.
I would probably have to do all the different startup.txt's in a different thread, unless I just provide a quick table... I will think about it however I do like the idea about bolding key words.
Most new people don't realize if they have their call/end/windows/back buttons on in winmo, they will stay on while on android and never go off. Might want to put that in your first post before telling them to run haret...
at the end where you say you can just delete the data.img and startover its probably a better idea to say to be patient and reboot the phone once or twice before ditching your data.img ! and creating it is the bulk of the first boot, the linux black screen with the scrolling words section.
you can talk about saving your data.img just incase something goes wrong.
titanium backup is a must
having an app that can save sms when you switch builds (not a big deal for everyone but important to some.)
also let new users know android isn't perfect, things randomly completely mess themselves all the time, don't get discouraged just start fresh with a format and new files when deleting the data.img doesn't work and you'll be just fine.
All I want to know now is if I have helped anyone yet and if they had any problems with any part of it or want me to clarify anything I will be quite happy with such replies ^-^
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
ryannathans said:
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
Click to expand...
Click to collapse
There's never an ETA for anything getting fixed - BT seems close, but who knows the exact date it will be done? As CyanogenMod says, the only rule is don't ask for release dates / ETA. It'll be ready when it's ready.
Some problems are being looked into more than others, but I wouldn't say one in particular has been left out to rot. jb is fixing up BT, entropy is working on GPS fixes, wistilt2 on the RIL of late... Basically devs pickup things that are of an interest to them to fix. There's a lot still to fix/cleanup, so taking it all on alone is a little daunting. Gotta break it down into smaller pieces so it's at least somewhat manageable.
Thanks and a question...
First, thanks for the awesome post - quite helpful...
Second: I haven't mussed with my phone for about a year, for various reasons, the main one being that I was happy with my previous phone and the ROM I finally settled on, the secondary one being that phone died, and I now have a (blech) Sprint TouchPro2 (RHOD400), and am on my sixth (yes, sixth!) brand new TP2 - they keep giving me a new one because of problems (things, like... oh... say, not being able to answer calls... kind of a basic function in a mobile phone, nah?!) And, I've had no interest in futzing with what is already a frustrating and non-functional phone. I was hoping I could upgrade instead of getting another TP2 the last time I brought it in for probs, but they would only downgrade me to worse phones. So... here I am, wanting to put Android on my phone and see if there is any improvement. Or, at the least, be able to utilize some of the decent progz/gamez for Android. I mean, if I can't answer calls, at least I can use it as a handheld gaming system, right?!
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
PS: one of my friends said "Tell 'em you're a hawt babe - then they'll help for sure!" (ROFL)
And, thanks, again!
Tynkrrbell said:
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
And, thanks, again!
Click to expand...
Click to collapse
Well the reason you can't find any info on it, is that it's not required .
These builds run entirely off of the SD (currently - I wouldn't try NAND yet, it's in its infancy) so there's no need to do any HardSPL or anything really to prep - just drop the bundle on your SD card - if it's at the root, run haret.exe and gogogo!
Oi. I get the stupidcard of the day!
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
My gf suffices for that .
Hope you enjoy Android!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
Not to burst any bubbles here, but if you are saying you are a "hawt babe" and give boobpr0n mumbo jumba, you are prolly not one and won't give it anyways.. so nobody will most likely believe you here..
Good luck though~
I have only had my G-Tablet for about a week and I already ROM it to 2.2 Vegan. This is probably a simple issue and easily fixed. I know Windows very well but the Android OS is totally new to me, sorry.
I have kids and installed a 16GB MicroSD card for movies. I have played with format and such for a few days and finally found that ACC audio at high volume settings and Mpeg4 Video seem to work the best. I use Total Video Converter and it works for everything i have, the G-Tab, Xbox360, my wifes iPhone, and even my Blackberry.
Anyway the issue is when I turn the Tablet off and then back on it keeps re-formating the MicroSD and I can't figure out how to make it stop doing this. I converted 8 movies (7.39Gb) and after the first shutdown of the day it formatted the card.
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Also double check which version of Vegan you are running. Vegan Froyo is up to 5.1.1, but has been discontinued. It's now called Mountain Laurel and is hosted on Slatedroid. It requires the 1.2 bootloader. I'm running CalkClem V6 http://forum.xda-developers.com/showthread.php?t=1024120 as a daily driver and it's amazing.
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
Thank you I will give it a shot here in a few minutes. If it works my kids will be most greatful.
brettdwagner said:
Also double check which version of Vegan you are running. Vegan Froyo is up to 5.1.1, but has been discontinued. It's now called Mountain Laurel and is hosted on Slatedroid. It requires the 1.2 bootloader. I'm running CalkClem V6 http://forum.xda-developers.com/showthread.php?t=1024120 as a daily driver and it's amazing.
Click to expand...
Click to collapse
I may need to change anyway. I am now getting a pop-up error, 3 and 4 times when i first boot. SORRY! the application Google Services Framework (proccess com.google.process.gapps) has stopped unexpectedly. Please try again. < Force Close >
Not sure what I did?
I am actually surpriced no one has come out with a fully functional Honeycomb OS for this tablet yet. I keep reading and they are still have wireless issues or some other small issues. Personally I want to try and upgrade it to a working 2.3 Gingerbread version.
Question, what Android version is CalkClem V6 build on?
Your force close issue will be solved by formatting the sd card. This will delete everything on your internal SD so beware! Instructions are in this tutorial http://forum.xda-developers.com/showthread.php?t=865245
CalkClem V6 is running Froyo, which is the only version of android which is fully operational on the gtab (full hardware acceleration). Gingerbread and Honeycomb roms work pretty well, but for me Froyo is perfect. Give CalkClem v6 (or5) a try if you have some time, it's based on the stock OS, but it's blazing fast (and overclocked to 1.5Ghz by default). Battery life is excellent.
Make sure you pay attention to your bootloader when selecting a new ROM. To read up on your bootloader and why it's important check out goodintention's site: http://viewsonic-gtablet-for-dummies.webs.com/
Good luck!
woody213 said:
I may need to change anyway. I am now getting a pop-up error, 3 and 4 times when i first boot. SORRY! the application Google Services Framework (proccess com.google.process.gapps) has stopped unexpectedly. Please try again. < Force Close >
Not sure what I did?
I am actually surpriced no one has come out with a fully functional Honeycomb OS for this tablet yet. I keep reading and they are still have wireless issues or some other small issues. Personally I want to try and upgrade it to a working 2.3 Gingerbread version.
Question, what Android version is CalkClem V6 build on?
Click to expand...
Click to collapse
Froyo, 2.2
And don't be surprised with not having a fully functional HC rom yet. In fact, the GB roms are also not "fully" functional. Nvidea has not released drivers for those OSs for our hardware. If they never do, then we'll never have fully functional versions of those firmwares. It also appears that HC runs on a different kernel base. From what I've read, the kernels we have available now are .32 kernels, and HC needs a .36 kernel. the numbers don't mean much to me, but kernel devs saying that it's a difficult hurdle eto jump does. If Pershoot and Clemsyn aree leary about developing .36 kernels, then it must be pretty difficult.
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
Well it is still deleting the movies. I read your post and tried to create a folder called .nomedia on the MicroSd card and windows will not allow the . in the folder name so I tried just nomedia as a folder name and surprising the folder stayed but the media with in the folder was deleted.
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
Disregard the last post. I must really be having a bad day. Windows can't make that folder but the tablet itself can. when I did that I moved my sons movie "Planet Hulk" and it stayed in the folder no issues. Thanks again.
You just saved me A LOT of headaches and frustration!!! Scanning another thread for a solution about my external microSD causing my gTab to lock up, doing what you suggested, adding a file named .nomedia, worked perfectly!! 3 system reboots in a row anyway. When I use it tomorrow we'll see if it still works
My gTab would hang for as long as I let it whenever I would insert any of my microSD cards into the slot. Scanning SD Card would NEVER go away, gTab would lock up, simply hitting the power button would shut it down. But not like holding it down to shut it off normally, hitting like you want to put it into sleep mode, that type of hit would just shut it down. Take the card out - gTab would work perfect...........
Now I can leave the darn thing in there instead of using the USB adapter I bought for it and it's one more "annoyance" I've managed to overcome.
THANKS!!!!!!!!!!!!!!
BTW, stock operating system....yes, the god awful tap n tap 1.2 crap..... I only watch mp4 movies on it and that works great, so I'm not messing with ROM's.....yet.......
brettdwagner said:
Congratulations on your new tablet. This issue has to do with the way the gtab indexes media and can be easily fixed by placing a file named ".nomedia" in the root directory of the sdcard.
Click to expand...
Click to collapse
I've got the Telstra RHOD110 and I've tried to install every Android build since about the first stable Froyo release. Every single one of them hangs during the Linux boot sequence.
It seems to be memory related, but past that I've got no clue - I'm an IT professional, but I'm in operations, not development so I'm a little out of my depth with this stuff.
I have NOT done HardSPL yet, but I was under the impression this wasn't necessary for the SD card method (which I wanted to test out before potentially bricking a ~$1000 phone). In theory it's just the standard Telstra WinMo 6.5 ROM...
It's getting a bit frustrating after years of trying this and seeing everyone else talking about how easy it is. I'm using F22's rootfs and TotalCommander isn't showing up any *.csv files in the \windows directory, so I can't even try the GBX0C (2.3.7) test build. Anyone know why my phone seems to be different?
Hi Nukkels lets focus on getting GBX0C running since
Nukkels said:
I have NOT done HardSPL yet,
Click to expand...
Click to collapse
First things first: Format the MicroSD you plan to use using the HP USB Disk Storage Format Tool. Just use google to find it. I use version 2.1.8. Perform a FULL format, FAT32.
Now download the package from here: http://files.xdandroid.com/GBX0C_Full_Bundle_2012.04.24.zip and extract all of the files to the root of your SD card
Nukkels said:
I've got the Telstra RHOD110
Click to expand...
Click to collapse
This device is identical to the RHOD100_UK so pull the startup.txt out of the STARTUPS\RHOD\RHOD100\ and place it on the root of your storage card.
Nukkels said:
I'm using F22's rootfs
Click to expand...
Click to collapse
I think I understand why you are trying to use that rootfs since it has some stuff tailor made for Rhod110/Telstra but I don't think it is necessary. Just leave the existing rootfs.img from the GBX0C package, it should work for you.
Nukkels said:
TotalCommander isn't showing up any *.csv files in the \windows directory
Click to expand...
Click to collapse
I haven't used TotalCommander for a while, but it seems to me that there is an option like "Hide Files in ROM" or "Show Hidden Files" or something like that which is probably preventing you from seeing the .csv's in /Windows/. So find that option and find those files and copy them to the root of your storage card.
If you can't find them I think that GBX0C should still boot as I have booted without any .csv's, there was just no sound in the build. But at least you can see that it is working. In case you absolutely cannot find them, here are my .csv's from rhod100uk: View attachment RHOD100_CSV.zip, unzip to your storage card, which hopefully will get you going.
Okay, now all you need is a touch screen calibration file. If you do not have one here is mine:View attachment ts-calibration.zip
Unzip it to the storage card.
Now you have everything in place on the card, please at this point do not try to edit the startup.txt or anything in /conf/. Lets just get this baby working.
Before you run anything I would set WM to airplane mode, set your backlight control to any level but auto (ie low), and make sure that you are not overclocking your processor in WM.
Now run HaRET.exe from the root of the storage card and cross your fingers mate!
Be patient, first boot can take ~10 minutes sometimes.
EDIT: Also there is a fairly good chance that your thread will get moved to the Android section... if it does and you aren't able to post in it anymore you can PM me.
I just wrote up a huge post and lost it all :crying:
Basically I followed your sintructions step by step and it worked!
I'd never done a FULL format before - that takes hours! I'm guessing this might have been the main issue.
I'll play around over the next few days with F22s rootfs and rhod110 startup parameter, Airplane mode turned on, etc to see if any of that had an impact. I never thought to set backlight to manual or use Airplane mode.
Hopefully I can help find the crucial step I missed, so it can be included in the installation instructions (or at the very least someone might stumble on this thread).
Anyway thanks a tonne for your help, it got me up and running!:good:
Thread moved to the appropriate section.
I genuinely hope you didn't pay ~$1000 for this phone... wow.
Caldair said:
Hi Nukkels lets focus on getting GBX0C running since
First things first: Format the MicroSD you plan to use using the HP USB Disk Storage Format Tool. Just use google to find it. I use version 2.1.8. Perform a FULL format, FAT32.
Now download the package from here: http://files.xdandroid.com/GBX0C_Full_Bundle_2012.04.24.zip and extract all of the files to the root of your SD card
This device is identical to the RHOD100_UK so pull the startup.txt out of the STARTUPS\RHOD\RHOD100\ and place it on the root of your storage card.
I think I understand why you are trying to use that rootfs since it has some stuff tailor made for Rhod110/Telstra but I don't think it is necessary. Just leave the existing rootfs.img from the GBX0C package, it should work for you.
I haven't used TotalCommander for a while, but it seems to me that there is an option like "Hide Files in ROM" or "Show Hidden Files" or something like that which is probably preventing you from seeing the .csv's in /Windows/. So find that option and find those files and copy them to the root of your storage card.
If you can't find them I think that GBX0C should still boot as I have booted without any .csv's, there was just no sound in the build. But at least you can see that it is working. In case you absolutely cannot find them, here are my .csv's from rhod100uk: View attachment 1184798, unzip to your storage card, which hopefully will get you going.
Okay, now all you need is a touch screen calibration file. If you do not have one here is mine:View attachment 1184808
Unzip it to the storage card.
Now you have everything in place on the card, please at this point do not try to edit the startup.txt or anything in /conf/. Lets just get this baby working.
Before you run anything I would set WM to airplane mode, set your backlight control to any level but auto (ie low), and make sure that you are not overclocking your processor in WM.
Now run HaRET.exe from the root of the storage card and cross your fingers mate!
Be patient, first boot can take ~10 minutes sometimes.
EDIT: Also there is a fairly good chance that your thread will get moved to the Android section... if it does and you aren't able to post in it anymore you can PM me.
Click to expand...
Click to collapse
I tired this on my TILT 2 it wouldnt work...
tru209 said:
I tired this on my TILT 2 it wouldnt work...
Click to expand...
Click to collapse
So... what's broken with it? Where does it stop?
Edit - basically, you've gotta give us more to go on. We can't help you with "wouldn't work" - it's simply not enough info. Provide as much as you can - what did you try, what happens when it boots, did anything semi-work, etc etc. Details!
tru209 said:
I tired this on my TILT 2 it wouldnt work...
Click to expand...
Click to collapse
Did you bite your tounge just right while dancing backwards to the wizard of OZ soundtrack? That always does it for me when it 'wouldnt work'.
My experience was that the full format using the HP tool is a crucial step. I did a full format using other tools but I had no joy until I did it with the HP tool.