Develop Bugs

Universal Died while upgrading

hi
i was upgrading my universal, following instructions from http://wiki.xda-developers.com/index.php?pagename=Helmi
after upgrading, on my computer i received an error saying the upgrade was unsuccessful and now my universal is dead
i tried hard resetting, i tried putting it into bootloader mode...
there is nothing on the screen
what should i do?

have you ever entered BL before? most new users would not realise their in BL as it doesn't have any backlight. look closely

yes, i have, it isnt working at all, there is nothing on the screen
when i try to flash the device the pc says error 101 connection error

does your charge light appears when connected to AC power?

nope, no charge light
its sad just about 3 hours ago my device was working perfectly

here's what you do:
start activesync on your computer.
Go to connection settings and deselect allow usb connections.
connect your uni to your computer and push the backlight + on/off button and hold these. Then press the reset with your pen, still holding the backlight and on/off.
The screen should say something about serial or usb.
The backlight will not be lighted so it's hard to read.
If the screen doesn't say anything, unplug and plug in the usb connecter one more time.
Does your red charge led lit when you put it on the wallcharger ?

i tried that, many many times, screen still remains blank
nope, no red light when i plug it into the wall
this is bad, its not responding to anything

When plugged, does it give you a red blink (Charge light) when you Soft Reset?

yes!
yes, the first sign of life, when pluged in via usb to the pc, when i soft reset i get a red blink
any ideas?

Try holding down Light + power for at least 5sec. and while still pressing, do a soft reset.
If you dont go to BootLoader then try to increase the Hold down Light + Power some more.

And BTW. dont get stressed, keep cool.
Youl just **** it even more up if you get stressed, Ok

k, i just tried that, everytime i let go fo the soft reset button the pc says the usb device is not recognized, but still nothing on the screen

lol yeah ur right
thanks for the help

NP. now run the original upgrade for your device...your device is in boot loader right?

nope no bootloader, the screen is completely blank

sahir said:
nope no bootloader, the screen is completely blank
Click to expand...
Click to collapse
Look closely, it wont have backlight on, so look really closely.
Remove the SD card and Sim, and just keep trying different time intervals with the "holding down Light + power for at least 5sec. and while still pressing, do a soft reset."
And if you had low battery when you started the upgrade, the use your Wall charger, not USB charger...and let it stay in for 1/2 hour before proceding.
Keep us updated

i removed the sim and sd, and have tried many different intervals, i charged the device all night last night with teh wall charger, still no luck

Hmmmmm, this is a bit strange.
The exact same thing happend to me some 5 days ago.
I managed to get it back with this trick.
Try Soft Reset between every try....just hang in there suddently it wil come to life

Do a ATX-reset/Destat.
Remove charger, battery etc and push in on/off button for 30sec twice. Then push down as many keyboard buttons as you can for a little while too. This way you "drain" it and everything should be reset. Try again.
Works especially well on computers that don't wanna POST. Same thing with cellphones, TV's, remotes etc.
ATX-Reset/Destat. Remember that one. Can solve loads of glitches.
How do I know?
Don't ask I work with these kind of issues every day.

i just tried the atx reset destat idea, it didnt boot it up
ive tried many different intervals now, ive spent hours trying to get this to work
bosjo were u connected to the pc while trying to get it into bootloader?

[FIX] [GUIDE] My story of how I messed up in Aroma Installer + Fix

