Related
[USB-BRICK] All you need to know about USB-Bricks
Fix here: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ or http://forum.xda-developers.com/showthread.php?t=691639
What is this thread for?
The main goal of this thread is to inform all Desire owners of the USB-Brick.
Especially the ones considering rooting / flashing ROM's.
And of course the people who have already bricked their phone...
There's many threads about rooting and current development on the matter,
but a thread that summarizes the issue was lacking in my opinion.
Index
What is this brick you're talking about?
How to recognize a USB-Brick?
When does this bricking occur?
Any numbers on this bricking?
I want to root and/or flash ROM's, what should I do?
I can wait, but for what?
I'm USB-Bricked what should I do?
Fix for SD Card and (maybe) Cellular Radio
Proxity Sensor Bug, never heard of it?
I'd like to return my device and want to flash an official ROM, how can I do that?
Disclaimer
This thread is useful, how can I help?
Sunday 30 May
Tuesday 1 June
Thursday 3 June Paranoid Rooting.
[*]What is this brick you're talking about?
The brick known as USB-Brick will mess up the USB Connectivity with the Desire.
How to recognize a USB-Brick?
Symptoms:
Unable to connect your phone using USB when booted into Android.
Unable to connect your phone using USB in Custom/Pushed Recovery.
FM Radio Malfunction.
Bluetooth Malfunction.
Wall charging doesn't start immediately.
Radio Malfunction. (Fix below)
SD Card Malfunction. (Fix below)
[*]When does this bricking occur?
Unfortunately it happens randomly. Some people experience it at their attempt at rooting,
others after 10 times of successful flashing. And there's people out there who have flashed
their device a 100 times and they're still fine.
Some people have blamed flaky USB Connections (through Cables and Hubs), others thought it was Apps2SD.
But it also occurs with all possible precautions and without Apps2SD, so noone really knows...
[*]Any numbers on this bricking?
On MoDaCo some guy named 'afiorillo' started gathering info from all flashing users.
This thread can be found here: http://android.modaco.com/content/h...-usb-disabling-bricking-issue-data-gathering/
'eVil D:' also started a poll in http://android.modaco.com/content/h...-or-legends-lets-get-a-count-55-and-counting/
but this thread is outdated.
This is the current poll: http://android.modaco.com/content/h...-or-legends-lets-get-a-count-66-and-counting/
[*]I want to root and/or flash ROM's, what should I do?
You can now, since the fix is out, make sure you backup the misc partition /dev/mtd/mtd0 in case it gets corrupted, it's very easy to flash the
original image back.
I'd suggest you use PaulOBrien's r5 rooting method. r5 added a nohup, which should prevent recovery from ending because of a flaky USB connection during flashing.
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/
ahmgsk released a different custom recovery http://forum.xda-developers.com/showthread.php?t=689778
This recovery supports wiping of ext partitions which is usefull for people using Apps2SD.
The method behind both recoveries is the same, so that might be because fewer people are willing to take the risk.
ahmgsk flashes over 30 times a day and his phone is fine. But this is no guarantee.
'ieftm' on XDA mentioned this command for linux
sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
See here: http://forum.xda-developers.com/showpost.php?p=6624079&postcount=81
And ahmgsk has updated his recovery script with this line.
[*]I can wait, but for what?
You can still wait for a safer recovery (one that doesn't corrupt the misc partition)
[*]I'm USB-Bricked what should I do?
Get it fixed, follow this link: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
You have two options here; fix what you can and wait for a fix or you send your device back. If you chose the latter, they will most likely replace your mainboard.
You might want to revert to a non-rooted official ROM even though this won't fix your problem.
[*]Fix for SD Card and (maybe) Cellular Radio
Boot into fastboot. Open a terminal. Navigate to folder where fastboot binary is located (Android SDK or whatever you used for rooting your phone)
fastboot oem enableqxdm 0
Source: http://forum.xda-developers.com/showpost.php?p=6634033&postcount=115
[*]Now I have cellular reception, but in calls I lose the connection after a few seconds?
This is called the 'Proximity Sensor Bug'.
It's unknown if it's related to the USB-Brick or the ROM you were flashing.
[*]Proxity Sensor Bug, never heard of it?
It seems that due to this bug cellular connection is lost whenever the screen turns off.
But there's no fix for this issue. And only a small subset of the USB-Brickers
has this problem.
[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
Be wary that you can't downgrade your bootloader.
[*]Todo
Proper formatting for the forum.
[*]Disclaimer
This summary is a result of me gathering information from both XDA-developers forum and MoDaCo forum + IRC for several days.
If you believe that something is wrong or missing, feel free to PM me so I can correct/add it.
[*]This thread is useful, how can I help?
If you're also into this issue, you'd do me (and many others) a favour by using this thread to keep us updated with interesting links to other topics, tweets or quotes from IRC.
Keep it short and simple.
[*]Sunday 30 May
ahmgsk updated his recovery with ieftm's recovery command line.
http://forum.xda-developers.com/showpost.php?p=6634416&postcount=3
[*]Tuesday 1 June
Integrated the fix into the whole story.
[*]Thursday 3 June - Paranoid Rooting
Since there's still no new recovery that prevents USB-Bricks from happening, I've added a few simple steps to the original rooting process to make it even easier when you brick your device the first time.
[-] Perform step 1 of the rooting guide.
[-] Boot your device as your normally would
[-] Check SD and USB functionality, if all is well, continue at [a]
[-] If you're already bricked, which is highly unlikely, continue at
Do the USB-Brick Fix, and save the working misc.img somewhere safe and skip [a]
[a] Backup your mtd0 / misc partition while it's still good, to do this, open a shell, become root by typing 'su' and then '/mount /sdcard' type: 'cat /dev/mtd/mtd0 > /sdcard/mtd0.img' to copy the contents of this partition into /sdcard/mtd0.img and save the proper misc.img somewhere safe.
[-] Continue with step2 of the rooting process and flash the rootedupdate.zip, or any other custom Rom.
[-] Happy flashing.
Very useful guide.
Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Recovery Getting update
nothing major ->
just addition of ->
'ieftm' on XDA mentioned this command for linux
sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
Click to expand...
Click to collapse
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update
oawalker said:
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update
Click to expand...
Click to collapse
If you are rooted there is no point in un-rooting! You can't do any damage unless you are in recovery and flashing. Stick with your current rom and sit tight for a new recovery
There's no reason to unroot if you've successfully rooted. The only risk comes when actively flashing the device - i.e. you've already gotten past the part where you could have broken it. There's no reason to go back - just sit tight where you are until it's fixed.
Edit:\\ Wow, nice timing, sock. Great minds think alike.
as my firend say in upper case
very usefull guide,m8
10ks
pls continue with exelent job
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device to be connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)
bee55 said:
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)
Click to expand...
Click to collapse
Details are in the first post here by Rudolfje.
[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/ht...ur-htc-desire/
Be wary that you can't downgrade your bootloader.
Click to expand...
Click to collapse
You can connect in fastboot mode, where USB still works, and flash one of the official RUUs. This will completely restore the phone software-wise, but will not restore USB-related device function.
I'm going to bow out here for now and let you carry on Prof. lol. There is no point in us both answering the same questions, and I have to get my house in order for the mrs coming over
OK, thanks for the reply. I just wasn't sure if you can still establish some kind of USB connection after the brick. I m off to flash froyo then .
socktug said:
I'm going to bow out here for now and let you carry on Prof. lol. There is no point in us both answering the same questions, and I have to get my house in order for the mrs coming over
Click to expand...
Click to collapse
Hah, my fault. Have a good one.
Good luck, FroYo flasher!
recovery just got v1.1 -> now u can start recovery via pc
then remove usb
still recovery works
ahmgsk said:
recovery just got v1.1 -> now u can start recovery via pc
then remove usb
still recovery works
Click to expand...
Click to collapse
This sounds ideal, nice work, AHMGSK you are prolific with your work on the desire, the desire comunity would be far less interesting without you so thanks
Does usb-bricking only happens with Desire? or n1 is also prone to that?
The Desire and the Legend. The N1 has an easy unlock, there's no worries.
Lots of people are now attributing this bricking issue down to using a usb hub.... I heard up to 85 percent of people bricked are using hubs.
Any thing that might help is a step forward,
JD
JupiterDroid said:
.... I heard up to 85 percent of people bricked are using hubs.,
JD
Click to expand...
Click to collapse
really, is this true? can we ask anyone here who is bricked to confirm this - if you are usb-bricked just post a quick ' yes bricked using hub ' or not !
For numbers, check out this thread\post: http://android.modaco.com/content/htc-desire-desire-modaco-com/309615/all-users-usb-disabling-bricking-issue-data-gathering/#
Yes, it looks like a very common question, but I used to own HTC-Wildfire once.
After installing custom ROMS, I have problems with battery malfunction. Untill now, I cannot fix it even if I brought a new battery.
I had purchased HTC One X, before I have found that the official ROM is not the best. I would like to try CUSTOM ROMS, but I'm afraid that it will make my mobile phone out of warranty.
However, I heard that after unlocking bootloader, we can lock it again and install an official ROM but the status of the phone will show " re-lock " instead of lock.
That means someone will know that I used to unlock it.
What do you think about this? Can I do it and also make it restore as untouched when my phone need fixing?
Thank you in advance.
KhSom
It will show re-lock, and I guess this is the purpose.
khom27820 said:
Yes, it looks like a very common question, but I used to own HTC-Wildfire once.
After installing custom ROMS, I have problems with battery malfunction. Untill now, I cannot fix it even if I brought a new battery.
I had purchased HTC One X, before I have found that the official ROM is not the best. I would like to try CUSTOM ROMS, but I'm afraid that it will make my mobile phone out of warranty.
However, I heard that after unlocking bootloader, we can lock it again and install an official ROM but the status of the phone will show " re-lock " instead of lock.
That means someone will know that I used to unlock it.
What do you think about this? Can I do it and also make it restore as untouched when my phone need fixing?
Thank you in advance.
KhSom
Click to expand...
Click to collapse
khom27820 said:
Yes, it looks like a very common question, but I used to own HTC-Wildfire once.
After installing custom ROMS, I have problems with battery malfunction. Untill now, I cannot fix it even if I brought a new battery.
I had purchased HTC One X, before I have found that the official ROM is not the best. I would like to try CUSTOM ROMS, but I'm afraid that it will make my mobile phone out of warranty.
However, I heard that after unlocking bootloader, we can lock it again and install an official ROM but the status of the phone will show " re-lock " instead of lock.
That means someone will know that I used to unlock it.
What do you think about this? Can I do it and also make it restore as untouched when my phone need fixing?
Thank you in advance.
KhSom
Click to expand...
Click to collapse
Your phone will still be in warranty in case of any hardware defects however should you break your phone as a result of flashing firmware then HTC will not assist you.
Yes, I believe that ANY rooting (and therefore ROM changes) voids the warranty of ANY phone however there are ways of unrooting your phone so that it appears completely unrooted.
Here's one method that may work: http://forum.xda-developers.com/showthread.php?t=900875
However if you use a program such as superoneclick, ginerbreak, etc then an unroot feature is often included.
I believe that these methods don't leave an obvious trace, thus allowing a warranty claim to be made.
dr9722 said:
Your phone will still be in warranty in case of any hardware defects however should you break your phone as a result of flashing firmware then HTC will not assist you.
Click to expand...
Click to collapse
That means if something wrong to my phone such as the screen is broken, I can still claim it, right?
If it is, I will begin to unlock my phone and install other ROM doubtlessly.
dr9722 said:
Your phone will still be in warranty in case of any hardware defects however should you break your phone as a result of flashing firmware then HTC will not assist you.
Click to expand...
Click to collapse
I had to send my HOX back to the shop because of a dodgy touchscreen. Of course, I had already installed ARHD so I was faced with the same issue. I reinstalled the proper RUU and relocked my bootloader. The shop accepted my RMA after finding the defect and told me that they had sent the phone to the HTC Service Center. So as of now the phone is wherever that is awaiting repair. The jury is still out as to whether they will investigate if the bootloader is relocked. I don't think it will be an issue, but I will report back as soon as I get word!
Cheers,
Mathieu
ps - I will change my signature as soon as I get my HOX back...
HTC will still honor warranty claims even if your phone was unlocked via HTCdev. The lcd on my One X decided that it would display the screen whenever it wanted to and not when I did. I called HTC and opened a ticket, shipped it to them, paid their slightly frustrating $20 USD handling fee, and now it's in repair with nothing else I need to pay.
This is with a unbranded HTCdev unlocked phone that had at least 4 different ROMs flashed as well as 2 kernels.
As far as your question of dodging the RE-LOCKED screen:
Until someone finds a way to S-OFF, we're stuck with it. But believe me that RE-LOCKED looks a whole lot better in HTC's eyes than TAMPERED.
If all you want to do is flash ROMs, just do it the HTC provided way.
Unless you manage to fry your phone by overclocking to 2.5ghz or overvolting, you'll be fine if the phone breaks.
Hi guys,
Just an update. I just received an email in which I was informed that my HOX has been repaired/replaced (I wonder which it is?). So either they didn't check the bootloader (or any secret log files of what has been installed) or they just didn't care. It would seem to have gone well...
Hi everyone! Here is the thing that is bothering me. I bought my phone month and a half ago. I recently unlocked bootloader, installed CWM, rooted it, changed kernel to Titanium KISS and overclocked it, while running stock rom. I have worries because many users reported that their phones suddenly died in 2 months period from purchase. What to do if that happens? I guess that my cell operator wont accept warranty if I give them unlocked and rooted phone back. What is your suggestion?
empyting ur pockets if system partition isnt burned up
I'm thinking to put it all back to stock and wait for another month to see how the phone will behave. :/
BGmaster said:
I'm thinking to put it all back to stock and wait for another month to see how the phone will behave. :/
Click to expand...
Click to collapse
If the phone is rooted (BL unlocked) the warranty is void as is.
If you get the QHUSB (dead) mode, and cannot resurrect the phone via the tool, it is quite possible, that you can claim warranty, given that even the manufacturer cannot read back anything from the phone.
Ken-Shi_Kun said:
If you get the QHUSB (dead) mode, and cannot resurrect the phone via the tool, it is quite possible, that you can claim warranty, given that even the manufacturer cannot read back anything from the phone.
Click to expand...
Click to collapse
You mean like if it's completely dead and I can't access to fastboot or anything they can't see what I did with the phone? So do you suggest that I go back to stock and wait for a little while or leave it like this?
paarthdesai said:
empyting ur pockets if system partition isnt burned up
Click to expand...
Click to collapse
How do they charge you dude??
5000 :'( whole mobo needs to be replaced
If your phone ends up going completely dead (QHSUSB_DLOAD mode, unable to get out of it), chances are your operator might not be able to tell you've done anything to it.
For example, I either ended up bricking my first One V due to overclocking way too high, or it had a faulty memory chip, and got the QHSUSB_DLOAD mode. I sent it back to my operator, and they said they were "unable to fix it" and sent me a replacement, so I'm assuming they couldn't tell I had rooted/unlocked/installed a kernel.
Some QHSUSB_DLOADs are recoverable though, so be careful.
BGmaster said:
You mean like if it's completely dead and I can't access to fastboot or anything they can't see what I did with the phone? So do you suggest that I go back to stock and wait for a little while or leave it like this?
Click to expand...
Click to collapse
If you get that dead mode, then it isn't matters that you are on custom or stock.
Guess i'll then then stick with the customization. If anything goes down that badly I'm gonna act dumb all the way :silly:
Why Worry?
Don't worry. buddy.
First of all, my and my friend's One V didn't die.
Second, if it dies, as you see the previous posts, HTC won't be able to tell that it's rooted if it's hard bricked.
First you could try to repair it using some methods available on the internet or at last you could send it to HTC.
When you're going to win in either way, they why worry?
My HOX was in this rom & kernell tripndroid_endeavoru-ota-eng.noeri_002.zip
http://forum.xda-developers.com/showthread.php?t=1784185
after install tripndroid_endeavoru-ota-eng.noeri_003.zip and flash thats kernel([email protected] #2)
my device do not allow me to flash other kernel(in bootloader allow and flashing successful but in phone os show [email protected] #2) OR do not allow to lock boot loader AND in TWRP recovery all operation same as format system, data, install new rom and other operations doing successful but after reboot phone i see nothing happen, and see last rom with last kernel last and last user data;
Who know anyway to go out from read only HOX?
How did you install that rom? Because that download link was deleted i think a month ago?
the v003 noeri kernel is the culprit of that hard bug.
Basically, you are now in apx mode. you can't do anything about it, even trip whacked his phone cause of numerous failed attempt to fix it.
Sorry dude but your phone was bricked. no other option but to send it to service center. hope you are still under warranty and your provider accept the repair for free:angel:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
if i am of any help, please hit the thanks button:good:
Sorry to say this mate but you're totally bricked.
Only a new motherboard will help...
Its best to search on how to brick your bootloader properly .....when the service center can't read/boot your bootloader anymore they don't know if it was actually unlocked before. This way you have more chance of a free repair. Because when they see the tripnraver stuff they are unlikely going to fix it under warranty/hardware defects.
but my HOX not have waranty or garanti!
i think wait to s-off to solve read only problem...
I hope you get it sorted when we get s-off !
I also have one in read-only, and I've done some investigations.
I'd rather say it's the emmc controller that's busted, in which case we won't be able to do anything as long it's not functional (I don't think even the official s-off methods will work). On the other hand, while bricking, the write protection went off and I could write some partitions, until it settled to read-only (my goal, back then, was apx). I find this interesting because this might be an short (but dangerous) way to s-off. Still, we need to identify the exact commit that holds the guild.
PS: if you don't have warranty, try changing the emmc chip, might be cheaper.
i have an option of buying a soft bricked m8, that says tampered relocked, unknown history of what was done to it, but im thinking have a go at trying to get it running again, i cannot get past any of the screens it's s-on as well, cannot go into phone settings, so i cannot do anything there.
http://img.photobucket.com/albums/v476/charvel_375/htc m8 broke.jpg?t=1515544191
So what is the question? Do you want to know if it's worth the risk/effort of buying? If we think it can be recovered? Or what exactly to do to recover it?
sorry i should have been more specific, answer.. can it be fixed, if so how, as i said i cannot get into the phone settings, i dont know if USB debugging is checked.
bluefender said:
can it be fixed, if so how, as i said i cannot get into the phone settings, i dont know if USB debugging is checked.
Click to expand...
Click to collapse
You typically don't need debugging enabled, to get the phone running. You don't need debugging to use fastboot, and it's fastboot that is critical to get the phone running.
Whether or not the phone can be fixed, is not definite with the information provided so far. A lot of times, no boot just means the ROM is corrupt or otherwise damaged, which is fairly easy to fix by a tool called RUU. Or alternately by unlocking the bootloader, putting custom recovery TWRP on the phone, and using that to flash a stock ROM or custom ROM.
"Tampered" and "relocked" (versus "locked") means that the previous owner did at least try to do some mods (unlocked bootloader, custom recovery, custom ROM and/or root). Whether those attempted mods resulted in the current condition is another question we can't answer (only the previous owner can answer). It could be as simple as a botched root attempt, such as wrong version TWRP or wrong version SuperSU (also easily fixed). Or it could be the simple act of the previous owner locking the bootloader, which by definition renders the phone unable to boot (again, RUU is one possible solution) and the person just didn't know that.
On the other hand, it's possible that the current condition is caused by a hardware failure, such as emmc failure, and you won't be able to flash a ROM, and the phone is pretty much shot (needs new motherboard, etc.). But there is really no way of determining hardware vs. software failure without trying to recover it. Although my gut tells me, this is a pretty easy software fix, and that the current condition is mostly a matter of the previous owner lacking the proper knowledge.
What are the conditions of the sale? Are you buying it "as is" whether you can fix it or not? Or is the person going to let you mess with it, before decided whether to buy it? If you fix it easily, is there a possibility they change their mind, and going to want to keep it?
thanks for the info, buying as is, owner puts his arms up and says no idea, buy as is no returns, possible guilt of not rooting correctly ? who knows.
bluefender said:
buying as is, owner puts his arms up and says no idea, buy as is no returns, possible guilt of not rooting correctly ? who knows.
Click to expand...
Click to collapse
That would be my guess, not rooted correctly, or tried to return to stock, and botched it.
The bet, if I had to make one, would be that it can be recovered (software issue). But as I said, no sure bet there. Might be worth a chance, depending on how much he is charging, and how much that amount of money means to you.
in the end i passed on it, as found out the phone has been doing the rounds, internal chip was dead iv been told.