Hi, I cant download or transfer apps to my sd card! people say that if i download astro it will fix but it didnt! So im looking for a way to fix it. can anyone help me
Sent from my MSM using the XDA mobile application powered by Tapatalk
x12CHRIS18x said:
Hi, I cant download or transfer apps to my sd card! people say that if i download astro it will fix but it didnt! So im looking for a way to fix it. can anyone help me
Sent from my MSM using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
If you're referring to USB Mass Storage in FRX07, then don't hold your breath.. unfortunately, it's a known issue.
maff1989 said:
If you're referring to USB Mass Storage in FRX07, then don't hold your breath.. unfortunately, it's a known issue.
Click to expand...
Click to collapse
It's unfortunately an issue with the loop'd mounts. If you create dedicated partitions for at the very least data - USB mass storage actually does work. hyc did some patching on this, not sure if that's in FRX07 or not. I haven't tried 07 on dedicated partitions yet.
Droid Explorer does a pretty damned good job of faking it tho...
arrrghhh said:
It's unfortunately an issue with the loop'd mounts. If you create dedicated partitions for at the very least data - USB mass storage actually does work. hyc did some patching on this, not sure if that's in FRX07 or not. I haven't tried 07 on dedicated partitions yet.
Droid Explorer does a pretty damned good job of faking it tho...
Click to expand...
Click to collapse
Ohhh I see thanks for the correction.
I noticed in the default rootfs.img for FRX07 that the init does in fact check for a dedicated data partition, although I'm not sure if it puts that partition to use as the data partition (that coding looked a little confusing :\). I assume it would otherwise it wouldn't make sense to check if there's no mount commands following...
It sounds intriguing, though.. May give the dedicated data partition a try; could help with performance, let alone fix USB MS
EDIT: Seems this idea has already been put into effect for FRX07... http://www.neopeek.com/viewtopic.php?f=14&t=7441
maff1989 said:
Ohhh I see thanks for the correction.
I noticed in the default rootfs.img for FRX07 that the init does in fact check for a dedicated data partition, although I'm not sure if it puts that partition to use as the data partition (that coding looked a little confusing :\). I assume it would otherwise it wouldn't make sense to check if there's no mount commands following...
It sounds intriguing, though.. May give the dedicated data partition a try; could help with performance, let alone fix USB MS
EDIT: Seems this idea has already been put into effect for FRX07... http://www.neopeek.com/viewtopic.php?f=14&t=7441
Click to expand...
Click to collapse
Indeed, but CWM of course uses different mount points than XDAndroid...
so XDA:
p1 - fat32
p2 - rootfs
p3 - system
p4 - data
CWM from Neopeek:
p1 - fat32
p2 - system
p3 - data
p4 - cache
So you can certainly setup dedicated partitions and use XDAndroid's rootfs. If you use CWM, just be wary, the layout is different. CWM is easier because it installs Android to these partitions for you - otherwise you have to move the data to the partitions yourself .
arrrghhh said:
CWM is easier because it installs Android to these partitions for you - otherwise you have to move the data to the partitions yourself .
Click to expand...
Click to collapse
By this, you mean copying, say, the rootfs.img to the second partition, or would the rootfs need to be extracted to the partition? I assume the latter..
maff1989 said:
By this, you mean copying, say, the rootfs.img to the second partition, or would the rootfs need to be extracted to the partition? I assume the latter..
Click to expand...
Click to collapse
Yes, the latter. Same with system.ext2 and data.img - these need to be expanded onto the dedicated partitions.
What I did was mount the system.ext2 file (looped) on my Ubuntu server. Mount a data.img (looped) as well. Then I stuck a mSD -> USB converter plug in the server, and formatted the card with fdisk assigning the partitions. Mounted those partitions in Ubuntu, then tar'd the data over (IIRC there's issues with cp, doesn't preserve permissions).
Code:
cd /dir1; tar cf - . | (cd /dir2; tar xf -)
is how I tar'd it.
arrrghhh said:
Yes, the latter. Same with system.ext2 and data.img - these need to be expanded onto the dedicated partitions.
What I did was mount the system.ext2 file (looped) on my Ubuntu server. Mount a data.img (looped) as well. Then I stuck a mSD -> USB converter plug in the server, and formatted the card with fdisk assigning the partitions. Mounted those partitions in Ubuntu, then tar'd the data over (IIRC there's issues with cp, doesn't preserve permissions).
Code:
cd /dir1; tar cf - . | (cd /dir2; tar xf -)
is how I tar'd it.
Click to expand...
Click to collapse
Oh wow... that's a bit different than I anticipated, although your information is very much appreciated the dir1 and dir2 refer to the mount points for the system.ext2 and data.img, respectfully, correct? And it's two commands in one, separated by the "|" correct?
Off-topic.. What's IIRC?
And also, I can comprehend that "tar'ing" files means copying them in some way, shape, or form, but how would that preserve permissions over simply cp'ing them from the mount point in Ubuntu to the partition on the SD card? Or perhaps even manually copying the files to the SD partition? Considering these actions are performed in Ubuntu, I would assume permissions wouldn't be altered :\
maff1989 said:
Oh wow... that's a bit different than I anticipated, although your information is very much appreciated the dir1 and dir2 refer to the mount points for the system.ext2 and data.img, respectfully, correct? And it's two commands in one, separated by the "|" correct?
Off-topic.. What's IIRC?
And also, I can comprehend that "tar'ing" files means copying them in some way, shape, or form, but how would that preserve permissions over simply cp'ing them from the mount point in Ubuntu to the partition on the SD card? Or perhaps even manually copying the files to the SD partition? Considering these actions are performed in Ubuntu, I would assume permissions wouldn't be altered :\
Click to expand...
Click to collapse
IIRC = if I recall correctly
Yes, that's all one command and dir1 is the system.ext2 mount or the data.img mount (the source), dir2 is the mount point on the card (destination).
I don't know why cp doesn't preserve permissions - there's probably some switch you can pass that will preserve perms. I'm not an expert here, I only know I had a boatload of issues when I just used cp... Talked to some experts, and they gave me that tar command - which worked perfectly.
Idk what you are talkin about! so is there way to fix this situation?!
x12CHRIS18x said:
Idk what you are talkin about! so is there way to fix this situation?!
Click to expand...
Click to collapse
You can fake USB mass storage with Droid Explorer. That's really the only option on looped mounts.
Where can I get droid explorer?
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
Where can I get droid explorer?
Sent from my Touch Pro II with Froyo
Click to expand...
Click to collapse
Here, let me Google that for you...
Haha thanks man! But I'm still having trouble.... I downloaded droid explorer then it told me that I have to download android sdk tool so I did and its still telling me that I have to download android sdk tools
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
Haha thanks man! But I'm still having trouble.... I downloaded droid explorer then it told me that I have to download android sdk tool so I did and its still telling me that I have to download android sdk tools
Click to expand...
Click to collapse
So... did you click the link to "do it for me" or whatever it says during install, or did you pick a manual install? You should just let the application do it for you, otherwise you have to download it yourself and then point it to whatever directory you installed it at... Oy.
I downloaded the zip file
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
I downloaded the zip file
Click to expand...
Click to collapse
Ok, would you like a cookie?
I still have a problem, droid explorer doesn't recognize my phone. i have my phone in debug mode
x12CHRIS18x said:
I still have a problem, droid explorer doesn't recognize my phone. i have my phone in debug mode
Click to expand...
Click to collapse
Did you get an 'XDA' device in device manager? Did you read the FAQ and install PDAnet if the drivers with Droid Explorer don't work?
yeah i got XDA but it wont let me install it, it keeps on saying "cant find device". Do I have to download PDAnet if i cant install it?
Related
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Tip from aled99 to edit without linux.
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
Some files that are already edited:
CoreDroid HD 0.4 edited by ricola7
Desire_hd2 system.ext2 file
HD2ONE 0.3.5 system.ext2
JDMS 1.62
MDJ HD v4.6
MDJ rEVOlution 2.3 rootfs.img
NexusHD2-FRG83D v1.8 from nzxtneo
Superram 1.5 from letama
Builds that already work with magldr:
DL DesireZ v2.2 from dandiest
HD2 Gingerbread/CyanogenMod7 from copenhagen
Is this a method to boot a NAND Rom from SD Card without flashing?
blax123 said:
Is this a method to boot a NAND Rom from SD Card without flashing?
Click to expand...
Click to collapse
No it boots the sd builds from this subforum. Not the nand builds.
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
izzy spun said:
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
Click to expand...
Click to collapse
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
buzz killington said:
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Click to expand...
Click to collapse
thanks.. so i must use linux? any tools available in win?
buzz killington said:
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Click to expand...
Click to collapse
can you elaborate on this please.
can you give a step by step.
i am real interested in trying this.
thanks in advance.
Anthonayy said:
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
Click to expand...
Click to collapse
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
vista1984 said:
thanks.. so i must use linux? any tools available in win?
Click to expand...
Click to collapse
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
WOOZ!E said:
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Dude, it has nothing to do with WP7, You boot Android from MAGLDR not WP7. So you would either use a different SD card to boot into Android BEFORE booting windows or you would partition your SD card in a way that it allows you to use it for WP7 and Android at same time.
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
asdfg2010 said:
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
Click to expand...
Click to collapse
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
buzz killington said:
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
Click to expand...
Click to collapse
I try but not successful
windows ext2 editing
buzz killington said:
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Click to expand...
Click to collapse
I think you can edit an ext2 image with windows using the method in post #4 from this thread: http://forum.xda-developers.com/showthread.php?t=808169
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
I've tried editing the file and it seemed to save the changes, but I haven't tried booting android yet.
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
can anyone uploade the files? i dont have linux..
Cool, thanks! I seems to be working for me with MDJ FroYo HD v4.6. Has anyone had any success getting two Android ROMs running from their microSD card? I was doing this when booting from WM6.5 by putting them in different directories and modifying rel_path in the startup.txt for one of them, but obviously this method won't work until MAGLDR supports startup.txt...
clio94 said:
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
I didn't do the superram built myself, but letama posted a full version later in that magldr thread. Try to see if you can find it. If not I'm sure I still have it somewhere I can post it for you.
You can change Android folder on SD using MAGLDR
Enter Magldr
Select 9. Services
then 1. BootSettings
then 3. AD SD Dir
*ALL THE USUAL DISCLAIMERS AND WARNINGS*
*THIS IS FOR VERSION 1.1 ONLY, DON’T TRY ON 1.0.0 OR 1.0.1*
Credit goes to: GabrialDestruir for the original auto-nooter, GLa’DOS for the boot animation, pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the “non-ugly” patch that is used to get androidID, mastapsi for testing and coding of the original auto-nooter, lewellyn for coding, [mbm] for ABI Fix, Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs and re-enable of ADB , Freenode's #nookcolor chat for code checking. A special thanks to all developers out there, without all of you this community would not be as great as it is.
Please Note: If you are the developer of an app that is included in this work, and would like me to remove it, feel free to contact me.
*I am copying the following step from the original auto-nooter, because they are tried and true, and people are already familiar with seeing them*
What it does:
Installs su and Superuser.apk
Installs Busybox with whoami
Installs Softkeys 3.0.6
Installs NookColor Tools (To Enable Non-Market Installs, and re-enable ADB)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Installs Gingerbread Keyboard
Enable ADB
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Known Problems:
With the version 1.1 update, ADB will not stay active after a reboot or unplug of the cable. To enable each time you want to use it, you will have to go into NookColor Tools /All Settings/Development/USB debugging, you will have to uncheck the box and then recheck it.
How to Use:
Before you begin:
* To update to 1.1 you must do a complete wipe.
* You must update to 1.1 to use Auto-Nooter 3.0.0 Instructions HERE.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: MultiUpload or MediaFire
*MD5 FB74865663B8D797A486A85022FAD9B2*
2 Linux: Unzip and use dd if=auto-nooter-3.0.0.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch, download the attached EVO HQ, and follow this code in adb
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb uninstall com.google.android.youtube
adb push YouTube.apk /system/app
adb reboot
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory ResetFactory Reset > Wipes /data
*You must do both of these to completely wipe clean your NOOKcolor.*
*Before anyone starts to say that I took this project away from GabrialDestruir, I posted this file in the original post, and sent the OP a PM asking to update the current project. I have yet to hear back, and the post was not updated. My post can be found HERE, dated February 2, 2011. I felt that this would be of a benefit to the community, so I am posting it now. If I am asked at some point to take it down I will do so at that time.*
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
I have never really seen an explanation as to why you don't format on the NC. I have formated via the NC and the card works fine both in the NC and my PC. When I want to burn an image, I have been able too. Been able to flash other images on it too.
Excellent!
Can you please add an MD5 to the first post?
Homer
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Formatting the SDcard doesn't touch the onboard storage. It is one of the easier ways to remove bonus partitions to recover the full card. UPDATE: I should clarify this: when running Eclair internally.
Homer
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
You're thinking of Nookie Froyo. The stock B&N system is fine for formatting the card.
I think formatting the SD card is an issue when you use one of the Froyo images and boot from eMMC. When you format the SD card it actually formats the internal boot partition or some such. I remember reading it in one of the threads which led me to only boot the Froyo images from an external card.
I am at 1.1.0. When did 1.1.1 appear & how do I get it?
BTW Is this exactly the same as the interim A-N 2.12.25 modified for 1.1?
k
I'd say it's a typo and should be v1.1?
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
also interested to know that!
And if there is benefits, can we use the auto nooter?
Just for clarification, in steps 3 & 4 should the NC be turned off? I have never been sure if it matters, but the following statement makes me think that it should be off,
"5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)"
Thanks,
kev
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Only with the froyo image.
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
The main difference I see is that Clockwork recovery is not involved.
johnny054 said:
also interested to know that!
And if there is benefits, can we use the auto nooter?
Click to expand...
Click to collapse
I guess it should be the same, but I had a couple of games break after up'ing with 1.1_r2. So I wanted to try stock/clean 1.1 and then root...hoping this would bring them back.
help please
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
brianf21 said:
Only with the froyo image.
Click to expand...
Click to collapse
Ok thanks for that clarification. I was pretty sure I read it somewhere!!
trentmaynard said:
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
Click to expand...
Click to collapse
You probably have a bad burn on the sdcard. Are you writing to the sdcard from the sd card reader or from the nook? Also, if you return to stock, (8 failed boots, then Power+N) You should be on firmware 1.0.0 or 1.0.1. Then root using one of the two original auto nooters, download rom manager from the market and flash the 1.1 pre-rooted firmware.
Thanks buddy, I try doing that. and I don't have an sd card reader so I just put the sd card that I'm going to write into my cell phone. then mount the sd card and write the img to the same storage device that represents the sd card. I'm sure this is the wrong way of doing it but I have gotten root doing the same thing before
Giving this a go now, coming from auto-nootered 1.0.1.
I've compiled a simple app to be able to easily mount to your PC any given partition.
Feel free to donate if this app is of any use to you. Much appreciated.
Please note that changes to the drive will not be saved if you do not properly unmount/eject the drive from PC (in Ubuntu: right click, unmount. In Windows, eject.).
For those using stock browser, apk files often fail to download.. You can install Astro explorer and activate downloads in settings (last option). Then you should be able to download this file.
Dolphin should work without issues..
This is a Beta release.
This requires a working root (su). By that I mean your nook must be rooted. Regarding HC, see j4mm3r's thread.
This can be used, for example, to open your SD or internal data on your PC..
You can mount pretty much any partition to your computer with this app:
- SD
- Media (internal drive for your media and documents...)
- SD Partitions (up to 4)
- Internal storage - BE VERY CAREFUL WITH THIS!!
There are two "mount points" on the nook (lun0 and lun1)
So you can simultanously mount two partitons.
As an example, you can mount SD on 1st and MEDIA on the 2nd.
Each mount point has it's own tab.
Please try it out and post feedback.
Thank you.
EDIT (13.02.2011):
This has been tested on HoneyComb and Froyo (not in Eclair 1.0>1.1).
In Froyo: USB Mass Storage (Notification bar) should be turned off.
Compatibility mode will need to be disabled in Spare parts (reboot required).
If this doesn't work for you, try entering manually in ADB while NC plugged in to your PC:
Code:
adb shell
echo /dev/block/mmcblk0p8 > /sys/devices/platform/usb_mass_storage/lun0/file
And post result here.
Sam
----------------
UPDATES:
13-02-2011: 0.2b => minor bugs and made app scrollable for Froyo Landscape
26-02-2011: 0.3b:
- Changed 'settings' label (mistake) to system.
- Added a "Make sure you properly unmount/eject drive from PC when finished" message when mounting.
- Added dual boot system and data (p9 and p10).
- Changed 'Confirm mounting' to 'Confirm', as poster suggested. Thanks.
--------------
Hmm can't quite seen to get it to work right. The app does nothing for me when I select a partition to mount. I can get the SD card mounted via android's USB connected notification. I've tried the app with it turned on and off. It's got super user, so that's not it. By the way, I'm running Froyo 6.7 off the eMMC. Let me know what to try.
EDIT: Got it to work after running the ADB command in 1st post. Awesome app, thanks.
Sam,
Thank You, you program made my day. It works great, I have been messing with vold.fstab for days and I could only mount the boot of my sdcard. So, I went with manually pushing file to /sys/devices/platform/usb_mass_storage/luno/file which worked but your app make the process much better.
Again Thank you for everything you have done.
Biz
Could this work as a Xbox media storage? I want to get a new demo, and I got no Hard Drive
Works great!
this is great! i was thinking (since your help in the other thread) about trying to cobble something like this together myself in android app creator suite but didnt know if i could manage or not. Now i dont need to even try! thank!
EDIT: 2 things, one, is it possible to have this setting survive a reboot? and secondly, is the display supposed to be tiny? it only fills like a third of the screen and is centered at the top. this is on emmc froyo 0.6.7 the screen is scrollable as you said so just have to scroll down for the confirmed button
Does it unmount them on the nook when they are attached to the PC? I was playing with the echo command and it seems that the nook is unable to see any changes to the filesystem. I wrote a script that unmount them then runs the echo statement. Then another script that remount them once they are disconnected.
Good question. As I said, this is beta. I'm open to any suggestion. From what I tested, changes did actually occur even when mounted on android..
Unchecked compatibility mode in spare parts and reboot for fullscreen..
Sent from my HTC Desire using XDA App
samuelhalff said:
Good question. As I said, this is beta. I'm open to any suggestion. From what I tested, changes did actually occur even when mounted on android..
Unchecked compatibility mode in spare parts and reboot for fullscreen..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
you did say that huh... sorry
This provided an easier way to fix root (SU binary) to make SuperUser work again on HC.
Glad it helped.
Over 100 downloads and very few feedbacks...
Sam
Sent from my HTC Desire using XDA App
samuelhalff said:
Over 100 downloads and very few feedbacks...
Click to expand...
Click to collapse
Interesting. I did see that if you try to download / install directly from the HC browser it doesn't work. Perhaps people do this instead of trying with their computer and assume it doesn't work? Downloads don't equal successful installs.
For Windows users, it (currently) provides the only way to mount the 4th partition of my HC SD card. Am I mistaken? Perhaps others don't realize what this is or are put off by the UI?
Keep it up. This is a much needed utility ATM.
The UI isn't THAT awful, is it?
Anyway, this can help a lot of people, especially the ones not too familiar with ADB..
Sam
Sent from my HTC Desire using XDA App
samuelhalff said:
The UI isn't THAT awful, is it?
Anyway, this can help a lot of people, especially the ones not too familiar with ADB.
Click to expand...
Click to collapse
To a person familar with partitions and the android file system it's fine. To those expecting a more fruity / friendly UI, it's far from it. However, you can't please everyone and it might be a waste of your energy to try. It's practical / functional and that's all I need it to be.
Indeed it can, much preferred over ADB even though I can use it just fine. You might want to make it more clear in the OP that users that have problems may need to type "adb shell" before the echo command. Not everyone will know this.
You app works well Sam! I can finally access my media partition via USB. I am looking forward to updates. Perhaps retaining setting after a reboot? Great work man!
Works great! I downloaded it with dolphin browser (running froyo on emmc) Then used root explorer to navigate to downloads and just clicked to install. Doesn't get any easier than that!
Would it be possible to have it mount media partitions? Like if I have dual boot setup would it be possible to mount the extra partitions to edit them?
Which media partitions?
Right, forgot about dual booters.. I'll implement that in 0.3..
Thanks.
Sent from my HTC Desire using XDA App
I want to thank you so much for this samuelhalff. I mean it. Something like this that may seem trivial to someone who can just do it means a WORLD to someone like me and i truly truly appreciate it. The devs/peeps here have made my little wanna be ereader ((hehe)) a great honeycomb tablet. I think its great for someone that cant afford the next great thing **xoom** to be able to join in the tech fun. You all have made me very happy with my little tablet.
Jamie.
Love the app!!!! but i got a issue now... There is no way for me to browse the media partition on the device... so I can not access my pictures that I placed on the internal storage...any insight?
Working great for me, HC on eMMC. Appreciate it!
Just a quick note for anyone strolling in. I am still supporting this modification. If you have any questions or comments, please feel free to post.
Hello everyone. Hopefully this hasn't been done before. This mod is a bit more of a fun one (In my humble opinion ).
You may have noticed that when you connect your phone up to a computer, while booted into a Sense-based ROM, the phone will mount two drives -- one being a mass storage device, and the other being a CD-ROM drive. Interestingly enough, when you select HTC Sync Manager from the USB connection type list, it makes the computer think that you inserted a CD-ROM.
That's interesting because that means that you could essentially hook the phone up to just about any computer, and it would recognize that "CD-ROM drive."
Click to expand...
Click to collapse
Background
I found that you can actually change that CD-ROM to just about anything you could possibly want (having some trouble with bootable ISOs though).
There is a file named PCTOOL.ISO inside the /system/etc directory that normally contains the HTC Sync Manager Software. By replacing that ISO with another, it'll mount that one instead. Because there isn't too much room to spare in the /system partition, the file should probably be kept relatively small.
Click to expand...
Click to collapse
Okay. Why does this matter? I can think of two reasons:
1. ROM Developers can include a package that contains a copy of the ADB and Fastboot executables within their ROM. ADB would be useful while the device is on; Fastboot would probably have to be copied to the computer.
2. Because the ISO is mounted as Read-Only media, it could be incredibly useful for field technicians who need to run portable software, without the risk of being infected with a virus on the host machine.
Click to expand...
Click to collapse
Info/Download
It's not hard to create these ISOs, and flash them to the phone. I can put up a how-to in the second post if anybody would like me to.
For now, here's a flashable zip containing ADB and Fastboot executables for Windows, Linux, and Mac OS X.
Just flash the file like you would flash any other.
There is an old version of the PCSC.apk in this file. A newer version is here for the time being.
Download
Click to expand...
Click to collapse
How to use
To use it, while booted, change the device-connection type to HTC Sync Manager. Tap 'Done'. You'll likely see a message on the phone that says "Connecting to HTC Sync Manager ..." Just tap the back button on your phone to clear that message.
On your computer:
If you're running Windows, you may get an AutoPlay window that gives you the option to launch the "ADB and Fastboot Command Prompt." If you click that, you'll get a Command Prompt Window that's pointed at the drive already. To use any of the commands, just type adb [COMMAND], or fastboot [COMMAND] (again, fastboot may be useless unless copied to the computer).
If you don't get an AutoPlay window, open up the CD-ROM drive, and double-click on the 'ADB_FASTBOOT_SHELL.BAT' icon to bring up the window. That batch file contains only one command (just to launch the Command Prompt to the CD location).
If you're running Linux, you may have to copy the binaries over to your computer to use them (they may not have correct permissions).
On Mac OS X, you'll likely have to open a terminal window and navigate to the CD-ROM drive to use them.
Click to expand...
Click to collapse
I know that this isn't anything huge, but I'll put this down here anyways. Developers, if you are interested in the ADB/Fastboot ISO or flashable ZIP, and would like to include it in your ROM, please feel free to do so. Modify it however you like. Only thing that I would ask of you is that you post here (or even PM me) saying that you used it. I'd just love to see if/where it's being used. This isn't a strict requirement though. Thanks!
Disclaimer: I am not responsible for anything that happens (including, but not limited) to your phone, computer, Sprint contract, etc. This is provided free of charge without any warranty.
Reserved
This is extremely interesting to me my friend. I ordered a 64gb sd so i could store pc repair programs such as hiren or others. So i woild always have with me. If i could just load a iso. God that would kick but. Id have a few o.s so ready at all times lol
Sent from my ice cream powered Evo Lte!
I definitely like the idea and possibilities this has. Good find, Closeone! I am goin to download just to keep for future. As I am only rooted stock, but I do plan to unlock soon. Was waiting on s-off but doubt that'll happen anytime soon, being that u can still flash kernels n etc with just unlocked bootloader.
Sent from my LTEVO via Tapatapa
When I connect my EVO to my PC running Windows 7 64 bit , it doesn't recognize it as MTP (Thank God, by the way....IMO), it mounts as a normal USB flash drive. I didn't install HTC Sync, so I am not sure if that has anything to do with it.
Are you referring to bone stock and you click on the Disk drive icon or the HTC Sync Manager when you plug in?
Just curious if I am using drivers that maybe others might get use of...
kaos420 said:
This is extremely interesting to me my friend. I ordered a 64gb sd so i could store pc repair programs such as hiren or others. So i woild always have with me. If i could just load a iso. God that would kick but. Id have a few o.s so ready at all times lol
Click to expand...
Click to collapse
Thanks! I'm not sure about the ability to boot. I did try a bootable ISO, which unfortunately was unable to boot. I may have to look closer into this. Also, the size restriction might hold you back. I wouldn't load a huge ISO into the /system partition, but there is one of two different things might be able to be done. One would be to possibly symlink the ISO and have it load from another place, the second would be to modify where the software would load the ISO from. Humm...
drewski83 said:
I definitely like the idea and possibilities this has. Good find, Closeone! I am goin to download just to keep for future. As I am only rooted stock, but I do plan to unlock soon. Was waiting on s-off but doubt that'll happen anytime soon, being that u can still flash kernels n etc with just unlocked bootloader.
Click to expand...
Click to collapse
Thanks, drewski83!
pinky059 said:
When I connect my EVO to my PC running Windows 7 64 bit , it doesn't recognize it as MTP (Thank God, by the way....IMO), it mounts as a normal USB flash drive. I didn't install HTC Sync, so I am not sure if that has anything to do with it.
Are you referring to bone stock and you click on the Disk drive icon or the HTC Sync Manager when you plug in?
Just curious if I am using drivers that maybe others might get use of...
Click to expand...
Click to collapse
The only way, I believe, that the system will mount the phone as MTP (or is it PTP in this implementation?) is by selecting the Media sync option when connecting. The two advantages I see to mounting it this way are that the SD Card doesn't have to be dismounted while connected, and the device shows both the "Internal SD" and the actual SD Card as separate drives that you can copy files to and from.
I haven't installed HTC Sync either. I'm referring to most any Sense-based ROMs for this device. If the phone doesn't give you a choice, it's possible that it's still hidden in the notification menu. If not, you can change that by going into Settings > Connect to PC, and tap Ask me, or you can change the default connection type from within that menu as well.
~co~
Closeone, you are awesome.
-Cupper- said:
Closeone, you are awesome.
Click to expand...
Click to collapse
Thank you -Cupper-. You are awesome, good sir!
~co~
bump for awesomeness
Quick question...if you flash this mod, do you have to reflash it every time a new ROM is flashed? Thanks in advance
bard77 said:
Quick question...if you flash this mod, do you have to reflash it every time a new ROM is flashed? Thanks in advance
Click to expand...
Click to collapse
Hi bard77. Yes. When you flash a new ROM, system data will (should) typically be wiped. This is written there. It's simple to flash however.
Thanks,
~co~
good stuff!! thanks
Just freakin' sweetness man. Pure epic find!
Sent from my EVO using Tapatalk 2
Androidious said:
Just freakin' sweetness man. Pure epic find!
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Agreed, nice work closeone. This is amazing.
evo401 said:
good stuff!! thanks
Click to expand...
Click to collapse
Androidious said:
Just freakin' sweetness man. Pure epic find!
Click to expand...
Click to collapse
regaw_leinad said:
Agreed, nice work closeone. This is amazing.
Click to expand...
Click to collapse
Thanks guys.
~co~
Closeone, good job on finding this!
I do computer repair, and I currently have an external 2.5" drive set up to be bootable to a Grub bootloader. From Grub, I can boot any ISO or boot partition on the drive. With the Sync Manager emulating a CD-ROM drive instead of showing up as a disk drive, it would be a huge advantage for booting, letting any computer (especially older ones) recognize it.
If you could find a way to keep the phone in Sync Manager even when it's not connected, the computer's BIOS should be able to see it as a CD-ROM and boot from it. As it is now, my BIOS won't see it because it's not treating the phone like a USB device. It would be excellent if you could map to an ISO on a different partition. Another option is to have the loaded ISO simply bring up a bootloader to boot from any ISO/partition you want, though this takes away the advantage of the selected ISOs being recognized as a CD-ROM drive. Grub can have problems when you boot from an ISO of a live CD and the booted OS needs to access the disc. The OS can't find a CD-ROM, so it doesn't work.
If you could successfully map this to an ISO on the SD card, you could even build a little app to let you choose which ISO you want to be selected. You could simply have it remap to the different folders with the respective PCTOOL.ISO files. For example, if you select "Acronis" from the app menu, it would direct it to sdcard/acronis/PCTOOL.ISO, and if you select "Ubuntu," it would map to /sdcard/Ubuntu/PCTOOL.ISO.
I hope this is all clear enough. Once I read this, I got pretty excited about all the possibilities!
This is going to be awesome if things can be modified to make this a bootloader. I would even donate for this functionality if someone wanted to tackle it.
Having the ability to have things like UBCD, Win XP PE (With Antivirus / MalwareBytes), etc as options running straight from my phone would be a computer guy's dream.
jamiphar said:
Closeone, good job on finding this!
I do computer repair, and I currently have an external 2.5" drive set up to be bootable to a Grub bootloader. From Grub, I can boot any ISO or boot partition on the drive. With the Sync Manager emulating a CD-ROM drive instead of showing up as a disk drive, it would be a huge advantage for booting, letting any computer (especially older ones) recognize it.
If you could find a way to keep the phone in Sync Manager even when it's not connected, the computer's BIOS should be able to see it as a CD-ROM and boot from it. As it is now, my BIOS won't see it because it's not treating the phone like a USB device. It would be excellent if you could map to an ISO on a different partition. Another option is to have the loaded ISO simply bring up a bootloader to boot from any ISO/partition you want, though this takes away the advantage of the selected ISOs being recognized as a CD-ROM drive. Grub can have problems when you boot from an ISO of a live CD and the booted OS needs to access the disc. The OS can't find a CD-ROM, so it doesn't work.
If you could successfully map this to an ISO on the SD card, you could even build a little app to let you choose which ISO you want to be selected. You could simply have it remap to the different folders with the respective PCTOOL.ISO files. For example, if you select "Acronis" from the app menu, it would direct it to sdcard/acronis/PCTOOL.ISO, and if you select "Ubuntu," it would map to /sdcard/Ubuntu/PCTOOL.ISO.
I hope this is all clear enough. Once I read this, I got pretty excited about all the possibilities!
Click to expand...
Click to collapse
webdude12 said:
This is going to be awesome if things can be modified to make this a bootloader. I would even donate for this functionality if someone wanted to tackle it.
Having the ability to have things like UBCD, Win XP PE (With Antivirus / MalwareBytes), etc as options running straight from my phone would be a computer guy's dream.
Click to expand...
Click to collapse
Apologies for my late response. I've been... tied up for the last couple weeks.
Thanks. Precisely. I thought that it would be a nice tool for technicians. I work in that field myself. There are a few problems that I noticed with how the PCTOOL.ISO is accessed. From my understanding, I believe that the problem with reading it from the SD Card (Internal Memory or External) is that it doesn't expect that it's going to be reading from a FAT32 formatted partition. It gets a bit more difficult with the fact that a huge ISO really probably shouldn't be placed in your system partition. Making it bootable is messy (I mean, it was intended for a completely different use in the first place though ). At the very least, an ISO with your favorite portable applications can be put in there and loaded up when needed. That alone is very valuable because it acts as read-only media, the phone can't be infected with anything nasty from the computer you plug it into.
Thanks again!
~co~
Why could we not partition a section of the SD card as EXT3 or whatever PCTOOL.ISO wants to see, then create a symalink as mentioned? Nothing says the entire SD card has to be partitioned FAT32. I actually had part of mine partitioned as EXT2 for the longest time, because the card wasnt always in my phone.
webdude12 said:
Why could we not partition a section of the SD card as EXT3 or whatever PCTOOL.ISO wants to see, then create a symalink as mentioned? Nothing says the entire SD card has to be partitioned FAT32. I actually had part of mine partitioned as EXT2 for the longest time, because the card wasnt always in my phone.
Click to expand...
Click to collapse
True. True. I didn't think about that. The first thing that's got to be done though is making the phone mount the ISO, or at least not wait for a request from the computer to go ahead and make the phone pop up with the menu of actions, and in turn say to the computer "Hi there, I see that you're booting. I'm a USB CD-ROM drive. Oh yeah, and you can boot from me now." Easier said than done, at least for myself.
~co~
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.