Database Users

Bricked cdma htc hero after ruu 1.56

i ran the ruu update when i got my phone and went to 90 percent then error 110 missing file,
now it only goes to fastboot menu with no options to select from, ive tried the ruu from sdk and same error,
so if any help i can get from you guys would be greatly appreciated,
ive looked all over the google.com and have come up with no luck on how to fix this ,
i know its like the radio image that doesnt flash or something, also in sdk i cant adb to recognize device.
please help ive been to geekfor.me and no help there,
if it helps the phone is a with google stamp on it. well lets see how this thread goes from here.

Try re-downloading the ruu.
What rom were you coming from?

I haven't found anyone that has a solution to the 110 file error when flashing the RUU...
I as well as a few other gave up hope and have all since gotten replacement Heros.
The main crux of the issue is that the fastboot you are booting into will not allow adb commands and hence will never allow the RUU to install completely.
Hate to say it, but figure out a way to exchange the phone for a new one, you are stuck in an infinite loop of 110 errors...
R

Hi again R.
Yes, error 110 is a nasty one indeed. It's the reason I am hesitant to root Hero #2. I still have my 110'd Hero and am (so far unsuccessfully) hacking it back to health.
@turboek99: Yes, what rom did you have installed? Mine was modaco 2.2

gibsontest said:
Hi again R.
Yes, error 110 is a nasty one indeed. It's the reason I am hesitant to root Hero #2. I still have my 110'd Hero and am (so far unsuccessfully) hacking it back to health.
@turboek99: Yes, what rom did you have installed? Mine was modaco 2.2
Click to expand...
Click to collapse
I already re-rooted both of my phones again and am playing with ROMs, LOL so although I know what the concerns are with RUU, I'm just hoping that I can not mess things up so much that a RUU would be my only choice. My only issue is I cannot deal with the phone being as slow as it was and without Root and a ROM, I feel like I'd rather go get something else... So I have no choice but to play with fire...
The way I see it, if I can keeep these stable long enough and something finally does happen, I only hope the Supersonic is out and I an "forced" to upgrade
R

Didnt know that about ruu...sucks.
Just noticed ur screenname,turboed b16?..u take it out to the tracks or run it in the streets?.....ima take a guess and say u stay in socal?lol

johndoehizzle said:
Didnt know that about ruu...sucks.
Just noticed ur screenname,turboed b16?..u take it out to the tracks or run it in the streets?.....ima take a guess and say u stay in socal?lol
Click to expand...
Click to collapse
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"

I'll probably brick my phone intentionally when the Supersonic or the next-gen Sprint android comes out so I have an excuse to upgrade.

Anyway... back on topic. Try flashing recovery image from ADB like this:
Code:
adb remount
It should then say remount succeded.
Code:
adb push recovery.img /sdcard
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
and then flash a custom ROM. I actually made that mistake when I first rooted.

Kcarpenter said:
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"
Click to expand...
Click to collapse
Niiice.i got 2 ej1's. One auto.the other stick.i used to run that one all the time,had a turboed gsr swap with type r head.got rid of it n back to a single cam...i recently got it stolen too..stereo n black slips with brand new tires got jacked lol.left it sitting on the ground..

Kcarpenter said:
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"
Click to expand...
Click to collapse
Mistamike <- 2001 Integra Type R

HeroMeng said:
Anyway... back on topic. Try flashing recovery image from ADB like this:
Code:
adb remount
It should then say remount succeded.
Code:
adb push recovery.img /sdcard
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
and then flash a custom ROM. I actually made that mistake when I first rooted.
Click to expand...
Click to collapse
there in lies the problem, after you get the 110 error you have no more ADB. it boots into a fastboot that does not have ADB support
so the real problem is how to re-enable ADB commands, then reflashing should be simple and straight-forward...
R

RTessi said:
there in lies the problem, after you get the 110 error you have no more ADB. it boots into a fastboot that does not have ADB support
so the real problem is how to re-enable ADB commands, then reflashing should be simple and straight-forward...
R
Click to expand...
Click to collapse
Well, you can flash in fastboot... but that never worked for me.

I'm on this same boat and have been trying to find a solution. Luckily I just recently got my phone and am planning on taking it in. I did seem to find a thread where someone fixed this but they didn't say how... I messaged the guy who helped that person out but he hadn't replied yet. Forum dot ppcgeeks dot com/showthread.php?t=111587 Hope it is ok to post the link otherwise I apologize. I would really like to get my hero fixed if possible. I have a sprint hero 1.56.651.2 and used the signed RUU that's on a few threads. At first, I kept getting the connection error while trying to do the RUU, I wish I would have stopped here. But I finally got the RUU to detect and start. it was at around 85% when it moved on to the next thing after user settings I believe and it gave me the ERROR[110]. I've tried the holding volume down and powering on and many other keys but no luck.

