Related
So some apps auto updated =/ and I lost root access. I am s-on. Using supersu tells me I have to update binaries and if I click continue, it restarts and no luck. If i click cwm/twrp method, that does not work either.
What to do? As I said I think this happened when supersu updated its app.
Checked with root checker, and im not rooted.
Download the latest version of SuperSU and flash in recovery. Did you ever get S-off?
Sent from my HTC M8
Magnum_Enforcer said:
Download the latest version of SuperSU and flash in recovery. Did you ever get S-off?
Sent from my HTC M8
Click to expand...
Click to collapse
Re flashing supersu does nothing, it re optimizes all apps but does not work, and when I re open supersu, it tells me binary needs to be updated. No, never got s-off.
Which version of SuperSU did you try to flash?
Sent from my HTC M8
Magnum_Enforcer said:
Which version of SuperSU did you try to flash?
Sent from my HTC M8
Click to expand...
Click to collapse
v 1.94
Try the newest version posted in the SuperSU thread. Somebody else was having issues with the older one recently and the newest version worked.
Sent from my HTC M8
Magnum_Enforcer said:
Try the newest version posted in the SuperSU thread. Somebody else was having issues with the older one recently and the newest version worked.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed 2.01 supersu and it does not even show up in apps anymore. (Flashed via TWRP)
Did you try installing the app again?
Sent from my HTC M8
Magnum_Enforcer said:
Did you try installing the app again?
Sent from my HTC M8
Click to expand...
Click to collapse
Yes, over and over and no luck.
koolcat7 said:
Yes, over and over and no luck.
Click to expand...
Click to collapse
install the 1.94 again and then go to the play store and down SuperSU and see if it show up.
I had the same thing happen. I reflashed superSU in TWRP and it dissapeared.... So I installed it from the play store, opened it and allowed it to update binaries in TWRP to resolve.
If the update does not happen automatically when you boot to recovery reboot and try again.
Thanks for all of your help, but nothing worked so I just did a nandroid restore, which fixed the issue. Everything is back to normal.
Have a nice day!:good:
I just a replacement model to be able to unlock my bootloader, root, etc. I am currently on 4.4.2 and was wondering if there is a method to root 5.0.2? If so, what are the steps?
EvoTheBoy said:
I just a replacement model to be able to unlock my bootloader, root, etc. I am currently on 4.4.2 and was wondering if there is a method to root 5.0.2? If so, what are the steps?
Click to expand...
Click to collapse
The same steps are required to root the phone on 5.0.2 as on any other version: Flash twrp recovery, flash the latest SU.
alray said:
The same steps are required to root the phone on 5.0.2 as on any other version: Flash twrp recovery, flash the latest SU.
Click to expand...
Click to collapse
I flashed UPDATE-SuperSU-v1.94.zip in TWRP recovery and when I go to verify root it says I am not rooted. Am I doing something wrong?
EvoTheBoy said:
I flashed UPDATE-SuperSU-v1.94.zip in TWRP recovery and when I go to verify root it says I am not rooted. Am I doing something wrong?
Click to expand...
Click to collapse
1.94 is pretty old is does not support lollipop.
Latest SU is 2.46 and will works fine on lollipop.
alray said:
1.94 is pretty old is does not support lollipop.
Latest SU is 2.46 and will works fine on lollipop.
Click to expand...
Click to collapse
Hi sir, if I root my phone, and then install again stock recovery, will I be able to recieve OTA Updaates ?
Xhemal1325 said:
Hi sir, if I root my phone, and then install again stock recovery, will I be able to recieve OTA Updaates ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Hello all,
With news that the Z3 and Z3 compact are starting to get Lollipop today I am sure a lot of people are going to be coming to the boards asking this exact question. So I wanted to start a thread that can help people find the answer quickly. (I'll update the OP as useful info comes in.)
I am currently on a D5803 running 4.4.4, with a locked bootloader and am rooted. I used This how-to to get where I am.
What is the best way to upgrade to Lollipop for me?
Is there a way to keep root? A pre-rooted FTF file?
Will all DRM features remain?
Will I need to reinstall anything? Recovery? Busy Box? SU?
Does this upgrade require a full wipe?
Thanks for any help
If anyone wants to check if their bootloader is locked:
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?
TheTomcraft said:
just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?
Click to expand...
Click to collapse
You root on KK then you can update to Lollipop and keep root.
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!
gruev said:
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!
Click to expand...
Click to collapse
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
q.
frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
Did you wipe? or flash over?
newbie2006 said:
Did you wipe? or flash over?
Click to expand...
Click to collapse
I wiped it (had too much crap on the phone anyway, so worth it), restored what I wanted with Titanium Backup when done.
---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------
I also tried with flashing lockeddualrecovery but recovery doesn't work. So need to wait for an update on that one I guess.
Any ideas about what could go bad if I don't wipe data?
Also, do you still have drm?
I succesfully flashed lolipop with this method without data wipe. I still have root and DRM keys. The only thing I lost was data of some app's with external data linked to SD card with Link2SD. And some root app's started to claim about busybox not installed properly. Besides that everything works like a charm
frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
When you flash those do you have system read and write as well? Do we need to worry about the RICDefeat in doing all this for the upgrade? Is RICDefeat integrated into that?
1.Flash the tft of lollipop
2.Get the zip of XZDualRecovery 2.8.3 Advanced Stock Kernel from http://nut.xperia-files.com/ and supersu from http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash the boot.img in AndroPlusKernel with cable on flashtool
4.Reboot in recovery
5.Flash XZDualRecovery 2.8.3 Advanced Stock and supersu
6.Enjoy
Sorry，it should be with UB
about not working recovery
Dont know it thats issue, but I have same clue.
On KitKat after applying all steps to root 4.4.4 rom recovery was working until I changed busybox.
Oryginaly busybox was in version 1.20.2-jb - with that recovery was working.
I need some other tools and updated busbox to version 1.22.1 and recovery wasnt working (starting recovery end up with bootloop, but could start to system).
Returning back to recovery 1.20.2-jb fixed problem.
frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
I was hoping by adding step 4, it would be possible the encrypt device. Sadly it still creates a bootloop.
in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?
skaarax said:
in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?
Click to expand...
Click to collapse
I want to know about this too.
And what is a safe process for us (locked bootloader, rooted 4.4) to upgrade to 5.02 or 5.1 in the future.
I heard that unlocking bootloader will causes the camera not working properly (at least the auto mode would be messed up)
Does TWRP requiring unlocking bootloader?
Thanks guys.
I'm resurrecting this thread as I've got the same question as previous posters and I've not been able to find an answer elsewhere on the forum.
Basically, I've got a phone with a Bootloader which can't be unlocked. I upgraded/rooted it last year. It's still on KitKat. Is there any way I can upgrade it to Lollipop or Marshmallow without going through the downgrade/flash pre-rooted ROM procedure, without losing root? In other words, can I make use of TWRP which I installed in order to flash the rooted ROM last time? If so, how? (I'm not keen on using KingRoot unless somebody can convince me that handing over my IMEI info is safe.)
Thanks in advance.
Just flash a pre-rooted 5.1 zip made with prf creator whilst still on root+recovery KK. That's how I updated my M2 from rooted 4.4.4 KK to rooted 5.1 lollipop whilst retaining my locked bootloader. No sure if it's working for mm yet though this way
So, I unlocked the bootloader, I flashed a custom recovery and then I installed Superuser, but after sometime I deleted everything and I installed a new ROM, but I lost my root, though I still have the bootloader unlocked and a custom recovery, I don't have superuser anymore, and root checker says I'm not rooted. My question would be, what does this mean? Is my phone rooted or not, and how does this state affect my phone, will apps be able to access root files or not? and so.
Thank you in advance.
Tarabas51 said:
So, I unlocked the bootloader, I flashed a custom recovery and then I installed Superuser, but after sometime I deleted everything and I installed a new ROM, but I lost my root, though I still have the bootloader unlocked and a custom recovery, I don't have superuser anymore, and root checker says I'm not rooted. My question would be, what does this mean? Is my phone rooted or not, and how does this state affect my phone, will apps be able to access root files or not? and so.
Thank you in advance.
Click to expand...
Click to collapse
Unlocked bootloader doesn't root your phone, SuperUser does that. So, if you don't have SuperUser binary installed, your phone is NOT rooted, and apps which require root access will NOT work. If you're running a Lollipop ROM, you need SU 2.46 because older SU will cause bootloop. So, download SU 2.46.zip, and just flash it via recovery. That will root your phone
donkeykong1 said:
Unlocked bootloader doesn't root your phone, SuperUser does that. So, if you don't have SuperUser binary installed, your phone is NOT rooted, and apps which require root access will NOT work. If you're running a Lollipop ROM, you need SU 2.46 because older SU will cause bootloop. So, download SU 2.46.zip, and just flash it via recovery. That will root your phone
Click to expand...
Click to collapse
I'm running KitKat, I was originally running Lollipop, I don't want to go back to root (I've tried though but it isn't working I don't know wh), I was just wondering if this can affect my phone "negatively".
Tarabas51 said:
I'm running KitKat, I was originally running Lollipop, I don't want to go back to root (I've tried though but it isn't working I don't know wh), I was just wondering if this can affect my phone "negatively".
Click to expand...
Click to collapse
Well, if you don't want root, apps that require root will not work. Nothing else can go wrong
donkeykong1 said:
you need SU 2.46
Click to expand...
Click to collapse
just to inform you that 2.65 stable is out now
alray said:
just to inform you that 2.65 stable is out now
Click to expand...
Click to collapse
Thanks for the info @alray [emoji106] [emoji4]
---------- Post added at 07:37 PM ---------- Previous post was at 07:35 PM ----------
alray said:
just to inform you that 2.65 stable is out now
Click to expand...
Click to collapse
Thanks for the info @alray [emoji106] [emoji4]
@alray, I know it's offtopic, but does SU 2.65 work fine? I see it's in beta state
donkeykong1 said:
@alray, I know it's offtopic, but does SU 2.65 work fine? I see it's in beta state
Click to expand...
Click to collapse
Its working fine.
2.65 is no more a beta release, its a stable release now:
http://download.chainfire.eu/supersu-stable
And since we are talking about tools update, there is now TWRP 3.0.0.0 for the M7 on mdmower's website. Iv flashed it this morning and its working fine.
alray said:
Its working fine.
2.65 is no more a beta release, its a stable release now:
http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
Thanks! You're a great help, as always! [emoji4]
i WOULD LIKE TO ROOT MY NOTE 4 and possibly install different roms,is it possible to root with this new update and if so could someone point me in the right direction ?I have not rooted a phone since Galaxy s 3 and it seems a bit more complicated now .Thanx in advance to anyone who can answer my question.
Just install the latest TWRP via ODIN and then flash the latest SuperSU via TWRP.
pvsgh said:
Just install the latest TWRP via ODIN and then flash the latest SuperSU via TWRP.
Click to expand...
Click to collapse
Is it a system or systemless root?
Mister_E105 said:
Is it a system or systemless root?
Click to expand...
Click to collapse
By default, it would be systemless, but if you need System mode, you would need to use another zip found under SuperSU subforum.
http://forum.xda-developers.com/apps/supersu
This isnt working. TWRP flashing failed.
aznmode said:
This isnt working. TWRP flashing failed.
Click to expand...
Click to collapse
No problem here, using EPJ2 (stock, debloated, root, xposed) everything working fine.
Which version of TWRP you are trying, and what is the ODIN version?
pvsgh said:
No problem here, using EPJ2 (stock, debloated, root, xposed) everything working fine.
Which version of TWRP you are trying, and what is the ODIN version?
Click to expand...
Click to collapse
Forgot to update my post but I fixed it by allowing OEM unlock in the developer option.
For some reason I don't have the OEM check box in my developer options. I haven't been able to root my phone in months.
ReallyRick said:
For some reason I don't have the OEM check box in my developer options. I haven't been able to root my phone in months.
Click to expand...
Click to collapse
Which update are you on and what issues are you having?
I have the latest update epj2 and I can't seem to root my device
ReallyRick said:
I have the latest update epj2 and I can't seem to root my device
Click to expand...
Click to collapse
You can't Odin twrp or flash supersu in twrp?
Sent from my SM-N9300 using Tapatalk
No it wont let me do any of this. These are the files I have. I tried to flash the TWRP and it hangs. Does I thought I had to use CF ROot to root the phone first? Have I forgotten how to root? http://imgur.com/a/FMfeC
ReallyRick said:
For some reason I don't have the OEM check box in my developer options. I haven't been able to root my phone in months.
Click to expand...
Click to collapse
I believe this option is only for T3 model not the regular T model.
ReallyRick said:
No it wont let me do any of this. These are the files I have. I tried to flash the TWRP and it hangs. Does I thought I had to use CF ROot to root the phone first? Have I forgotten how to root? http://imgur.com/a/FMfeC
Click to expand...
Click to collapse
Again if you regular T model, use the files related to your model.