New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
muyan
Old
(Last edited by muyan; 6th September 2009 at 04:05 PM.) Reason: More info
#1  
Junior Member - OP
Thanks Meter 0
Posts: 15
Join Date: Jan 2007
Default No SD Card/USB, execept from bootloader (kernel boots: board_hero.disable_sdcard=1)

Major problem as a result of an unsuccessful attempt to permanently installing the recovery image.
The result is that Android now reports that the SD card is not present (I've tried 3 different cards), and the USB mode allowing adb is no longer available – the USB interface is not recognised (except from the bootloader).

I can flash stock firmwares from my SD card using Hboot or from RUU packages using USB by manually booting the bootloader, thus the interfaces themselves are working.
I have attempted to clean wipe the entire device, updating/downgrading and even installing the newest 2.73.405.5 ROM did not resolve this issue.

I have not found anyone reporting the same problem. I am running out of ideas and could really need some help/advice on how to resolve this. Especially if someone have a better understanding of how android is booted and how the symlinks and devices are created. I am a long time Linux user, but without the ability to use the recovery image/adb, USB or SD card to patch or inspect I am currently experiencing some difficulty investigating this further.

Update:
I've done some more digging and I think I have found the problem, however I don't know how to correct it.
Dmesg shows my kernel command as:
board_hero.disable_uart3=1 board_hero.usb_h2w_sw=1 board_hero.disable_sdcard=1 smisize=32 androidboot.baseband=6.35.06.18 androidboot.cid=HTC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=HERO10000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT97ML906986 androidboot.bootloader=1.76.0007 no_console_suspend=1 console=null

it also lists:
trout: SD-Card interface disabled

and as a result /dev/block/vold/179:1 is never created and not mounted.

Is there a way to correct the kernel command line, or do I need to wait for a S-OFF Hboot firmware to have possibly correct this?
 
Reso9
Old
#2  
Member
Thanks Meter 0
Posts: 35
Join Date: Jan 2007
Same problem here. Nobody who knows how to solve this???
 
packetlss
Old
#3  
packetlss's Avatar
Senior Member
Thanks Meter 6
Posts: 220
Join Date: Aug 2009
Can you still boot images using fastboot?

like: fastboot boot <recovery-image-name>

Also, which HBOOT version does it display?
 
Reso9
Old
#4  
Member
Thanks Meter 0
Posts: 35
Join Date: Jan 2007
Quote:
Originally Posted by packetlss View Post
Can you still boot images using fastboot?

like: fastboot boot <recovery-image-name>

Also, which HBOOT version does it display?
It's showing HBOOT version 1.76.0004

I can still boot a recovery image but when i selcet update.zip, any zip or nanroid backup it's saying "Can't mount sdcard".

Another very big problem is that the device can't read any sd cards even when i have booted android normaly. It's always showing that no sd card is plugged in.
 
packetlss
Old
#5  
packetlss's Avatar
Senior Member
Thanks Meter 6
Posts: 220
Join Date: Aug 2009
Really strange. Your cmdline say HBOOT is 1.76.0007 and your bootscreen 1.76.0004.

You can alter the commandline from fastboot though.

Try something like this:
fastboot -c "board_hero.disable_uart3=0 board_hero.usb_h2w_sw=0 board_hero.disable_sdcard=0 no_console_suspend=1 console=null" boot cm-hero-recovery.img

It only appends to the commandline though, but it's worth a shot.

For reference I give you my full booted cmdline if it is of any use.

# cat /proc/cmdline
board_hero.disable_uart3=0 board_hero.usb_h2w_sw=0 board_hero.disable_sdcard=0 smisize=32 androidboot.baseband=6.35.06.18 androidboot.cid=HTC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=HERO10000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT<removed> androidboot.bootloader=1.76.0004 no_console_suspend=1 console=null

I'm pretty sure there is some way to configure the HBOOT, do you remember want exactly went wrong/what you did when flashing the recovery?
 
Reso9
Old
(Last edited by Reso9; 11th September 2009 at 08:57 AM.)
#6  
Member
Thanks Meter 0
Posts: 35
Join Date: Jan 2007
Thanks for your help but i have maked a big mistake in the meantime. I have flashed the new rom with ruu. Now it' showing HBOOT 1.76.0007 and i can't load the recovery image. Still it's showing me that there is no sd card.

The commandline that you have written doesn't works because of this. Nothing with fastboot works at the moment becouse of HBOOT 1.76.0007.

Do you know how to get back to 1.76.0004 or how to load fastboot with HBOOT 1.76.0007???

Edit: I have just saw your answer on the other post. I will give it a try. Thanks for your help.
 
Reso9
Old
#7  
Member
Thanks Meter 0
Posts: 35
Join Date: Jan 2007
It isn't possible to flash the old HBOOT because i can't access the sd card. Is there a way to enable the sd card without recovery or is there a way to flash the old HBOOT without sd card???
 
paulobrien
Old
#8  
paulobrien's Avatar
Senior Member
Thanks Meter 5337
Posts: 4,419
Join Date: Nov 2003
Location: Norwich
So can the recovery flasher APK not flash without a SD card?

If not, how about tricking it into thinking the sdcard (when booted up) is there by mounting /data then symlinking /sdcard to a dir on /data?

P
Follow me on Twitter - http://twitter.com/paulobrien

Follow MoDaCo Android on Twitter - http://twitter.com/modaco

Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

 
Reso9
Old
#9  
Member
Thanks Meter 0
Posts: 35
Join Date: Jan 2007
I don't know if i can flash the apk recover without sd card. That's why i am asking for how to make this.
How can i trick on booting up? Do you know where i can find a tutorial or something like that?
Can you help me please?
I'am a newbee on android just changed from winmo.
 
Reso9
Old
#10  
Member
Thanks Meter 0
Posts: 35
Join Date: Jan 2007
Quote:
Originally Posted by modaco View Post
If not, how about tricking it into thinking the sdcard (when booted up) is there by mounting /data then symlinking /sdcard to a dir on /data?

P
Can anbody tell me how to do this?


XDA PORTAL POSTS

Avoid Framework Bootloops on Xperias Running Jelly Bean

If you’re a Sony device owner running a stock Android Jelly Bean firmware and … more

Forum Added for the Samsung Galaxy Mega

What do you do when the Galaxy Note line is simply not big enough? You get theSamsung Galaxy Mega. … more

Voice Control Your Phone with Tasker and AutoVoice – XDA Developer TV

XDA Developer TV Producer Kevin set up his phone to respond to … more

Guide to Take Better Control of Your Volume Levels

Would you like to know one of the things that really annoys me on a daily basis? Tough, … more