After failing to install CM 10.1 I have custom recovery, CM is just stuck on boot logo, I don't even want it anymore.
Anyway I have made a back up in meanwin, but I moved it to my computer because it was too large, all I need is to copy that folder to my phone but I can't. I can use an sd card but I haven't purchased one yet.
How can I copy the backup folder? I tried the mounting option in custom recovery but it didn't show up in my computer.
Please help! any advice would be greatly appreciated!!
dateacake said:
After failing to install CM 10.1 I have custom recovery, CM is just stuck on boot logo, I don't even want it anymore.
Anyway I have made a back up in meanwin, but I moved it to my computer because it was too large, all I need is to copy that folder to my phone but I can't. I can use an sd card but I haven't purchased one yet.
How can I copy the backup folder? I tried the mounting option in custom recovery but it didn't show up in my computer.
Please help! any advice would be greatly appreciated!!
Click to expand...
Click to collapse
supposing that you have adb file on your pc or you have android SDK installed
boot into custom recovery, connect your phone to pc open cmd and type the following commands (you dont need to enable usb debug for this process):
Code:
adb devices
you must see a serial number
Code:
adb push C:\name of rom.zip or backup /data/media/
supposing that your rom/backup is on C
Code:
adb reboot recovery
once done, go to your phone and install the rom.zip/backup from recovery, reboot.
EDIT : first wipe data and cache with recovery then reboot it may fix the bootloop
EDIT 1: if you find this hard (and it is not, it is good to learn something) you can make the wipe and flash stock firmware
samersh72 said:
supposing that you have adb file on your pc or you have android SDK installed
boot into custom recovery, connect your phone to pc open cmd and type the following commands (you dont need to enable usb debug for this process):
Code:
adb devices
you must see a serial number
Code:
adb push C:\name of rom.zip or backup /data/media/
supposing that your rom/backup is on C
Code:
adb reboot recovery
once done, go to your phone and install the rom.zip/backup from recovery, reboot.
EDIT : first wipe data and cache with recovery then reboot it may fix the bootloop
EDIT 1: if you find this hard (and it is not, it is good to learn something) you can make the wipe and flash stock firmware
Click to expand...
Click to collapse
I learned something new even if I don't need it but thanks
Related
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1781250
follow that guide, will get you back to stock then start again, and dont erase sd card next time! just factory reset to go from stock to CleanROM
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
Put the ROM zip file in your Android SDK/platform-tools directory on your computer. Open a command prompt window, change directories to your Android SDK/platform-tools location (for me that's: cd sdk/platform-tools) and type in:
Code:
adb push <name of ROM zip> /sdcard
Wait about 30-60 seconds until it's done, then flash your ROM. It'll be on the root of your internal storage (/sdcard).
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Nico_60 said:
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
danman132x said:
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Click to expand...
Click to collapse
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
RMarkwald said:
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
yudanjah said:
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
Click to expand...
Click to collapse
You should ask in the kindle fire 2 forums as some advice may be hardware specific.
I everyone,
I was installing a font and by accident caused it to reboot midway install and now my rom won't boot, it just hangs on paranoid logo.
I need to transfer the rom file and gapps although I don't know how to access the file directory so I can transfer from PC to phone in recovery or download mode.
Any ideas? I use clockworkwork mod and dont have option to mount usb.
ps I'm on a mac.
T89 said:
I everyone,
I was installing a font and by accident caused it to reboot midway install and now my rom won't boot, it just hangs on paranoid logo.
I need to transfer the rom file and gapps although I don't know how to access the file directory so I can transfer from PC to phone in recovery or download mode.
Any ideas? I use clockworkwork mod and dont have option to mount usb.
ps I'm on a mac.
Click to expand...
Click to collapse
Use adb sideload
place the rom in the platform-tools folder, wipe, then from recovery select adb sideload then run adb sideload nameofrom.zip
Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
When you are just trying to clear all apps and data for the ROM you are using, go to recovery and just wipe /data and that should be it. This leaves the /system alone so your ROM is still there when you boot. May have to flash gapps again though.
Sent from my Nexus 4 using Tapatalk 4 Beta
BugJuice said:
Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
Click to expand...
Click to collapse
You cant choose the sideload option under the recovery menu? Just do that then connect to a computer and type adb sideload /home/user/romofyourchoice.zip in Linux terminal or windows command prompt. That saved my ass a few times. If he can't do that go into your bootloader download a complete image of stock then use the fastboot command and reflash every partition one by one then once that boots up you can continue from there.
Nexus 4 CyanogenMod 10.1.0
ryaniskira said:
You cant choose the sideload option under the recovery menu? Just do that then connect to a computer and type adb sideload /home/user/romofyourchoice.zip in Linux terminal or windows command prompt.
Nexus 4 CyanogenMod 10.1.0
Click to expand...
Click to collapse
I dumped the rom in the sideload folder and typed adb sideload romname.zip and it says adb devices not found.
BugJuice said:
I dumped the rom in the sideload folder and typed adb sideload romname.zip and it says adb devices not found.
Click to expand...
Click to collapse
I modified my previous post refer to it hopefully you can still do the fastboot flash command. You should be able to find a stock image somewhere unzip the zip file and flash the images with the fastboot flash command (example fastboot flash recovery recoveryfilename.img) just make sure you flash the img files to the right partitions
Nexus 4 CyanogenMod 10.1.0
BugJuice said:
Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
Click to expand...
Click to collapse
What you did in clockwordmod was erase the contents of system, data, cache, and Dalvik cache. If you already have downloaded and copied the ROM you want to the "sdcard", all you need to do is boot into recovery again, select Install, select the zip file that contains the new ROM, and press the power button to install the ROM.
If you have the ROM downloaded but have not copied it to the phone, move the ROM file to the folder on your computer where you installed adb and fastboot. Boot your phone into recovery and select Mounts and Storage then connect the USB cable from the computer to the phone. Confirm that phone shows "Unmount /sdcard/" and "Unmount /system/" or press toggle button to change status as necessary. Open a command prompt on your computer by clicking Start -> Run, typing cmd, and pressing <ENTER>. At the command prompt type cd C:/Android/ replacing "/Android/" with the path name to the folder where adb is installed and press <ENTER>. At the command prompt type adb push ROM.zip /sdcard/ROM.zip replacing "ROM.zip" with the actual filename of the ROM you downloaded and moved to this folder. Now disconnect your phone from the computer and close the command prompt. From the clockwordmod main screen select Factory Reset, then Wipe Cache Partition, and Wipe Dalvik Cache then repeat full wipe twice. Finally, from the clockwordmod main screen select Install ZIP from SD Card followed by Choose file from SD Card, select the ROM.zip file you pushed to the phone's sdcard, and.press the power button to install the ROM.
When clockworkmod reports "Install from SD Card Complete.", return to the main screen and select Reboot system now. The first boot following a fresh installation of a new ROM can take several minutes, just be patient while the ROM initializes the system, applies customizations or updates, and boots to the phone's setup screen.
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
juckeyy said:
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
Click to expand...
Click to collapse
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
gee2012 said:
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
Click to expand...
Click to collapse
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
gee2012 said:
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
Click to expand...
Click to collapse
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
gee2012 said:
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
Click to expand...
Click to collapse
Hmm, couldnt find my adapter. Is there no way to flash in the stock rom with odin?
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Hmm wow seems like a long process but i'll try it.
Thanks!
samersh72 said:
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
Click to expand...
Click to collapse
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
gee2012 said:
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
Click to expand...
Click to collapse
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
thank you my friend
Click to expand...
Click to collapse
Wait one minute bro.
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
Click to expand...
Click to collapse
Hey when I type in adb devies it says mine is unauthorized :/
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
-Edit- also with usb debugging disabled the serialnumber is shown.in recovery.
juckeyy said:
Hey when I type in adb devies it says mine is unauthorized :/
Click to expand...
Click to collapse
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
gee2012 said:
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
Click to expand...
Click to collapse
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
samersh72 said:
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
Click to expand...
Click to collapse
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
juckeyy said:
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
Click to expand...
Click to collapse
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
samersh72 said:
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
Click to expand...
Click to collapse
I did still didnt work. Now I managed to get a ROM into my SD-card so now i'll boot custom recovery and try to install.
lets hope for the best!
Hey again!
Just wanna thank everybody for the help. I solved everything with flashing in stock ROM with odin.
I'll try again tomorrow with other ROM:s
Thanks, Joakim.
had same problem
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
fezz64 said:
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
Click to expand...
Click to collapse
Is it the same with other roms?
Make sure the download is not corrupted.
Wipe data, cache and dalvic after flashing the rom, reboot
sent from my Galaxy
Hi there.
I have a Nexus 4 with a failed root through Nexus 4 Root toolkit.
The toolkit unlocked the bootloader with no problems but it failed at applying SuperSU-v1.45.zip through ADB through CWM
I am pretty certain that this process failed because I did not Enable USB debugging before starting.
So, I think the question I want to ask is: Is it possible to Enable USB debugging so I can apply perform adb sideload SuperSU-v1.45.zip
Do I have any other options? At present the device won't boot into Android OS. The states I currently have are either
1. fast boot mode
and then Recovery Mode -> CWM
2. Just a black screen, the Google logo, and an unlocked padlock
Any pointers would be greatly appreciated
Thanks!
jon.
Why CWM? TWRP is a lot better.
And Android USB debugging has no job in recovery so it isn't necessary if you're sideloading
Oh, and a few extra bits of info:
* I am on a mac
* I am pretty sure it's the adb ruining the party because when I do this:
(null) latform-tools jonwhittlestone$ adb devices
List of devices attached
(null) latform-tools jonwhittlestone$
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
jonwhittlestone said:
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
Click to expand...
Click to collapse
You shouldnt have used a toolkit.
Anyways, i think that you are misunderstanding this. You DO NOT need usb debugging enabled for adb to work while in a custom recovery. Adb works by default in a custom recovery.
I would suggest pushing a rom onto your phone (download a rom on your mac, put the phone into cwm, and run "adb push rom.zip /sdcard/").
After that go back to the phone and choose: wipe data/factory reset, wipe cache partiiton, advanced> wipe dalvik cache. Then go to install zip from sdcard and install the rom that you just pushed.
*Download the newest TWRP .img file from TWRP website
*Rename it to recovery.img to get rid of that long name
*Go into bootloader but don't choose anything (fastboot mode)
*In ADB type: fastboot flash recovery file_location/recovery.img
Sideloading in TWRP is in Advanced menu
consonant edbreach
Chromium_ said:
You shouldnt have used a toolkit.
Click to expand...
Click to collapse
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
jonwhittlestone said:
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
Click to expand...
Click to collapse
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Chromium_ said:
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Click to expand...
Click to collapse
Thanks to both - I've now solved and rooted
I reflashed with the stock google image
Followed androidpolice.com/2013/07/24/how-to-flash-your-nexus-4-to-android-4-3-jwr66v-and-root-it-right-now/
And - got the official TRSW from Gooapps on the Market
Flashed the SU update using the shell script - all details in the link above.
current supersu is 1.65
Can i enable usb debugging via locked phone [pin screen lock]
ok so i have a phone its an lg k5 or in mexico lg q6 a friend has asked me to unlock it with out doing any kind of hard reset or format so he he can access the pictures and other things on the phone since it belongs to his brother who passed away. anyways does anybody know of any way i can enable usb debugging so i can reset the lock screen via ADB ?? or maybe some other way?