My nexus 6 is running on 6.0 MRA58N and before i was on lolipop 5.0.1 and i tried to root my device and it apparently didnt work i did some major mistakes i used NRT to do so and while i was installing supersu my device rebooted and gave me an error of my device being corrupted and something with trust and may not work properly. and then it rebooted into my device. All i want now is to have a fresh new 6.0 device
and i am a little noobie i need help to fix my phone, and also before i had nethunter installed and since the update i have all my files in there and i want to delete them i have taken a backup with titaniumbackup and i just want to get rid of everything and start with a fresh new 6.0 and root it and thats it.
thank you in advance.
scruffyhere said:
My nexus 6 is running on 6.0 MRA58N and before i was on lolipop 5.0.1 and i tried to root my device and it apparently didnt work..........
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059493
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
Corrupt message just means that the system is modified, doesn't necessarily mean it won't always boot.
You need to use the latest Supersu due to the changes in marshmallow.
Related
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
JohnnySSH said:
Hi,
I've just upgraded the OS of my HTC One to 4.4 with Sense 5.5 and rooted the handset.
I took the majority of information and downloads from here:
http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/
while the rooting stuff I grabbed from here:
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
So ok this is my 3rd OS upgrade with root so in a basic sense I did this:
- Updated TWRP to version 2.7.x
- Used TWRP recovery WIPE option to format / (root)
- Installed the 4.4 stock ROM from above link
- TWRP then asked me if I would like to root the device and so I said ok to that
- Booting into the OS everything was fine and I had the SU-Root icon in the Apps menu
I'm not sure what happened if the battery got drained or so but in anycase after a restart the handset was no longer rooted??
As I have the 2.65 SU-ROOT Zip file on my storage partition I went back to TWRP and Install then clicked on the Zip file and re-rooted the device; then wiped the cache and booted back into the OS.
For some reason now the phone isn't able to be rooted at all? I am pretty sure I had similar behavior with Android 4.3, though the initial stock build was absolutely fine.... I think I managed to get from 4.1 to 4.2 successfully.
Will I need to format the handset again then re-install the ROM and re-root or is something else going on which I'm unaware of??
I've also noticed that the device becomes un-rooted each time the battery goes low or dies for some reason... a persistent root would be nice as I have many apps needing full root access; not to mention being able to work with the full Android system too.
Would anyone be able to suggest anything? Thanks!
Click to expand...
Click to collapse
I think there is an update for supersu
please google it
if yes than move it to your phone and flash it in the recovery
Thanks I managed to find version 1.94 which worked fine:
http://download.chainfire.eu/396/
Hello all,
i rooted my nexus 6 and now that android 6.0 has been release i can't install the upgrade. My phone shows there is a system upgrade available. I have clicked to download the upgrade. Now its showing that a system upgrade has been downloaded and verified. Once i click on install update, it reboots to the teamwin. And to be honest, i don't really know if its taking the updated or how i can upgrade if possible.
can someone help me please?!!!!
Same answer every time. You can't get the OTA if you're rooted.
Options are :
- flash factory image (see sticky roll-up in general)
- flash a pre-rooted zip from recovery.
if you dont want to lose your data. just flash system.img, boot.img and recovery.img of your current build.
you can extract the images from the factory image...
Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it, as I did with my Nexus 10 a couple of years ago.
Your best bet is to use Wugfresh's Nexus Root Toolkit (NRT). Since this is a major upgrade you can't use the "no wipe" option, so you'll lose any data that you haven't backed up first - photos, etc. - so do that before you do anything. Also take a TWRP backup of your current ROM and copy it to your PC so that at least you can recover to where you are now. NRT also has a backup option.
If you tell NRT that your current ROM is MRA58K (Android 6.0) and then tell it to flash stock and unroot, it will pull down all the required files before applying them to your Nexus. You can then re-root if you want to. It's a beautifully-engineered program, pretty well foolproof if you follow the instructions and choose the right ROM for your device.
dahawthorne said:
Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it
Click to expand...
Click to collapse
It cant get to that stage any more.
Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.
dahawthorne said:
Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.
Click to expand...
Click to collapse
OTA zips used to check individual files in system to ensure they matched before updating. It checks either md5 or sha hash. It didn't take account of every file or even files added by the users. so upgrading could cause issues.
Now, it checks the md5/hash of the entire system, which means all files are taken into account.. It will not flash of anything is changed.
Thanks - happy to roll you over to 19,400...
Hi,
So i have a Moto G 2 XT-1068 with Android 5.0.2 and system version 22.21.28.titan_retaildsds.retaildsdsall.ex.03 reteu.
I rooted it and installed Xposed.
Since some days, my phone notify me that there is a new (official) update avalaible :
22.56.3.en.03
My first reflex was to post in the Xposed forum :
I have a Motorola Moto G 2nd edition (2014 XT-1068) with Android 5.0.2 and these xposed versions installed :
XposedInstaller_3.0_alpha4.apk
xposed-v75-sdk21-arm-1
This morning, my phone notify me that there is a newsoftware update available :
22.56.3.en.03
Can i update ?
Will Xposed still running or do i have anything to do before or after update ?
Click to expand...
Click to collapse
then :
Yes i'm rooted (i didn't know i could install exposed without root ?!) and i ask the question to rooted users : what is the recommended behavior to have when we are rooted and there is an official update like this one ? Should i ignore it ? Should i wait ? Should i update (with one of your solutions) ?
Click to expand...
Click to collapse
and this is the reply i had :
You'll have to ask how an OTA works for that in your device forum.
For Google Android (untouched by OEM) in Kitkat, OTA used to check each important file individually and if one was modified, OTA would fail. This did not check all existing files or added files such as root, so as long as you uninstalled Xposed properly (restoring the original app_process files etc) then an OTA would be fine.
Since Lollipop, OTA checks the /system partition as a single item so any modification in any file, or any additional file will make the OTA fail. In which case, the only way to update would be to flash a stock ROM.
You will need to find out in your device forum which of these applies to your device.
Click to expand...
Click to collapse
So this is it, i make a post in this Moto G 2014 forum
Doing the OTA will most likely delete the XposedBridge.jar so you will have to flash it again.
Else the Xposed app will still be available but the Framework won't be installed.
If it doesn't update because the /system partition has been modified, you'll have to flash the whole rom to update.
Ok, so i can try without risk ?
And what about my root ?
nonobio said:
Ok, so i can try without risk ?
And what about my root ?
Click to expand...
Click to collapse
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Hi
TheKill69 said:
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Click to expand...
Click to collapse
Ok.
Seriously said:
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Click to expand...
Click to collapse
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
nonobio said:
Hi
Ok.
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
Click to expand...
Click to collapse
You might have to flash the whole stock firmware back to get the stock recovery. Big waste of time.
Then rooting back means using CF Auto Root Commands again..
You have to update to it though if you want Android 6.0.
Since it won't be soon, you rather go for CM13 once it gets really stable.
Also by the way, Xposed is already supported on MM.
Thanks for these precisions.
So if i can resume : a custom rom is easier for enjoy Android updates than just Xposed.
Hi,
Can you confirm :
For someone searching advanced features like customize status bar, quick settings, shutdown menu, hardware buttons, etc : customs roms and "stock rom + exposed" are two solutions. BUT, for someone searching these same advanced features but also keep his device up to date : custom rom is really a better solution. Isn't?
I was happy when i discovered xposed as it seemed to be a easier process that flashing a custom rom, but i didn't know that i couldn't update easily..
So, what is the advantage to use xposed instead of custom rom?
Hi,
I am always thinking if i will update my stock rooted xposed rom, or if i will install a custom rom prerooted like Cyanogen mod (o have easier future updates).
i have some questions :
1- Is it possible to install xposed and modules on a custom rom like cyanogen mod ? I think yes but can you confirm ?
I know that CM come with inbuilt tweaks but i discover some great xposed module i would continue to use, even if i install CM.
2-If i keep my stock rooted xposed rom, and don't make this "little" Android 5 OTA update, will be i notified for "Android 6" ?
(i don't want to lose my time to reflash my rom, reroot mydevice, etc.., just for a little update, but i could do that for a more important update like Android 6...
3- We are agree that if i flash a custom rom like CM, it will resolve my "ota update" problem, cause there won't be "Motorola OTA" anymore, but there will be CM updates easy to make, isn't ? If yes, what could be the advantage to use stock rom rooted + xposed vs custom rom + xposed ?
Thanks
Good Morning Everyone! I decided to open this discussion hoping someone could help me solve or at least understand the problem I have been having on my Nexus 6 with Android N Preview. So, I have the Nexus 6 since April and I got it from a friend who sold it to me. At that moment the phone was already enrolled in the Beta Program, and was running one of the first previews. But here came the problem. In fact I wanted to unenroll the phone but when I enter the Beta Program page, my Nexus does not appear as eligible device nor I can unenroll it from there. I looked at Device Manager and it shows my Nexus 6, but I actually could not do anything to unenroll it. I tried flashing a Marshmallow build with NRT but as soon as I turn on my phone, an annoying notification shows up, saying I can update to the N preview. So, how can I try to uneroll my Nexus 6? My friend says he is not able to do it for me, cause he doesn't see the device on his account anymore. What do you suggest me to do?
Thanks in advance, guys!
Here is an idea.
When NRT is used Twrp-recovery is installed.
Copy a lite stock rom in 'zip-format' to internal memory. Or download it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Reboot in recovery and wipe the system partition and caches.
Still in Twrp-recovery - Flash the 'zip' with lite stock rom.
Reboot.
NLBeev said:
Here is an idea.
When NRT is used Twrp-recovery is installed.
Copy a lite stock rom in 'zip-format' to internal memory. Or download it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Reboot in recovery and wipe the system partition and caches.
Still in Twrp-recovery - Flash the 'zip' with lite stock rom.
Reboot.
Click to expand...
Click to collapse
Thanks for your tips, man! I have some questions about: with this procedure I'm going to install a custom ROM, but if I wanted to go back to latest official MM build and flash it with NRT, will be the problem solved in the same way in your opinion or will I get the notification about the preview again? What if I try to access with another different account after that in your opinion?
Ste293919 said:
.... if I wanted to go back to latest official MM build and flash it with NRT, will be the problem solved.....
Click to expand...
Click to collapse
You need to delete the current account and do a factory reset.
For going back to stock there is a tutorial,
http://forum.xda-developers.com/showthread.php?p=57063390/
So I managed to go back to android MM after enteting a new account and unenrolling my Nexus 6 from Beta Program. Now everything seemed fine but then after I updated back with the OTA I received, I noticed my device has still July Security patch. I thought Google would have sent me September ones, so I tried to check manually and waited a whole day, but nothing happened. Coukd it be a problem related to bad installation in your opinion? Do you suggest me to restore September build through NRT?
Thanks for all your help man, I owe you and thanks you for your time!
Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!
KyleStilkey said:
Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!
Click to expand...
Click to collapse
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here
mrmazak said:
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here
Click to expand...
Click to collapse
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.
KyleStilkey said:
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.
Click to expand...
Click to collapse
Will be redoing the patch again and making not pre-rooted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.
mrmazak said:
Will be redoing the patch again and making not predicted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.
Click to expand...
Click to collapse
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.
KyleStilkey said:
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.
Click to expand...
Click to collapse
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom
mrmazak said:
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom
Click to expand...
Click to collapse
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.
KyleStilkey said:
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.
Click to expand...
Click to collapse
I have seen it mentioned that Google + does not work on 8.3 in general not just this modified one.
That recovery is the one I use and has advantage over the other one (lopestom's versio) in that in recovery you can use external sdcard and also mtp connection.