Develop Bugs

[Q]Help! Bricked my Desire. NO ADB/SD/USB

Good morning...this is my first Thread in this forums, so i'd like to say hello to eyerybode...
The need to make an account here came today, as i wanted to flash the baadnwz SenseHD rom onto my HTC Desire (PVT4 - S-ON, HBOOT 0.93).
I used Unrevoked and the modified version of Clockwork Recovery (2.5.1.3)
Now i have got a serious problem.
I have no access to the SD Card, SIM Card does not work (Carrier does not work), no USB access and thus no ADB/Fastboot access.
I read a whole bunch of tutorials on how to unbrick my desire, but they all need USB/ADB/SD support...what should i do?
I can use Windows XP and Mac OS...
Thanks in advance!
UPDATE: SD Support & Carrier works, USB is still down. I am following the guide here in the forums, but i have an O2 Germany Software, so my CID differs form the one shown in the guide...how do i edit the mtd0 correctly, because the final command "/data/flash_image misc /data/mtd0.img" returns an error "new line expected..."

I take it that this was your first time rooting?
Can you switch on your phone? If you can try to do a factory reset in settings.
Have you tried taking out the sd card/sim card and using them on another phone?
You might need to create a goldcard to try and get your phone back to working order. Lots of tutorials on the web.
Side note: Was your rooting process successful? If so, can you go into recovery? Switch off phone, Press Vol Down + Power button.

friedkimchi, thanks for your reply.
I can switch on the phone. it boots up, the only thing that does not work is the usb support.
I was following this http://forum.xda-developers.com/showthread.php?t=691639 guide to unbrick it. It gave me back SD Card support, but the commands (cat /sdcard/...etc) do not have any effect on the usb support...
Maybe i am editing the mtd0.img file in the wrong way...my CID is O2__12, so what should i do?

Bobuscho said:
friedkimchi, thanks for your reply.
I can switch on the phone. it boots up, the only thing that does not work is the usb support.
I was following this http://forum.xda-developers.com/showthread.php?t=691639 guide to unbrick it. It gave me back SD Card support, but the commands (cat /sdcard/...etc) do not have any effect on the usb support...
Maybe i am editing the mtd0.img file in the wrong way...my CID is O2__12, so what should i do?
Click to expand...
Click to collapse
run the o2 RUU again from shipped roms to return it to stock and fix misc
once done start again and use the standard 2.5.0.7 clockwork mod or use amonRA 2.0.1
all other revisions of clockworkmod have problems
if you have s-off you could rename that img to misc.img and do "flastboot flash misc misc.img"
are you o2 DE or o2 uk? i thought its supposed top be o2___01

