Related
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
diamondx911 said:
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
Click to expand...
Click to collapse
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
phonic said:
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
Click to expand...
Click to collapse
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
diamondx911 said:
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
Click to expand...
Click to collapse
Understood, and "hacking" android, especially Google devices, is pretty easy once you know what you are doing. The reason I dislike toolkits is that it prevents people from understanding the process, which really is fairly easy to understand, and can complicate troubleshooting steps.
The bootloader can easily be unlocked and locked. It takes one command and it's done. In order to flash anything with fastboot, you need it to be unlocked. The problem is, when you do this, it factory resets the device. So if you inadvertantly relock it, your going to need to reset it to unlock it again.
Even without the toolkit, going from unopened stock Nexus7 to fully rooted, updated and custom firmware Nexus7 only takes maybe 10 minutes, and 9 minutes of that is waiting for it to finish doing the various steps (flashing, rebooting, etc.). The most time consuming part is, unless you have good backups, restoring all your apps and settings. Titanium Backup is the best tool (IMHO) for that.
But yeah, in this case, you're going to need to unlock/wipe again. However, you CAN backup your "sdcard" to your computer and push the files back to it after the wipe. That can be very time consuming depending on how much you have.
Hi, I know it may have been foolish of me to get the Dev edition and im not a dev but it's unlocked, more storage and i think it was the better choice.
With that being said, is there a way to root this device permanently? I see there's an HTC One toolkit but it seems to be only for the ones with the Bootloader locked. This bootloader is unlocked so is there a thread yall can direct me to in order to root and flash a custom rom?
I'd appreciate it Folks
stepinmyworld said:
Hi, I know it may have been foolish of me to get the Dev edition and im not a dev but it's unlocked, more storage and i think it was the better choice.
With that being said, is there a way to root this device permanently? I see there's an HTC One toolkit but it seems to be only for the ones with the Bootloader locked. This bootloader is unlocked so is there a thread yall can direct me to in order to root and flash a custom rom?
I'd appreciate it Folks
Click to expand...
Click to collapse
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
matt95 said:
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
Click to expand...
Click to collapse
Thank you! Awesome
matt95 said:
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
Click to expand...
Click to collapse
One more stupid question about Dev edition: will I be able to flash mods/apps from zip files using custom recovery, without rooting the phone/installing custom rooted ROM? There is a reason I don't want to root - my corporate mail will not work on rooted device, then I will need to use something like Voodoo OTA Root keeper and hide my root all the time, then restore it when I need, do what I need and after it I will need to re-install corporate email and re-enroll to company's server, in order to not get in trouble with company's Information Security, which I do not want.
I am not so interested in custom ROMs, but do interested in few mods and addons that will definitely come soon (e.g. separation of Ringtones sound level from Notification, battery charge percent on the battery icon in status bar, etc)
Thanks!
EugeneR said:
One more stupid question about Dev edition: will I be able to flash mods/apps from zip files using custom recovery, without rooting the phone/installing custom rooted ROM? There is a reason I don't want to root - my corporate mail will not work on rooted device, then I will need to use something like Voodoo OTA Root keeper and hide my root all the time, then restore it when I need, do what I need and after it I will need to re-install corporate email and re-enroll to company's server, in order to not get in trouble with company's Information Security, which I do not want.
I am not so interested in custom ROMs, but do interested in few mods and addons that will definitely come soon (e.g. separation of Ringtones sound level from Notification, battery charge percent on the battery icon in status bar, etc)
Thanks!
Click to expand...
Click to collapse
well i don't think so... if you do not want to be rooted you have to remain with the stock rom and i don't know if every mod is compatible with that
Root issues
matt95 said:
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
Click to expand...
Click to collapse
I did the same. I just flashed CWM Touch Recovery and Superuser, but AdAway disables every time I reboot and I can't get rid of the Google Bloatware and FB/Twitter - which I don't use. I tried deleting them using ES File Explorer, but they come back every time I reboot. Please help. I hate having the bloatware and knowing that it takes up almost 150 MB makes me mad!!!
/system has kernel protection and you need to flash either a kernel or rom that disables it.
Ah!
gunnyman said:
/system has kernel protection and you need to flash either a kernel or rom that disables it.
Click to expand...
Click to collapse
Ah! I see. Do you know of any kernel that I can safely flash and not break my phone? It's only a week old and I don't want to end up bricking it or something. Also, do you know if I can still receive OTA updates from HTC? Whenever they do come out, that is. Sorry to be asking such a noob-ish question..
Also, is that the same reason AdAway gets auto-disabled at every boot?
Faux123 has a great kernel, and yes the hosts file gets reset for the same reason.
gunnyman said:
Faux123 has a great kernel, and yes the hosts file gets reset for the same reason.
Click to expand...
Click to collapse
Can you please tell me what the potential issues are, if I flash the kernel? Also, please let me know about the OTA updates and if it'll work after rooting and/or flashing a new kernel. Thank you!
Flash the kernel known as elemental X. It seems to have zero issues, I've been running it for a while now and the only difference is I am fully rooted with this kernel.AS far as OTA updates..
well whenever you unlock the bootloader at HTC's website it will definitely reset a non developer edition phone to factory defaults and from there it will remove calculator and a couple of other apps so that HTC knows you're no longer boot loader locked and yes this will prevent OTA updates.
since yours came with an unlocked bootloader in theory you could just flash the kernel and from there when you install SuperSU you will be able to do anything you need to do. With SuperSU you can temporarily turn off root so that you can do things that would normally be prevented/notice that you are rooted.
The Redbox streaming video service app is an example, it will not work on rooted devices but if you go in the SuperSU app and turn on temporary un-root. Then you are able to load the app, watch a show then close the app and restore root all without rebooting..
IIHomieII said:
Flash the kernel known as elemental X. It seems to have zero issues, I've been running it for a while now and the only difference is I am fully rooted with this kernel.AS far as OTA updates..
well whenever you unlock the bootloader at HTC's website it will definitely reset a non developer edition phone to factory defaults and from there it will remove calculator and a couple of other apps so that HTC knows you're no longer boot loader locked and yes this will prevent OTA updates.
since yours came with an unlocked bootloader in theory you could just flash the kernel and from there when you install SuperSU you will be able to do anything you need to do. With SuperSU you can temporarily turn off root so that you can do things that would normally be prevented/notice that you are rooted.
The Redbox streaming video service app is an example, it will not work on rooted devices but if you go in the SuperSU app and turn on temporary un-root. Then you are able to load the app, watch a show then close the app and restore root all without rebooting..
Click to expand...
Click to collapse
Thank you for allaying my fears. I flashed the faux123 kernel because it was suggested "first!" Working fine now. I rebooted and the apps haven't come back after uninstalling them. Thank you so so much for educating me!
PS: How do I Thank you officially? Is there some thank button on here?
---------- Post added at 01:19 AM ---------- Previous post was at 01:05 AM ----------
IIHomieII said:
Flash the kernel known as elemental X. It seems to have zero issues, I've been running it for a while now and the only difference is I am fully rooted with this kernel.AS far as OTA updates..
well whenever you unlock the bootloader at HTC's website it will definitely reset a non developer edition phone to factory defaults and from there it will remove calculator and a couple of other apps so that HTC knows you're no longer boot loader locked and yes this will prevent OTA updates.
since yours came with an unlocked bootloader in theory you could just flash the kernel and from there when you install SuperSU you will be able to do anything you need to do. With SuperSU you can temporarily turn off root so that you can do things that would normally be prevented/notice that you are rooted.
The Redbox streaming video service app is an example, it will not work on rooted devices but if you go in the SuperSU app and turn on temporary un-root. Then you are able to load the app, watch a show then close the app and restore root all without rebooting..
Click to expand...
Click to collapse
Thank button found and clicked!
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
That's always a risk. Read playstore comments before installing anything.
Has nothing to do with being rooted or not...or boot loader state.
Sent from my Moto X cellular telephone...
Cozume said:
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
Click to expand...
Click to collapse
You could have asked at AC and I would answer it over there.
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified. I can flash custom recovery to your phone. Custom recovery give full root access to the phone. It is then easily possible to copy all your data from the phone and also disable the lock for your phone. Although if you encrypt your phone, then custom recovery will require the password to give access to the /data partition, which is where all the user datas are. I guess if someone is determine enough, then they can make an image copy of your phone and try to decrypt it.
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader. However, if the phone brick then you can't get back your data in the phone.
eksasol said:
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified.
Click to expand...
Click to collapse
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
eksasol said:
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader.
Click to expand...
Click to collapse
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Cozume said:
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
Click to expand...
Click to collapse
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system. Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Click to expand...
Click to collapse
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
If you have an older Android phone, you don't need to do anything except to enable USB Debugging and run a program to install root. But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection. But KitKat is much safer now.
You don't need root to install malware and virus to your phone. Just download an infected app or use unreliable app stores like Aptoide. Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Point I'm trying to make is, if the phone have unlocked bootloader, or even locked bootloader with custom recovery, and someone else have a hold of it, then all bets are off.
eksasol said:
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system.
Click to expand...
Click to collapse
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
eksasol said:
Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
Click to expand...
Click to collapse
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
eksasol said:
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
Click to expand...
Click to collapse
good to know!
eksasol said:
But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection.
Click to expand...
Click to collapse
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
eksasol said:
But KitKat is much safer now.
Click to expand...
Click to collapse
why is this?
eksasol said:
Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Click to expand...
Click to collapse
thanks, Amazon app store required that to be enabled to load apps from their app store.
Cozume said:
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
Click to expand...
Click to collapse
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
Click to expand...
Click to collapse
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA.
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
Click to expand...
Click to collapse
Yes. The actual component of root isn't the SuperSU app, but a 'su' binary. Without the SuperSU app, anything can have full fledged root access. You need SuperSU to control that access.
why is this?
Click to expand...
Click to collapse
For many reason, I'm not a developer so I can only talk about what I know and seen from a user perspective. It used to be that you can flash an exploited update.zip to modify the stock recovery of Android, in order to make it ignore the package signatures, so the recovery could flash any package without the correct signature. Now there are no such exploits for latest stock recovery. With USB Debugging enabled in Android 4.3 or newer, it would not even allow access when connected to a PC unless you accept to trust that PC in a pop up dialog in the phone, I'm not sure if it's mean the phone is totally invulnerable to exploits (like memory overflow), you'll have to ask someone smarter. Also apps like Framaroot that I just linked won't work anymore.
eksasol said:
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA. My guess is if you tried it with modified logo it will either fail or overwrite it.
Click to expand...
Click to collapse
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Cozume said:
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Click to expand...
Click to collapse
You already gave me enough thanks at AC.
eksasol said:
You already gave me enough thanks at AC.
Click to expand...
Click to collapse
what is your user name there?
Cozume said:
what is your user name there?
Click to expand...
Click to collapse
someguy
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Sent from my Moto X cellular telephone...
eksasol said:
someguy
Click to expand...
Click to collapse
ok great!
kj2112 said:
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Click to expand...
Click to collapse
I am just trying to understand how all of this works.
Okay one thing why are you trying to unlock the bootloader without rooting?? Or did I read everything wrong? And yes unlocking the bootloader allows you to write to every partition of the phone. Except when HTC and you're s-on you have to manually flash the boot.img via fastboot. But with moto. There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty. Three it can disable functions on your phone like features, camera options I think and yeah etc. But if you follow instructions you won't have any problems ever rooting or shouldn't if you semi have a brain and know how to follow instructions if not well you can somewhat brick :$ I don't mess with moto much but I have. Sorry this thread was in my latest and scrolling through xda. Lol. You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
edit: link: http://forum.xda-developers.com/showthread.php?t=2575586&page=2
pball52998 said:
Okay one thing why are you trying to unlock the bootloader without rooting??
Click to expand...
Click to collapse
I rooted but a friend of mine is unlocked but not rooted. She wanted to be unlocked because it wipes your device so wanted to do it before she got the phone all set up. She is afraid of rooting. Anyhow, maybe she shouldn't have unlocked but she did.
pball52998 said:
There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty.
Click to expand...
Click to collapse
She has the dev ed so it doesn't void her warranty. And she may want to Wifi tether in the future so I told her she needs to unlock and root for that so get the dev ed. She did and unlocked but is afraid to go any further.
pball52998 said:
You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Click to expand...
Click to collapse
It increases the phone's resale value to unlock it.
eksasol said:
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
Click to expand...
Click to collapse
I thought I saw a thread where someone could relock the Moto X bootloader.
And what about this?
Re-Lock Your Bootloader
It should just be a command like fastboot_oem_lock or something but idk. And two if she has the dev edition. Root that thing!!! XD that's what it's for!! Just install twrp via goo manager. Wipe factory reset all that good stuff. After making a back up. Notice after backing up. Then flashing rom and gapps In that order. I mean its a lot easier than htc rezound or htc one, htc in general and such lol.
Sent from my crappy apple iPad.....
pball52998 said:
Wipe factory reset all that good stuff. After making a back up.
Click to expand...
Click to collapse
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.
And I don't have a backup, but do I really need one if I can flash the factory images?
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
ice_cold17 said:
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
Click to expand...
Click to collapse
If you're unlocked, rooted and have TWRP, why not just install custom ROM? Otherwise you can download factory image that you want, unzip and flash images individually via fastboot. Just don't flash user data and you won't loose data.
Just use the toolkit to 100% flash back go stock. It will unroot and reinstall stock recovery. Just remember to always keep USB debugging on and keep that boot loader unlocked. Once your back to the out box state you should be v able to receive ota. Or just use toolkit to flash the new stock image for your device. Ends with I.
Sent from my Nexus 6
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
ice_cold17 said:
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
ice_cold17 said:
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
Click to expand...
Click to collapse
I don`t erase and flash userdata usualy, its good to erase cache and then flash cache cache.img. A data factory reset after the procedure is adviced however for preventing fc`s and such.
So in the end is should wipe anyway? Oh well I was trying to avoid that only as a last resort. It wouldn't even let me unroot through the toolkit for some reason...
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
fubofo said:
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
Click to expand...
Click to collapse
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Evolution_Freak said:
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Click to expand...
Click to collapse
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
fubofo said:
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
Click to expand...
Click to collapse
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Evolution_Freak said:
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Click to expand...
Click to collapse
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
rootSU said:
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
Click to expand...
Click to collapse
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
OK, let me ask this, what is your current software? 5.0 or 5.0.1?
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
rootSU said:
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
Click to expand...
Click to collapse
Thank you sir for helping!
Evolution_Freak said:
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
Click to expand...
Click to collapse
Thanks @Evolution_Freak I'll give a shot at flashing just the stock recovery, unrooting and trying the OTA
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
There is a way, I believe, by running TWRP on your PC and flashing SuperSU from your PC. However, it's not a recommended method as you will have no way of backing up. Also, if you get caught in a bootloop, you won't be able to recover without a custom recovery.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
and you don't have to "hack" a nexus as well, as google provided an easy way to unlock your bootloader and to obtain root. if you just got your nexus a few days ago, just unlock the bootloader and root it. loosing a few days of information is more than worth it for root. don't waste your time worrying over a few days of data.
Can be done but not recommended.
adb backup/restore can save a little bit of information for you, but I wouldn't go in expecting it to save everything
Sent from my Nexus 6
What did you set up? You can back up your messages, and your apps will re-download. Your photos are already syncing to Google. If it's not rooted, I can't imagine you've done that much customization.
Lesson learned: unlock should ALWAYS be the very first step you do on a new phone.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
danr93 said:
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
Click to expand...
Click to collapse
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
danarama said:
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
Click to expand...
Click to collapse
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
danr93 said:
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
Click to expand...
Click to collapse
Good stuff. Once rooted, Flashify is a great tool to flash TWRP. With the nexus 5, you could unlock the bootloader with an app that didnt wipe everything, which was great, but Nexus 6 doesn't allow that, but always do go to settings > developer options > OEM Unlock (Set to enable). Without this set, you cannot unlock the bootloader from fastboot. Also, side note, developer options doesn't show up until you go into Settings > About phone then tap "Build number" several times to make the option visible. Think its 7 times.
It's interesting saying that you need kingroot to remain on the device. Thats a bit of a pain. Does it install SuperSU or not? If not, might be interesting to see what happens if you install the SuperSU app from Play - whether it allows it to be removed then.
My preferred method however is definitely unlock the BL, fastboot flash TWRP, From TWRP flash SuperSU zip (or rooted ROM).
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
arcooke said:
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
Click to expand...
Click to collapse
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
danarama said:
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
Click to expand...
Click to collapse
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
arcooke said:
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
Click to expand...
Click to collapse
That's lollipop for you. It changed everything.
It's still really simple.
Good to know. Thanks for the info!