Hi,
I installed the CM12.1 nightly on my SGP521 using the guide on the CM wiki. So my bootloader is unlocked. I installed superSU via the CM recovery but it didn't work of course. But then I read scattered hints that I need to downgrade my firmeware.
1. Could you please point me to the right files to downgrade my tablet?
2. Could you confirm that, after flashing the downgrade that I could then root the phone by flashing the file from this thread? http://forum.xda-developers.com/xperia-z2-tablet/general/update-t3082546
3. Or kindly tell me what to do instead please.
waverd said:
Hi,
I installed the CM12.1 nightly on my SGP521 using the guide on the CM wiki. So my bootloader is unlocked. I installed superSU via the CM recovery but it didn't work of course. But then I read scattered hints that I need to downgrade my firmeware.
1. Could you please point me to the right files to downgrade my tablet?
2. Could you confirm that, after flashing the downgrade that I could then root the phone by flashing the file from this thread? http://forum.xda-developers.com/xperia-z2-tablet/general/update-t3082546
3. Or kindly tell me what to do instead please.
Click to expand...
Click to collapse
You simply can enable root on CM in the settings: Enable the developer settings by clicking several times on the build-number. No need to install anything. SuperSU should also work, though. No problems here with root.
BabelHuber said:
You simply can enable root on CM in the settings: Enable the developer settings by clicking several times on the build-number. No need to install anything. SuperSU should also work, though. No problems here with root.
Click to expand...
Click to collapse
Awesome, thank you! It worked and then I installed the SuperSU 2.48 and AdAway - perfect!
Related
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Wrong forum. This is a dev forum, not Q&A. Rooting w/out custom recovery is possible with chainfire's autoroot flashable zips. But still you won't receive OTA updates b/c since Lollipop the validation process has changed and you need to be pure stock. This also includes the recovery iirc.
Moved to correct forum
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
giannisgt said:
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Click to expand...
Click to collapse
brownog1 said:
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
You will not receive OTA updates if you are rooted.
cam30era said:
You will not receive OTA updates if you are rooted.
Click to expand...
Click to collapse
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
HansiHusten said:
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
Click to expand...
Click to collapse
My bad. I should have said you will not be able to install OTA if you are rooted. The install script checks system files and if anything has been modified, it aborts installation. Your better option is to fastboot flash the Google factory image.
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
HansiHusten said:
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
Click to expand...
Click to collapse
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
cam30era said:
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Click to expand...
Click to collapse
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
HansiHusten said:
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
Click to expand...
Click to collapse
Stable should work for Lollipop. Beta necessary for M. And beta works fine on Lollipop, too, FWIW.
I've lost root twice after flashing ROMs in TWRP. Here is the process I'm going through:
Flash 10b using the LGFlashTool.
Root using StumpRoot. Verify successful Root via RootChecker/SuperSU/BusyBox.
Use Flashify to install TWRP bumped (2.8.0.0, then upgrade to 2.8.3.0 using the recovery.img in this link w/ Flashify: http://forum.xda-developers.com/ver...recovery-twrp-touch-recovery-2-8-2-0-t2966014)
Reboot and verify root again.
Boot into TWRP, wipe (tried factory reset and advanced cache/system/boot/data methods)
Install ROM (tried Resurrection 5.2.8 and Illusion 3.0).
Reboot, lose root.
I am new to the G3, but I've done many flashes on several devices throughout the years thanks to the folks on XDA. If someone could point out my error it would be much appreciated!
I don't know about resurrection but illusion comes with root disabled. Just flash the latest SU package.
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
BTW searching within the rom threads would have given you the answer faster than typing up this new thread.
I didn't see notes in the OP in either ROM thread regarding disabled root nor flashing SuperSU. Thanks for the quick reply.
you're not alone. I lost root on CM12 (o'1.5.15) and can't seem to get it back either. I was hoping your post was on that, but no avail. I have tried flashing su.zip latest from twrp 2.8.3.0 with no success.
----
turns out, bad zip and adb/apps disabled within dev options of CM12. might not be the same on the ROMs your dealing, but was my solution. FWIW.
Just download the latest SuperSU zip and flash it in recovery and you should have root back just check in developer options that root is enabled
Here's a link to the latest SuperSU zip
https://www.dropbox.com/s/rsyrixpe6uo3bma/UPDATE-SuperSU-v2.40.zip?dl=0
I am new to android and rooting so please bear with me. I used the LG flash to to downgrade from 12b and then I got TWRP and flashed Illusion and Gapps, but now it says I am not rooted and I cannot seem to get back into TWRP. Is my best option to start over using the flash tool? Is there a better lollipop rom that keeps root? This forum has been so helpful in the learning process so thanks in advance.
MurphDawg37 said:
I am new to android and rooting so please bear with me. I used the LG flash to to downgrade from 12b and then I got TWRP and flashed Illusion and Gapps, but now it says I am not rooted and I cannot seem to get back into TWRP. Is my best option to start over using the flash tool? Is there a better lollipop rom that keeps root? This forum has been so helpful in the learning process so thanks in advance.
Click to expand...
Click to collapse
Go into developer options and turn root on.
As for a better rom.... ill let you slide on that...
bweN diorD said:
Go into developer options and turn root on.
As for a better rom.... ill let you slide on that...
Click to expand...
Click to collapse
Wow. I'm such a noob. (facepalm) Thank you!
Yeah I'd also like to chime in on this a few weeks ago I went to try cm12 (was using illusion 4.0) and I also had root problems too
But then I've read twice in the last ten minutes that cm12 has deprecated supersu.
So basically it sounds like illusion 4.0 just hadn't updated enough yet to be like cm12.
I seriously thought my phone had major issues. Paired with the PA gapps cluster f... Yeah basically I haven't had to use roms for nearly 2 years.
Anyway thanks four this useful thread!
If you have a custom recovery installed you can't "lose root".
You can always get it back by flashing SU or whatever.
CM12 has root as an option in the developer section of the settings.
Sorry if this is common knowledge or if I'm just not finding it on the forums, but I recently did the JB RUU on my phone, then upgraded to Kitkat 4.4.2 using the built-in update option. Everything is running fine except that I want to use SDFix to access my SD card fully, but it requries root.
I've searched around the forums but can't seem to find a guide and/or the files required. Could someone give me a quick explanation or perhaps give me a link to a guide?
Thanks!
rubejb said:
Sorry if this is common knowledge or if I'm just not finding it on the forums, but I recently did the JB RUU on my phone, then upgraded to Kitkat 4.4.2 using the built-in update option. Everything is running fine except that I want to use SDFix to access my SD card fully, but it requries root.
I've searched around the forums but can't seem to find a guide and/or the files required. Could someone give me a quick explanation or perhaps give me a link to a guide?
Thanks!
Click to expand...
Click to collapse
First, you need to have your bootloader unlocked. HTC has basic instructions on that.
Second, you need to install TWRP from this thread. Basic instructions for flashing are on TWRP's page.
After that you can boot into recovery (adb reboot recovery) or power off phone then hold Vol - and Power and select recovery when phone turns on. Once in TWRP, reboot the device it will ask if you want to root it. Let it install root and then when phone reboots you should get a notification to install SuperSU, click it and when it finishes you'll have root access.
Hey just wondering that TWRP one is for Zara_cl. Is the Zara_ul one this? https://twrp.me/devices/htcdesire601gsm.html
How do i install twrp on my htc? i cant find a tutorial..
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin
So yesterday I unlocked the bootloader and root my OPX, and today I've installed cyanogenmod 13. I have also downloaded Root Checker to check if I am still root or not, and it says that I am not a root user anymore.
Do I have to root again? And if so, which steps do i have to take?
Thank you in advance
_mikelanda said:
So yesterday I unlocked the bootloader and root my OPX, and today I've installed cyanogenmod 13. I have also downloaded Root Checker to check if I am still root or not, and it says that I am not a root user anymore.
Do I have to root again? And if so, which steps do i have to take?
Thank you in advance
Click to expand...
Click to collapse
I would recommend checking out this article http://www.cyanogenmods.org/forums/topic/enable-root-access-cm13cyanogenmod-13-roms/
It seems CM13 has an option in the Developer Settings. I cannot confirm this as I don't have it installed, or never have had experience with Cyanogen. But what it seems is that the conventional flashing method of the SuperSU.zip is for most other versions of Android and their tweaked variants (e.g OOS), including CM11 and 12 but 13 is different.