Related
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
dray_jr said:
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
Click to expand...
Click to collapse
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Cozume said:
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Click to expand...
Click to collapse
as for the logo i am not sure i think you should be ok .
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go,
and anytime i flash something i always wipe the cache/davlik
dray_jr said:
and anytime i flash something i always wipe the cache/davlik
Click to expand...
Click to collapse
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Cozume said:
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Click to expand...
Click to collapse
you dont have too but it is recommended
dray_jr said:
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go
Click to expand...
Click to collapse
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Melarsa said:
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Click to expand...
Click to collapse
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Got it, that's what I'll do when the time comes. Thanks!
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
piccit said:
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
Click to expand...
Click to collapse
I thought it might be different because I'm rooted, and encrypted.
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
flashallthetime said:
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not using a custom ROM though.
fbiryujin said:
I'm not using a custom ROM though.
Click to expand...
Click to collapse
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
flashallthetime said:
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
So far no official update available to me even after flashing the stock image from Moto. My biggest goal here is to find a way to backup and restore nandroids from the encrypted phone.
Flash and relock Moto X manually
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
_slam said:
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
Click to expand...
Click to collapse
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
_slam said:
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
Click to expand...
Click to collapse
1) You don't need to do much. Revert the Entitlement hack you did, you need the one that came on the device, not a hacked one.
2) Flash the stock recovery back to your phone. You'll need the stock recovery to install the OTA. Just do it the same way you flashed TWRP to your phone but use the stock recovery.img file from the 4.4 .sbf ( http://sbf.droid-developers.org/download.php?device=0&file=5 )
You will NOT lose root flashing the stock recovery, you will NOT lose root taking the OTA.
After updating, use Xposed and the Moto Tether module for tethering instead of using a hacked version of the app.
shadowmonk36 said:
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
Click to expand...
Click to collapse
If you have the Dev edition from VZW, it's simple to install the OTA.
This is what I did as I had root and xposed installed.
1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard
2. Flash stock 4.4 recovery image via fastboot.
3. Flash 4.4 system image using mfastboot (must use mfastboot)
4. Boot into recovery
5. Apply update and selected the OTA zip.
6. Reboot
7. Power down and boot back into fastboot.
8. Flash TWRP, allow it to root, reboot.
9. Reinstall Xposed framework.
All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.
Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.
Sent from my Dev Edition Moto X
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
saman0suke1 said:
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
Click to expand...
Click to collapse
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
My Nexus 6 took 5.0.1 just fine, but my Nexus 7 does this same thing, running stock ROM/Bootloader/Recovery/etc. The ONLY thing done to it is the Fastboot OEM unlock, but I doubt that alone would stop it. I'm curious to know what resolves this ( other than downloading the factory image and flashing it without wiping the userdata )
Just got same error. I didnt even root phone, bought it today, it installed apps from backup of my previous Nexus 4 and OTA is failing.
cupfulloflol said:
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
Click to expand...
Click to collapse
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
saman0suke1 said:
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
Click to expand...
Click to collapse
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
cupfulloflol said:
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
Click to expand...
Click to collapse
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
saman0suke1 said:
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
Click to expand...
Click to collapse
I'm interested as well. Mine is rooted and I have encryption disabled, and I have TWRP on my phone. I tried to sideload the OTA update, but I can't get my phone to start sideload. I even flashed the stock recovery to get it to go, and no dice. What do I do next?
Anyone? I would appreciate the feedback, thanks!
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
cmh714 said:
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
Click to expand...
Click to collapse
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
saman0suke1 said:
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
Click to expand...
Click to collapse
If your doing from the PC you need to extract the zip file from within the image and then fastboot them. As for root, when you do it from fastboot I dont believe it matters as you will lose root anyway and need to re-root via flashing SuperSU.zip
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
naulsballs said:
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using XDA Free mobile app
saman0suke1 said:
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Click to expand...
Click to collapse
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
TOCS88 said:
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Click to expand...
Click to collapse
Try pulling your Sim card out and rebooting.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you're planning to stay rooted (meaning no OTA in future) system.img, boot.img and radio.img in any order.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you use fastboot, just run these commands in terminal (I used windows, so in order to flash using fastboot, put the image that you downloaded for the update in the same folder where you have fastboot and open a terminal there) you can rename the .img files to whatever you like and replace those name in the commands below:
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
Then reboot it:
fastboot reboot-bootloader
Then flash these:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And that's it. These commands are run while the phone is connected to the PC, you have to turn it on by pressing volume up + volume down + power.
Good luck.
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
bovineyard said:
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
Click to expand...
Click to collapse
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
cam30era said:
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
Click to expand...
Click to collapse
i think with root but encrypted will do the update
HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
cam30era said:
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
Click to expand...
Click to collapse
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
5.1.1 is NOT officially out for the nexus 6. it is in aosp though. thats two differing things. stock is on 5.1.
HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
The OTA package only looks at system.img and boot.img. Of course you need stock recovery to install it. And the "unroot" option inside SuperSU is insufficient. It leaves some traces around that will prevent the OTA from loading. Flash the stock system.img.
And afterwards, when unencrypting, you'll have to fastboot format userdata. Which will wipe your SDcard again.
HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
Bootloader status has no effect on the OTA.
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
ibraheeemz said:
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
Click to expand...
Click to collapse
As it says above, you cannot FLASH the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
danarama said:
As it says above, you cannot receive the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
Click to expand...
Click to collapse
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
ibraheeemz said:
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
Click to expand...
Click to collapse
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
danarama said:
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
Click to expand...
Click to collapse
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
ibraheeemz said:
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
Click to expand...
Click to collapse
No. Only factory reset or unlocking the bootloader loses data. System.img is the rom, flashing to /system. Boot.img is the kernel, flashing to /boot. if you flash these separately, userdata.img is not flashed to /data, so your /data partition remains in tact.
root doesn't touch /data either. Just /system
HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
How do you get root while leaving it encrypted?
Arfyness said:
How do you get root while leaving it encrypted?
Click to expand...
Click to collapse
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Evolution_Tech said:
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Click to expand...
Click to collapse
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Arfyness said:
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Click to expand...
Click to collapse
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
edit - this was a duplicate. i can't delete it.
Evolution_Tech said:
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
Click to expand...
Click to collapse
Oohhh, wait, so flash from fastboot, except flash SuperSU from TWRP? (update.zip style?) Is only the data partition encrypted then? If that's the case why are folks decrypting? Unlocking the bootloader requires it, but what is that required for?
And thank you loads BTW! I'm so far behind! I'm coming off 3 years of rooted, stable SGS3 stock, last updated to 4.1.2. There were no further stock updates that I wanted, (too many bugs) and everything was working so I left well enough alone.
(I probably would have messed about with CM and other roms, if I had not initially bricked the thing trying to put TWRP on... and had to send it for somebody to JTAG reprogram it. Thought about it several times, but never wanted to chance it again.)
Thanks again!
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot
Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.
prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot
Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!
Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!
Sesamechicken said:
Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?
Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.
Gus Ghanem said:
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?
Click to expand...
Click to collapse
Forgot to quote sorry
Sesamechicken said:
Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.
Click to expand...
Click to collapse
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.
Gus Ghanem said:
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.
Click to expand...
Click to collapse
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app
Sesamechicken said:
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app
Click to expand...
Click to collapse
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.
Gus Ghanem said:
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.
Click to expand...
Click to collapse
Just tried that to no avail.
Is there anyway to root without having a custom recovery?
Sesamechicken said:
Just tried that to no avail.
Is there anyway to root without having a custom recovery?
Click to expand...
Click to collapse
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks
Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Nevermind! I am so f****ng stupid!!!!
I NEVER ACTUALLY SELECTED USING UP VOLUME I ALWAYS CLICKED THE POWER BUTTON WHICH REBOOTED. I AM ACTUALLY SO STUPID.
Thanks anyways!
Sesamechicken said:
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks
Click to expand...
Click to collapse
Since we don't know for sure what's causing it not to boot, might as well flash the whole fimware, I think you can paste all the commands at once, or create a batch file in the firmware folder, flash.bat, shift+right-click, open command window here... type flash.bat
Or you can use RSD Lite
If/when you lose signal/data/wifi you can try flashing just the modems from stock:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn