why cant i get the driod to boot upon my hd2
seidel6969 said:
why cant i get the driod to boot upon my hd2
Click to expand...
Click to collapse
Don't know. Give us some more information:
Witch rom
witch radio
Witch Android build
what did you do, what do you see!?
We are able to help you if you give us some more details.
PS you need to have minimum Radio 2.08 on your device fore be able to run Android.
um im not sure im not that good with phones how do i find the rom the raidio stuff
Q; Witch Rom/Radio version do I have?
Go to your setting tab > Info about your device > Software Info > You can see your Rom/radio version there.
rom is 2.12.531.1(90963)wwe
radio is 2.10.50.26
seidel6969 said:
rom is 2.12.531.1(90963)wwe
radio is 2.10.50.26
Click to expand...
Click to collapse
Based on the info I know/see it seems your device software is compatible with Android. So try this:
1. Format your SDCard with FAT32 (backup your data first) (what kind of card do you use? (size) (some users mention to have troubles on 16GB SD cards))
2. Copy your android to your SD card (read the installation guide of the chef, not all Android Builds runs from /Storage Card/Android)
3. Run CLRCAD.exe and then Haret.exe.
4. Be patient, it will take a few minutes at the first boot.
5. if you complete the setup process reboot and then you can do what ever you want.
Normally this must work.
how do i format my sd card to what you said how do i back up my data and its a 16 gb
seidel6969 said:
how do i format my sd card to what you said how do i back up my data and its a 16 gb
Click to expand...
Click to collapse
First of all get start on a other SD, to much peoples have problems with that.
Format SD: (tittle is deferent but it is the same way)
Backup date? copy it to your PC
Attention if you have a software like Navigation software on your device there are mostly a protection key placed on your device (anti piracy) so don't format your SD, you will loose your installation key!
when i tryto boot it it tells me the job control is turned off
seidel6969 said:
when i tryto boot it it tells me the job control is turned off
Click to expand...
Click to collapse
Did you tray what I have mention! I mean install it on a other SD!?
Make sure the SD card is format.
Ow PS; witch build do you use!?
Give me the link pleas.
http://www.multiupload.com/UDBG8J4TMG
Related
And installed Modaco's ROM ( nice work fella ) - a few questions ( I'm new to this so bear with me).
1) Where do I get the new 'radio' - and how do I install it? ( If you say 'push' it to the phone, can you explain that.
2) Does BlueX make te Bluetooth work on the Hero ( send & recieve files ). Yes I did a search!
3) Is there a simplistic way to partition my SD card? I'm on a Mac with no access to PC / Linux machines
4) I did ( and glad did ) a Nandroid backup which I used once effectively - where s the backup file, is it on the phones computer. If so can I transfer it to the SD card ( and still use it )..I want to save space as I'm down to 97mb.
5) Finally, still to save space, can I et the various program cache files to use the SD card instead of the phones memory.
Thanks all
1) The most recent radio can be found at MoDaCo here. It's packaged as a *.zip so installation is as easy as copying it to /sdcard as update.zip and then applying it as before from the recovery screen.
2) Dunno.... haven't pursued BT xfers myself yet.
3) I've no experience with Macs so dunno what partitioning software is available for them, but you can partition your card non-destructively (shrink the FAT32 partition and create a new ext3 in the resulting free space) using the GParted LiveCD. Boot from the LiveCD with the card in a reader and it will be recognised. Just be very careful that you select the correct volume before making any changes.... repartitioning your HDD by mistake can cause raised blood pressure!
4) /sdcard/nandroid/HT*/ contains the backups. I generally keep my most recent on-card but save various others on a PC for testing purposes.
5) Search the Market for TA Utility. It does exactly that.
HTH
/Al
Shluggity said:
1) The most recent radio can be found at MoDaCo here. It's packaged as a *.zip so installation is as easy as copying it to /sdcard as update.zip and then applying it as before from the recovery screen.
2) Dunno.... haven't pursued BT xfers myself yet.
3) I've no experience with Macs so dunno what partitioning software is available for them, but you can partition your card non-destructively (shrink the FAT32 partition and create a new ext3 in the resulting free space) using the GParted LiveCD. Boot from the LiveCD with the card in a reader and it will be recognised. Just be very careful that you select the correct volume before making any changes.... repartitioning your HDD by mistake can cause raised blood pressure!
4) /sdcard/nandroid/HT*/ contains the backups. I generally keep my most recent on-card but save various others on a PC for testing purposes.
5) Search the Market for TA Utility. It does exactly that.
HTH
/Al
Click to expand...
Click to collapse
Speaking of the radios, my generic hero came with baseband 63.18.55.06U_6.35.04.25 and I downloaded modaco's update (didn't apply it yet) and I'm unclear as to the version number of this baseband update since it is marked identical to mine with the exception of the "U".
megaoptimus said:
Speaking of the radios, my generic hero came with baseband 63.18.55.06U_6.35.04.25 and I downloaded modaco's update (didn't apply it yet) and I'm unclear as to the version number of this baseband update since it is marked identical to mine with the exception of the "U".
Click to expand...
Click to collapse
but the new radio is 63.18.55.06_6.35.05.15.
My UK Orange Radio version number has the U as well. It it customised by Orange perhaps ?
I'm seeing no difference between 63.18.55.06U_6.35.04.25 and 63.18.55.06_6.35.05.15 on an Orange Hero running MoDaCo v1.1. I updated the radio after reflashing the ROM so that I could compare before with after, and my untrained eye sees nothing unexpected. No issues previously, and none afterwards.
/Al
my UK sim-free Hero had the U in the version before I upgraded the radio, and it still has the U in the version now, even though it wasn't shown in the version string at MoDaCo, whence I got the upgrade.
cdmackay said:
my UK sim-free Hero had the U in the version before I upgraded the radio, and it still has the U in the version now
Click to expand...
Click to collapse
Well I'll be.... so has mine! I'd never noticed, probably 'cos I only glanced at it brieflyto check the update had worked. Thanks for the heads-up, sir.
/Al
Hi All,
I have been using Android for a while now, with no real issue. After changing my DPI I found I could no longer use my old build (Black screen) after booting into Android. Now whatever build i choose I cant boot past linux with it errroring out at
"superblock could not be read or does not describe correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an altanative superblock"
Seraching the forums I found this means I have no/corrupt intrid.gz, so i redownloaded and formatted my SD card and to still no avail.
Is anyone able to assist? Devs?
Thanks alot to all the devs that built these great ports, now I cant stand being without Android.
Things Tried:
- Task 29
- SD Re-Format
- Different Builds
- Left to run for ages hoping it will pass
- Tried numerous times
- Tried an older build
- Tried class 2 (Currently using class 6)
Have you ever think of reflashing winmo and start over again?
To be honest, no... I havn't changed anything in winmo though, and didnt think that would affect it?
try delete Android folder, not Android App. see what happens. everytime mine didn;t boot i did that and it boots. dunno what it is but it just work
ginjopowder said:
try delete Android folder, not Android App. see what happens. everytime mine didn;t boot i did that and it boots. dunno what it is but it just work
Click to expand...
Click to collapse
Thanks mate I tried that, I just backed up ma lil guy so I'm going to try a reflash and Task 29. Will report back.
Hey Guys,
I really need help! My Haret is getting stuck still at the same point trying to boot linux after Task 29!
Are there any other powerful tools than Task 29?
Have you think of trying another sd card?
justwonder said:
Have you think of trying another sd card?
Click to expand...
Click to collapse
I have tried the class 2 16gb and my usual class 6 8gb, its driving me crazy. What is the conventional method of formatting an SD card? I use panasonics SD Formatter?
Spoofy said:
I have tried the class 2 16gb and my usual class 6 8gb, its driving me crazy. What is the conventional method of formatting an SD card? I use panasonics SD Formatter?
Click to expand...
Click to collapse
Go into windows mobile start menu tools format sd and go from there. Looks like some screw up on your sd card.
xlr8me said:
Go into windows mobile start menu tools format sd and go from there. Looks like some screw up on your sd card.
Click to expand...
Click to collapse
Hey Mate thanks for that i just tried it and still same error message... I've resorted to playing games on my GF's iPhone...
Hello, my phone can only boot 10% of builds released.
try the same as you:
-hspl
-mtty
-change WMO ROM
-differents SD Cards.
The only builds that i can boot are:
-mattc1.7
-mdeejay froyo sense 2
if you didnt try it, do it if you can.
Thanks, Unfortunately I have tried those and I'm running HSPL3.
I have updated the first post with the things i have tried to fix this...
Back to playing games on my girlfriends iPhone...
Dont know if this helps, it also says:
"/bin/sh: can't access tty; job control turned off"
Are you using any of the builds which create their own 512MB/1GB/2GB datastore? Those may take up to 30 mins or more to complete the initial config and show up the GUI
Spoofy said:
Dont know if this helps, it also says:
"/bin/sh: can't access tty; job control turned off"
Click to expand...
Click to collapse
check your startup text file. It might've changed somehow. I should show where android is supposed to boot up. ex: [ set cmdline "rel_path=Android" ] or whatever the name of the folder where android is located. I've got two going right now. One in a folder called AndroidJ for JDMS' v1.7 and another folder called HyperDroidv1.5. I've used quickstart android apps on the winmo side and sometimes they screw up the "startup.txt" file. Make sure that what's in the "startup.txt" is the same name of the folder where it's located. One last ex: for my android that's located in the "AndroidJ" folder, my startup.txt reads: set cmdline "rel_path=AndroidJ"
Because of the apps/shortcut/whatever you can use to boot up android in winmo mode have messed up my startup.txt, I now just use file explorer or total commander to go to the actual folder and hit CLRCAD and then HARET.exe.
edding7 said:
Hello, my phone can only boot 10% of builds released.
try the same as you:
-hspl
-mtty
-change WMO ROM
-differents SD Cards.
The only builds that i can boot are:
-mattc1.7
-mdeejay froyo sense 2
if you didnt try it, do it if you can.
Click to expand...
Click to collapse
WOW mdeejay's seems to work!!
Thanks for the heads up!
Drakknar said:
Are you using any of the builds which create their own 512MB/1GB/2GB datastore? Those may take up to 30 mins or more to complete the initial config and show up the GUI
Click to expand...
Click to collapse
I'm fairly sure Mattc's does but i left that and Froyostone over night and to still no avail...
Answers to "can no longer boot any android Build"
Okay I had the same situation but the way I fixed that was to
Turn off my Device
Push Volume up/down at the same time and then push the end button and hold it until it you see an icon on you phone and press vol/up again. and confirm yes
after that let the phone reboot again and turn it off
and now you press only the DOWN/VOL and END button at the same time. and now you are taking to the HSPL to Flash your Rom again.
Flash a WinMO rom of your choice. and let it reboot.
after that you need to reformat your SD card and uncheck the QUICK FORMAT let it fully format the SD card
and after your SD card if finished.
Download An ANDROID Build of your choice and enjoy!
I hope this helps
and sorry for the poor english
dalpha08 said:
Okay I had the same situation but the way I fixed that was to
Turn off my Device
Push Volume up/down at the same time and then push the end button and hold it until it you see an icon on you phone and press vol/up again. and confirm yes
after that let the phone reboot again and turn it off
and now you press only the DOWN/VOL and END button at the same time. and now you are taking to the HSPL to Flash your Rom again.
Flash a WinMO rom of your choice. and let it reboot.
after that you need to reformat your SD card and uncheck the QUICK FORMAT let it fully format the SD card
and after your SD card if finished.
Download An ANDROID Build of your choice and enjoy!
I hope this helps
and sorry for the poor english
Click to expand...
Click to collapse
No poor english at all, i didnt think it wasn't your first language!
I have tried the Mdeejay build and it works for now!
Thanks for the help, but i'm pretty sure i tried it all except re-install my hspl? Wouldn't task 29 do the same?
This is meant to be a basic guide to installing and maintaining Android (SD CARD/RAM) on your HD2
NOTE: This guide is not meant for NAND versions of Android installation !!
I want to thank all the XDA forum developers who have made it possible to put Android on the HD2. This is my attempt to make a simple guide for what can be confusing and somewhat scary process (It certainly felt like that to me!!).
For detailed information guide and FAQ please read this thread by mskip
For clear explanation of how things work in Android on HD2 these two threads have excellent detailed information:
http://forum.xda-developers.com/showthread.php?t=813434
http://forum.xda-developers.com/showthread.php?t=790095
Click to expand...
Click to collapse
Before you start you need this Info
Windows ROM version > All Ship ROMs are compatible
Radio Version > Radio needs to be 2.08.50.xx or more (x.xx.51.xx are not compatible)
SPL
Click to expand...
Click to collapse
How to get the Info
For items 1,2 in WinMo look under Settings>About Phone>Software information
This info is also displayed on the bottom left corner (the numbers after the alphabets R,D,G) of your initial boot up white screen with green HTC logo
For item 3 >> Turn phone off > Press and hold Volume down button >briefly press release power button >SPL version is displayed on bootloader screen (Red/Green/White)
Click to expand...
Click to collapse
For those with Radio > 2.08.50.xx you can install Android >> GO TO STEP B
Click to expand...
Click to collapse
For those with Radio < 2.08.xx.xx you cannot install Android without upgrading your Radio (Flashing a new Radio) >> GO TO STEP A then STEP B
Click to expand...
Click to collapse
STEP A (Flashing a new Radio)
If you do not have a compatible Radio version follow the steps below:
Upgrading to the newest HTC stock ROM: This process will upgrade your Radio version anyway (The latest 3.14 ROM has Radio version 2.14.50.4 which is compatible with Android installation): LINK HERE
If you don't want to / or can't upgrade to the latest HTC stock ROM you are going to have a slightly more complicated way
If SPL is 2.10.xxxx or below then use HSPL method. Click here
If SPL is more than 2.10.xxxx you have 2 choices (since HSPL does not work)
Use SSPL method click here
Downgrade your SPL and then use HSPL method click here
Note:
>>Please check the radio version recommended by the Android Build maker>>
>> Click here if you want to download Radio versions
Click to expand...
Click to collapse
STEP B (Installing Android)
If your Radio is compatible (>2.08.50.xx) then here is how to install Android on your HD2
1) Micro SDHC card
Should be atleast 4 Gb, Class 2/4/6/8/10
Formatted clean with 32 or 64 Kb cluster size
2) Install automatic boot loader on WinMo :
This allows you to choose between booting into Windows or Android on start up. From 2nd Android bootup onwards these programs will make it easier to load Windows/Android at startup and you can even specify autoboot into Android if you wish.
Download this as a cab file and install in the phone memory (not in SD card)
Android Loader v6.0 Final for HD2
Exceller bootloader
You can of course manually always boot up Android anytime from Windows File Explorer by running CLRCAD and then HaRET files included in the Android build (see below).
3) Android Build :
Download your chosen Android build on your computer.
Extract / Unzip the folder on the computer
Now copy into the Root of your SD card.
Folder should be labelled "Android"
Once copied into SD card you will see 2 files: CLRCAD.exe and HaRET.exe which have to be run to boot into Android.
There will also be other folders / files (Android Apps, initrd.gz, system.ext2, rootfs.img, zimage, startup.txt, ts-calibration) please leave them as they are.
There are many choices in builds available, such as - MDJ, Darkstone, MIUI,. Please search the forum to look at the different features. I can't advise you on what clothes to buy. The same reasoning applies to advising on Android builds, you have to find out what is right for you...Try the build, if you dont like it, just go for another build..copy and paste your new android folder over the old one and its done.....
4) Data.img :
Your build may have a ready-made one included in the build folder or available to download separately. Size of data image is upto you, 256Mb/512Mb/1Gb (or more). This determines the Size of your Android operating system space for settings and downloaded apps etc. Bigger size allows you to keep more apps etc.
>> At start up if you have a ready-made data.img file, booting up in Android is much faster (5-10 min). (You can choose the image size yourself with this option)
>> If you boot up without a ready-made data.img (Clean Install), then this is created by Android system at first bootup which takes longer (up to 30 min) Here the system will choose its own set default image size depending on startup commands in the build. Its not easy to change this size once its created (although it is possible)
5) First Android Boot
Once you have reached this step you are all set. It really is that simple!
These steps are performed with the phone booted in WinMo
Charge your phone to 100%. This ensures proper battery calibration.
In your File Explorer open the Android folder on the SD card
Run CLRCAD - Nothing seems to happens - This is normal. !!!
Run HARET - Small pop up window with grey progress bar appears with message HaRET LINUX BOOTING - You should then see some text lines in the top left corner of the screen and then a Splashscreen (blank screen with a HTC logo) Please be patient and allow time for the initial bootup.
If Android loads successfully, then (depending on your build )another Splashscreen will appear and then the Lockscreen for Android is launched.
Set up your phone for first use as per onscreen instructions and let all account finish syncing before doing anything else
Click to expand...
Click to collapse
Once you are up and running here are some of my own tips to maintain your system.
1) Always back up of your data.img file on to your pc/mac (weekly)
This is better done in WinMo. This will mean that you can always have a failsafe arrangement for troubleshooting.
2) Troubleshooting (If you start getting data corruption errors or force closes .
> Make another Clean Install of the build -Boot into Android- Reboot in WinMo - Connect to Computer - Copy backedup data.img file into the New (compatible) Android folder.
DONE! you are back where you started. All apps, settings, contacts,emails, messages are saved as they were at the time of backup.
You can also use a backup programme like Titanium Pro. This is useful when going over to a completely different chef build as you cannot (usually) take your old data.img file across.
3) Changing kernels
Follow instructions on the relevant thread.
For MDJ / Hastarin Kernels the following steps work
Boot up in windows - copy 'zimage' and 'Root' folder (which has modules) from the new kernel and paste into your /Android folder on SD card (i.e replace zimage of old kernel).-
Boot up android - check for successful upgrade under Settings>About phone>Software>Kernel ... the new kernel should be listed.
On boot up android will copy the contents of the /Android/Root folder to the relevant place.
If upgrade is successful then while in Android use a File explorer (with root permissions) to delete the 'Root' folder within Android folder, as this is no longer needed.
Note: Some kernels require the Modules (wifi,bt,lights etc) to be copied manually using Root File explorer while booted in Android. Please check the relevant posts for correct steps.
4) Upgrading Android Builds
I always do a clean install i.e let the Android build its own data.img with a clean formatted SD card.
Once this is done then copy your old backed up data.img and overwrite the newly created data.img to get all your info and settings as they were.
Caution: data.img is usually not compatible across different chef builds and its best to start a clean install if you are going to use a completely different build altogether. You can get you settings back by using a backup programme such as Titanium. Google sync will get your Contacts and Calendar back anyway if you have synced it previously to Gmail account.
5) Improving Battery Life
Having read through a lot of forums and trying out various techniques here are tips that have worked for me.
Charge your phone in WinMo to 100% (Green LED) While still connected to charger boot to Android and wait for the LED to go green. Then disconnect from charger.
Autoboot before launching into windows/sense fully, I use Exceller autoboot in 3 sec.
Rebooting Android 2-3 times after initial install and letting it 'settle' for a 1-2 days
Turn off any functions not required e.g BT, WiFi, GPS, Autosync
Turn down screen brightness to minimum
Use a battery current widget to monitor drain
Conditioning of battery: Boot into windows when battery is @ 5%, Discharge the battery fully and let the phone turn off> charge fully to green LED while phone off >> Boot up in Android and continue charging till LED green>> One cycle every 2 weeks
Recalibration: In Android with File explorer (e.g ES Explorer), Choose settings, enable root access and then in Root delete ... /data/system/batterystats.bin . This should be done when 100% charged, Now disable root access in file explorer and close, Run the battery down fully and follow the step above...
Fully conditioned battery should show about 4.2 - 4.3 V charge at 100% (Free app Battery Indicator)
Dataswitch (free app) allows switching mobile data when phone is not in use such as during night time etc
I keep Airplane mode in windows as default before first boot in Android (Not sure if this really helps)
For me greatest battery drain seems to be when i am in area of poor phone signal> switching to 2G helps using Dataswitch app
Things that don't work:
Task killers are not really very useful according to Hastarin
For more detailed information regarding battery life issues have a look at this post
Click to expand...
Click to collapse
Have fun and enjoy your HD2 with Android
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Noob question
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Proz00 said:
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Click to expand...
Click to collapse
Updated, Thanks for that.
loni90 said:
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Click to expand...
Click to collapse
I agree with you on that. The stock ROM work fine (check my sig) and to be honest I tried the custom ROMs but felt more comfortable with the Stock ROM. It means less messing around with your phone!
Its most important however that your Radio is compatible though. If its not then there is no choice but to Flash a new Radio ROM.
Seems to be well explained, thanks
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Ahh i just told mate at work copy android to sd card run cllr then haret.
Worked fine lol
omershahab said:
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Click to expand...
Click to collapse
This only applies for Upgrading and not a New install. For a new install its always better to let the system create a data image or use the 'empty' image supplied with the build. Most builds have codes to create a default size image. If thats not to your liking then you can choose a supplied image of desired size and do the first boot up...
For upgrading purposes this method has advantages
1) it ensures a clean trouble free installation first time (makes sense to avoid any conflicts with the old data image on boot up.)
2) If there are any problems with the build then at least you can identify them before you transfer the old data image.
solid.snake said:
Seems to be well explained, thanks
Click to expand...
Click to collapse
Your welcome
Difficult to express how easier you made this process for me, with all info provided.
In my name, and the name of all the rest,that will use this thread to start with Android on HD2...... txs
Updated
updated info on maintanence and battery life
despy1989 said:
updated info on maintanence and battery life
Click to expand...
Click to collapse
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
KrewsialNL said:
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
Click to expand...
Click to collapse
Not at all Reminds me I have to do the same on my signature too
Hey, would doing this void my warranty/contract insurance?
Im on virgin media UK, if that helps.
Thanks for the great tutorial anyway
Unless u install a HSPL my understanding is that there is no reason to void your warranty. But I m no expert in these matters. Having said that my old hd2 touchscreen was freezing and I had hspl on it but managed to reinstall the original SPL back and returned it to virgin and this one is the replacement..they didn't complain ..
Sent from my HTC HD2 using XDA App
I have radio 2.07.51,22_2 and spl 1.42
Does that mean the only way I can do this is the HSPL method?
Great guide m8 good job well explained, but I dont know if this helps anyone but I always un-mount my SD card before a reboot or shutdown, on some builds it can reduce corruption to your data image (ie cedesmiths builds)
JR
@ samdeath . Have u considered upgrading your HTC stock ROM? The new 3.14 ROM also upgrades ur radio. In that case there is no messing with HSPL. The other option is SSPL which does not change ur original SPL.
@ JR . In theory if u umnount the SD Card in Android, it only delinks the the SD card portion outside of your data image? If u umnount the whole SD card then android would crash.
Sent from my HTC HD2 using XDA App
I cant upgrade the stock rom, there isnt a virgin media rom on the htc website, and the normal one says my device is not eligible for it. However, ive installed HSPl now, and followed all the steps, changed the radio to 2.15 etc, However now ive just "installed" android for the first time and its been on the htc spash screen for like an hour. I did not use a data file, is this normal?
Using froyo hd v4.6 btw
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.
Hello,
First of all, if I seem to be rude or impolite, it's just because of my bad english, I apologize in advance...
I have bought a nook tablet 8G, cyanogenmod (android 4.3.1), as it uses to bootloop very often (and as it needs a simple wipe of data but a re-installation of the apk) every 4 or 5 boots, I thought it would be a great idea to re install a new cyanogen...I thought it would be as easy as on my samsung galaxy
But now, the only thing that it does is to reboot on recovery mode...When I try to power it on, it starts just like if it is ok, then it boots on TWRP mode (my CWM on galaxy seems to be more friendly). I have tried again to reinstall my rom, but it is said that it is "unable to mount data1".
I have also done a wipe dalvik cache but I prefer to stop and ask for further information before I do serious damages
I have also tried to install "flashable fix bootloop" but no way
Thank you very much !
Have you tried re-installing using SD-based CWM (e.g., see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163 or http://forum.xda-developers.com/showpost.php?p=50828000&postcount=1)?
Hello Digixmax,
Thank you very much for your answer.
Before asking, I have searched and I saw this post http://forum.xda-developers.com/showthread.php?t=2692403, and I am very happy to have the opportunity to be helped by the one who posted it !
I haven't tried it because there are some parts that I don't understand very well but now I'm gonna try :fingers-crossed:
- I have a 32g sd card that I would like to use for my apk, shall I use it to install CM11 or shall I buy a new one ? Will a 2G sd card be sufficient ?
- What does "set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag" mean ? To set = let it free ? "Set its Active flag", I have no idea of what it means, will I understand by doing the manipulation ?
- For the second part, I have to download next u-boot.bin and flashing_boot.img in boot.zip from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet but I don't know wich one to choose.
What does MLO means ?
For the other points, I think it will be ok.
Oh...Is it necessary to intall CM10 before upgrading to CM11 ?
Thank you very much Digixmax, I am sorry to bother you with such stupid questions
Sarah B. said:
...
I have a 32g sd card that I would like to use for my apk, shall I use it to install CM11 or shall I buy a new one ?
Click to expand...
Click to collapse
You can just use existing card.
Will a 2G sd card be sufficient ?
Click to expand...
Click to collapse
It should be sufficient for installing CM.
- What does "set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag" mean ? To set = let it free ? "Set its Active flag", I have no idea of what it means, will I understand by doing the manipulation ?
Click to expand...
Click to collapse
You should see menu for partition type/flag settings when you're in a disk partition tool.
- For the second part, I have to download next u-boot.bin and flashing_boot.img in boot.zip from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet but I don't know wich one to choose.
What does MLO means ?
Click to expand...
Click to collapse
MLO is one of 3 the files you need, they are contained in the zip file succulent_boot.zip
...
Is it necessary to install CM10 before upgrading to CM11 ?
Click to expand...
Click to collapse
No. See http://forum.xda-developers.com/showthread.php?t=2692403 for pointers/tips on installing CM11.
Thanks a lot, Digixmax, I'm gonna do this tomorrow (I've to go to work now).
I will tell you what the situation is as soon as I finish.
Sarah B. said:
Thanks a lot, Digixmax, I'm gonna do this tomorrow (I've to go to work now).
I will tell you what the situation is as soon as I finish.
Click to expand...
Click to collapse
Since your NT is already on CM, you might want to try first the method to update from an older CM version to CM11 outlined at http://forum.xda-developers.com/showthread.php?t=2670589.
digixmax said:
Since your NT is already on CM, you might want to try first the method to update from an older CM version to CM11 outlined at http://forum.xda-developers.com/showthread.php?t=2670589.
Click to expand...
Click to collapse
:victory: :victory: :victory:
Thank you very very very very very much :highfive: