Related
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?
Same problem here. Nobody who knows how to solve this???
Can you still boot images using fastboot?
like: fastboot boot <recovery-image-name>
Also, which HBOOT version does it display?
packetlss said:
Can you still boot images using fastboot?
like: fastboot boot <recovery-image-name>
Also, which HBOOT version does it display?
Click to expand...
Click to collapse
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.
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?
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.
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???
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
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.
modaco said:
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
Click to expand...
Click to collapse
Can anbody tell me how to do this?
I think I have the same problems.
See this thread: http://forum.xda-developers.com/showthread.php?p=4547286
I can't use USB during normal Hero operation (so no option to mount SD card).
I can't use adb. If I do adb devices adb returns with none.
The 2 above are in conjunction with Windows (7 x64, but with correct drivers, it worked before) not recognizing the usb device.
I CAN however go into bootloader (power+back button) and use the fastboot command.
So what I do to flash stuff is physically pulling the sd card from my phone and putting it in my pc (via adapter of course) , copying the necessary files onto sd card and then putting the card back into the phone.
What I still want to try is flashing Amon Ra's recovery permanently and therefore you have to use a adb shell command (adb shell flash_image recovery /sdcard/Recovery-RA-HERO-v1.2.2.img).
I will try to use a terminal on the Hero itself (Better Terminal Emulator Pro) for this command or otherwise use the program FlashRec.apk, thus circumventing the need for adb at all I hope.
I have the same problem, It was working perfectly, then all of a sudden the computers wouldnt recognize the phone anymore (Unrecognized USB). I was speaking to HTC about it who told me to send the unit back for service/repair.
I will send it back to HTC tomorrow and it will take about 2-3 weeks till I get it back again. I will post a report here on what they did to it.
USB Brick and brick sdcard, please help
Hi
Maybe giving a bit more detail about what happened to get the usb/sd bricked would help people to reply you
My device is connected to the PC does not recognize the Android and the recovery. currently no driver error: "Qualcomm CDMA Technologies MSM"
(Sorry for my English which should not be used goolge translate)
Do you have ROOT??
I unbricked my Desire yesterday so I know how to do it (only with ROOT).
Just download the correct RUU for your region from one of the post in this forum. Connect the USB cable, run the RUU exe and it flash your phone back to the OTA ROM.
I was put on the original room and then proceed boot, successfully run the STEP1, STEP2, but to the error can not enter the recovery
yolkie said:
Just download the correct RUU for your region from one of the post in this forum. Connect the USB cable, run the RUU exe and it flash your phone back to the OTA ROM.
Click to expand...
Click to collapse
Rom I downloaded OTA and it still can not root, and do not receive equipment, including sdcard
Maybe have a look here: (good q+a)
http://forum.xda-developers.com/showthread.php?t=749551
edit: also to this usb brick fix:
http://forum.xda-developers.com/showthread.php?t=691639
with kind regards..Alex
yolkie said:
Just download the correct RUU for your region from one of the post in this forum. Connect the USB cable, run the RUU exe and it flash your phone back to the OTA ROM.
Click to expand...
Click to collapse
His computer don't have connection with phone. It's BRICK, so how he can use RUU?????
lanh_lung do you have ROOT(modified recovery)???
edit: also to this usb brick fix:
http://forum.xda-developers.com/showthread.php?t=691639
with kind regards..Alex[/QUOTE]
My Desire is: T-Mobile have to follow steps on it?
lanh_lung said:
edit: also to this usb brick fix:
http://forum.xda-developers.com/showthread.php?t=691639
with kind regards..Alex
Click to expand...
Click to collapse
My Desire is: T-Mobile have to follow steps on it?[/QUOTE]
Champion ... no matter if your Desire is or not operator ...
Had the same problem and I was able to retrieve the roles of USB and SD Card making the procedures described in the tutorial past links above ...
Read carefully and make with calm ...You'll see that it is not as difficult as it sounds!
Good luck!
lanh_lung do you have ROOT(modified recovery)???[/QUOTE]
step2 I can not run because of the driver error: "Qualcomm CDMA Technologies MSM"
lanh_lung said:
USB Brick and brick sdcard, please help
Click to expand...
Click to collapse
it's very strange, I have exactly the same problem since yesterday!
SD Card brick is resolved by this command in fastboot mode :
fastboot oem enableqxdm 0
But USB Brick is not resolved and my phone no longer root how can I do? I tried unsuccessfully Z4 root, is there another software to root without USB?
My capital is very little English, I did follow the instructions at the link:http://forum.xda-developers.com/showthread.php?t=691639. But it is not possible, please provide detailed guidance and may include images is very good.
(Each charge to just plug the cable and reboot the machine to receive a new charger)
Hi, I had the Same Problems some Minutes ago. (I was using the new AmonRA Recovery to flash a new ROM).
Here are the Steps what I have done to solve my problem (Rooted ROM is required):
1.) Download Android SDK -> Then open a comand Line and change into the Tools Directory:
cd path\to\AndroidSDK\tools
2.) You need to know your CID.
Turn your Phone into fastboot mode (Pressing Back and Power On). Then in your Comand Line do:
fastboot oem boot
The log will say something like the following:
CODE
.
.
.
#INFOCID is T-Mob101
In this specific case, the CID is T-Mob101.
3.) Get and extract the the attached Rescue.zip File.
Open the File "misc.img" in a hex Editor of your Choice and change "T-MOB101" to your CID
3.) Turn your Phone again into fastboot mode (Pressing Back and Power On) then go to your Command Line and do:
fastboot oem enableqxdm 0 (This will enable your SD Card to be seen in your favorite explorer on your phone)
then "Reboot"
4.) Then get the two files to your SD-Card (email them or dropbox them or what ever).
5.) Open a Terminal Emulator (http://www.appbrain.com/app/android-terminal-emulator/jackpal.androidterm) on our Phone
enter:
su (Enter to get Superuser Rights)
cat /sdcard/flash_image > /data/flash_image (this will copy the file to /data, therefore you need root!)
cat /sdcard/misc.img > /data/misc.img (this will copy the file to /data, therefore you need root!)
chmod 755 /data/flash_image (this makes the file "flash_image" executable)
/data/flash_image misc /data/misc.img (this will execute flash_image the result will be that you overwrite your misc section)
Reboot.
Everything should be ok
Ok this is a bit weird cos my usb got bricked yesterday too but a lot of searching i have managed to get it sorted. i lost root too so used this method http://forum.xda-developers.com/showpost.php?p=9056719&postcount=15 its similar to the above but for people who have lost root.
I've already re rooted and back on my leedroid2.2b
Guys can i just ask if your usb got bricked after you s-offed your desire and upgraded to the new amon ra recovery
I "S-OFF'ed" my Device some Time ago without any Problems. Today I flashed the new AmonRA via Unrevoked. Everthing went fine. After Flashing a new ROM (Oxygen) i had the mentioned USB/SD-Card Problem.
I was able to access my Device via Fastboot and get into Recovery but my SD Card was not able to be mounted anymore. (Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)).
Also i was stuck in a Bootloop after the "S-OFF Bootlogo".
After "fixing" the SD Card Problem, i was able to Boot the new Rom, access the SD Card via FIle Explorer, but my Device was not recognized properly while connected via USB. Something like "unrecognized Quallcom Device" Driver not found.
Yeah i had similar experience i had i flashed new amon ra via fastboot then backed up my leedroid2.2b rom via rom manager just cos i could rename it easily then booted into amon ra wiped and flashed latest leedroid. On the reboot it decided to reboot on the spalsh screen a few times and then the boot animation started when i booted i realised i had sd problem but wasn't aware of usb so ended up going the long way around
Guys need some help here.
I was previously on 1.28 with ARHD 4.1.
Recently tried to flash to ARHD 5.1 but during flashing, phone was bricked. It's currently stucks at the htc logo homescreen.
I can enter CWM into recovery mode but I do not have any existing ROMS in my SDcard. I believe we can write into the SD card by using the ADB commands in terminal. But my ADB devices list is being shown as empty
I have installed the latest htc drivers. I suspect this could be because one have to manually select the USB debugging mode on the phone upon plugging in. But since my phone is bricked, how do I go about enabling this option? Kind of lost now
Any help would be greatly appreciated!
Cheers!
If you can enter in recovery then it is not bricked. Try to mount storage in recovery and put zip file and reflash. Sorry cant help much myself but dont worry someone will tell you exactly what to do. I can reassure you, your phone is not bricked.
Cheers
If you can enter recovery, under mounts and storage or something there's an option called Mount USB Storage. Use that to connect your phone like a thumbdrive to your computer and you can flash any zip file from there. Also, did you flash the boot.img for ARHD via fastboot?
tlkh said:
If you can enter recovery, under mounts and storage or something there's an option called Mount USB Storage. Use that to connect your phone like a thumbdrive to your computer and you can flash any zip file from there. Also, did you flash the boot.img for ARHD via fastboot?
Click to expand...
Click to collapse
yes. i had flashed the boot.img file prior to it. i had tried the mount usb storage option but my computer ( have tried both mac & pc) , doesn't seem to pick up the device.
http://forum.xda-developers.com/showthread.php?t=1609190
Don't worry you can push files thru adb on to the sdcard, i did it few days back to recover from a similar situation.
The way to get adb working is by booting the phone directly from the recovery image rather than using the recovery on your phone.
Firstly, in case you aren't already using it, get the latest CWM recovery so that you may charge your phone in case its low on battery.
Secondly, get into fastboot mode and boot directly into recovery. (Not very sure about the syntax right now so not writing it here, search the forum.. its there somewhere)
Next, make sure sdcard & data are mounted in the recovery under "mounts & storage".
Now you can check if adb is working thru devices (most probably it should). Once that is confirmed, you are ready to push files thru adb & flash them.
Hope this helps...
problem solved. +)
cheers to all!
have a great day ahead!
Hi all
I'm starting to suspect that the partition my recovery uses as temp storage is full.
It gets stuck in the flashing process, I just tried side-loading with adb and it is now stuck, and has been for 1 hour.
Latest message from ADB says:
Code:
serving: cm-13.0-20151221-NIGHTLY-m8.zip (~47%)
Latest message from my recovery (latest stable CM)
Code:
Finding update package...
I have S-ON, but haven't had any problems flashing updates to cm so far
Any ideas?
I have the same problem on Sony Xperia M. It stops at 47% on cmd terminal, but on the phone it continues however I'm on bootloop now and couldn't get help anywhere.
joaobot said:
I have the same problem on Sony Xperia M. It stops at 47% on cmd terminal, but on the phone it continues however I'm on bootloop now and couldn't get help anywhere.
Click to expand...
Click to collapse
Sideload is very finicky. I've seen it fail and cause a lot of problems, where simply flashing from other means works just fine.
If you have a USB card reader and a MicroSD card, just put the ROM on the MicroSD card, insert into phone, and flash it from there (using custom recovery).
Otherwise, try to adb push the ROM to the phone's storage. Then flash in your custom recovery.
I don't have any specific experience with your phone, so that is probably all I can help.
redpoint73 said:
Sideload is very finicky. I've seen it fail and cause a lot of problems, where simply flashing from other means works just fine.
If you have a USB card reader and a MicroSD card, just put the ROM on the MicroSD card, insert into phone, and flash it from there (using custom recovery).
Otherwise, try to adb push the ROM to the phone's storage. Then flash in your custom recovery.
I don't have any specific experience with your phone, so that is probably all I can help.
Click to expand...
Click to collapse
Just to update, ADB push wouldn't work, ADB devices printout show device connected on sideload mode only.
So I tryed again untill it worked.
Thanks!
When I boot to twrp in recovery, I am unable to accomplish anything -- wipe or install. When I try to do either I get an error about "unable to mount sdcard". I have seen this thread, but cannot find the zip mentioned anywhere. I am able to run "adb push" to /sdcard and then to actually see the file pushed there in twrp recovery. I'm just not able to do anything with the pushed file in the install function.
Tried mounting with adb shell, but kept getting error of "Invalid argument". Did discover that /sdcard is /dev/block/mmcblk0p36, and using fdisk in adb shell found that it "doesn't contain a valid partition table". I'm not concerned about losing data. Everything was backed up, but anybody know how to create the correct partition table so I can install a ROM?
Original post:
So I screwed up. I rooted my phone according to this post. Unfortunately I then did something stupid when trying to flash a new recovery and get actual SU privileges to remove bloatware. Instead of going back to the first page in that thread and seeing the links to use there, I followed this guide. Unfortunately, when I ran the script, install-insecure-linux.sh, it flashed the boot.insecure.img and then spit out errors related to incompatibility with the ncurses version on my laptop. It seems difficult if not impossible to downgrade the ncurses without causing a ton of other headaches. It went to reboot and just stayed dead.
Thought I was hosed, but then after charging for a while I got signs of life. Managed to boot to fastboot. Connected back up to the laptop and decided to follow the cyanogenmod guide for installing CM11. Flashed the CM recovery img file successfully but after rebooting I can't do anything.
I still occasionally get into the fastboot on the phone. Running fastboot devices on the laptop lists the phone. Running adb devices does not. Running any other fastboot command sticks at either nothing or <waiting for device>. Running any adb command gives "error: Device not found". I added a udev rule and adb_usb.ini with the device id "0bb4" and mode 0666, but no joy.
I only have a linux machine available at the moment, so I'd prefer suggestions for working in linux. If someone knows of a good Windows solution, I can probably try that in a few days. Thanks in advance.
EDIT: Progress
Noticed that for a second when I first connect to the laptop USB the fastboot menu showed in red FASTBOOT USB before going back to just FASTBOOT. Managed to tee up the command for flashing the twrp recovery img and ran it immediately upon plugging in. Was then able to boot to recovery. Not sure what my next step to getting a working phone is though. Help still appreciated.
My last post got swallowed by the ether I guess. I was able to fix it by formatting the sdcard using mkdosfs -F 32 -n INT_SD -s 64 /dev/block/mmcblk0p36. Then rebooting, wiping, and installing CM11. All is good again.