Related
when flashing the build for cm7 could i do it using ClockWork Mod v2.5.1.2 or is there a special recovery i need to flash before trying to put cm7
reason i ask is because on the MT4G you need to flash recovery to v3.0.0.0+ before flashing cm7 build
if someone could please responf on this thread or pm me would be awesome!
Thank You
pretty sure you can just flash it the regular way.. wouldn't see why not as the gingerbread roms are flashed through the regular cwm also
bomber889 said:
pretty sure you can just flash it the regular way.. wouldn't see why not as the gingerbread roms are flashed through the regular cwm also
Click to expand...
Click to collapse
my next question, i tried rooting the phone using the unrevoked program but after it tries running the root it come with an error
"ERROR:Failed to get root. Is your Firmware too new?"
does anyone know anything about this?
Jlom117 said:
my next question, i tried rooting the phone using the unrevoked program but after it tries running the root it come with an error
"ERROR:Failed to get root. Is your Firmware too new?"
does anyone know anything about this?
Click to expand...
Click to collapse
well sounds like you already have the latest Clockwork installed? if so, I believe UnRevoked comes with a downgraded version so I would try and downgrade the version on your phone see if it helps
Well I'm able to go into recovery it's just when I try and use rom manager or titanium backup it comes up saying the phone doesn't have root privileges so I thought it wasnt rooted properly. If I'm rooted because I can go into recovery and it shows s= off in h boot then how do I fix the privileges part of it all?
Sent from my HTC Glacier using XDA App
Jlom117 said:
Well I'm able to go into recovery it's just when I try and use rom manager or titanium backup it comes up saying the phone doesn't have root privileges so I thought it wasnt rooted properly. If I'm rooted because I can go into recovery and it shows s= off in h boot then how do I fix the privileges part of it all?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This happened to me after I used unrevoked. It ran successfully, I tested w/ rom manager and it worked. I then rebooted a few minutes later and tried using several other root apps and none could obtain root privelages. So, I flashed a custom ROM (cyanogen 6.1) then had full root access again. Maybe that will help?
pokedroid said:
This happened to me after I used unrevoked. It ran successfully, I tested w/ rom manager and it worked. I then rebooted a few minutes later and tried using several other root apps and none could obtain root privelages. So, I flashed a custom ROM (cyanogen 6.1) then had full root access again. Maybe that will help?
Click to expand...
Click to collapse
ok cool ill try that! THANKS!
sounds like superuser isn't installed or you aren't letting it have privileges
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
sounds like superuser isn't installed or you aren't letting it have privileges
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
ok everything went through for the root and privileges, now im having an issue flashing cm7..... is there something special i need to do to flash it?
when i try flashing through recovery using 2.5.1.2 it aborts the installation please help, ive been trying to this for my gf for the passed 2 days.
Thanks
EDIT: still same issue, what do I do to fix?
The most peculiar thing happened after I applied today's JWR66Y update.
Prior to the update my GNex was running stock 4.3, rooted with SuperSU, and TWRP recovery was installed. So I flashed back to stock recovery and used the SuperSU app option for "Full unroot" in preparation to apply the OTA update.
Instead of letting the system do it, I copied the downloaded zip file from cache to my PC and used ADB sideload. Then I used fastboot to flash TWRP. From TWRP I flashed UPDATE-SuperSU-v1.51.zip
Here's the peculiar part. When I rebooted I didn't have root. The SuperSU app appeared as installed under Apps, but there was no icon in the app drawer. So I went to Google Play and installed SuperSU from there. After that everything was back to normal.
I never saw this happen before. Out of curiosity does anyone know why? I'm thankful it was so simple to fix but I'm scratching my head.
Sent from my Nexus 7 using xda app-developers app
Mine did something strange as well, but different than yours. I'm also running stock 4.3, rooted with SuperSU, and TWRP. For me it downloaded and installed the update then booted into TWRP recovery. After that finished doing something automatically it asked if I wanted to fix root, which I did. The phone booted back up and it's back on JWR66V and when I check for updates it says there aren't any. Still have root though.
Raugturi said:
Mine did something strange as well, but different than yours. I'm also running stock 4.3, rooted with SuperSU, and TWRP. For me it downloaded and installed the update then booted into TWRP recovery. After that finished doing something automatically it asked if I wanted to fix root, which I did. The phone booted back up and it's back on JWR66V and when I check for updates it says there aren't any. Still have root though.
Click to expand...
Click to collapse
Put stock recovery and the update should work. Then you can put TWRP back.
unsought spendsP
sordna said:
Put stock recovery and the update should work. Then you can put TWRP back.
Click to expand...
Click to collapse
Thanks. I'll try that once I can find somewhere to download the update (or whenever it decides to show up again.
Raugturi said:
Thanks. I'll try that once I can find somewhere to download the update (or whenever it decides to show up again.
Click to expand...
Click to collapse
Don't answer "Yes" to that question. Then flash latest compatible supersu. Do you have root then?
a manta sent this.
Raugturi said:
Thanks. I'll try that once I can find somewhere to download the update (or whenever it decides to show up again.
Click to expand...
Click to collapse
You can download the update zip file from here:
http://www.droid-life.com/2013/08/2...ta-updates-for-the-nexus-7-hspa-galaxy-nexus/
I just did it for my Nexus 7, followed the same steps described for my GNex, and the same thing happened haha. Oh well, easy enough to fix but I'm still wondering why flashing the UPDATE-SuperSU-v1.51.zip didn't install the app.
Sent from my Nexus 7 using xda app-developers app
sordna said:
Put stock recovery and the update should work. Then you can put TWRP back.
Click to expand...
Click to collapse
That was always enough for me with prior updates, too (before 4.3) but this update couldn't be applied without unrooting. It threw a Status 7 error and "Installation aborted". The moment I unrooted, the update installed without issue.
Sent from my Nexus 7 using xda app-developers app
beekay201 said:
Don't answer "Yes" to that question. Then flash latest compatible supersu. Do you have root then?
a manta sent this.
Click to expand...
Click to collapse
Did you mean to quote someone else?
Please if i may ask...is twrp better than cwm? What r d pros n cons
Sent from my Galaxy Nexus using Tapatalk 4
Another question, i don't have the stock recovery. img file from jwr66v now google images only show jwr66y..will extracting recovery.img from this to flash before update work? Since I'm still on jwr66v? Or csn u pls upload the recovery. img for gsm yakju. Thanks
Sent from my Galaxy Nexus using Tapatalk 4
David said:
Another question, i don't have the stock recovery. img file from jwr66v now google images only show jwr66y..will extracting recovery.img from this to flash before update work? Since I'm still on jwr66v? Or csn u pls upload the recovery. img for gsm yakju. Thanks
Click to expand...
Click to collapse
Instead of accepting the OTA, install the zip file efrant posted here:
http://forum.xda-developers.com/showpost.php?p=44886292&postcount=102
it has the recovery dependency removed, so you can keep your custom recovery. Copy the zip to your sdcard, rename to update.zip and install via either CWM or TWRP.
Thanks.. Will do that and give a report. :thumbup::thumbup:
Sent from my Galaxy Nexus using Tapatalk 4
I downloaded the file..from the link above, renamed to update.zip, got into cwm. Hit apply...didn't work..gave a systsm 7 error..somethijg about build.prop and a directory/file not found in d package
Update:
Then copied my ota from cacbe n flashed thru cwm, toggled file verification off. It worked a bit then system 7 again but this time rebioted like someone mentioned above as though it was fully updated.. Ie upgrading apps etc..but after all it was stil jwr66v. So now i need d stock recovery.img file i guess.. Can someone please upload
Update 2:
As many have already stated...i went into supersu app..full unroot, rebooted into cwm using the original ota from cache( which i had copied into clockwork folder) flashed it successfully, then flashed supersu 1.51 which i also put in d above folder. Rebooted and now I'm rooted on jrw66y..last thing was to install the supersu app from playstore. Hope it helps
Sent from my Galaxy Nexus using Tapatalk 4
Raugturi said:
Mine did something strange as well, but different than yours. I'm also running stock 4.3, rooted with SuperSU, and TWRP. For me it downloaded and installed the update then booted into TWRP recovery. After that finished doing something automatically it asked if I wanted to fix root, which I did. The phone booted back up and it's back on JWR66V and when I check for updates it says there aren't any. Still have root though.
Click to expand...
Click to collapse
Raugturi said:
Did you mean to quote someone else?
Click to expand...
Click to collapse
Nop, quoted the "wrong" post.
a maguro sent this.
David said:
...then flashed supersu 1.51 which i also put in d above folder. Rebooted and now I'm rooted on jrw66y..last thing was to install the supersu app from playstore.
Click to expand...
Click to collapse
Which brings me back to my original question. Why does the SuperSU app have to be installed from Google Play if UPDATE-SuperSU-v1.51.zip is installed from recovery? All of the system su files are there, just not the app. Isn't this a bit peculiar?
Sent from my Nexus 7 using xda app-developers app
Yeah
Sent from my Galaxy Nexus using Tapatalk 4
I got the OTA. I did "full unroot" in SuperSU. Isntalled the OTA, TWPM automatically installed the update.zip.
But now my device in unrooted and when i want to reboot into recovery in order to flash SuperSU i get the android logo with the exclamation mark! What to do?
plaktoets said:
I got the OTA. I did "full unroot" in SuperSU. Isntalled the OTA, TWPM automatically installed the update.zip.
But now my device in unrooted and when i want to reboot into recovery in order to flash SuperSU i get the android logo with the exclamation mark! What to do?
Click to expand...
Click to collapse
reflash twrp in fastboot.
i bet you used a toolkit to root didnt you?
Zepius said:
reflash twrp in fastboot.
i bet you used a toolkit to root didnt you?
Click to expand...
Click to collapse
No, initially I rooted by flashing supersu.
Flashing TWRP did the trick, thanks.
Nexus 4 did the same
CatThief said:
The most peculiar thing happened after I applied today's JWR66Y update.
Prior to the update my GNex was running stock 4.3, rooted with SuperSU, and TWRP recovery was installed. So I flashed back to stock recovery and used the SuperSU app option for "Full unroot" in preparation to apply the OTA update.
Instead of letting the system do it, I copied the downloaded zip file from cache to my PC and used ADB sideload. Then I used fastboot to flash TWRP. From TWRP I flashed UPDATE-SuperSU-v1.51.zip
Here's the peculiar part. When I rebooted I didn't have root. The SuperSU app appeared as installed under Apps, but there was no icon in the app drawer. So I went to Google Play and installed SuperSU from there. After that everything was back to normal.
I never saw this happen before. Out of curiosity does anyone know why? I'm thankful it was so simple to fix but I'm scratching my head.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have a Nexus 4 and my device did exactly the same after updating from 4.2.2 to 4.3(jwr66v).. Do not know the reason.. But after downloading the app from Play Store, things are working fine.. I suspect the Full Unroot option in SuperSu to be the culprit..
After some days ( and updates) on CM13 my Superuser binary is outdated.
So i flashed the newest SuperSu from chainfire (2.74 i think)
But the message appears again.
The update in the SuperSu APP didn't work, also i can Boot in TWRP in the APP.
Has anybody a solution for this Problem ?
Thank you
Sincerly
Lorddoener
Sent from my Wileyfox Swift using XDA-Developers mobile app
Lorddoener said:
After some days ( and updates) on CM13 my Superuser binary is outdated.
So i flashed the newest SuperSu from chainfire (2.74 i think)
But the message appears again.
The update in the SuperSu APP didn't work, also i can Boot in TWRP in the APP.
Has anybody a solution for this Problem ?
Thank you
Sincerly
Lorddoener
Sent from my Wileyfox Swift using XDA-Developers mobile app
Click to expand...
Click to collapse
Perhaps try to flash a recent SuperSU zip from TWRP?
Dior DNA said:
Perhaps try to flash a recent SuperSU zip from TWRP?
Click to expand...
Click to collapse
I flashesd the newest SuperSu with twrp
(2.74) but the message still appears and i don't have root
Sent from my Wileyfox Swift using XDA-Developers mobile app
Lorddoener said:
I flashesd the newest SuperSu with twrp
(2.74) but the message still appears and i don't have root
Sent from my Wileyfox Swift using XDA-Developers mobile app
Click to expand...
Click to collapse
Oops, sorry, I misread you already flashed with twrp
Perhaps try another version? (like v2.65)
Dior DNA said:
Oops, sorry, I misread you already flashed with twrp
Perhaps try another version? (like v2.65)
Click to expand...
Click to collapse
also tried that, but i hasn't success
Sorry for my English [emoji16]
Sent from my Wileyfox Swift using XDA-Developers mobile app
Lorddoener said:
also tried that, but i hasn't success
Sorry for my English [emoji16]
Sent from my Wileyfox Swift using XDA-Developers mobile app
Click to expand...
Click to collapse
well : I am also having trouble rooting COS 13 ...
I received a (new) Swift for a friend and when I flash SuperSU v2.46 from recovery, the phone reboots and only shows (forever):
Code:
cyanogen
mod
ready
I tried several custom recoveries (twrp 2.7 and 3.0 and CM-13.0).
To recover I needed to fastboot re flash stock.
Note that I could once root COS 12.1 on another Swift phone for another friend just fine.
So this seems a 13.0 specific issue. Perhaps how SuperSU handles Android 6.
Good news is I can take a TWRP backup. But I would also want to be
able to take Titatium Backup and do other things that require root.
Does this ring a bell?
Thanks for enlightening me how to root COS 13.0
Dior DNA said:
well : I am also having trouble rooting COS 13 ...
I received a (new) Swift for a friend and when I flash SuperSU v2.46 from recovery, the phone reboots and only shows (forever):
Code:
cyanogen
mod
ready
I tried several custom recoveries (twrp 2.7 and 3.0 and CM-13.0).
To recover I needed to fastboot re flash stock.
Note that I could once root COS 12.1 on another Swift phone for another friend just fine.
So this seems a 13.0 specific issue. Perhaps how SuperSU handles Android 6.
Good news is I can take a TWRP backup. But I would also want to be
able to take Titatium Backup and do other things that require root.
Does this ring a bell?
Thanks for enlightening me how to root COS 13.0
Click to expand...
Click to collapse
Try the su beta from here
https://download.chainfire.eu/740/supersu/beta
robin0800 said:
Try the su beta from here
https://download.chainfire.eu/740/supersu/beta
Click to expand...
Click to collapse
Unfortunately this does not make a difference, system boot stays on cyanogen/mod/ready logo.
I had to recover back to TWRP backup.
Anyone who successfully rooted COS 13.0 please raise a hand ...
update (1)
I tried to hack my way around by putting recent CM 13.0 su binary in mounted system/xbin (+ symbolic link in system/bin) via adb shell TWRP, and now SuperSU starts, but: then finally I end up same situation as Lorddoener : supersu fails to update su (normal and twrp)...
Again: any help / ideas welcome
update (2)
One needs systemless SuperSU... starting from (stable) UPDATE-SuperSU-v2.65-20151226141550.zip
I'm talking about CM13 not about CS13 !!!!!( i wrote it in my first post)
Sent from my Wileyfox Swift using XDA-Developers mobile app
Lorddoener said:
I'm talking about CM13 not about CS13 !!!!!( i wrote it in my first post)
Sent from my Wileyfox Swift using XDA-Developers mobile app
Click to expand...
Click to collapse
I am sorry and apoligise
I downloaded and flashed the OOS 3.2.0 zip once it was posted online but pulled by oneplus. I have been getting a notification for a system update for the past few days. As previously mentioned I'm running OOS 3.2.0, I'm rooted(systemless... Obviously) and I am using the official version of TWRP.
Is it safe for me to run the OTA? I'm also encrypted if that matters.
I've attached a few screenshots below...
TIA,
MeeGz
If you are rooted OTA will fail to install.
Sent from my SM-T810 using XDA-Developers mobile app
danyvw said:
If you are rooted OTA will fail to install.
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
danyvw - that is what I suspected. Is there any way to flash the OTA file? I know that xposed needs to be turned off... I'm not sure what else I should do.
- MeeGz
MeeGz said:
danyvw - that is what I suspected. Is there any way to flash the OTA file? I know that xposed needs to be turned off... I'm not sure what else I should do.
- MeeGz
Click to expand...
Click to collapse
The best option is to download the whole 3.2.1 firmware, flash thru TWRP and immediately flash Supersu, clean Cache and Dalvik Cache and voila!
Sent from my SM-T810 using Tapatalk
MeeGz said:
I downloaded and flashed the OOS 3.2.0 zip once it was posted online but pulled by oneplus. I have been getting a notification for a system update for the past few days. As previously mentioned I'm running OOS 3.2.0, I'm rooted(systemless... Obviously) and I am using the official version of TWRP.
Is it safe for me to run the OTA? I'm also encrypted if that matters.
I've attached a few screenshots below...
TIA,
MeeGz
Click to expand...
Click to collapse
I think it will fail. You need to download and flash the full OS zip to make it work.
I kind of saw that coming. This is the number one issue I have with rooting and with custom ROMS like CM in the past. Updating is always a giant PITA...
Do I download update Ota then install on rooted rom, or flash Back to stock and update
pdolo5784 said:
Do I download update Ota then install on rooted rom, or flash Back to stock and update
Click to expand...
Click to collapse
You should flash back to stock and update. Cannot install OTA over a rooted rom I believe.
However, I came from Paranoid Android and followed the advice here, and it worked perfectly. Was able to keep root and TWRP.
http://forum.xda-developers.com/showpost.php?p=68314164&postcount=69
oeusr said:
You should flash back to stock and update. Cannot install OTA over a rooted rom I believe.
However, I came from Paranoid Android and followed the advice here, and it worked perfectly. Was able to keep root and TWRP.
http://forum.xda-developers.com/showpost.php?p=68314164&postcount=69
Click to expand...
Click to collapse
currently on CM13.1 nightly I'm going to follow what you did. Hope it will work
I was rooted I use this post, and the is a link in that thread to the actual zip your will need, and also you must have the updated TWRP as well. All the information is in that thread. but that is literally it.
Download update zip
Download Flashfire
download new TWRP
Back up you crap ( will not wipe SD card unless you tell it to )
Run FlashFire, set setting correctly
run it, you will already be rooted when done
set dev mode
re-flash new TWRP
PROFIT
Did you get the option "Restore boot and recovery images" when setting Flash OTA zip? I just got Auto mount and Mount /system read/write.
pdolo5784 said:
Do I download update Ota then install on rooted rom, or flash Back to stock and update
Click to expand...
Click to collapse
You can use Flashfire to flash OTA file
i don't get the option to restore boot and recovery images. is that ok ?
pdolo5784 said:
Do I download update Ota then install on rooted rom, or flash Back to stock and update
Click to expand...
Click to collapse
If you have Xposed just get Android N-ify and it's just like having 7.0
Anyone updated from DP5 / systemless root / TWRP?
And flashed zip for adaway to work.
What are the steps to update with ota zip?
Yes and everything is ok. Follow the steps carm01 suggests some post above. Its easy and at least for me everything worked. After fisrt boot you can go to TWRP and flash everything else you need.
blackra1n said:
If you have Xposed just get Android N-ify and it's just like having 7.0
Click to expand...
Click to collapse
Not really other then a couple of options.
Sent from my Nexus 5X using Tapatalk
milan187 said:
Not really other then a couple of options.
Click to expand...
Click to collapse
You can get the same experience without going through the trouble of upgrading and then having to root again etc. I personally like it but we all have opinions
blackra1n said:
You can get the same experience without going through the trouble of upgrading and then having to root again etc. I personally like it but we all have opinions
Click to expand...
Click to collapse
I used it months ago so there could be a lot of changes to it since then?
I don't believe the new notifications are there? Quick pull down? It's also nice that it takes up a GB less for system as well.
What rom are you on?
Sent from my Nexus 5X using Tapatalk
milan187 said:
I used it months ago so there could be a lot of changes to it since then?
I don't believe the new notifications are there? Quick pull down? It's also nice that it takes up a GB less for system as well.
What rom are you on?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The notifications are definitely there, so is quick pull down It's updated frequently so I'm sure the experience is the same
I'm running Dirty Unicorns 6.0.1 with ElementalX kernel
blackra1n said:
The notifications are definitely there, so is quick pull down It's updated frequently so I'm sure the experience is the same
I'm running Dirty Unicorns 6.0.1 with ElementalX kernel
Click to expand...
Click to collapse
I just looked at N-Fy, pretty impressive. Good for them.
Sent from my Nexus 5X using Tapatalk
milan187 said:
I just looked at N-Fy, pretty impressive. Good for them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
They've definitely done a great job