I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
simms22 said:
youll have to unlock your bootloader again. but being rooted, why dont you just flash any of the rooted 5.1 stock roms or a 5.1 aosp rom? it would be much much easier.
Click to expand...
Click to collapse
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked? And I want to try using fastboot because it seems simple to me.
Click to expand...
Click to collapse
it is easy, enjoy
simms22 said:
it is easy, enjoy
Click to expand...
Click to collapse
So to reassure, the process I listed is good to use for updates?
Forerunner326 said:
So to reassure, the process I listed is good to use for updates?
Click to expand...
Click to collapse
yea, its fine, but you dont have to reboot the bootloader after each flash.
simms22 said:
yea, its fine, but you dont have to reboot the bootloader after each flash.
Click to expand...
Click to collapse
Rebooting the bootloader like this doesn't hurt correct?
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
i wouldnt think so
simms22 said:
i wouldnt think so
Click to expand...
Click to collapse
What does rebooting the bootloader do?
Forerunner326 said:
What does rebooting the bootloader do?
Click to expand...
Click to collapse
just that, reboot the bootloader, nothing else. its been too long since i flashed a factory img! good thing too
Forerunner326 said:
Why would I have to unlock the bootloader again if it is already unlocked?
Click to expand...
Click to collapse
You don't.
Forerunner326 said:
Rebooting the bootloader like this doesn't hurt correct?
Click to expand...
Click to collapse
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
efrant said:
You don't.
Doesn't hurt, no. You should reboot into the bootloader after flashing a bootloader and after flashing a radio, so that you are running those before you flash the other images. (Just flashing the bootloader doesn't start it up -- you need to reboot-bootloader to actually start the new bootloader.) It may not be necessary, but it is likely safer to flash new images when on the latest bootloader, just in case.
Click to expand...
Click to collapse
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Forerunner326 said:
Which is why I have "fastboot reboot bootloader" in place after the bootloader, radio, and boot image.
Click to expand...
Click to collapse
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
efrant said:
It does absolutely nothing to boot into the bootloader after flashing the boot image, as the boot image doesn't "boot" in the bootloader. Only the bootloader and radio do.
Click to expand...
Click to collapse
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Forerunner326 said:
Which means I can remove "fastboot reboot bootloader" after the boot image and nothing will be affected?
Click to expand...
Click to collapse
Yes.
This is my method verified with 5.1.0 D and E variants, this will not wipe your device.
Download images from: https://developers.google.com/android/nexus/images#shamu
Extract all files to your comp including the main .tgz and the .zip inside that
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img (optional if keeping TWRP or you can flash the latest TWRP here)
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot (Or enter recovery and re-root if you kept TWRP)
efrant said:
Yes.
Click to expand...
Click to collapse
Is there anything else I should know before I flash any update files onto the device?
Forerunner326 said:
I was wondering if this process is okay for updating to new versions using fastboot
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. fastboot flash bootloader {bootloader-shamu-xxx.img}
4. fastboot reboot-bootloader
5. fastboot flash radio {radio-shamu-xxx.img}
6. fastboot reboot-bootloader
7. fastboot flash boot boot.img
9. fastboot reboot-bootloader
10. fastboot flash system system.img
11. Boot into TWRP by selecting Recovery Mode on device and pressing power button
12. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm > main menu > reboot)
13. Reboot
Did I miss any steps or would I do something wrong with these steps?
Click to expand...
Click to collapse
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
gee2012 said:
1 to 6 are good
7 fastboot flash system system.img
8 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
11, 12 13 are good.
Click to expand...
Click to collapse
What about the cache image? Would it go after boot.img gets flashed? Or do I not worry about it?
This is what I have so far.
Code:
1. Enable USB debugging and OEM unlock
2. Reboot into bootloader (volume-down + power)
3. Connect to pc and load platform tools command window
4. fastboot flash bootloader {bootloader-shamu-xxx.img}
5. fastboot reboot-bootloader
6. fastboot flash radio {radio-shamu-xxx.img}
7. fastboot reboot-bootloader
8. fastboot flash system system.img
9 fastboot flash boot boot.img (stock or modified decrypted/custom kernel)
10. Boot into TWRP by selecting Recovery Mode on device and pressing power button
11. Flash supersu via TWRP (Install > Choose the zip package > swipe to confirm)
12. Reboot (Main menu > reboot)
You can do that after boot:
fastboot erase cache
fastboot flash cache cache.img
11, 12, 13.
Related
Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4
cw18306 said:
Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4
Click to expand...
Click to collapse
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way
danger2u said:
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way
Click to expand...
Click to collapse
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X
flashallthetime said:
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X
Click to expand...
Click to collapse
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
look alot of people are having this issue it is a simple fix follow the directions step by step
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
as soon as you type the above command to flash TWRP we need to boot the phone into recovery before we let it boot to android we can do that via the command below.
Code:
adb reboot recovery
MAKE SURE THAT AFTER YOU TYPE THE FIRST COMMAND DO NOT LET THE PHONE BOOT TO ANDROID.
right after you hit enter for the mfastboot command type the reboot command it will boot into recovery. if not i would redownload the correct TWRP recovery for 4.4
there is a link here
http://forum.xda-developers.com/showthread.php?t=2603358
cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
If recovery flashes but is not available, your best bet is to flash the sbf firmware and flash recovery, its worked for numerous folks including me
Sent on my Moto X
cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.
xawen said:
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.
Click to expand...
Click to collapse
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
Like I said previously ,flash the kitkat firmware, forget jb. You can not flash back to the pre camera ota, gpt.bin is the bootloader which if is incompatible will fail, saving you from hard bricking your device
Sent on my Moto X
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
What errors are the RSD and fastboot actually failing with?
When you're trying to do the fastboot flash, does "fastboot devices" actually show your device as connected?
-----Edit----
Are you sure that is the right version of the firmware? I'm waiting for access to the files from the moto site right now so I can compare the full file name, but I'm pretty sure you have the Maxx Dev Edition firmware file there.
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
fastboot reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted
@cw18306 just got turnt up
SuperSU.ZIP Move to Phone?
dray_jr said:
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
adb reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted
Click to expand...
Click to collapse
You are THE MAN! Quick question regarding SuperSU.zip...Do I unzip it in windows and MOVE the 4 folders to the phone, OR do I only need to move the UNZIPPED SuperSU file to the phone? I am about to flash recovery and want to be sure. Thanks so much!!!
Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.
nhizzat said:
Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.
Click to expand...
Click to collapse
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android.
cw18306 said:
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android. I rebooted to bootloader again, reflashed TWRP, highlighted Recovery, hit UP, and the screen goes black and does not boot. If I press the power button, the phone will boot to Android. That is where I am now. Something must be up with my Recovery file?
Click to expand...
Click to collapse
@dray_jr
cw18306 said:
@dray_jr
Click to expand...
Click to collapse
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:
cw18306 said:
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:
Click to expand...
Click to collapse
no problem glad everything worked out for you enjoy
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!
Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?
mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.
Awesome man, worked perfect, you sir rock!
Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse
So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
scothern99 said:
So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
Click to expand...
Click to collapse
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
livinginkaos said:
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
Click to expand...
Click to collapse
Ok, so not to be a noob, where do I get the image files to flash?
Nexus images are all posted here - https://developers.google.com/android/nexus/images
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
scothern99 said:
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
Click to expand...
Click to collapse
Does anyone know if this is correct?
What I did to upgrade without wiping, i was on stock with elementalx kernel, root and twrp.
Only flashed radio and system img.
1. Downloaded images, extracted zip of the images.
2. Reboot to bootloader
3. Fastboot commands
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
4. Reboot to bootloader again
Run chainfire autoroot script.
5. Done
Remember to read read read if you don't know what are you doing, nobody here is responsible if things go wrong.
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
lion1750 said:
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
Click to expand...
Click to collapse
I'm wondering the same. Usually it was out right away and I would do the same as you. Seems crazy to me that we would have to unroot update and reroot agaain.
Usually I would flash a stock rom with the update that the dev would also throw root into.
livinginkaos said:
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
Click to expand...
Click to collapse
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
GMoGoody said:
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
Click to expand...
Click to collapse
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
livinginkaos said:
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
That su 2.4zip is for all devices? Not just for the n7 fhd? Thx
Via my NeXus™ 7FHD on XDA Premium app
I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.
Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery
From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up
y2whisper said:
From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up
Click to expand...
Click to collapse
Only if you boot android before rooting. Install-recovery.sh is suppled with the ROM that upon boot will install stock recovery. However flashing SuperSU hijacks this script for its own purposes, removing its ability to flash recovery. So trick is flash the ROM, boot straight to recovery and flash SuperSU
Ah. Good to know
rootSU said:
Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery
Click to expand...
Click to collapse
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
EDIT: See your post above (I took too long typing). Thanks for clarifying.
ManHands said:
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
Click to expand...
Click to collapse
Have a look above.
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed
moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
rootSU said:
Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed
Click to expand...
Click to collapse
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.
ManHands said:
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.
Click to expand...
Click to collapse
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.
Look at the op on Franco's thread and you'll have your answer
holeindalip said:
Look at the op on Franco's thread and you'll have your answer
Click to expand...
Click to collapse
If he looks in the Franco thread, it will answer his question about having to flash a stock boot.img?
moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?
rootSU said:
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.
Click to expand...
Click to collapse
Brain fart, for future reference Franco r1-r19 is 5.0,5.0.1,5.0.2 and r20+ is for 5.1
Thanks for the input everyone. To follow-up, I took the steps just as I planned in OP. No need to flash boot.img as frano-r20 is what I'm running and is compatible with 5.1 (despite the build # difference). I also didn't want to encrypt as the factory boot.img will force encrypt.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
And just as @rootSU pointed out, prior to booting system, go into TWRP from bootloader to install su.zip first (otherwise factory recovery will overwrite TWRP). Then boot system, and you're back in business. Just had to re-do a couple build.prop edits, but everything else was as it was before.
If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?
lamenting said:
If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?
Click to expand...
Click to collapse
That, or you can wait for 47E factory boot.img that's non-enforcable. But, from the sounds of it people are still able to use the 47D boot.img linked in the post you provided. I'd imagine there's not much difference between the two.
Forerunner326 said:
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?
Click to expand...
Click to collapse
I have no idea honestly, I saw someone else post it that way. It is probably not necessary.
ManHands said:
I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.
Click to expand...
Click to collapse
After flashing the files in fastboot you said to use the hardware buttons to boot into TWRP. How exactly did you go from fastboot to TWRP? Did you just power off while in fastboot or something else?
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
hollywood_jack said:
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
Click to expand...
Click to collapse
Or do it manualy with adb, look here as a guide http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504 method 2. Toolkits will always bite you in the ass at some point in the future
gee2012 said:
Toolkits will always bite you in the ass at some point in the future
Click to expand...
Click to collapse
Sorry but I not have understood this
hollywood_jack said:
Sorry but I not have understood this
Click to expand...
Click to collapse
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
gee2012 said:
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
Click to expand...
Click to collapse
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
hollywood_jack said:
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
Click to expand...
Click to collapse
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
gee2012 said:
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
Click to expand...
Click to collapse
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
hollywood_jack said:
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
Click to expand...
Click to collapse
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
gee2012 said:
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
Click to expand...
Click to collapse
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
hollywood_jack said:
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
Click to expand...
Click to collapse
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
gee2012 said:
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
Click to expand...
Click to collapse
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop with the following flash (always method 2)?
hollywood_jack said:
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop?
Click to expand...
Click to collapse
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
gee2012 said:
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
Click to expand...
Click to collapse
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
hollywood_jack said:
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
Click to expand...
Click to collapse
Extract the rom and flash the bootloader first (fastboot flash bootloader namebootloader.img) and fastboot reboot-bootloader, then the radio and also reboot and then the rest in one go. Good luck an if you have doubts/problems post it here. Plenty of helpfull members around
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
hollywood_jack said:
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
Click to expand...
Click to collapse
Once you unlock the BL it stays unlocked unless you lock it manualy. Even if you flash a new bootloader.
Thanks my friend...thanks alot
with my Nexus 6
hollywood_jack said:
Thanks my friend...thanks alot
with my Nexus 6
Click to expand...
Click to collapse
Good luck, its only a bit stressfull the first time
gee2012 said:
Good luck, its only a bit stressfull the first time
Click to expand...
Click to collapse
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
hollywood_jack said:
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
Click to expand...
Click to collapse
- You don`t have to erase boot and recovery
- Yes you can flash a non encryped kernel but you`ll have to factory reset after you flashed and the N6 is booting or your storage will say its 32GB.
- Rooting is easiest by placing the latest 2.8.7.1 TWRP recovery in the sdk-platform-tools folder, reboot in bootloadermode and fastboot boot namerecovery.img and boot up and flash the latest superSU.zip (Beta 2.49 afaik) or use a toolkit if want to.