Related
Now my SU is giving me trouble, it doesn't work or the su exe file is missing. No problem, I'll reflash the zip.
I still have the stock recovery, so I:
fastboot boot recovery.img
but when I do that , it appears to succeed, but hangs the phone on the fastboot screen.
So I can't boot or flash a custom recovery.
Tried goomanager, that didn't work either.
Any help appreciated in getting su working again, and/or installing a custom recovery and/or ROM.
Thanks!
bilybob said:
Now my SU is giving me trouble, it doesn't work or the su exe file is missing. No problem, I'll reflash the zip.
fastboot boot recovery.img
Thanks!
Click to expand...
Click to collapse
that only worked with hboot 1.44, you're going to have to flash it.
I tried flashing - that didn't work either. I did:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
Same problem. Are you certain this should work?
Thanks
bilybob said:
I tried flashing - that didn't work either. I did:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
Same problem. Are you certain this should work?
Thanks
Click to expand...
Click to collapse
try erasing cache.
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That seems to have worked.
Not sure if it was the cache erase or I believe I was missing the recovery from:
fastboot flash recovery recovery.img
I just had:
fastboot flash recovery.img
Anyway, I have re-flashed the SU pkg and all appears good now.
Thanks very much for the help from each of you.
khandelwalsiddharth said:
try erasing cache.
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
If I am not mistaken and read it wrong, SuperSu needs to be updated with the OTA 4.3 read this link http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/
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
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.
Anyone else noticing that the device now shows a swap partition? I used diskinfo (https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en) for this, and before updating to MOB30I, this swap partition wasn't there, it was included in my normal RAM.
EDIT: Here's a screenshot. http://i.imgur.com/GoLG6EP.jpg
Mine doesn't. Only flashed bootloader & system though.
Strange. I did a flashboot flash-all install of 30i and don't have a swap partition.
Sent from my Nexus 6 using XDA Labs
No swap partition here either. Also on MOB30I
Wow that's really strange. I flashed all of the img files one by one. And then noticed the swap partition. I didn't do anything out of the ordinary. ._.
H4X0R46 said:
Wow that's really strange. I flashed all of the img files one by one. And then noticed the swap partition. I didn't do anything out of the ordinary. ._.
Click to expand...
Click to collapse
What order maybe that matters
DR3W5K1 said:
What order maybe that matters
Click to expand...
Click to collapse
My exact steps.
fastboot flash bootloader bootloader[tab]
fastboot reboot-bootloader
fastboot flash radio radio[tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
then I rebooted, installed elite kernel, went back into bootloader and ran fastboot format userdata again to unencreypt, systemless rooted, and installed xposed. Those are my exact steps, this swap partition caught me by surprise.
H4X0R46 said:
My exact steps.
fastboot flash bootloader bootloader[tab]
fastboot reboot-bootloader
fastboot flash radio radio[tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
then I rebooted, installed elite kernel, went back into bootloader and ran fastboot format userdata again to unencreypt, systemless rooted, and installed xposed. Those are my exact steps, this swap partition caught me by surprise.
Click to expand...
Click to collapse
It's probably from elite having swap default. Or maybe you turned or on with kernel auditor
Could that mean possible Ubuntu touch support with Multi ROM?
Sent from my Nexus 6 using XDA-Developers mobile app
DR3W5K1 said:
It's probably from elite having swap default. Or maybe you turned or on with kernel auditor
Click to expand...
Click to collapse
I got with the dev for elite and he said it was in a recent update to the kernel, so it's the kernel that does this. Thanks guys!