Related
Hi,
Problem: my desire s is not Booting up!! {not even in recovery mode} it is S-off and rooted
Symptoms: if i try to boot up it just vibrates for 2-3 times and the Red Charge indicator light, turns on. if i try to hold down the volume key & press the on key then it vibrates for 2-3 times & the Green indicator light turn on. That's it!! it is stuck there... doesn't boot up or anything.
What might have happened last night!!:
1. i downloaded some games apk from different websites and installed those.
2. tried to update ROM manager but failed
3. suddenly the volume increase indication came up in my screen (without even touching the volume keys!!) this kept coming...then i decided to give it a restart...after restarting everything came back to normal
4. but again it started to show up this morning...so decided to restart it again...and thats it....it wont boot up again!!!
Guys please DO help me out!!
Thanx in advance
Hello
Attempt to put charge into the phone by plugging it into the main charger.
Does the charge light come on when the phone is being charged?
Now download and Install the adb & fastboot onto your PC which you'll see in a link in my signature. Ensure that you have HTC drivers on you PC if not also download and install the link in my signature.
Plug phone into PC by USB cable.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb devices[/COLOR][/B]
?
whats the response?
thanx for the reply bro...
if i enter "adb devices" it shows:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
list of devices attached
C:\android-win-tools>
Now what shall i do???...please help me out...i m very novice in this matter <to be mentioned that... i had a given factory reset before this!!>
After startup and the two vibrates, what's on the screen?
were you forced to pull the battery at any point?
Sent from my HTC Desire S using xda premium
after the vibration the screen doesn't show anything!! its just pitch dark...
yeah last night i had to pull the battery out as the Red light wont turn off!!
this isnt sounding good!
check out the link in bens signature regarding emmc chips...
The most unexpected happen right now!!!!
i installed the adb tools then plugged in my device to the pc..suddenly it booted up...everything seemed to work perfectly {though the volume increase notification was still bugging me!!!}.
So, i decided to give it a Factory default reset. i went to the settings & clicked the factory default button....it gave me a couple of warnings and wiped all the installed apps. then it started to restart again...!!! AND Here you go ....its stuck again!!!! Back to that old black screen & the red light!!!!!
Please tell me WHAT to do????? plz i m waiting...should i plug it out???
<if i try to boot into recovery mode...it vibrates 4 times the green lights turns on!!>
shariaphobia said:
The most unexpected happen right now!!!!
i installed the adb tools then plugged in my device to the pc..suddenly it booted up...everything seemed to work perfectly {though the volume increase notification was still bugging me!!!}.
So, i decided to give it a Factory default reset. i went to the settings & clicked the factory default button....it gave me a couple of warnings and wiped all the installed apps. then it started to restart again...!!! AND Here you go ....its stuck again!!!! Back to that old black screen & the red light!!!!!
Please tell me WHAT to do????? plz i m waiting...should i plug it out???
<if i try to boot into recovery mode...it vibrates 4 times the green lights turns on!!>
Click to expand...
Click to collapse
Very strange indeed, can you recall any part of the warnings?
Unless the phone semi-boots or can at least be recognised by adb (which yours doesn't) then you can use the HTC ROM utility to re-flash your phone)
Does sounds frightening like a hardware related issue, although it's difficult to tell as it appears to intermittently boot!?
The good thing is if it won't boot then hopefully the service centre won't be able to tell that you S-off'd so may well replace unit or motherboard for you under warranty.
bro ...i m really getting hopeless here!!!!
1. Can u plz tell me the steps if the adb recognizes my set or give me some links so that i can follow....
2. Or tell me the steps to use RUU to flash my set
Anyways thanx a lot for yr time
---------- Post added at 04:20 PM ---------- Previous post was at 03:51 PM ----------
bro...
i've tried the adb devices command again...now it shows this message:
List of devices attached
HT15JTJ05547 recovery
Does it mean anything???
shariaphobia said:
bro ...i m really getting hopeless here!!!!
1. Can u plz tell me the steps if the adb recognizes my set or give me some links so that i can follow....
2. Or tell me the steps to use RUU to flash my set
Anyways thanx a lot for yr time
---------- Post added at 04:20 PM ---------- Previous post was at 03:51 PM ----------
bro...
i've tried the adb devices command again...now it shows this message:
List of devices attached
HT15JTJ05547 recovery
Does it mean anything???
Click to expand...
Click to collapse
Yes that's good news.....Although I'm at work now so bit busy...
Try
Code:
adb reboot recovery
from the PC if it loads into recovery Good!
From recovery try to format the CACHE partition, write what happens?
I'd then say download a wipe script and a safe custom ROM and then load them onto your SD card, ie like LBC Mod v0.6.0
If no errors, then first flash the wipe ZIP file and then the LBC ROM ZIP file using the "install from sdcard/zip file options from your recovery....
Report back any errors...if you're not quite sure of any of the steps then ask questions....I'll check back later...
Nope...if i enter the command adb reboot recovery...its just vibrates twice and nothing comes on the screen (with the red light on).........!!
i guess i have go for RUU process
---------- Post added at 05:52 PM ---------- Previous post was at 05:37 PM ----------
i just remembered one thing....couple of days ago i installed the FOTA updates...has that changed something in my S-OFF or Root????
shariaphobia said:
Nope...if i enter the command adb reboot recovery...its just vibrates twice and nothing comes on the screen (with the red light on).........!!
i guess i have go for RUU process
---------- Post added at 05:52 PM ---------- Previous post was at 05:37 PM ----------
i just remembered one thing....couple of days ago i installed the FOTA updates...has that changed something in my S-OFF or Root????
Click to expand...
Click to collapse
I'm getting out of my depth here....As we don't know what version of ROm you're now running especially if you ran the OTA. There is a possibility that the OTA has removed your custom recovery, S-OFF and root. As as you can't see the HBOOT screen you can't confirm that you're even still S-OFF..
You could try to start to run an RUU as this might tell you want you current ROM version is......
But I'd wait for someone else to provide some more advice...as I don't know what the "recovery" next to your device serial number from adb devices quite means ( I assume it means that your device is in recovery)...
---------- Post added at 01:06 PM ---------- Previous post was at 01:02 PM ----------
google adb yourself and see what safe options and commands of it you can use that will provide you with further information about your phone
hi...
Thanx to ALLAH...may b at last i have found the problem area.
it is the volume rocker!!! somehow the "+" side of the volume rocker is jammed so, whenever i try to boot the device it goes in a recovery mode!!!
But strangely though when I played with the volume buttons and they don't feel jammed at all, the vol. down button is clicking fine, doesn't feel stuck or anything. And if that wasn't bad enough, I tried turning my phone off and on, but when turning it on, it still thinks it's held down so it will only boot into recovery!!!
is there any solutions for it???
shariaphobia said:
hi...
Thanx to ALLAH...may b at last i have found the problem area.
it is the volume rocker!!! somehow the "+" side of the volume rocker is jammed so, whenever i try to boot the device it goes in a recovery mode!!!
But strangely though when I played with the volume buttons and they don't feel jammed at all, the vol. down button is clicking fine, doesn't feel stuck or anything. And if that wasn't bad enough, I tried turning my phone off and on, but when turning it on, it still thinks it's held down so it will only boot into recovery!!!
is there any solutions for it???
Click to expand...
Click to collapse
Well done in discovering the fault
But, I'm afraid that I don't know of any way to disable the buttons, without obviously dis-mantling the case from the unit (which is way over my head) ...
this maybe a daft question but have you tried the command
Code:
adb reboot
(not adb reboot recovery)?
if this does not work you may have to take your device to HTC
Guys, i flashed the GoApk ROM 2.3.5 with Sense 3.0 and everything was fine. Today, i flashed the new Unity v9 kernel after wiping Dalvik cache and rebooted, but now my phone has been stuck at the wite HTC screen for the past 1 hour. The three button reset is not working, neither is the adbreboot recovery command as adb does not detect my device. Please help... I do not want to pull the battery and fry my eMMC.
EDIT: Got into the recovery and restored nandroid backup. Back up and running now. Thanks everybody for their contribution.
enigmaamit said:
Guys, i flashed the GoApk ROM 2.3.5 with Sense 3.0 and everything was fine. Today, i flashed the new Unity v9 kernel after wiping Dalvik cache and rebooted, but now my phone has been stuck at the wite HTC screen for the past 1 hour. The three button reset is not working, neither is the adbreboot recovery command as adb does not detect my device. Please help... I do not want to pull the battery and fry my eMMC.
Click to expand...
Click to collapse
Look in my signature for various links...
Download and extract the adb & fastboot into a directory on your PC. Ensure that you have HTC drivers installed on you PC if not also download and install the link in my signature.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb reboot recovery[/COLOR][/B]
which should take you into recovery, where you'll be able to reflash or restore a nandroid backup from.
What's your hboot.
It's a most recent 2.00.2002
or the older ?
I think it got updated to the most recent one when i flashed the ROM. I tried everything you have suggested. Nothing works...
---------- Post added at 08:18 PM ---------- Previous post was at 08:16 PM ----------
I'm just waiting for the battery to run out so it powers off and then i'll try to boot into recovery again. I thought Unity kernels were compatible with sense roms. Please can anybody help me out here?
No, the newest hboot must be flashed alone.
It's not included in the rom.
You can find it on this thread: GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5
it's a solution maybe
Maybe you have new .2 hboot and kernel is not compatible ?
philos64 said:
No, the newest hboot must be flashed alone.
It's not included in the rom.
You can find it on this thread: GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5
Click to expand...
Click to collapse
Will it help solving the problem ?
So then what should i do now? Will i ever be able to boot into recovery? I have ClockWorkMod recovery.
i dont think that install kernel kill your phone. if you can't access adb or anything you have no other chance as pull the battery.
if something like this me happen,
- i pull battery
- go to recovery
- go to 4EXT menu and wipe system,data and cache as EXT4
- then go to factory reset and install your rom
- restart
@ proxuser: But i do not have EXT4, i have CWM recovery. Can you guide me as to how to do what you sais in your last post please?
---------- Post added at 08:31 PM ---------- Previous post was at 08:27 PM ----------
Also, wont pulling the battery fry my eMMC? i'm scared of that...
enigmaamit said:
@ proxuser: But i do not have EXT4, i have CWM recovery. Can you guide me as to how to do what you sais in your last post please?
Click to expand...
Click to collapse
Have you attempted the suggestions in my earlier post #2?
After following what I suggested, although I'm not the only person to suggest that you attempt to use adb ....you seem to be missing the point or perhaps not understanding?
Follow step in post #2
Then fire up a PC CMD window, go to the directory where adb is extracted to and type the command
Code:
adb devices
tell us what the response is?
---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------
enigmaamit said:
wont pulling the battery fry my eMMC? i'm scared of that...
Click to expand...
Click to collapse
It doesn't matter whether you have CWM or 4EXT they both are similar and perform the same functions.
If you have to pull the battery, READ the first post of this thread
ben_pyett said:
Have you attempted the suggestions in my earlier post #2?
After following what I suggested, although I'm not the only person to suggest that you attempt to use adb ....you seem to be missing the point or perhaps not understanding?
Follow step in post #2
Then fire up a PC CMD window, go to the directory where adb is extracted to and type the command
Code:
adb devices
tell us what the response is?
Click to expand...
Click to collapse
@ben - I tried what you said and your instructions very very clear. But when i type adb devices it just says "List of devices" Thats all... and Typing adb reboot recovery just gives an error with no device connected...
---------- Post added at 08:39 PM ---------- Previous post was at 08:35 PM ----------
@ben : Yours was the first help post that i read and i have tried everything you suggested and i'm down to the last point where i may have to pull the battery. even if i reinsert it after a minute, there are chances of killing mu eMMC, right. That is where i'm stuck currently...
The same issue happened to me last week while trying to flash EXT4Recovery over CWM.. I have pulled the battery and reinserted after few seconds.. And then I was able to boot into the ROM..
http://forum.xda-developers.com/showthread.php?t=1264527
@Nirubhai, can you tell me exactly how you got past the white screen into recovery?
Hey bro, if you do pull the battery, do not instantly re insert it. Re insert about a minute later. Try ADB commands.
You don't need to worry, relax. You're in no trouble at all. A kernel flash is usually harmless.
Sent from my HTC Desire S using Tapatalk
How much was your phone charged?
Around 52%
That'll take a while to run out. Is adb detecting your phone? ADB is probably your best bet.
You'll get into recovery eventually, it's not a question of IF , but WHEN.
I am going to wait the entire night if it takes that... Adb is not detecting my device. Have run out of all options but to wait till it switches off, then connect to charger and try recovery. WHEN i get into recovery, should i do a nand restore or flash another kernel, ext4 or what? Any suggestions willl be a big help...
enigmaamit said:
@ben - I tried what you said and your instructions very very clear. But when i type adb devices it just says "List of devices" Thats all... and Typing adb reboot recovery just gives an error with no device connected...
---------- Post added at 08:39 PM ---------- Previous post was at 08:35 PM ----------
@ben : Yours was the first help post that i read and i have tried everything you suggested and i'm down to the last point where i may have to pull the battery. even if i reinsert it after a minute, there are chances of killing mu eMMC, right. That is where i'm stuck currently...
Click to expand...
Click to collapse
Sorry to hear that, just needed feedback to know what to suggest next.
when you plug charger in does LED light ?
The way I see it you have two options
1)
If LED was lighting when you tried charging phone?
Then you could wait until the battery runs completely flat and the phone turns itself off. Then plug in charger and fully charge the phone before turning phone ON and trying to enter bootloader by pressing VOLUME DOWN + POWER button.
2)
Just go for it and pull it, pull it out quickly leave out for about 30seconds and replace it and try to enter bootloader by pressing VOLUME DOWN + POWER button.
Anyone agree?
Do you have a nandroid backup? If you do, restore that. No need for Ext4 or anything right now.
Yeah ben, thats probably what i would do. I've been stuck on this screen many times, and thats what i did. Pull the battery, and re insert a minute later.
Lots of people are having problems with the Android 4.2 update. They lose root or they can't get back into recovery. So BEFORE you flash 4.2 or if you already did and are having issues. Download this utility I whipped up. It will flash (or reflash) the 4.2 update (Including system, kernel and bootloader). It'll flash the latest 4.2 compatible ClockworkMod Touch Recovery. And then it'll get you all set up to re-root your N7 within the latest CWM. Instructions are included in the README file. PLEASE READ IT!
You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.
If anyone is having any issues and you get caught at the Google splash screen. You can use Power, Vol - to hard shut down the tablet, then Power, Vol +, Vol - to get into the bootloader. From here you can install the factory images from google. Once you're back up and running, you can run this tool to gain root and CWM back.
Updated 11/14/2012: Replaced SuperSu.apk with the latest version designed for 4.2
Updated 11/14/2012 14:41EST: This package will now contain 3 different runme files. One of them will not erase your data, one will erase your cache only and the last one will erase your data and cache. It seems people coming from some roms are having bootloops or hangs because of a lack of data wipe. You can attempt to run the one with no data wipe, but if you run into trouble, try one of the others. Some have made it through with only a cache wipe. See what works for you.
Updated 11/14/2012 16:53EST: Removed full data erase option as I forgot it will erase your SD card and therefor erase the root zip before it gets a chance to flash. There is only 1 runme file now and it will erase your cache, but leave your data alone. If you're having problems, or you want to avoid problems. Erase your data in CWM before you flash the supersu zip included in the package.
For Now - Windows ONLY, Sorry.
Linux version, on the way
Anyway:
Download and PLEASE READ the Read Me!
Saweet
Sent from my Nexus 7 using xda premium
Just trying to make it easy
im on 4.2 already ,can i use this to root?
Thanks for putting this together tucstwo, it was super helpful and easy for a lot of us here
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Ugh. now my device is stuck at the google start screen, and not going anywhere. Android is too complicated sometimes for dumb people like me...
Solange82200 said:
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Click to expand...
Click to collapse
Its booting you in fastboot. just follow the instructions in the window that comes up when you run the runme.bat.
When it boots in fastboot just hit the space bar. It will take a couple times of hitting the spacebar before you reach the CWR stage where you flash the PlaceMeOnYourSDCardSuperSu.zip
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
EDIT: My nexus 7 is connected and has usb debugging turned on.
Hasan10 said:
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
Click to expand...
Click to collapse
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
trusteelfan said:
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
Click to expand...
Click to collapse
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Solange82200 said:
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Click to expand...
Click to collapse
You can run it again if it got stuck. I had to run it twice
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
Hasan10 said:
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Click to expand...
Click to collapse
The Nexus 7 toolkit will put the right drivers in place if you need them.
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh? Or is there a 4.2 bootloader floating around that I can just flash using CWM and save myself the trouble?
Hasan10 said:
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh?
Click to expand...
Click to collapse
It takes it a few minutes to run the process. You should have just waited
trusteelfan said:
It takes it a few minutes to run the process. You should have just waited
Click to expand...
Click to collapse
No I realized it didn't install the fastboot drivers before the process began. So it was actually not able to send the bootloader. Anyways, can you please read my edited post above and advise me with that to do?
EDIT: I went ahead and re-ran the process. Since all drivers were in place, the total process took less than 5 mins, arguably faster than an OTA. Still have all of my data and the goodness of 4.2.
Thanks a lot OP for this great utility.
trusteelfan said:
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Click to expand...
Click to collapse
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
essay708 said:
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
Click to expand...
Click to collapse
I had to wipe my data. It didnt like coming from AOKP
Nevermind, I wiped cache and dalvik cache and it worked for me too.
Everything is good over here. Rooted with twrp instead tho. Anyway something weird is going on with my battery, and yo seem pretty knowledgeable so I thought I'd run it by ya and see if you couldn't shed some light on the issue. Anyway my battery stats are showing that the device isn't awake.. When clearly it is and in the stats it says the screen is even on.. But not awake. Also the screen seems to brighten and dim at odd times idk if that has anything to do with it. But I flashed an ota update.. Bootloader and all. Kept root with supersu. You think something might have been corrupt or something? Here's a screenshot of the issue.. Hmm another issue, whenever I try to take a screenshot.. With more than one app, it takes a pic of an earlier point when I was on twrp getting ready for the 4.2 update. Some really strange things are going on..
Lets make a long story short, i just got my OPO, as an advanced android user i desided to put
ParanoidAndroid 4.6, but before I installed custom bootloader (TWRP) and rooted it. Since i am installing new ROM i did a backup and then i needed to wipe my device, by accident i wiped everything from my phone, including backup and new ROM. I was left with TWRP (It is my 1st android phone without sdcard so i started to panick), then i started it in fastboot mode, to check if I can copy ROM again from my pc, but it didnt work. Then i went to restart options in TWRP and choose restart in recovery mode, then my phone turned off. Apperently it did restart but now my screen is just black and I cant do anything with it. I was holding power button, then with volume up, then with volume down, no result. When i connect it to my PC i hear sound that phone is connected but still nothing is happening. Please help me what should I do. My guess is when i pressed to restart in recovery mode, it wasn't meant to be the custom one, so it tried to open one that dosen't exist. My phone was charged 40% when i was doing that.
Note1: Unknown USB Device (Device Descriptor Request Failed), this is what i get when I check Device Manager.
Many suggestions were made so far none of them help. Hope someone will help me here!
First, TWRP isn't a custom bootloader, it's a custom recovery. The phone can't 'open a recovery that doesn't exist', it opens whatever recovery you have installed at the time. Make sure the phone is powered off (hold power for about 10-15 seconds), then try booting into recovery again (hold power + volume down).
Transmitted via Bacon
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
There is another problem
bigballa said:
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
Click to expand...
Click to collapse
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Only 1 thing
I just need to fix how to find device in adb and then it will be very easy.
Mod Edit: quoted post removed.
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
[/COLOR]
Gapkobob said:
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Click to expand...
Click to collapse
Gapkobob said:
I just need to fix how to find device in adb and then it will be very easy.
Click to expand...
Click to collapse
My friend you're in a bit more trouble than I think you realise you're in. Your device is showing up as QHSUSB_BULK in Windows, which means it's technically bricked. I believed you can save it though, have a look in this thread, you're gonna need to read through it all to find the solution you need. Let me know how you go.
Transmitted via Bacon
Simple driver issue.
The following steps will solve your problem: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
Solved !!!
Solved thx to everybody. http://forum.xda-developers.com/one...een-fastboot-adb-t2835696/page16#post55129486 this helped
Great news.
Transmitted via Bacon
Here is the rundown. I have the d 850 LG g3. Was planning on unrooting phone from towel root and rerooting it using towelroot once I found the mod I wanted. I have the latest version of twrp loaded as well. On my way home from work yesterday I was riding my motorcycle and listening to music, all the sudden the music stops so I pull over to see what happened and look to see that my phone has somehow opened twrp. I get home and try to reboot phone and it loads right back into twrp. I did a backup. Restarted phone to same results. I factory reset phone thinking that would work. NOPE. Straight back into twrp so I plug phone into computer to see what's on it. It appears all my games music LG backup etc is still there's why can't I get out of twrp. Could I have accidentally wiped everything while in my pocket? Can I fix this problem or do i now have a $500 paperweight? Please please folks out there in xda land help me out. I've got experience in rooting with my htc m7 so am familiar with this stuff. Any help would be greatly appreciated. Thanks for your time.
dcm1200 said:
Here is the rundown. I have the d 850 LG g3. Was planning on unrooting phone from towel root and rerooting it using towelroot once I found the mod I wanted. I have the latest version of twrp loaded as well. On my way home from work yesterday I was riding my motorcycle and listening to music, all the sudden the music stops so I pull over to see what happened and look to see that my phone has somehow opened twrp. I get home and try to reboot phone and it loads right back into twrp. I did a backup. Restarted phone to same results. I factory reset phone thinking that would work. NOPE. Straight back into twrp so I plug phone into computer to see what's on it. It appears all my games music LG backup etc is still there's why can't I get out of twrp. Could I have accidentally wiped everything while in my pocket? Can I fix this problem or do i now have a $500 paperweight? Please please folks out there in xda land help me out. I've got experience in rooting with my htc m7 so am familiar with this stuff. Any help would be greatly appreciated. Thanks for your time.
Click to expand...
Click to collapse
Make backup and try repair your system partition with lg flash tools and tot or if you have twrp. Try flash any rom stock bumped
Try this..
dcm1200 said:
Here is the rundown. I have the d 850 LG g3. Was planning on unrooting phone from towel root and rerooting it using towelroot once I found the mod I wanted. I have the latest version of twrp loaded as well. On my way home from work yesterday I was riding my motorcycle and listening to music, all the sudden the music stops so I pull over to see what happened and look to see that my phone has somehow opened twrp. I get home and try to reboot phone and it loads right back into twrp. I did a backup. Restarted phone to same results. I factory reset phone thinking that would work. NOPE. Straight back into twrp so I plug phone into computer to see what's on it. It appears all my games music LG backup etc is still there's why can't I get out of twrp. Could I have accidentally wiped everything while in my pocket? Can I fix this problem or do i now have a $500 paperweight? Please please folks out there in xda land help me out. I've got experience in rooting with my htc m7 so am familiar with this stuff. Any help would be greatly appreciated. Thanks for your time.
Click to expand...
Click to collapse
Somehow your rom partition/system seems to be corrupted. If you want to try and save your data, Please copy the downloaded version of your current rom and dirty flash (flash without wipe) and try to get back into the system. If you do not have your rom in your internal memory, try adb sideload or try to copy it to your external SD card and install from there.
You can also try to copy your stuff over to the external SD card using the file manager in TWRP and then wipe and install your rom.
If none of these wor, you still can flash factory image by process defined in the this thread: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I believe you can still rescue your phone. Please let us know how it went.
I tried flashing a ROM with gaps and rebooted and it still senT me back into TWRP.
Maybe his phone tried to download and install the OTA? Try this also if the above doesn't work. http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
harihacker said:
Somehow your rom partition/system seems to be corrupted. If you want to try and save your data, Please copy the downloaded version of your current rom and dirty flash (flash without wipe) and try to get back into the system. If you do not have your rom in your internal memory, try adb sideload or try to copy it to your external SD card and install from there.
You can also try to copy your stuff over to the external SD card using the file manager in TWRP and then wipe and install your rom.
If none of these wor, you still can flash factory image by process defined in the this thread: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I believe you can still rescue your phone. Please let us know how it went.
Click to expand...
Click to collapse
Will do. Going home in a bit to try it out. Will keep u posted and thanks to everyone who has given advice. Ill be happy to get it back to stock and then starting over from scratch with a good custom from and kernel. Quick question, I tried flashing the custom illusion rom with gapps. Is that rom a bmp.img?
No.. A Zip file.
dcm1200 said:
Will do. Going home in a bit to try it out. Will keep u posted and thanks to everyone who has given advice. Ill be happy to get it back to stock and then starting over from scratch with a good custom from and kernel. Quick question, I tried flashing the custom illusion rom with gapps. Is that rom a bmp.img?
Click to expand...
Click to collapse
The rom is normally a zip file.
If you already tried to flash a rom (other than your current one) I suggest you try the "back to stock" thing that was referred in my last post. If you have all the drivers in place and do the process correctly (preferably from a Windows 7 laptop), Your phone will be burst back to life in no time.. Good luck..!!
harihacker said:
The rom is normally a zip file.
If you already tried to flash a rom (other than your current one) I suggest you try the "back to stock" thing that was referred in my last post. If you have all the drivers in place and do the process correctly (preferably from a Windows 7 laptop), Your phone will be burst back to life in no time.. Good luck..!!
Click to expand...
Click to collapse
Following the steps and just to part where I press volume up and plug into USB port and it said download for a second then jumped to firmware update do not unplug until process is complete. Its been a couple of minutes and in still at zero %
Good..
dcm1200 said:
Following the steps and just to part where I press volume up and plug into USB port and it said download for a second then jumped to firmware update do not unplug until process is complete. Its been a couple of minutes and in still at zero %
Click to expand...
Click to collapse
That is exactly what you want. You are now in download mode. So please proceed to next step (i believe the next step is on the laptop).
But the firmware update hasn't even gotten to 1% yet and I don't know how to get back to download mode. I don't know if unplugging device and trying again will mess it up even more. Device manager didn't pop up on computer either
dcm1200 said:
But the firmware update hasn't even gotten to 1% yet and I don't know how to get back to download mode. I don't know if unplugging device and trying again will mess it up even more. Device manager didn't pop up on computer either
Click to expand...
Click to collapse
Device manager wont "pop up".. you need to pull it from control pannel. Once you confirmed/changed the port to 41, i believe you can pull the usb, wait for 5 sec and put in back in. Follow exactly as instructed in the thread and you should be fine.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Also firmware update starts after the "usb pull" and re-plug in.
harihacker said:
Device manager wont "pop up".. you need to pull it from control pannel. Once you confirmed/changed the port to 41, i believe you can pull the usb, wait for 5 sec and put in back in. Follow exactly as instructed in the thread and you should be fine.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Also firmware update starts after the "usb pull" and re-plug in.
Click to expand...
Click to collapse
I haven't gotten a chance to pull it up. IT goes to download mode and then right into firmware update. I'm looking on control panel for my phone so I can go into port but its not showing up in control panel
dcm1200 said:
I haven't gotten a chance to pull it up. IT goes to download mode and then right into firmware update. I'm looking on control panel for my phone so I can go into port but its not showing up in control panel
Click to expand...
Click to collapse
1) The "firmware update" page is the download mode.
2) Control Panel -> Device Manager -> Ports -> Select LG one -> Port Settings -> Advanced -> look for "Com Port Number" on left hand side.
---------- Post added at 04:32 PM ---------- Previous post was at 04:29 PM ----------
If your device does not show in the Ports section, that means that your drivers are not installed correctly. Did you install the one given in the thread?
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
Try these drivers if you cant find the right one: http://www.koushikdutta.com/post/universal-adb-driver
Yes drivers showed in port. Followed instructions according to LG flashtool and in getting a message saying that lgusb/ parallel lock key is not detected
?
dcm1200 said:
Yes drivers showed in port. Followed instructions according to LG flashtool and in getting a message saying that lgusb/ parallel lock key is not detected
Click to expand...
Click to collapse
At what stage of the process are you getting this error? Please refer to the step number in the "back to stock" thread.
Lg flash tool is saying authentication failed
Re-try.
dcm1200 said:
Lg flash tool is saying authentication failed
Click to expand...
Click to collapse
Again, at what stage did you get the error? Which step?
Did you install the driver i quoted above? If you did in between the process, please pull the battery and try from the beginning if the flash process did not start.
harihacker said:
At what stage of the process are you getting this error? Please refer to the step number in the "back to stock" thread.
Click to expand...
Click to collapse
Step 12 go to LG flash tool and run as administrator.
DLL
dcm1200 said:
Step 12 go to LG flash tool and run as administrator.
Click to expand...
Click to collapse
Did you replace the DLL file in the folder as instructed? Did you give the computer's correct admin password? Are you logged in as an admin in the laptop?
harihacker said:
Did you replace the DLL file in the folder as instructed? Did you give the computer's correct admin password? Are you logged in as an admin in the laptop?
Click to expand...
Click to collapse
I got in