Develop Bugs

My Universal Dead . Please help...

Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou

quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
Please try to enter the bootloader mode in a bright room as it is very difficult to see in poorly lit environment. Till you enter the bootloader mode your device will not be recognised. Perhaps one of the three keys is getting released..the light button is the usual culprit. Once you are in the bootloader you can reflash.

Thank d_ranade for your answer.
I am sure the screen is 'all black' and I've tried to press the buttons several times.
I think the main problem now is how to enter the Bootloader.

I sometimes find it takes several goes to get into Bootloader mode. If not, have you tried a hard reset?

I've tried whatever i can do. Hard reset is useless too.

quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
I have sent you a pm, it should help you.
-Jwrightmcps

Thank Jwrightmcps for your help, but i can not enter the Bootloader ,so can not use mtty to do more.

Unable to start/see bootloader
I seem to have the same problem with my upgraded universal which was working fine for about ten days. Then I installed TomTom on it and again it was all working that evening.
Then, when I turned it on the screen went blank (white), so I re-flashed it, but, part way through the screen went black, so I left it connected for further hour and nothing. I have since been unable to get it to do anything, it is not recognised by activesynch, it will not charge (either from the mains or the USB on either of the batteries) nor will it turn on or respond in any way.
I have unset ‘allow usb connections’. I have tried solidly for +/-10 minutes doing the backlight + on/off button and reset bit - repeatedly, with my wife helping to ensure all buttons were being pressed. All I got was a message from MicroSoft telling me that ‘One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it’. The only positive thing is that every time I do it and depress the reset, the red LED flashes (provided I leave the USB cable in) but at no point have either of us been able to see any writing on the screen.
Any guidance (apart from where to take it for recycling) would be welcome…

It happened to me several times too. Even in the old ROMS. But had learned many things out of it. I removed the battery. Wait for several seconds or maybe minute before placing it back. And after placing it back wait again for some time before doing the "power + light + reset" (bootloader). At some point when I am in the bootloader mode already and reflashing, connected to the PC already, the screen went blank again. So I'm sure that something went wrong again. I repeated the procedure again (removing battery, placing it back etc...) and the reflashing continued. It takes patience (maybe).
After having experienced this so many times, I'm beginning to assume that it is not because the battery is "bad" or there is a problem on the ROM being reflashed. It is on how it (the battery) is connected to the unit. The reason why it does not turn on, charge even if connected to the charger, does not hard reset, does not react to anything... I just don't know.
One thing more, the procedure I said above sometimes does not work at once. But at least I managed to "resurrect" my device several times.
This I am sure, it is not in the ROM that is being flashed or the update...
Hope this helps,
Lelen

lelen, Thanks for your assistance. I tried last night, but it still could not enter the bootloader mode...