I was trying to flash the Lifeless rom back onto my phone, and had Aroma wizard started up, and was checking the options I wanted, when I remembered that absentminded me had forgotten to do something in the OS that I can't remember at the moment. I didn't see a cancel button in Aroma, and since I'm so impulsive, I held down power and volume up to reboot the phone. It nearly booted to the OS, with the capacitive keys lighting up at the bottom, when it suddenly shut off and attempted to reboot (maybe because I was flashing AC!D audio earlier and had checked the build.prop tweaks). It didn't reboot, but seemed BRICKED.
Ok, the actual problem.
It seemed totally hard bricked to me, nothing when I plugged it in to my PC or charger, so I, enraged, walked away and left my Optimus plugged in. When I came back, I saw that the notification light was blinking red, one shade of red brighter than the other. I gained some hope back by...
The FIX
... following the directions on YouTube (look it up, I can't post links) on performing a hard reset by disassembling the phone and disconnecting/reconnecting the battery connector. I, however, had to do a little twist to get my phone to PARTIALLY boot.
When I detached the battery connector from the mainboard,(phone still plugged in) the phone would proceed to bootloop, showing up the unlocked Google screen, etc. (flashed the ZVB Teenybin, that's why the Google screen) until it got to the battery charging icon in the center with the lightning bolt in the center. At this point, I reattached the battery connector and BOOM, the phone rebooted NOT LOOPING , PARTIALLY STILL but with the battery icon animation stacking up.
Unfortunatly, my battery was nearly dead so I then waited for a bit and let it charge up.
I held down the power button + vol up (on my bare phone with the backing taken off) to get it to boot into fastboot, then TWRP to flash the rom. I SUCCESSFULLY flashed the rom (relieved at this point) and I booted FULLY :laugh: . It got me to the Optimizing apps numberhere/biggernumberhere screen. Suddenly, the frickin phone shuts off and the notification light blinks red, but with a delay this time instead of a brighter shade of red. I did what I did before numerous times, but the phone would stay alive less and less.
I let the phone cool off for a bit (Heating issues on the Optimus ), tried charging it again, and I managed to finish optimizing my apps. It loaded up the lock screen for a split second, and then shut off with the LG goodbye animation.... Which is a hell of a lot better than a blinking reset light.
So after it shut off I let it charge...
And I was back!
NOTES:
The video I describe was originally made to resolve some other reset indicator, with alternating blinking capacitive buttons and the notification light, but also helps with the issue I had with solely the notification light blinking.
I don't think that anyone has had this issue since not really anyone is retarded enough to force reboot with Aroma loaded up.. but I decided to type this up just in case.

Phone will not boot past samsung logo.

Hi everyone,
As the title says, my phone simply will not boot past the samsung logo. I insert the battery, a few seconds later there is a vibration. Then the samsung logo appears, and it shuts down. It does not reboot itself; it just suddenly dies. After it the shutdown, all buttons are unresponsive; holding the power button will do nothing.
I have tried plugging in the charger both with and without the battery inside the phone. When I plug in the charger, the red LED that indicates that it is charging turns on. After a few seconds it vibrates, then almost immediately the red LED light flickers off, and everything is just as unresponsive as before. Leaving the charger inside will yield no results or change.
I have tried to turn my phone on with the battery and charger plug into the phone with a few variations. First, charger first, then battery. The battery is inserted within a second or two of plugging in the charger. The red LED light appears, then the light turns off right before the vibration. The screen shows the battery logo that indicates the phone is charging. This image appears for a few seconds, then it becomes unresponsive as before. Second, battery first, then charger. There are two more variations for this. One is battery, then plugging in the charger right after the battery is put in (before the vibration is felt). After the vibration, the battery logo appears for a few seconds before it shuts down and becomes unresponsive again. The second variation is: battery first, then vibration, then right after the charger. Same result as before.
I have also tried to remove both sim card and sd card. No avail.
I have tried to boot it into recovery mode, as well as download mode. Nevertheless, the phone will shut down before getting into any menus.
I have tried to tap the power button multiple times in case the power button and home button were stuck or jammed. However, I doubt this is the problem.
My computer will not recognize my phone, since I cannot boot it past the samsung logo.
I have tried using different batteries, same issue.
I am aware that a factory reset may be an option that I may have to take, but I have some important data on my phone that is not backed up, and I would very much prefer not to lose it all. I would appreciate any insight on how to fix my problem.
Thanks!

Mine was doing this for a bit until I realized my power button was stuck. The button seemed to press fine and all and looked fine physically, but the contact was somehow stuck. Take apart the phone, direct some compressed air into it using the little 'straw' for the nozzle to focus it... Also try pressing the button a bunch of times hard, etc. And see if that helps.

invario said:
Mine was doing this for a bit until I realized my power button was stuck. The button seemed to press fine and all and looked fine physically, but the contact was somehow stuck. Take apart the phone, direct some compressed air into it using the little 'straw' for the nozzle to focus it... Also try pressing the button a bunch of times hard, etc. And see if that helps.
Click to expand...
Click to collapse
Fixed it! Opened it up, jiggled around with the power button stuff. I had no idea what I was doing. I blew, with my mouth, really hard on it. Now it works. laaaaaaaaaaaaaaaaaaaaawwwwwwwwwll
You helped! Thankyou

Now would be a good time to backup that important data. A lot of the time, that's is just a temporary fix and it may happen again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

January 2017 patch bricked my Pixel XL 128GB?!

Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent

Have you held power and volume down for 14 seconds?

vincent.lorentz said:
Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent
Click to expand...
Click to collapse
How long have you had it plugged in? It sounds like the battery is empty.
Try to leave it on the charger for a couple of hours.
If it does not boot by pressing the power button, you can try to boot bootloader by pressing volume down and power at the same time.

The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.

vincent.lorentz said:
The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.
Click to expand...
Click to collapse
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.

Golf c said:
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.

vincent.lorentz said:
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.
Click to expand...
Click to collapse
Your screen may be black, but there is a small chance your still in the bootloader. I have read that other people have recovered from a black screen. I still think its worth a try to connect to a PC and see if the factory image flashes after holding power and volume down and after vibration. Those vibrations have meaning.

Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:

vincent.lorentz said:
Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:
Click to expand...
Click to collapse
I thought there might be a small chance. At least you will get a new phone. Best of luck.

I hate to tell you this but I had the same issue with a 32 GB 5 inch pixel...It was dead...Everything you have said is what happened with mine.
What happened was the slot the phone was trying to boot into had no bootloader or it was a bad flash...Either way, the slot didn't have a bootloader on it when it tried to boot and that black screen is the result...Google sent me a new one and all was well and they will do the same for you.
This is why I don't trust OTA updates...I manually flash everything and I'm sure to flash the bootloader to both slots anytime I update my phone...Good way to keep this from happening again....Best of luck man

You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..

Thank you very much for your kind support, guys.
Your explanations is very interesting. This means that the strategy implemented for the bootloader itself is not very safe. I would be interested in knowing how such a faulty flash can happen and what are the possible reasons behind. Is there a procedure that can increase the chances for a successful flash by doing some things before the OTA update is allowed to be installed?

xocomaox said:
You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..
Click to expand...
Click to collapse
Believe me, I pressed the button for a very long while also (hours) by blocking the button in such a was that the phone boots up until the battery is discharged. So also such an extreme tray was made. The only consequence was the red light flashing.

Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.

droidan said:
Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.
Click to expand...
Click to collapse
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!

5.1 said:
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!
Click to expand...
Click to collapse
Yes. Bad OTA Flash.
Hold 30secs still nothing.

droidan said:
Yes. Bad OTA Flash.
Hold 30secs still nothing.
Click to expand...
Click to collapse
RMA is your only option so

SW3 won't start

Well a few days ago, like 2 weeks ago, I thougt I lost my SW3 (I use it w / o leash because it broke and there's no replacement for the stainless steel one) but actually it was lost on my travel bag xD
After plug in again it started to charge, but when I tried to turn on (after reach 100%), after the sony and SW3 logo, it turns off, like it has a problem at boot. I tried to repair via Xperia Companion and the process was succesful, but the watch just gets stuck on the same SW3 logo.
Now I think is the battery, but I'm really hoping is not, there are any suggestion guys about what could be happening?

Is it stuck at the 4 dots spinning? If So I have the same problem, I have tried a factory reset, updating the rom via push commands etc I have brought a new SWR50 thats working with ADB debugging enabled this time (Didn't do it on the last one) my question hopefully will help the OP as well can I take a complete clone/rom backup from the working watch then push that to the broken watch (Bare in mind no debugging enabled on the broken one) Also to the OP have you held down the power button to get to the fastboot menu and factory reset/recovery settings? if not then you turn off the watch, press and hold the power button until the "insert usb now" shows, you then press the power button quickly twice to access the recovery menus

The Watergod said:
Is it stuck at the 4 dots spinning? If So I have the same problem, I have tried a factory reset, updating the rom via push commands etc I have brought a new SWR50 thats working with ADB debugging enabled this time (Didn't do it on the last one) my question hopefully will help the OP as well can I take a complete clone/rom backup from the working watch then push that to the broken watch (Bare in mind no debugging enabled on the broken one) Also to the OP have you held down the power button to get to the fastboot menu and factory reset/recovery settings? if not then you turn off the watch, press and hold the power button until the "insert usb now" shows, you then press the power button quickly twice to access the recovery menus
Click to expand...
Click to collapse
I forgot about this thread lol
thanks dude!, A couple times it reached the spinning dots, but not always, sometimes it turned off on the SW3 logo before the dots appear, and actually I tried all those things you mentioned, but it didn't work, also I think my watch is (even more) screwed now xD...
Trying to do a second repair on Xperia Companion, the watch got turned off in mid repair, lending obviously on an error, and also losing the ability of do offline charge so once the battery reach 0, is over...
now when I plug in just stays on the SW3 logo, I still can go to connect USB screen and go to the two clicks menu (and stays on), but every time I try a repair, in the middle of the process disconnects and turns off, I don't know exactly why only when is plugged on the repair process it turns off, even pluged in the PC w/o repair stays connected all the time... bad thing is I don't know if is charging or not, so could stop working anytime

Have you tried to push the update through adb recovery mode?

The Watergod said:
Have you tried to push the update through adb recovery mode?
Click to expand...
Click to collapse
every day I'm more convinced the watch is screwed
If I turn on the watch stays on the SW3 logo all the time (it seems offline charge works after all), I even can go to the "insert USB" screen and stays on all the time, but when I try to push something to the watch, always disconnects, turns off and the process obvioulsy gets interrumpted, I'm losing my hopes xD
I'm using the original charging wire, but tried with other working ones

my sister bought me this smart watch , it came on long enough to program a few this after I charge it and then 10 minutes later it shut off and now it won't come back on or power up , what should I do ?

I have a weird problem with my sw3. When I plugin my watch to a charger nothing shows up but the watch gets heated up. But when I connect it to PC it just keeps turning on and off. Tried various methods available on this site but none of them worked.