Hey!
I accidentally bricked two of the exact same phones, and I dont know how to unbrick them. They both are Samsung SGH-T959V's. They are pretty old, and I wanted to put a newer OS on them. Here is what is wrong with them:
Phone 1: Can boot into TWRP but when I try doing anything, it just gets stuck, forever.
Phone 2: Screen has multicolored lines all over it. Kinda like tv's when you go to the wrong channel.
I would be really grateful if anyone can help.
nahtnam said:
Hey!
I accidentally bricked two of the exact same phones, and I dont know how to unbrick them. They both are Samsung SGH-T959V's. They are pretty old, and I wanted to put a newer OS on them. Here is what is wrong with them:
Phone 1: Can boot into TWRP but when I try doing anything, it just gets stuck, forever.
Phone 2: Screen has multicolored lines all over it. Kinda like tv's when you go to the wrong channel.
I would be really grateful if anyone can help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1358498
The multicolored lines are due to not having the GB bootloader.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=1358498
The multicolored lines are due to not having the GB bootloader.
Click to expand...
Click to collapse
Hey!
Thanks for the reply.
For some reason, ADB is not recognizing my device so I cant flash it. I am running ubuntu 14.04. Not sure what to do!
nahtnam said:
Hey!
Thanks for the reply.
For some reason, ADB is not recognizing my device so I cant flash it. I am running ubuntu 14.04. Not sure what to do!
Click to expand...
Click to collapse
What does adb have to do with it? adb doesn't work in Download Mode.
es0tericcha0s said:
What does adb have to do with it? adb doesn't work in Download Mode.
Click to expand...
Click to collapse
Oh, thats why its not working.
Anyways, the jar isnt detecting my phone then but when I do lsusb it shows up though.
nahtnam said:
Oh, thats why its not working.
Anyways, the jar isnt detecting my phone then but when I do lsusb it shows up though.
Click to expand...
Click to collapse
Do you have the correct version of Java that's suggested in Step 2?
es0tericcha0s said:
Do you have the correct version of Java that's suggested in Step 2?
Click to expand...
Click to collapse
Im running open-jdk-7, instead of 6. Shouldnt that still work?
nahtnam said:
Im running open-jdk-7, instead of 6. Shouldnt that still work?
Click to expand...
Click to collapse
Always go with the recommendation of the installation notes. Just think about it in the terms of tools. You might need a phillips head screwdriver to fix something, but they make different sized ones for the job...
Related
I just got the phone today and I already screwed it up. I followed this http://wiki.cyanogenmod.com/wiki/Mo...ng_the_Bootloader_with_RSD_Lite_.28Windows.29
but forgot to install fastboot now am I screwed?
jeffreygtab said:
I just got the phone today and I already screwed it up. I followed this http://wiki.cyanogenmod.com/wiki/Mo...ng_the_Bootloader_with_RSD_Lite_.28Windows.29
but forgot to install fastboot now am I screwed?
Click to expand...
Click to collapse
Edit: I think I got fastboot working on the pc end, but when i run "fastbook oem unlock" it just says waiting for devices.
jeffreygtab said:
Edit: I think I got fastboot working on the pc end, but when i run "fastbook oem unlock" it just says waiting for devices.
Click to expand...
Click to collapse
Waiting for devices means it isn't seeing the phone. Did you install the drivers from Motorola properly?
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/78830/p/30,6720,7898/session/L3RpbWUvMTM0OTM5NzcwOC9zaWQvbDI3UUpWN2w%3D
Unplug phone from computer, install drivers on PC from link above, plug phone back in, and wait until Windows has finished updating the drivers.
Also, make sure you are using a USB port on the back of your PC, as this can make a difference.
CaelanT said:
Waiting for devices means it isn't seeing the phone. Did you install the drivers from Motorola properly?
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/78830/p/30,6720,7898/session/L3RpbWUvMTM0OTM5NzcwOC9zaWQvbDI3UUpWN2w%3D
Unplug phone from computer, install drivers on PC from link above, plug phone back in, and wait until Windows has finished updating the drivers.
Also, make sure you are using a USB port on the back of your PC, as this can make a difference.
Click to expand...
Click to collapse
No installed some moto device manager/helper garbage, as instructed in a different post. I'll try this. Thanks.
EDIT that is what I installed i think :/
jeffreygtab said:
No installed some moto device manager/helper garbage, as instructed in a different post. I'll try this. Thanks.
EDIT that is what I installed i think :/
Click to expand...
Click to collapse
Also it fails to flash the sbf file i believe, it gets to 98 percent and then says it failed.
jeffreygtab said:
Also it fails to flash the sbf file i believe, it gets to 98 percent and then says it failed.
Click to expand...
Click to collapse
Ok so I got the bootloader to unlock. THANK GOD. Now I need to get cwm, up and running... My heart almost stopped 10 times while doing this...
Thanks for the help. Although that wasn't the problem.
jeffreygtab said:
Ok so I got the bootloader to unlock. THANK GOD. Now I need to get cwm, up and running... My heart almost stopped 10 times while doing this...
Thanks for the help. Although that wasn't the problem.
Click to expand...
Click to collapse
My best suggestion is to follow all of the instructions here: http://forum.xda-developers.com/showthread.php?t=1302423 It sounds like you probably have the first part done, so go with the "Proper Recovery" section once you're sure you have the prerequisites.
Sent from my MB860 using xda app-developers app
Also, could you try using EDIT POST more often?
ravilov said:
Also, could you try using EDIT POST more often?
Click to expand...
Click to collapse
Yeah sorry my bad I was just frantic, i got it all figured out now.
I recently acquired an optimus g and the guy that owned it before said he tried flashing a KitKat ROM and it soft bricked. I can't get the computer to recognize the phone and I got the most recent drivers for it. I was gonna use lgnpst to fix it but I can't. Does anybody have any ideas on how I can fix it?
gerg6986 said:
I recently acquired an optimus g and the guy that owned it before said he tried flashing a KitKat ROM and it soft bricked. I can't get the computer to recognize the phone and I got the most recent drivers for it. I was gonna use lgnpst to fix it but I can't. Does anybody have any ideas on how I can fix it?
Click to expand...
Click to collapse
Computer doesn't recognize it at all, or just lgnpst? Lgnpst doesn't work with USB 3.0 if that helps explain it.
adfurgerson said:
Computer doesn't recognize it at all, or just lgnpst? Lgnpst doesn't work with USB 3.0 if that helps explain it.
Click to expand...
Click to collapse
My computer won't recognize it at all, I have another lgog that I use and I used that 1 to get all the recent drivers. I don't understand it....
gerg6986 said:
My computer won't recognize it at all, I have another lgog that I use and I used that 1 to get all the recent drivers. I don't understand it....
Click to expand...
Click to collapse
Does it show up in windows device manager? Also if it was ever converted it might need nexus 4 drivers.
adfurgerson said:
Does it show up in windows device manager? Also if it was ever converted it might need nexus 4 drivers.
Click to expand...
Click to collapse
That's the only conclusion I have come across, if it was converted is there anyway to fix it?
gerg6986 said:
That's the only conclusion I have come across, if it was converted is there anyway to fix it?
Click to expand...
Click to collapse
Lgnpst using n4 drivers then there is a thread for fixing camera and storage issues.
adfurgerson said:
Lgnpst using n4 drivers then there is a thread for fixing camera and storage issues.
Click to expand...
Click to collapse
OK awesome, I will give that a try and report back when I get the chance. Thank you
gerg6986 said:
OK awesome, I will give that a try and report back when I get the chance. Thank you
Click to expand...
Click to collapse
Check device manager too. If it shows as QSUSB Dload it is a hard brick that can't be fixed with lgnpst.
What is it doing exactly, have you tried getting to recovery with button combo?
adfurgerson said:
Check device manager too. If it shows as QSUSB Dload it is a hard brick that can't be fixed with lgnpst.
What is it doing exactly, have you tried getting to recovery with button combo?
Click to expand...
Click to collapse
I can get to recovery but t it won't read my sdcard. I'm gonna try the n4 drivers and try lgnpst...
gerg6986 said:
I can get to recovery but t it won't read my sdcard. I'm gonna try the n4 drivers and try lgnpst...
Click to expand...
Click to collapse
Does it boot into the ROM? Is it softbricked now? You may just need a newer recovery.
adfurgerson said:
Does it boot into the ROM? Is it softbricked now? You may just need a newer recovery.
Click to expand...
Click to collapse
its still soft bricked, i tried numerous drivers for the n4 and i still cant get my computer to recognize the phone. i dont know what to do...
gerg6986 said:
its still soft bricked, i tried numerous drivers for the n4 and i still cant get my computer to recognize the phone. i dont know what to do...
Click to expand...
Click to collapse
I wonder if you could get adb to recognize phone. If so you could fastboot flash a different recovery, or adb push a zip to internal storage.
Does it boot to the splash screen? If so have you tried a factory reset using button combo?
adfurgerson said:
I wonder if you could get adb to recognize phone. If so you could fastboot flash a different recovery, or adb push a zip to internal storage.
Does it boot to the splash screen? If so have you tried a factory reset using button combo?
Click to expand...
Click to collapse
it only boots to the lg logo, im trying SDK tools to try and get adb to recognize it. hopefully it works...
gerg6986 said:
it only boots to the lg logo, im trying SDK tools to try and get adb to recognize it. hopefully it works...
Click to expand...
Click to collapse
For factory reset it is from phone powered off hold volume down and power until menu comes up.
adfurgerson said:
For factory reset it is from phone powered off hold volume down and power until menu comes up.
Click to expand...
Click to collapse
i tried that and it only boots to the lg logo..
adfurgerson said:
For factory reset it is from phone powered off hold volume down and power until menu comes up.
Click to expand...
Click to collapse
even wih he updated drivers i still cant get the computer to even see the phone at all...
adfurgerson said:
Does it boot into the ROM? Is it softbricked now? You may just need a newer recovery.
Click to expand...
Click to collapse
i cant get into the rom, everything has been completely wiped. i still have no success at getting the computer to recognize that it is plugged in..
gerg6986 said:
i cant get into the rom, everything has been completely wiped. i still have no success at getting the computer to recognize that it is plugged in..
Click to expand...
Click to collapse
I can't think of anything else to suggest. If anything pops into my head I'll post it here.
adfurgerson said:
I can't think of anything else to suggest. If anything pops into my head I'll post it here.
Click to expand...
Click to collapse
ok thank you very much...
I need to flash a file that locks the bootloader. It contains Aroma Installer. Is there a way to flash it without booting into recovery? Something linke an app that flashes the file directly from the phone?
MICH_** said:
I need to flash a file that locks the bootloader. It contains Aroma Installer. Is there a way to flash it without booting into recovery? Something linke an app that flashes the file directly from the phone?
Click to expand...
Click to collapse
Everything is gonna be done in recovery or bootloader. No way to do it other wise.
zelendel said:
Everything is gonna be done in recovery or bootloader. No way to do it other wise.
Click to expand...
Click to collapse
bad ._.
The problem is that i cant turn my phone off and boot into recovery.
MICH_** said:
bad ._.
The problem is that i cant turn my phone off and boot into recovery.
Click to expand...
Click to collapse
And why cant you turn it off?
zelendel said:
And why cant you turn it off?
Click to expand...
Click to collapse
dont know. my phone is somehow broken. If i turn it off it wont turn back on.. no idea why.
MICH_** said:
dont know. my phone is somehow broken. If i turn it off it wont turn back on.. no idea why.
Click to expand...
Click to collapse
I would use the ADB commands to boot into recovery. Also might want to look into logcats to see what the issue is.
zelendel said:
I would use the ADB commands to boot into recovery. Also might want to look into logcats to see what the issue is.
Click to expand...
Click to collapse
not even ADB works anymore. The phone is not being recognized by the pc..
MICH_** said:
not even ADB works anymore. The phone is not being recognized by the pc..
Click to expand...
Click to collapse
Looks like a logcat is the next step
Bat cave One
zelendel said:
Looks like a logcat is the next step
Bat cave One
Click to expand...
Click to collapse
I cant boot into fastboot either..
MICH_** said:
I cant boot into fastboot either..
Click to expand...
Click to collapse
That has nothing to do with getting a logcat
Bat cave One
zelendel said:
That has nothing to do with getting a logcat
Bat cave One
Click to expand...
Click to collapse
Btw my phone is now powered off.
MICH_** said:
Btw my phone is now powered off.
Click to expand...
Click to collapse
Well if you cant turn it on then you maybe out of luck and need a replacement.
zelendel said:
Well if you cant turn it on then you maybe out of luck and need a replacement.
Click to expand...
Click to collapse
Do you think HTC will spot the unlocked bootloader etc. ?
MICH_** said:
Do you think HTC will spot the unlocked bootloader etc. ?
Click to expand...
Click to collapse
Most likely, yes. If they can get it to power up.
zelendel said:
Most likely, yes. If they can get it to power up.
Click to expand...
Click to collapse
I make the bootloader to show "locked" and flashed the stock recovery!!!
Now the only thing i have to do is to s-on. It is still s-off. Is there as adb command for this? Or how to do that? Btw: I have got a HTC One
Yeah um I was changing some things in framework-res.apk and I forgot to change it back and now my phone just stays on the boot animation.
I have a rooted Sony Xperia m5 and I would like to know is there anyway that I can somehow access the phones folders while its in this state so I can rename it or just something to get it going again without losing all of my data because I have something kind of important on it. Any help is appreciated
If you have root then just use ADB to rename the file. There are plenty of tut on how to do this.
zelendel said:
If you have root then just use ADB to rename the file. There are plenty of tut on how to do this.
Click to expand...
Click to collapse
Do I need twrp or something because it keeps saying device offline
ih8redsn0w said:
Do I need twrp or something because it keeps saying device offline
Click to expand...
Click to collapse
That is just a driver issue. If it is installed them remove it and reinstall it.
zelendel said:
That is just a driver issue. If it is installed them remove it and reinstall it.
Click to expand...
Click to collapse
I've tried but still says offline
Am I supposed to to put it in some certain mode because I don't think it's working
ih8redsn0w said:
I've tried but still says offline
Am I supposed to to put it in some certain mode because I don't think it's working
Click to expand...
Click to collapse
Download mode is what you need to be in. Also helps alot if your in a Linux os
zelendel said:
Download mode is what you need to be in. Also helps alot if your in a Linux os
Click to expand...
Click to collapse
I put it into download mode and when I type adb devices it just stays blank but if I turn it on and it stays at the boot animation it comes up but says unauthorised and I'm on Windows 10
Would it help if I flashed twrp or no?
I am facing a weird issue with fastboot not detecting my device.
USB is fine (as in I have other USB-C based devices, and they are detected just fine and am able to flash images just fine with them), ADB is fine, including all commands like sideload, etc...
I just get hung on <waiting on device> when I boot to bootloader mode... I am sure it's possible that I am simply doing it wrong... I generally just run adb reboot bootloader on other devices, and boom I was in fastboot mode.
What I'm trying to do is go back to stock... I'm on The Developer Preview 2 for 13 at the moment and am finding some deal breaking issues with a couple apps that I need.
kevp75 said:
I am facing a weird issue with fastboot not detecting my device.
USB is fine (as in I have other USB-C based devices, and they are detected just fine and am able to flash images just fine with them), ADB is fine, including all commands like sideload, etc...
I just get hung on <waiting on device> when I boot to bootloader mode... I am sure it's possible that I am simply doing it wrong... I generally just run adb reboot bootloader on other devices, and boom I was in fastboot mode.
What I'm trying to do is go back to stock... I'm on The Developer Preview 2 for 13 at the moment and am finding some deal breaking issues with a couple apps that I need.
Click to expand...
Click to collapse
May be a driver problem. Do you have the latest of this installed?
why not show exactly what you are trying to do and what you get. copy paste what you see. then check version numbers of the tools you are using.
Lughnasadh said:
May be a driver problem. Do you have the latest of this installed?
Click to expand...
Click to collapse
had a previous version installed. will check when I fire th PC back up tomorrow
Lughnasadh said:
May be a driver problem. Do you have the latest of this installed?
Click to expand...
Click to collapse
It was exactly that. Going to have to bookmark that. I thought I had the latest installed (it was latest as of December lolol)
I do appreciate the help mate, now back to stock Rom for me... (got sick of A13 DP2's issues), plus now I can finally root this thing
kevp75 said:
It was exactly that. Going to have to bookmark that. I thought I had the latest installed (it was latest as of December lolol)
I do appreciate the help mate, now back to stock Rom for me... (got sick of A13 DP2's issues), plus now I can finally root this thing
Click to expand...
Click to collapse
Awesome! Glad you got it going
Lughnasadh said:
Awesome! Glad you got it going
Click to expand...
Click to collapse
You and me both lololol
I've been around these rooms a long long time, and this is the first device I've ever had issues like this with. Usually it's been a USB cable or port, but never a 3 month old driver lol
Now, that I'm back to stock, and rooted... maybe I can get some dev going