Develop Bugs

Bricked Universal?

My bootloader was 0.x so I tried to upgrade to 1.0 and now I think it might be bricked.
I've read LOTS of posts here, but it won't hard reset or go into bootloader. The screen shows nothing, no matter what I do. The battery is good though as it works in my friends Uni. If I plug into my PC I get 'device not recognised' error.
Anybody got any ideas at all, ie flash from SD? Is this possible. I'll try anything!
Thanks in advance.

MTTY
Find a copy of MTTY, as notes on attached txt file, and follow brief notes.
Its a way of issuing commands direct to the PDA.
If its bricked you dont have much to loose :-(
Mike

yes it's work!
bigyellowdog said:
My bootloader was 0.x so I tried to upgrade to 1.0 and now I think it might be bricked.
I've read LOTS of posts here, but it won't hard reset or go into bootloader. The screen shows nothing, no matter what I do. The battery is good though as it works in my friends Uni. If I plug into my PC I get 'device not recognised' error.
Anybody got any ideas at all, ie flash from SD? Is this possible. I'll try anything!
Thanks in advance.
Click to expand...
Click to collapse
!!!sorry for my english!!!
your must click light key + power key + reset
then your divice ready to change your rom with out use the actve sync

mikechad said:
Find a copy of MTTY, as notes on attached txt file, and follow brief notes.
Its a way of issuing commands direct to the PDA.
If its bricked you dont have much to loose :-(
Mike
Click to expand...
Click to collapse
Thanks Mike. But the problem is that it just won't go into bootloader. I've tried MTTY before and no luck. It just doesn't see any device connected to my PC.

djmfxp said:
!!!sorry for my english!!!
your must click light key + power key + reset
then your divice ready to change your rom with out use the actve sync
Click to expand...
Click to collapse
Thanks for the suggestion but as said before it just won't go into bootloader. Appreciate any other ideas?

Big Yella - what does the phone do? Anything at all?
If it's trully fecked, you'll have to get a gold card or jtag interface. But is there any life in it at all? Do the lights come on when charging?
V

Vijay - the only sign of life is when I push the reset hole and the light flashes red. Also when the battery runs out completely and I plug in the charger the light stays red for about 2 or 3 minutes and then goes out.
Apart from that, nothing. The screen doesn't react to soft/hard reset or trying to put it into bootloader. But it was a perfectly working Uni until I tried to upgrade the bootloader from 0.x to 1.x.
Do you think I deleted the bootloader?
Thanks.

If it's not the battery, I think the bootloader it messed up and bricked...sorry

Sounds like the battery is completely dead to me.
Mine did exactly the same thing a couple of months ago but all I needed was a new battery. Had me very worried for a while too though.
I haven't still got my old knackered battery to check, but I would guess that you should be able to get the bootloader up while the device is connected to the charger (and the LED is on, and red)? Not sure if that will work if the battery is totally screwed, but if it does, then it would at least prove that the bootloader is still "there"...
EDIT: Just noticed that you say the battery works in another Uni - I'm flummoxed then! There's nothing wrong with the actual battery contacts/connections in your Universal is there - 'cause your device really is displaying exactly the same behaviour that mine did when the battery didn't work...

sub69 said:
Sounds like the battery is completely dead to me.
Mine did exactly the same thing a couple of months ago but all I needed was a new battery. Had me very worried for a while too though.
I haven't still got my old knackered battery to check, but I would guess that you should be able to get the bootloader up while the device is connected to the charger (and the LED is on, and red)? Not sure if that will work if the battery is totally screwed, but if it does, then it would at least prove that the bootloader is still "there"...
Click to expand...
Click to collapse
Cheers Sub, but no the battery is ok. It works in my friends Uni and his battery doesn't work in mine.

Edited my post above just too late to catch you! As I said though...
There's nothing wrong with the actual battery contacts/connections in your Universal is there?

sub69 said:
Edited my post above just too late to catch you! As I said though...
There's nothing wrong with the actual battery contacts/connections in your Universal is there?
Click to expand...
Click to collapse
Hmmm. The contacts/connections looks ok. Do yo think its worth taking a screwdriver to it and looking further inside? (I'm more than happy to do that, its way out of warranty)

If this happened just right after the bootloader flashing, I don't think opening it up would help. I really think the bootloader is messed up.

Unfortunately I guess clemsyn is probably right. Shame though cause I was hoping it was just a power problem, which showed the same symptoms in my case.

Request for work on Charging

As most of you know, we have had an issue with charging all nand flashed Android devices, put simply, unlike windows mobile, we cannot charge while the device is powered down.
This has caused quite a few problems for users who are unaware of this, there are many posts related to dead batteries, non-booting devices etc, and although there are steps we can take to avoid this, it is perhaps a more important issue than GPS or Camera.
This is in no way disrespect to those working on these aspects, I have nothing but admiration for the way you guys have improved upon the usability and functionality of our beloved gadgets.
However I feel that we also need to address this issue, it is, for many, a major stumbling block, which causes many to return to Windows mobile, with a sense of dissatisfaction for all that has been achieved.
Much as I'd love to work on this, my skills are not in this field, and have no idea where to start looking, although I suspect it's Kernel based, since it affects all builds.
So what I'm asking for is for those with more knowledge than me, to start throwing a few ideas around, see what we can come up with.
Thanks for reading this

zenity I don't think that is a big issue cause there is a workaround.
I already post this in Warm Donut thread and I learned from polyrhythmic
When your battery is dead, plug phone into the charger and when the LED turns orange power on the device. Then leave it alone to charge.
My battery drains out at least twice a week and powering on while LED is orange always worked for me.

I know this isnt the thread for work arounds but I wanted to put my two cents in...
When phone is dead (power button does nothing):
1. Plug in for about 20 seconds
2. Unplug
3. Remove and replace battery
4. Turn on
5. Plug in again.

Well while we are throwing 2cents in the pot...
My experience was thinking I destroyed my phone cause even after being on charge for some time after full battery drain it wouldn't come on with power button... Finally poked soft-reset button and it booted right up, and since then I've learned on complete drain, plug in for a couple minutes then hit reset and it comes on...

Ive also noticed the soft reset thing, but for me the experience is mostly quite different. I havent experienced a long delay between dead battery and charging maybe but whenever my phone turns off at 0% battery, almost every time it turns on automatically when I plug in the charging cable, and I get the charging sound notification during the android splashscreen. I'm using myns warm donut on nand.

The problem is that all these workarounds are not addressing the root of the problem, we cannot charge while switched off, and this is the issue I'd like to see a solution to.
I like the simplicity of the plug in and power on workaround though, didn't think of that, lol.

when you flash nbh kernel on device, you overwritting standard bootloader, that knows about system state, when you plugging charger in - phone waits sometime and starts bootloader, that starts kernel without display powered up (you can see it on flashing LEDs) - to fix this problem, we need dump that bootloader code from winmo nbh and try to include it to our bootloader.
problem is - nobody knows how to do that

Well that's an answer, lol, perhaps not the one I expected, but at least it gives somewhere to look

rzk333 said:
when you flash nbh kernel on device, you overwritting standard bootloader, that knows about system state, when you plugging charger in - phone waits sometime and starts bootloader, that starts kernel without display powered up (you can see it on flashing LEDs) - to fix this problem, we need dump that bootloader code from winmo nbh and try to include it to our bootloader.
problem is - nobody knows how to do that
Click to expand...
Click to collapse
OK... that gives me and idea....
BRB...

Nevermind...
I had pulled apart the winmo nbh before, so I thought I would give it a try...
I think the HardSPL most of us install to get android installed is the issue.
I flashed just the spl that came with the stock HTC rom for tilt,
it wrote OK but didn't overwrite the HardSPL and didn't fix the charging.
I know some people flash the android nbh without going to hardspl first.
my question would then be...
can anyone that has the original stock spl on the phone charge android with the phone off?

I think we need HardSPL on our phones to flash the NBH anyway, however wouldn't that affect winmo charging also?

zenity said:
I think we need HardSPL on our phones to flash the NBH anyway, however wouldn't that affect winmo charging also?
Click to expand...
Click to collapse
I haven't gone back to winmo in so long...
Does the phone charge while off in winmo after installing hardspl???

Yes it does, got my spare kais on stock winmo for a work related development project just now, it charges fine when off, hardSPL 3.34.

well that just shoots a hole in my theory then doesn't it...
the contents of the stock nbh are as follows...
00_GSM_0x301.nb (radio)
01_SPL_0x200.nb (Bootloader)
02_MainSplash_0x600.nb (Bootsplash)
03_OS_0x400.nb (windows mobile OS)
when flashing android nbh's we only change the OS
most of us have changed the radio as well as flashing HARDSPL
I have changed my Bootslpash as well but I am sure that isn't the problem.
like I said... I flashed just the stock spl back to the phone.
but it didn't change the HArdSPL.
however, if the phone still charges with the winmo OS and Hardspl
I am again at a loss.

just reread this:
HardSPL prevent you from accidently flashing a new SPL (you must use Jump/Soft SPL for this) and SuperCID your phone.
Click to expand...
Click to collapse
so that explains the spl flash not overwriting hardspl...
not sure we want to do that anyway.

As far as I'm aware it's kernel related, but I really don't know enough about it to know exactly the relationship between the kernel and how it handles charging while off.
When switched off something must wake up the kernel in order to initiate the charging process, now why does it stop charging? That is the problem that has to be solved.

here is a quote from the wiki...
Why would I want to change my SPL back after I HardSPL?
Up until a week ago the answer you would have probably gotten is "you wouldn't." However with the release of the Official 6.1 HTC ROM there has been alot of speculation, and some real data inferring that for best performance of a ROM you should use the SPL that came with a ROM or at the very least (to put it another way) you should use a newer SPL with a newer ROM.
There is no definitive proof or specific results that can show you how one SPL will make your device perform over another. I believe I have conducted the most "scientific" experiments on this to date which you can find here. However which SPL you use is up to you based on how you feel it makes the device operate. I recommend however that you use either one of the HardSPLs or the SPL that came with your ROM. It is not recommended (at this point) to run your ROM with an SPL that is not matched to it.
Click to expand...
Click to collapse
maybe the SPL is looking for winmo...
do we need an android specific hardspl???
or like you said it may be kernel related.

Just looking for patterns everyone one in this thread is using the newest radio. Maybe try an older radio. My thought is that maybe the battery never went to 0 when you were using wimo and the newest radio (my case).
On a side note. It is really bad to let LiOn batteries go to 0. they are different than NiCad yet many keep the same habits. NiCad had to be drained for the memory problem that LiOn doenst have. I always turn my phone off at 10% if i cant get to a charger. Never need to charge with the phone off.

and look at that, as soon as i comment on battery stuff my phone shuts off and i have to charge with it off

blindguyinanorgy said:
Just looking for patterns everyone one in this thread is using the newest radio. Maybe try an older radio. My thought is that maybe the battery never went to 0 when you were using wimo and the newest radio (my case).
Click to expand...
Click to collapse
Ok not the case, i just tryed with a old radio 1.65.x
Are we sure that its not working? Inside the OS the light blinks and in wimo it was solid. could it just be that once the SPL loads the kernal that the light turns off? I remember leaving my phone plugged in even though the light was off and it turned on charged to 40%(when i got to where i was going).
In the end I still think a good fix is to have the phone shut down at 5%. I remember wimo did this, and as much as you wanted to turn it back on, it just shut down(could be changed, yes). Much better for LiOn anyway. This would help keep the install from going corrupt.

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.

You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.

Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin

Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.

Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.

Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.

I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.

"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.

[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.

Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.

[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.

15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.

Repair bricked phone

Hi everybody!
I have an almost 2 years old DHD which I think is completely bricked. It was working for approximately one years perfectly and then suddenly it stopped working. Whenever I tried to turn it on, it only vibrated once and did nothing more. Sometimes it turned on and these working periods were enough to restore to stock condition (It was rooted and had Eng S-OFF before.). I had brought it to service and they said they was not going to repair it as the device got water damaged. I'm pretty sure it was not! After a few weeks, it started working again. I was using it for 3 months then it bricked again and it's the situation today as well.
Previous week I looked into the development thread and saw all of these new amazing roms. So I took my DHD to see if it's working or not. The situation is the same. Everytime I power it on, the phone only vibrates once and nothing happens. I'm not able to get into hboot mode. At some very rare occassions the phone turns on and works flawlessly till reboot. When I connect it with USB, the computer doesn't recognize it. Battery is charged, I even tried another battery.
Does anybody know what happens with the phone? I'm open to any possible solutions to try. Please don't suggest to bring it to service or repair it, because I have another phone, just want to try to recover it and ask your ideas about the problem.
Thanks in advance!
Greetings,
Adam

So you say you cant enter in fastboot or recovery?

Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.

paescheh said:
So you say you cant enter in fastboot or recovery?
Click to expand...
Click to collapse
I cannot enter into hboot mode. Didn't try recovery, but assume it's the same.
waterbox said:
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
Click to expand...
Click to collapse
I also think it's a hardware problem. Will take a more careful look at the battery.
Sent from my CM10-powered GT-I9103

need help
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...

goofed again said:
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
Click to expand...
Click to collapse
Wrong sub forum buddy, post in the One V Forum.

Its possible that there isn't "water damage", but there could be moisture getting into the phone causing it to act erratic. To cancel out that possibility, submerge it in a closed container full of rice for a few days
Sent from a satellite

[Q] $$$ for HELP

Before flaming me... notice I've been a member since 2009 with my G1, and also notice that I've barely posted. I mostly read, search, and follow instructions.
I am having a problem that I've never seen before through all the Android's I've had. It's SIMILAR to one's I've seen, but NOT the same. I'm hoping someone can take a minute to give me ideas.
The other night I installed TWRP 2.6.0.0 via GooManager... when I chose "reboot recovery" from inside GooManager just to see what had changed and then the following happened........................
My GS2 will NOT boot up. Will NOT charge. Will NOT go into recovery... however it WILL GO INTO DOWNLOAD (ODIN) MODE. I've bricked phones before... never once have I been able to access DL mode. HOWEVER: I cannot get the PC (ODIN, ADB, GS2 Toolkit, Keis) to recognize the phone in download (or any) mode. When I try to boot the phone unplugged the Samsung logo will flash up quickly then the screen goes blank. Typically I'd see Deviant Development or Cyanogenmod Boot Anim at this point but NOTHING. Just goes black. Same result for manually trying to boot into recovery. When plugging the device in while powered off, I will get an empty battery with "waiting/busy/thinking" circle inside of it for a second then it also goes blank.
What I've tried:
-uninstalling Samsung USB drivers and reinstalling (both versions i could find in my PC and online- v1.3.2200.0 and 1.5.14.0 or something close to those)
-uninstalling Keis and reinstalling in combo with the Samsung drivers
-uninstalling all traces of drivers from anywhere and seeing if Windows Update would notice it
-different USB cables... about 9
-other Samsung Android phones in DL mode (windows immediately recognizes them and installs necessary drivers)
-CRC QD Electronic Cleaner inside USB
-took apart phone, gently cleaned with alcohol and insured no loose pieces
-tried with no battery inserted
-probably other's I've forgotten by now
I'm begging and willing to pay at this point for the person who helps me fix my phone. I cannot afford a new one. Samsung and T-Mobile are not willing to do anything for me. I'm pretty good with Android, and with using ADB for simple tasks. If it's possible to have happened- it honestly seems like the Recovery and OS got deleted. Either that or the USB port has gone bad but no tabs are bent inside and all "looks" fine.
Again, a CASH reward is being offered to the person who helps me FIX this. How much $ will be considering how much work it takes for the individual(s) to help fix it.

Did you try different USB ports? Or a different computer?

meekrawb said:
Did you try different USB ports? Or a different computer?
Click to expand...
Click to collapse
ports yes, computer no... i don't have any others built here at my house. i just dont see how all the other phones and cables are working with this PC... how could that matter. im willing to try it but i just dont have another one up and going yet.

Try opening kies and selecting "Emergency firmware recovery"
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
Hope this helps:
http://forum.xda-developers.com/showthread.php?t=2261153
Sent from my Nexus 7 using xda app-developers app

Droid8Apple said:
Before flaming me... notice I've been a member since 2009 with my G1, and also notice that I've barely posted. I mostly read, search, and follow instructions.
I am having a problem that I've never seen before through all the Android's I've had. It's SIMILAR to one's I've seen, but NOT the same. I'm hoping someone can take a minute to give me ideas.
The other night I installed TWRP 2.6.0.0 via GooManager... when I chose "reboot recovery" from inside GooManager just to see what had changed and then the following happened........................
My GS2 will NOT boot up. Will NOT charge. Will NOT go into recovery... however it WILL GO INTO DOWNLOAD (ODIN) MODE. I've bricked phones before... never once have I been able to access DL mode. HOWEVER: I cannot get the PC (ODIN, ADB, GS2 Toolkit, Keis) to recognize the phone in download (or any) mode. When I try to boot the phone unplugged the Samsung logo will flash up quickly then the screen goes blank. Typically I'd see Deviant Development or Cyanogenmod Boot Anim at this point but NOTHING. Just goes black. Same result for manually trying to boot into recovery. When plugging the device in while powered off, I will get an empty battery with "waiting/busy/thinking" circle inside of it for a second then it also goes blank.
What I've tried:
-uninstalling Samsung USB drivers and reinstalling (both versions i could find in my PC and online- v1.3.2200.0 and 1.5.14.0 or something close to those)
-uninstalling Keis and reinstalling in combo with the Samsung drivers
-uninstalling all traces of drivers from anywhere and seeing if Windows Update would notice it
-different USB cables... about 9
-other Samsung Android phones in DL mode (windows immediately recognizes them and installs necessary drivers)
-CRC QD Electronic Cleaner inside USB
-took apart phone, gently cleaned with alcohol and insured no loose pieces
-tried with no battery inserted
-probably other's I've forgotten by now
I'm begging and willing to pay at this point for the person who helps me fix my phone. I cannot afford a new one. Samsung and T-Mobile are not willing to do anything for me. I'm pretty good with Android, and with using ADB for simple tasks. If it's possible to have happened- it honestly seems like the Recovery and OS got deleted. Either that or the USB port has gone bad but no tabs are bent inside and all "looks" fine.
Again, a CASH reward is being offered to the person who helps me FIX this. How much $ will be considering how much work it takes for the individual(s) to help fix it.
Click to expand...
Click to collapse
A lot of people have had trouble updating through goo. Some in this thread discuss it: http://forum.xda-developers.com/showthread.php?t=1768742
All seem to solve their problem with Odin though. Make sure you're on Odin 1.85, I used 1.84 by mistake once and it kept failing and once crashed my computer. Also make sure to deactivate Kies, Odin won't work with it running. Sometimes we miss basic stuff when we're stressing!
T989D
latest CM10.1
latest Uber

Go into Samsung kies and try a emergency firmware update
sent from my xylonified phone....

Droid8Apple said:
ports yes, computer no... i don't have any others built here at my house. i just dont see how all the other phones and cables are working with this PC... how could that matter. im willing to try it but i just dont have another one up and going yet.
Click to expand...
Click to collapse
The only other advice I can think of is to try making a new Windows user account and give it administrative privileges.

Droid8Apple said:
Before flaming me... notice I've been a member since 2009 with my G1, and also notice that I've barely posted. I mostly read, search, and follow instructions.
I am having a problem that I've never seen before through all the Android's I've had. It's SIMILAR to one's I've seen, but NOT the same. I'm hoping someone can take a minute to give me ideas.
The other night I installed TWRP 2.6.0.0 via GooManager... when I chose "reboot recovery" from inside GooManager just to see what had changed and then the following happened........................
My GS2 will NOT boot up. Will NOT charge. Will NOT go into recovery... however it WILL GO INTO DOWNLOAD (ODIN) MODE. I've bricked phones before... never once have I been able to access DL mode. HOWEVER: I cannot get the PC (ODIN, ADB, GS2 Toolkit, Keis) to recognize the phone in download (or any) mode. When I try to boot the phone unplugged the Samsung logo will flash up quickly then the screen goes blank. Typically I'd see Deviant Development or Cyanogenmod Boot Anim at this point but NOTHING. Just goes black. Same result for manually trying to boot into recovery. When plugging the device in while powered off, I will get an empty battery with "waiting/busy/thinking" circle inside of it for a second then it also goes blank.
What I've tried:
-uninstalling Samsung USB drivers and reinstalling (both versions i could find in my PC and online- v1.3.2200.0 and 1.5.14.0 or something close to those)
-uninstalling Keis and reinstalling in combo with the Samsung drivers
-uninstalling all traces of drivers from anywhere and seeing if Windows Update would notice it
-different USB cables... about 9
-other Samsung Android phones in DL mode (windows immediately recognizes them and installs necessary drivers)
-CRC QD Electronic Cleaner inside USB
-took apart phone, gently cleaned with alcohol and insured no loose pieces
-tried with no battery inserted
-probably other's I've forgotten by now
I'm begging and willing to pay at this point for the person who helps me fix my phone. I cannot afford a new one. Samsung and T-Mobile are not willing to do anything for me. I'm pretty good with Android, and with using ADB for simple tasks. If it's possible to have happened- it honestly seems like the Recovery and OS got deleted. Either that or the USB port has gone bad but no tabs are bent inside and all "looks" fine.
Again, a CASH reward is being offered to the person who helps me FIX this. How much $ will be considering how much work it takes for the individual(s) to help fix it.
Click to expand...
Click to collapse
OK this is he fix for that, can u get into DL mode? If u can its an easy fix
---------- Post added at 08:46 PM ---------- Previous post was at 08:37 PM ----------
Droid8Apple said:
Before flaming me... notice I've been a member since 2009 with my G1, and also notice that I've barely posted. I mostly read, search, and follow instructions.
I am having a problem that I've never seen before through all the Android's I've had. It's SIMILAR to one's I've seen, but NOT the same. I'm hoping someone can take a minute to give me ideas.
The other night I installed TWRP 2.6.0.0 via GooManager... when I chose "reboot recovery" from inside GooManager just to see what had changed and then the following happened........................
My GS2 will NOT boot up. Will NOT charge. Will NOT go into recovery... however it WILL GO INTO DOWNLOAD (ODIN) MODE. I've bricked phones before... never once have I been able to access DL mode. HOWEVER: I cannot get the PC (ODIN, ADB, GS2 Toolkit, Keis) to recognize the phone in download (or any) mode. When I try to boot the phone unplugged the Samsung logo will flash up quickly then the screen goes blank. Typically I'd see Deviant Development or Cyanogenmod Boot Anim at this point but NOTHING. Just goes black. Same result for manually trying to boot into recovery. When plugging the device in while powered off, I will get an empty battery with "waiting/busy/thinking" circle inside of it for a second then it also goes blank.
What I've tried:
-uninstalling Samsung USB drivers and reinstalling (both versions i could find in my PC and online- v1.3.2200.0 and 1.5.14.0 or something close to those)
-uninstalling Keis and reinstalling in combo with the Samsung drivers
-uninstalling all traces of drivers from anywhere and seeing if Windows Update would notice it
-different USB cables... about 9
-other Samsung Android phones in DL mode (windows immediately recognizes them and installs necessary drivers)
-CRC QD Electronic Cleaner inside USB
-took apart phone, gently cleaned with alcohol and insured no loose pieces
-tried with no battery inserted
-probably other's I've forgotten by now
I'm begging and willing to pay at this point for the person who helps me fix my phone. I cannot afford a new one. Samsung and T-Mobile are not willing to do anything for me. I'm pretty good with Android, and with using ADB for simple tasks. If it's possible to have happened- it honestly seems like the Recovery and OS got deleted. Either that or the USB port has gone bad but no tabs are bent inside and all "looks" fine.
Again, a CASH reward is being offered to the person who helps me FIX this. How much $ will be considering how much work it takes for the individual(s) to help fix it.
Click to expand...
Click to collapse
Just read a little more of your post here is how u can fix it and its very simple, the thing is goomanager has been a little f'd up lately, its been softbricking ppls phone since 2.6 came out, u need to go here http://techerrata.com/browse/twrp2/hercules and download twrp 2.6.0 tar file, turn off or uninstall kies, odin will never connect or see the phone if kies is running, even if in the background odin will never see the phone if kies is abywhere near it, and kies wont see it because its modified software wise, now open Odin file and run the app, put the Hercules into DL mode and connect to PC with your factory OEM USB cable, Hercules doesn't like any other cable with Odin for some reason, Odin should say "Added" once it does click on the PDA box- DONT CHECK ANYTHING ELSE, find the tar file u downloaded from the link i put above, the click start, Odin should take about 1min to do its thing, do not dissconect the phone at all until Odin gives the green "passed" signal in upper box, Odin will auto reboot ur device and that should've fixed it, if not u may need to flash another rom bit don't worry all easy fixes, I can't stress how important it is to not panic in these situations, follow what I said and ur herc will be good as new, no I don't want the money, just forward the help to the next person...

I'm about to try this. Let it rest a few days. I will go into the PC and remove kies and all its traces... I have tried many times without it installed and still it won't recognize the phone. Even with the 3 OEM cables I tried. I do use Odin 1.85 and have a few tar laying around I would have used had I got a connection. Other galaxy phones and my wife's captivate glide are recognized as soon as I plug them in. I just feel like it is more than it is letting on to. Like ... something as stupid as could the battery be bad. Would it cause this. Did a jig for my i897 mess up my USB port or motherboard. I'm just so upset. Using a crappy $20 phone and it sucks bad. Thanks to all who have helped so far. Going to take a few more stabs at it.
Sent from my Nexus 7 using XDA Premium HD app

meekrawb said:
The only other advice I can think of is to try making a new Windows user account and give it administrative privileges.
Click to expand...
Click to collapse
thank you, i'm trying this right now, just deleted all traces of samsung anything off the computer and am going to reboot. not a bad idea.

Kies fixed my soft brick when odin didn't work, don't underestimate it
Sent from XDA app

Droid8Apple said:
I'm about to try this. Let it rest a few days. I will go into the PC and remove kies and all its traces... I have tried many times without it installed and still it won't recognize the phone. Even with the 3 OEM cables I tried. I do use Odin 1.85 and have a few tar laying around I would have used had I got a connection. Other galaxy phones and my wife's captivate glide are recognized as soon as I plug them in. I just feel like it is more than it is letting on to. Like ... something as stupid as could the battery be bad. Would it cause this. Did a jig for my i897 mess up my USB port or motherboard. I'm just so upset. Using a crappy $20 phone and it sucks bad. Thanks to all who have helped so far. Going to take a few more stabs at it.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That is very strange indeed then, I can't think of any other task reason as to why it wouldn't recognize the device, if kies isn't installed and ur on OEM cable and drivers are installed that's very strange indeed I don't think I've ever run into an issue like that, I do know goo has been fing ppls phones up lately but I also heard they got it fixed so Im lost, I mean theoretically it could be the battery but it still doesn't make sense because u should get done response even with no battery, let me look into it a little more, now I'm interested, pm me if u figure it out or any new info this struck an itch in my brain lol sorry to hear about the herc, I lost mine for a whole day due to a bad Odin flash once and was freaking out cuz I had to use my old precedent so I feel for u, just doesn't make sense...

no luck
soupysoup said:
That is very strange indeed then, I can't think of any other task reason as to why it wouldn't recognize the device, if kies isn't installed and ur on OEM cable and drivers are installed that's very strange indeed I don't think I've ever run into an issue like that, I do know goo has been fing ppls phones up lately but I also heard they got it fixed so Im lost, I mean theoretically it could be the battery but it still doesn't make sense because u should get done response even with no battery, let me look into it a little more, now I'm interested, pm me if u figure it out or any new info this struck an itch in my brain lol sorry to hear about the herc, I lost mine for a whole day due to a bad Odin flash once and was freaking out cuz I had to use my old precedent so I feel for u, just doesn't make sense...
Click to expand...
Click to collapse
so here is a brief update... tried everything that was replied. im getting ready to make a video just so the hacking world can see. thats what i mean, im no NooB when it comes to this stuff. i've been building computers since i was 14... not a genius but i've never gotten "stuck" before. even when bricked i have found out how and coached people how to fix their issues lol. doesn't make any sense at all to me either. i tried searching everything i could and came up with people who had similar issues not exact. unlike you, some who replied to this didn't read my entire post especially where it says "what i've tried" lol. glad you did though. i cant tell you how much it means to me that you're thinking about it. i wish there was a way to "escalate" this matter lol. i bet the original Cyanogen dev Steve Kondik would know in a heartbeat. not discrediting anyone just saying. i bet he has come acrossed it before. unfortunately though i was running JMT6 i didn't receive any help from Deviant Development when i posted to their facebook group. Just wish more people were on who'd take a second to help others like you did. thanks again.

*_!*_!*_!*_! I tried kies folks *_!*_!*_!*_!*_!*_!
gc84245 said:
Kies fixed my soft brick when odin didn't work, don't underestimate it
Sent from XDA app
Click to expand...
Click to collapse
GUYS I'VE TRIED EVERY POSSIBILITY WITH KIES. Anything that Kies could give me right now in this state (aka: one of 2 things... install drivers 50 times or 'emergency firmware upgrade' which requires an acknowledged connection to PC and a screen that is similar to the DL screen but indeed is not the DL screen...) i have tried. that's why i went through the hassle of making this post... if it were a basic, every-day NooB problem i would have fixed it already...
sorry if that sounds trollish but i took the time i did writing the "issues/what i've tried" in the original post for a reason. this goes far beyond what Kies can do for me. thank you very much for the help though, much obliged!

Droid8Apple said:
so here is a brief update... tried everything that was replied. im getting ready to make a video just so the hacking world can see. thats what i mean, im no NooB when it comes to this stuff. i've been building computers since i was 14... not a genius but i've never gotten "stuck" before. even when bricked i have found out how and coached people how to fix their issues lol. doesn't make any sense at all to me either. i tried searching everything i could and came up with people who had similar issues not exact. unlike you, some who replied to this didn't read my entire post especially where it says "what i've tried" lol. glad you did though. i cant tell you how much it means to me that you're thinking about it. i wish there was a way to "escalate" this matter lol. i bet the original Cyanogen dev Steve Kondik would know in a heartbeat. not discrediting anyone just saying. i bet he has come acrossed it before. unfortunately though i was running JMT6 i didn't receive any help from Deviant Development when i posted to their facebook group. Just wish more people were on who'd take a second to help others like you did. thanks again.
Click to expand...
Click to collapse
Haha I'm STILL thinking about it lol, like u I've been building and hacking software for around ten yrs now, and also like u I've never just been stuck, I've bricked devices and still brought them back, even applied the unbrickable mod to my captivate and never have I just not been able to explain what was going on lol, I help whenever I can because I may be the one asking for help someday, this issue u have though is very perplexing, it can't be the port if the phone still goes into DL mode, but then why is it not able to connect? The PC should see something, even a hard brick gets noticed by PC as being there, can't get a flashable connection but the pc still sees it, I've been working this over for 2 days now lol, I am trying for u buddy lol
Sent from my SGH-T989 using Tapatalk 4 Beta

btw...
soupysoup said:
That is very strange indeed then, I can't think of any other task reason as to why it wouldn't recognize the device, if kies isn't installed and ur on OEM cable and drivers are installed that's very strange indeed I don't think I've ever run into an issue like that, I do know goo has been fing ppls phones up lately but I also heard they got it fixed so Im lost, I mean theoretically it could be the battery but it still doesn't make sense because u should get done response even with no battery, let me look into it a little more, now I'm interested, pm me if u figure it out or any new info this struck an itch in my brain lol sorry to hear about the herc, I lost mine for a whole day due to a bad Odin flash once and was freaking out cuz I had to use my old precedent so I feel for u, just doesn't make sense...
Click to expand...
Click to collapse
btw, something weird... once i created the new account on my PC and tried different cables, when trying my HTC EVO 4G (old school) cord i got the "duh-dum" from windows as if it knew i plugged my device in- however it didn't pop up with "installing device driver software" nor show up in Device Manager anywhere... i got it to make the sound on/off maybe 3 times in half an hour.
so... to tease your brain even more... why would ONLY the HTC cord make it do that and why wasn't anything "happening" in the pc? even driver manager (freeware) doesn't do anything.

Droid8Apple said:
btw, something weird... once i created the new account on my PC and tried different cables, when trying my HTC EVO 4G (old school) cord i got the "duh-dum" from windows as if it knew i plugged my device in- however it didn't pop up with "installing device driver software" nor show up in Device Manager anywhere... i got it to make the sound on/off maybe 3 times in half an hour.
so... to tease your brain even more... why would ONLY the HTC cord make it do that and why wasn't anything "happening" in the pc? even driver manager (freeware) doesn't do anything.
Click to expand...
Click to collapse
That's very strange lol, so it only made the connection sound when using the HTC cord? Now that I can't explain lol, but, I'm trying to recreate ur issue on another device, I'm going to figure it out lol it's like that proverbial itch u just have to scratch lol, so even with the connection sound from windows the device is still not seen anywhere? Uuughh
Sent from my SGH-T989 using Tapatalk 4 Beta

haha
soupysoup said:
Sent from my SGH-T989 using Tapatalk 4 Beta
Click to expand...
Click to collapse
^^^^^
HAD to throw that in there didn't you... the fact that yours is still working hahaha jk.
anyhow like i said its awesome you're thinking about it and trying for me. really appreciate that. and i agree- never seen anything like that. ready to start waving cash wads around hahaha. you're exactly right though- example here:
take out battery, insert battery, press volume hardware keys to get into download and plug in charging cord.... it shows me samsung and just starts rebooting and vibrating every 2 seconds until i let go and unplug....
take out battery, insert battery, press volume hardware keys to get into download and plug in USB cord... goes into "blah blah blah press volume up to continue to download, press volume down to restart device" so i obviously hit UP and it goes into download. it HAS TO know im connected to the computer.
there's a chance it just reads how much voltage is coming into the USB and determines whether or not to go into DL mode- i've seen that before. just wish i had another PC here to try on.
about ready to give out my LogMeIn info and let people see im not crazy hahaha

Droid8Apple said:
^^^^^
HAD to throw that in there didn't you... the fact that yours is still working hahaha jk.
anyhow like i said its awesome you're thinking about it and trying for me. really appreciate that. and i agree- never seen anything like that. ready to start waving cash wads around hahaha. you're exactly right though- example here:
take out battery, insert battery, press volume hardware keys to get into download and plug in charging cord.... it shows me samsung and just starts rebooting and vibrating every 2 seconds until i let go and unplug....
take out battery, insert battery, press volume hardware keys to get into download and plug in USB cord... goes into "blah blah blah press volume up to continue to download, press volume down to restart device" so i obviously hit UP and it goes into download. it HAS TO know im connected to the computer.
there's a chance it just reads how much voltage is coming into the USB and determines whether or not to go into DL mode- i've seen that before. just wish i had another PC here to try on.
about ready to give out my LogMeIn info and let people see im not crazy hahaha
Click to expand...
Click to collapse
Oh I believe u lol I've seen some unbelievable stuff before, just never like this, and yes I guess it could be acting like a jig but then where are u getting the 301k to jump it lol believe me I had my herc for a day, went to root it and Odin failed halfway through bcuz I forgot to disable kies, which led me to " firmware upgrade encounter an issue, please select recovery in kies and try again" for two days because it wouldn't connect and that's the only screen it would boot to, ugh had to use my old zte merrit, ugh that sucked, so I feel for u buddy, have u tried different PCs? I can't think of any other reason, if u have no other way u could JTAG it, I know I know but as a last alternative, I got a buddy with a box, I'm trying to recreate it on a galaxy precedent but all I've gotten so far was a few soft bricks I can't figure out why its not being seen as anything, there should be something there, somewhere, even if it only sees the qualcom chip something should be seen with PC...
Sent from my SGH-T989 using Tapatalk 4 Beta

yeah... ive been thinking about that. on the other hand im thinking that $400 isnt that much money and i'd really like an upgrade lol. id LOVE a Note 2 or GS4... but that takes time and patience and saving for a couple weeks... therein lies the problem haha. this guy right here has limited patience.
keep plugging away at it (no pun intended) and let me know if you have any new ideas.