Hi all,
So I need to send my phone back for repair meaning I need to return it to stock for the warranty to be valid. It's currently running Cyanogenmod.
I read on here that the best bet was just to install the official 2.3 ROM from HTC's site but because of some USB error I can't get it to work. See here for the error: http://androidforums.com/incredible-tips-tricks/161463-ruu-error-170-171-solution-windows-7-a.html
So now i'm looking for a 2.2 ROM to try. I've found one that's labelled RUU_Brav2_UK_1.20.207.1_Radio_32.36.00.28U_4.06 .00.02_2_release_124865.exe in the following thread:
http://forum.xda-developers.com/showthread.php?t=695667
I assume that's the right one for a UK Desire? It was bought unlocked so the network is irrelevant to me. So the first question is should I use that one or another (it will have SIMS from various networks in, not just O2)?
The second is, do I simply run the .exe from my computer as per the 2.3 ROM and if so, am I just going to get the same stupid USB error?
Not sure if it's relevant but HTC Sync can never see my phone. I'm guessing because of this USB thing.
Thanks in advance.
Woah there.
That's branded to o2. Having the wrong branded ruu is relevant as it Voids warranty.
Also its android 2.1 (software version starts with a 1) and many 2.1 were amoled only so if yours is slcd, your screen won't work.
For UK unbranded, you want 2.29.405.5 if you want 2.2. That said, you'll maybe still get a usb error.
By the,way, can only run ruu from fastboot screen (back plus power from off) if you're not running HTC Rom. HTC sync only sees HTC roms too, so that also explains that
Sent from my HTC Desire using Tapatalk
Thanks for the reply. So just to get this straight (and while I wait for my battery to charge enough to update):
1. download 2.29.405.5
2. Boot phone while holding back button to enable fastboot
3. run .exe
?
Thanks
Yes try that first. If you get the same errors, there is another route to go down...
Sent from my HTC Desire using Tapatalk
Assuming your phone has a custom rom counter, flashing it to stock won't reset it. You can always search for a fix, but if one isn't available, you might be screwed.
My post isn't to cause panic, but rather to make you aware. Double check to see if your phone has a rom counter, before sending it out.
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
PeartFan40 said:
Assuming your phone has a custom rom counter, flashing it to stock won't reset it. You can always search for a fix, but if one isn't available, you might be screwed.
My post isn't to cause panic, but rather to make you aware. Double check to see if your phone has a rom counter, before sending it out.
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
Click to expand...
Click to collapse
Wtf?
Op, ruu wipes and re writes everything on NAND. 100s of people have sent their phone back for warranty. No idea what this guy is talking about.
Sent from my HTC Desire using Tapatalk
rootSU said:
Wtf?
Op, ruu wipes and re writes everything on NAND. 100s of people have sent their phone back for warranty. No idea what this guy is talking about.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I was giving him a heads, just in case his device has a rom counter. As I stated in case his device had one, he should double check it. On my phone, only a special hack will reset the rom counter. All the wiping in the world won't reset it. It must be done using a special patch. If his device doesn't have one, then he has nothing to worry about. Relax....
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
PeartFan40 said:
I was giving him a heads up, just in case his device has a rom counter. As I stated earlier, in case his device had one, he should double check it. On my phone, there is a rom counter that keeps track flashes, which only a special hack will reset. All the wiping in the world won't reset it. It must be done using a special patch. If his device doesn't have one, then he has nothing to worry about. Relax....
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
Click to expand...
Click to collapse
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
PeartFan40 said:
I was giving him a heads up, just in case his device has a rom counter. As I stated in case his device had one, he should double check it. On my phone, there is a flash counter that keeps track of roms, only a special hack will reset the rom counter. All the wiping in the world won't reset it. It must be done using a special patch. If his device doesn't have one, then he has nothing to worry about. Relax....
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
Click to expand...
Click to collapse
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
Ooops, not sure why my response triple posted.
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
There is no "rom counter" on the desire and even if there was, upgrading the Rom officially on our phones does not void our warranty.
Out of interest, on your device, where does it store the result?
Sent from my HTC Desire using Tapatalk
rootSU said:
There is no "rom counter" on the desire and even if there was, upgrading the Rom officially on our phones does not void our warranty.
Out of interest, on your device, where does it store the result?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
As I previously stated, IF there was a counter. On Samsung phones, the counter is stored in the bootloader.
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
PeartFan40 said:
As I previously stated, IF there was a counter. On Samsung phones, the counter is stored in the bootloader.
Sent from my Galaxy S II (SGH-i777) using XDA Premium.
Click to expand...
Click to collapse
the htc RUUs overwrite also the bootloader, so the problem doesn't exists for us
the ruu restore and format everything (bootloader, radio, recovery, kernel, system, data, cache)
So finally got around to trying this and it doesn't work. I put my phone into the white screen with the little skateboarding androids on it and run the RUU. It hangs on the 'verifying information on your Android phone' screen then gives me a USB error 170.
Are there some other drivers for my phone I should be trying here. So frustrating.
rootSU said:
Yes try that first. If you get the same errors, there is another route to go down...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Hey so wondering what this 'other route to go down' you mentioned is?
I'm getting a USB error at a different stage now but I wonder if it's because I tried to install a different driver for the phone (which I've since deleted). Before it recognised the phone but hung when it tried to start the install.
Now it hangs on the verifying the information on your handset bit.
Is there a way to ensure i've totally removed any non working drivers and installed a good one?
Thanks
Related
Hi,
1. For a month ago i've learned how to root my galaxy s2, and since then i've flashed new ROM's and kernels almost every week, and thats because almost everyone told me that it was almost impossible to brick the phone.
In 2 days i will recive my new Galaxy Nexus, and i don't know if i will Root it or not, is it worth doing this to this phone?
thanks
People say it's almost impossible.. Just search the threads where people think they bricked their phones
It is EXTREMELY hard to brick the Galaxy Nexus.
And it is definitely worth rooting. There are some amazing ROMs and kernels available
Learning to root and use android from scratch, I bricked this fella at least six times, but mostly due to bad file transfers and user error.
Use a toolkit, wugfresh's makes it excessivlely easy.
Sent from my Galaxy Nexus using xda premium
I did not wipe data out before flashing, my phone could not start. I thought i bricked my phone but after went to recovery mode to wipe data, my phone worked fine.
As far as I know, the only time that you can brick this phone is when flashing bootloaders. For example, the lights go out during the 2 secs required to flash it. But the window of opportunity is so small you have to really be unlucky, and if you have UPS or do it on a laptop, that won't be a problem at all. The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
TwilightSparkle said:
I bricked this fella at least six times
Click to expand...
Click to collapse
So what you really mean, is that you didn't actually brick it once?
Lol - interesting thread...
I'll bet that I can brick one in a few minutes, so it can't be that hard... xD
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
thirtynation said:
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
Click to expand...
Click to collapse
No. As long as your volume button and power button are not broken, you can start into the bootloader and start over.
Bricking is a very final thing that one can not repeat on the same device. Once bricked, it's only good as a paperweight. If you can revive the device, then it was never bricked in the first place
Wrong radio will brick your device for certain. Kernel and ROM not so much...
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought I remembered reading that in some /r/android comments a few months ago. Thanks for confirming.
So since I'm on 4.0.2 running the leaked 4.0.3 radios, if I wanted to run 4.0.4 everything would you recommend just reverting back to pure stock 4.0.2 via this thread or similar method, and then going from there?
Vangelis13 said:
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
Click to expand...
Click to collapse
Not confirmed with this phone, but typically the bootloader will do an md5 type check, but recovery doesn't. If you disable signature verification in recovery, then it's all in your hands...
j.go said:
[snip]
The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
Click to expand...
Click to collapse
Not sure if the bootloader flow is the same on the Galaxy Nexus (probably not), but on the Nexus One, the bootloader will not flash a bootloader that is not signed. Period. Unless of course there is no NAND lock (i.e., S-OFF for HTC devices).
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
psycho2097 said:
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Dare you to flashable radio from another phone...
danger-rat said:
Dare you to flashable radio from another phone...
Click to expand...
Click to collapse
LOL!!!!!
Sent from my Galaxy Nexus using Tapatalk
I Dare y'all to flash the 4.0.4 update on a GSM phone. ;P
Sent from my Galaxy Nexus using xda premium
OK, I have found the wiki guide to return a phone to stock condition for warranty repair (part of the screen can't touch). I have a few questions...
You need to have radio S-OFF to follow this steps
Click to expand...
Click to collapse
How do I do this?
Please make sure that gfree_verify returns secu_flag = 0 before following this steps!!!
Click to expand...
Click to collapse
Huh?!?
If you main software version is higher than the version of the PC10IMG you want to install (in this case 1.19.531.1) you have to change the main version number in the misc partition.
Click to expand...
Click to collapse
What's the main software version? What's PC10IMG?
In case of the original T-Mobile G2 the stock rom is called PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
Click to expand...
Click to collapse
I have a Desire Z bought from Hong Kong. I suppose I will use:
RUU_Vision_hTC_Asia_HK_CHT_1.84.708.1_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168263_signed.exe
as
RUU_Vision_hTC_Asia_HK_CHT_1.34.708.3_Radio_12.28b.60.140e_26.03.02.18_M2_release_154602_signed.exe
is corrupt and won't execute?
Restore the backup of your partition 7.
Click to expand...
Click to collapse
What's partition 7? What does the file look like?
Geez, this guide sure is technical...there is a whole lot more there. It reads like it was written by an expert, as a sort of hand notes for what he did so he can follow it again later. It sure doesn't read like a easy-to-follow guide for novices like me.
well to start you were wondering if you have soff? did you root your phone yourself? do you know what guide you used? most of these steps are just reversed from optaining root and soff
you may want to boot into your bootloader (power on while holding volume down) and check your phone
nipqer also has a guide to follow, search the dev section for that, not @ a computer so can't easily link it to you right now but it is called something like "return to stock with broken digitizer) of course it will work even if your touch screen is fine
Sent from my HTC Vision using xda premium
Help
Some one should please help me. I gave my friend my HTC G2 for a research work. Some days later, he returned it to me pleading that i should forgive him. He mistakenly deleted my G2's Operating System and every other thing in it. Right now the phone is just blank. It boots up to the bootloader and displays the HTC Logo. Please, I am begging for any body with any solution to this. PLEASE I URGENTLY NEED YOUR HELP. THANKS
Were you rooted prior to this? Do you know what was done to make this happen? Can you boot to bootloader at all?
See if this helps at all
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my SGH-T839 using Tapatalk 2
Help
demkantor said:
Were you rooted prior to this? Do you know what was done to make this happen? Can you boot to bootloader at all?
See if this helps at all
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my SGH-T839 using Tapatalk 2
Click to expand...
Click to collapse
Yes I can boot to bootloader and the phone was rooted prior to the deleting stuff. It was rooted with super one click. When I opened my sd card, I saw Superwipe+4ext. When I confronted him yesterday, he said he just downloaded the stuff but didn't use it. I suspect he used that Superwipe+4ext to wipe out my phone because when I went online to read about this software, I was convinced that he used it. Thanks
The superwipe is safe to use, can you still boot to recovery?
Sent from my Nexus 7 using xda premium
Help
Yes I can boot to recovery.
Then flash a new rom
Sent from my Nexus 7 using xda premium
OK what? Urch make your own topic. Dont rob other's topics....
gromky, tell us about your phone: Is it rooted? Is it S-OFF? Do you know anything about your phone at all?
Hi Guys,
I managed to hard-brick my phone somehow. I sent it back to HTC already, but I just don't want to do it again. Can anyone figure out what did I do wrong?
Here is the story:
1, I've rooted the phone. I tried with the one-click root first, it did not work, but the other method involving unlocking the bootloader through htcdev.com and flashing CWM (endeavoru) and SuperSU worked.
2, I wanted to install my cmdsp update, which worked already in several devices (Nexus S, Galaxy Nexus, Nexus 7, Galaxy S III). I flashed the exact version which was in the thread (that one is created from the Galaxy Nexus CM9 distro (maguro)).
3, The device booted, but then got frozen on the UI. I hesitated what to do next.
4, I thought that maguro is not binary compatible with my device, so I downloaded CM10 from this thread, extracted the necessary files and created an update.zip for this device, then flashed it.
5, It got flashed nicely, but then the phone did not boot anymore.
It had 100% battery before, but long-pressing power button did not do anything. No way to get into hboot mode, and the device is not recognized as an USB device if plugged into a mac (sorry, no windows at home). The led does not even light up if I plug it to the charger.
So, the question is: what did I do so wrong that it got hard-bricked. I might get another device from HTC, I might need to pay for that, I don't know, but I do not want to repeat this mistake.
Do not flash other phone's **** into ur phone..
No human can take horse's penis in ass
Same way phone doesn't take other phone's **** into own..
Sent from my HTC One X using Tapatalk 2
sumeshd said:
Do not flash other phone's **** into ur phone..
No human can take horse's penis in ass
Same way phone doesn't take other phone's **** into own..
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
This is an update.zip, I flashed it to many other ARM-based device with no problem (ICS, JB).
Because you don't read and experiment, that's why.
Laurentius26 said:
Because you don't read and experiment, that's why.
Click to expand...
Click to collapse
Don't read what? The doc of the update.zip that I made myself? This update.zip installs some libs into the /system partition. What can go wrong about it?
You got the SAME responses on the SAME thread you started in the at&t, rogers, telestra One XL forum. Tho your story didnt add up over there. Looks like u just need to come to terms with it amigo:beer:
#2 - CRAP Flashing doesnt pay
dlux.hu said:
This is an update.zip, I flashed it to many other ARM-based device with no problem (ICS, JB).
Click to expand...
Click to collapse
Almost every Android has an ARM architecture CPU, doesn't mean you can flash whatever you want onto every phone.
Sent from my HTC One X using xda app-developers app
Because you overwrote your hboot when flashing the device?
Try running the JB Firmware Flasher.
Sent from my HTC One X using xda app-developers app
Actually I'm very interrested in what you flashed exactly?
With a S-ON device it should not be possible to flash anything that will hard-brick your device. So maybe you could post it for me?
EDIT: The ZIP you are linking to in your other thread could never have hard-bricked your phone. On a S-ON device it is impossible to flash onto a protected partition. So something else must have happened!
It is indeed possible to hard rbick an son device only by simply flashing a rom and boot.img meant for your device.
Recently it happened in the one x community when an (anonymous) developer released a rom and several people got bricked because of it.
Sent from my One X using xda premium
TToivanen said:
It is indeed possible to hard rbick an son device only by simply flashing a rom and boot.img meant for your device.
Recently it happened in the one x community when an (anonymous) developer released a rom and several people got bricked because of it.
Sent from my One X using xda premium
Click to expand...
Click to collapse
There is no boot.img in the ZIP he links to, only libraries and an APK file. I highly doubt that could hard-brick a S-ON device, but who knows.
Hey guys,
Before I get teared apart limb from limb, I tried searching for rooting on the new software and didn't really come up with any guides.
So, anyway. I just got my upgrade HOX in the mail, and I'm so excited! Of course, I've been on XDA before and rooted and customized and flashed to my heart's content, but I need some help.
Would someone lead me to a guide for rooting HOX on the NEW software? I just got my new kit today, I don't know if it automatically updates or not. I pretty much want to learn how to get to flashing a ROM.
Thanks!
C
i used this no problems.
http://forum.xda-developers.com/showthread.php?t=1577671
cappyandroid said:
Hey guys,
Before I get teared apart limb from limb, I tried searching for rooting on the new software and didn't really come up with any guides.
So, anyway. I just got my upgrade HOX in the mail, and I'm so excited! Of course, I've been on XDA before and rooted and customized and flashed to my heart's content, but I need some help.
Would someone lead me to a guide for rooting HOX on the NEW software? I just got my new kit today, I don't know if it automatically updates or not. I pretty much want to learn how to get to flashing a ROM.
Thanks!
C
Click to expand...
Click to collapse
Use it as stock for a few weeks at least to rule out any manufacturer hardware issues.
Update via the OTA check for updates in settings. (2.17 is the latest)
------
The when you want to play with custom, root of etc....
Install Android SDK
1st step is unlocking the bootloader via HTCdev
Then flashing clockworkmod touch recovery
Then flashing a rom of choice, all which have root I think.
Sent from my HTC One X using XDA Premium HD app
chrisjcks said:
Use it as stock for a few weeks at least to rule out any manufacturer hardware issues.
Click to expand...
Click to collapse
I would actually emphasize this. So many people have had hardware issues and it will be a struggle to get the phone repaired after rooting via HTCDEV. Spare yourself trouble and give some time to rule out those problems.
Besides you can use that time to get to know the available roms, issues with them and the rooting/flashing process
chrisjcks said:
Use it as stock for a few weeks at least to rule out any manufacturer hardware issues.
Click to expand...
Click to collapse
I also came here to post exactly this
akselic said:
I would actually emphasize this. So many people have had hardware issues and it will be a struggle to get the phone repaired after rooting via HTCDEV. Spare yourself trouble and give some time to rule out those problems.
Besides you can use that time to get to know the available roms, issues with them and the rooting/flashing process
Click to expand...
Click to collapse
Sorry I'm just trying to learn here but here I go. Are their any complications of using HTC to unlock the bootloader meaning can't the boot loader be relocked if he is trying to send it in for repairs?
Sent from my Nexus S using Tapatalk 2
TG2708 said:
Sorry I'm just trying to learn here but here I go. Are their any complications of using HTC to unlock the bootloader meaning can't the boot loader be relocked if he is trying to send it in for repairs?
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
It can be relocked but unlocking the first time sends HTC a notion that your device has been unlocked. And there are several people that are having a tough time getting their phones repaired even though the issues are hardware.
Depending on the country and law it is possible to force them to repair or replace a faulty device but trust me, that process will be a lot faster and simpler if you haven't tampered with the bootloader.
An irrelevant response but that's why I will always go the nexus route when buying android so I could avoid most if not all these issues.
Sent from my Nexus S using Tapatalk 2
Help with HTC One X ATT version
Hi Guys,
So I have unlocked my HTC One X ATT version using the HTCDev.com site. Now I want to install clockworkmod so I can proceed with custom ROM installations. But all the links that I find to CWM are dead.
Can someone point me to the live links please? I am itching to get the CM10 rom installed on my HOX.
Please note there are plenty of sites and links for international version of HOX but I want for ATT.
Thanks,
jhawk_007
jhawk_007 said:
Hi Guys,
So I have unlocked my HTC One X ATT version using the HTCDev.com site. Now I want to install clockworkmod so I can proceed with custom ROM installations. But all the links that I find to CWM are dead.
Can someone point me to the live links please? I am itching to get the CM10 rom installed on my HOX.
Please note there are plenty of sites and links for international version of HOX but I want for ATT.
Thanks,
jhawk_007
Click to expand...
Click to collapse
Can CWM version on HOX Tegra 3 international work on an AT&T model?
I'd supply you my CWM touch, but i don't want to if it won't work.
As I'm unsure, I'll leave this up to you to decide.
Sent from my Nexus 7 using XDA Premium HD app
chrisjcks said:
Can CWM version on HOX Tegra 3 international work on an AT&T model?
I'd supply you my CWM touch, but i don't want to if it won't work.
As I'm unsure, I'll leave this up to you to decide.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried CWM version but it does not work. The phone goes into loop when I try to boot it into recovery mode.
Thanks for the response though...
jhawk_007
jhawk_007 said:
I tried CWM version but it does not work. The phone goes into loop when I try to boot it into recovery mode.
Thanks for the response though...
jhawk_007
Click to expand...
Click to collapse
You'd be better off asking in the AT&T One X section of this forum. I didn't think you could even use htcdev with it.
jhawk_007 said:
I tried CWM version but it does not work. The phone goes into loop when I try to boot it into recovery mode.
Thanks for the response though...
jhawk_007
Click to expand...
Click to collapse
This is what you're looking for:
http://techerrata.com/file/twrp2/evita/openrecovery-twrp-2.2.2.0-evita.img
Found it through this thread:
http://forum.xda-developers.com/showthread.php?t=1677447
And these are the forums where you should go for an AT&T HTC One X:
http://forum.xda-developers.com/forumdisplay.php?f=1538
If you have a ATT HTC One X, get off this forum, go to the proper section, and never come back here. Flashing any rom here will permanently brick your device.
Sent from my Inspire 4G using Tapatalk 2
Hi, I know its seems strange to u but I want to hard brick my phone. I've a bootloader locked unrooted phone, everything is stock. It has frequent flickering problem but couldn't show it to the service centre guys. So they are not believing this problem. So I need a sure shot method so I can replace my one V as I'm still covered under warranty. I tried the 0% battery drain method n vol+power button combination but none of them works. Please help guys, I need to fix this problem. Please help.
Sent from my HTC One V using xda premium
Uhm, i think one of the methods is just put an wrong root on your phone so it bricks, but then you lose your warranty.........
Sent From My Rooted Samsung Galaxy S2 JB 4.1.2 (GT-I9100)
Yes can do that then I need unlock my bootloader which would void my warranty. Can you please confirm if my phone is bricked, would the service center be able to understand that??
Sent from my HTC One V using xda premium
They can fix it, but i think they dont understand, all those jerks want money.
Sent From My Rooted Samsung Galaxy S2 JB 4.1.2 (GT-I9100)
Probably I will install a custom rom first to check if this flickering is problem is still there or not. If not then fine, otherwise I'll unlock the bootloader n atleast soft brick it (if not hard brick). Then will take it to service. Seems like there is not much option left now. Btw thanks dude for your help.
Sent from my HTC One V using xda premium