Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
First, woohoo!
Flashing now, thanks bud!
EDIT: Hey Bunny, maybe I'm missing something. Where are those bootloader images available?
@bunny0007 is this pre-rooted, or stock ?
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
bunny0007 said:
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
Click to expand...
Click to collapse
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Moe5508 said:
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Click to expand...
Click to collapse
I flashed the ota file before i made the system dump.
Im not sure if the new bootloader an stuff are required for this update, but the ota are not a new rom, just patched files, no new boot image or recovery image.
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Moe5508 said:
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Click to expand...
Click to collapse
The only way to flash the ota file are from stock non rooted 5.0.1 via sideload from recovery.
You might fastboot flash stock 5.0.1 system, boot and recovery, then you shuld be able to flash the ota from recovery.
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system-rooted.img
Stock 5.0.2 boot partition dump download (sorry for the partiton size): http://www68.zippyshare.com/v/4v4NAT5J/file.html
Stock 5.0.2 recovery partition dump download (sorry for the partiton size): http://www3.zippyshare.com/v/hpeV5W22/file.html
Stock 5.0.2 System rooted: http://d-h.st/IGov
Smaller 5.0.2 boot.img and recovery.img might fe found here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if nessesary.
Extract the files and use the flash cmd file from windows cmd, or flash the files manually with fastboot.
bootloader.aboot.img
bootloader.imgdata.img
bootloader.rpm.img
bootloader.sbl1.img
bootloader.sdi.img
bootloader.tz.img
Download Bootloader Stuff : http://d-h.st/bDXl
Click to expand...
Click to collapse
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
akaHardison said:
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
Click to expand...
Click to collapse
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
fronc said:
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
Click to expand...
Click to collapse
yep have changed the error in new zip
@bunny0007 can you please post a step by step guide for how to flash this?
I am on rooted 5.0.1 and do not understand the order, or not even which imgs are necessary to flash?
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash system system-rooted.img
Stock 5.0.2 System rooted: http://d-h.st/IGov
Click to expand...
Click to collapse
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
BostonDan said:
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
Click to expand...
Click to collapse
Just uncheck the "Download with Dev-Host Download Manager" box.
Spleeno said:
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
Click to expand...
Click to collapse
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
b0gd4n said:
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
Click to expand...
Click to collapse
Boot into fastboot, then make sure you can use fastboot from windows in cmd shell.
Then use this to flash
1. Unzip and flash bootloader stuff with cmd file.
2. Flash system with "fastboot flash system filename.img"
3. Flash boot with "fastboot flash boot boot.img"
4. Flash Stock 5.0.2 recovery with "fastboot flash recovery recovery.img"
5. Reboot the watch
Is there coming a stock rooted 5.1.1?
TimV_ said:
Is there coming a stock rooted 5.1.1?
Click to expand...
Click to collapse
Yep here http://forum.xda-developers.com/g-watch-r/development/rom-stock-rooted-5-1-1-t3124921
How do you come around to get the watch listed in adb (adb devices command). I installed several drivers for my lg g watch r, tried both in win10 test and non test mode, but the watch is not recognized. DEvice manager lists it as "unknown usb device descriptor request failed".
I appreciate any type of suggestion. Thanks in advance!
Related
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
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.
I have moto x dev ed, I just unlock the bootloader. i tried to install this custom recovery i keep getting this.
<bootloader> variable not supported!
target reported max download size of 805306368 bytes
etc etc...
im trying to download the twrp custom recovery
i dont why it keeps doing that
I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?
Groid said:
I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?
Click to expand...
Click to collapse
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo
Fastboot the recovery.img then type fastboot reboot and choose recovery in fastboot menu
dat010man said:
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo
Click to expand...
Click to collapse
Sounds like it did not flash correctly because the laying down android leads to the stock recovery. I would try redownloading twrp for ghost again and make sure that is in the folder with fastboot and verify your getting the file name correct when flashing. Just repeating the steps all the through may be successful, we all miss a step occasionally. Good luck [emoji106]
Edit: p.s. I did read somewhere that some people had issue with recovery not sticking after flashing. They got around this by typing the command fastboot reboot bootloader right after flashing the recovery. After that custom recovery would stick.
I'm still getting the same error. Am I suppose to hold the volume up button until the recovery loads?
If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?
Travisdroidx2 said:
If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?
Click to expand...
Click to collapse
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?
dat010man said:
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?
Click to expand...
Click to collapse
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?
Travisdroidx2 said:
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?
Click to expand...
Click to collapse
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash
dat010man said:
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash
Click to expand...
Click to collapse
Shouldn't have to rename it but sounds like you got it working. Great.
Travisdroidx2 said:
Shouldn't have to rename it but sounds like you got it working. Great.
Click to expand...
Click to collapse
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application
dat010man said:
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application
Click to expand...
Click to collapse
I thought you said when you renamed it that it worked? So still no?
Travisdroidx2 said:
I thought you said when you renamed it that it worked? So still no?
Click to expand...
Click to collapse
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it
dat010man said:
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it
Click to expand...
Click to collapse
Put the twrp.img file in your SDK folder with your fastboot.exe files. Not on your device.
Is USB debugging turned on?
If so in download mode when you type fastboot devices do you see your device?
If so you just shift right click and open command prompt from that folder you have the files in on your PC.
Then fastboot flash recovery "name of file". IMG
After that volume down to recovery and then volume up to enter twrp.
Just to be clear, you are using the command:
fastboot flash recovery twrp-2.8.4.0-ghost.img (assuming twrp-2.8.4.0.img is the recovery file) and you have copied 'SuperSU-v2.46.zip' into the root of internal memory (called sdcard). After flashing the recovery, you should definitely not boot directly to the system. You should issue the command fastboot reboot-bootloader. Then, choose recovery from the menu and up arrow to start it. I can't remember the exact order of things, but somewhere along the way twrp will prompt you about the supersu and near the end it will ask about making changes so the stock recovery isn't applied back over twrp. Let it make the changes. When you do boot into the system you should have root.
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.
2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.
danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.