So the USB port on my Desire is dead - well, not quite, it will still charge, but data transmission will not work. It is most definitely hardware, clockworkmod will not mount USB storage, and nothing even gets detected in Windows/Linux.
My challenge is that I would like to try out an ICS ROM. However, guides tell me that my phone has to have S-OFF before I do this. For this, you need to use ADB over USB. Hmm!
As it stands now, I have flashed Clockworkmod 2.5.0.1, and I am running Cyanogenmod 7.1. Everything works fine (minus USB of course).
My bootloader shows the following information:
BRAVO PVT1 SHIP S-ON
HBOOT-083.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
JUN 10 2010, 12:12:05
FASTBOOT
(OPTIONS)
My phone is currently rooted and was originally done so to install Oxygen (by previous owner). I then upgraded to Cyanogenmod without too much trouble later on.
My question is, should I be able to use clockworkmod recovery to flash BCM or Sanvold's ICS ROM as is, or should I find a way to alter the hboot and s-off without USB, such as ADB over WiFi? Or should I just stick to Cyanogenmod 7? Would love some opinions before I try something stupid and brick what is still a good phone! Thanks in advance
Already checked bortaks troubleshooting guide?
Sent from my HTC Desire using XDA
MatDrOiD said:
Already checked bortaks troubleshooting guide?
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I did, but I'm a little bit confused. Bootloader says S-ON, but my ROM has root, is that right?
edit: yes, that makes sense now. But I still can't see how I can achieve permenant S-OFF without USB.
Is your USB port damaged on a hardware level, or is your phone USB bricked (software issue)?
TVTV said:
Is your USB port damaged on a hardware level, or is your phone USB bricked (software issue)?
Click to expand...
Click to collapse
It's hardware, as stated in OP. Totally toast. But still charges.
How can you tell that it's a hardware issue? Can you see the damage to the USB port?
Unfortunately, as far as i know, there is no way to achieve S-OFF without using the USB port.
If the port is really damaged (and your phone is not just USB bricked - which is fixable), you can try getting your port replaced at a phone repair shop. It shouldn't be too expensive.
TVTV said:
How can you tell that it's a hardware issue? Can you see the damage to the USB port?
Unfortunately, as far as i know, there is no way to achieve S-OFF without using the USB port.
If the port is really damaged (and your phone is not just USB bricked - which is fixable), you can try getting your port replaced at a phone repair shop. It shouldn't be too expensive.
Click to expand...
Click to collapse
I'm an IT Technician, so I know what I'm doing. As far being USB "bricked", I don't think so. It used to work when I was on CM7, and then it just suddenly stopped working.
As it seems, it looks like it's stuck on gingerbread. Should I be able to update to Cyanogemod 7.2 RC2 without S-OFF?
Your situation is a weird one. As far as i know, while being S-ON, you shouldn't be able to flash a custom recovery to your phone, yet you say you did. This leads me to believe that your phone might have been S-OFFed, at one point in time, by Unrevoked Forever. What Forever does is completely remove the S-ON RADIO flag instead of just messing with the bootloader. Ergo even if your bootloader is a stock one, reading S-ON, you're really still S-OFF. Please test this by trying to write stuff (i.e. copy a file) to your phone's system partition with a (root) file explorer of your choosing (while booted into Android, of course). If it works, then you're actually S-OFF thus meeting the ICS ROM's requirement. If it does not, then something's amiss.
Regarding the USB port, i'm not trying to offend your skills in any way, but please boot the phone into HBOOT, switch to fastboot mode and then try connecting your phone to a PC using a different USB cable. If HBOOT reads FASTBOOT USB instead of just FASTBOOT, then you have an USB brick on your hands. I'm insisting because i haven't heard of a problem such as yours. Usually, when the USB port goes, it goes completely.
TVTV said:
Your situation is a weird one. As far as i know, while being S-ON, you shouldn't be able to flash a custom recovery to your phone, yet you say you did. This leads me to believe that your phone might have been S-OFFed, at one point in time, by Unrevoked Forever. What Forever does is completely remove the S-ON RADIO flag instead of just messing with the bootloader. Ergo even if your bootloader is a stock one, reading S-ON, you're really still S-OFF. Please test this by trying to write stuff (i.e. copy a file) to your phone's system partition with a (root) file explorer of your choosing (while booted into Android, of course). If it works, then you're actually S-OFF thus meeting the ICS ROM's requirement. If it does not, then something's amiss.
Click to expand...
Click to collapse
Actually, I faced the same issue. Was unable to update recovery through Rom Manager (although I had root access) because somehow the first time I used Unrevoked (v3) it flashed CWM recovery, gave me root but didn't S-OFF.
After that I had to S-OFF again in order to be able to update my recovery.
As for usb, I had the same kind of issue with the usb port of an Archos tablet, usb flash drive was powered (flashing led) but absolutely not detected by the tablet (same kind as in power ok but data nok). I finally had to return it (and they refunded it).
Changing the port might work, but that's not 100% sure.
TheTenth, thank you for your reply. Upon reading it, i realized that you might be right. After reading the first post, i was under the impression that the OP has recently installed clockworkmod himself, thus making the arguments in my previous post valid. But indeed, clockworkmod 2.5.0.1 appears to be "bundled" with Unrevoked v3.1, so the phone might have been rooted in the past by Unrevoked, but never S-OFFed. Well, that's a bad situation for the OP, then, because again, i can't think of another way to gain S-OFF than via USB.
If there's a custom recovery, one should be able to flash a custom rom - I have never heard of roms that require S-OFF to work. There are, however, some roms that require a certain hboot, and for changing that s-off is required. But flashing an ICS rom should work with the stock hboot - in fact, Sandvold's builds seem to work best on stock hboot. So no need to s-off for now, except that you are stuck on your old recovery (which hopefully should also be able to handle touch input in aroma installer).
muellersmattes said:
If there's a custom recovery, one should be able to flash a custom rom - I have never heard of roms that require S-OFF to work. There are, however, some roms that require a certain hboot, and for changing that s-off is required. But flashing an ICS rom should work with the stock hboot - in fact, Sandvold's builds seem to work best on stock hboot. So no need to s-off for now, except that you are stuck on your old recovery (which hopefully should also be able to handle touch input in aroma installer).
Click to expand...
Click to collapse
Ah great! Yes, I couldn't care if the recovery is not touch operatable, as long as it works! Will try Sandvold's ROM soon I thought you needed S-OFF to run ICS ROMS for some reason. Thanks!
TVTV said:
Your situation is a weird one. As far as i know, while being S-ON, you shouldn't be able to flash a custom recovery to your phone, yet you say you did. This leads me to believe that your phone might have been S-OFFed, at one point in time, by Unrevoked Forever. What Forever does is completely remove the S-ON RADIO flag instead of just messing with the bootloader. Ergo even if your bootloader is a stock one, reading S-ON, you're really still S-OFF. Please test this by trying to write stuff (i.e. copy a file) to your phone's system partition with a (root) file explorer of your choosing (while booted into Android, of course). If it works, then you're actually S-OFF thus meeting the ICS ROM's requirement. If it does not, then something's amiss.
Regarding the USB port, i'm not trying to offend your skills in any way, but please boot the phone into HBOOT, switch to fastboot mode and then try connecting your phone to a PC using a different USB cable. If HBOOT reads FASTBOOT USB instead of just FASTBOOT, then you have an USB brick on your hands. I'm insisting because i haven't heard of a problem such as yours. Usually, when the USB port goes, it goes completely.
Click to expand...
Click to collapse
Root access read and write works fine, HBOOT reads FASTBOOT. So it looks like I do have S-OFF, but my HBOOT is reporting that incorrectly? :S
Either way, i'll try a new ROM and let you know how it goes.
So the USB port really is shot. Well, that's a shame, but if you can WRITE to the /system partition while Android is booted, then you're S-OFF via Unrevoked Forever and a working USB port is not needed anymore, as you can flash bootloaders from the USB card (if needed).
For wireless file transfers, do try Airdroid. It's free and, furthermore, GREAT!
TVTV said:
So the USB port really is shot. Well, that's a shame, but if you can WRITE to the /system partition while Android is booted, then you're S-OFF via Unrevoked Forever and a working USB port is not needed anymore, as you can flash bootloaders from the USB card (if needed).
For wireless file transfers, do try Airdroid. It's free and, furthermore, GREAT!
Click to expand...
Click to collapse
UPDATE: So I just installed Sanvold's ICS ROM, no worries, running smooth Now that I understand more about hboots I realise the stock hboot is fine, and USB is not necessary anymore.
Yeah, Airdroid rocks! Been using it for a while now, very useful if you have no reception in your room but you can SMS if you put your phone near a window or something
Related
i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
just done the hboot hing and at the top of screen it says
vision pvt ship s-on
hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685
OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1
try wiping all the caches...
Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
So, after messing around with my "new" replacement EVO and getting it rooted (successfully with HBOOT 2.1, 2.6.32.15 Kernel, ROM back to stock Sprint 3.29.651.5, baseband 2.15.00.09.01), I decided to try and put Warm's ROM back on it. That was all fine and dandy until I rebooted with the ROM on my SD and went into recovery... to get the little Angry Red Triangle of Death. Even though it's showing as SOFF, when I ADB in (via FASTBOOT), it won't let me push anything and acts like it's not rooted; TB/WH/etc... aren't working either.
That being said... how do you go about flashing a new recovery when HBOOT won't properly read the PC36IMG.zip file? It reads it and does its little break out thing for the individual components, but then never gives me an option to flash it. Obviously, I can't flash any IMGs via ADB because the phone thinks that it's not rooted... am I semi-screwed? I can probably find a way to brick it and take it back to Sprint for another one, but I'd rather fix it myself than take the dishonest path.
Any help is much appreciated in advance. Let me know if I can answer any other questions that need answering. Radios are also the latest, IINM, and if it even matters.
*edit* Also, I was stuck in a boot lock at the white HTC screen previously, which I fixed by running an older Sprint RUU while it was connected via fastboot. Did that potentially make things worse?
What hardware version do you have? I am guessing since you have 2.1 h boot, that, you may have 004 hardware. Also I'm not sure what root method you used, but I would try and re-root using unrevoked then see how it affects your recovery.
I have no idea if this would work, but try flashing a recovery through rom manager. However, is your bootloader borked?
eventer289 said:
I have no idea if this would work, but try flashing a recovery through rom manager. However, is your bootloader borked?
Click to expand...
Click to collapse
Nope, bootloader seems to be fine. I can get into it and it reads the PC36IMG files but just doesn't want to load them up and/or try to install them. Everything else in the regular bootloader menu works too, past recovery.
Hardware version is indeed 0004. Does that make any difference? I couldn't find anything in the FAQs about whether or not hardware version makes a difference with the newest ROMs.
Hi all
For the last few weeks I have been trying to fix my HTC Desire back to some sort of working state. After awhile, I managed to get back to stock (from CM7), but soon realised I had the USB brick and SD Card issue. For info I used the stock HTC 2.3 Gingerbread RUU and used Alpharev PB99IMG_downgrade.zip for HBOOT (I was using Alpharev S-OFF with CM7).
So, I followed this guide, http://android.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/ and managed to mount the SD Card. However, I could not get the update.zip file to apply because I was no longer rooted.
So I followed the guide linked in the USB brick article, http://android.modaco.com/topic/307...ide-now-with-hboot-080-and-os-to-121-support/ and soon realised that I did not have the HBOOT version required. Either 0.75 and below, or, 0.80 and below. I have 1.02.0001.
Not a problem, I thought. I will follow this guide to downgrade, http://forum.xda-developers.com/showthread.php?t=768256 as it specifically says that "...the downgrade does not depend on any version of HBOOT" which is what I need. However, first step is to get a working Goldcard. This is where I start to get into trouble and I'm already losing track of what I'm doing, but I soldier on...
How do I create a Goldcard? I followed this guide, http://android.modaco.com/topic/305672-creating-a-goldcard/ and got stuck at running the ADB command as because my USB is broken, Windows 7 (x64) refuses to see the Phone. Luckily, my father has the same phone, so I put my SD Card into his Desire and managed to create a Goldcard (he is running CM7 on his Desire too).
So Goldcard in hand, I go back to the downgrade guide and then spot my next issue. I can't get Windows to see the phone to use ADB commands and I also can't get Windows to see the phone when it is booted up (the charge light won't even come on now), meaning I can't run the downloaded application.
Not to be outdone I went back to the Rooting Guide and tried both of the downloads with the "step1-windows.bat" command just in case they did work, but both give an error, which on searching, is to do with the HBOOT version being incompatible.
I tried putting on the PB99IMG_downgrade.zip file from Alpharev again, then re-running the HTC 2.3 Gingerbread stock RRU and taking the ROM.zip folder and re-loading it on to the phone, but it hasn't changed the HBOOT version. So my cry for help is.... how can I downgrade HBOOT without using ADB commands or having to have Windows detect my phone? I'm basically stuck with Fastboot and my SD Card.
Even though my phone looks stock, I can't call people as it disconnects straight away, the USB is broken and the battery drains stupidly quickly.
Thanks for any help!
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
bortak said:
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
Click to expand...
Click to collapse
Hi bortak,
Thanks for the reply. It is a bit of a strange situation I agree. I've been putting off signing up and posting for help as I feel quite dumb for breaking my own phone, but I have to admit defeat on this one.
I saw your reply also in this similar topic, http://forum.xda-developers.com/showthread.php?t=1290391, so I will definitely try your suggestion and report back.
Appreciate you taking the time to post.
Thanks.
USB Brick on official GB 2.3.3 and HBoot 1.02
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
dexterm1 said:
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
Click to expand...
Click to collapse
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
bortak said:
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
Click to expand...
Click to collapse
I´ll have a try
just fixed my desire 1 hour ago and it works.
look at this http://forum.xda-developers.com/showthread.php?t=1296916
What I did:
I was able to connect my pc and phone through wi-fi and adb worked (adb connect phones-IP-address ) and then pushed, chmod'd 755 and executed zergrush. Gained root via cmd with adb shell in windows and after that I just pushed flash_image and mtd0.img to phone and ran it like you supposed to in the guides (chmod 755 and execute). Rebooted and voila! USB connection is working and now my phone signal isn't dropping anymore - phone fixed!
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
dexterm1 said:
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
Click to expand...
Click to collapse
Hi, pls. tell us how did you managed to connect your unrooted phone over wifi with adb? I get only "unable to connect to ... ip ..."
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
exocetdj said:
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
Click to expand...
Click to collapse
I can not install anything without root, and i can't root 2.3.3 software.
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
exocetdj said:
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
Click to expand...
Click to collapse
Ignore this, you can't root 2.3.3 with unrevoked
r5_alpine said:
I can not install anything without root, and i can't root 2.3.3 software.
Click to expand...
Click to collapse
Use revolutionary instead
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
eddiehk6 said:
Ignore this, you can't root 2.3.3 with unrevoked
Use revolutionary instead
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I can't do both of this, because my phone is not recognized by PC in any way, i must root it without PC.
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
matus.karahuta said:
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
r5_alpine said:
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
Click to expand...
Click to collapse
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
matus.karahuta said:
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
Click to expand...
Click to collapse
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
r5_alpine said:
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
Click to expand...
Click to collapse
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
matus.karahuta said:
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
Click to expand...
Click to collapse
The phone is not seen by pc in any statement, not in bootloader, or fastboot, or recovery. I need to either downgrade to 2.29 rom version, or to root it in some way.
I am stuck on my Desire: I have no telephone connection anymore.
I am on S-Off Data++ with BCM RC4.0.
I really want to know the best way to get the phone back to stock but I do not know how as I have no USB connection.
If I sent it to HTC they want a stock phone.
Suggestions much appreciated!
BarnOwl said:
I am stuck on my Desire: I have no telephone connection anymore.
I am on S-Off Data++ with BCM RC4.0.
I really want to know the best way to get the phone back to stock but I do not know how as I have no USB connection.
If I sent it to HTC they want a stock phone.
Suggestions much appreciated!
Click to expand...
Click to collapse
Check the development section for USB brick fix. You'll find the description there.
Best regards Coempi
I am just looking for a way to flash a stock rom to the device. This is the first time I am stuck with a smartphone since 2002!
I do not want to do a usb de-bricking method as I am going to sent it in. But I doubt they will give me any service if I bring a modified Desire in.
BarnOwl said:
I am just looking for a way to flash a stock rom to the device. This is the first time I am stuck with a smartphone since 2002!
I do not want to do a usb de-bricking method as I am going to sent it in. But I doubt they will give me any service if I bring a modified Desire in.
Click to expand...
Click to collapse
In order to use the USB you have to fix the USB brick. After that you can flash a custom recovery, a stock rom, whatever you want.
So you're saying there is no way to achieve this otherwise? I thought maybe there is a stock rom that can be applied through the sd card.....
I'll try that USB brick anyway, thanks!
Funny thing is: Yesterday I lost my G2/G3 connection, then I started to get another rom because I thought it had something to do with that and then my USB went completely dead. HTC said it probably is a "software" problem.
BarnOwl said:
So you're saying there is no way to achieve this otherwise? I thought maybe there is a stock rom that can be applied through the sd card.....
I'll try that USB brick anyway, thanks!
Funny thing is: Yesterday I lost my G2/G3 connection, then I started to get another rom because I thought it had something to do with that and then my USB went completely dead. HTC said it probably is a "software" problem.
Click to expand...
Click to collapse
When you cannot access your phone via USB, that's called a USB brick, so give the fix a go.
Best regards Coempi
Help....really stuck now!
Ok, guys, here's the deal:
Somehow HTC decided I had voided my warranty as I said I had downloaded the REGULAR updates from their site.........(????) So now I am stuck with a bricked Desire.
I have downloaded the Alpharev downgrade boot and I have a 2.33 Android RUU on it. Version 3.14.405.1. The 5.17.05.23 radio is on there as well.
If I boot in Hboot I see the following:
BRAVO PVT3 SHIP S-ON
HBOOT-1.02.0001
MICROP-0514
TOUCH PANEL-SYNTH0101
RADIO 5.17.05.23
Jul 22 2011.16.19.16
That's what I got from the Alpharev s-off site (downgrade hboot)
Charging via USB works. SD can be accessed (That's how I have been trying the last few days to get it back to normal via PB99IMG.zip.
But I really don't know how to get the USB functionality back and it doesn't recognise the fastboot drivers and so on.
I.m pretty sure it is not a hardware problem as I had the cables checked in a repair place.
Surely there must be a smart wizard out there that can help me?
AFAIK u have to be s-off to flash H-boot
and the ruu runs from your computer
colin_404 said:
AFAIK u have to be s-off to flash H-boot
and the ruu runs from your computer
Click to expand...
Click to collapse
I know that......but what H-boot do you want me to put on it?
If you extract the rom.zip from the ruu, you can also put it on the device by using the sd-update.
I also saw this recovery with build-in usb unbrick. But how to get it on the phone?
There is no point in putting any h-boot on the sd card
Rename the rom.zip to PB99IMG.zip
I'm fairly confident that your problem is to do with the RILs that were included as part of BCM 4.0. They tried including new RILs and it didn;t work for lots of people.
If you read the BCM home page it talks about this problem on the release notes
My 3G didn't work. I downloaded the RILs put them on my SD card. booted to recovery (I'm using 4EXT graphical user interface recovery) and then chose to install the old rills (it's just a zip file).
Really easy.
Alternative you could reflash BCM 4.1U2. I think you were just a bit unlucky!!
owennewo said:
I'm fairly confident that your problem is to do with the RILs that were included as part of BCM 4.0. They tried including new RILs and it didn;t work for lots of people.
If you read the BCM home page it talks about this problem on the release notes
My 3G didn't work. I downloaded the RILs put them on my SD card. booted to recovery (I'm using 4EXT graphical user interface recovery) and then chose to install the old rills (it's just a zip file).
Really easy.
Alternative you could reflash BCM 4.1U2. I think you were just a bit unlucky!!
Click to expand...
Click to collapse
Ok, thanks.......I got a bit tired of this issue so I got a new device. But I still have the Desire and I will definitely give it a go, have not tried that one yet. I'll report back here!
I have a problem. USB port in my DHD is down (neither charges nor connects to PC) and there's also a problem with the screen, so I have to send it to warranty service. It's rooted, S-OFF and custom ROM installed. How can I bring it back to official software without using USB?
http://forum.xda-developers.com/showthread.php?t=857537
To go back to S-ON:•Flash stock ROM (RUU, not over 1.7)
•Temproot using Visionary
•Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
•Enjoy your factory-state phone
http://forum.xda-developers.com/showthread.php?t=1151683
giannis-21 said:
http://forum.xda-developers.com/showthread.php?t=857537
To go back to S-ON:•Flash stock ROM (RUU, not over 1.7)
•Temproot using Visionary
•Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
•Enjoy your factory-state phone
http://forum.xda-developers.com/showthread.php?t=1151683
Click to expand...
Click to collapse
Thanks for reply, but am I right that the tool from first link requires to connect DHD to PC with USB cable? As I wrote USB in my DHD is down so I'm looking for a method which uses only SD card without USB connection.
Don't think that's possible. One thing you can try is the PDxxIMG.zip method of flashing stock ROM through bootloader (search). I really don't know if that'll restore the bootloader to stock though. Put the zip in the root of your SD card through a card reader. Your problem is clearly hardware only though, so worst case, I guess you can try to give it for service and claim warranty on grounds that it is an obvious hardware fault that cannot possibly have been caused by any software changes you made.
I also found this method: http://forum.xda-developers.com/showthread.php?t=1208507
It's made for Inspire 4G, if it worked for DHD I would use it and then flash RUU for DHD with SD card, but I'm not sure if flashing Inspire 4G ROM will be safe for my DHD.
Cossack_PL said:
I have a problem. USB port in my DHD is down (neither charges nor connects to PC) and there's also a problem with the screen, so I have to send it to warranty service. It's rooted, S-OFF and custom ROM installed. How can I bring it back to official software without using USB?
Click to expand...
Click to collapse
as shashank said above u can use pd98img.zip to restore to stock but s-on i dont think its possible but u never lnow
I know about it, my main concern now is whether flashing Inspire 4G RUU will break my DHD or not. If not, this would be way to restore S-ON.
I wouldn't try it. The hboots are different and can mess your phone up good. Also the Inspire has different hardware (Atmel screen; DHD uses Sharp I think). So I don't think a stock Inspire RUU will work.
Sent from my Desire HD using xda premium