Hey,
i am on S-ON, so i guess i cannot flash the .img via fastboot...
My carrier is O2 Germany, i already downloaded the latest RUU, but since i have no USB connection, the RUU Utility returns a 171 connection error and gets stuck at the beginning ("rebooting bootloader...or so).
Is there any possibility to flash the content of an RUU via SD Card?
The easiest way would be to reactivate USB support...but this does not work as described in the USB Brick Fix tutorial...

[Q] Help with SD problems

So Ive been having problems with my SD card as posted here http://forum.xda-developers.com/showpost.php?p=16689682&postcount=286, and my question is, can someone explain to me how to flash back to stock without the use of my SD card ? Or am I screwed ? Thanks.

What you can do is download the RUU exe for the hboot you are on, if 2.10, its the 3.70, if 3.16, its 4.24 [the new ota], then connect the phone to the pc via usb, boot into the bootloader, select fastboot, then run the exe on the pc.

Thanks for the reply, and sorry for the noob question but how do you determine what hboot you are on ? Cause if I boot to the white Revolutionary screen (volume down + power) the third line down says "HBOOT-6.16.1002", is this right ?
----------
*EDIT*
Also dont know if this will help but when I am in recovery, if I try to mount my SD card it says "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (I/O error)"

Well I don't know if it was changed, but since you were on 2.3.3, you had to be on the 2.16, so for ruu purposes, look for that.

Alright, got stock back on. Thanks a lot.
I didn't know which one to use so I decided that since I have only had my evo for less than a month then I would use the latest version and it seems to have worked. So again, thanks a lot.

Okay, so I guess that I have a hardware problem and I will have to have it replaced. While my phone was just sitting there a notification came up that said "SD card unexpectedly removed"
Do I have to change the phone back to S-On before I get it replaced or can I keep it S-Off ?

Glad that you got it working, and you need to be s-on.
If you're s-off, re-root, then download the unrevoked s-on tool, flash the zip in recovery, make sure the bootloader reads s-on, the unroot again.

okay, so when I try to use the unrevoked s-on tool it fails and says unsupported radio type. any fix for this ?

BioBot said:
okay, so when I try to use the unrevoked s-on tool it fails and says unsupported radio type. any fix for this ?
Click to expand...
Click to collapse
try the 3.70 radio

You need to go to the development thread, then download the 2.1...11.19 radio and flash that.

Thanks for all the help guys. I've ran into another problem now. Before this new problem, if I wanted to put a new file on my SD card I had to flash to stock which gave me a 30-45 second window to mount the card to my pc and copy any files I needed to and power off before it unmounted it. Then I had to reboot, run revolutionary and get a recovery before it unmounted. Then I could flash a zip from my SD. BUT NOW, even if I reflash stock, it auto unmounts the SD at bootup.
Frustrated but still trying to problem solve.... Will update if anything changes.

Okay. I think I got it fixed now. After spending all day trying and flashing my phone at least 12-15 times it seems to be doing okay.
Solution : New SD card
Thanks for your help everyone !

[Q] Help - stuck at HBOOT/Recovery and can't run RUU on HTC Desire

Hi guys, wonder if you can help me. I have a HTC Desire (GSM) and rooted it, removed UK O2 branding and putting Froyo (2.2) on it and a new radio and Clockwork Mod Recovery. I messed around - thought I’d bricked it following a dodgy flash, as couldn't boot, get into recovery or anything, with the phone looping at the HTC logo and powering on until I took the battery out.
Thought I’d look at it today and made progress, but still can’t get a RUU to install on it. I can get into Recovery menu via bootloader and I think the SDcard is a goldcard. Issues I have are:
• I can’t flash a RUU onto the phone from running the file through Windows, as I constantly get an Error 170 USB Connection error. I’ve tried reinstalling HTC Sync, trying different versions, tried a different USB cable and port. I’ve tried running HTC Sync as Admin, and in compatibility mode under XP SP 2 and updated the driver in Control Panel and it displays as “My HTC”, nothing works. I am running Windows 7 64 Bit.
• I tried putting the RUU onto the phone as a PB99IMG.zip file and running it through Recovery, but I get a message saying “bad file”
• As soon as I put a file onto the SD card, Ext3 then won’t mount with an error message and I have to repartition the SD card in Windows (Using Mini-tool Partition Wizard). The error I get is "can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!” I can fix it, but soon after it is fixed it reverts back to error it I add any files to root of the SD card to run through Recovery.
I just want to get the phone back working, whether it is branded or unbranded, and whatever RUU I can get working on it. Can anyone advise the steps I can take from here please?
My stats/versions are:
HBoot 0.93.0001
Radio 5.09.00.08
ClockworkMod Recovery v2.5.0.7
S=On
Thanks,
Stewart

Tried downloading the RUU again? I recommend to check md5sum afterwards.
Sent from Sandvold's ICS using Transparent XDA App

Thanks MatDroid, I've managed to get past the 171 error and now getting a 131 error, saying it is the incorrect ROM. Is there somewhere I can get confirmation of the correct ROM for my device and check MD5sum before loading?

I would look at putting on another recovery, something like 4ext touch. Google it, your current clockwork recovery is pretty dated. Look at a program called android flasher, and you will be able to flash a new recovery through that.
Once you get the new recovery working, there is an option to toggle USB storage in which you can put your custom from on the SD card. Once the custom from is on your SD card, flash it through recovery. Hopefully it should work
Sent from my HTC Desire using XDA App

you should really look at my guide, you don't flash RUU zip files through recovery.

just realised you are s- on so android flasher won't work. Therefore until you s-off your phone, as mattdroid said you may have a bad download for the ruu. Try downloading ruu again nd running the exe file
Sent from my HTC Desire using XDA App

bortak said:
you should really look at my guide, you don't flash RUU zip files through recovery.[/QUOTE
Yeah just realised that too sorry for the wrong information. he is only wanting a ruu which of course is not done through recovery with the exe file. Custom rom is a different story.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse

Thanks guys I've figured it out and have now succesfully got the phone working.
Issues were:
I was trying to flash the wrong RUU (a 2.09 instead of 2.10) so when flashing it was rejecting as a lower version. Using the right RUU worked
My SDcard wasn't a goldcard - I thought it was but apparently not. I re-created the goldcard and it worked
I was trying to flash from the wrong place - instead of through FastBoot USB I was going into Clockwork Mod and loading files, mucking around with the mountings and things like that
All great now, so thanks again.
Stewart

[Q] Can't Root HTC Desire

Im stuck on rooting..
First when i try to install the HBOOT drivers it installs them as "HTC Serial Interface (COM4)" after the Android 1.0 thing (windows automaticly installs them and cannot abort that, and if i want to update it with the custom ones it says the current drivers are up-to-date.
So i dont have the "Android Bootloader Interface" option at the device manager.
Got the HTC Driver and HTC BMP USB drivers installed and removed HTC Sync.
Second, whatever Revoked version (i used 3.21-3.32, it keeps hanging on "waiting for Bootloader, make sure drivers are installed"
I've been repeating the process like 100x each step and still.
Additional info:
OS: Windows 7 64-Bit
Android 2.2.2 Original Stock (SoftwareNr: 2.29.405.15)
4GB SD Card (class 10)
Bravo PVT4 SHIP S-ON
HBOOT 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
Radio-5.11.50.26
Aug 10 2010, 17:52,18
I have used various methods from different forums none seem to work and i'm really clueless.
I've flashed Samsungs, Sony's, even MTK's flawlessly and this particular HTC device is a pain in the ass.
Ive used XDA guide: http://forum.xda-developers.com/showthread.php?t=1275632
and: http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
and: http://androidforums.com/desire-all...ked-windows-updated-11th-november-2011-a.html
and: http://androidforums.com/desire-all-things-root/503471-desire-all-things-root-guide.html
Is there anyone with a sollution because i really need more app space (or a bloatware free rom) and based on various comment on the sites mention didn't work as well as it should.

You'll want to gain s-off first before rooting. To do this you can use revolutionary.
First I'd suggest removing any drivers (and HTC sync) that you have already installed. Then setup adb/fastboot as it may be useful later. Finally install these fastboot drivers. Now to test if its being detected put the phone into the bootloader (turn off, then boot up using volume down + power). Next plug the phone into the computer via usb and open up a command prompt window. Run "fastboot devices" and the phones serial number should be shown. Let me know once you've done this.

Chromium said:
You'll want to gain s-off first before rooting. To do this you can use revolutionary.
First I'd suggest removing any drivers (and HTC sync) that you have already installed. Then setup adb/fastboot as it may be useful later. Finally install these fastboot drivers. Now to test if its being detected put the phone into the bootloader (turn off, then boot up using volume down + power). Next plug the phone into the computer via usb and open up a command prompt window. Run "fastboot devices" and the phones serial number should be shown. Let me know once you've done this.
Click to expand...
Click to collapse
Thanks i will try that and report back.
It would've been nice if any of those tutorials mentioned S-OFF needed before hand!
Edit: okay the phone is S-OFF, i will now proceed with the ADB thing but its downloading the SDK files as we speak...

@Chromium
Okay ive installed the adb files and set it all up. But i'm stuck on "fastboot devices" on the cmd command line saying it cannot find "fastboot devices"
If i run C:/adb fastboot devices i get a bunch of commands while the phone was booted into HBOOT (S-OFF ofc)
Also tried C:\adb\platform-tools>fastboot devices but nothing is shown
For some strange reason my device manager says SAMSUNG ANDROID PHONE > Android Bootloader Interface when i hit "Bootloader" in HBOOT (was testing this)
Ignoring the adb step: I rerun every step again but it's still stuck on "waiting for Bootloader, make sure drivers are installed" after running Unrevoked3
additional info:
Revolutionary S-OFF
HBOOT-6.93.1002
Edit: question; I installed Revolutionary CWM v4.0.1.4 through revolutionary after the S-OFF process (which is weird since installing a custom recovery needs root access).
Is it possible to install 'custom rooted roms' through "update from sdcard", without root access?
I ask before hand because i dont want to brick my phone..
I have done a backup in CWM, so i'm going to try and flash a rom...

Ok i succesfully flashed my htc with CM7.2 without rooting my htc in the first place.
I've been struggling with the rooting process for 2 days, but as i mentioned in my previous post i just flashed through revolutionarys CWM.
thank god!

(Even though your best ROM thread was closed, I did mention s-off and revolutionary and the guides...the ones you found are old)
You don't technically need root access to install custom recovery as you have found out.
You are already s-off, that's the hardest bit, rest is easy.
To root your existing ROM if you need to, flash superuser thru recovery
Don't know why fastboot devices didn't show, driver issue somewhere or not set up correctly.
Anyway if you can boot into the os, install 4ext recovery via app from 4ext,net.
Backup your sd card and use 4ext to partition your sdcard.
Then yes you can install a stock rooted ROM or any custom ROM of your choice, check for individual a2sd features or requirements

eddiehk6 said:
(Even though your best ROM thread was closed, I did mention s-off and revolutionary and the guides...the ones you found are old)
You don't technically need root access to install custom recovery as you have found out.
You are already s-off, that's the hardest bit, rest is easy.
To root your existing ROM if you need to, flash superuser thru recovery
Don't know why fastboot devices didn't show, driver issue somewhere or not set up correctly.
Anyway if you can boot into the os, install 4ext recovery via app from 4ext,net.
Backup your sd card and use 4ext to partition your sdcard.
Then yes you can install a stock rooted ROM or any custom ROM of your choice, check for individual a2sd features or requirements
Click to expand...
Click to collapse
I know and i've seen the link, but i started with the ROOT part from that website as i thought the S-OFF part came after the rooting process.
I just installed CM7.2 and everything worked fine.
I partitioned the SD card in the CWM menu but i didn't knew what size to pick so i went with 1024mb and 256mb cache.
Im glad cm works and my app space is 151mb however on first boot there was 148mn available and now after a reboot & googleplay store only 56mb is left????
Well atleast i can move apps to SD (i guess)
edit: I flashed Beanstalk 4.4 (release 4.5) with jmcclue's 250/5/182 hboot & 4EXT Recovery. Everything works perfect.

JMailuhu said:
I know and i've seen the link, but i started with the ROOT part from that website as i thought the S-OFF part came after the rooting process.
I just installed CM7.2 and everything worked fine.
I partitioned the SD card in the CWM menu but i didn't knew what size to pick so i went with 1024mb and 256mb cache.
Im glad cm works and my app space is 151mb however on first boot there was 148mn available and now after a reboot & googleplay store only 56mb is left????
Well atleast i can move apps to SD (i guess)
edit: I flashed Beanstalk 4.4 (release 4.5) with jmcclue's 250/5/182 hboot & 4EXT Recovery. Everything works perfect.
Click to expand...
Click to collapse
You've rushed into it without following instructions or understanding how things work................
- You shouldn't partition with cwm as it often makes badly aligned partitions (they don't work)
- You don't need to partition with cache as the ROM needs to be programmed use it, and has limited benefit anyway
- You're not actually using your partition if you don't flash an a2sd script or use an app to actually move things to the partition of the sdcard. Your 'move to sd' is moving part of the app to the original fat32 part of your sdcard, exactly the same as before you even rooted/s-off i.e no gain...
- You should have flashed a different hboot before you flashed the ROM as you're wasting space on /system, which is also why your seeing low memory already. Again you have exactly the same amount of internal space as before you rooted/s-off....
So....
- please flash 4ext recovery as instructed
- completely backup and re-partition your sdcard from scratch with that recovery, no swap or cache
- learn to flash cm7r2 hboot with fastboot, instructions in the earlier guide you found
- full wipe and reinstall cm7 ROM again
- flash a2sd script or use an app such as s2e to move future apps to your sd partition (sd-ext)
- Keep apps on internal to trick them to sd-ext, your memory won't necessarily appear expanded, but your partition is working
- install an app like DiskUsage to understand how all your memory is being used in the first place...
Seems a lot but you should have read and done this in the first place you can do it correctly now or run into trouble later when you have no idea why...
EDIT: only saw your edit after my initial reply.
Some of my points still stand...please at least understand how your memory is being used (DiskUsage)

[Q] Freezes after applying downgrade via AAHK2

Hello,
I wanted to root my HTC Desire HD with AAHK2. At first it worked fine, connected to my phone, said that it needs to downgrade, went into hboot and did the necessary tasks.
Now I am unable to boot my smartphone. It freezes at the HTC logo. The same in HBOOT - it also freezes.
HBOOT shows me following info:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011,00:55:45
I removed micro SD and sim and were successful in doing a fastboot. After that I did a factory reset but that did not change things either.
Somebody knows what I should do now (except buying a new phone )
Greetings in advance!

Where did u factory reset...the phone settings,recovery or on the bootloader?
Sent from my One X using Tapatalk

Hi, directly via the bootloader menu. Menu named "Factory Reset" directly under the menu item "Recovery". Greetings!

So your Bootloader freezes too ?

echizen81 said:
Somebody knows what I should do now (except buying a new phone )!
Click to expand...
Click to collapse
Hello echizen81,
Firstly, you must ensure that your phone can still receive fastboot commands. To ensure this, navigate to tools\win folder on AAHK2 extraction location and issue a 'fastboot devices' when you boot to bootloader to see if fastboot works (you should get a entry corresponding to your phone as a result of the command).
If this does, then there's still some hope of recovery! Read on...
On many posts related to AAHK2 issues, senior-forum-members (and Phiber2000 himself) have suggested using brands of SD cards which are known to work. One such list is present here, http://forum.xda-developers.com/showthread.php?t=2367322.
It is possible that your issue could be due to either
a bad SD card which corrupted the transferred zip (since it appears that HBOOT itself was 'downgraded' properly), or
a bad USB connection (which corrupted the zip during transfer), or
a bad flash/hardware (in which case, you'd unfortunately need to buy a new device )
I'd recommend you change your SD card before attempting any sort of recovery of your device from this state. Also, make sure that the USB plug stays snug during file transfers. (and keep your fingers crossed while hoping that it is not a device's issue)
I had a similar (not same) issue, wherein I soft-bricked my device due to (incorrect) usage of attn1's AAHK.
Since you can access bootloader, you should be able to use an official RUU (pick an RUU which is supported without downgrade on AAHK2 from here http://shipped-roms.com/index.php?category=android&model=Ace - be sure to pick a Froyo RUU ONLY IF you were using Froyo earlier, else pick-up a GingerBread RUU). However, since misc_version has altered the information an official RUU verifies on your device before flashing, you'd need to use a goldcard.
I recovered my device by creating a goldcard manually and flashing an official RUU. Here are the steps I followed:
acquire another SD card of one of the brands known to work with AAHK2 (Samsung, SanDisk, ADATA, etc)
You'd need to know the CID of the card you are using. Since it is a property of the SD card:
find a device (from a friend, maybe?) in which you can put the SD card
install ES File Explorer (https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en)
read the card's CID register (by navigating to /sys/class/mmc_host/mmc{N}/mmc{N}:{ID}/cid, where 'N' identifies the SD card (in case the device you are using has internal memory as well)
to be sure that you are actually reading the correct CID, repeat the procedure AFTER removing/replacing the SD card
note which MMC ID is absent/changed. This is the ID ('0', '1', or '2') whose CID register you should read and note.
Once you have the CID, visit http://forum.xda-developers.com/showthread.php?p=17247562 for instructions on goldcard creation.
The Gene Poole's http://huygens.hoxnet.com/goldcard.html was working till a few days ago, but is down right now.
If Gene Poole's portal remains unavailable, use the tool in the second post on the thread.
insert the goldcard, ensure your phone is charged more than 30% (if it's not, RUU wouldn't allow a flash. Follow this thread to 'charge' the device to appropriate voltage levels if the 'normal' method of charging won't work: http://forum.xda-developers.com/showthread.php?t=1658084)
Make sure you've all the correct HTC drivers installed. Fire the RUU and your phone should be recognized.
Proceed with flash, and keep your fingers crossed!
Do post your results. All the best!