finally got it replaced
well i got a replacement phone so kinda happy now, too bad it s a refurb unit as opposed to the brand new unit i f'ked up before. well off to what i was when i fked up my other one.haha

Heh, ditto. I got a brand spanken new one though. This time I made a backup before I soiled it.

Unrevoked Easy Root Method

Does anyone know when a easier root method will be installed?
I got into adb shell once and i can not duplicate that method again.
Any information would be greatly appreciated either posted on this thread or pm'd to me. Thanks.

when you were in it did u root?

No i did not push the update i messed up and didn't time it late.

chasehale10 said:
No i did not push the update i messed up and didn't time it late.
Click to expand...
Click to collapse
Uhh, if you messed the timing up, all you got to do is try again, not have to get in there again. So you messed up, you just repeat it until you get the timing right.

to late because in the 10 min video he says if you messed up to start over.

no he says restart the 1.bat like everyone else does... i followed the video and never start over from root.. just reload the 1.bat and try from there not restart the whole thing

god im an idot, i thought i had to restart the whole adb shell. Now i cant get back into recovery. Does anyone know when a packaged root will be ready?

no clue and i know its a pain but keep trying im sure you will get it again... try a PNY card if having lots of trouble

The easiest way I used was continuously popping in and out the sdcard while it was booting into recovery.

Help
Can someone help me with getting this Inc into recovery? I have tried several times for the last couple days and keep getting this message, " * daemon not running. starting it now *". I have the adb running in loop.

[HOW-TO] Fix 5 vibrate and black screen

Here was my situation: when trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so I decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way I think makes the most sense, but read all of what I wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what I needed to do and bringing all of their minds together in one place.
The Process
First thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
UPDATE: To clarify: fastboot is a completely separate (although closely related) piece of software from adb. If you do not have "fastboot.exe", download it from http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/ and follow the instructions there. Or, you can just download the full sdk from google which should include adb and fastboot. I recommend the second option, but my hard drive can take the hit. (thanks BonzTM)
UPDATE: If you get an error saying "The Program can't start because AdbWinApi.dll is missing from your computer" you need to copy that file from platform-tools to tools, then it should work (thanks Jester1614).
If you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
Disclaimer
Note: This is what I experienced with my amoled incredible; in no way do I take responsibility for anything you do. If you try to blame me for bricking your phone I will enjoy a hearty laugh while salting my soup with your tears.

Worked great for me and saved me from the hassle of needing a new phone.
THANK YOU!

goblue13579 said:
here was my situation: When trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so i decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way i think makes the most sense, but read all of what i wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what i needed to do and bringing all of their minds together in one place.
the process
first thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
if you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
disclaimer
note: This is what i experienced with my amoled incredible; in no way do i take responsibility for anything you do. If you try to blame me for bricking your phone i will enjoy a hearty laugh while salting my soup with your tears.
Click to expand...
Click to collapse
u saved my life/phone i love u son

Perfect Solution!
Thanks Thanks Thanks +1

So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb

sofocused715 said:
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
Click to expand...
Click to collapse
Actually you can download it from the link I provided in my post to the xda page for it (http://forum.xda-developers.com/showthread.php?t=833953). Scroll to the bottom of the first post and in the attached files there is a version that works. That's what I did, and then you can run the usb fixing commands. Then it's just reboot, re-root, and restore.
Hope this helps.

This thread needs more attention.

This needs to be stickied(sp?) and maybe added to the Development section where it would most likely be looked for first.
If I've helped you, hit the thanks button!

As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.

goblue13579 said:
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
Click to expand...
Click to collapse
I re-worded your OP and posted it on another forum. I did credit you though. You are now famous.

Cool, thanks!

I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.

brando56894 said:
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
Click to expand...
Click to collapse
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.

doug piston said:
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
Click to expand...
Click to collapse
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol

wildstang83 said:
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
Click to expand...
Click to collapse
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.

Thank you goblue13579, wildstang83 and Doug Piston! My phone is totally functional once again.
Odd timing how the problem happened only 2 days ago on my phone, and coincidentally, a fix was hashed out in the same time period after all this time of it being unfixable.
I owe you all a beer! Thanks again!

doug piston said:
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Click to expand...
Click to collapse
Yea bud, even I use adb so much that I keep forgetting that there's emulators to use. Its just one of those things we never think about.

Even though it was really more dumb luck and excessive googling that got me to this solution, thanks! I'm glad my compilation has helped so many people. And honestly, it's the least I can do for all the help and goodies I've gotten from these forums and developers.
Happy modding!

What if the devise isn't rooted?

Let the phone sit for an hour with the battery out. Put the battery in after that, should be good
Sent from my 2.3.5 Incredible Obsession

[Q] New kind of unfixable Super Brick?

My kindle is bricked and I have tried everything.
This is what i did: I rooted it, installed CM7, it worked fine. I then wanted to go back to the stock rom (due to countless FCs and freezing in CM) so i flashed the stock rom through TWRP. When i re-booted, the TWRP recovery screen no longer shows and it has the stock kindle fire logo on screen.
It does not show up in device manager in windows, I have re-installed the usb drivers multiple times. Any recovery methods using ADB simply result in "waiting for device" forever.
I have tried:
hard reset
fastboot commands
booting to linux live cd with firekit
kindle fire unbrick utility
None of these work because it does connect via usb
Anyone else have this problem>?
EDIT: Im fed up, ive tried every method on XDA and youtube, nothing works. I convinced amazon to replace it. Thanks anyways.

Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728

lovejoy777 said:
Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728
Click to expand...
Click to collapse
If you notice, that uses ADB shell. All of these commands result in "waiting for device" as it it not detected as a USB device

Sorry forgot to attach
Ok dont worry ive gotten my self into the same issue and lots of other ones lol
I just kept on trying different things.
it will be a driver issue Ill try to find the thread that got me out of it
---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------
Found it Try this.http://forum.xda-developers.com/showthread.php?t=1399889

I bricked mine last night and kept getting stuck at "waiting for device" and figured out Windows ceases to recognize it as something it has a driver for.
Windows Device Manager showed the Kindle with a yellow sign next to it. I right clicked and updated the driver but rather than detecting it at all I manually picked a device.
Don't have Windows in front of me right now but it was something like "Android Phone" for the device type and then the device was the first one listed "ADB Interface" or something starting with ADB anyway.
Once that driver was loaded I could issue ADB commands again and got it fixed.
Sent from my Kindle Fire using Tapatalk

Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.

googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.

bg4 said:
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.
Click to expand...
Click to collapse
Well considering he already convinced amazon to send him a new one its a little too late, and others have already weighed in to help, its not very nice but its the truth. If he would have just waited more than an hour for people to try and help him he would probably have been able to fix it.

Jus a quick servh would give you the answers you're looking for. It's not bricked. So relax

HaroldBawls said:
Rooting it inst the issue, trying to put a phone OS on a tablet is the issue.
Click to expand...
Click to collapse
?
Tell that to all the Nook Color users running CM7 or to Samsung, HTC and others that shipped tablets with Android 2.2 and 2.3

googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
Troll found. Anti-Hate taser activate.
Sent from my Kindle Fire using Tapatalk

Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.

i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else

zbhest said:
Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.
Click to expand...
Click to collapse
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk

mattlgroff said:
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
This is exactly what happened. Because it didn't have the TWRP recovery screen or anything, any average tech support person wouldnt be able to tell it had been rooted. The failure actually happened after installing the stock rom so im pretty sure if they even take the time to inspect it, they wil see an unused, unrooted stock rom on the devoce

punkboyarde said:
i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else
Click to expand...
Click to collapse
Thanks, but this only works if it connects over usb. Doing this results in "waiting for device" as mentioned before

[Q] trouble with SuperOneClick

Ok so I have searched around here and other places for a while and I can't seem to make this work. I apologize if this post is super nooby :/
I am trying to root my wife's continuum. I first tried using z4root and that just keeps freezing mid process every time. Now I am trying to use SuperOneClick and I keep getting stuck at the same spot.
It gets to step 5, and I keep ended up with this
[+] Found a Froyo ! 0x00017108
[*] Scooting ...
[-] Error creating Nydus: Permission denied
END: 17357
I made sure that the SDcard is not mounted. The phone is set to USB debug mode. The phone recently got the EC09 update from Verizon.
I really don't want to do anything fancy like flashing new roms or themes or anything, I am just trying to get rid of some of the bloatware.
Thanks in advance!

Superoneclick v2. 3. 3 confirmed working on ec09
Sent from my SCH-I400 using xda premium

thanks. that ended up working. I had been on 2.2 I think and every time I tried to find 2.3.3 the site wouldn't exist. Finally found someone mirroring it.

Am i the only one who did it manually with adb? lol,

I would have liked to but my current knowledge is not that great and I didn't want to mess anything up!

abby_nitewolf said:
Am i the only one who did it manually with adb? lol,
Click to expand...
Click to collapse
Well, oh great one, show us the way.