Develop Bugs

Is it possible to flash a hero without sd card?

Hello everyone!
I have run into problems with my hero since I flashed Drizzy's hero rom.
My sd card reader is no longer functioning and hence I am locked into drizzy's rom without any possibility of any kind of sd card use.
The sd card can't be read from cyanogens recovery even.
Is there any way to put a new rom on the phone without access to the sd card?
(I have root if that helps)
Thanks in advance,
Hampan

Can I use the fastboot update command without an sd-card available to the phone?

you can push (=upload) with adb (command is: adb push [local] [remote]) a file to the sdcard (just connect your phone via usb to computer)
example:
update.zip is here: C:\update.zip
then do:
adb push C:\update.zip /sdcard/update.zip
then it will upload the file (about 5-10 minutes).. ready to flash

Thank you for your reply , no I can't make adb connect to the phone.
Only fastboot works, and even if adb was working I couldn't possibly make it push the update to the sdcard since the phone can't see the sd card at all.

and you are even not able to access the sdcard via cyanogen recovery AND adb shell??

No exactly, the sd card can't be reached from ANYTHING , adb shell won't connect although fastboot does, and i can use fastboot commands.
I tried using the "fastboot update update.zip" with modacos rom but got the message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I'm thinking maybe one can flash the device without putting anything on sd via "fastboot update" .. can anyone confirm?

simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot

Thanks for your reply, yes I did make a nandroid backup and copied it to my pc
However, as it stands now I can only reach the phone from the computer with fastboot, usb is not recognized in windows and sd card is not functioning (even in cyanogen fastboot).
So, if I use my old stock nandroid backup and somehow the sd and usb is still not functioning, would there be a possibility that I would be stuck with the old slow rom forever?
Thanks for any help!

keatonreckard said:
simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot
Click to expand...
Click to collapse
Yup, now I tried .. doesn't work
C:\android-sdk-windows-1.5_r3\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
I'm sh*t out of luck aren't I?

