Related
Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Has anyone experienced this or am I the only one?
M5devil said:
Has anyone experienced this or am I the only one?
Click to expand...
Click to collapse
Sorry I have never heard of this or witnessed it while flashing anything to my device. Obviously the battery screen signifies that the phone is off but is in charging mode and hitting the power button will boot the device up. (I'm sure you already know of this). Never heard of it being stuck at that screen after flashing. Hopefully you can get this solved soon. Good luck
M5devil said:
Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Click to expand...
Click to collapse
Slow down for a second. Your phone is definitely not bricked. Ive been over the edge, and been able to bring my phone back to life.
To clarify, you flashed vibrant6.zip through clockwork mod, and then the phone got stuck on the samsung S? How long did you let it sit there?
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
I flashed the stock ROM via Odin and then wanted to install Vibrant6.zip. For that I entered into a recovery mode via Clockwork and as someone in the other thread advised, I formatted system and also data, don't recall exactly. Then it looped to a standard recovery mode and I just rebooted the phone. This is where it got stuck... Vibrant in the center and Samsung at the bottom of the screen. To test it I left it like that from night till this morning. In the morning I woke up it was on the same boot screen.
Before that at night, after seeing it hand at the boot, I held both volume keys and power, waited for it to reboot, and immediately it showed a circular progress bar, but not moving just highlighted the 12 o'clock bar and second later I see the battery image all in gray and nothing else. It just sits on that grey static image without actually charging it (no green section or flashing dots)
Boot logo only appears if I am trying to reset without the USB cable. On the boot loop I plug in the cable and I hear the USB connecting it, I see the 2 Removable disks, but both inaccessible and adb commands don't recognize the device.
Very weird, as in turned off mode it's not charging at all.. just shows this grey battery image with a circle progress froze on 12 o'clock bar.
That's pretty much it.... I was never able to enter into recovery nor download via the buttons. It would just always reboot into this grey battery screen....
Completely helpless.... I did order a new battery from TMO, maybe the battery is fried and that's why it's not charging and just sits on this stupid static grey battery screen.
ArbitrageMan said:
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
Click to expand...
Click to collapse
Holding both volume keys and releasing power once screen goes blank, only show Vibrant logo again... I have tried this a million times
With USB cable it shows grey battery screen, without the cable just a Vibrant boot loop...
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
zephiK said:
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
Click to expand...
Click to collapse
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
M5devil said:
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
Click to expand...
Click to collapse
Are you sure that you're doing the right things to get to download? I've been in this situation and I wasn't able to get into recovery but I was able to get back into download mode.
I believe if you return it back and they find out it was rooted, they will charge you for it. If not, it'll appear on your bill.
I'm sure that you're doing the wrong things to get into download mode. If something is appearing on your screen it is a soft-brick and you're not bricked.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen (powers on its own when plugged in)
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
Click to expand...
Click to collapse
A tip to get into download mode is to put the phone HORIZONTALLY (sideways) and it will make it a lot easier.
I am pretty much positive about it. I know a lot of people can easily enter into recovery or download modes, but I know many can't and I am one of them. It would just load the grey battery image instantly as I let go of the power button.
1. Take out battery, put it back in. (to turn the phone fully off) DONE
2. Don't turn it the phone on! DONE
3. Plug the phone into your PC, do not hit the power button! DONE
4. See if the phone shows anything on the screen (powers on its own when plugged in) FIRST THING THAT APPEARS IS A CIRCULAR PROGRESS BAR THAT CHANGES TO A GREY BATTERY IMAGE WITH A BAR IN THE MIDDLE OF IT. STATIC IMAGE, NOTHING ELSE.
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons. DONE
6. Hold the power button as well as the volume buttons until the screen goes black. DONE
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons! DONE
THE STUPID GREY COLOR BATTERY IMAGE APPEARS AS BEFORE....
I'm thinking maybe battery is fried and that's why the grey color screen appears and not the usual screen where you see the battery charging...
After reading this thread it's clear that my handset is one of the new ones that have recovery/download modes disabled via the volume+power buttons.
So that pretty much covers it... I hope TMO will not ***** about the files that are on the internal sd that I am unable to access and remove... unless anyone else has any fresh ideals how to gain access to the disk
I think I might have a similar problem.
I accidentally deleted the touchwiz framework so I can't do anything ON the phone. It boots up, and gets me to the lock screen. As soon as I unlock, I am greeted with dozens of unending force closes.
I can get into both download and recovery mode, however, I have not been able to get ADB to recognize the device. I am attempting to push the stock ROM to the internal memory to flash over everything.
I'm not sure what to do to get ADB to work but it's driving me nuts!
Stuck at vibrant? I have a fix
Check out android Dev Section... I figured out how to access download mode or stock recovery mode when you are stuck at the vibrant screen!!!! BACK IN BUSINESS VIBRANT OWNERS!!!
i got the same problem and nothing seems to work
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
eduardo_reflex said:
i got the same problem and nothing seems to work
Click to expand...
Click to collapse
... do i even have to say it?
droyd666 said:
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Click to expand...
Click to collapse
this problem is most likely solved. After 2 years!
mylostlonelysoul said:
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
Click to expand...
Click to collapse
Try asking another question. But I suggest using a USB jig. They usually work. Then odin
Sent from Mount Olympus via Hermes
Did you ever get it fixed man? I literally did the very same to mine a while back and It works like butter as we speak. It is fixable with a mini-usb jig or dongle. You can make your own with about $3 worth of parts from radio shack but I recommend buying one, it will be easier. I for the record made mine simply twisting together the resistors and though it was tough to touch the right pins it did eventually work and get me back into download mode.
Hopefully you already got it fixed though. If not I can help you out.
Well, after spending almost 11 hours trying to boot into recovery or download, I know for sure that there is something going on with my phone re: hardware locked. The date on my box is 7-16. It is an early Vibrant. But no matter what I do, I cannot get into download or recovery which means my ****ing phone is literally worthless.
I have tried all possible thousands of combination's of buttons, batteries, and cords while booting and nothing happens.
The Vibrant logo shows, then it shows the pink, annoying as hell T-mobile logo, than goes to the Galaxy S logo which loads for a little bit and then just leads me to a black screen. Eventually the 4 buttons on the front of the phone turn on and then nothing else happens. It will just sit like this forever.
I know all I need to do is get a working ROM loaded but it is literally impossible to do so.
Can anyone offer any suggestions? Or are anyone else having the same problem?
I guess the only way I can get a working phone is to get in touch with T-mobile and do a Warranty exchange. That's a damn shame too, because I will be without a working phone for a week.
What about using adb?
adb reboot recovery -or- adb reboot download ?
I had a hw locked vibrant, never tried the adb reboot download, recovery did work.. I added another line on my account last night for somone, who got a vibrant, theirs wasn't hw locked, so I traded 'em ;P
Agree with the above poster I have been stuck on the vibrant screen or dark screen and adb still worked to save me
when i try to use adb, it just tells me that it cant find the device. i'm not able to boot into android OS at all.... screen just hangs. so my computer is never getting a chance to see my phone hence why i cant use adb to reboot it into recovery or download.
I believe your device has to go into recovery mode then check with and devices and if you see a device I THINK it is and reboot download, I am 90% certain
Sent from my SGH-T959 using Tapatalk
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
98classic said:
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
Click to expand...
Click to collapse
i do believe i have the correct drivers installed. i was able to use adb to run lagfixes before i was having this problem. when i boot my phone, i get a sound from my computer saying that it recognizes a usb device. the two drives in the vibrant show up in My Computer but i cannot access them as windows says they are not accessable at the moment.
at what point will adb be able to recognize my phone when booting? no matter what i do when i try adb shell i get error: device not found
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Same problem here. I probably just have to sell it fast on ebay or something. Hopefully some kind of fix starts by the end of the week. First phone in my smartphone life to brick from a simple Voodoo lag fix. Please XDA gods find a solution.
crazycaveman said:
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Click to expand...
Click to collapse
nope, no go. adb will not recognize my device no matter what. and the device isnt loading the OS so i cannot turn debugging on. i guess this is a real "brick" then.
This sounds like a rant rather than a question. Just sayin'.
DKYang said:
This sounds like a rant rather than a question. Just sayin'.
Click to expand...
Click to collapse
fixed that. my bad.
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
renocivik said:
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
Click to expand...
Click to collapse
thanks for the suggestion. i found your thread and went through the steps in the OP... still no luck. no matter what i do, i cannot get passed the black screen the loads after the galaxy s logo. i also cannot get into download mode or recovery no matter what combination of button presses i use.
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
core99 said:
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
Click to expand...
Click to collapse
this isnt working either. :-(
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
atoz350 said:
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
Click to expand...
Click to collapse
this is exactly the method i want to try. but unfortunately i cannot get the phone into recovery or download mode. i have tried at least 100 times now with many different combination's of plugging the usb cord in and pressing the volume and power buttons.
two ideas: one, is it possible that i wiped recovery and download mode from my phone on accident? the reason why i ask is that i was super tired and flashing roms and kernels to my phone. i flashed back to my original stock rom and then i flashed the kernel. for some reason, i selected wipe date/cache in Rom Manager before flashing the kernel. i have no idea why i did this. seriously. totally noob move. so im assuming i have a kernel flashed but now there is no ROM installed for the phone to boot into.
two, if above is not the issue, than im going to assume that the phone is not recognizing any button presses while its off, so when i turn it on it just recognizes that the power was pressed and ignores the volume presses, thus not booting the phone into recovery or download.
edit: i should mention again that at no time does adb recognize my device. so i cannot use adb to reboot the phone into the mode i need.
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
byt3b0mb said:
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
Click to expand...
Click to collapse
I understand what you mean. I appreciate your criticism of my original post. Let me say that I wrote it while frustrated. But I know that isn't an excuse.
The device is fantastic. I know that I did this to it myself. It's unfortunate.
Anyways, I received a replacement phone. I will be more careful this time.
Let me prefice this by saying that my son doesn't know how to flash files, know what super user is, or know how to do much on his phone at all other than watch youtube and text.
He is running either official CM7-RC2 or RC3 for his P500, installing Link2SD and linking a few games is the only tweak I did.
He says it just started boot looping in the morning after charging all night.
My son was complaining his P500 was not starting, I figured it was a very low battery which ended up in a boot loop pattern. The next morning he said he charged it all night and it still wasn't working. Now I knew something was not right.
I pulled the battery, tried to offline charge it, gets stuck at lg logo. Tried to boot with no battery, just the usb plugged in, same bootloop.
Tried to boot into CWM by holding vol up/home and this screen somes up!
Now every time I turn on the phone I'm greeted with this Blue Error Handler message.
Code:
[Blue Error Handler V1.2] Arm 9 Crash!!
[Press Volume up key] To get Ramdump!!
[Press Volume down key] Reboot&savelog!!
:Excep
MODEM Excep :PROXY_00
...
...
<CallStack>
<Additional Info about this crash>
Build ID: P500-M76XX-V20i-DEC-06-2011-XX
Time of crash (m-d-y h:m:s): 06-15-2012
Uptime (h:m:s): 0:00:04
Error in file hsu_mdm_apis.c, line 557
REX_TCB ptr: 0x01ea5640
tcb.task_name: PROXY_00
I can get into emergency mode but lsusb shows nothing, adb sees nothing, kdz says phone not found. I've tried shaking the phone like a fool over and over.
The computer and usb cable work fine on my two other P500s.
I'm kind of out of ideas.
This should help
I bricked mine yesterday...KDZ did not work for me either...
the second post in the link below solved mine...
http://forum.xda-developers.com/showthread.php?t=1710559
You also might need the p500 drivers installed to use the lg thunder 1.5
You can download it from here
https://dl.dropbox.com/u/46581752/LGUnitedMobileDriver_S4981MAN36AP22_ML_WHQL_Ver_3.6.exe
LGMDP doesn't connect to the phone, it waits at the select port screen. The drivers are installed since LGMDP can see my other P500s.
*edit* I was just thinking, I haven't tried connecting my other phones in emergency mode. Perhaps it is the drivers.
You boot to CMW with home+VOLDOWN+power... you mentioned volup.
Sent from my LG-P500 using Tapatalk 2
Try this
mrplowdan said:
LGMDP doesn't connect to the phone, it waits at the select port screen. The drivers are installed since LGMDP can see my other P500s.
*edit* I was just thinking, I haven't tried connecting my other phones in emergency mode. Perhaps it is the drivers.
Click to expand...
Click to collapse
It did not detect mine either at first place... follow this.
1) close the LGMPD
2) plug the usb into a different port you are already doing
3) put the phone into emergency
4) connect
5) then start LGMPD
hope this helps
you could try flashing a new kernal/rom through the computer?
try to put phone in recovery with volume down button
ankitwashere said:
...the second post in the link below solved mine...
http://forum.xda-developers.com/showthread.php?t=1710559
Click to expand...
Click to collapse
basically ends up with my trying to use lgmpd and seeing no phone at the select port screen
ankitwashere said:
You also might need the p500 drivers installed to use the lg thunder 1.5
You can download it from here
https://dl.dropbox.com/u/46581752/LGUnitedMobileDriver_S4981MAN36AP22_ML_WHQL_Ver_3.6.exe
Click to expand...
Click to collapse
thanks, same version I already had installed though
ankitwashere said:
It did not detect mine either at first place... follow this.
1) close the LGMPD
2) plug the usb into a different port you are already doing
3) put the phone into emergency
4) connect
5) then start LGMPD
hope this helps
Click to expand...
Click to collapse
thanks, tried all 8 ports still no detection, changed my bios settings to use usb 1.0 only, didn't help, tried usb 2.0 highspeed didn't help, tried usb 2.0 full speed, didn't help
-DarkKnight- said:
you could try flashing a new kernal/rom through the computer?
try to put phone in recovery with volume down button
Click to expand...
Click to collapse
I wish I could get recovery going, but it always just hangs and the first lg logo if I hold any buttons down during boot. The only way I can get emerg mode going is to wait for the Blue Error Handler message to come up then hold vol down and back.
Once my phone got bricked and yes nothing detected my phone in emergency mode...so I just kept my phone turned off and plugged in and started doing what the thread said...then it automatically detected my phone and my phone's problem was solved
Please do it at ur own risk...I wont hold any responsibilty.
Sent from my LG-P500 using XDA
mrplowdan said:
Let me prefice this by saying that my son doesn't know how to flash files, know what super user is, or know how to do much on his phone at all other than watch youtube and text.
He is running either official CM7-RC2 or RC3 for his P500, installing Link2SD and linking a few games is the only tweak I did.
He says it just started boot looping in the morning after charging all night.
My son was complaining his P500 was not starting, I figured it was a very low battery which ended up in a boot loop pattern. The next morning he said he charged it all night and it still wasn't working. Now I knew something was not right.
I pulled the battery, tried to offline charge it, gets stuck at lg logo. Tried to boot with no battery, just the usb plugged in, same bootloop.
Tried to boot into CWM by holding vol up/home and this screen somes up!
Now every time I turn on the phone I'm greeted with this Blue Error Handler message.
Code:
[Blue Error Handler V1.2] Arm 9 Crash!!
[Press Volume up key] To get Ramdump!!
[Press Volume down key] Reboot&savelog!!
:Excep
MODEM Excep :PROXY_00
...
...
<CallStack>
<Additional Info about this crash>
Build ID: P500-M76XX-V20i-DEC-06-2011-XX
Time of crash (m-d-y h:m:s): 06-15-2012
Uptime (h:m:s): 0:00:04
Error in file hsu_mdm_apis.c, line 557
REX_TCB ptr: 0x01ea5640
tcb.task_name: PROXY_00
I can get into emergency mode but lsusb shows nothing, adb sees nothing, kdz says phone not found. I've tried shaking the phone like a fool over and over.
The computer and usb cable work fine on my two other P500s.
I'm kind of out of ideas.
Click to expand...
Click to collapse
Mind if I ask how long have ur son been using this phone? To me, it looks like it is due to age. Well that is how I see it.
a cheap trick
This is what i tried on some other phone with similar situation...
use KDZ updater....to update v20g
put to emergency...
start the update (even if the phone is detected or not)
it may or may not install the rom correctly ......but after that LGMDP will start detecting your phone..
allenwalker1998 said:
Mind if I ask how long have ur son been using this phone? To me, it looks like it is due to age. Well that is how I see it.
Click to expand...
Click to collapse
It was a Christmas gift but its been used quite a bit.
ankitwashere said:
This is what i tried on some other phone with similar situation...
use KDZ updater....to update v20g
put to emergency...
start the update (even if the phone is detected or not)
it may or may not install the rom correctly ......but after that LGMDP will start detecting your phone..
Click to expand...
Click to collapse
ya I've tried updating using KDZ updater many times it always hangs at the point where it says phone not found.
I use Ubuntu on my machine and its a pain to have to reboot to windows to try to flash it, are there any linux alternatives to LGMPD or KDZ? Maybe I'll try the official LG updater full program thing next time I reboot.
I just bought an atrix 4g for myself so I'm busy playing with my new toy
I just got the error it looks like you overclock too high of a frequency u got that instead of the kernel panic. I think it is because that our processor can't handle the oc and crashed.
But somehow I got out of it and no bootloop. Will investigate.
allenwalker1998 said:
I just got the error it looks like you overclock too high of a frequency u got that instead of the kernel panic. I think it is because that our processor can't handle the oc and crashed.
Click to expand...
Click to collapse
He's never overclocked it on purpose, I just asked him, he doesn't know what overclock means.
Thanks for the input though
mrplowdan said:
He's never overclocked it on purpose, I just asked him, he doesn't know what overclock means.
Thanks for the input though
Click to expand...
Click to collapse
Have u tried using kdz and update ur son's phone back to stock?
allenwalker1998 said:
Have u tried using kdz and update ur son's phone back to stock?
Click to expand...
Click to collapse
Should try. I think it is a corrupt rom or something.
Went to researched and found out that the error happens wipe the /system isn't wiped properly. Try kdz first then install a custom recovery and wipe /system using amora recovery instead of cwm.
not to sound rude but have you read this thread? I've tried kdz multiple times in many different ways. Do you have any kdz tips I haven't tried?
mrplowdan said:
not to sound rude but have you read this thread? I've tried kdz multiple times in many different ways. Do you have any kdz tips I haven't tried?
Click to expand...
Click to collapse
Yeah I have. Uninstall usb drivers. Reinstall them turn off LG USB modem. Connect it to ur com. Shake the phone like crazy and hope it connects once connected just update.
allenwalker1998 said:
Yeah I have. Uninstall usb drivers. Reinstall them turn off LG USB modem. Connect it to ur com. Shake the phone like crazy and hope it connects once connected just update.
Click to expand...
Click to collapse
Uninstalled-reinstalled, rebooted, lg virtual modem doesn't appear on the list until you get the phone to connect at least once, I shook shook shook, while in emerg mode, it never seems to connect, I tried lgmdp and kdz, both never connect. Tried with and without the battery in, never connected.
Hello,
I was so enthousiastic about the MM update that I didnt realize I was flashing the Z4 Table MM ftf to the Z5 compact. ****!! Now my phone seems to be dead. No vibrating, no lights no matter what I do.
I try to flash the correct ROM with Flashtool, but it doesn't recognize the device.
In device manager, the phone is not recognized "Unknown USB device, attempt for device descript failed" (if I translate correctly).
Is there something I can do?
Open flashtool. Select the firmware you want. And press on flash. Once flashtool prompts you, ONLY THEN you connect your phone while holding the power down button
Sadman Khan said:
Open flashtool. Select the firmware you want. And press on flash. Once flashtool prompts you, ONLY THEN you connect your phone while holding the power down button
Click to expand...
Click to collapse
Unfortunately it didn't work. I read in some other thread that battery has to die for the memory to reset, then recharge and flash. So I am waiting for this to happen... hope it's working.
Enrico2828 said:
Unfortunately it didn't work. I read in some other thread that battery has to die for the memory to reset, then recharge and flash. So I am waiting for this to happen... hope it's working.
Click to expand...
Click to collapse
If you're stuck on the Sony logo screen hold volume up and power to hard boot, there is no need to let the battery drain.
Download a fresh mm .ftf, load up flash tool and prepare files(exclude nothing), wait for flash mode prompt then plug in device while holding volume down(do not let go until it stays solid). It takes a long time to flash,you'll probably think it's stuck at times.
civicsr2cool said:
If you're stuck on the Sony logo screen hold volume up and power to hard boot, there is no need to let the battery drain.
Download a fresh mm .ftf, load up flash tool and prepare files(exclude nothing), wait for flash mode prompt then plug in device while holding volume down(do not let go until it stays solid). It takes a long time to flash,you'll probably think it's stuck at times.
Click to expand...
Click to collapse
I got back from work and no miracle happened. Phone is still dead. The screen is black. When i put it to charger or pc, no led is blinking. When I do hard reset (with little buttin next to sim tray) nothing happens. When I attempt to reset with power button + volume up nothing happens, no vibration.
I tried repair with Sony Companion, it does not recognize the phone. Windows first recognized the device as some generic, then on second and following attempts reports a malfunctionion USB device.
Have I destroyed my phone??? I never unlocked the bootloader or even unrooted. How could I destroy vital parts of the system? Isn't there some low level something there that still should enable me to flash another rom? How can I get to this part?
I feel a bit devastated now. I actually never realized flashing had this danger (if bootloader locked ...)
Enrico2828 said:
I got back from work and no miracle happened. Phone is still dead. The screen is black. When i put it to charger or pc, no led is blinking. When I do hard reset (with little buttin next to sim tray) nothing happens. When I attempt to reset with power button + volume up nothing happens, no vibration.
I tried repair with Sony Companion, it does not recognize the phone. Windows first recognized the device as some generic, then on second and following attempts reports a malfunctionion USB device.
Have I destroyed my phone??? I never unlocked the bootloader or even unrooted. How could I destroy vital parts of the system? Isn't there some low level something there that still should enable me to flash another rom? How can I get to this part?
I feel a bit devastated now. I actually never realized flashing had this danger (if bootloader locked ...)
Click to expand...
Click to collapse
try reinstalling your drivers also when you connect your phone to the charger do u get a charging light ?
did you try a different USB cable, i saw it hapen that crappy USB cables gives a bad flash, or doesn't recognize the device
If you really don't find any other solution, bring it to the Sony repair center/the shop you bought from and tell that it was updating to Marshmallow but after the restart, the phone was dead.
I highly doubt your phone will work again in the current state you've left it in.
I've flashed a boot.img from another device to see what happens, the phone just vibrates and turns back off. Can easily recover by flashing the correct boot.img, so it looks like yours is damaged at a lower level.
I assume the bootloader tried to update itself with files from the wrong device instead of checking.
Good Luck.
Sent from my E6653 using Tapatalk
Thanks everyone for the support. I didn't have a chance to report back earlier due to work. I want to describe everything as good as possible, so maybe other people having the same problem later on can refer to this thread.
When I put in the charger, no LED is turning on.
I tried a different computer (win7), installed flashtool and then ALL drivers included with flashtool drivers. No help.
I left the charger on for many hours, the previous night I also tried what is referred to as the "rubber trick". Nothing.
I looked at several threads, http://forum.xda-developers.com/showthread.php?t=1849170, http://forum.xda-developers.com/xperia-m2/help/hard-bricked-power-to-flash-mode-t3004020, http://forum.xda-developers.com/xperia-z2/help/help-bricked-z2-t3052671, http://forum.xda-developers.com/xperia-m2/help/dead-m2-recognized-somc-flash-device-t3304758. As far as I can see none of the people who encountered similar symptons have reported back solving it other then sending it to Sony repair.
I contacted Sony support, they asked me to charge it, attempt Sony Companion repair. Of course it doesn't help. So I contact them again tomorrow (indeed telling after MM upgrade it didn't start) and then send it to them.
I just don't understand how this could have been happened, seeing what celderic reports. Is it even related to me flashing the wrong ftf, or could it also happen even likely while flashing the good ftf?
Is flashing ftf's even save? If not, maybe we should warn people more about it. (I always assumed as long as you don't root / unlock bootloader nothing can really go wrong, cause the important parts I am never allowed to touch).
Ironic, I was so impatient for FINALLY getting a working, performing phone, boy, did I prolong my wait. It is really ridiculous Sony could sell us this piece of crap that is slower than my old Blackberry Z10 and make us bear it for so long, and then suddenly they are able to turn it into a superblazer. Should have been like this right from the beginning.
How long did you press the reset button? I had a similar situation with my Z1C a few days ago. Misclicked without realizing it and flashed a wrong rom. Out of frustration and because I was talking to somebody I pressed a paperclip against the reset button for about a minute. At that point the phone did vibrate, went blank again and I could put it in flash mode.
Hm .. I pressed it long, but probably not a minute long. Can't try again though, phone is on its way to repair center.
By the way, someone asked, I used original Sony cable.
Got my phone back working today. Very good support from Sony!! Only took 5 working days. (I'm in the Netherlands)
Facts:
- Pocophone F1 is in an endless boot loop. Every 8 seconds it reboots itself.
- Recovery mode and Fastboot are reachable, but this doesn't stop the boot loop.
- I have never used a custom rom
- The bootloader is unlocked (ADB confirms this), USB debugging is enabled, but OEM unlocking is NOT enabled.
History:
The problems started after a regular update (I had never put a custom rom on the phone). The phone became unstable, constantly restarting itself. Sometimes restarting quickly, sometimes after a few minutes (reaching Android). I tried to unlock the bootloader, by tapping 7 times on MIUI Version, enabling USB Debugging [I did not enable OEM unlocking unfortunately...] and run the flashtool. The flashtool reported that the phone was unlocked. And after restarting, the phone reports to be unlocked. ADB confirms this too. But after unlocking the phone, it never ever again reached to Android, restarting itself always after exactly 8-9 seconds. I can get into recovery mode and fastboot, but it will still restart. In Fastboot, my pc recognizes the phone as an Android Phone. Is there a magical way to get out of this loop?
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
lockhrt999 said:
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
Click to expand...
Click to collapse
The problem persist when I completely remove the connector of the power/ volume button... When I push the power button I feel that the button moves and I hear a click-sound. Something else must be the cause of the problem. But still thanks for your help.
i have the same issue, did you find any solution to the problem?
Have the same problem is there any solution?
I don't have the phone so I cannot say this will solve the issue, however this sounds like a problem with the battery, something similar happened to my Redmi Go. The voltage should be low enough that the system boots, but just as it starts up the voltage drops to the point it reboots.
Solved it!!
I have Played with the power button and press it several times and it help.
I think the button was stuck or something close to that.
Thanks for you help guys!
ozer86 said:
Facts:
- Pocophone F1 is in an endless boot loop. Every 8 seconds it reboots itself.
- Recovery mode and Fastboot are reachable, but this doesn't stop the boot loop.
- I have never used a custom rom
- The bootloader is unlocked (ADB confirms this), USB debugging is enabled, but OEM unlocking is NOT enabled.
History:
The problems started after a regular update (I had never put a custom rom on the phone). The phone became unstable, constantly restarting itself. Sometimes restarting quickly, sometimes after a few minutes (reaching Android). I tried to unlock the bootloader, by tapping 7 times on MIUI Version, enabling USB Debugging [I did not enable OEM unlocking unfortunately...] and run the flashtool. The flashtool reported that the phone was unlocked. And after restarting, the phone reports to be unlocked. ADB confirms this too. But after unlocking the phone, it never ever again reached to Android, restarting itself always after exactly 8-9 seconds. I can get into recovery mode and fastboot, but it will still restart. In Fastboot, my pc recognizes the phone as an Android Phone. Is there a magical way to get out of this loop?
Click to expand...
Click to collapse
Chance 1: Power button bug
Chance 2: EMMC failed and your phone is long gone.
lockhrt999 said:
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
Click to expand...
Click to collapse
Thank you! This was the issue. There is no way to tell that the power button is stuck. But it is and was causing my Poco F1 to bootloop even in fastboot or recovery mode. A symptom to look out for: your phone randomly locking once in a while due to this.
mateuxi said:
I don't have the phone so I cannot say this will solve the issue, however this sounds like a problem with the battery, something similar happened to my Redmi Go. The voltage should be low enough that the system boots, but just as it starts up the voltage drops to the point it reboots.
Click to expand...
Click to collapse
i booted in TWRP for 8-9 minutes with full brightness & no timeout but then mine didn't go into bootloop... recovery's getting powered but OS isnt?
Same thing happened to my F1, I press and flicked my power button hard and it worked. My problem happened maybe because the hard cover pushing the button too tight because it sometimes lock it self. Thank you for the tips! Just made account to reply to this thread.