Related
As i said on the title,suddenly i couldn't recharge my Universal anymore,yes i've tried with a brend new official battery as well but everything was in vain.As soon as i plug my charge to my Universal it appear a Red Led and after 3 min or so the led turn off and so the battery.
How can i fix this problem?!
Is there any chance?!
Is it really dead like that?!
Please HHHHHHHEEEEEEEEELLLLLLLPPPPPPPPPPPPPPPPPPP!!!!!!!!!!!!!!!!
If the battery is really brand new, then I guess the connectors might be damaged or the internal power buses might be broken somewhere. Have you dropped your device recently? Or did anything that might explain broken connectors or internal buses?
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
tetsuokaneda said:
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
Click to expand...
Click to collapse
It can be a software error. Have you tried hard resetting or installing another ROM?
tnyynt said:
It can be a software error. Have you tried hard resetting or installing another ROM?
Click to expand...
Click to collapse
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
tetsuokaneda said:
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
Click to expand...
Click to collapse
Your battery is fine, unfortunately your device broke
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
mzalan said:
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
Click to expand...
Click to collapse
I wanna die!!!I'm completely Fu.. up!!!
What a terrible news!I can't believe it!!!!
If i'll bring my phone to the assistant i'm gonna pay alot of money,at least 200.00 euro!!!!
similar problem
i had the exact same thing happen to my EXEC when i got 2 new batteries for it. One was a standard sized, pretty much the same as the stock one that came with the phone and one was a much larger capacity one that needs an extra cover for the back.
Id been using the device for ages on this huge battery and the charge said 100% constantly. then the device turned itself off and it wouldnt come back on. upon connecting the charger the LED was red, so i thought the battery was dead. I left it on charge over night and when i tried again the next morning it was fine.
this happens everytime with this battery, it just needs a much longer charge than the standard one, and doesnt register properly on the default OS, i havent tried it on my recent upgrade to one of the midget roms.
so try leaving it on charge over night or for a very long time. if all else fails just get a new battery.
That might reset the battery back to life, but I wouldn't exactly count on that. A battery with a broken monitor circuitry is pretty hard to reset.
My last hope,i'm gonna leave charging my phone for a day and then see what happend....I'm desperate
Permanent red light...
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
wtpelzer said:
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
Click to expand...
Click to collapse
Could u post it please?!
Took a while but here it is...
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Same Problem, Led Indicator Always red
Hi,
We have the same situation, my jasjar just died in my hands, im reading a txt messages then al of the sudden it hangs, so what i did is reset it but it didnt power on, i removed the battery then after 10mins i put it back but then no power,then i charged it but it didnt power on too and the led indicator is always red, they say that if the indicator is red it means that there is no battery or the battery is missing but i check it thoroughly,the battery is perfectly place on the back of jasjer, i even tried to enter to bootloader but it cant. If anyone knows how can i revive my jasjar pls pls let us know....Thank you so much.
So sad till now there's no single solution.....
wtpelzer said:
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Click to expand...
Click to collapse
Exactly if my Jasjar is completely dead how can i connect via usb and then use mtty?!
I'm losing my hope to bring it back to live!
have same problem - can do nothing, still waiting
but there is one thing - led flashes once, when i put the charger into the device - but it does nor light, nor flashes - exactly nothing happens
If your device is dead...
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
wtpelzer said:
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
Click to expand...
Click to collapse
The point is that the device is dead and that is why the constant red light. I have a device that is stuck on the splash screen (no solution in sight) and another that fell down and broke. The one that fell down does not power on. If you put a charged battery ang plug in the charger nothing happens, no light comes on, but if you put a discharged battery the red light comes on. I have a third Uni that I accidentally flashed with a BA rom. It is behaving exactly like the broken uni, it does not turn on, does not go into bootloader and the red light comes on when I plug in the charger with a discharged battery in it.
For some things, there's just no cure...
Okay I understand where you're coming from but essentially what you need to do, under normal circumstances, is connect it to your PC, which if the device is working at all the PC will detect it but not connect... In the case of two of your Uni's I don't think this will help - the dropped one and the BA ROM failure. The one with the Red LED, which has stopped working could be a component failure on the board or it could be a Corrupt DOC table. Now to get back to how you'd go about fixing it if it is a corrupt DOC table, when you connect it to the PC and the PC detects it you disable ActiveSync and start MTTY it should give you the option of connecting to the USB port, when it does this if you get a prompt the problem should be fixable because MTTY can "talk" to the device... As for the other's try this method and if it doesn't work sell them for parts or canabalise the one for parts for the other...
Hello ppl,
since 2 days I've got a big problem with my Polas (at all XDA Orbit 2)
Ok first the bad story. My device did take a little shower and had water in it, which seems to be dried out now.
First, you all should think there is nothing to rescue here anymore.
BUT after the first problems (i will tell you some lines below), later on my device got working again. It worked for nearly a whole day.
And then the same problems as before came back again and now I'm stuck on it.
Here is the scenario:
- Without Power Plug: I turn on the device. It boots up as always. When boot is finished and coming to Windows Mobile, the device tells me "low power" and shuts off directly
- With Power Plug: I turn on the device. Showing the o2 Splash Screen. And that's it. Not even the ROM Version Numbers are showing up. When I take out the Plug after a while, XDA just turns off. Oh and the orange LED is lightened.
I can also plug it in while the XDA is off and it shows the orange LED, so you should think it's getting power.
But it doesn't when I try it afterwards without the Plug.
When I boot up without the plug, and plug it in after the Splash Screen, it's the same behaviour as on the scenario "Without Power Plug", it doesn't recognize that the plug is in or is not getting power I don't know.
So why was it working for one day? I don't get it!
You think that maybe only the battery is damaged? But why was it working?
I hope this text is not too confusing and maybe somebody is able to help.
I'm dying without my lovely device.
Oh and yes, i did try a hard reset.
I think the biggest problem for me is, that the device doesn't boot when the plug is in. That is totally weird from my perspective.
Thanks in advance!
gmc
Weird! I am able to flash the ROM. But still the same ;( What the hell?
While flashing the ROM there was no sign of a not working battery.
I'm confused!
Update: Re-Flashed O2 Rom and also tried udK Diamond. Flash is always successful but behaviour doesn't change or get fixed ;(( This can't be true.
Well one question... when the version numbers show up on the Splash Screen what is the "G"-Number? It looks a bit weird, "25.69.30.05H"
Maybe that part of the ROM is down?
gmc said:
- Without Power Plug: I turn on the device. It boots up as always. When boot is finished and coming to Windows Mobile, the device tells me "low power" and shuts off directly
Click to expand...
Click to collapse
I had this problem too, so did some other guys, Check out this thread:
http://forum.xda-developers.com/showthread.php?t=381442
Don't know how/if others managed to solve it but in my case only the replacement of my motherboard (under warranty) solved it.
satfly said:
I had this problem too, so did some other guys, Check out this thread:
http://forum.xda-developers.com/showthread.php?t=381442
Don't know how/if others managed to solve it but in my case only the replacement of my motherboard (under warranty) solved it.
Click to expand...
Click to collapse
Thanks for the link. Will check it out. As there is no more sign of water damage on my device, i hope i can use the warranty too.
I have a Sprint TP2 which I have SIM, Security, and CID Unlocked (using Olipro's wonderful unlocker). I also have Sprint's GSM radio flashed. The phone has worked perfectly with my T-Mobile SIM card for the past 4 months, but suddenly it decided to break! Just last week, suddenly the phone was stuck on the HTC loading screen but luckily performing a hard reset fixed it. However today, the phone wouldn't turn on at all. I tried hard resetting again, but the phone showed no response (the screen was completely dark). I also tried a soft reset, but the phone was completely unresponsive. I can't even get it to display the bootloader screen! No matter what I do, the phone remains on a black screen. When I plug it into the computer, the orange light turns on but no matter what buttons I press (hard reset, soft reset, etc) the phone's screen remains black. I have gotten a brand new battery and put it in the phone, but this does nothing.
I've noticed that the phone emits a faint buzzing sound when the battery is inserted.
Is there anything I can do to fix this?
dude im think you are fcked, try charge the battery first. and see if the light comes greens thats mean that the phone at least have something working. after that try to get it on the boot menu to do a usb rom update, if you have some skills open the phone and clean it inside and de ram memory (next to the mini sd) any way wait for the gurus of the forum to have a better info about what to do and good luck
wmao1 said:
I have a Sprint TP2 which I have SIM, Security, and CID Unlocked (using Olipro's wonderful unlocker). I also have Sprint's GSM radio flashed. The phone has worked perfectly with my T-Mobile SIM card for the past 4 months, but suddenly it decided to break! Just last week, suddenly the phone was stuck on the HTC loading screen but luckily performing a hard reset fixed it. However today, the phone wouldn't turn on at all. I tried hard resetting again, but the phone showed no response (the screen was completely dark). I also tried a soft reset, but the phone was completely unresponsive. I can't even get it to display the bootloader screen! No matter what I do, the phone remains on a black screen. When I plug it into the computer, the orange light turns on but no matter what buttons I press (hard reset, soft reset, etc) the phone's screen remains black. I have gotten a brand new battery and put it in the phone, but this does nothing.
I've noticed that the phone emits a faint buzzing sound when the battery is inserted.
Is there anything I can do to fix this?
Click to expand...
Click to collapse
guess/shot in the dark: if you plug it into the PC it doesn't try to load some new USB drivers by any chance, does it?
As last chance
Try CMonex thing first, then if phone is out of warranty and definetly seems to be dead as last chance i would try to dismount motherboard and remove all the shielding covers to expose electronics. Take care to ground yourself to protect board from electrostatic discharge.
First inspect it with a glass lens to see if there's some kind of phisical damage or if all seems to be okay.
Then thoroughly heat it up with a hairdryer (set at max heat and max speed, very close to the mobo) paying attention not to blow any plastic or flex cables. The goal is to eventually restore fake solderings that may have occurred due to age or shocks. You have to be very patient and careful to heat it very well but not too much: there's no need to see tin melt, this in fact would be dangerous, just till it turns a bit shiny, some experience and understanding of electronics helps.
I tried this method a couple of times with dead phones and sometimes worked.
Hope you can work it out.
wmao1 said:
I have a Sprint TP2 which I have SIM, Security, and CID Unlocked (using Olipro's wonderful unlocker). I also have Sprint's GSM radio flashed. The phone has worked perfectly with my T-Mobile SIM card for the past 4 months, but suddenly it decided to break! Just last week, suddenly the phone was stuck on the HTC loading screen but luckily performing a hard reset fixed it. However today, the phone wouldn't turn on at all. I tried hard resetting again, but the phone showed no response (the screen was completely dark). I also tried a soft reset, but the phone was completely unresponsive. I can't even get it to display the bootloader screen! No matter what I do, the phone remains on a black screen. When I plug it into the computer, the orange light turns on but no matter what buttons I press (hard reset, soft reset, etc) the phone's screen remains black. I have gotten a brand new battery and put it in the phone, but this does nothing.
I've noticed that the phone emits a faint buzzing sound when the battery is inserted.
Is there anything I can do to fix this?
Click to expand...
Click to collapse
Hey wmao, well , the spl( secundary program loader ) has broken .... you must use the riffbox .. With this device Is the only way to save the rhodium..... Good luck
seems your boot is dead
Omnia repair tool can fix it
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
---------- Post added at 11:47 PM ---------- Previous post was at 11:38 PM ----------
Chichoman said:
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
Click to expand...
Click to collapse
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Chichoman said:
<snip>
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Click to expand...
Click to collapse
This won't do anything for the OP's inability to boot. That's why I said that likely his best bet is to see if he can boot into AP Fastboot, so that he may be able to FXZ back to stock...
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Apex_Strider said:
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
fire_fist_ace said:
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
Click to expand...
Click to collapse
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Apex_Strider said:
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Click to expand...
Click to collapse
The battery reset actually worked! I had to charge it for quite a while on the usb charger since it wouldnt charge on the mains charger. Once it was on i made a backup then cleared the battery stats, and now it detects the mains charger.
Cheers for your help guys i still dont get why it wouldnt charge on the mains charger when the battery was low, even though before it would charge before when the battery wasnt...
Hello,
I had an accident and after that my Nexus 5 screen was broken. So I decided to buy an new one from Amazon (~60$) and I tried to replace the screen on my own.
Yesterday I replaced the screen with a YT-Video, then I charged my Nexus 5 an the "Charging-Symbol" showed up.
After that I left the house for 2 hours and when I came back (I left the Nexus at home for charging ofc.) I tried to turn on the phone and nothing happened.
Then I tried to press power and volume down to get into the boot-menu and this also worked and the screen showed everything perfectly (!) and then I tried to start my handy from the boot-menu.
Until then everything has worked well but during the start progress I noticed that the (starting-)animation is really slow and laggy, so I decided to try to reboot my phone by holding power off for around 10 secs.
I tried to start my phone one or two times more and tried to get into the boot-menu, restart bootloader, etc. and then I realized that my phone didn't even want to work anymore. I could(and can) neither get into the bootmenu nor simply start it...
Do you have any ideas?
What suprised me the most is that it stopped working so quickly, so I concluded that I replaced the screen right but anything else went wrong...
Please help me :/
PS:
USB-Debugging is turned off and I cant access my phone with my pc or anythin else
Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.
audit13 said:
Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.
Click to expand...
Click to collapse
Thanks, now I could get into my phone and enable USB-Debugging with much lock D)
My problem is, that my phone runs very unstable and shuts down often so I can't really work with it.
Do you know any solution and the more important question:
How can I save my data? I think, that I can save it anyhow if I enabled USB-Debugging with the bootloader and a pc, can't I?
Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?
audit13 said:
Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?
Click to expand...
Click to collapse
I have now moved on!
My charger cabel was broken but now I got a new one!
I can start my Nexus (with some issues) and it runs but sometims it still shuts down and always when I try to plug in my cabel into the Nexus the screen gets black (but on the side you can see that the screen is light up in some way, idk...)
Is there a reason for the heating and for the shut downs? :/
I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.
audit13 said:
I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.
Click to expand...
Click to collapse
And that means what?
And can I do anything for it? Maybe flash it or something?
Reset, etc..
With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.
audit13 said:
With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.
Click to expand...
Click to collapse
Yeah first sentence makes sence..
I swapped software and hardware, sry
my other screen doesn't work at all, completly destroyed...
The problem is that I can't imagine what should be the failure...
And yeah, I already tried disassembling and re-assembling it...
Still same problem
I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.
audit13 said:
I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.
Click to expand...
Click to collapse
Nahh but the screen works I think..
Everything looks clear etc and the screen wasn't really cheap with 65$-70$ I guess..
I think it's something else because my phone gets really on near the CPU and this can't be because of the screen...
Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.
audit13 said:
Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.
Click to expand...
Click to collapse
Yeah, I also thought about a short-circuit but I don't know how I can test this.
When I try to start my phone it fails like 4-5 times and then it works most of the time. The fail looks the following:
The "Google" logo appears and then suddenly the screen gets black, but not the "out"-Black (so that screen it out), I mean the "on, but black"-Black (hope u can understand.. xD)
During this 4-5 Tries my phone feels like 40°C-50°C (sry im from Germany, idk the conversion to °F value.. )
After this (I got the phone running one time for about 20 minutes) the phone doesn't heat up so much, if it starts right I think that the temparatur problem is over, but there is still the problem (also if the phone is running for 20 minutes) that it suddenly shuts down... :/
Sorry, idk much about canadian dollar, like I said im from germany and I payed around 65€
Google says, that this is around 67 (US-Dollar)
I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.
audit13 said:
I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.
Click to expand...
Click to collapse
Mhh, ok :/