maybe the remaining option is to send it to htc... :-( but that will cost money cuz you lost the garanty

Yup, that, sadly -Is my conclusion as well.
Anyway, the phone works as usual , just no SD and no updates.
Since I have no warranty I might just wait until a new android version is released for Hero.
Thank you all for replying and trying to help me.

stupid question, but did you check to see if it is the micro sd that went bad, not the reader? you don't need to embarrass yourself by responding, I just hope it helps if that is what it was.

I have the same problems and follow these threads:
http://forum.xda-developers.com/showthread.php?t=556335
http://forum.xda-developers.com/showthread.php?t=559106

Can't you try to 'update' (restore) it with the htc RUU .exe
?
not totally sure since i dont have a hero myself, but i think this might work...

[FIXED] HELP NEEDED! Deleted Framework-res and stuck in loading screen ;[

Ok im not usually this stupid but for some unknown reason my brain went on holiday this morning and I deleted the framework-res.apk from the system/framework folder on the phone when performing a mod. As expected now my nice new phone is stuck in the animation screen and I dont know how to get the file back on the phone.
* The bootloader is unlocked and I have rooted it.
* Adb is setup on my pc but if I boot the phone into the fastboot screen I get no device found when I type adb devices.
* I have tryed the same thing in the Recovery screen.
* Fastboot works and I can lock and unlock the bootloader.
I have installed the samsung usb driver pack which and used the samsung android adb interface as my Adb Interface driver.
I need to somehow push the framework-res.apk (which I have on my pc) back to the /system/framework folder on my phone so it will boot back up or im going to have to send it back ;[
I know there is a dump in the Development forum so I dont know if I can use part of that to flash the system image using fastboot?
Im not too big to ask for help when I need it and thisd isnt my speciality. I have been googling this all night to no avail so now I pass it over to you.
Im not going to bed I hope someone will be able to help when I wake up or its off to phones4u with my broken phone lol.
Mark.
EDIT: Fix can be found *HERE*

As long as that dump is correct, and it seems to be judging from the other replies in the thread, you should be able to simply flash it using 'fastboot flash system system.img' (or whatever he called the file).
If you don't want to do that for some reason you could check if ADB is enabled in recovery as it is in custom roms. If so, you could mount the system partition (mount /system) and then push it from there. Might not be enabled in stock recovery though.
EDIT: I saw you mention adb devices. That only works when adbd is running which it naturally isn't in fastboot mode as that is a much lower level than that. The command 'fastboot devices' exists though.

I'm not familiar with fastboot at all but have you tried adb kill-server and then adb devices?
I had an issue before with finding a device and it fixed it

altimax98 said:
I'm not familiar with fastboot at all but have you tried adb kill-server and then adb devices?
I had an issue before with finding a device and it fixed it
Click to expand...
Click to collapse
ADB is handled by the daemon adbd which starts during boot and is an Android/linux binary. The bootloader most certainly isn't something that high-level though so it makes no sense to try to interface with it using ADB in that mode.
Recovery is a very slimmed down Android though so it would work if it's enabled in stock recovery.

blunden said:
As long as that dump is correct, and it seems to be judging from the other replies in the thread, you should be able to simply flash it using 'fastboot flash system system.img' (or whatever he called the file).
Click to expand...
Click to collapse
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.

mskip said:
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
Click to expand...
Click to collapse
http://www.hard-reset.com/samsung-galaxy-nexus-hard-reset.html
?

winwiz said:
http://www.hard-reset.com/samsung-galaxy-nexus-hard-reset.html
?
Click to expand...
Click to collapse
Doesnt do anything I have tryed going through the recovery selection in the fastboot screen. Also that page is inacurate as you need to hold Volume Up + Volume Down while powering up. Volume Up + Power just boots up as normal..
My only bet before taking it back is via fastboot which works fine. I still have the bootloader unlocked but that system image wouldnt flash .
Mark.

Well theoretically you can try to use fastboot and
fastboot flash system system.img
All you need to do is to make system.img

mskip said:
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
Click to expand...
Click to collapse
The system image is probably not a sparse image -- that is, the image exceeds the RAM size for fastboot. Same issue with the Nexus S.

mike1986. said:
Well theoretically you can try to use fastboot and
fastboot flash system system.img
All you need to do is to make system.img
Click to expand...
Click to collapse
How do I make a system image from the system dump *HERE*?
Mark.

ydaraishy said:
The system image is probably not a sparse image -- that is, the image exceeds the RAM size for fastboot. Same issue with the Nexus S.
Click to expand...
Click to collapse
Yes thats exactly what I read about in the Nexus S thread when I was researching this. Is there any way to make it smaller so its flashable?
Mark.

Post here your framework-res.apk

mike1986. said:
Post here your framework-res.apk
Click to expand...
Click to collapse
Here you go
Mark.

In the meantime - have you tried this? http://forum.xda-developers.com/showthread.php?t=1193915
It has "Flash multiple files in one click by using custom folders and tags."
Worth to give a shot. Let me know if it works.

Ok I think I know how to solve your problem What is your stock ROM? ITL41D?

mike1986. said:
Ok I think I know how to solve your problem What is your stock ROM? ITL41D?
Click to expand...
Click to collapse
Yes its the retail build which is ITL41D
Mark.

So here is what I have done:
I included framework-res.apk in ramdisk inside boot.img. This way it should fix your problem but now keep in mind that you can't replace framework-res.apk because it will be reloaded from ramdisk on every boot. So if your device will boot with boot.img from me then adb push framework-res.apk /system/framework and reboot in fastboot and fastboot flash boot boot.img BUT stock boot.img this time so it wont replace your framework-res.apk. So:
1. Modified ITL41D boot.img - flash in fastboot using fastboot flash boot boot_mod.img
2. If system boots (I'm not sure if will) then adb push framework-res.apk /system/framework
3. Boot in fastboot and flash Stock ITL41D boot.img - flash in fastboot using fastboot flash boot boot_stock.img

mike1986. said:
So here is what I have done:
I included framework-res.apk in ramdisk inside boot.img. This way it should fix your problem but now keep in mind that you can't replace framework-res.apk because it will be reloaded from ramdisk on every boot. So if your device will boot with boot.img from me then adb push framework-res.apk /system/framework and reboot in fastboot and fastboot flash boot boot.img BUT stock boot.img this time so it wont replace your framework-res.apk. So:
1. Modified ITL41D boot.img - flash in fastboot using fastboot flash boot boot_mod.img
2. If system boots (I'm not sure if will) then adb push framework-res.apk /system/framework
3. Boot in fastboot and flash Stock ITL41D boot.img - flash in fastboot using fastboot flash boot boot_stock.img
Click to expand...
Click to collapse
WOW. nice if it works!

Doesnt work im afraid..
I get the following information in the command screen:
fastboot flash boot boot_mod.img (my input)
> sending 'boot' (8752 KB)... OKAY
> writing 'boot'... FAILED (remote: Write Fail)
On the phone is displays:
FASTBOOT STATUS - FAILWrite Fail
Mark.

mskip said:
Doesnt work im afraid..
I get the following information in the command screen:
fastboot flash boot boot_mod.img (my input)
> sending 'boot' (8752 KB)... OKAY
> writing 'boot'... FAILED (remote: Write Fail)
On the phone is displays:
FASTBOOT STATUS - FAILWrite Fail
Mark.
Click to expand...
Click to collapse
rename it to boot.img and try again.

Flashing Radio using Android Flasher

I can't post on the developers thread so thought best to post here.
I'm trying to use android flasher to flash the latest Desire radio (bravo.5.17.05.23) as recommended by the Sense ROM's I'd like to try.
I have installed Windows .net 4.0 on Windows Vista, have downloaded HTC Sync and then uninstalled it leaving only the drivers remaining. I also have USB debugging enabled.
I have booted into FASTBOOT having powered off (Power button, back button) and have connected the phone to the laptop to get FASTBOOTUSB to appear.
I unzip Android Flasher and the two .dll files to the desktop and then open Android Flasher. I select Desire and then browse for the radio .img on my desktop. I tick "I'm already in fastboot" and then press flash.
At this point the status bar reaches just over halfway. No script appears in the dialogue box and nothing further happens.
Can anyone advise if I have missed a step? Do I need to reboot the phone from inside the FASTBOOT USB menu?
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27

You might want to try and flash the radio image directly via fastboot. Just download the fastboot binary, put it in a path you can remember, put the radio img file in the same directory, click Start > Run and type in cmd. Then, type in 'cd C:\path\to\the\fastboot\directory\', followed by 'fastboot.exe flash radio radio_image_name.img'. That's it!

Proz0r said:
You might want to try and flash the radio image directly via fastboot. Just download the fastboot binary, put it in a path you can remember, put the radio img file in the same directory, click Start > Run and type in cmd. Then, type in 'cd C:\path\to\the\fastboot\directory\', followed by 'fastboot.exe flash radio radio_image_name.img'. That's it!
Click to expand...
Click to collapse
Hello - I just tried this and got the following error ....
H:\>fastboot.exe flash radio D:bravo.5.17.05.23.zip
sending 'radio' (11561 KB)...
OKAY [ 1.906s]
writing 'radio'...
FAILED (remote: image update error)
finished. total time: 1.969s
Any ideas ?

Sorry wrong post

Looloup said:
Hello - I just tried this and got the following error ....
H:\>fastboot.exe flash radio D:bravo.5.17.05.23.zip
sending 'radio' (11561 KB)...
OKAY [ 1.906s]
writing 'radio'...
FAILED (remote: image update error)
finished. total time: 1.969s
Any ideas ?
Click to expand...
Click to collapse
Yep, you need to extract the .Img file from the zip and fastboot flash that. Not going to work trying to flash the zip file.
Sent from my HTC Desire using Tapatalk

Is it necessesary to be S-OFF to flalsh new Radio?
I tried with revoked but it does not find my phone so i think of flashing radio via fastboot instead of sdcard.

Px80 said:
Is it necessesary to be S-OFF to flalsh new Radio?
I tried with revoked but it does not find my phone so i think of flashing radio via fastboot instead of sdcard.
Click to expand...
Click to collapse
yes i believe you need to be s-off to flash radios
in your sig, you have desire s, so don't flash radios from this thread (for desire (Bravo))!
make sure you check the md5 sum of the radio.img before flashing, a bad radio flash = brick! the fastboot commands should still be the same however.

[Q] stuck on htc quietly brilliant screen

Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.

You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium

Thanks sir, I'll try.

sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.

thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card

sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too

dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.

See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA

Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.

"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command

sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA

Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!

Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.

Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!

I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?

All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot

i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.

mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?

When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s

Nobody can help me?!! ((

[Q] cant flash europe ruu 1.32.401.8 zip

when i try to do the fastboot flash zip command for the m9 europe ruu 1.32.401.8, fastboot crashes and i get an error "invalid sparse file format at header magi"
any ideas whats going on?
i can flash the eu exe ruu file, that installs fine - version 1.32.401.17
i need this one installed, as i think the exe file is the wrong one

eggyfish said:
when i try to do the fastboot flash zip command for the m9 europe ruu 1.32.401.8, fastboot crashes and i get an error "invalid sparse file format at header magi"
any ideas whats going on?
i can flash the eu exe ruu file, that installs fine - version 1.32.401.17
i need this one installed, as i think the exe file is the wrong one
Click to expand...
Click to collapse
are you using the regular fastboot file or the htc_fastboot file?

anandlal said:
are you using the regular fastboot file or the htc_fastboot file?
Click to expand...
Click to collapse
not sure what you mean there, but i go into the black htc screen after reboot ruu, i also cant copy the file over usb as it says the device isn't responding or its disconnected .

eggyfish said:
not sure what you mean there, but i go into the black htc screen after reboot ruu, i also cant copy the file over usb as it says the device isn't responding or its disconnected .
Click to expand...
Click to collapse
@anandlal meant that you need to use htc_fastboot instead of fastboot. htc_fastboot is capable of handling larger files. Download htc_fastboot and put it in the same folder as fastboot. It works exactly the same other than adding the "htc_" in front of the command.
this post has a link to download:
http://forum.xda-developers.com/showpost.php?p=60657724&postcount=7

jollywhitefoot said:
@anandlal meant that you need to use htc_fastboot instead of fastboot. htc_fastboot is capable of handling larger files. Download htc_fastboot and put it in the same folder as fastboot. It works exactly the same other than adding the "htc_" in front of the command.
this post has a link to download:
http://forum.xda-developers.com/showpost.php?p=60657724&postcount=7
Click to expand...
Click to collapse
Thanks! htc_fastboot was mentioned before in guides i read but it was never really explained, the ruu flashed fine and my phones up and running
thanks for your help