I was trying to flash something onto my phone and it didnt go well. It gets stuck at the google sign but goes no further, I can still get into clockwork recovery but when I try to reset to factory image and delete cache etc it has no effect. My computer also wont recognise the phone anymore. Ive no idea what to do, any help would be much appreciated
Fungie89 said:
I was trying to flash something onto my phone and it didnt go well. It gets stuck at the google sign but goes no further, I can still get into clockwork recovery but when I try to reset to factory image and delete cache etc it has no effect. My computer also wont recognise the phone anymore. Ive no idea what to do, any help would be much appreciated
Click to expand...
Click to collapse
you cant "reset" to factory image via your recovery, that is done vua the bootloader and fastboot. you can push a good rom to your phone via your recovery and adb push, then flash it.
f
simms22 said:
you cant "reset" to factory image via your recovery, that is done vua the bootloader and fastboot. you can push a good rom to your phone via your recovery and adb push, then flash it.
Click to expand...
Click to collapse
Thanks for you reply. How can I do this when my computer wont recognize my phone?
Fungie89 said:
f
Thanks for you reply. How can I do this when my computer wont recognize my phone?
Click to expand...
Click to collapse
install the right android drivers onto your computer. itll recognize your phone then. btw, what did you flash?
simms22 said:
install the right android drivers onto your computer. itll recognize your phone then. btw, what did you flash?
Click to expand...
Click to collapse
Ill give it a go. I was trying to install the beats app to my nexus to improve the headphone sound. I've found it a bit weak.
Fungie89 said:
Ill give it a go. I was trying to install the beats app to my nexus to improve the headphone sound. I've found it a bit weak.
Click to expand...
Click to collapse
you should try viper4android, free at the play store. root is needed. it installs its own sound driver, and has controls to set it up. ever since installing it, my n4 has never sounded better.
simms22 said:
you should try viper4android, free at the play store. root is needed. it installs its own sound driver, and has controls to set it up. ever since installing it, my n4 has never sounded better.
Click to expand...
Click to collapse
Will do if I can unbrick it that is!
nitness divites
simms22 said:
you should try viper4android, free at the play store. root is needed. it installs its own sound driver, and has controls to set it up. ever since installing it, my n4 has never sounded better.
Click to expand...
Click to collapse
I tried installing the drivers but it wouldnt allow me. ive included a screenshot of my device manager screen.
Fungie89 said:
I tried installing the drivers but it wouldnt allow me. ive included a screenshot of my device manager screen.
Click to expand...
Click to collapse
wont allow you? error? theres a universal android driver by koush, try installing that one. google it, it should be easy to find.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
theres also this http://adbdriver.com/
simms22 said:
wont allow you? error? theres a universal android driver by koush, try installing that one. google it, it should be easy to find.
---------- Post added at 05:49 PM ---------- Previous post was at 05:48 PM ----------
theres also this http://adbdriver.com/
Click to expand...
Click to collapse
Ive done that but it doesnt find any devices since the comp doesnt recognise the phone properly. ive attached a picture
Is it detected in fastboot mode? You flash a stock image using fastboot...
And you have to be in recovery for adb to work, your phone won't be detected on Google logo :?
Sent from my Nexus 4 using Tapatalk 4
Fungie89 said:
Ive done that but it doesnt find any devices since the comp doesnt recognise the phone properly. ive attached a picture
Click to expand...
Click to collapse
are you in your bootloader when connecting? itll only see your device when in the bootloader(fastboot).
---------- Post added at 06:58 PM ---------- Previous post was at 06:45 PM ----------
http://forum.xda-developers.com/showthread.php?t=2010312
hackergnome said:
Is it detected in fastboot mode? You flash a stock image using fastboot...
And you have to be in recovery for adb to work, your phone won't be detected on Google logo :?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
ok the device has been found when in recovery mode. what is the fastboot command needed? I have the zip file ready
Follow this tutorial http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda app-developers app
Related
Hi guys,
So just received my Nexus 7, the device is rooted and i'm trying to flash clockworkmod to the device.
So far, i've tried both of the toolkits in the developement section, ROM Manager and also flashing the recovery through ADB with the images in the development section too...
With some of them, after selecting recovery from the bootloader, it just stays on the "Google" logo, on other, it just boots up.
The device has no issue's booting, it's just Clockwork that won't boot.
Any ideas please?
Thanks.
SWFlyerUK said:
Hi guys,
So just received my Nexus 7, the device is rooted and i'm trying to flash clockworkmod to the device.
So far, i've tried both of the toolkits in the developement section, ROM Manager and also flashing the recovery through ADB with the images in the development section too...
With some of them, after selecting recovery from the bootloader, it just stays on the "Google" logo, on other, it just boots up.
The device has no issue's booting, it's just Clockwork that won't boot.
Any ideas please?
Thanks.
Click to expand...
Click to collapse
Have you rebooted into recovery after flashing and made it perminent? Otherwise the stock recovery will get flashed back (immediately)..
http://www.androidauthority.com/nexus-7-root-unlock-bootloader-clockworkmod-recovery-cwm-100890/
Usually I temp boot CWM, but today I flashed it on both my GNex & Nexus7. Can easily go back to stock recovery if required...
Thanks for the link mate, hadn't seen that one before and indeed, CWM is now working.
Much appreciated.
SWFlyerUK said:
Thanks for the link mate, hadn't seen that one before and indeed, CWM is now working.
Much appreciated.
Click to expand...
Click to collapse
No problem. When you exit CWM it tries to fix it anyway. Not sure if it just moves the file or what, but the key is to boot into CWM straight after flashing it (I made the same mistake this morning)..
I'm having the exact same issue...so If I re flash the Recovery as Markey Said will I lose the contents of my Internal memory or not?
hope this helps
MassiveDRS said:
I'm having the exact same issue...so If I re flash the Recovery as Markey Said will I lose the contents of my Internal memory or not?
Click to expand...
Click to collapse
if your using cwm i found to boot into recovery you have to have the 7 plugged into your computer with the micro usb..i dont know why but it worked for me..are you using the side bottons to get into recovery..if so plugged the cable in first then try to enter recovery
Easiest way is grab quick boot from the play store and it will let u reboot to cwm.. As above said a pc is needed because of a bug.. U can also do it connected to a phone if u have otg cable
Sent from my GT-N7000 using Tapatalk 2
or you can use ROM manager and reboot from there in cwm
capoooro said:
or you can use ROM manager and reboot from there in cwm
Click to expand...
Click to collapse
That's what I do. Works great.
Sent from my Nexus 7 using xda premium
kuczmad said:
if your using cwm i found to boot into recovery you have to have the 7 plugged into your computer with the micro usb..i dont know why but it worked for me..are you using the side bottons to get into recovery..if so plugged the cable in first then try to enter recovery
Click to expand...
Click to collapse
Yup it is working now Thanx bro
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
capoooro said:
or you can use ROM manager and reboot from there in cwm
Click to expand...
Click to collapse
I already Know that
but I'm asking about the button combo approach because, it is very important ; in case you brick your device and you can't boot it and obviously you cant lauche rom manger
MassiveDRS said:
Yup it is working now Thanx bro
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I already Know that
but I'm asking about the button combo approach because, it is very important ; in case you brick your device and you can't boot it and obviously you cant lauche rom manger
Click to expand...
Click to collapse
You can access CWM through the power, up, down method and choosing recovery mode.... the tablet MUST be plugged in though... at least for me it does. Running CWM6 Touch....
So my nexus 4 is rooted and unlocked. Well actually Im not sure, because after updating with the OTA it seems to have lost that capability. Even though there are SU Binaries still there.
Anyway, I am trying to install Cyanogenmod Nightly, but I cannot get my phone to show up in my computer or Device manager. I have the drivers install and all. I have tried with usb debugging on and off. I have tried in teh Fastboot mode. I have tried after a factory reset.
I'm at a lost as to what I can do....When I try to go to recovery it says "No Command" or something
SO strange,
Thanks
BTW: I have tried two different win7 computers, same result
Bump*
thegreyspot said:
So my nexus 4 is rooted and unlocked. Well actually Im not sure, because after updating with the OTA it seems to have lost that capability. Even though there are SU Binaries still there.
Anyway, I am trying to install Cyanogenmod Nightly, but I cannot get my phone to show up in my computer or Device manager. I have the drivers install and all. I have tried with usb debugging on and off. I have tried in teh Fastboot mode. I have tried after a factory reset.
I'm at a lost as to what I can do....When I try to go to recovery it says "No Command" or something
SO strange,
Thanks
BTW: I have tried two different win7 computers, same result
Click to expand...
Click to collapse
thegreyspot said:
Bump*
Click to expand...
Click to collapse
Is there a way to root from the phone and not use a PC?
Have you tried going into recovery and mounting your device in recovery
Sent from my primoc using Xparent Red Tapatalk 2
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
If that doesn't work then try doing the command in command prompt using your computers emulator sudo su hit enter then do command adb devices if that doesn't show up you can try sudo adb mount and if that doesn't work im out of ideas you can always google it and I'm sure find a way
Sent from my primoc using Xparent Red Tapatalk 2
sbkjuggalo said:
Have you tried going into recovery and mounting your device in recovery
Sent from my primoc using Xparent Red Tapatalk 2
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
If that doesn't work then try doing the command in command prompt using your computers emulator sudo su hit enter then do command adb devices if that doesn't show up you can try sudo adb mount and if that doesn't work im out of ideas you can always google it and I'm sure find a way
Sent from my primoc using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I can't get into recovery cause it says "no command", when I try to get there
Personally I would try downloading Wug's toolkit and doing a full restore that way...
http://forum.xda-developers.com/showthread.php?t=2015469
Try that out
Sent from my Nexus 4 using xda app-developers app
lsbjeep said:
Personally I would try downloading Wug's toolkit and doing a full restore that way...
http://forum.xda-developers.com/showthread.php?t=2015469
Try that out
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I gave it a try and it actually said "device connected" but when it tried to go to fastboot mode, my phone did nothing and it says it couldn't find the phone in fastboot. I went to fastboot myself, and the program still counldnt find it.
Im so at a loss on what to do!!
Kinda desperate here :/ anyone else got a guess?
Need to bump this sorry. Anyone have any ideas of what I can try? I cant RMA this cause the phone is semi rooted (although it says it isnt rooted, i just see supersu and fastbook tells me lock state is unlocked)...
Have tried uninstalling the drivers from within device manager, then unplug your device and plug it back in again?
Sent from my Nexus 4 using xda app-developers app
Yes I have tried that, I have also tried a computer that has never seen a N4 before
Can you install the Windows drivers? Do you see the drivers in the Device Manager?
Make sure you have the latest windows Media Player installed. It installs the MTP service.
Try a different USB cable and other computers.
I accidently deleted everything on my internal storage of my Nexus 4 which had the gapps and custom ROM at the same time wiped out my stock ROM. Is there a way for me to recover? My phone is rooted with Team Win Recovery Project v2.4.1.0. I heard ADB might be able to save my phone but I do not know how it works. My computer cannot find my device whatsoever thus I cannot put any form of ROM onto my Nexus 4.
Go back to stock and start again...
http://forum.xda-developers.com/showthread.php?t=2010312
Recovery mode
EddyOS said:
Go back to stock and start again...
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Does ADB Sideload work in Recovery Mode?
Should do if you're using the latest version of the custom recovery but you also need adb working to use it
EddyOS said:
Should do if you're using the latest version of the custom recovery but you also need adb working to use it
Click to expand...
Click to collapse
Before the incident happened I'm pretty sure ADB connection worked. But now the computer can't even detect this device.
vinnchou said:
Before the incident happened I'm pretty sure ADB connection worked. But now the computer can't even detect this device.
Click to expand...
Click to collapse
Try a different USB port, and check in Device Manager to see what Windows sees the unit as. If ADB/fastboot won't work you're stuck
EddyOS said:
Try a different USB port, and check in Device Manager to see what Windows sees the unit as. If ADB/fastboot won't work you're stuck
Click to expand...
Click to collapse
Well the thing is when I plug it in nothing shows up or says that I've plugged anything in. It sees nothing. So is Fastboot another option?
Get your phone into fastboot and plug it in the PC. If it is seen by the PC then you can go back to stock. If not, you'll have to try another PC to rule out something your end. If that doesn't work either then you might have to RMA it
EddyOS said:
Get your phone into fastboot and plug it in the PC. If it is seen by the PC then you can go back to stock. If not, you'll have to try another PC to rule out something your end. If that doesn't work either then you might have to RMA it
Click to expand...
Click to collapse
Just to clarify, adb won't see the phone but fastboot will. The command "fastboot devices" is what you want. This is for flashing a new OS on the phone.
EddyOS said:
Get your phone into fastboot and plug it in the PC. If it is seen by the PC then you can go back to stock. If not, you'll have to try another PC to rule out something your end. If that doesn't work either then you might have to RMA it
Click to expand...
Click to collapse
Yes! The connection is seen by the computer and it is just recognized as a SAMSUNG Android Phone. So what is RMA? Or do I not need to worry about that? What do I do from here? Maybe there's hope!
fenstre said:
Just to clarify, adb won't see the phone but fastboot will. The command "fastboot devices" is what you want. This is for flashing a new OS on the phone.
Click to expand...
Click to collapse
Why you quoting me? I don't have the problem!
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
vinnchou said:
Yes! The connection is seen by the computer and it is just recognized as a SAMSUNG Android Phone. So what is RMA? Or do I not need to worry about that? What do I do from here? Maybe there's hope!
Click to expand...
Click to collapse
That's fine, it shows the fastboot driver is installed. You can flash the stock factory image by following the guide I posted earlier in the thread. Once back to stock, you can then see if the PC will find the phone in ADB
fenstre said:
Just to clarify, adb won't see the phone but fastboot will. The command "fastboot devices" is what you want. This is for flashing a new OS on the phone.
Click to expand...
Click to collapse
How exactly do I FastBoot? I'm on the Screen that says FASTBOOT MODE. What do I do from here?
EddyOS said:
Why you quoting me? I don't have the problem!
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
That's fine, it shows the fastboot driver is installed. You can flash the stock factory image by following the guide I posted earlier in the thread. Once back to stock, you can then see if the PC will find the phone in ADB
Click to expand...
Click to collapse
Ok Thank you! I will try my best! If Fastboot shows does it mean I have the correct drivers already installed?
vinnchou said:
Ok Thank you! I will try my best! If Fastboot shows does it mean I have the correct drivers already installed?
Click to expand...
Click to collapse
Try running 'fastboot devices' and see if anything comes up. If it does then you're good to go!
EddyOS said:
Try running 'fastboot devices' and see if anything comes up. If it does then you're good to go!
Click to expand...
Click to collapse
So I got stock ROM 4.2.2 back on my phone and the storage is only 5.6GB why is that?
EddyOS said:
Get your phone into fastboot and plug it in the PC. If it is seen by the PC then you can go back to stock. If not, you'll have to try another PC to rule out something your end. If that doesn't work either then you might have to RMA it
Click to expand...
Click to collapse
Why would he RMA it? This isn't Google's fault.
Sent from my iPad 4
Adb push a ROM?
-Sent from Marino's Maxx-
vinnchou said:
So I got stock ROM 4.2.2 back on my phone and the storage is only 5.6GB why is that?
Click to expand...
Click to collapse
There is a bit about that in the back to stock thread under the instructions, it happened to me as well
Looks like you got it working again but another option is using the nexus toolkit v1.63 I think (its under the development thread). The toolkit can push a ROM on your PC directly to the phone and flash via recovery. It only took 5 mins for me to get my phone working when I had this exact same problem.
Sent from my Nexus 4 using xda app-developers app
otariq said:
Looks like you got it working again but another option is using the nexus toolkit v1.63 I think (its under the development thread). The toolkit can push a ROM on your PC directly to the phone and flash via recovery. It only took 5 mins for me to get my phone working when I had this exact same problem.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
But now the OP has the knowledge of how to do it manually, which everyone should know as relying on a Toolkit is lazy
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
kujhawk1977 said:
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
Click to expand...
Click to collapse
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
playya said:
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
Click to expand...
Click to collapse
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
kujhawk1977 said:
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
Click to expand...
Click to collapse
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
CWM will not be able to flash OTA successfully. You need to sideload it through stock recovery or TWRP.
playya said:
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
Click to expand...
Click to collapse
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
kujhawk1977 said:
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
Click to expand...
Click to collapse
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
playya said:
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
Click to expand...
Click to collapse
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
kujhawk1977 said:
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
Click to expand...
Click to collapse
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
I what to do whatever I have to do to fix my problem and I am not sure what that is.
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
Click to expand...
Click to collapse
OK I have adb platform tools. And I have the krt16s.zip Where can I find instructions on how to push the rom over to my phone and flash?
kujhawk1977 said:
I what to do whatever I have to do to fix my problem and I am not sure what that is.
Click to expand...
Click to collapse
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
playya said:
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
Click to expand...
Click to collapse
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
kujhawk1977 said:
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
Click to expand...
Click to collapse
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
playya said:
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
!!!!!!!!!!
So I still have the problem and cannot find a fix. Anyone here up for the challenge?
I was stuck in a bootloop and a failed OTA 4.4 update.
My nexus 4 is rooted and has CWM so yes I know i should have updated manually in the first place, but I didn't. After the update failed, it was stuck in a bootloop.
The next step I did was to side load the update. It ran through the install and at the end when 100% is says Installation Aborted. When my device is rebooted it is now stuck on the screen Google in white font.
Some other notes that MIGHT be related: USB Debugging is NOT enabled, as I can not boot into my device.
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
---------- Post added at 07:37 PM ---------- Previous post was at 07:31 PM ----------
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
No one has answered your question yet. I will.
Edited to say I did find a way to bridge (adb) files over without having USB Debugging selected on the phone.
Updated drivers and used ADB / SDK to move new Recovery and ROM over to my phone using CWM. Never trusting TWRP again
Pull out the battery, reinsert it after 30 seconds and boot the device into CWM Recovery: Volume Up+ Home + Power keys simultaneously.
Go to “Advanced”
Choose “Wipe dalvik-cache”
Now go to “Mounts & Storage”
Choose “Wipe /cache”
Reboot your phone
The bootloop should be gone now. If it still persists, do this.
Boot the phone again into CWM Recovery
Now go to “Mounts & Storage”
Choose “Wipe /data”
Choose “Wipe /cache”
Then reboot your phone.
Now the phone should reboot normally. Next time when you install a ROM, follow the instructions prescribed by the developer. Be more attentive to the warnings before experimenting with any third party ROM or mod. Always ensure what you are about to install is meant for your device.
i did something stupid... lol. was running PA 4.4 rom with no troubles, had a backup as well. in preporation to sell this thing, i restored my stock backup , and noticed there was an update from att. so i decided to try installing it. well it downloaded fine, but when i tried to install it, it rebooted into twrp recovery. now i cant get it to boot into the OS. i tried restoring backup again but it still boots into recovery. any help?
At this point sideload pa 4.4 or return to bone stock they are described in the forums clearly.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
At this point sideload pa 4.4 or return to bone stock they are described in the forums clearly.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
i am trying to return to bone stock, but i cant get it to boot in to download mode? it still boots into recovery? can you elaborate or point me in the right direction of how to sideload ?
ssreynolds said:
i am trying to return to bone stock, but i cant get it to boot in to download mode? it still boots into recovery? can you elaborate or point me in the right direction of how to sideload ?
Click to expand...
Click to collapse
To get into dl mode....turn off the device....then hold ONLY the volume up button while putting in the usb cable...it will go into dl mode.
MalignantQuechnitlan said:
To get into dl mode....turn off the device....then hold ONLY the volume up button while putting in the usb cable...it will go into dl mode.
Click to expand...
Click to collapse
thanks for the reply... i know how to do it, but its not working because i screwed my device up by trying to insall an ota update with a rooted device and a custom recovery. so my only option now is to sideload, which i am working on... hope it works...
cant get adb to recognize my device, maybe because i dont have usb debugging enabled? which i cant enable because icant boot into os... what do i do to get this thing working again? i have android sdk tools installed
Omg I can't believe tons of people are having same problem, ok here u go stock lg drivers don't seem to help pc recognize phone in recovery mode what I did was downloaded pdanet on pc and connected phone to pc in recovery mode and then opened pdanet in pc and installed lg drivers through it and then my pc recognized my phone as adb sideload when adb was run hope it helps you too.
Sent from my LG-D800 using xda app-developers app
I had the same thing happen today, couldn't get into download mode. I followed the fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2477595 and it worked great.
He has links in that window to the specific file to flash.
lingarajug said:
Omg I can't believe tons of people are having same problem, ok here u go stock lg drivers don't seem to help pc recognize phone in recovery mode what I did was downloaded pdanet on pc and connected phone to pc in recovery mode and then opened pdanet in pc and installed lg drivers through it and then my pc recognized my phone as adb sideload when adb was run hope it helps you too.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I tried this, along with everything else, and my phone is still stuck in a boot loop. I cannot enter download mode. I was rooted with custom recovery, but i could never get the recovery to work. I tried to update to the OTA (i know, i know) and it killed the phone. Now when I connect it nothing happens other than a bunch of drive popups asking if i want to format. No download or recovery mode. only the LG logo screen and then a quick flash of the "Secure booting error Error: Boot Certification Verify!" screen, and nothing else since.
The main issue is that i cannot get my phone to be recognized by the computer for any type of reflash. If I could get into download mode, I could handle it from there. I hope I don't have to buy a new phone. Im not sure how verizon would feel about it if I took it back to them and it shows as rooted.
Can u at least get into twrp recovery using key combination
Sent from my LG-D800 using xda app-developers app
lingarajug said:
Can u at least get into twrp recovery using key combination
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
No, I cant get to recovery mode either. I think this is a hard brick. I've only had it for one day. Something told me not to mess with it.
Roninceo said:
No, I cant get to recovery mode either. I think this is a hard brick. I've only had it for one day. Something told me not to mess with it.
Click to expand...
Click to collapse
hei.connect to pc you can see a lot of drive to format?sorry my poor english
来自我的 Galaxy Nexus 上的 Tapatalk
pageniao said:
hei.connect to pc you can see a lot of drive to format?sorry my poor english
来自我的 Galaxy Nexus 上的 Tapatalk
Click to expand...
Click to collapse
Yes,
When I connect it to my computer I see a large list of drives to format. the messages keep popping up from G: to V:
Roninceo said:
Yes,
When I connect it to my computer I see a large list of drives to format. the messages keep popping up from G: to V:
Click to expand...
Click to collapse
maybe i can help you.
can you see a new device called "QHSUSB_DLOAD" on PC "device manager" when you connect your phone to pc?
来自我的 Galaxy Nexus 上的 Tapatalk
pageniao said:
maybe i can help you.
can you see a new device called "QHSUSB_DLOAD" on PC "device manager" when you connect your phone to pc?
来自我的 Galaxy Nexus 上的 Tapatalk
Click to expand...
Click to collapse
Mine says "QHSUSB_BULK"
see this
http://forum.xda-developers.com/showthread.php?t=2477595
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
see this
http://forum.xda-developers.com/showthread.php?t=2477595
and from chinese
http://bbs.gfan.com/android-6728131-1-1.html
pageniao said:
see this
http://forum.xda-developers.com/showthread.php?t=2477595
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
see this
http://forum.xda-developers.com/showthread.php?t=2477595
and from chinese
http://bbs.gfan.com/android-6728131-1-1.html
Click to expand...
Click to collapse
Ive seen the pages. Thanks for the help. I cannot get into recovery mode and unfortunately I can't read Chinese.
i dont know if you have tried this but i hear it works. it didnt for me, i keep getting a no memory error but if you get it to work can you please let me know how http://forum.xda-developers.com/showthread.php?t=2451696
on chinese .this problem so easy.
来自我的 Galaxy Nexus 上的 Tapatalk
this worked for me, and will work for those of you who are stuck in recovery boot loop... this is caused from installing an att update on a rooted device with a custom recovery and or rom. so heads up, if your rooted and you have a custom recovery and or a custom rom, NEVER install a OTA update!!!
so folow the instructions in the link, basically while in twrp, you use the amazing terminal emulator feature to type in the foillowing command, and viola! your phone will boot into the OS!!! make sure to type it in exactly as shown , with spaces and all... good luck!
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
http://forum.xda-developers.com/showthread.php?t=2451696