Database Users

fully back to stock ONLY using recovery adb?

I've got cyanogen's optimized 1.5r2v3.4, and Recovery Image v1.2. I have read half a dozen threads on how to get your phone back to stock, including this one http://forum.xda-developers.com/showthread.php?t=491350, but I have a unique impediment.
The screen on my fiance's brand new phone completely stopped working after less than a week. I can only interact with the phone via adb connected to the recovery shell, so I have to be absolutely sure it goes perfectly the first time (since the odds of having a working recovery shell after a bad flash are slim). I have not changed the second splash screen, so by what I read, all I need to flash back are the SPL, then the DREAIMG.nbh, correct?
How do I do update.zip for flashing the SPL via the recovery console? I had no problems getting the phone from stock to rooted, followed the instructions step by step. But now that I have to try and figure out how to do EVERYTHING via adb ONLY, I read the most simple instructions and find myself going 'wait, what?', trying to figure out how that would work done entirely without being able to see feedback on the phone screen.

Use the DREAIMG.nbh and recovery.img for rc29 stock its in the rooting thread.......load up the phone in fastboot (camera and power button) the phone will recognize the files and tell u to hit a button....you hit that whopping one button and wait 2 minutes and you'll be back to stock rc29 where then you can reroot or just sit around waiting for Over the air updates from t-mobile to catch u up to cupcake.....honestly i don't use fastboot EVER but i always keep those two files on my sdcard so if i have a problem i just run it and blast back to rc29 and start over......hope u see this before its closed in 5 seconds for not using the SEARCH BUTTON

sorry just use just reread ur post...use the DREAIMG.nbh it has the old SPL built into it

i'm not sure how this would be done, but what iwould suggest is put the original SPL on the SD card as update.zip and the DREAIMG.nbh on the sd in the root of the sdcard, then reboot holding home, give teh phone 5 minutes to boot into recovery then press alt+S wait 10 or more minutes to let it flash and then press home and back to reboot, or in adb shell type reboot bootloader, give it a minute or so and then press power, wait 30 minutes and hit the trackball, if after hitting the trackball the phone vibrates then it went fine, if not then the .nbh didn't flash

tubaking182 said:
i'm not sure how this would be done, but what i would suggest is...
Click to expand...
Click to collapse
Yeah, that sounds like a plan. Thanks, I just really couldn't get my head around how I could possibly do this!

Can I ask why you are bothering? Are you afraid they will hit you with an out-of-warranty fee because it's rooted? They won't, I've returned a first gen G1 that had the issue of the screens ribbon cable coming unplugged (sounds like your problem) and T-Mobile sent us a new one no problem.

GenericNode said:
Are you afraid they will hit you with an out-of-warranty fee because it's rooted?
Click to expand...
Click to collapse
Yeah, actually. *shrug* it doesn't seem to have flashed back to the stock image anyway, so I guess it'll have to go back in whatever form it's in. Hopefully you're right and they don't care about custom images.

heldc said:
Hopefully you're right and they don't care about custom images.
Click to expand...
Click to collapse
They sure didn't care about mine.
And besides, whether or not your phone is rooted isn't in the check-list of questions a CSR is supposed to ask before accepting a return, so how could it be your fault?

Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked(which i found odd since the demo phone in my t-mo store is rooted and running dude 1.2). as long as it doesn't have a custom splash screen it should be ok.
also you could always grap the OTA update and edit it in some way(resize a pic and put it back) and then resign with testkeys and rename update.zip then the only thing they'll see if they really look at the phone is a bootloader that's been changed and recovery, but the rest will look like their stuff.

tethering caused double post sorry

tubaking182 said:
Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked
Click to expand...
Click to collapse
No way. Sweet. I haven't seen this policy yet, but I never pay attention

yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.

tubaking182 said:
yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.
Click to expand...
Click to collapse
When you talk to those people you have to sound as newbish as possible, that's probably why they kept asking if you rooted it.

trust me i sound like a freaking idiot. "they told me on the t-mobile forums to press the homekey and turn the phone on and i got a triangle with an exclamatioin point, and then i pressed alt+w and after a few seconds my phone rebooted but the screen is always sideways when i open apps." i act like an idiot and they replace it. the only problem i had was when the guy asked what my favorite thing about the phone is, right after i told him i didn't know what root was. i just said games cause that's all i could come up with

Issue getting to recovery to activate root, stuck on "Downloading"

I am trying to root my Vibrant, but when I hold down both ends of the volume rocker and power the device on I get stuck on a screen that says "Downloading..... Do not turn off Target".
Is my phone actually downloading something from the web? I left it on like this all night and nothing seemed to have changed.
If it is actually downloading something should I move to an area with better 3G reception while trying to root?
Any help on this subject is IMMENSELY appreciated.
Thanks!

It shouldn't be downloading anything. Unless I'm mistaken. The phone should just be installing the zip that's on the phone.

