Guest Xeronage Posted April 29, 2010 Report Posted April 29, 2010 (edited) That sounds great. Does the SD card needs to be empty / just FAT32 formatted in order to achieve that? I just used the 4GB SDHC that came with my Desire, formatted FAT32 (Can I switch to EXT3 after rooting?). All the goldcard is, is that the first 180 bytes of your sdcard are filled in by the goldcard. It makes your SD unbootable (I think) but doesn't affect partitions. Besides this a goldcard does not differ from a regular card. Feel free to use it for all your storage needs. You don't even have to format it to turn it into a goldcard either. Edited April 29, 2010 by Xeronage
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 I've just had it set to 0 for swap, 768 for ext2 and the rest for fat32 You're all good, just reboot now.
Guest kingoffail Posted April 29, 2010 Report Posted April 29, 2010 What systems are you using and have you tried disconnecting it, rebooting it, and then connecting it again? Yes, I have tried rebooting the phone. Paul's tinycore in VMWare and also Arch Linux x86_64 running natively. I should note that this worked fine before I tried to install apps2sd, which totally broke everything. I was under the impression that reflashing would wipe everything, undoing whatever it was that apps2sd did. Is that not the case?
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 Yes, I have tried rebooting the phone. Paul's tinycore in VMWare and also Arch Linux x86_64 running natively. I should note that this worked fine before I tried to install apps2sd, which totally broke everything. I was under the impression that reflashing would wipe everything, undoing whatever it was that apps2sd did. Is that not the case? Reflashing wipes app2sd. What steps did you perform to install app2sd?
Guest Elemetrix Posted April 29, 2010 Report Posted April 29, 2010 You're all good, just reboot now. thanks, what is the difference between ext2,3,4? why are people asking to switch to ext3?
Guest theboxman Posted April 29, 2010 Report Posted April 29, 2010 (edited) instead of calling qemu with: -cdrom current.iso you could use: -cdrom *.iso so the name is ininfluent... the problem is, instead, that usb support on windows compiled binaries is not always present or functional... tried 3 different build of qemu... for language, it was repeated 2 o 3 times: rom includes french, german and english, plus a language that is different from country to country, and linked to the sim card inserted... so, spanish for you, italian for me :-) @MrShark: yeh I was being lazy as my original installation of QEMU had six or seven ISO's sitting around in the folder - complicated arrangement! I've uploaded my version of QEMU here however, as I don't have the necessary files from Pauls end yet I can't test it over here to see if it works correctly yet. I'm fairly sure I've used USB devices with this version before. Anyway it's only 3Mb ish! @MrShark: Yes I read that there was no spanish in the ROM and you'd get another one from your SIM and given your sim was italian you got italian.....My sim's from the UK hence I've no confidence whatsoever that I'll end up with spanish if it's not on the original ROM..... Looks like I won't get to do this until a new ROM becomes available. :-{ Best of luck with this file all, I hope this file works! Let me know!QEMU.zip Edited April 29, 2010 by theboxman
Guest kingoffail Posted April 29, 2010 Report Posted April 29, 2010 (edited) Reflashing wipes app2sd. What steps did you perform to install app2sd? Copy zip onto goldcard, recovery-linux.sh, update. I've just discovered that I can get the phone to appear as a usb device if I make sure it's unplugged from the computer UNTIL the screen with the red triangle appears. lsusb then has this to say: Bus 002 Device 045: ID 05c6:9002 Qualcomm, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x05c6 Qualcomm, Inc. idProduct 0x9002 bcdDevice 0.00 iManufacturer 3 Qualcomm, Incorporated iProduct 2 Qualcomm CDMA Technologies MSM iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 85 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 1 Qualcomm Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0001 Self Powered [/codebox] adb still doesn't work though. Edited April 29, 2010 by kingoffail
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 thanks, what is the difference between ext2,3,4? why are people asking to switch to ext3? Stability.
Guest spocky Posted April 29, 2010 Report Posted April 29, 2010 Hi everybody (and thanks paul for what you're doing for us). I think I need you help. I followed the tutorial exactly but I had an error during flash : Image has been uploaded to the phone, then a had a bunch of : INFOzip header checking INFOzip info parsing INFOchecking model ID... [....] INFO[RUU@WP,radio,0 INFO[RUU@WP,radio,6 INFO[RUU@WP,radio,14 INFO[RUU@WP,radio,19 INFO[RUU@WP,radio,27 INFO[RUU@WP,radio,36 INFO[RUU@WP,radio,44 INFO[RUU@WP,radio,51 INFO[RUU@WP,radio,59 INFO[RUU@WP,radio,100 FAILED (remote:90 hboot pre-update! please flush image again immediately) <waiting for device> Does anybody here know what I should do (I'm afraid of bricking my device if I unplug / reset it) Thanks for any information that could help me...
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 Copy zip onto goldcard, recovery-linux.sh, update. I've just discovered that I can get the phone to appear as a usb device if I make sure it's unplugged from the computer UNTIL the screen with the red triangle appears. lsusb then has this to say: Bus 002 Device 045: ID 05c6:9002 Qualcomm, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x05c6 Qualcomm, Inc. idProduct 0x9002 bcdDevice 0.00 iManufacturer 3 Qualcomm, Incorporated iProduct 2 Qualcomm CDMA Technologies MSM iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 85 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 1 Qualcomm Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0001 Self Powered [/codebox] adb still doesn't work though. Does ADB still give an error or did it change?
Guest kingoffail Posted April 29, 2010 Report Posted April 29, 2010 Does ADB still give an error or did it change? Still gives an error. adb devices shows no attached devices.
Guest ascito Posted April 29, 2010 Report Posted April 29, 2010 Trying to root it with Sun VirtualBox, after first command line, it stucks in "waiting for Device"...how to get rid of it and go on?
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 Still gives an error. adb devices shows no attached devices. Where did you run lsusb under? Your VM or your Arch Linux?
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 Trying to root it with Sun VirtualBox, after first command line, it stucks in "waiting for Device"...how to get rid of it and go on? I saw people having problems with VirtualBox. Did you mount your phone to the VM?
Guest kingoffail Posted April 29, 2010 Report Posted April 29, 2010 Where did you run lsusb under? Your VM or your Arch Linux? My Arch Linux (same place I ran adb under). Tried the same thing in the VM, same result.
Guest Elemetrix Posted April 29, 2010 Report Posted April 29, 2010 Hmm.. why do I only have 80MB phone memory now? Also since installing apps2SD 'SuperUser Permissions' doesn't show as an installed app.
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 My Arch Linux (same place I ran adb under). Tried the same thing in the VM, same result. What steps do you perform to get to the red triangle? (Volume Down + Power and then selecting recovery?)
Guest kingoffail Posted April 29, 2010 Report Posted April 29, 2010 What steps do you perform to get to the red triangle? (Volume Down + Power and then selecting recovery?) Yup - volume down, power, recovery.
Guest d.code Posted April 29, 2010 Report Posted April 29, 2010 Does the ./recovery-linux.sh work with the image posted on post 1? After rooting, if I want to apply A2SD how can I do it via the TinyCore?
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 Yup - volume down, power, recovery. Try disconnecting your phone, turning it off, rebooting in recovery mode and then connecting it again.. Make sure you mount your phone to the VM (Never used Arch Linux tho, can't tell you how hehe) Also i used the traditional method of rooting, not the iso.
Guest Xeronage Posted April 29, 2010 Report Posted April 29, 2010 (edited) Stability. Ext2 does not have journalling Ext3 has journalling Ext4 is faster, has better journalling, but is new and *might* glitch. And for those using VirtualBox. To use USB add yourself to the 'vboxusers' group and logout and back in. Now you can add the device ID to the list of USB hooks or re-add it everytime it reconnects itself. I've rooted mine using VirtualBox (Proprietary) with the TinyCore image under Ubuntu. Edited April 29, 2010 by Xeronage
Guest BeRtjh Posted April 29, 2010 Report Posted April 29, 2010 I was at 80MB before installing anything. That icon is not there. It was there earlier after the first root flash but not since the apps2sd flash :-/ Did you flash app2sd with your GoldCard?
Guest gregDT Posted April 29, 2010 Report Posted April 29, 2010 Sorry for the delay in posting a reply. If you install A2SD and partition an SD card you obviously have to stick with that card or you loose all your apps. However the first thing you should install after getting root and installing A2SD is Titanium Backup and pay for the full version. Now you can make a complete backup of your apps. Now copy the backup off the SD card to a PC. Partition the new SD card, copy the backup to the new SD card and finally re-install Titanium and restore all your apps. Sorted :huh:
Guest afiorillo Posted April 29, 2010 Report Posted April 29, 2010 Ext2 does not have journalling Ext3 has journalling Ext4 is faster, has better journalling, but is new and *might* glitch. And for those using VirtualBox. To use USB add yourself to the 'vboxusers' group and logout and back in. Now you can add the device ID to the list of USB hooks or re-add it everytime it reconnects itself. I've rooted mine using VirtualBox (Proprietary) with the TinyCore image under Ubuntu. As far as you know, converting ext2 to ext3 will wipe the partition?
Guest Elemetrix Posted April 29, 2010 Report Posted April 29, 2010 Did you flash app2sd with your GoldCard? Yes. goldcard stayed in up until I needed to partition the bigger card.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now