Okay, So obviously Im new but I need some help. I've got my phone rooted but I can't get the recovery image part down. I have followed all the steps in the threat for rooting.. My computer recognizes my phone but wont update the driver's from SDK. It say's the driver's are up to date. When I put my phone into recovery mode the only option is to open update.zip which is not even on my SD.
Any help would be greatly appreciated I've been at this for hours.
are you sure your phone is in USB Debugging mode when plugged into your PC?
Settings > Applications > Development > check USB Debugging
do you remember doing this step from your PC?
** adb push recovery.img /sdcard ** (via command prompt)
i followed the directions here originally, and everything worked flawlessly!
http://forum.xda-developers.com/showthread.php?t=647707
Related
I'm having problems Rooting my Nexus One and would be extremely greatful if someone could help me. I got my Nexus One directly shipped to the UK, I am using Windows 7 Ultimate 64bit.
Here's what I've been doing;
I checked 'about' screen and saw it's ERE27 on my N1.
1) I download Superboot for ERE27 - download MD5: 19d302e1bcb18932f009d2a36a3d688f and extracted it to directory (C:\)
2) Turned off phone then plugged in the USB to the N1 (sound on my Windows 7 confirmed the USB connection was made)
3)I I put my N1 in bootloader mode - Turn off the phone then press and hold the trackball to enter the bootloader.
4) I double click 'install-superboot-windows.bat' extracted file on my pc.
BUT then Command Prompt pops up and I get - C:\Users\Bukhtiar\Desktop\1.0-ERE27-nexusone-superboot>fastboot-windows.exe flash boot boot.ERE27.superboot.img
< waiting for device >
After that nothing happens, please could someone help me with a step by step guide as I am new to this.
Many Thanks
You need the USB drivers for the nexus (http://djdoprkngutub.cloudfront.net/usb_driver.zip)
Also, did you unlock the bootloader? You didnt mention it
You need to download the Android SDK and run "Fastboot OEM Unlock"
Do I need to have the phone connected while downloading the Android SDK? Sorry about the Q's but I'm new to all this.
Follow step 1 and 2 in this link
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
then do your superboot step that you have mentioned.
Afterwhich, your phone is unlocked,has a new recovery img, rooted and ready for flashing of custom roms.
Worsty said:
Follow step 1 and 2 in this link
androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
then do your superboot step that you have mentioned.
Afterwhich, your phone is unlocked,has a new recovery img, rooted and ready for flashing of custom roms.
Click to expand...
Click to collapse
I downloaded the Android SDK folder and downloaded the files within it then I followed the links instructions....as follows;
# Reboot phone into fastboot: Power off device and hold down trackball while powering back on. (The fastboot screen is the one with the Androids on skateboards)
# Open a command prompt and navigate to your Android SDK tools folder.
# Type ‘fastboot devices‘ to make sure your phone is recognized.
I opened Command Prompt and navigated to the Android SDK tools folder but I get nothing coming up when I typed ‘fastboot devices‘ nor any message saying my phone is recognized, except in 'Fastboot USB' the phone screen.
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
tparnet said:
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
Click to expand...
Click to collapse
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
svs57 said:
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
Click to expand...
Click to collapse
Thanks svs57 for the quick reply.
Would you mind elaborating a bit more? I am an IT guy but by no means a developer. When I boot into recovery is the phone supposed to show up in My Computer via MTP or PTP? The phone is not showing up as a device. Or am I supposed to use adb commands to pull the files down?
When I go into recovery and run the "adb devices" command now I get what appears to be a serial number followed by the word "unauthorized". I rebooted and went into recovery mode again this time tried "apply update from ADB". When I try using either the adb push or adb pull I get "error: closed"
Thanks again for the help.
You have to use latest version of adb. Then you can login to phone via adb and find file you want to backup. Then use "adb pull" to get file to PC.
If you have custom recovery you also can make backup you data using recovery.
Also you can flash the same ROM you have without wipe data.
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?
Hi, I accidentally formatted my phone yesterday night. Trying to flash the factory image from command prompt using this guide http://forum.xda-developers.com/showthread.php?t=2010312 but I am stuck on Google logo and cant enable the USB debugging mode under settings. I think i did install the driver using Root Toolkit as it shows under device manager but toolkit says adb device not found (see attached).
Please advise how can I bring back my phone to normal.
vineet381 said:
Hi, I accidentally formatted my phone yesterday night. Trying to flash the factory image from command prompt using this guide http://forum.xda-developers.com/showthread.php?t=2010312 but I am stuck on Google logo and cant enable the USB debugging mode under settings. I think i did install the driver using Root Toolkit as it shows under device manager but toolkit says adb device not found (see attached).
Please advise how can I bring back my phone to normal.
Click to expand...
Click to collapse
Boot device into boot loader and in the toolkit tick the current status as "soft-bricked/bootloop" and do a "back to stock"
*hint* You don't need ADB; you need fastboot.
Have, same issue, but in bootloader mode, windows not seen device.
Only what I have chance to fix it, write some from usb-otg thru twrp?
In download mode too several computers with different cables not see device. Only one pc with windows xp reconize unkown device with pid vid 0000
So I deleted everything in my phone, including the Rom I wanted to flash (smart, right?) and all I have is TWRP Recovery mode and Download Mode. When I put my phone into any mode, my PC does not recognize it and I therefor cannot fix it... I've tried it on three computers with downloading and updating the drivers. The first time it works after installing and updating the drivers, but when I put it in the second time it does not work. I need to unplug my phone in download mode while doing the LG program, and the computer won't recognize or find my phone. All help is greatly appreciated and thanks to repliers in advance
Day 2 of not having a phone: I can't do this xD I need to fix it somehow, if anyone can help me please do
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
x714x said:
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
Click to expand...
Click to collapse
Tried that and it would say "device not found." and other error codes. One time I was able to load my device onto the computer and after it completed the CM 11 transfer it stopped. I may have to order an OTG cable or something...