Thanks for the reply Rick!
to quote the Root your Vibrant Guide:
"7. In Recovery menu select 'Reinstall Packages' (use vol_down then power to select)"
Does this mean I do not need to do this? I put the renamed file "update.zip" onto the phones internal memory....
Am I missing something?

Unplug the usb cable and try again.

or alternatively, issue a "adb reboot recovery" command from ADB.

phantasm714 said:
or alternatively, issue a "adb reboot recovery" command from ADB.
Click to expand...
Click to collapse
Unfortunately Windows is not properly identifying the Vibrant, and it seems that ADB is not detecting it as a result either.... I'll keep at it.

symbit said:
Unfortunately Windows is not properly identifying the Vibrant, and it seems that ADB is not detecting it as a result either.... I'll keep at it.
Click to expand...
Click to collapse
I'm assuming you have the correct drivers installed on your Windows box?

phantasm714 said:
I'm assuming you have the correct drivers installed on your Windows box?
Click to expand...
Click to collapse
I cant find any standalone drivers, but I am downloading this Samsung PC Studio crap. I hope that has them.

symbit said:
I cant find any standalone drivers, but I am downloading this Samsung PC Studio crap. I hope that has them.
Click to expand...
Click to collapse
Did you turn on USB Debugging in the setting menu?
I know it's a stupid question, and I'm not trying to call you stupid, but it is a commonly missed step in getting ADB recognition.

really dude there are plenty of answers you could have found for this with a little searching but your in download mode yellow triangle sign with the android guy digging right? well unlplug the charger from the phone hold both volume up and down and hold power while turning on the phone and then the recovery should pop up use the volume keys to select reinstall packages then select it with the power button then reboot and now your rooted.... you should have searched for this instead of posting a thread and this is not development it should have been posted in the general section and if you cant do this then you should try to root your phone in the first place but if you need a easier way to do i have a theory of a one click method using rom manager from the market that should work

skater4690 said:
really dude there are plenty of answers you could have found for this with a little searching but your in download mode yellow triangle sign with the android guy digging right? well unlplug the charger from the phone hold both volume up and down and hold power while turning on the phone and then the recovery should pop up use the volume keys to select reinstall packages then select it with the power button then reboot and now your rooted.... you should have searched for this instead of posting a thread and this is not development it should have been posted in the general section and if you cant do this then you should try to root your phone in the first place but if you need a easier way to do i have a theory of a one click method using rom manager from the market that should work
Click to expand...
Click to collapse
Thank you for correcting me. Was that meant to be one long sentence?

symbit said:
Thank you for correcting me. Was that meant to be one long sentence?
Click to expand...
Click to collapse
no it wasnt i just dont like using punctuation. Did it help you, or do you need me to put it in numerical order of the steps?

This is all starting to seem very similar to the dream forum.you guys need to all chill out.
Sent from my SGH-T959 using XDA App

Minker17 said:
This is all starting to seem very similar to the dream forum.you guys need to all chill out.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i just left that forum lol its not as bad as this posting was usually in the right place

skater4690 said:
Thank-you I agree you can't search for anything on this phone cause nothing is out or made for it yet. And then I have some ungrateful people saying SEE A SIMPLE SEARCH WOULD HAVE FOUND THIS....
...so if you have nothing nice or helpful then please don't say anything
Click to expand...
Click to collapse
quoted from a guy with nothing good to ever say...
...literally this is the only thing good ever stated from this guy...

junkdruggler said:
quoted from a guy with nothing good to ever say...
...literally this is the only thing good ever stated from this guy...
Click to expand...
Click to collapse
so what is this suppose to even mean? i already posted something towards helping this guy and what have you done? and how would you know what the only good thing i have ever said? have you read any of the 300 some odd posts ive had?

Besides arguing why couldn't someone advice him to unplug the phone from the USB cable in order to enter recovery mode.

Soft brick installing GingerbreadlatinIME.zip

I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:

to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.

tenbeau said:
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
Click to expand...
Click to collapse
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.

bobsbbq said:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
Click to expand...
Click to collapse
yes I a sure am. I trusted the Dorid-Life site and should not have. Thanks for the swift response...

setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.

Please post questions in Q&A section.

I did the same thing. I flashed the .zip file from droid life forum and got a success message when I installed it through recovery and mine never bootlooped. I didn't get the gingerbread keyboard but it didn't bootloop either
Sent from my HTC Glacier using XDA App

tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
I think you mean bootloader? You only have 1 recovery. If you flashed clockwork you no longer have stock recovery. Vol Down + Pwr gets you to bootloader or SPL where it shows S=off.

I did not flash the zip (sounds like an overkill to flash a zip for new KB). I ADB pushed both files and got a FC on multi-touch KB... oh well, I like HTC_IME better anyway

tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
make sure fastboot is checked off otherwise you cant get into the bootloader. to make sure it is off go to: menu, settings, applications and uncheck fastboot. you're good to go then. to get into recovery, you can do it thru bootloader or by opening up rom manager and clicking on the "reboot to recovery" option

setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
the website was not specific enough. the port at the current moment is for motorola droid devices. they should have been more specific instead of saying any rooted 2.2 android phone. even if you do get it on your phone, its only going to force close every time you try and type something. thats what happened to me, so after about 24 hours i said **** it and removed it. swype in my opinion is better anyway. im trying to port the g2 swype to our phone so we can have a swype with a mic on the keyboard. oddly, ours didnt come with one.

[Q] MYT4G recovery mode

how do you put the myt4G in to recovery mode?

Wow not to be rude but did you try the search button......hold down the power button and the volume down button at the same time while the phone is off. The select recovery
Sent from my icy cold glacier freezing every phone in its path

i did and i tried search by looking up hbooting myt4g recovery mode couldn't find nothing i even googled it and found this method your giving me but for some reason when i hold down home and power then let go of power button it fastboots..

but now i realized its the vol button i was looking at the myt3G recovery...thank you.

this is not working for me BTW.... can anyone else help out?

l0uisz said:
this is not working for me BTW.... can anyone else help out?
Click to expand...
Click to collapse
You have to have fastboot unselected before it will work. I'm looking into rooting my wife's mt4g, and that took me forever to figure out.
I have a vibrant, so I'm new around these parts. Still doing my research before taking the plunge.

lol! wow thanks i wouldve never figured that out hah! yea well this is very helpful here http://forum.xda-developers.com/showthread.php?t=858996 hoping that you know how to use ADB of course =) now i am ready to root !
OH! btw how do you get off recovery mode ? do u just pull the batt out?

l0uisz said:
lol! wow thanks i wouldve never figured that out hah! yea well this is very helpful here http://forum.xda-developers.com/showthread.php?t=858996 hoping that you know how to use ADB of course =) now i am ready to root !
OH! btw how do you get off recovery mode ? do u just pull the batt out?
Click to expand...
Click to collapse
factory recovery image? that i am aware of, yes. but i might be incorrect on that.

bnielsen40 said:
You have to have fastboot unselected before it will work. I'm looking into rooting my wife's mt4g, and that took me forever to figure out.
I have a vibrant, so I'm new around these parts. Still doing my research before taking the plunge.
Click to expand...
Click to collapse
Please use the term quick boot when referring to the reboot option that does not fully restart the phone.
Use 'fastboot' to refer to the low level utility / protocol that allows image (ROM,etc) flashing via USB

l0uisz said:
lol! wow thanks i wouldve never figured that out hah! yea well this is very helpful here http://forum.xda-developers.com/showthread.php?t=858996 hoping that you know how to use ADB of course =) now i am ready to root !
Click to expand...
Click to collapse
No problem (clicky the thanks button ). I was actually leaning toward this method: http://forum.xda-developers.com/showthread.php?t=834225. I'm still trying to determine the difference between it and the one you linked. The main purpose will not be really to flash any roms (she likes the stock), but to resolve some minor issues she has w/ her device. For example, her market fc's every time it updates - it's getting old to have to uninstall updates before she can even access the market. So I'm wanting to root so I can use TB to freeze the market updater.
cal3thousand said:
Please use the term quick boot when referring to the reboot option that does not fully restart the phone.
Use 'fastboot' to refer to the low level utility / protocol that allows image (ROM,etc) flashing via USB
Click to expand...
Click to collapse
Aha...see this is the stuff I need to learn - I simply used that term b/c it's what was in the reboot option. So it sounds like "fastboot" is the same as Downloading mode on my vibrant, correct? In other words, roms can be flashed via either clockwork or a usb connection to a computer while the device is in fastboot...?
I need to find a tutorial that explains the basics for the mt4g. It's a pretty different animal than my vibrant. I'm creating my own flashable mods for my vibrant, yet I pick up my wife's mt4g and I'm back to square one. Fruustratting!

If you already flashed it, Power Off > Hold Vol Down + Power until booted > Vol Down to recovery and select

bnielsen40 said:
No problem (clicky the thanks button ). I was actually leaning toward this method: http://forum.xda-developers.com/showthread.php?t=834225. I'm still trying to determine the difference between it and the one you linked. The main purpose will not be really to flash any roms (she likes the stock), but to resolve some minor issues she has w/ her device. For example, her market fc's every time it updates - it's getting old to have to uninstall updates before she can even access the market. So I'm wanting to root so I can use TB to freeze the market updater.
Click to expand...
Click to collapse
thats what i want i don't want to deal with flashing roms and all that crap lol i just want ROOT and keep it stock i just better not forget to UNroot before accepting an OTA update lol

hey i'am successfully rooted now with stock ROM! with the link i gave you! i think you should use the one i gave you its more detailed that the one you linked to me...theres a few things missing there in your link.

[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