I was using my phone to look through Facebook when all of a sudden I get a notification that my battery is too cold to leave phone on and it was also at 1% battery(I know my phone was above 50% battery before this happened). When I dismissed the notification it jumped back up to 50% battery. Then all of a sudden the screen goes black then shows the crashdump mode. I did some research immediately and attempted to repair it through the EDL mode method, but my phone isn't going into edl mode no matter how many times I try with my homemade edl cable. Any suggestions or ideas to help me out? Thanks to anyone who helps.
iBluesurge said:
I was using my phone to look through Facebook when all of a sudden I get a notification that my battery is too cold to leave phone on and it was also at 1% battery(I know my phone was above 50% battery before this happened). When I dismissed the notification it jumped back up to 50% battery. Then all of a sudden the screen goes black then shows the crashdump mode. I did some research immediately and attempted to repair it through the EDL mode method, but my phone isn't going into edl mode no matter how many times I try with my homemade edl cable. Any suggestions or ideas to help me out? Thanks to anyone who helps.
Click to expand...
Click to collapse
Sorry to say dude, I haven't got any experience in this as I've not had this issue on any of my devices... But, have you checked out this youtube vid on repairing?
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
iBluesurge said:
I was using my phone to look through Facebook when all of a sudden I get a notification that my battery is too cold to leave phone on and it was also at 1% battery(I know my phone was above 50% battery before this happened). When I dismissed the notification it jumped back up to 50% battery. Then all of a sudden the screen goes black then shows the crashdump mode. I did some research immediately and attempted to repair it through the EDL mode method, but my phone isn't going into edl mode no matter how many times I try with my homemade edl cable. Any suggestions or ideas to help me out? Thanks to anyone who helps.
Click to expand...
Click to collapse
Taken from this thread;
'The first step of the unbricking process is to put your phone into EDL mode. If your ROG Phone 2 is showing a black screen and vibrates upon press the power button, it’s probably already in EDL mode and you skip to step #2.
In case your phone isn’t already in EDL mode, you will need to do it manually. First, make sure that your phone is powered off completely. Then hold the Volume Up and Power keys together until your phone enters Fastboot Mode. Once your ROG Phone 2 is in Fastboot Mode, connect it to the PC by plugging the USB cable into the side port (not the bottom port).'
Does that help at all?
EDIT: I take it you've tried, without success, to boot into fastboot mode - that's not an option, right?
---------- Post added at 06:48 PM ---------- Previous post was at 06:30 PM ----------
Another option to boot into edl mode is to use the 'all in one tool' from here. Again, I've never had to use it, but I'm guessing the device needs to be in fastboot mode to A. be recognised by the program, which will then allow it to B. run the 'reboot to edl' option. Might be worth a go tho.
Hell, I'm just trying/throwing some options at you!!! Hopefully something will work for you
---------- Post added at 06:48 PM ---------- Previous post was at 06:48 PM ----------
reg66 said:
Sorry to say dude, I haven't got any experience in this as I've not had this issue on any of my devices... But, have you checked out this youtube vid on repairing?
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
Taken from this thread;
'The first step of the unbricking process is to put your phone into EDL mode. If your ROG Phone 2 is showing a black screen and vibrates upon press the power button, it’s probably already in EDL mode and you skip to step #2.
In case your phone isn’t already in EDL mode, you will need to do it manually. First, make sure that your phone is powered off completely. Then hold the Volume Up and Power keys together until your phone enters Fastboot Mode. Once your ROG Phone 2 is in Fastboot Mode, connect it to the PC by plugging the USB cable into the side port (not the bottom port).'
Does that help at all?
EDIT: I take it you've tried, without success, to boot into fastboot mode - that's not an option, right?
---------- Post added at 06:48 PM ---------- Previous post was at 06:30 PM ----------
Another option to boot into edl mode is to use the 'all in one tool' from here. Again, I've never had to use it, but I'm guessing the device needs to be in fastboot mode to A. be recognised by the program, which will then allow it to B. run the 'reboot to edl' option. Might be worth a go tho.
Hell, I'm just trying/throwing some options at you!!! Hopefully something will work for you
---------- Post added at 06:48 PM ---------- Previous post was at 06:48 PM ----------
Click to expand...
Click to collapse
Unfortunately it seems like my phone might just be dead in general. None of the methods provided worked for me. I'm gonna attempt to order a replacement battery for it and attempt to change out the battery myself. Maybe that will work. I'll be sure to update this thread after I attempt this.
iBluesurge said:
Unfortunately it seems like my phone might just be dead in general. None of the methods provided worked for me. I'm gonna attempt to order a replacement battery for it and attempt to change out the battery myself. Maybe that will work. I'll be sure to update this thread after I attempt this.
Click to expand...
Click to collapse
Oh man, that's quite extreme... Would it not be easier/better to try and send it back to Asus for repair under warranty?
One more thing... Is there any indication that the phone is either on or off? You could try to let the battery run out completely, then charge it up again and see if there's any life with either fastboot mode or edl...
reg66 said:
Oh man, that's quite extreme... Would it not be easier/better to try and send it back to Asus for repair under warranty?
One more thing... Is there any indication that the phone is either on or off? You could try to let the battery run out completely, then charge it up again and see if there's any life with either fastboot mode or edl...
Click to expand...
Click to collapse
I voided the warranty the moment I unlocked the bootloader as far as I know. I've given the phone several days to discharge already and left on charger to no results. I'm not sure how much asus may charge me to repair the phone.
iBluesurge said:
I voided the warranty the moment I unlocked the bootloader as far as I know. I've given the phone several days to discharge already and left on charger to no results. I'm not sure how much asus may charge me to repair the phone.
Click to expand...
Click to collapse
Technically yeah, bootloader unlock voids warranty. But I'm wondering if they may not check and just accept the rma. Could be worth a go before you disassemble the phone trying to put a new battery in
reg66 said:
Technically yeah, bootloader unlock voids warranty. But I'm wondering if they may not check and just accept the rma. Could be worth a go before you disassemble the phone trying to put a new battery in
Click to expand...
Click to collapse
I'll attempt to contact them. Thanks for the suggestion.
iBluesurge said:
I'll attempt to contact them. Thanks for the suggestion.
Click to expand...
Click to collapse
Just don't mention the bootloader!
reg66 said:
Just don't mention the bootloader!
Click to expand...
Click to collapse
Welp asus has replied back to me with a quotation and asking for $650 to repair the device. They sent a pic of the damage which appears to be water damage around the board where the battery connects to it. I was wondering if there is any possibility I can repair this myself for cheaper instead? I'll attach the picture they sent me with an edit I made to it to highlight the damage area. FYI I used jerryrig's teardown video of the ROG Phone 2 as reference to identify the damage as ASUS didn't actually highlight the area for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edited with an embedded picture since the file I uploaded doesn't seem to show.
https://ibb.co/M695WrN
iBluesurge said:
https://ibb.co/M695WrN
Click to expand...
Click to collapse
Sorry dude, no idea on that
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
le
this is where im at.
first the history. I had serindipity, tried adding the unusefull kernel and got stuff in a att splash then off cycle. I made a jig, got it to the downloader screen. plugged into odin and all was going well but odin stalled and i waited a good 15 minutes. nothing, i pulled the battery and no matter what i do i get this screen. been looking all over for answers before i asked, but nothing anyone else did works. currently my pc does not see anything plugged up which scares me. ive tried 3 different usb cables. any ideas?
and yes i read ALL the threads that populated when i typed the title.
Can you still get into download mode?
You did try closing odin, then reopen it. Pull battery out of phone. Put back in. Dont turn it back on. hold volume up and down button at same time then plug the usb into phone.
Sent from my GT-I9000 using XDA App
Build or buy a USB download mode JIG. Just search the term and either give it a shot or buy one to get back into download mode.
what is an unusefull kernel? do you mean unhelpful? the forum member? that was a 2.1 kernel. other than that i dont know what an "unusefull" kernel can be.
even if you get the phone to computer screenthe phone can take a connection from odin occasionally.
pull the battery
open odin
hold the volume up and volume down buttons
put the battery back in
keep holding the volume buttons untill either the phone+computer or a yellow android with a shovel pops up on the phone screen
watch odin and see if a yellow box lights up. if it does then press start on odin.
the phone + computer screen sometimes shows when the phone is in download mode if something is really messed up but seeing it doesnt mean you are also in download mode.
i dont want anyone telling me the difference between the phone+computer and download because i have succesfully flashed with the phone+computer screen as well as with a completely black screen, sometimes you get lucky!
It was the unhelpful kernal. Sorry about that. I have done everything you guys have said already. I guess I will just keep trying for now. Hopefully it it will work atleast once. I have the jig an that's how I got it to dl mode the first time.
http://forum.xda-developers.com/showthread.php?t=775911
i have read all 23 of these pages, and im still stuck. but i want it back. nice to have a rooted phone for all the fun stuff!
lucky my main phone is a moto atrix. this phone was donated for experiments from a customer.
just keep trying.. If you have the jig and can get into download mode.. Keep trying. Try a different usb port, restart your computer.. close up odin and re-open it..
why did you make a jig before flashing? dont you know about the button combos?
dani forgot to mention have the phone plugged into the computer for his instructions.
few ways to try download mode:
from powered off, hold both volume buttons, plug usb into phone FROM PC
or
remove battery, plug usb into phone and pc, hold both buttons, put in battery
or
from powered off, put in jig.
or
just MAYBE>>> from soft brick screen, try adb command "adb reboot download" (adb setup guide in my sig) worth a shot.
what version of odin are you using? 1.0? use 1.82. it freezes less. and some people have been able to flash at the soft brick screen
ODIN3 v.1.82.zip
just for one small second i got the pc to know something was plugged in. but no drivers were found and then adb coudnt get to it. still stuck at phone!computer. i havent seen any other screen other than that yet.
its late so i will get at this again tomorrow. thank you for the help so far.
if you wouldnt mind sending it to someone adam outler may be able to flash it being it is not a hard brick. he has been able to get download mode with his uart/arduino setup. the method is far from complete or perfected but it is fairly safe for the phone.
heres what i get from adb. i should also say that i still dont hear my pc making a noise at anytime when i plug it in. normally anytime i plug something into a usb i hear it make a sound. is this bad or normal at this point?
i have tried all the key combos and jig. still stuck with the same screen. even when i use the jig i still get phone--!-- computer.
Coreym said:
just keep trying.. If you have the jig and can get into download mode.. Keep trying. Try a different usb port, restart your computer.. close up odin and re-open it..
Click to expand...
Click to collapse
Definitely fixable with the jig! Best investment I ever made ..... after fidgeting with a home-made one from Radioshack.
... i have tried all the key combos and jig. still stuck with the same screen. even when i use the jig i still get phone--!-- computer.
Click to expand...
Click to collapse
Homemade jig or did you buy one? If it's homemade, you have to keep trying - it took me a half hour to touch the right contacts the first time ....
Jig should work - it shorts out the usb connection and forces download mode ....
go to ebay, search for "micro usb jig".
i already have a jig (homemade), thats how i got it to download mode instead of the looping. the last time i used the jig it still put it into phone--!--computer. i just searched ebay and found it, im gonna order one.
lucky my daily phone is a atrix, (soon to be a s2, LOVE the samoled) this is just a experiment phone so i can learn (donated by a loving customers pool). i now know a lot more than a did 2 days ago.
well, i guess i have got the jig working well now. i have got it back into dl mode. i should be good from here. thank you thank you guys!!!
all done!!!
re rooted and ready to screw something else up!!! how else will i learn?
it's great that you got your phone going... after a week of attempts with my home made jig, i finally ordered one fromm ebay. I'll attemtp to repair then and post results.
UPDATED!
I had forgotten about posting here, and my problem has been resolved. So here it is... I tried everything that I could find within this forum, almost. I built my own jig with inferior radio shack components that would not activate download mode, though it would turn the phone on. I got wise, spent 8 dollars at ebay and purchased a JIG there. Instant download mode after 3 days (shipping). Reflashed with one click, updated w/ kies, made kernal changes and am now rockin my captivate. Thanks to those who assisted.
hi
i think my galaxy s (i9000m) is fully bricked i used to access to download/recovery mode with 3 button combo but since i flashed jp1 i get phone--!--computer screen and there is no way to access either download or recovery mode i don't have any warranty is there any way to fix this ??
thank you
Check it out in Youtube~It's called the Jig USB method~
There are also topics concerning making Jig of your own in this forum =]
thanks for your reply
its seems complicated isn't there a way to buy a cable ? and is there a (free) way to get download mode back again ?
thanks
don't know if that helps but when i try the 3 button combo phone restarts to the same screen again and again and again ....
I'm a complete noob soo i don't know if this is true (and i'm not responsible if anything goes wrong) but here it goes.
I don't know if this is your case but that happened to me yesterday,
i connected the USB cable while i had that screen on my phone and was able to flash with ODIN.
It was like even with the phone--!--computer screen, it was still in download mode.
Try pressing the keys to put in download mode and then see if ODIN adds it
That happened to me also last week while trying to root a gingerbread version, started to panic.
I took the battery out for 5mins, refitted it and then was able to enter download mode ok, then managed to flash back to froyo, and jobs a good un now.
Ebay sell jig and amazon i bought one had exactly same problem fixed it in minutes
Sent from my GT-I9000 using XDA App
thank you for your replies,
is it possible to get a repair from samsung even if i bought the phone from kijiji ?
biscuit26 said:
hi
i think my galaxy s (i9000m) is fully bricked i used to access to download/recovery mode with 3 button combo but since i flashed jp1 i get phone--!--computer screen and there is no way to access either download or recovery mode i don't have any warranty is there any way to fix this ??
thank you
Click to expand...
Click to collapse
Hang on, one more thing you can try, worked for me just last weekend....
"Leave Odin Open. Then Plug the USB. While the USB is plugged in and Odin running press and hold volume down + Home + Power. Once the black screen comes release the Power Button. It will get to the download mode"
Worked like a charm, got it from this thread
http://forum.xda-developers.com/show...1#post13630631
If it works for you make sure you hit the thanks button of the guy that originally posted it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DMD9 said:
Hang on, one more thing you can try, worked for me just last weekend....
"Leave Odin Open. Then Plug the USB. While the USB is plugged in and Odin running press and hold volume down + Home + Power. Once the black screen comes release the Power Button. It will get to the download mode"
Worked like a charm, got it from this thread
http://forum.xda-developers.com/show...1#post13630631
If it works for you make sure you hit the thanks button of the guy that originally posted it
Click to expand...
Click to collapse
thanks for you help, but it didnt work i release the power button when the screen goes black but the phone---!----computer screen comes back
any chance of getting a repair from samsung ?
Just called samsung they told me i have to send the phone to bell first. the guy told me there is no way i can send it directly to samsung. since im not a bell customer and i unlocked my phone bell won't take it..
anyone knows a good place in montreal where i can get my phone fixed ?
thanks
U can try doing this:
Pull out battery and sim card
Hold both vol. Up and down buttons
Without pressing power button plug USB in phone while Odin is running on comp.
Even if it gives error at this point, ur still in download mode.
Try flashing a different .md5 file.for phone.
Sent from my GT-I9000 using XDA App
drtusharks said:
U can try doing this:
Pull out battery and sim card
Hold both vol. Up and down buttons
Without pressing power button plug USB in phone while Odin is running on comp.
Even if it gives error at this point, ur still in download mode.
Try flashing a different .md5 file.for phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
think i tried all possible combinations it just don't want to go on download mode
My GT-I9000 did this 2 weeks ago. Nothing worked and I didn't try the Jig but sent it back to my phone store (optus australia) who sent it back to samsung and they fixed it no problem.
I do have insurance on it though for the 2yrs.
It was the- Anim Mod *Root* by JRummy that bricked it?
no its was the jp1 firmware that bricked it
i think its dead can't get the phone replaced or repaired
How did you go with your phone mate? I had mine sent back under warranty and was returned in under two weeks.
If it want under warranty I would have made or bought a jig and had a crack at that, otherwise maybe look in your local newspaper or call a computer repair place and see if they know anyone in your area who could fix it. Word of mouth mainly!
biscuit26 said:
Just called samsung they told me i have to send the phone to bell first. the guy told me there is no way i can send it directly to samsung. since im not a bell customer and i unlocked my phone bell won't take it..
anyone knows a good place in montreal where i can get my phone fixed ?
thanks
Click to expand...
Click to collapse
let me tell you something ok i had exactly the same problem as you and my warranty ran out and i know what the problem is
Your motherboard has froze on you i recommend you get a new motherboard needs replacing or you can get your dogdy phone repaiir shop to do it for you
I got mine bricked one time so I just went to my carrier dealer. They fixed it. ;3
Sent from my GT-I9000 using xda app-developers app
Your phone is not bricked,it has a corrupted boot loader etc. Samsung can easily fix it but the cheaper way is to build or buy the usb jig, lets face it gonna cost you about 10 quid to buy the jig. I happened to me sometime ago, Samsung fixed for free, then i made a jig just in case.
Hi, have a bit of an issue. My sister dropped her GXS in a pool today. she got it out and wiped it and it seemed to work fine (i told her that she should have taken the batt out immediately... she didn't) She went on then the phone died and got stuck in an endless reboot cycle. i opened it up and cleaned it and dried it, looks clean, from what i can tell. the screen shows the little refresh circle in the center, then shows the battery image for a few seconds then repeats the process (if i connect it to a wall charger, the battery image lasts about a second longer but it still restarts). it constantly restarts. and here is the problem, i can get it to download mode, but even in download mode it restarts after 3-4 seconds so i cant flash anything in such a short period. recovery does not work (even if it did i bet it would still restart after 3-4s). it starts doing this as soon as the battery is inserted.
It was running an old nightly of CM9 (about 2-3 months old)
Any help will be greatly appreciated
UPDATE:
Left it out on the sun for a few hours to dry even more off, now shows the galaxy I9000 splash screen and the semaphore kernel logo but it still restarts after 3-4s
UPDATE 2:
Dissasembled it and put it in a jar of rice, not expecting much. Took a look at the motherboard to prepare for the unbrickable mod. Those pads are TINY, i mean really tiny
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FULL size image here:
http://dl.dropbox.com/u/11992935/2012-09-08 18.32.42.jpg
That HUGE thing on the chip above is the microsd card
So my new questions are, in the original unbrickable thread i dont quite understand the instructions. IS it like in the picture near the enlarged piece numbered 1. that you must resolder the yellow marked resistor to the blue marked pads, or like in number 2. you must remove the resistor and put a wire (drawn grey) like in the picture or do you do first number 1. and then attach the wire to the upper end of the moved resistor and then to the other pad?
Congrats to your sister, looks like she killed her SGS.
Looks like the battery's not the problem, if it reboots when it's unplugged (an almost empty battery -almost empty = already shut down, but reboots for a few seconds- shows at
least unlock screen for me when I turn it on).
If recovery and download mode don't last enough to flash, it's over IMHO. And even if your warranty is still valid, water damage is not covered..
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
quantity rostsrt
total.destroyer said:
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
Click to expand...
Click to collapse
Try to put the phone in a jar of rice for 24H.
After that try to flash a rom using odin.
total.destroyer said:
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
Click to expand...
Click to collapse
I doubt this has anything to do with Unbrickable mode solutions, anyway links to test mode tare on My Android Solutions, link below.
You problem would be most likely due to moisture shorting power and usb ports/contacts
xsenman said:
I doubt this has anything to do with Unbrickable mode solutions, anyway links to test mode tare on My Android Solutions, link below.
You problem would be most likely due to moisture shorting power and usb ports/contacts
Click to expand...
Click to collapse
I went over your list before posting, nothing helped in my situation, and there is no test mode on your list, or maybe i missed it. I cleaned the usb port and it looks clean, the battery contacts are also clean, no obvious damage shows, and the power on button can not be shorted because it is a potted foil membrane and the leading contacts are clean, and the button works otherwise i could not get temporarily in download mode. gonny try and mess about with adb if i can get the phone to be seen.
total.destroyer said:
and there is no test mode on your list, or maybe i missed it.
Click to expand...
Click to collapse
Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
you can only revive phone using unbrickable mode when phone is totally dead with only this words SEC S5PC110 TEST B/D, that why I said, i am doubtfull you need to use it.
xsenman said:
Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
you can only revive phone using unbrickable mode when phone is totally dead with only this words SEC S5PC110 TEST B/D, that why I said, i am doubtfull you need to use it.
Click to expand...
Click to collapse
I think i have no other choice, i have tried everything, my only options now are to get it repaired without warranty (probably will cost more than a new gxs off ebay), use it as a paperweight or try to do the unbrickable mod and see if that works.
Is there a possibility that a software error is constantly rebooting the phone or is there a hardware problem? I mean, could a corrupted bootloader constantly reboot the phone, no matter what mode the phone is in, like in download mode is the bootloader still runing in the background? or the kernel?
Good luck if you decide to try. I'm considered extremely good at soldering by many, I have all the proper tools including a top notch soldering station, and moving that 0201 resistor took me like an hour. One of the most difficult things I've ever had to do, and I didn't think it would work in the end. Having two irons and a microscope would have helped a lot but it's not a mod for the faint of heart. That said it saved my phone from some nasty software business.
I really doubt it would solve this problem, since it's water damage it's probably long gone. If you have no possible other option though, there's no harm in trying this.
FjarrKontroll said:
Good luck if you decide to try. I'm considered extremely good at soldering by many, I have all the proper tools including a top notch soldering station, and moving that 0201 resistor took me like an hour. One of the most difficult things I've ever had to do, and I didn't think it would work in the end. Having two irons and a microscope would have helped a lot but it's not a mod for the faint of heart. That said it saved my phone from some nasty software business.
I really doubt it would solve this problem, since it's water damage it's probably long gone. If you have no possible other option though, there's no harm in trying this.
Click to expand...
Click to collapse
I have a friend that does electronics and solders daily so he should be able to do it, but the big question is, is this actual hardware damage from water or a short caused data corruption and the problem is software, because the thing works, the display works, animation works, the buttons work, it only decides to repeat the process every 3-4s (it varies, sometimes it last about 6-7s, especially if i plug it in to charge, or it dies in a second or two). Could water damage it so precisely to do that, or was there a short that caused some data corruption of the rom/bootloader/kernel/whatever that makes it reboot after the boot process encounters that section of bad data, or the memory chip got corrupt. Is there a way to find out, can a log be dumped out while it is booting? my pc does not recognize anything is connected while it does its refresh battery thing, or maybe you need special drivers.
total.destroyer said:
I think i have no other choice, i have tried everything, my only options now are to get it repaired without warranty (probably will cost more than a new gxs off ebay), use it as a paperweight or try to do the unbrickable mod and see if that works.
Is there a possibility that a software error is constantly rebooting the phone or is there a hardware problem? I mean, could a corrupted bootloader constantly reboot the phone, no matter what mode the phone is in, like in download mode is the bootloader still runing in the background? or the kernel?
Click to expand...
Click to collapse
If your phone had no problems and this problem only developed after the water damage it has nothing to do with software and all to do with hardware . I think the Phone reboots due to minute shorts in the hardware ..moisture underneath the chips could be one...you can try heating a few of larger chips...best would be to keep the phone wrapped in tissue and in a pot of rice for a week or so
solved
i see one galaxy s like this before.
the phone boots if after u see a green battery on screeen
1.but u have to connect a strong charger (1 to 2 Amps) or a USB (1 Amp) laptop computer .
2.after connect the phone, u have to wait aprox. 30 sec, if nothing happened u ned to reconect (pull out battery , then insert it back in the same time with usb or charger plug )
3.if the grenn battery appears on screen wait to charge to 50% then press power button but not detach cable or charger
4.after complete boot , u are free to use your phone (ALL THINGS WORKS)
Hi there,
I've been using CM all the time, but now I decided to switch back to stock rom.
I installed everything properly but after boot up, I got the message "use genuine battery" and the phone shuts down.
Of course I am using my original battery that was in the package.
I tried without success:
- pressing PowerOn-button for 20 seconds when battery unplugged
- cleaning battery contacts with nail polisher
By googling I found this advise that shoud fix the problem:
Many LG Models have a common error of saying Use Genuine Battery then powering off. This is a very common and fixable issue. please understand that this method will most on most LG phones but does exclude the 8100 and older models, and the exact location of the items you'll be looking for in programming will vary model to model.
If you encounter this error you can attempt to correct the phone if you have another battery for the phone that will power the handset up.
Install the battery that is working
Type in: ##LGSERVICEMENU send (##5473784296368) on the dialpad.
enter the security code: 000000
locate: SW/HW Tests or HW test or SW/HW Versions
once you locate and select the correct field you need to find "bypass booting"
in this menu you need to locate fake battery mode select it and choose on.
Your LG will now work with any battery that fits into the phone.
Click to expand...
Click to collapse
I tried this and borrowed a battery from a friend. With this battery everthing worked fine. But unfortunately the service-menu as described by typing ##5473784296368 didnt work on my 4xHD. Instead I tried the hidden menu 3845#*880#. But there I wasn't able to find anything like "fake battery" or so.
Does anybody know where this menu point could be?
My phone is too old so I wont get a new battery from LG Service.
thanks in advance :good:
Try this number: 3845#*880# maby is that option in this menu
Sent from my LG-P880 using xda app-developers app
noppoer2 said:
Try this number: 3845#*880# maby is that option in this menu
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
hello read what he said:
I tried this and borrowed a battery from a friend. With this battery everthing worked fine. But unfortunately the service-menu as described by typing ##5473784296368 didnt work on my 4xHD. Instead I tried the hidden menu 3845#*880#. But there I wasn't able to find anything like "fake battery" or so.
Ok @eFCiKay maybe you should enter in recovery and wipe all partitions, this would be fix that problem.
If i was right please hit the thanks button
Have a nice day!
Allex42HD said:
hello read what he said:
I tried this and borrowed a battery from a friend. With this battery everthing worked fine. But unfortunately the service-menu as described by typing ##5473784296368 didnt work on my 4xHD. Instead I tried the hidden menu 3845#*880#. But there I wasn't able to find anything like "fake battery" or so.
Ok @eFCiKay maybe you should enter in recovery and wipe all partitions, this would be fix that problem.
If i was right please hit the thanks button
Have a nice day!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you SERIOUSLY just recommend that the OP simply wipe all partitions in order to fix a battery problem? Really? I guess he'd be so pi$$ed off at no longer having a phone which would boot that he would no longer notice the battery problem?
If this is the level of your advice to help people out then I suggest you stop bashing on your keyboard and find something else to do with your time instead.
And to top it all off you beg for thanks at the bottom of your post
thanks for all answers
of course I would have been aware of, that in case I'd wipe all partitions, I need to reflash recovery and rom.
But could this really fix the problem?
I even tried another baseband (v10h and v20a)
Just re-read your first post properly.
You have been using CM with no issues, but when you went back to Stock this started happening? What Stock have you gone back to? Given that, I'd be tempted to do a full KDZ reflash and see if that makes any difference as it's possible something has gone wrong when you've reflashed.
Although, if I read right, you used a friend's battery with no problems? Just buy an OEM battery from eBay and see if that fixes it.
SimonTS said:
I'd be tempted to do a full KDZ reflash
Click to expand...
Click to collapse
how would you do it? (to be sure everything else than stock has been wiped...)
this way?
http://forum.xda-developers.com/showthread.php?t=2179126
eFCiKay said:
how would you do it? (to be sure everything else than stock has been wiped...)
this way?
http://forum.xda-developers.com/showthread.php?t=2179126
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=35971349
With pictures and everything, this guide works perfectly if you follow the instructions.
tanks for all your help, but unfortunately flashing via this method didnt work either. same message at startup...
I gonna buy a new battery
eFCiKay said:
tanks for all your help, but unfortunately flashing via this method didnt work either. same message at startup...
I gonna buy a new battery
Click to expand...
Click to collapse
pfffff..... that it's a problem, you should charge your battery with a phone battery charger device and when it's fully charged or 80% put the battery on the phone plug the usb on the phone press down volume button and plug the usb to your computer (you will need to have phone driver installed)
and flash the fw with kdz.
just give one more chance to your battery!
Fix Maybe?
Hello,
Sorry to bring up an old thread, but just for information in case anyone else comes over this issue and end up on this thread.
I found with my p880 that one of the battery prongs on the phone was bent in so that it didn't attach properly to the battery connection.
I got a pin and hooked it underneath, then pull the pin slightly out which brought it back in line with the others.
I then got cleaning alcohol, I used isopropyl, to clean all the contacts.
After doing this I found the error message went away and the phone works as it should.
Hope this helps someone else with the problem.
Regards,
Monkey
So I got a package today from FedEx. Opened up the first box, plug the phone in and nothing. Holding down the power button for any length of time does nothing. Let it sit on the charger for a while, nothing. Stuff happens right? Well this is where it gets a little interesting.
- OnePlus explains I have to ship the phone back, they will look at it and verify the problem. Then a replacement will be shipped. Roughly 12 days until I get a new one generally.
- I offer to just pay for new one in the mean time so one can be cross shipped, which apparently is not possible.
- At this point I kindly tell the this rep I would like to wait a moment and decide what to do, as I may not want a replacement, I may just return everything.
- I think on it, and then open up a chat with OP. I ask if the replacement will get priority shipping like my original order, and am told no. Replacements are shipped regular shipping, 5-7 days.
- So now I ask if I will be getting a shipping label. I'm told no, to just use what ever method I would like. This is where I point out I should not be out money for their mistake / defective device.
I almost understand some of this in certain situations. However I'm calling them literally an hour after FedEx deliver the device, with a phone that is clearly DOA. It would be quicker for me to just return this phone, and buy a new one.
The two reps that I dealt with did what they could, but it seems like I really had to push in the end to sort of get around the this OnePlus policy. Perhaps OnePlus just doesn't have a high failure rate so they don't know what to do when this does happen, but this is not what to do.
OhioYJ said:
So I got a package today from FedEx. Opened up the first box, plug the phone in and nothing. Holding down the power button for any length of time does nothing. Let it sit on the charger for a while, nothing. Stuff happens right? Well this is where it gets a little interesting.
- OnePlus explains I have to ship the phone back, they will look at it and verify the problem. Then a replacement will be shipped. Roughly 12 days until I get a new one generally.
- I offer to just pay for new one in the mean time so one can be cross shipped, which apparently is not possible.
- At this point I kindly tell the this rep I would like to wait a moment and decide what to do, as I may not want a replacement, I may just return everything.
- I think on it, and then open up a chat with OP. I ask if the replacement will get priority shipping like my original order, and am told no. Replacements are shipped regular shipping, 5-7 days.
- So now I ask if I will be getting a shipping label. I'm told no, to just use what ever method I would like. This is where I point out I should not be out money for their mistake / defective device.
I almost understand some of this in certain situations. However I'm calling them literally an hour after FedEx deliver the device, with a phone that is clearly DOA. It would be quicker for me to just return this phone, and buy a new one.
The two reps that I dealt with did what they could, but it seems like I really had to push in the end to sort of get around the this OnePlus policy. Perhaps OnePlus just doesn't have a high failure rate so they don't know what to do when this does happen, but this is not what to do.
Click to expand...
Click to collapse
Are you sure it was DOA? Holding power button for 5 seconds or so doesn't produce a buzz and boot the phone?
amg83 said:
Are you sure it was DOA? Holding power button for 5 seconds or so doesn't produce a buzz and boot the phone?
Click to expand...
Click to collapse
You are correct, holding the power button for 5-10 seconds, even 30 seconds, does nothing. When you plug the phone in it does nothing. You know how normally if the phone is off it would bring up the battery and show how much of a charge it has and such, this particular phone does none of that.
I would also try pressing/hold power and volume up for a extremely long amount of time. Random key presses and holds! Bumped mine out of a weird dead spot restart one time.
mang0 said:
I would also try pressing/hold power and volume up for a extremely long amount of time. Random key presses and holds! Bumped mine out of a weird dead spot restart one time.
Click to expand...
Click to collapse
I tried volume down, I didn't try up. The problem is unique to this phone. Others work fine. I would like to try and avoid all of this headache though.
*Edit* Ok I tried Up, tried Down again, Tried all three together, No dice. *Edit*
So the only other interesting thing I noticed, is I also hooked it back up to a dash charger, and it still doesn't respond at all as before, but it is actually drawing power, but only 0.53 amps. Obviously well below what a dash charger is capable of putting out.
This is unfortunate. I really like OnePlus philosophy on their products, so really would expect better service.
Totally agree OP company should have a better exchange policy for defective device, the customer definitely shouldn't have to pay for an exchange. You offering to purchase a second device is beyond generous and shouldn't even be an option for a company to ask that of you. Hopefully they will see this thread and make it right for you!
sounds like its in DFU mode or EDL mode. (factory flashng modes)
considering its drawing power, id bet it is in a flash mode that presents visually as dead.
do you have adb installed on your PC? if not, google minimal adb fastboot, dl and install. then run the command 'fastboot reboot'
its a crap shoot, but its worth a try. i wish someone from OP or a dev could chime in to confirm or deny my theory...
maybe @Funk Wizard or
@mauronofrio
know the answer or who would.
also, if it is in fact, DOA, they should absolutely overnight a replacement with a return label. if they dont, hopefully you used a CC you can do a charge back on, bc you did not get what you paid for. perhaps you just got misinformed chat people. there is not much reason for any company to expect you to accept a failed device.
Their testing is thorough, but im sure its possible one made it through after being flashed without being booted to Android and powered down.
kind of like the remnant pics Linus talks about in this vid. I highly doubt a fully DOA phone made it out of the factory, but something like leaving it in the flashing mode is far more plausible imho.
kitcostantino said:
sounds like its in DFU mode or EDL mode. (factory flashng modes)
considering its drawing power, id bet it is in a flash mode that presents visually as dead.
do you have adb installed on your PC? if not, google minimal adb fastboot, dl and install. then run the command 'fastboot reboot'
its a crap shoot, but its worth a try. i wish someone from OP or a dev could chime in to confirm or deny my theory...
maybe @Funk Wizard or
@mauronofrio
know the answer or who would.
Click to expand...
Click to collapse
I do have both installed. You had me hopefully, but no dice on that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wonder if the Qualcomm tool would see it? I'll boot up a Windows machine and try that.
OhioYJ said:
I do have both installed. You had me hopefully, but no dice on that.
I wonder if the Qualcomm tool would see it? I'll boot up a Windows machine and try that.
Click to expand...
Click to collapse
fastboot edl devices
fastboot reboot-bootloader
honestly, you may need to install the proper driver for this phone for your os.
with it not listing
adb devices: (serial number or empty space)
if properly installed, the output should either be your serial number in devices, or fastboot devices with a blank field behind it if none are detected..
adb devices only works when you are booted into android
fastboot devices may or may not list it depending on the mode the phone is in. the mode being unknown to me is why i tagged smarter peeps than myself. lol.
edl mode on qualcomm devices always has a button combo in addition to being accessible from adb i.e.-
adb reboot edl
this isnt case-specific (doesnt apply to your phone), but shows my theory. when he presses and holds power and vol down to enter you can see what i believe you have.
dont do the unbrick steps. i just wanted to show what "msm mode" as he calls it looks like so you know youre not crazy.
kitcostantino said:
fastboot edl devices
fastboot reboot-bootloader
honestly, you may need to install the proper driver for this phone for your os.
with it not listing
adb devices: (serial number or empty space)
if properly installed, the output should either be your serial number in devices, or fastboot devices with a blank field behind it if none are detected..
adb devices only works when you are booted into androidm
Click to expand...
Click to collapse
It's there to some degree, so you are on to something. The MSMDownloadtool sees it on COM3, if I unplug the USB cable it disappears. I've got to admit though, I'm more familar with Linux than Windows at this point. so I'll have to fumble around with this for a moment. Let me see if I can get ADB and Fastboot working on Windows.
OhioYJ said:
It's there to some degree, so you are on to something. The MSMDownloadtool sees it on COM3, if I unplug the USB cable it disappears. I've got to admit though, I'm more familar with Linux than Windows at this point. so I'll have to fumble around with this for a moment. Let me see if I can get ADB and Fastboot working on Windows.
Click to expand...
Click to collapse
yeah, all of the major companies use windows based flashers in a factory environment afaik. makes it a pita if youre on linux or mac,
but that is also why i keep a dual boot setup. i love mint vs win, but for miflash (zte phones) rsd lite, radiocomm (motorola phones) and every other oem tool ive used, you end up needing windows a lot of times.
kitcostantino said:
dont do the unbrick steps.
Click to expand...
Click to collapse
Haha, yeah, I was just using that tool to see if anything would recognize the phone.
BTW I was actually showing that LTT video to a friend while they were over here when I was showing this dead phone to them.
Contact me on telegram and i will help you: https://t.me/mauronofrio
OhioYJ said:
So I got a package today from FedEx. Opened up the first box, plug the phone in and nothing. Holding down the power button for any length of time does nothing. Let it sit on the charger for a while, nothing. Stuff happens right? Well this is where it gets a little interesting.
- OnePlus explains I have to ship the phone back, they will look at it and verify the problem. Then a replacement will be shipped. Roughly 12 days until I get a new one generally.
- I offer to just pay for new one in the mean time so one can be cross shipped, which apparently is not possible.
- At this point I kindly tell the this rep I would like to wait a moment and decide what to do, as I may not want a replacement, I may just return everything.
- I think on it, and then open up a chat with OP. I ask if the replacement will get priority shipping like my original order, and am told no. Replacements are shipped regular shipping, 5-7 days.
- So now I ask if I will be getting a shipping label. I'm told no, to just use what ever method I would like. This is where I point out I should not be out money for their mistake / defective device.
I almost understand some of this in certain situations. However I'm calling them literally an hour after FedEx deliver the device, with a phone that is clearly DOA. It would be quicker for me to just return this phone, and buy a new one.
The two reps that I dealt with did what they could, but it seems like I really had to push in the end to sort of get around the this OnePlus policy. Perhaps OnePlus just doesn't have a high failure rate so they don't know what to do when this does happen, but this is not what to do.
Click to expand...
Click to collapse
Went thru the exact situation, same rep procedures. Finally held vol up vol down and power at the same time.
The phone came on. If it wasn't for this phone being so good I would have returned it and never spend another nickel with them. It is absolutely ridiculous having to wait 2 wks for a phone just delivered.
sirj00 said:
Went thru the exact situation, same rep procedures. Finally held vol up vol down and power at the same time.
The phone came on. If it wasn't for this phone being so good I would have returned it and never spend another nickel with them. It is absolutely ridiculous having to wait 2 wks for a phone just delivered.
Click to expand...
Click to collapse
I swear I just did this earlier... However, the phone is now on. I sat there and held all three buttons until the phone finally came on. It booted into fast boot, once in fast boot I was home free.
OhioYJ said:
I swear I just did this earlier... However, the phone is now on. I sat there and held all three buttons until the phone finally came on. It booted into fast boot, once in fast boot I was home free.
Click to expand...
Click to collapse
Yaaay.
Yeah... it's happened to me twice now when restarting, strangely. The last time that it happened it was power/vol up that brought it out of that state.... but yeah it's weird.
In a way, having seen how stringent their hardware testing is, i can almost see why they would believe complete failure (DOA) is impossible and respond accordingly (2 week exchange horse manure, etc). Also, I imagine that its even possible for a user to accidentally press the key combo to enter a flashing/factory mode completely by accident on initial boot. Instructing the customer to reboot in the way you would exiting said modes would make far more sense than instructing someone to ship it back at their own expense and wait two weeks bc you believe it is operator error is just poor CS/Support. I am so glad you posted here instead of doing all of that. maybe that is why thats the standard response. lol. enjoy your 6t now.
Did OP confirm if his computer is seeing his phone as QUSB aka Qualcomm Download mode?
BIGWORM said:
Did OP confirm if his computer is seeing his phone as QUSB aka Qualcomm Download mode?
Click to expand...
Click to collapse
The only troubleshooting OP did was the initial phone call, which in fairness, was the only time we discussed it. Every other interaction I had with them we were discussing the "what in the world" is going on with these policies and trying to get this phone replaced in a timely manner. Luckly I didn't have to end up going through any of that.
The rest of the troubleshooting I did with suggestions from members here.
*Edit* Haha, was that OP OnePlus or Original Poster ? I just realized that. The unbrick tool was seeing my phone to some degree as it was assigning it a COM port l, but I did not try and flash anything