Hi,
I was going to install a ROM on my Nexus, so I made a backup and wiped EVERYTHING. Including the SD card so now in clockworkmod
it can not mount the SD card, I cannot mount it to my computer... I am shaking and my hands are cold... I cant flash any rom HELP NOW!!!! ((((
thanks
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
nodstuff said:
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a factory image please tell me how'd I do that in fastboot! (only if they had a begging at knees thing)
ok i will write you some step by step functions to follow in order to get yourself a rom onto your device
Info that is Needed!
Do You Already Have ADB functioning on your Computer
If Yes - Skip to Step 2
If No Proceed from Step 1
----STEP 1----
install the ADB drivers for your device
im going to assume you have a windows machine here so the followthrough will be for windows (i use Win7 but it should be the same)
BOOT YOUR DEVICE INTO RECOVERY WHILE PLUGGED INTO YOUR PC BUT DO NOT CLICK ON ANYTHING
1. Download These Google Drivers for Nexus Devices http://www.themoviedb.org/movie/15092-crank-ii-high-voltage
2. extract the folder
3. press the start button
4. right click on "Comptuer" or "My Computer (XP)
5. Click on Manage
6. in the new window press "Device Manager" on the left
you should see in the tree on the right (a device with a yellow exclamation mark ! probably called nexus)
7. right click it and press update driver software
8. press browse my computer for driver software
9. press let me pick from a list of device drivers on my computer
10. press have disk
11. press browse
12. on the new window navigate to the folder you extracted earlier and select the android_winusb.inf
13. press ok
14. there will either be 1 or 2 options to choose - click Android Composite ADB Interface and then press next
15. tick always trust software from google inc. and then install
your device should now have ADB capablilities
Proceed to step 2
----STEP 2----
this will use adb to push a file to your device while it is in recovery mode which you can then flash
1. Download This - http://www.mediafire.com/?50baad8rykng2j0
these are adb & fastboot binaries which will allow your pc to send files to your nexus via ADB
2. extract the downloaded archive to somewhere easy to remember ( i suggest C:\fastboot )
3. rename your downloaded custom rom to rom.zip (for simplicity) and copy it to the extracted directory (the one with adb.exe & fastboot.exe)
4. bring a command prompt to this directory
- in the directory you extracted (c:\fastboot) hold shift and right click in a blank area of the main window
- click "open command window here"
or
- Windows Key & R
- in the new box type cmd then press enter
- type cd c:\fastboot (where c:\fastboot is the directory where you extracted)
now to push it over
5. in the cmd window type adb devices and make sure your device is listed
your should see something like
list of attached devices
XXXXXXXXXXXXXXXX Recovery
where XXXXX is your devices serial number
6. in your cmd window type adb push rom.zip /sdcard/
this will take a while to complete but once it is down go back to your device and try to install a rom as you usually would
you should see the file in your internal memory to install now
^^ I was too slow!
First install the android SDK (Google it) then you need to put fastboot in your path you need to open my computer, system properties, advanced system settings, environment variables button at the bottom, then in the bottom window scroll down til you see find path and edit it and add the path to the android SDK and in particular the platform-tools folder.
So if you download the android SDK to your C drive, the path you will be adding will be like ";C:\android-sdk\platform tools" (note the semi colon at the start, important to separate entries)
Once the path is set up you can use fast boot in cmd just by typing fastboot xxxxx rather than typing C:\android-sdk\platform-tools fastboot xxxxx every time.
So next thing is to extract the images to somewhere.
Inside the zip is another zip called image-nakasi-jzo54k,
unzip that til you have .IMG files, system.img, boot.img etc.
then once they are extracted you use cmd to CD to that folder where you have the images and you can start to flash them.
fastboot flash system system.img
fastboot flash boot boot.img
You could just use flash-all.bat but and that will flash them all automatically but will wipe your internal SD.
Sent from my Nexus 7 using xda premium
If you JUST read that, I figured it out, and if I can flash all the partitons correctly, I will punch the thanks button.
cburk01 said:
yay new problem
Ok, so I unzipped it, extracted the thing inside, but it was it a weird format Windows recognized as "file". So, I added .zip to the end. WinRAR opened it, I saw the files, began to extract when an error popped up about the archive being damaged. WTF.
Click to expand...
Click to collapse
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
nodstuff said:
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Now I REALLY DO have a problem. I flashed boot.img, system.img, userdata.img, everything to the right partitons and still have a problem. Boot loop. Sticks on Google logo. Why? I did everything right. I even tried fastboot boot boot.img, no luck. I saw some people having boot loop problems, too on 4.1.2. So now, until you reply, I am going to try a custom kernel. Scratch that I'm using ToolKit to download and install 4.1.1.
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
nodstuff said:
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*facepalm* with the SD I already wiped that before I flashed. And I didnt run flashall.bat or what ever its called so I am going in to try that. Ran flashall got some weird radio flashing error so now continuing with ToolKit.
Flash-all.bat just automatically flashes all the images by running one command, it simplifies the process.
It just isn't ideal if you wanna keep your SD contents.
that's why you flash images separately, so you don't flash userdata.img but since you already wiped it then you're good to go.
Sent from my Nexus 7 using xda premium
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
cburk01 said:
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Click to expand...
Click to collapse
Your backup is most likely gone, its stored on the SD card and that is wiped. Unless you have it on your computer, then you are all good.
Glad its back to life and now you know how to fix it if anything goes wrong.
What you learned today is very valuable to know.
It's nearly impossible to kill a nexus device (from a software perspective)
Sent from my Nexus 7 using xda premium
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
cburk01 said:
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
Click to expand...
Click to collapse
Update first
Sent from my Nexus 7 using xda premium
Yes, I have my backup on my Macbook (running Windows 7). Thanks for all the useful advice. lol about the Nexus devices are hard to kill thing, I imagined a cockroach. And about the valuable lesson thing, I learned fastboot commands and adb stuff all when I was messing with (then soon after fixing) my HTC EVO 3D. Oh, I love XDA. Thanks again.
-cburk
Related
OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root
Below is a great guide to rooting, from several sources, (mostly taken from pingvinen's "An Idiot's Guide to Flashing the Xoom" and a guide by publicanimal. and I hope it helps. You can find the links to all of the files referenced below in the Xoom Heaven thread (thanks StrifeSoldierVII!)[/I]
(New thread in General Section by Jack207407 will have all the updated links for flashing
http://forum.xda-developers.com/showthread.php?t=1443110
One Stop For ROM's, MOD's, and Root Wifi-Only and 3G/4G Models)
"What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and don't try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned.
HERE'S THE USUAL DISCLAIMER--I AM NOT RESPONSIBLE FOR ANY HARM THAT MAY COME TO YOUR DEVICE IF YOU FOLLOW ANY PART OF THIS GUIDE--ANY RISK IS ON THE USER!
I strongly recommend you to read the entire guide before trying. In fact, read it twice to ensure that you have understood everything. If there is weird stuff that you don't understand, don't hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but no one (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
Just a note before we begin: the different Xoom. Models that are able to use this guide are the following:
MZ600 - stingray_cdma - Motorola US 3g Xoom (technically this device is stingray as well, but I will be using stingray_cdma as the two devices have incompatible software)
MZ601 - utms_everest - Motorola EU 3g Xoom
MZ602 - stingray - Motorola US 4g Xoom
MZ604 - wingray - Motorola Wifi Xoom
(thanks solarnz!)
___________
Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity) 2. Install Java SDK and Android SDK tools (for adb and fastboot commands) 3. Unlock the device for flashing (allowing replacement of recovery and boot images) 4. Install a modified recovery image (ClockWorkMod recovery for Android) 5. Root the device (Allow r/w access to the device filesystem) 6. Flash a kernel that supports overclocking etc.
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows PC. Windows 7, Mac and Linux users will probably have to do some steps differently.
1.0 Install the latest Motorola USB drivers
The installation file can be found at: http://developer.motorola.com/docstools/USB_Drivers/
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2.0 Installation of development software
Android SDK and Java SDK need to be installed. You can find the installation kits here.
http://developer.android.com/sdk/index.html In case you can't find fastboot.exe, look for it here (thanks to jerrycycle): http://forum.xda-developers.com/showpost.php?p=19546334&postcount=5
Update: you could also just install the adb fastboot pack here:http://www.android.net/forum/downloads.php?do=file&id=67
http://www.oracle.com/technetwork/java/javase/downloads/index.html
2.1 Install them as any other software, making an Android SDK folder on C/.
2.2 Make sure that all the files you need are in the Platform Tools folder (fastboot, recovery image file and so on). Copy any files in the Tools folder to the Platform Tools folder if necessary. Note: If the Android SDK complains that the Java Dev Kit can't be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
(Warning: Never put any zip files in your Platform Tools folder. Flashing zip files through fastboot will cause very serious problems. Zip files must be flashed from the external micro SD card through CWM recovery on the Xoom...we'll get to that later.)
2.3 Test that ADB and FASTBOOT works. You should open a command window by right clicking in your Platform Tools folder where all of your files are, plug in your Xoom to your computer with your Motorola cable (it may not work with a generic cable) and write 'adb devices'. Your Xoom should now be listed. Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom.
Optional: Those that want to be able to access adb from any where on their computer, here's a tip from scsa20: "For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon ().
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%Sy stemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\ System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
It's long but do you see the android stuff there at the end?"
Update: xda poster Mandelbrot Benoit suggests an alternate adb setup, here: http://forum.xda-developers.com/showpost.php?p=18072572&postcount=50
If your windows computer doesn't see your Xoom, consider this (Originally Posted by AngryBulleteyeTruth):
When the xoom does not show up on PC it may be the problem of.... windows media player!
Xoom uses drivers of WMP to communicate with PC. If someone does not have the newest WMP drivers it will not show up and you can see xoom device in the devices tab on PC having an exclamation mark.
So the solution is to download and install Windows Media Player 11. It has worked for me.
--------
OK. Now that you are set up, it's Showtime! Take a deep breath...
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to secure important data before you start. (It will also void your warranty, so you still have time to go back.)
3.1 Power up and start the Xoom.
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode.
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal. Don't bother to do any setup at this time, just make sure that USB debbuging is checked in settings, and now go on to step 4
4. Install recovery image (CWM) UPDATED 4/19/12
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/showthread.php?t=1604014 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
Important: At this time, make sure you have a good (known to be working) microsd card in your sdcard slot in your Xoom. Reboot the Xoom with the sdcard in the slot to make sure it's mounted.
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery eos-recovery-r6.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
UPDATE(12/28/11) Since putting this guide together, Motorola has issued a number of Over-the-Air (OTA) updates that have complicated the process of flashing the Clockawork Mod recovery, so if you have accepted any OTA updates, please read the following, which describes each step (http://forum.xda-developers.com/showthread.php?p=26009191#post26008083) (Thanks to Landorin.)
(If you have root and want to remove these files, remove or rename /system/etc/install-recovery.sh with something like root explorer. You can then flash your custom recovery through fastboot again.)
For those of you that get stuck with some error like 'device not recognized' poster Madjinj gives the following advice:
1) Be sure that you have your adb folder in the root of C drive directly and be sure that you are in adb folder in command prompt program (CMD in Windows machines) i.e by typing "cd c:\XXX" where XXX is the name of adb folder in your machine.
2) Be sure that you type "adb reboot bootloader" in comand prompt to activate adb program. if the problem persists, try typing "fastboot reboot" then after reboot type "adb reboot bootloader" in command prompt program.
3) Use the USB cable that came with your Xoom (some cables are not good in flashing for unknown reason..!!
4) make sure that you activate USB debugging mode.
5.0. Rooting the Xoom
The Universal Xoom Root zip file from solarnz is located here: http://forum.xda-developers.com/showthread.php?t=1242241
5.1 You need to transfer the Universal Xoom Root zip file to a working external micro SD card. You can do this on a computer or cell phone, but the Universal Xoom Root zip file must be located in the root directory of the micro SD card.
5.2 Insert the now prepared SD card in the Xoom.
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option.
5.4 Select 'Install ZIP from sd card.'
5.5 Select 'Choose ZIP.'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install any app requiring root and start it. If the rooting was successful, then the app should request superuser permission and you should be able to grant it without any problems.
6. Flashing a new rom or kernel...(e.g. Tiamat Moray Rom and/or Odachi Kernel). Look in the Xoom Heaven thread or in the Development section of this form for all of these files.
6.1 This step is identical to 5, but swap out the ROOT zip for the ROM or KERNEL zip. For simplicity, you may want to prepare the micro SD card with both zip files at the same time in step 5.1..."
------------------------
This is still one of the best explanations of how to use adb and fastboot to unlock and root the Xoom and install a custom recovery, etc, and doesn't deserve to buries on back pages of this forum. Hopefully, the step-by-step nature of this guide will help those of you that have limited experience with this kind of tinkering.
Oh, and please feel free to correct any errors or omissions. As I said, it came from several sources and needed to somewhat updated.
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
fastyan said:
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
Good luck! Let us know how you make out and if anything needs to be clarified.
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
fastyan said:
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
Click to expand...
Click to collapse
Check to make sure that your file download is good, and that you are typing it's name correctly. Better yet, you could rename the file "recovery.img" and that will make it very easy to get it right.
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
When you're in the bootloader, you won't be able to access the SD Card or anything of that sort and adb won't work, in stead, when you're in the bootloader, you're switching over to fastboot. I'm sure if you type in fastboot devices you'll see your xoom listed.
Thank you for the reply and that's one thing sorted but any idea why its telling me "cannot load recovery"? I have tried renaming it and downloaded the recovery file 4 times incase that was wrong but still no joy :-(
I have done this all before on my phone and never had a problem so I must be missing something but f$*@ed if I know what?
Thanks again for your help though.
Sent from my Desire HD using xda premium
Just had a thought. Could it be that the XOOM hasn't actually unlocked, would that cause it to not load? Is there any way to check if its unlocked successfully? Although I did try it twice before?
Sent from my MZ604 using xda premium
Once you got it in the bootloader, you gotta make sure you do fastboot oem unlock, press volume down then up, press volume down again then up again, and let it format and reboot.
If it's already unlocked, you'd get a message telling you so (generally).
Then when you go to flash the recovery, make sure that the recovery image is in the folder where fastboot is and type in fastboot flash recovery recovery.img (if I remember the syntax that is, I'm at work and don't feel like scrolling up or going into the root guide to confirm xD ).
fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium[/QUOTE
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
okantomi said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote.Oof course the cwm recovery img.. goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
With the way I have my system setup, I can run adb and fastboot wherever I am
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
scsa20 said:
With the way I have my system setup, I can run adb and fastboot wherever I am
Click to expand...
Click to collapse
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
fastyan said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
Click to expand...
Click to collapse
If, as you follow this guide, you find any explanations that are not clear or if you think of a step to take or something else that might improve the guide, please post it and we can add it in. It's been almost 6 months since I've unlocked and at least a couple of months since I've had to use adb, so I'm sure I've forgotten some things. Those of you whose experience is fresh can give really good advice. That's how this guide was originally written, by pingvinen, right after he had gone through a grueling rooting process.
okantomi said:
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
Click to expand...
Click to collapse
For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon (;)).
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
Click to expand...
Click to collapse
It's long but hey, see where the android stuff is near the end?
@Okantomi:
We all have learned some things from trial & error (eg.the sk cannot detect java dev kit)
i could only flash recovery after renaming it to recovery(do not forget to add.img in cmd while flashing).also the official motorola name recovery as same.
after downloading sdk and updating to platform tools i have kept a zip in safe location so that i do not need to download again platform tools if i install sdk fresh
initially knowledge was scattered now it is at one place.
right now testing steady hawkin's kernel and new recovery
btw good signature pic.
Ok so another night has gone and still can't get recovery on!! Tried re unlocking the XOOM and every time it comes up with "cannot load recovery.img" I tried installing everything on my laptop and went right from the start and getting exactly the same thing!
Starting to think im never gonna get this sorted now :-( just feels like the XOOM isn't unlocking? Every time I go through the unlocking process it never states that its already unlocked? Is there any way I can check that it is unlocked?
Please help im losing the will to live now lol
Sent from my MZ604 using xda premium
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
scsa20 said:
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
Click to expand...
Click to collapse
Not getting any error message it just says "cannot load recovery.img"
I have tried with and without the .img and always the same?
Tried going through the whole process again on my laptop incase I had missed something but exactly the same.
When I unlock it I follow the onscreen instructions and at the end it says its complete before it reboots. Then I turn on usb debugging again and reboot bootloader all ok but won't let me load the new recovery?
Normally I would just say it wasn't meant to be and leave as it is but I wont be beaten on this so I'm purposely not installing anything on it till its done. Any ideas apart from bringing it round yours lol ;-)
Sent from my Desire HD using xda premium
I am trying to root my new Nexus 4 and I am stumped. I am trying to follow efrant's instructions: http://forum.xda-developers.com/showthread.php?t=2010312
I successfully completed part D and now am trying to work through part E. I am stuck at step 3 of E: I downloaded SuperSU v 0.98 (is that really the one to get?) and I'm supposed to put that in /sdcard. Where is /sdcard? There is no SD Card in a Nexus 4. Is this a hidden folder somewhere? Do I have to make it? How can I see that folder? I am using a Mac and the Android File Transfer program window shows no sdcard folder anywhere.
Also: Why does another unlock guide talk (http://forum.xda-developers.com/showthread.php?t=2018179) about pressing "Build Number" seven times? Why doesn't efrant's guide mention this?
I don't follow this part at all. How do I put that damn file where it needs to be?
Just download the N4 toolkit. Will do everything you want.
Toolkit
Doggonit said:
I am trying to root my new Nexus 4 and I am stumped. I am trying to follow efrant's instructions: http://forum.xda-developers.com/showthread.php?t=2010312
I successfully completed part D and now am trying to work through part E. I am stuck at step 3 of E: I downloaded SuperSU v 0.98 (is that really the one to get?) and I'm supposed to put that in /sdcard. Where is /sdcard? There is no SD Card in a Nexus 4. Is this a hidden folder somewhere? Do I have to make it? How can I see that folder? I am using a Mac and the Android File Transfer program window shows no sdcard folder anywhere.
Also: Why does another unlock guide talk (http://forum.xda-developers.com/showthread.php?t=2018179) about pressing "Build Number" seven times? Why doesn't efrant's guide mention this?
I don't follow this part at all. How do I put that damn file where it needs to be?
Click to expand...
Click to collapse
When you plug the phone into the computer /sdcard is the folder that comes up. Just place it in there.
Sent from my Nexus 4 using xda app-developers app
DO NOT USE TOOLKITS. Especially if you're new to modding.
That's like saying, I want to overclockmy computer. Just give me a toolkit where I can one click and overclock my computer.
Read more here http://forum.xda-developers.com/showthread.php?t=1469909
Do it the proper way and download ADB drivers
http://forum.xda-developers.com/showthread.php?t=1514942 (enable USB debugging)
set up ADB environment
adb reboot bootloader
fastboot oem unlock
unlock bootloader on phone
download clockwork recovery or TWRP (i suggest TWRP)
put the .img file of recovery into your /platform-tools/
fastboot flash recovery <name-of-file>.img
then boot into recovery and there you can flash your ROM, gapps, kernel.
In the long run, IT WILL PAY OFF because eventually YOU will be faced with a problem with your phone and you won't be able to recover your phone because you dont know basic fastboot or adb commands all simply because you wanted to use a toolkit. People are already asking on how to use adb / fastboot in Q&A, we can reduce the clutter by not having people use toolkits and actually learning how adb / fastboot works when it isn't a very complicated thing to do at all
As stated in my original post, I am using a Mac. Not a PC. Therefore I don't use ADB, nor any other drivers. I also do not see, as stated before, any sdcard folder. I don't, I repeat, don't see it.
Doggonit said:
As stated in my original post, I am using a Mac. Not a PC. Therefore I don't use ADB, nor any other drivers. I also do not see, as stated before, any sdcard folder. I don't, I repeat, don't see it.
Click to expand...
Click to collapse
you dont need drivers on mac then... you can still ADB connect using mac.
simple: google search..... http://lmgtfy.com/?q=mac+adb first link
Doggonit said:
Where is /sdcard? There is no SD Card in a Nexus 4. Is this a hidden folder somewhere?
Click to expand...
Click to collapse
On the Nexus 4, /sdcard is the same as /storage/emulated/0. As mentioned earlier in the thread, this is the default location for native USB file transfer.
Sent from my Nexus 4
i was trying to install a new PA nightly and then i wanted to wipe the phone clean before i install it, but i accidentally wipe the sd card. Can i just use a toolkit and flash stock OS or can i just connect it to pc and paste a zip file of PA? help please
If you can use adb just do
adb push nameofrom.zip /sdcard
Then install as normal
Sent from my Nexus 4 using xda app-developers app
yes i have adb, i hope i have a copy of any zip file there :/
aside from that can i do a fresh install using a toolkit? i have mskips toolkit and as far as i can remember it downloaded the stock images.
eluspo said:
yes i have adb, i hope i have a copy of any zip file there :/
aside from that can i do a fresh install using a toolkit? i have mskips toolkit and as far as i can remember it downloaded the stock images.
Click to expand...
Click to collapse
Why would you? You are as clean as you can get as you wiped everything. Just push PA and gapps to the sdcard as said by Alex240188 before and flash the rom.
so command would be adb push filename.zip/sdcard? no spaces?
doest matter where i put my zip file? no need to indicate the location of the zip file?
eluspo said:
so command would be adb push filename.zip/sdcard? no spaces?
Click to expand...
Click to collapse
"adb push nameofrom.zip /sdcard/"
Also do the same for the gapps
Sent from my Nexus 4
eluspo said:
doest matter where i put my zip file? no need to indicate the location of the zip file?
Click to expand...
Click to collapse
It doesn't matter where you put it if you have adb.exe in your environment variables.
If you don't then you have to have it in the same folder as adb.exe and then CD to that folder in command prompt.
You can flash stock images in fastboot then copy new ROM back on if that's easier for you.
On a side note I keep laughing every time I put fastboot in because the slide keyboard always likes to default to Fatboy
Sent from my Nexus 4 using xda app-developers app
thanks for the info, im just wondering if i have stock images downloaded becase when i downloaded mskips toolkit it downloaded the stock 4.2.2
if i can see the images maybe ill flash stock then flash everything again.
there are tutorials all over xda on how to use adb and thats all you need to do is just push it over and flash. The longest part would be simply pushing the file over to your phone... hit up google and check it out
Hi everybody
When the factory images came out, I flash my N4 with the stock factory images that we used to find here : https://developers.google.com/android/nexus/images#occamkrt16s because it is now the KRT16S build
After a few days, when the KRT16S build came out, I was proposed in my phone to update it. I downloaded it, tried to flash it but nothing worked, I'm still on KRT16O and the OTA doesn't appear anymore... Then I remembered that I flashed a mod found here : http://forum.xda-developers.com/showthread.php?t=2527525 (that's a great mod btw) so I guessed that I could reflash the undo file available on the thread, flash the ota file dl mannually (I attached it in this thread) which I did through TWRP. Then I was able to see the problem, it told me that, from what I remember, Agenda.apk was missing (I think it's diary in english, not sure) then I remembered that I manually deleted some apps I never use (diary is one of them...)
So, what's next, shall I reflash the gapps to finally update my phone
Thanks for your help :laugh:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
howard bamber said:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
Click to expand...
Click to collapse
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
azertguigui said:
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
Click to expand...
Click to collapse
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
taodan said:
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
Click to expand...
Click to collapse
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
azertguigui said:
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
Click to expand...
Click to collapse
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
MameTozhio said:
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
Click to expand...
Click to collapse
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
UP
azertguigui said:
UP
Click to expand...
Click to collapse
**
azertguigui said:
UP
Click to expand...
Click to collapse
azertguigui said:
**
Click to expand...
Click to collapse
Not sure what you're trying to say here..
azertguigui said:
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
Click to expand...
Click to collapse
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Ibrahim.Rahman said:
Not sure what you're trying to say here..
Click to expand...
Click to collapse
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Ibrahim.Rahman said:
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I'll give a try
saifulh2304 said:
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
arffrhn said:
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Click to expand...
Click to collapse
thanks guys, I'm gonna find tutorials on the web like the one you pointed to me
azertguigui said:
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Click to expand...
Click to collapse
Haha right!
Sent from my Nexus 4 using xda app-developers app
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
If you can boot to bootloader you should be able to replace the file with a standard one.
Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out
1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.
Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?
Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!
Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0
same thing happened to me.... stuck on google even after flashing stock....
dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app
Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.
RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too