Related
Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.
Have you tried Quick Boot in the market?
SugarMouth said:
Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.
Click to expand...
Click to collapse
The thing with these Vibrants is that some of them have that problem where the phone doesn't register that your pushing the volume buttons at boot up...only the power button, which is why it just turns on and nothing else. This is a known issue that was found out by another canadian phone company(Bell)
I just bought a Vibrant and I could not boot into recovery from day one...after a week I took it back 'today' and got a replacement and now it works. I guess me and you were the unlucky ones.
If you really want it to work I would take it back somehow because this isn't fixable, its a hardware issue on boot.
-By the way, you can still boot to recovery from adb or rom manager, anything like that, just not physically. The down side of this is that if your in a boot loop and your computer doesn't recognize your phone your screwed. It also doesn't recognize Download Mode either to restore.
Hope it works out for you.
Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."
s15274n said:
Have you tried Quick Boot in the market?
Click to expand...
Click to collapse
I need root for that and I can't boot into recovery to get root.
SugarMouth said:
Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."
Click to expand...
Click to collapse
Actually thats exactly what I did...I told them I like to have control over my phone and that I use the recovery to "clean up" my phone every month or so and I like to use the recovery to do it. I also told them in the past i've used the recovery to install OTA updates that simply did not want to install over the air, so I would download it myself and install manually. The T-mo rep didn't seem to care.
So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300
s15274n said:
So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300
Click to expand...
Click to collapse
Exactly...do that. Like I said in my first post, you can still do everything thru Quickboot, Rom Manager, etc and ADB. You just won't be able to get to recovery that way if your phone won't boot or is stuck in a boot loop..that would suck.
As I mentioned in your other thead on this subject, I have the same problem with a brand-new Vibrant, and I don't want to root it yet. Only way I was able to get into clockwork recovery was via 'adb reboot recovery' method. Once I'd done that, I was able to install and run wirelessap tethering without rooting, infrastructure mode and all. Still not rooted, but I never did get my intended 'factory-fresh' nandroid backup, I gave up and popped in my SIM and installed a few things before I got adb talking to the phone. (running adb on ubuntu box, hadda kill and restart server as root to fix permissions issue)
j
I got my replacement vibrant, after bricking the first one, and I can confirm that I am not able to boot into recovery by holding the volume buttons. I hope samsung hasn't changed something...
But thankfully I was able to finally get into recovery using ADB...
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
First of all, there's no such thing as semi brick, there's brick or not. Try installing your Rom again..
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
dude, he cant back up if he cant access the homescreen. neither can he use rom manager..
cant use the hardware buttons to get into dl or recovery either... read op guys...
2010ngojo said:
[Q] Need help with semi/soft brick!
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
Click to expand...
Click to collapse
Do this bro... just tested it myself, works fine...
get adb installed on your computer, should already have it if your rooting but if not get it, youll find it in the stickied thread for informative links in the development section.
get a cmd prompt open on your computer and type in
>adb devices
let it start up deamon and it will tell you device not found, its ok.
now type and have ready...
>adb reboot recovery (do NOT press enter yet)
start your phone like normal. before its even finished with the boot up tmobile animation and the galaxy s (but after the plain vibrant text/picture) logo press enter. if it says error: device not found then wait all the way till galaxy s only you did it too early...
screen will go black and reboot into standard recovery... hope to goodness you had a working clockwork recovery installed and nandroid ready for this next part...
go down using your volume keys and select reinstall packages using the power key
now in clockwork recovery go down to nandroid
now go to restore
go to your earliest back up and restore it.
there you go.
I would start fresh get odin set up and reinstall the original rom at this point as something may still be corrupted, reroot, install latest clockworkmod, latest vibrant 9 rom (im using and see no bugs and runs better then the vibrant 6 rom i had) and DONT install the lag fix until the newest "TRUE" lag fix comes out with the new file system and kernel that JAC is working on and has almost ready.
good luck and pm me if any of these steps need further explanation.
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
iwillkillyou said:
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hes just stated man that he cant even get into recovery, my guess is hes locked out using the volume up/down keys like many new phones are (which btw is a known defect, spend 10min on the phone with tmobile doing thier trouble shooting to show them it doesnt work and they send you a replacement..) sooooo I gave him a way to get into recovery without the buttons and not having to wait till he gets to a black screen where possibly its frozen and he cant use adb commands.
I was just making mention to you also that he cant even back stuff up NOW (hopefully he already archived all his apps and data) and hes better off starting fresh since hes getting problems using his current rom/lagfix....
Thanks for the quick reply p()()pypants, but i will have to try your method later. It's late and I have class (college) tomorrow, but i will post my results soon. Thank you again.
Edit 1:
Btw, is there a way to back up my current rom? Like the way rom manager back up roms? I know my current rom works before so that's why I want to back it up.
Edit 2:
Actually i did not use adb to root my phone, just used the one click method. So can you please give me more detailed instructions on how to install/use adb?
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
2010ngojo said:
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
Click to expand...
Click to collapse
Do you have the right drivers installed? You can check here: http://forum.xda-developers.com/showthread.php?t=728929
Another very stupid question, just to cover all bases - your phone is plugged into the computer, correct? When you install the new drivers, try plugging the phone into a different USB port on the computer than you've been using, so it will hopefully pick up the new drivers without much extra effort.
If that doesn't help, just keep trying the command while the phone boots up. Maybe you'll get lucky and it will work. Sorry I don't have any real solution for you :\
I'm fairly sure I have the right drivers, otherwise I wouldn't be able to root in the first place. Yes, the phone is plugged in also. I'll try a different USB port and see what happens...
Update: Trying different USB ports does not help.
What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App
jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.
Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.
I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.
I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10
How do you know whether you have a hardware locked Vibrant or not?
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk
Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?
Hello,
My Samsung Galaxy S4 is still under warranty, and the volume down button seems to have jammed. This has resulted in my phone being constantly booted onto the screen where I can either download a custom OS or restart the phone. The problem is I cannot choose either of these options as the volume down key is stuck and I can't choose either. I then have to restart my phone and, surprise surprise im back on that screen. The only way around this is to hold the volume up key, which then takes me into safe mode. I have previously rooted this phone so I cannot take it in for warranty, but I was wondering if there was any way to either boot my phone into the normal mode or to remove the root so I can take it in under warranty.
Thanks for any help.
Use ADB to boot into download mode (search; tutorials/how to's easily found on here/Google), flash 3 part stock rom which will wipe it, send it in for warranty service. Sorted.
MistahBungle said:
Use ADB to boot into download mode (search; tutorials/how to's easily found on here/Google), flash 3 part stock rom which will wipe it, send it in for warranty service. Sorted.
Click to expand...
Click to collapse
Thank you so much for such an easy and quick response! I'll write back here when I'm done to let you know how it went. Thanks again!
MistahBungle said:
Use ADB to boot into download mode (search; tutorials/how to's easily found on here/Google), flash 3 part stock rom which will wipe it, send it in for warranty service. Sorted.
Click to expand...
Click to collapse
Tried this method, and fell at the first hurdle. Not sure if its because I'm in safe mode but couldn't get ADB to work. It wasn't installing the drivers and wasn't being recognised when I checked for ADB devices..
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
toopty said:
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
Click to expand...
Click to collapse
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
cgillie92 said:
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
Click to expand...
Click to collapse
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
toopty said:
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
Click to expand...
Click to collapse
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
cgillie92 said:
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
Click to expand...
Click to collapse
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
toopty said:
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
Click to expand...
Click to collapse
I hope someone helps us out. I really cant afford a new one because the warranty is void. I was going back to stock because of all of the little bugs that need to be ironed out in roms. cause kit kat is around the corner hopefully and my problem virtually is the same i might have had my brightness on auto or something prior to that.
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
After following the instructions on the above link i was able to get fastboot status on my phone. It did not fully restore my phone however. I was able to flash twrp via fastboot. I was then able to boot into twrp and run the command at this link via twrp terminal http://forum.xda-developers.com/showthread.php?t=2451696
Thanks to everyone for all your help.
toopty said:
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Click to expand...
Click to collapse
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
cgillie92 said:
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
Click to expand...
Click to collapse
Ignore all the message, unplug you phone get ready to type the command, plug it in and immediately press enter to run the command. it took some trial and error, and i had to use this other post to help me out. I actually got fastboot working first, then used this post to http://forum.xda-developers.com/showthread.php?t=2477595 to get download mode working, and to flash twrp recovery. After that i used this post to run the command line from with twrp. http://forum.xda-developers.com/showthread.php?t=2451696 . I didn't have to flash the factory tot to my phone, but i have that option now because download mode is working. This process will work, there is hope for you getting your phone back. I'm fully recovered. I decided 12B is not worth it in the mean time, but if you want 12B you need to flash the factory tot and then upgrade. There is a way to root 12B, but as of this time you are unable to get Custom Recovery on it.