I have the same problem =( and i don't know what to do, someone told me that i have to change motherbord to resolve this problem, i hope there are some other solutions.

Dead Uni
I too had this problem. With the device not responding at all and not able to enter bootloader stops mtty from working.
Only way i could get it to work was to take it to an O2 shop to send it away for repair (luckily the O2 XDA range has a 2 year warranty and because its completely dead they cant tell the OS has been modified).
Unfortunatly like the previous post i think it can only be fixed by replacing the mainboard.

Hi all, i found this thread http://forum.xda-developers.com/showthread.php?t=291097&page=6
so many people have the same problem , and nobody found a solution? i can't believe that on all this universals died motherboard, and there is no way to fix it with some special cable or some programm.

yes,i post the last reply of the thread you mentioned above, but nobody can resolve it.

I recommend you remove the battery and leave it over night. Put the battery back on, ensure it is properly mouted and try booting it.
It worked for some, no idea why though. I'm actually suspecting a bad battery mounting, which results in the motherboard unable to detect a battery is iserted, thus refusing to boot.

finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40

I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.

coolbeans252 said:
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
Click to expand...
Click to collapse
i guess thats what i will have to end up doing
anyone goten repairs done in north america?
( i live in western canada)

got the same problem
sofene said:
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
Click to expand...
Click to collapse
hi..please let me know if your device is fixed and how you managed to fix it. my email id is [email protected]

http://forum.xda-developers.com/show...6&postcount=52

Device start up failed due to sudden loss of power.

I have an extra Excalibur with the official T Mobile WM6 rom that isn't working. When I turn the phone on, I get a screen with a white background, red text, and blue soft key buttons that reads:
Device start up failed dueto s
udden loss of power. Please c
lick "yes" to continue.
Note:
Do not remove battery be
fore device has been comple
tely shutdown (OFF).
Yes | No
If I press yes the phone does a power cycle and hangs at either the T Mobile splash screen or the WM6 splash screen. I've had no luck with a hard reset. Anybody familiar with this issue? It isn't a huge deal. Currently I'm using a Cavalier and I also have a working Excalibur and a working Wizard, both with 6.1 roms. However, it's be nice to get this phone working.

Only time I ever seen that error is when I ws messing with editing a ROM and must of removed a file that screwed WM up. Now since you say it's the official T-Mo ROM maybe it got currupted somehow. How I fixed it was the Hard Reset the USB way. Hold down the camera button while plugging in the USB with the cell off. It'll load the boat loader and you need to reflash with an official ROM. Now I know you said you Hard Reset, but I've seen people explain a few differents methods all being explained as Hard resetting. This method worked for me during my testing.

I'm flashing the original rom and everything seems to be working alright.
I really appreciate your help man.

Okay, I wish I had better news but I'm still running into problems. After I finished installing the rom from T-MO's website, I powered the phone on. It showed the T-Mo screen, then the WM6 Screen, then played the T-Mo animation/sound. The screen stuck here, and the phone would not power off so I removed the battery and put it back in. I then got the original error message and pressed yes, and the phone lagged at the same point again.

how long did you wait for fist boot?

rickwyatt said:
how long did you wait for fist boot?
Click to expand...
Click to collapse
Like Ricky said, how long did you wait? The first boot could take a while, the flash is going to perform a "Cold Boot Config". It take a bit longer that first time to load.

I actually got it to prompt me for cold boot config once, but after finishing the phone rebooted and hung once again.

I don't know, maybe you got a hardware problem. I'd try reflashing it again and when it boots the first time don't touch it and see what happens. If it hangs for more then say 10 mins. I'd say you might be having a hardware problem.

Hmm. I guess I most definitely have a hardware problem. An error of that sort would most likely be from a faulty motherboard, correct? I have a dash that was taken into the lake not too long ago. Everything recovered okay, other than the screen. The phone no longer turns on for a completely different reason, but I think the guts are mostly good.
Is it possible to change out motherboards? If so, is it unwise to try the motherboard that went swimming with me over the summer?

Well considering neither work, what do you have to loose? lol I say try swapping aprts and see what comes of it. I have seen cells "go swimming before and servive as long as the battery is removed right away and it's allowed to dry thoroughly. They don't opperate on much voltage so short curcuits due to water is not as bad as say a 12 volt or higher device.

Also, I forgot to mention the status on the phone. Okay, I can flash an official ROM and it will boot up and run Cold Boot Config. After that the phone will power cycle. It hangs a little bit at the T-Mo splash screen, but does eventually start. At that point it basically works flawlessly, except I cannot detect it through ActiveSync via USB.
Once the phone powers off, it will not turn back on. I don't get the original error message, just nothing happens. Only way to get the phone turned on again is to hold the camera button down while plugging in the USB cord, and start all over flashing an official ROM.

Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.

drkfngthdragnlrd said:
Yeah, I would say hardware failure. It's a complete new flash so it shouldn't be suffering from a software problem. Maybe the ROM Chip is damaged causing errors to the WM installation. Same thing as a bad hard drive in a computer that will currupt files and end up crashing the system.
Click to expand...
Click to collapse
That's exactly what i'm thinking too, sounds like a hardware error as a flash wont solve it.

So what piece of hardware is the most likely culprit?

I never took mine apart, but I would say it's the ROM Chip which should be soldered to the motherboard. If it is replace the whole motherboard...

t mobile dash
so when holding down the camera key and plug the usb do i try to also turn it on what am i looking for and how long do i hold the keys down
thank you

xda universal dead

pls help me ..i lost connection ugrading to a new rom...now my xda exec universal is dea...even cant get into bootloeader..onmy soft reset and when i press the O for factory defoulds .still does nothing just goes to its dark screen

put it in to bootloader and flash a new rom.

universal dead
thanxs for the replay ..the universal dont even gets in bootloader. when i press the 3 keys for geting in the bootloader ,it does not .what else can i do???

Please read the wiki before posting:
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial

I think what dekyprio is saying is that the Uni does nothing while powered on. I have the same issue on my side, so for now my Uni is waiting in a box for the process to bring it back to life :-(
Any help would be appreciate.
Regards

hey,
i have the same problem. I got a looking new universal, I tried to updaty the system, but my battery is very broken, and it crashed while updating. Now, when I try to get in the bootloader, it's crashing.
I hope you can help me!! And I never worked with a windows phone, and I never tried to flash one, so I don't know sth. about doing this...
ebi

There is no backlight in bootloader mode. Go to bootloader, put the screen under a direct light source and see if it says SERIAL or USB (it will be very faint). If it doesn't, the device is almost certainly bricked. Make sure the battery isn't dead and try this while connected to USB or AC charger.
You could also try the mtty method in the stickied topic and see if the device responds at all. It could be a screen problem (long shot though).
Don't forget to remove SD and SIM cards before trying to flash.

Don't think my device is broken, as I successfully updated the ROM, then played with it, forget it more than 2 weeks on my desk. and then never wake up again.
So when battery is dried down, and the internal backup battery (I think it's a supercapacitor), are fully empty, then there is no way to bring it back to life. As the battery only start charging when at least we passed the bootloader sequence, how could we bring it back to life in that case ?
Just in addition to this, I already tried to replace the battery by an external power supply, taking care of the polarity. But without success.
Please advise.
Regards

me too,i put my device in bootloader but led not light(not light screen)

billounet said:
Don't think my device is broken, as I successfully updated the ROM, then played with it, forget it more than 2 weeks on my desk. and then never wake up again.
So when battery is dried down, and the internal backup battery (I think it's a supercapacitor), are fully empty, then there is no way to bring it back to life. As the battery only start charging when at least we passed the bootloader sequence, how could we bring it back to life in that case ?
Just in addition to this, I already tried to replace the battery by an external power supply, taking care of the polarity. But without success.
Please advise.
Regards
Click to expand...
Click to collapse
You would need a fully charged battery when flashing even if you had it on a charger while flashing, the charger will do nothing while theres a ROM being updated.

atl_luan said:
me too,i put my device in bootloader but led not light(not light screen)
Click to expand...
Click to collapse
There would be no lights when in bootloader mode nor lights on the screen but you will see SERIAL at the top and V2.01 or lower at the bottom but you would need to look closely as there are no lights.

Phone doesn't turn on!

Hey people,
Well, this day to me is not going so good. When I woke up I catched my cellphone and tried to turn it on. Nothing... Well, I tried then to plug it to the wall and recharge the battery, and still nothing. Then I tried to take it off charging and getting into Download Mode, this time with success... I don't know if it is a battery problem or what, it was fine yesterday at night...
Can you help me?
From a hopeless man... Merry Christmas!

Merry Christmas!
Be sure Battery is not empty...
If possible, check battery in other handset...
I have for instance this, for external charge...
S8500 + second battery
Best Regards

Well I do not have other battery around, but can take it to local handset's seller to see if the can manage something,,,
The method I used that was putting it charging didn't solve nothing. But I can get into download mode... This is strange as I havent flashed it...
Can I reset it through download mode?

Can I reset it through download mode?
Click to expand...
Click to collapse
If you want to loose all your data...
Again. Be sure Battery is not 0 Volt...
1.
I have damaged Battery...
It is half dead...
2.
If not enough Volt, handset NOT power on normally...
3.
Download Mode need less Battery... but maybe it will Boot Cycle... left after few Seconds Download Mode by it self...
Sorry, no other idea...
If DL Mode, then you can flash with Multiloader, YES.
But you loose all your private Pics, love SMS and so on....
Your choice.
Best Regards
P.S.:
Few bada 2.0 Betas maybe fully decharge Battery. Are you on bada 2.0 ?

Well, this looks like a Frankenmobile!
I managed to somehow turn it on. I did the DL mode combination, and it appeared downlaod mode. After a few secs, I did the same thing and it returned a blue screen, followed by a green one. Then I pressed End Key for a while and it simply turned the bootcycle on and appeared the bootanimation of bada 1.2, the one I have, XXKF3.
It showed empty battery, hour and that were completly wrong (it said 2am and that to be 1 January 2005), but everything else was fine. Then I turned it off competly and on again, but this time no success and it didnt turned on. So I did the same thing again (DL mode, blue/green screen and bootanimation again). It did turn on this time and now I am charging it to full.
Now my question is: how the hell this happened and what could cause it? Is it a defective battery?
Thank you very much for your help!
Cheers
PS: If you could say where can I buy that dock I would be pleased!

New Status:
I did manage to turn on the phone and charge it. It was almost full, only 1 bar left to full charge. I decided to turn it off to put in the memory card, but now I can't put it back on again. I can't get to the "blue/green screen" again...
So I think that it is a software problem.
I did a hardreset about 3 or 4 months ago, can it be the cause? What can I do? Will I lose my warranty becouse I did a hard reset? Or will I loose if I flash it with the same firmware?
Thank you, and Merry Christmas!

It's technically possible to check flashing history of phone, so yes - by flashing phone you're losing warranty I think. But practically I seriously doubt someone will check it if so.
Anyway, if phone doesn't even show static boot logo (white texts "Wave I/II, Samsung") it may point out hardware problem. I'd try to flash it with the same or similiar firmware if you can get dload mode, try to avoid flashing bootloaders, just do it as last resort.

Good night,
Thank you very much for the help!
I can take the phone on Wednesday to a local samsung's assistance center. So, if it is damaged, probably it will be secured by the warranty. But, I did already a hardreset on the device and I don't know if it takes out warranty, although I doubt it does, as it is a feature of the phone through settings...
I also have to point that it stopped vibration a while ago, like 6 or more months... It simply stopped. I can also stat that in the assitance center, or it will not be much of a help?
Thank you for your patience!
Merry Christmas to you all
PS: Do you know any key combination that can lead me to that "blue and then green" screen?

yes i know one
if you were trying to get download mode and you pressed volume up button instead of volume down
best regards

Hardreset doesn't take out warranty IMO. Bring it to service then.

Good afternoon,
Yesterday I managed to get into that blue/green screen again. I did that getting into download mode normally, taking of batrery while in download mode and then putting it in again and access download mode again. By doing this, it dont go to download mode somehow. I use the same key combination to acess the blue/green screen as to access the download mode. Simply, what happened was this:
1-Press download mode key combination
2-Download mode appears in red and a frame around the The screen in blue
3-Take off battery during download mode
4-Phone goes off
5- 2 Seconds later put battery on again
6- Press the download mode key combination
7- Screen goes full blue, and after few seconds goes green
8-Press End key till the phone presents the boot logo
UPDATE: Strange thing happened. I turned off the phone to put in memory card, but this time I couldnt turn it on again by that method... It's stange.
I noticed that I can acess DL mode throught end key+camera key+ ANY VOLUME KEY (Up or Down). Is this normal?

Bricked Nexus 7 [Solution?]

Hi folks,
first post but an important one. Important enough to join and hopefully get some answers.
My LTE Nexus 7 (running 5.0.2) bricked last night. It got stuck on the Google screen and I had no way to unlock the bootloader to flash a different version of the OS. SO this morning thinking I had nothing to lose I removed the back panel with the intention of tearing the thing down. Then it hit me. The common theory seems to be that it's the way the bootloader is not mounting the storage. So as the device never completely powers off what would happen if I cut the power manually. Hopefully a hard reset. So I detached the battery cable from the board and left it alone for a few moments. After popping the kettle on I returned, replaced the cable and tried turning on my Nexus. Lo and behold it works!
I have an unbricked device.
Which is great an all, but I have the proper tools and knowhow to delve into the hardware. More importantly though I'm trying to find out why that might have worked.
Any thoughts?
Has anyone else tried this as a solution to unbrick their device? Did it work?

There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button

Gorgtech said:
There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button
Click to expand...
Click to collapse
But surely that's not the same as disconnecting the battery?
Trev

It´s not the same but once you´re in a "boot loop", you have no chance of eg. entering the recovery. This is why you need a way to shut down the device first.
But in case even this "forced shut down" doesn´t help and you´re out of warranty, maybe it´s not the worst idea to open the device anyway since you´ve got nothing else to lose