Related
how get in h boot else
as side button because volume button NOT work
hang boot logo from costum firm
any way from desktop
Try using this command in adb: adb reboot bootloader
Source: 1 minute with Google. Seriously. Google exists. Use it.
pls adb close everytime fastly?
abumaha said:
pls adb close everytime fastly?
Click to expand...
Click to collapse
pls help here don´t get it have video pls
Do this: Copy the location of you adb.exe
Open up command prompt
cd [location]
adb reboot bootloader
You need to access the adb via the command prompt, not just open it.
look pls my cmd
where can´t find it
pls can help team viewer
you are not doing it right. once you have downloaded the android skd you need to open the file and go all the way to \Android\android-sdk\platform-tools. then go to the top of the page in the toolbar, and copy the address. then go to the command prompt and the type cd (followed by the location you have just copied) then type adb shell
then type adb reboot bootloader. that should do it.
or! just use this app allowing you have root
https://market.android.com/details?...NvbS5zaXJpdXNhcHBsaWNhdGlvbnMucXVpY2tib290Il0.
hit the thanks button if i helped
problem is cant start phone and can´t get via side button in recovery
device can not found?
hang in bootlogo
problem is phone can´t be detect
simply how can erase all of it
side button not work cant start phone !
abumaha said:
problem is cant start phone and can´t get via side button in recovery
device can not found?
hang in bootlogo
Click to expand...
Click to collapse
this might not end well. has the hardware method ever worked for you? because if adb doesnt recognise the device your stuffed i think :/ are you s-off and stuff?
100% worked before i used with 3 costum rom via rom manager
but last was this **** rom icyfire hang on android logo always
now phone is off red light is on charge but not connecte to desktop
Sounds more like offmode charging bug to me, pop out the battery then replace and try to power on the phone. If it works go back to recovery and flash a new rom or a backup.
Then post here if it works and someone will help you fix it.
Sent from my HTC Wildfire using xda premium
yes think so
no connect to desktop
else i would flash with official ruu like before
i tried like u say but like i showed u hang on boot or just in off bug charge
when i take out batterie wait one moment then back batterie it starts
u see htc logo after u see again android logo hanging all the time
i think theres no way else only via jtag right
Take out the battery then replace, don't power on the phone normally, use volume down and power to get into hboot. If that still won't work your only choice is to use adb to enter recovery,
Do you know how to use adb?
Sent from my HTC Wildfire using xda premium
pls read thereads before cän´t go in recovery
my side button not work damaged!
allready used adb but no connect to desktop
only one sound hear but not else
First, I did read the thread that's why I thought I'd chip in and try to help.
Second, your english isn't too clear so what you're saying doesn't make much sense.
Third, if you have adb setup correctly all you need to do is connect the phone to pc, open a command prompt and type adb reboot recovery then wipe everything in recovery and flash a new Rom or restore a backup..
But if my help is not wanted take your ass over to eBay and buy a new volume button and sort it out yourself.
Sent from my HTC Wildfire using xda premium
abumaha said:
allready used adb but no connect to desktop
Click to expand...
Click to collapse
That's how you use ADB (Per your Screenshot)? Well done. Hopefully this gives you a lesson to not flash stuff randomly in the future and research before messing with your phone.
Anyway, cant help much apart from the battery pull method which Scratch described because applying any working fix WILL need you to boot ATLEAST into HBOOT, if not Recovery. So, if your battery fix doesn't work, get the volume button fixed, then you can be in a position to get it back to life. (Else, JTAG, as you said)
are you sure your side button doesnt work?
sometimes it takes my phone a little time to get into hboot it just depends where you are pressing on the side button... also try holding the side button down first and then just tap the power button
before you say my side button doesnt work at least try it
!!!!!!!NOTE!!!!!!!
USE TEENYBIN IN DEV SECTION
!!!!!!!!NOTE!!!!!!
Hi All,
I've noticed that there isn't a guide that contains all the information for restoring your phone to a stock state. I recently soft-bricked my phone, and with the help of XDA and the members at IRC I was able to restore my phone. Most of these methods will require you LGNPST ; however, we'll also attempt to fix with restoring backups and flashing new roms.
Accessing Recovery Screen (First Step if you have bricked your phone)
This is our initial step for any problems that might arise. If you can access recovery, usually you're in a perfectly fine situation.
1. Power off your phone by holding Volume down & power at the same time.
2. When the screen shuts off, switch to entering fastboot by holding Volume Up & Power. Release immediately once you see a black screen with some text on the bottom.
3. You should see a black screen with some text at the bottom.
4. Press volume down 2x and then the power button.
5. You should see either TWRP or CWM recovery.
6. Wipe Cache, Dalvic Cache, and Factory Wipe
7. Flash new stock zip. Wipe caches again.
8. Restart.
I don't have a zip in my local storage!!!!
It's okay. We can still fix this. All we need to do is sideload the zip.
On PC or Mac
1. Download the Android SDK HERE or Download Files Located below.
2. Place files on Desktop.
3. Enter Terminal or Console
4. Go to your desktop by entering
cd /Users//Desktop
The is your unique information.
On Phone
1. Do step 1 -5 above.
2. On TWRP go to advanced and place your phone in ADB mode.
3. Wait for the terminal screen to come on.
After setting up the above
1. Go back to your PC and type the below.
For Windows remove the "./"
./adb sideload .zip
2. On terminal you should see the percentile for the upload.
3. Wait.
4. Do steps 6-8 on Accessing Recovery Screen
LGNPST(No Direct Links)
Getting the files to revert back to stock can only be accessed from IRC or private message me. Please, DO NOT SHARE the link.
For anyone at IRC, if I provide to much information, I will be more than willing to pull information.
IRC Here
After you've acquired the Auto-LGNPST and the .tot file which can be accessed from the Sprint Directory.
1. Run install.bat to install the necessary programs. If you are using Windows Vista or later then Run install.bat as Administrator (Right click install.bat and click Run as Administrator)
2. Download the proper factory image (should end with .tot) and rename the file from .tot to .bin (if it ends with .zip, gzip, .rar, .7z, .tar, etc. than you need to extract it first)
3. Plug your phone into the computer. Then put your phone in download mode, continue reading if your not sure how. From then power off state press and hold Volume Up + Down and then press Power. If this does not work then try again except release the power before the LG logo shows up. The phone's screen will says "Download Mode Do Not Unplug".
4. Wait for the drivers to be detected and installed. Once they are run LGNPST. To do so do the following: Click Start - All Programs (if applicable) - LGNPST
5. Select LGNPST_LS970.dll for the DLL file and then for the .bin file, use the bin file that you renamed from tot to bin.
If LGNPST errors out at 85%, after a few minutes turn your phone off and hold the power button until the phone powers on, then release.
Helpful Button Presses
From Powered Down Device
Volume Up + Power = Boot into Fastboot Mode
Volume Down + Volume Up + Power (While Plugged into Computer) = Download Mode
Volume Down + Volume Up (While PLUGGING into Computer) = Download Mode
Bootloop
Volume Down + Power = Power Down
On launcher screen
Volume Down + Power = Power Down
Fastboot Screen
Volume Down twice, then press Power = Enter Recovery
Additional information
There is now a v9 root method.
Utilize the v9 .tot avaible in XDA or IRC. v9 tot
Many people are experiencing issues when LGNPST times out at 85%, which then leads to a phone that never roots and unlocks properly. If you're still soft-bricking, follow these steps.
Shut the phone off by placing your phone in download mode
When in download mode, hold down volume down and power for 30+ seconds
When the phone is shut off, and isn't turning itself back on when no buttons are pressed, plug into a wall cahrger
If you don't immediately see a charging battery, leave the charger for a considerable amount of time.
Reroot your phone after restoring
Root Device - Thanks to Engine95
Thanks
sharkboy0901
B-Breezy
AshtonTS
engine95
Folks at IRC
Very nice. Thank you! This'll help alot of us.
Sent from my LG-LS970 using xda premium
Does anyone need other information for this guide?
Awesome guide thanks for the hard work!
Sent from my LG-LS970
_______________________
Samsung Galaxy S III
HTC Evo 4G LTE
Google Galaxy Nexus
Samsung Galaxy S II
Google Nexus S
HTC Evo 3D
HTC Evo 4G
This should be stickied somewhere.
It reboots at 67% but after all I get is the flashing red notification and flashing soft keys at the bottom....help lol
Sent from my SPH-L710 using xda premium
If possible could I get a LGNPST pm?
So my computer doesn't seem to recognize my device. I wiped out too much info with TWRP and now have no ROM or any OS on the device, but can get into fastboot and TWRP, but when I enter "adb devices" the list is empty. How can I get my Win 7 computer to recognize my device?
swizz-knife77 said:
It reboots at 67% but after all I get is the flashing red notification and flashing soft keys at the bottom....help lol
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Getting the same. I'm at a loss -____-.
Re: [GUIDE] Restoring Phone from Soft-Brick and FAQ [1/5]
This has some really useful information. Especially with our tempermental phones. Can we get this stickied?!
Sent from my LG-LS970 using xda premium
So I'm using LGNPST to get my friends phone back to stock using all files provided via IRC.
Just as indicated, LGNPST errors out at 85%, I unplug and hold power button as instructed but nothing happens. Am I doing something wrong?
*EDIT* got it figured out, thanks to everyone that helped.
Disaster (I hope not)
Hi ... please help my phone is drowning and needs some CPR badly.
I tried to install lifeless on Sprint LS 970 using TWRP ... all went well,or so TWRP reported, until I tried to reboot and got the dread gray screen that won't ever turn completely off ...
I've repeatedly (like over and over) tried everything in this post to try and get into recovery or fast boot but nothing worked ... it will go into download mode and it will turn off and not immediately turn back on if I hold the power and vol down button for a minute or so, but when I try the next step and plug in the ac charger I get an immediate single flash of the LG loader and the gray screen.
So what should I do now or next or whatever to try and salvage the thing. Computer wise I am running Win 7 64, is there anything I can do from there via download mode?
Also, there's a pinhole on the top (G side of the LG logo) of the phone which looks suspiciously like like it should be a reset button, but pusing it with a dental pick has gotten me nowhere ... but maybe I'm missing something there as well.
Or would it help to remove the two torx screws, open the case, and pull the battery for a minute or two. (Must remind myself to never ever buy another phone with a locked down battery ... talk about the ultimate in dumb design ... especially when the thing starts refusing to accept a charge long before the user is due for a two-year upgrade.) The problem is it's wonderful phone except for that bit of idiocy.
Anyway, I would appreciate it more than I can say, and even donate something to the development kitty, if someone could help me reanimate this phone.
Thanks
AdriVelazquez said:
Hi All,
I've noticed that there isn't a guide that contains all the information for restoring your phone to a stock state. I recently soft-bricked my phone, and with the help of XDA and the members at IRC I was able to restore my phone. Most of these methods will require you LGNPST ; however, we'll also attempt to fix with restoring backups and flashing new roms.
Accessing Recovery Screen (First Step if you have bricked your phone)
This is our initial step for any problems that might arise. If you can access recovery, usually you're in a perfectly fine situation.
1. Power off your phone by holding Volume down & power at the same time.
2. When the screen shuts off, switch to entering fastboot by holding Volume Up & Power. Release immediately once you see a black screen with some text on the bottom.
3. You should see a black screen with some text at the bottom.
4. Press volume down 2x and then the power button.
5. You should see either TWRP or CWM recovery.
6. Wipe Cache, Dalvic Cache, and Factory Wipe
7. Flash new stock zip. Wipe caches again.
8. Restart.
I don't have a zip in my local storage!!!!
It's okay. We can still fix this. All we need to do is sideload the zip.
On PC or Mac
1. Download the Android SDK HERE or Download Files Located below.
2. Place files on Desktop.
3. Enter Terminal or Console
4. Go to your desktop by entering
cd /Users/<username>/Desktop
The <username> is your unique information.
On Phone
1. Do step 1 -5 above.
2. On TWRP go to advanced and place your phone in ADB mode.
3. Wait for the terminal screen to come on.
After setting up the above
1. Go back to your PC and type the below.
For Windows remove the "./"
./adb sideload <filename>.zip
2. On terminal you should see the percentile for the upload.
3. Wait.
4. Do steps 6-8 on Accessing Recovery Screen
LGNPST(No Direct Links)
Getting the files to revert back to stock can only be accessed from IRC or private message me. Please, DO NOT SHARE the link.
For anyone at IRC, if I provide to much information, I will be more than willing to pull information.
IRC Here
After you've acquired the Auto-LGNPST and the .tot file which can be accessed from the Sprint Directory.
1. Run install.bat to install the necessary programs. If you are using Windows Vista or later then Run install.bat as Administrator (Right click install.bat and click Run as Administrator)
2. Download the proper factory image (should end with .tot) and rename the file from .tot to .bin (if it ends with .zip, gzip, .rar, .7z, .tar, etc. than you need to extract it first)
3. Plug your phone into the computer. Then put your phone in download mode, continue reading if your not sure how. From then power off state press and hold Volume Up + Down and then press Power. If this does not work then try again except release the power before the LG logo shows up. The phone's screen will says "Download Mode Do Not Unplug".
4. Wait for the drivers to be detected and installed. Once they are run LGNPST. To do so do the following: Click Start - All Programs (if applicable) - LGNPST
5. Select LGNPST_LS970.dll for the DLL file and then for the .bin file, use the bin file that you renamed from tot to bin.
If LGNPST errors out at 85%, after a few minutes turn your phone off and hold the power button until the phone powers on, then release.
Helpful Button Presses
From Powered Down Device
Volume Up + Power = Boot into Fastboot Mode
Volume Down + Volume Up + Power (While Plugged into Computer) = Download Mode
Volume Down + Volume Up (While PLUGGING into Computer) = Download Mode
Bootloop
Volume Down + Power = Power Down
On launcher screen
Volume Down + Power = Power Down
Fastboot Screen
Volume Down twice, then press Power = Enter Recovery
Additional information
There is now a v9 root method.
Utilize the v9 .tot avaible in XDA or IRC. v9 tot
Many people are experiencing issues when LGNPST times out at 85%, which then leads to a phone that never roots and unlocks properly. If you're still soft-bricking, follow these steps.
Shut the phone off by placing your phone in download mode
When in download mode, hold down volume down and power for 30+ seconds
When the phone is shut off, and isn't turning itself back on when no buttons are pressed, plug into a wall cahrger
If you don't immediately see a charging battery, leave the charger for a considerable amount of time.
Reroot your phone after restoring
Root Device - Thanks to Engine95
Thanks
sharkboy0901
B-Breezy
AshtonTS
engine95
Folks at IRC
Click to expand...
Click to collapse
ekb606 said:
Hi ... please help my phone is drowning and needs some CPR badly.
I tried to install lifeless on Sprint LS 970 using TWRP ... all went well,or so TWRP reported, until I tried to reboot and got the dread gray screen that won't ever turn completely off ...
I've repeatedly (like over and over) tried everything in this post to try and get into recovery or fast boot but nothing worked ... it will go into download mode and it will turn off and not immediately turn back on if I hold the power and vol down button for a minute or so, but when I try the next step and plug in the ac charger I get an immediate single flash of the LG loader and the gray screen.
So what should I do now or next or whatever to try and salvage the thing. Computer wise I am running Win 7 64, is there anything I can do from there via download mode?
Also, there's a pinhole on the top (G side of the LG logo) of the phone which looks suspiciously like like it should be a reset button, but pusing it with a dental pick has gotten me nowhere ... but maybe I'm missing something there as well.
Or would it help to remove the two torx screws, open the case, and pull the battery for a minute or two. (Must remind myself to never ever buy another phone with a locked down battery ... talk about the ultimate in dumb design ... especially when the thing starts refusing to accept a charge long before the user is due for a two-year upgrade.) The problem is it's wonderful phone except for that bit of idiocy.
Anyway, I would appreciate it more than I can say, and even donate something to the development kitty, if someone could help me reanimate this phone.
Thanks
Click to expand...
Click to collapse
I'll private message you instructions to LGNPST. Did you try LGNPST?
Also the hole is a microphone, let's hope you didn't mess it up
AdriVelazquez said:
I'll private message you instructions to LGNPST. Did you try LGNPST?
Also the hole is a microphone, let's hope you didn't mess it up
Click to expand...
Click to collapse
During the LGNPST process in OP, when I plug in my phone and set it to download mode, it crashes my PC ???? I am on Windows8 64 bit
any ideas ... also in LGNPST program I cannot click on Select DLL, my clicks dont register???
Shantox73 said:
During the LGNPST process in OP, when I plug in my phone and set it to download mode, it crashes my PC ???? I am on Windows8 64 bit
any ideas ... also in LGNPST program I cannot click on Select DLL, my clicks dont register???
Click to expand...
Click to collapse
That;s odd. I have windows 8 also and it worked fine. Try the updated drivers that engine's root thread has.
AdriVelazquez said:
That;s odd. I have windows 8 also and it worked fine. Try the updated drivers that engine's root thread has.
Click to expand...
Click to collapse
OK thx!
---------- Post added at 10:44 PM ---------- Previous post was at 10:28 PM ----------
Shantox73 said:
OK thx!
Click to expand...
Click to collapse
Didnt help =(
ZeroCool84 said:
If possible could I get a LGNPST pm?
Click to expand...
Click to collapse
Could I please get one too. I'm trying to find LGNPST and can't anywere
mendojester said:
Could I please get one too. I'm trying to find LGNPST and can't anywere
Click to expand...
Click to collapse
I am having trouble too. When I click install.bat it doesn't install anything. It says file path could not be found. I have done it twice
to no avail. I am already logged in as admin. Home computer running 64bit win 7. Also in lgnpst I can select a dll file but it is a
componant 5 .dll not anything near what it should be.
O.k. N.M. The problem with my computer is I can't extract in my download folder, I need to move the file to my desktop and work from there.
We will see how the rest goes now. Well it didnt help, it errors out in like 2 seconds. Looks like i will have to wait for a rom.
LGNPST for linux
Can LGNPST be run on a linux box and if so where can I find the download?
I apologize for anyone that's been trying to contact me regarding LGNPST. As you know, JB leaked and we've all been busy. Hopefully one of the many amazing members helped.
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
the proper term to use here is bootloop
ur phone bootlooped and u need to flash back the stock firware via odin
go back in the dev section and find somethng relatd to odin
remmbr bfre flashing any rom u shud always backup ur rom via clockworkmod
u must have done something wrng while flashng jellybean mod...take the steps crrctly
EDIT:- http://forum.xda-developers.com/showthread.php?t=1827685
heres the link to fix ur phone
properly take the steps plzz
bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
Are u able to boot into CWM recovery, Power and both volume up and down?
garner said:
Are u able to boot into CWM recovery, Power and both volume up and down?
Click to expand...
Click to collapse
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
bluroot said:
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
Click to expand...
Click to collapse
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
Do you mean that I need to continually rock the Volume key up and down while holding the Power button? Volume Up with Power put it in boot mode, and when I tried rocking it a couple of times I got the same result. It I understand you correctly, the idea sounds tricky. Is this supposed to work on a Galaxy Nexus?
press and hold both ends of the volume button and the power button... its really not that hard.
Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
What I really should have done was slow down, or quit while I was ahead to get some rest last night! I had researched the root process for my phone ad nauseum, which I know is why I succeeded at getting ClockworkMod safely installed. By the time that was done I was tired, but I counldn't stand the thought of living without my files loaded on my phone - I was in the bad state of needing too much to complete what I had intended to do. I see I had the wrong impression that ClockworkMod would take care of the whole process once I had that working, guess it didn't. When you've been through the process of installing a hundred versions of Windows and Linux on a PC, which never needs to be pre-wiped (the new OS does that), who would have thunk it's that much different with a phone computer?
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
This is another thing I never would have guessed without being told specifically, that it's even possible to hold down both ends of a rocker switch and have it do a different function - I tried this, and now it works! I had used my PC to root my phone last night, and right now I'm at work, where there will be time to go through this in a couple of hours. I took a brief look at the tutorial recommended by Zepius, and am wondering if I am set to proceed. I plan on using my work PC, not the one at home with the drivers I used to root my phone. Nobody else uses it and I have never used it for anything phone-related. Can I presume any drivers which I'm warned should be uninstalled would be on the PC which is used, and not the phone?
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
bluroot said:
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
Click to expand...
Click to collapse
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
bluroot said:
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
Click to expand...
Click to collapse
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I got a device ID (long string of characters) on that fastboot command, but I'm still concerned that my phone won't talk to Device Manager at all. Windows 7 doesn't pop up a connection window when it's plugged in, should that be expected?
What I mean by "not talking to Device Manager" is that the only item under Portable devices is just E:\ - no device listed here! The tutorial in your signature hinges on there being a device listed "without thde yellow exclamation point", for the installation of new drivers, therefore I don't know how to follow it from here. The adk drivers which were used to root my phone (they were good, the problem began when I tried to flash a rom and missed a step or three) are stil there, but I'll replace them if I can find a process which can talk to my phone in it's present state.
On a side note (and only because it held me up in responding tonight from my Windows system), is this site partial to Firefox? I am able for the first time to login, and I wonder if it isn't because I quit trying to through my Windows 7 system. It has only Windows IE, and Chrome (which couldn't even browse this site). I am currently on my Ubuntu system with Firefox.
good lord... you have a device ID so just use the fastboot commands... start at part D
Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I said much the same myself.
For the fastboot devices test, I have a string of characters, but no device name, only "fastboot" on the single output line with those characters. Is this a valid device ID?
"...just use fastboot" Ok, but how? Should (can I) even do this use fastboot to transfer files to my phone under it's somewhat anonymous status with Windows? Since last night's fiasco nothing was named under "Portable Devices", only "E:\" was displayed. I have no graphical display in the file manager, so how am I supposed to transfer the necessary files to the root of my phone? I don't even see a way of addressing it to install drivers now.
I will need drivers because I attempted to follow this tutorial (which doesn't account for what I am (not) seeing on my system. I got as far as uninstalling the good drivers which I used last night in favor of what was offered for use with the tutorial, and now Device Manager doesn't even have a Portable Devices category. The "Universal Naked Driver" was to replace my uninstalled drivers, and interestingly the contents of it's expanded folders don't even contain fastboot (the adb package which I used last night did). In light of this, how am I supposed to have even fastboot?
I hate to be a PIA about this, but I guess I'm more a n00b than was presumed in this tutorial - it's either that or my situation really is too different that I can use it as is. Could I please get a few clues in light of what the tutorial doesn't address? Do I have any means of installing anything and transferring files with my device-PC communications as they are, and if so how can I do it? I'll give it a run if I understand how.
Thanks.
Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I see now that Part D calls for flashing JO03C from my PC, not the device root, ok.
Also, after rebooting my laptop, the E:\ is back under Portable Devices in Device Manager. When I double-click this I get the statement
Device: Portable Devices
Manufacturer: Generic-
Location: on UMBus Enumerator
I don't think this looks better than the Microsoft default, but is it good enough for what I need to do?
I still have the driver package android-sdk-windows, which contains adb and fastboot, so perhaps I should just use this according to Part D and see what happens?
bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
garner said:
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
Click to expand...
Click to collapse
Good god, I never should have read Zepius's tutorial - I didn't need my PC at all! If I understood what bananagranola had said, I could have saved a lot of time!
Oh, no, now I can't connect with the server!
Could I have possibly lost my radio from what I did earlier? I was able to boot up, and I was upgraded to 4.2.1 when I did the data wipe. Starting over, I should have had a prompt to connect with gmail and download my contacts, but this didn't happen. My People app is unpopulated, so I chose to connect to "sign into an account". While I am sure of my login input, it didn't recognize this, and then the process ended with a "couldn't finish - couldn't open connection with the server" error. Any clue where to go from here?
Some standard apps are missing too, including the Play Store app!
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)
wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.
Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.
So my screen blacked out and I would like to attempt and retrieve the information off of my phone. I have an idea to use the CWM I have installed on my phone and from there mount it. But since I cannot see the screen, I was hoping somebody could tell me the number of presses of each button so I can mount it. Thanks!
joecarp said:
So my screen blacked out and I would like to attempt and retrieve the information off of my phone. I have an idea to use the CWM I have installed on my phone and from there mount it. But since I cannot see the screen, I was hoping somebody could tell me the number of presses of each button so I can mount it. Thanks!
Click to expand...
Click to collapse
not sure if cwm will help, but twrp 3 will definitely help, i want you to boot into download mode and flash twrp 3 using Odin, and then boot into recovery.
TWRP 3 has MTP enabled by default, so when you're in TWRP and connected your phone to PC, you will see your phone on PC and will be able to copy anything you want.
also you can use adb pull commands but it requires usb debugging on in your rom.
MigoMujahid said:
not sure if cwm will help, but twrp 3 will definitely help, i want you to boot into download mode and flash twrp 3 using Odin, and then boot into recovery.
TWRP 3 has MTP enabled by default, so when you're in TWRP and connected your phone to PC, you will see your phone on PC and will be able to copy anything you want.
also you can use adb pull commands but it requires usb debugging on in your rom.
Click to expand...
Click to collapse
Should I be able to do all this without the use of my screen?
joecarp said:
Should I be able to do all this without the use of my screen?
Click to expand...
Click to collapse
yes, you will do it blindly, but it's not hard.
you press power + home + volume down for 3 seconds, then press volume up, and connect your phone to PC, then flash the TWRP 3 using Odin,after the flash is done, remove battery, and insert again, then hold the power + home + volume up for 4 seconds, the release the power and keep holding the other 3 buttons for another 3 seconds then release, by now it should be in recovery mode, now connect to PC and you should see your phone and all its content.
MigoMujahid said:
yes, you will do it blindly, but it's not hard.
you press power + home + volume down for 3 seconds, then press volume up, and connect your phone to PC, then flash the TWRP 3 using Odin,after the flash is done, remove battery, and insert again, then hold the power + home + volume up for 4 seconds, the release the power and keep holding the other 3 buttons for another 3 seconds then release, by now it should be in recovery mode, now connect to PC and you should see your phone and all its content.
Click to expand...
Click to collapse
Alright thanks, I'm going to go try it when I have some more time. Thank you a lot
joecarp said:
So my screen blacked out and I would like to attempt and retrieve the information off of my phone. I have an idea to use the CWM I have installed on my phone and from there mount it. But since I cannot see the screen, I was hoping somebody could tell me the number of presses of each button so I can mount it. Thanks!
Click to expand...
Click to collapse
How about just turn the phone on and connect a USB and tranfer everything to your PC ?(Donot requires screen)
Gurkanwal Chauhan said:
How about just turn the phone on and connect a USB and tranfer everything to your PC ?(Donot requires screen)
Click to expand...
Click to collapse
good question.
he can't do it in two cases:
1- if he is using android 6.0+
2- if he is using a password, PIN or a pattern in his lock screen.
i believe he should have tried your suggestion already, it would be a shame if he didn't because it's an Obvious thing.
however, i should have mentioned that as well...