Now that the bootloader is unlocked, everyone is asking "WTF do I do now?". Well, here's a bit of help to get you started. I'm assuming you already have adb and fastboot setup and working -- if not, quit reading and get that taken care of. Also, I only run Linux...so I'll try to be transparent and only list the fastboot commands.
I assume that you're not a complete moron and can Google what you don't understand.
Don't use the stock\SDK fastboot binary for flashing /system.
An updated fastboot binary for Lin\Win\Mac can be found here on the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory in your $PATH -- Ubuntu\Debian users can just add it to ~/bin (enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere handy...that's on you to decide.
ROOT\ADMINISTRATOR INFO
On Linux, you might have to run as root in order to run some of the fastboot commands. If your system uses sudo for root commands, typing "sudo -i" will bring up an interactive sudo shell so you don't have to type sudo over and over again. If your system uses su for root, well, you already know the command.
On Windows, you have to enable Administrator Privileges to be able to run some of the fastboot commands.
Linux Terminal Hints
~/ means your home directory -- example -- "gedit ~/Documents/file.txt" would open file.txt in gedit easier than /home/yourusername/Documents/file.txt
You can add a * to file names and directories to not type as much -- example -- "gedit ~/Doc*/file.txt" is the same as the command above, only shortened. If two files have similar names, like Documents and Downloads, then you have to type the name up until the firs different character then add *.
Use the command "../" to go up\back one directory. The command is stackable so "../../" would go back 2 directories and so forth and so on.
Use "cd" to change directories. Is an example really needed for this...
Proper Apps to Use
For zip file editing, use 7-zip on Windows and Archive Manager (file-roller) on Linux
For editing text files on Windows use Notepad++ or any text editor that has unix line breaks -- do not use default Notepad or Wordpad -- you've been warned. Use what ever you prefer on Linux. I prefer Gedit myself.
Basic Fastboot Command Syntax
fastboot flash "partition" "image" -- flashes partition image where partition is where to write to and image is the path to the image being written.
example -- fastboot flash system /path/to/system.img
fastboot -w -- does a factory reset; to expedite things, "-w" can be added to "fastboot flash system system.img -w"
fastboot continue -- continue with the boot process
fastboot devices -- list devices fastboot recoginzes
fastboot -s "device model number" -- set the device fastboot will write commands to; use "fastboot devices" to find model number
fastboot reboot bootloader -- reboot phone into fastboot mode (or restart fastboot mode while in fastboot); same as "adb reboot bootloader"
fastboot help -- list all of this & more
Command Info
Not all the fastboot commands work for us. Specifically, the "erase" commands. If a wipe command doesn't work, skip it. I'll mark them with a ! at the end if it might fail.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Install Stock Fastboots ICS
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img.ext4
fastboot erase cache !
fastboot -w
fastboot reboot
Install Alternate Radio
Reboot into fastboot
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
NON-HLOS.bin is found inside a fastboot zip.
Easy Kernel Install
Download kernel-flash.zip in the attachments[/URL]
Open the zip
Replace the zips current boot.img and device_tree.bin from the fastboot of your choice
Install the zip with CWM
By default, kernel-flash.zip comes with Mex Retail kernel and devtree
Easy CWM Install
Download recovery-flash.zip in the attachments[/URL]
Install the zip with CWM
Not sure if its SS compatible, but it is CWM compatible (for the lazy Photon Q users).
Obtain root after installing a Stock Firmware
There are two choices for obtaining root after a stock flash. the closed source SuperSu by Chainfire & and the open source Superuser by Koush.
Download SuperSu zip from Chainfire (Closed Source)
Download Superuser from Koush (Open Source)
Download the one of the root zips above.
Reboot into CWM/TWRP -- adb reboot recovery
Locate and flash the zip (see below for an alternative way)
Reboot, that's it. Nice not having to run exploits\hacks\Linux just for root
Install Rom/Zip file with ADB + CWM
CWM has the awesome ability to install zip files without having to manually copy them to the phone first. All's necessary is a PC with working adb.
Reboot into recovery
Select "install zip from sideload"
On PC, type "adb sideload /path/to/zip" and press enter
The zip will now be copied to the phone's cache & install
Once installed, do any requirements you'd normally do like wipe caches, etc
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Unless you're not rooted with an unlocked BL, there's really no reason why it shouldn't work?
Sent from my N4'd Atrix HD
I was rooted before unlocking... shouldn't it still be rooted?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Did you uninstall safestrap?
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
miketravis said:
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
Click to expand...
Click to collapse
Still did not work for me
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
miketravis said:
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
tvd0405 said:
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
Click to expand...
Click to collapse
same here.
I have the same problem. I was able to flash cwm, uninstall the SS recovery, and uninstall the app. The first time I got the dead android symbol. I restored SS via Titanium Backup, reinstalled the SS recovery, and flashed cwm again. I tried rebooting into recovery and was able to get cwm working. As soon I uninstalled SS and rebooted, I got another dead android.
probably because were all on the XT926 if we were to revert back to XT925 then the recovery should work otherwise we will have to tweak the recovery to get it to work properly witht the XT926 software awesome thing is we can now free up the space that SS used for a rom slot however for noobs you might wana stick with SS once you hardbrick without anything to go back too it will be game over for your phone and then you have to con ATT for another
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
htchd2fix said:
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
Click to expand...
Click to collapse
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
skeevy420 said:
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
Click to expand...
Click to collapse
What's MR?
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Markyzz said:
What's MR?
Click to expand...
Click to collapse
Mexican Retail
Install instructions in OP
htchd2fix said:
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Click to expand...
Click to collapse
You won't lose root
And with an unlocked bootloader, all you gotta do is flash an updater zip with the su binary and app for Stock roms that don't have root
I'll link to a root zip in the op once I find one (or just make it; depends on how quick I find it in a search)
thanx again..
ahahahha...what a beautifullll day....
skeevy420 said:
Mexican Retail
Install instructions in OP
Click to expand...
Click to collapse
is there a point to flash a different firmware? is it required by any means?
I had SS and was backed up, I booted up the "stock ROM" and was successful in unlocking the BL and flashing CWM. I made a new backup of the stock ROM and restored it with success in CWM. In the video it show he has MR , but im confused as to why.
Also, I cant seem to get rid of safestrap....how in the hell do you uninstall it???
Related
Hello All,
I am a noob and recently learned how to root, unlock or re-partition, install blackrose etc but using your blogs and wikicynogemod.
I am trying to update my phone to Texas ICS using blog by OP- http://forum.xda-developers.com/showthread.php?t=1366897
I was able to reach till the step mentioned below :
i.e.
fastboot flash hboot hboot_brcrust_220-10-206-ICS.nb0
fastboot reboot-bootloader
fastboot -w
and now my phone shows TexasICS on the second line that mans it flashed correctly.
I downloaded the tar file "Evervolv-Perdo-2.2.0a6" but I am clueless about the next steps.
1. To build Evervol --> How and where as repo command doesnt work on my computer undert android sdk directory
2. tar xjf --> I am using windows 7 and hence no tar on my laptop.Meanwhile I am downloading the zip file also and see if unzip works.
But I am curious where to run these commands- either on cmd prompt under android-sdk directory or the phone emulator.
And interestingly, android-sdk dont have unzip/tar command and I have no access to phone now, its not booting.
Also I cant login to my phone now, when I boot it, its stuck at the Nexus One startup logo, not going further, so I believe I can't put anything in the SD card now.
Kindly help as my phone is not accessible now and I am kind of handicapped because of that
FYI : Recently I upgraded the phone to 2.3.7 using Cynogenmod, clock recovery.
you might have lost ur recovery
so fastboot any preffered recovery.img . put .zip in sd and flash it
or you can fastboot system.img, boot.img n recovery.img
Sent from my Nexus One using Tapatalk
If you have a custom recovery like clockworkmod just turn on your device holding trackball or something (I don't remember exactly) and you'll be in recovery or fastboot. Anyway, go to recovery and restore your nand backup. After that you can keep trying (or read below).
If you don't have a backup you can insert the SD card directly into the computer and copy the Evervolv latest version (.ZIP). Then go to recovery and wipe data & cache then install the zip from sd card.
You don't need to pay attention to the building Evervolv part of the post as it's not needed for the install. Don't forget to flash gapps later if you want to.
Sorry for my English and I hope this helps as I'm a bit noob also
Sent from my GT-P7510 using xda app-developers app
flash recovery
Flash recovery by
booting in fastboot
fastboot flash recovery recoveryNAME.img
then reboot to recovery u will get recovery the flash ICS.zip rom
Hello Folks,
I'm still stuck with my nexus one since I don't care that much about phones.
I've seen that jelly bean roms have made a significant progress. Thus I decided to give it a shot.
I started with installing adb and fastboot. :good: After that I rooted the nexus one :good: I've used this how to:
c2med blog, can't post links...
Next, I ran blackrose. :good: I saved the rom on the micro sd. Having done all the preperations I wanted to flash the JB rom.
I started the phone in bootloader mode but - unfortunately - couldn't access the recovery mode (ext4). I only get the Android figure and an exclamation mark.
In the how-to it sais i should use fastboot to flash the recovery made by ext 4.
Problem # 1: Ext4 generated a .zip, not a .img file
Problem # 2: I connect the device in fastboot mode, navigate to the adb/fastboot folder and use ./fastboot devices. The phone is recognized and I see the serial number. Next I try "flash recovery...." but I only get "command not found". Now, I basically have no idea what to do.
Which recovery should I flash? And how?
I'm so looking forward to your answers.
Androdicct said:
Hello Folks,
I only get the Android figure and an exclamation mark.
Which recovery should I flash? And how?
Click to expand...
Click to collapse
What you get is the stock recovery.
Flash 4Ext recovery or Amon RA recovery ( fastboot flash recovery recovery-RA-passion-v2.2.1.img)
Among the several guides to install JB, I suggest you to look at the following post:
http://forum.xda-developers.com/showthread.php?t=1804571
I just finished this morning the following process:
install RA recovery,
install Blackrose and resize partition,
install from SD card Evervolv-Perdo-3.2.0-Nightly-2013.01.13-passion.zip
install from SD card gapps-ev-jb-20120816.zip
I spent a lot of times reading and trying. I had an issue after installing Evervolv-perdo-3.1.0final-passion zip. That's why I switched to the Nightly (JB 4.2).
Once you are set install a2sd from within the terminal emulator on your N1.
In my opinion this is so far the best ROM I ever have had on my Nexus 1.:good:
I am impressed to the extend that I offer to my wife to do the same on her N1. She said no. No to unlock, no to root and of course no to custom ROM.
Good luck
Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...
Androdicct said:
Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...
Click to expand...
Click to collapse
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?
gunner1937 said:
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?
Click to expand...
Click to collapse
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=611829 : read posts #15 and #16.
In other words open your folder android-sdk-windows installed on the root of your C: hd. Click on the folder platform-tools and download Amon RA recovery in this folder. Left click anywhere on a blank area of this folder then press the key Shift (keyboard) and right click your mouse. In the drop down menu select Open command window. In the CMD, to be sure that the N1 is recognized by the pc (meaning the right drivers are installed) type ADB devices and press enter. You should see a string of numbers like HT9C......
Type adb reboot bootloader and press enter. You are in the fastboot mode ( and mood if I may say so) and the phone shows that it is in the bootloader. You can check again that N1 is recognized by the pc by typing fastboot devices. Same string appears.
Type fastboot flash recovery recovery-RA-passion-v2.2.1.img.
After the installation is completed boot in recovery, select Flash zip from sdcard, select the ROM you have dropped on the card. When the installation is completed go back to Flash zip from sdcard ( you are still in recovery mode) and select the gapps you have dropped on the sdcard.
Go back to Reboot system now. You are then out of the recovery and it takes some times for the N1 to boot to this beautiful JB
Edit:
http://forum.xda-developers.com/showthread.php?t=1804571 this is for posts #15 & #16
Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
As c2med posted in his guide, sometimes, people lose their recovery when they repartition using Black Rose. Hence, its always best to have Amon-RA or 4EXT flashable .img file in your PC so that incase you lose recovery, you can always flash it back.
Once you are in bootloader ( also called FASTBOOT mode) you can flash your recovery.
Then reboot into recovery from FASTBOOT (Shutdown and then restart using the recovery combination)
Once you are in recovery, follow the steps in c2med's guide (wipe cache/dalvik/etc - except sd-card ofcourse) and flash your ROM from sd card.
Then reboot into JayBee
In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img
jolinnard said:
In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img
Click to expand...
Click to collapse
Thank You! That's what I figuered out last night. Of course I also tried "fastboot flash" but forgot the "./". That was the key. Now the JB ROM works like a charm.
New Problem:
I can't install google apps. In fact I don't really need them. I only use a few apps and found the .apk files with google. Unfortunately the "official" Google apps like chrome don't work.
Plus, I wanted to install the camera (laggy in the evervolv - rom) and keyboard from here.
http://forum.xda-developers.com/showthread.php?t=1965290&page=38
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?
Androdicct said:
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?
Click to expand...
Click to collapse
When you're in recovery, select "Flash zip from SD card" and then select "Toggle signature verification" to disable signature verification, and then "Choose zip from SD card" and navigate to the zip file that you want to flash.
downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help
BFRAPV42 said:
downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help
Click to expand...
Click to collapse
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )
flashing error
Codex01 said:
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )
Click to expand...
Click to collapse
i was on here prior but its been a while i appreciate the help. my issue theres no system on my AHD so how to get pacman rom redownloaded to my pc and no im not super BA at scripting. ya i can delete a few getvar lines to flash back to stock jb and start over again but syste.img wont even flash there while in AP Fastboot.
Thanks man
Trying to go to stock jb now, i had root and have unlocked bootloader, when usign rsd lite v5.7 i flash the xml after editing it and taking the 2 getvar lines out and now system wont flash, it says phone "Fail flashing process" "system.img" phone returned fail. flashing everything fine till it gets to the system.img file.
(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.
Codex01 said:
(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.
Click to expand...
Click to collapse
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check
stock jb
skeevydude said:
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check
Click to expand...
Click to collapse
so i downloaded stock att jb rom from xda, went to the directory C:\user\costco\desktop and to the stock jb folder open command prompt and typed the code.(phone is in fast boot currently as well) Cmmnd prompt says is not recognized as an external or internal command,operable program or batch file. Maybe my head is just to busy to focus i must be messing up somewhere. You guys are so freaking awesome for being patient with me and helping me, ill buy the brews haha
Not an issue with bootloader already unlocked i assume cause once im back on stock im gonna be 1000 times more careful when rerooting again to get back where i was.
idk if its terminal for vista or if its the download i got, i got it from a link on here from, I leave the "getvar lines on the xml file when i do it through terminal right?
Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone
Droid4Drew said:
Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone
Click to expand...
Click to collapse
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.
still no bueno
BFRAPV42 said:
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.
Click to expand...
Click to collapse
still a no go, have the new folder with all 5 items needed, pulled up command prompt and its giving same issue. F WORDDDDDDDDDs
C:\Users\Costco>fastboot flash system system.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
same error.
You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM
Droid4Drew said:
You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM
Click to expand...
Click to collapse
i have the snapdragon fastboot .exe and .api in the folder already. along with the system.img , epinters recovery.img and MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
i took a screen shot of the directions you gave with the command prompt open and the folder with the files in it but couldnt upload it unfortunately.
Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app
TTLayland said:
Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
fastboot.exe is admin api doesnt have an option in advanced for run as admin, i opened terminal and cd to where the file was on c: drive and typed [fastboot flash system system.img] hit entere and it worked but the phone never rebooted after it completed, when i typed [fastboot flash recovery recovery.img] with is epinters recovery it says ERROR cannot load recovery.img
Scratch that I'm actually replying to this from stock jb, thank all you guys for all the help.
Sent from my MB886 using xda app-developers app
So my advice worked?
Sent from my MB886 using xda app-developers app
Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app
BFRAPV42 said:
Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I found that the advice I gave you was the only thing that was not in the instructions. Good stuff that you got it working though.
Sent from my MB886 using xda app-developers app
Got a ? about Atrix HD flashed with Pac Man v22
I flashed Pac Man and everything looks great, and works well tiny lag issues but I love it so thank you to all the devs involved.
But...I have seemed to lose root access. I have tried to reinstall the root access with one click and it stops at Daemon started successfully *
any ideas thanks in advance!
Install a superuser zip through cwm.
Sent from my PACMAN MATRIX HD MAXX
Preamble
As the title suggests, I had a Nexus 5 running stock Android 5.0, with root and TWRP, and wanted to update to Android 5.0.1 (without losing all my data, of course). I couldn't find any guides for my particular circumstances, so after working out how to do it myself, I thought I'd share my method.
Note: This guide is not for the uninitiated. Be prepared to Google something for yourself if you don't understand it.
Prerequisites
Before starting this guide, you should have:
A Nexus 5 that running stock Android. The presence of root/Xposed/custom recovery (maybe custom kernels?) shouldn't be relevant, but I can't vouch for the efficacy of this guide if you've done something obscure to your install.
Android SDK tools, specifically the ADB and fastboot binaries. Additional USB drivers may be required on Windows.
The factory image for the Android version you are currently running.
1. Uninstall root and other /system modifications
If you have rooted your Android, and/or installed BusyBox, Xposed or other modifications to /system, you will need to uninstall these modifications. Failing to do so will cause the OTA to complain that there's something funky going on in your /system partition.
You may be able to manually uninstall each of these modifications, but this was not enough for my install – doing a ‘Full unroot’ in SuperSU still left behind files in /system. The easiest way to uninstall all /system modifications is to reflash the /system partition.
Extract the Nexus 5 factory image (e.g. hammerhead-lrx21o-factory-01315e08.tgz), yielding a directory with files such as flash-all.bat and image-hammerhead-XXXXXX.zip. Do not use the flash-all script, as this will unnecessarily wipe all data on the device.
Extract the image-hammerhead-XXXXXX.zip file, specifically the system.img file.
Open a command prompt/terminal window.
Connect the phone to the computer with a USB cable.
Boot the phone into the bootloader.
Method 1: Power down the phone, then hold VolUp + VolDn + Power until the phone boots into the bootloader.
Method 2: From the terminal, run adb reboot bootloader while the phone is still powered on.
From the terminal, run fastboot flash system /path/to/system.img.
2. Uninstall any custom recovery
Custom recoveries don't seem to support OTA updates, making it necessary to uninstall the custom recovery by reflashing the stock recovery.
Extract the recovery.img file from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash recovery /path/to/recovery.img.
Optional: Reflash boot.img and/or cache.img
Some users have reported that reflashing system.img was not sufficient, and that reflashing boot.img and/or cache.img was also necessary. I did not have this problem, but if you do:
Extract the boot.img and/or cache.img files from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash boot /path/to/boot.img.
From the terminal, run fastboot flash cache /path/to/cache.img.
3. Apply the OTA update
The simple part. In the bootloader, use the VolUp/VolDn buttons to select ‘Start’, then press the Power button, to reboot into Android. Follow the system update instructions to install the OTA update.
4. Reflash the custom recovery and re-root
Also self-explanatory.
Hey,
I just wanted to say thanks. This totally fixed the problem I was having. I also want to add that after I flashed the system.img, I was getting errors related to "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot" with a bunch of numbers after. I googled it and found I had to also flash boot.img, and after that, the OTA worked fine. I would assume if anyone else gets errors like this, they should flash whatever img it shows in the error (ie: mine said /by-name/boot so I flashed boot.img).
-BGM
It worked for me
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
azlan96 said:
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
Click to expand...
Click to collapse
I also had problems using ‘Full Unroot’ in SuperSU. It's not actually as ‘full’ as it sounds.
Flashing a full factory image would normally wipe everything, but carefully following this guide will only reset the /system partition, not any user data.
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Taiyo85 said:
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Click to expand...
Click to collapse
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
azlan96 said:
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
Click to expand...
Click to collapse
Flash Stock + Unroot wipes everything and defeats the purpose of the tutorial made by RunasSudo
First and foremost you should download Android SDK (Tools only) on http://developer.android.com/sdk/index.html and then ask to install the extra: Google USB Driver.
With Nexus Root Toolkit you don't need terminal, click on advanced and you should see options to flash through fastboot the system only, recovery and kernel. It is pretty straighforward and it asks where the .img are in your computer
Thanks! This guide worked.
For Ubuntu users, you need to install adb and fastboot with these commands :
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update (optional)
sudo apt-get install android-tools-adb android-tools-fastboot
Thanks for the great step by step.
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img. Once that was done, I had no problems side loading the update and am now running LRX22C.
I only seem to fiddle with adb once a year - when it OTA time comes - and can never seem to remember some of the steps that need to be taken. Reading through some of the other threads, I have a feeling a lot of people who rooted/custom recovery and cant do the OTA are going to be doing complete image re-flashes when this guide makes that completely unecessary.
thanks again,
.d
BananasGoMoo said:
I googled it and found I had to also flash boot.img, and after that, the OTA worked fine.
Click to expand...
Click to collapse
datcon said:
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img.
Click to expand...
Click to collapse
Thanks for the feedback! I've added a note about boot.img to the OP.
+1 for flashing boot.img worked perfect after I did that.
I tried with this tutorial. I flashed system and recovery and then restart. Confirm OTA but I get ERROR.
Then I flashed boot as it was described. Now I don't get OTA In About phone, I'm still on 5.0.0, Check for updates now don't find update
Any idea?
UPDATE - UPDATE: After hour now it is here ... super, it works.
This walkthrough was most helpful! Ended up replacing the boot.img as well since I had ElementalX installed. My apps are optimizing as we speak. Thank you!
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
adb reboot bootloader
Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache (this is optional. I didn't have to do it, but you might)
Use Volume Up/Down to select Start > press Power Button to reboot
Update via Settings > About Phone > System Update
Re-flash TWRP recovery:
Get the file from here: http://forum.xda-developers.com/showpost.php?p=57580889&postcount=1
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
Paul22000 said:
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
1. Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
2. Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
3. Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
4. Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
5. adb reboot bootloader
6. Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
7. Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
8. Use Volume Up/Down to select Start > press Power Button to reboot
9. Update via Settings > About Phone > System Update
Click to expand...
Click to collapse
Maybe you could add `fastboot erase cache` as stepp 8.
gee2012 said:
Maybe you could add `fastboot erase cache` as stepp 8.
Click to expand...
Click to collapse
I added it to step 7, thanks. :good: I also cleaned up the formatting and added step 10 about re-flashing TWRP.
Loading problem
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
guangy said:
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
Click to expand...
Click to collapse
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
RunasSudo said:
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
Click to expand...
Click to collapse
I flashed the cache image as well, then the problem solved. Thanks
Hey,
I enrolled to the Android Nougat program and rooted my phone (chainfire) a few days ago. Decided to un-root (using superSU), and it said I was unrooted. After doing the un-rooting, the OEM unlock-option was greyed out (and on OFF setting), but the phone recovery says it's unlocked api 3.... I pretty much just wanted to unenroll and go back to MM. Every time I choose unroll from Google, download the MM OTA and it reboots I get an error. Just an image of android with message "ERROR". The only way to get the phone working is to do a hard reset and go back to Nougat.
Not quite sure what is wrong here. Any suggestions?
It's probably because the SuperSU unroot hasn't cleaned up everything that the MM installer checks for. Your best bet is to use the sideload OTA here:
https://developers.google.com/android/nexus/ota
to install MM again. It's quick and easy, and doesn't touch your data.
Since you received the actual uninstall OTA you must have successfully unenrolled, so you should be ok from now on.
dahawthorne said:
It's probably because the SuperSU unroot hasn't cleaned up everything that the MM installer checks for. Your best bet is to use the sideload OTA here:
https://developers.google.com/android/nexus/ota
to install MM again. It's quick and easy, and doesn't touch your data.
Since you received the actual uninstall OTA you must have successfully unenrolled, so you should be ok from now on.
Click to expand...
Click to collapse
I received the OTA but while installing MM it gives me an error, so I have to go back to Nougat every time. I've tried the unenroll option several times and it gives me the same "error" every time. So, I should try manually flashing MM, then?
UPDATE:
I tried the following:
Downloaded and tried to sideload 6.0.1 (MOB30W) to my Nexus 6-device. It got up to 46% and after it gave me and error saying:
WARNING: No file_contexts. This package is for shamu devices; this is a "".
E: Error in /sideload/package.zip
Status 7
Installation aborted.
UPDATE2:
Tried another package. Didn't work. All the OTA updates stop at 46% giving me the same error. Device remains unlocked, but appears not to be rooted. Still stuck on Nougat.
What does "Tried another package" mean?
It may be that your download was corrupt. I always check the SHA with this checksum utility:
http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
though I've read in the instructions that the Android installation itself checks the package - it may be this error that the installation is reporting.
dahawthorne said:
What does "Tried another package" mean?
It may be that your download was corrupt. I always check the SHA with this checksum utility:
http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
though I've read in the instructions that the Android installation itself checks the package - it may be this error that the installation is reporting.
Click to expand...
Click to collapse
No, the checksum is fine. The package is fine. I mean I tried several OTA packages for N6 and it always stops at 46%. There's something else going on here. Maybe if I re-root with chainfire and the use another method to unroot it? Which is the correct method, I have no idea?
Factory reset, and try sideloading MOB30W again.
dahawthorne said:
Factory reset, and try sideloading MOB30W again.
Click to expand...
Click to collapse
Done it like 5 times already. Also wiped cache. No help.
Hannes084 said:
Done it like 5 times already. Also wiped cache. No help.
Click to expand...
Click to collapse
My suggestion is to go back to Android N, root with SuperSU and see if your OEM UNLOCK toggle in Developer Options is working again and not greyed out. Then I would fastboot flash back to MM and install TWRP and SuperSu.
Sent from my Nexus 6 using XDA-Developers mobile app
Dude, just flash the system image you want. Forget about the OTA
The OTA is a system image.
fast69mopar said:
My suggestion is to go back to Android N, root with SuperSU and see if your OEM UNLOCK toggle in Developer Options is working again and not greyed out. Then I would fastboot flash back to MM and install TWRP and SuperSu.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Root with SuperSU? I think you mean with chainfire?
dahawthorne said:
The OTA is a system image.
Click to expand...
Click to collapse
You could say the new full otas are, but you can't go flashing them freely over newer images.
The unenroll option resets the phone anyways, so the best and aparently the only option for him is to flash the system image he wants from scratch.
blanco2701 said:
You could say the new full otas are, but you can't go flashing them freely over newer images.
The unenroll option resets the phone anyways, so the best and aparently the only option for him is to flash the system image he wants from scratch.
Click to expand...
Click to collapse
Sorry for asking but how would I even do that? I'm on Ubuntu 12, so it seems mega complicated.
Hannes084 said:
Sorry for asking but how would I even do that? I'm on Ubuntu 12, so it seems mega complicated.
Click to expand...
Click to collapse
Well my friend I have no idea since I'm on Windows. Google how to use adb and fastboot on ubuntu, there should be a solution for you.
This is a script that I used to run before the full OTAs became available. It worked many times for me, but the usual caveat - you follow it at your own risk. You can probably skip the backup step in your situation.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
dahawthorne said:
This is a script that I used to run before the full OTAs became available. It worked many times for me, but the usual caveat - you follow it at your own risk. You can probably skip the backup step in your situation.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
If I download the factory image (OTA) off google's site it has none of those files under the zip-folder.
Hannes084 said:
If I download the factory image (OTA) off google's site it has none of those files under the zip-folder.
Click to expand...
Click to collapse
One thing is the OTA image, and another is the Factory Image.
Download the factory image from here.
https://developers.google.com/android/nexus/images#shamu
Unzip everything and you should get all the files needed. As I said before, you would need to have a computer with adb and fastboot installed.
blanco2701 said:
One thing is the OTA image, and another is the Factory Image.
Download the factory image from here.
https://developers.google.com/android/nexus/images#shamu
Unzip everything and you should get all the files needed. As I said before, you would need to have a computer with adb and fastboot installed.
Click to expand...
Click to collapse
Thanks, doing that now!
Hannes084 said:
Thanks, doing that now!
Click to expand...
Click to collapse
Just be sure to have selected "oem unlocking" in the developer options, make a backup (everything will be wiped), and start flashing!. There are several guides everywhere.