Related
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
The key piece of information to remember is that rooting does't cause the issues we experience. It's the custom ROMs and hacks we install that cause problems
I think most everyone here remembers that we're doing these things at our own risk.
As for the OP, if you don't feel a desire for the features available after rooting or flashing a custom ROM, that's cool. It's not for everyone.
Rooting, flashing, hacking... it's for tinkerers. People who like to find out why something does or doesn't work and then find a fix for it.
I would place a bet on this:
The people who don't have root or don't want to root, and they rarely post their issues in comparision with those who have rooted.
Yes, Most of the issues you see here are self inflicted, but it's what we do. We like a challenge/problem, it gives us something to do. Another reason to stay up till 3 in the morning to find out WHY it's jacked up.
If your issues are so bad, RUU and stick with stock (A whole new set of issues).
We mention our problems so that developers can try and fix them for the next release. In all honesty, Ive had one 1 problem, that was when I installed AOSP 1.6, which btw is/will not supported by our phone officially, I got the dreaded SMS issue that SOME people are experiencing.
Well yea many people post about issues who are rooted, but it is caused by other things they are doing that require it. Simply rooting your device shouldn't cause anything to go wrong.
Roms and other things that require root access tend to be beta, and even if they are not beta they are created by people, and not everything will be perfect.
It is pretty hard to permakill your hero compared to other devices. The only way I know of using the software is through flashing the radio, or messing with ESID and stuff like that.
Which you aren't supposed to do .
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
rdisanza said:
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
Click to expand...
Click to collapse
There's not an issue with rooting in and of itself. Take me for instance. I've had some problems with my phone:
1. Apps2SD didn't work...but that was part of a ROM that was being beta tested.
2. Kernel locked up...that was due to an invalid setting I put into the kernel I was building.
3. Lost CPU kernel control...this is something I'm doing wrong in the kernel I am building. I simply restore a control file from a previous build and recompile.
These are things that were expected in testing and needed to be fixed or that I inflicted on my own.
I have a friend who has rooted his Hero, but hasn't applied any of the custom ROMs to his phone (although he has installed applications that require root). He's never had an issue with the phone.
It really depends on what you use it for.
rdisanza said:
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
Click to expand...
Click to collapse
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
watzone69 said:
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
Click to expand...
Click to collapse
lol I second this my wife hates the fact the I have tis really nice phone and when ever I am at home she can never get ahold of because I am always doing something to it.
to the OP rooting really is not hard I mean if you are hosting a MMORPG server you could surely do it, but if your happy with your phone as is then that is really awesome. I myself when I first got my phone knew ABSOLUTLY NOTHING about android or linux or what in the work a kernel or apk was but with the help of the great community here I have learned so much. Dont get me wrong I am no where near where a lot of the guys on here are but I am learning and helping as much as I can just as those that helped me (i mean I am just happy that I think I could go through and make a theme now lol). if you are happy with the phone as is the only benifit of rooting I would bring up is being able to make backups of everything that way if anything does happen to the phone then you dont have to go trough and redownload apps and set everyhting back up again.
if you do decide to make the leap there are many people here more than willing to help.
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
rdisanza said:
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
Click to expand...
Click to collapse
oh please understand I wasnt trying to insult you at all, and yes I understand the control thing. thats why I rooted originally but then I flashed my first rom and got addicted. Now if im not changing my phone in some way on a pretty much daily basis I start to get the DT's lol.
No insult taken my friend. The DT's, lol WORD!
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
HeroMeng said:
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
Click to expand...
Click to collapse
You don't have to push the asroot2 exploit!?!?!!?
Kcarpenter said:
You don't have to push the asroot2 exploit!?!?!!?
Click to expand...
Click to collapse
Not if you're flashing a custom rom that already has it.
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
gu1dry said:
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
Click to expand...
Click to collapse
I never had to do that when I rooted. Flashed MCR right after I rooted using above method and it worked fine.
Yes the asroot2 exploit is was allows to root the phone, so therefore you had run the exploit initially.
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
You need to do the root process to get to the care bear, then flash villainrom on the care bear, before rebooting.
That will get you sorted
Well I rooted using universal androot, then used the teminal to input the su (press enter)
flash_image recovery /sdcard/recovery.img (press enter) part of instructions but at no point do I see the care bear :S
I have the same problem as Ejen. The phone is root i have superuser permission i do titanium backup .I put RA-hero-v1.7.0.1 with Better Terminal Emulator. When I turn off phone and press Home&Power I get a picture phone with a triangle. Does anyone have an idea how to solve this?
Yes, this is because stock rom automatically reflashes recovery with the stock one each shutdown iirc.
You need to stop this happening, but I can't remember the command. When you have root using universal androot though, you can stop it happening.
Or maybe it's too early for me. Wait till I've had a coffee or two and I'll revisit this...
Perhaps you can edit /system/etc/install-recovery.sh. A quick look trough /system didn't find anything like a shutdown script so perhaps this file is run by the android environment.
I had this same issue the other night, been searching for a fix, hopefully one appears here soon, thanks Pulser_g2, i was hoping to install your 1.5 Rom
Bloke
Ah seems I'm not the only one well at least I wasn't just being silly then, well tried it multiple times but still seem to have no success even tried the unlockr websites method with no success either.
If anyone knows thanks
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try http://forum.xda-developers.com/showthread.php?t=726118 and see if that works.
I'm trying to work out what's going on here...
P
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Ejen said:
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Click to expand...
Click to collapse
Ok,... So how far did you get on setting up adb http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) ?
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Ejen said:
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Click to expand...
Click to collapse
Type adb devices, and if you see your phone's serial number, then you don't need to worry about drivers. Remember to "cd" into the correct folder first.
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Ejen said:
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Click to expand...
Click to collapse
Where have you downloaded your Android SDK too?
for example > "cd c:\SDK\tools"
pulser_g2 said:
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try VillainROM Roots 2.1 and see if that works.
I'm trying to work out what's going on here...
P
Click to expand...
Click to collapse
I guess that is already on the phone RA-hero-v1.7.0.1 as you said stock rom automatically reflashes recovery. I suppose that the method VillainROM Roots 2.1contains RA-hero-v1.6.2.img. What will then happen with recovery if i try to do again root with VillainROM Roots 2.1?
When you try that method, you get the phone booted into patched recovery, at which point you take a nandroid backup and flash a custom ROM.
this prevents the recovery being lost. Just try it
I'm not at home and can not install ADB and run runindos.bat. I have on SD card recovery and FroydVillain 1.5. That's why I tried this method.Next week I'll be home and if someone does not fix the problem i will try the method you suggested me.
Can I try to put again recovery with Better Terminal Emulator, maybe recovery was corrupted ....
i went through the same thing!!
Ejen said:
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
Click to expand...
Click to collapse
helloo!! i apologise if i am interupting or butting in whilst your in the middle of other solutions... i just saw the title and jump right in. i went through the exact same thing just 2 weeks ago!! unfortunately for me there was no successful forums or websites at the time... it sounded like a simple problem, with no simple solution.
this may not be what you where looking for, but its a very quick easy method that definately worth a try.
so... am i right in saying you have the official OTA HTC android 2.1 update?? and you now want to get this rooted?? and have you also tried rooting using the two common methods, the "one click root" and the "unrevoked" one? thats wat i did and i kept being stuck at the same red triangle and exclamation mark.
those methods (and countless others) will not work with the official htc hero android 2.1. (as far as i know) what you will need to do is downgrade the phones software. check htc's website and look for the older RUU and using the computer get your hero back to android 1.5. (under no circumstance should you upgrade your 1.5 android to the 2.1 android via HTC's OTA update... its only going the remove the root access!!!! - always reject it)
then continue to root as per the numerous rooting guides. done? now, obviously you will want to flash an android 2.1 rom. if you want to keep to htc's original 2.1, you can search for this in the forums under 'development'. or go ahead and flash the custom roms (villianrom).
thats exactly how i did it. im not entirely sure if this is the info you are after... but reply back and ill be happy to answer any query - big or small. (i should warn you, im no expert - but this forum is filled with the earths most powerful brains - u should have an answer in no time!!)
I have an HTC Hero. I ran the simple root method and got Carebare response.
I too have read numerous threads in the forum here and elsewhere but can't seem to get past the USB section.
adb says no device
I can use HTC Sync to sync data to the phone.
The SDK is installed and I have previously used it to capture screen shots of my device.
If I try to run one of the RUU executables, it fails with a [114: USB Error] (number may be wrong but the message is right.
I can mount the SD card and copy files to/from it.
I am running Windows 7 Home Premium 64bit on a Quad Core AMD CPU.
If I do the Home/Power thing, I get the same red triangle as described in the 1st message of this thread.
Fwiw, I have successfully and repeated loaded ROM's on my previous phone (HTC S621) so I am not a complete newb (but i am newb to Android).
What am I missing? This shouldn't be this hard (at least from what I've seen posted anyway)
I have been lurking around here for a while (Yes another noob) and have been thinking of rooting and flashing my phone to DJ05 from this page.
http://forum.xda-developers.com/showthread.php?t=869990
However, before I do I hoped some of the more experience guy/gals maybe able to enlighten me a bit.
The Radio is basically what it sounds like right. Cell/data service, GPS, wifi, and ect?
The kernal is the os under the gui?
The rom is the GUI?
I looked at the stickes and the wikki and I am a bit confused.
First I need to root my phone with the one button flash instructions on the stickes.
Then what.
What do you use back up?
Can I back up games?
Is there a simple step by step instructions that start how to put phone in the right mode?
What do install on computer to flash?
Will this also get rid of all the bloatware?
Basically where to start step by step including what programs to use?
Like I said I'm a complete noob, and apprciate any and all help.
Thx
Scott
In the developement section there are stickies. They will get you from stock to rooted to romed.
There us an app called z4root which is a 1click rooting system and far better then the adb program imo.
After that you want to flash cwm.tar also coverd in the stickies.
Get familiar with odin. Remember pda button is your friend.
After you have rooted , make a back up through rom manager....
Sigh...... Its 4am my puppy woke me up. Someone else can take over lol. Pm me if you need assistance over the phone I can walk you through the whole process if need be.
Sent from my SCH-I500 using XDA App
This is your one-stop shop for all your questions
Is there a wiki project affiliated with xda? I would like to organize everything I know about bricking and fixing these things, organized with hyperlinks. A lot of times I don't know the most efficient solution, but that could be refined.
It would be nice if I could see a question here and simply point to section 12a.13 of a comprehensive guide, concisely written (not necessarily my strong-suit I admit) with brief jargon and a complete glossary.
Swyped w/ XDA App. When in doubt, mumble.
Anubis9000 said:
I have been lurking around here for a while (Yes another noob) and have been thinking of rooting and flashing my phone to DJ05 from this page.
http://forum.xda-developers.com/showthread.php?t=869990
However, before I do I hoped some of the more experience guy/gals maybe able to enlighten me a bit.
The Radio is basically what it sounds like right. Cell/data service, GPS, wifi, and ect?
The kernal is the os under the gui?
The rom is the GUI?
I looked at the stickes and the wikki and I am a bit confused.
First I need to root my phone with the one button flash instructions on the stickes.
Then what.
What do you use back up?
Can I back up games?
Is there a simple step by step instructions that start how to put phone in the right mode?
What do install on computer to flash?
Will this also get rid of all the bloatware?
Basically where to start step by step including what programs to use?
Like I said I'm a complete noob, and apprciate any and all help.
Thx
Scott
Click to expand...
Click to collapse
The radio/modem/baseband is basically what you say, yes. It lives on it's own partition.
The kernel is the OS.
Afaik ROM is a general term, and can include any combination of kernel, ui changes, and system apps.
You mau root with a one button app like z4root. However manual roots don't take long, and ensure that you have working samsung drivers, and a working adb environment, and at least a basic knowledge of how your phone can be modified in a shell if everything goes FUBAR on you. It is just nice to be prepared, and to know how to at least root (and unroot) your phone if the one clicks hang or stop working.
Avoid even considering a voodoo install until you a) have installed a clean rom like super clean or blackhole and configured it with adw or launcher pro b) replaced the kernel if you found it too slow or replaced the modem. c) still notice lag (specifically during disk writes - ex you stream a ton of rss feeds and email constantly) that is intolerable to you. d) you have bricked and fixed your phone on at least two different ways already and are prepared to take full responsibility for whatever crashes happen and for data lost. Ie. You are a newcomer, you should probably just stay away, non voodoo kernels are quite smooth -i have always been satisfied.
Titanium backup pro does a wonderful job of restoring your most important apps. I recommend not backing up every item / system data. It is just easier for me to stay lightweight. It also gives you the ability to freeze/delete bloatware.
Rom manager and accompanying cwr gives you a way to backup almost everything. It is CRITICAL to do this backup before doing any odin flashes or installing any ROMs for the first time.
Yes you can backup games.
I am not 100% clear on modes.
* if your phone is working and you installed adb on your computer like you should have -simply type 'adb reboot download' or 'adb reboot recovery' EASY! (what I do)
* download - Hold volume down button while your phone is turning on until you see the yellow warning sign. (get it? Down for download). You use this mode for heimdall/odin
* recovery - hold volume up & down buttons while turning on phone. If you get a battery icon instead, unplug the phone or the battery. This is basic stock recovery, not CWR.
Heimdall or odin for flashing. Always use pda button. Put on android SDK and set your path variables too. And of course install samsung drivers for your phone!
Where to start? Read the first post of every sticky in this forum, particularly in development.
Don't post to development.
Swyped w/ XDA App. When in doubt, mumble.
Thanks for all the help. I have read some of the stickes. I will read the rest. Thanks for pointing me in the right direction.
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
Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.
taboo_ said:
Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.
Click to expand...
Click to collapse
I would flash a stock rom to get the phone running again, and next time make a nandroid backup that you can restore with a custom recovery before you mess with system files.
I'm currently downloading a stock rom from a very slow source. In the 3hrs or so it's going to take to download I thought I would absolutely confirm I was buggered as it would be nice if a few ADB commands could save me.
gee2012 said:
next time make a nandroid backup with a custom recovery before you mess with system files.
Click to expand...
Click to collapse
I do certainly know better. But Samsung in their power have decided to Knox flag your device if you install a custom recovery. As such creating a nandroid backup was not an option for as long as I want my warranty. I do have Titanium backups, and I thought I was doing the right thing by making a copy of build.prop before doing anything... turns out I was wrong. But really, thanks for your concern and advice.
..
fffft said:
Three hours huh? You should talk to Santa about a faster net connection.
Click to expand...
Click to collapse
I live in Australia. We asked our government and they said yes.... then we got a new government. But in this case it's the speed of the host that was hindering. It's all elementary now anyway as the download finished. No one had replied. I flashed it. It failed. And the long and short of it is adb is now useless to me.
fffft said:
You should know this already though as a five minute search on how to use ADB would have pulled up numerous tutorials.
Click to expand...
Click to collapse
I appreciate the help. But I'd spent all day reading tutorials. Trying commands. Failing. Googling the error. Trying new commands. Failing. Googling those errors. After doing that for some time I thought it would just be more sensible to ask people that have actually had experience.
fffft said:
You're also on the wrong site if you are obsessing over the Knox flag. Yeah, it might affect your warranty. Probably not, but I'll grant that it could. So simply decide up front it you want to modify your phone or wait out your risk free warranty period.
Click to expand...
Click to collapse
So here's the thing. I don't want my cake and eat it. I will absolutely be blowing away knox. I just didn't see a point in doing it preemptively. The phone is only a couple weeks old so I decide it would be wise to at least keep my warranty until I'm happy it's rock solid and I have a good reason to lose it - nice stable Cyanogenmod I'm looking at you. Plus anything I wanted to do up to now I was able to with Towelroot and xposed. I just couldn't Nandroid.
Really. Thanks for listing the commands. As of this morning I hadn't needed to use ADB at all. I appreciate you spelling it out. I just wish I had of seen it mere minutes earlier as I would have been able to let you know if it worked. Unfortunately I didn't. But I appreciate the effort.
..
fffft said:
And you say that your firmware download speed was host limited. I just did a search for half a dozen S5 firmware builds. Found all of them widely disseminated. And as one might expect, not all of the hosts were slow..
Click to expand...
Click to collapse
I was using sammobile.com on a free account. I'm sure I could have found a faster host but I've used sammobile.com many times in the past and they've always been reliable. I'd rather wait longer and get something I trust when I'm not in a hurry than download a file that has the right name but is just from a random "megaupload" link or something.
Now regarding adb I got a lot of the information I needed through google searches. I also watched a number of videos. But here's the thing. If I were just taking the opportunity to learn about adb google-ing around would have been fine. But as the circumstances were a little dire in this situation and I've expressed that I've never used adb before and was not confident. I didn't know what I was doing or have the experience to know the implications of what I was doing. As such 1) I didn't want to take the chances of getting it wrong and screwing myself over further and 2) I seemed to have a fairly unique issue (can't boot, stock recovery, "error: close" issue).
It wasn't just about knowing the commands to use, it was about finding out whether I was even able to do what I was hoping to do from a stock recovery on an S5 (hence the title of the thread).
You're getting a little judgey, which is fine you're entitled to your opinions. But I'd ask you read my title and first post again. It wasn't about just getting the commands outright coz I was too lazy to look, it was about getting a number of questions that I didn't know the answer to due to lack of experience, and that I hadn't had directly answered through google searches. Also I never implied an urgency, it was simply a case of "I had a contingency plan in place (downloading a stock rom) but I thought I may as well ask for some advice in the time I had while waiting for it to download".
It's not as though my case was a dime-a-dozen, "answered directly a million times". It was a little more unique and I had answered many of the general questions myself and decided that my remaining hesitations are best answered by those with experience. I'm sorry that bothers you.
Plus the reason you were able to have so much success is because you have experience and knew what to look for and understood the compounding factors. I had figured your first and third command out for myself. I was missing your second and I don't know if that was my problem, but the error I was getting "error: closed" seems to have a massive lack of documentation on the internet. Not many people are talking about it and those that are pretty much just say "update abd" - I was running the latest version. That is where I was coming undone.
But if you're STILL feeling disconcerted at my efforts here is my session from yesterday right before I made this thread. This is literally only a few of the tabs I had gone through: http://i.imgur.com/WDB3qIg.png
..
I just can not understand why you're being like this man. I've been nothing but polite. But I came on here to learn. If I was doing something blatantly against the community I'd expect to hear about it, but I just wanted help. You gave me help which was awesome but every time I took it or added something to explain my reasoning for my actions you added a lecture with it.
All I was trying to put across to you was that you don't know what I did or my reasoning for asking questions. I was just hoping you could see that your initial assumption about my laziness may not have been correct. Again, I'm not trying to be a **** about this and I really was thankful for the help you gave. But it seems you're more than willing to dish out the criticism but as soon as I defend myself or talk back you in turn get your back up. But I just don't understand why you seemed so interested in making assumptions about my efforts, my internet speeds and then telling me how I should be doing everything differently.