are you rooted already ? (OPPO N1) - Oppo N1

hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?

nowy57 said:
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
Click to expand...
Click to collapse
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.

sorry mate
it doesnt work to me
I have tried two times
as you wrote

Harfainx said:
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
Click to expand...
Click to collapse
I have the same issue too. SuperSU installed 3 times. Did the full unroot like you said and reran the install after wiping both the cache. Still no root access.

I think that magic which found us oppo+CM team is missunderstand couse when I first time heard about cooperation this two companies I was so much happy .
by now when I have it I know that maybe couple of hundred is sold this phones and nobody cares about support it .
1.ROM straight from CM/OPPO site doesnt install propely via TWRP( without ingeration for user-script)
2.no root acces yet
this is sad true .
I v got note3 and I see more future with this phone
AOSP/CM is on a way - a lot of android entusiasts is working for free of charge about better and better ROMs
I am dissapointed - no offens to anybody

I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
it is not installed under CM ROM

It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
The exploit method was apparently patched in the official CM release. That exploit doesn't work.

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
i am really confused couse I am pretty sure I am doing good as you said but no succes .

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
If TWRP doesn't work properly how did you root? With the stock recovery?

it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
You can indeed install straight from stock recovery. I did it last night. You have to use the official rom for the n1. Works nicely. I also had root working on cm. I flashed cm from stock recovery then used fastboot to install twrp. After twrp i flashed supersu zip. After i did the fix root or remove or whatever it is in the ap, reinstalled and tested it in titanium. Said i did have access but then went back to coloros to try and fix my mediascanner issue.
Sent from my N1 using XDA Premium 4 mobile app

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
I mean straight flash CM on the stock recovery, not on TWRP. You would have to be on the stock recovery for it to work straight from the CM download. On the stock recovery though, you will not be able to flash SuperSU on it. I do not believe that Omni can be flashed from there either, but I could be wrong (I haven't tried it).
There's a thread in the dev section that has the stock recovery hosted there. You can always fastboot flash back to that at any time.

Okay, I decided to install Cyanogenmod for the heck of it.
I already had TWRP 2.6.3.1 installed,
I downloaded and modified cm-10.2-WPPH50O-n1-signed.zip as per this page's instructions:
http://forum.xda-developers.com/showthread.php?t=2553165
I also downloaded supersu (current version is 1.86).
I entered TWRP and installed it, following that page's instructions.
After the install, I selected 'reboot'.
When I selected 'reboot', It prompted me with:
install superSU now? this will root your device.
I said no, and then rebooted back into TWRP.
Now back in TWRP, I install SUPERSU.
Now reboot again.
Now in CM.
Now run SuperSU, select 'settings', and unclick 'Respect CM root settings".
Now root works for me.
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
2) If, after the CM install, you answer 'install SuperSU' with YES", then it installs SuperSU, and reboots.
When you go back in, and run SuperSU, it says "gee, you aren't rooted, install SuperSU?"
If you answer THAT with yes, then it downloads some version of SuperSU, reboots into twrp, and installs it.
So it's kinda pointless answering YES in the first place, imho.

Are you serious right now?! I was worried unchecking Respect CM root setting would mess things up. But now I have root access. OMG... I unchecked it and it works! ^_^

57 43235953
ChodTheWacko said:
...
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
...
Click to expand...
Click to collapse
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.

hammerandtongs said:
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
Click to expand...
Click to collapse
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank

ChodTheWacko said:
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
Click to expand...
Click to collapse
WOW...so it literally disappeared as I was composing this message.
Cyanogenmod "signed" installed with the oppo bootloader (not rooted as supersu doesn't install successfully through bootloader etc).
Some kind of UI refresh after I changed some home screen settings?
It was persistent through 5-10x reboots and now is gone.
Obviously a glitch since I don't have su and I'm not truly rooted but it WAS there :\
I'd say its a bug to be filed if you are rooted and it's not available.

Related

Am I the only one with these bugs?

Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?
AMKhatri said:
Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?
Click to expand...
Click to collapse
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
How do I get “root”?
If you are booted into a custom recovery (recoveries will be covered later), root is enabled by default. If you want root while booted into Android, you will need to place two files on your system partition: an “su” binary which grants root access, and a superuser app that manages that access. The two that are available are ChainsDD’s Superuser and Chainfire’s SuperSU. Usually these files are packaged up in a zip file that is flashable using a custom recovery, but they can be flashed manually using ADB. Both of these methods will be described below.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.
beekay201 said:
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.
Click to expand...
Click to collapse
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PSo you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872
AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
Mr., please, read the LINK i gave you! THIS ONE ->>>> http://forum.xda-developers.com/showthread.php?t=1812959
If you read it, you'll stop thinking you need to be doing anything at this point in FASTBOOT interface! Like mrgnex says, you need to be on a custom recovery to format /system. (Have you read the link yet? By now you should know that the /system partition and the /sdcard/ (aka userdata) are 2 different things!)
mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). (...) roms are a personal choice so there is no 'best' ROM. Just try out.
Click to expand...
Click to collapse
+1
For your reference, you can't erase /system in stock recovery.
AMKhatri said:
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872
Click to expand...
Click to collapse
Stop! THERE'S NO NEED FOR FASTBOOT HERE!
Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?
AMKhatri said:
Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?
Click to expand...
Click to collapse
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Now it's definitely clear!
I'll download CM10.1.2 tomorrow and will decide to install it once Stock JB 4.2.2 starts acting up again.
In the meantime I'll read on about kernels, please keep don't close this thread...yet.
clerk usdEuro
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)
AMKhatri said:
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)
Click to expand...
Click to collapse
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks...
I'll flash CM in a week or two, as I'm on a tight schedule currently, and I also wanna note down the average battery time I get out of 4.2.2
So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?
AMKhatri said:
So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?
Click to expand...
Click to collapse
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus
Pirateghost said:
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
What was I thinking...
I apologize guys... I guess I wasn't thinking straight as its past midnight here...
So just to clarify stuff so that I don't end up doing something wrong:
-> Head into Recovery Mode (with usb debugging enabled... connect usb cable to phone and pc)
-> Wipe System
-> Wipe Cache
-> Install from SD card (select .zip file)
right?
Also, I performed a backup of the applications I have via Titanium Backup, They'll work on 4.3 when I restore them right? or do you recommend downloading them from the play store again?
Sorry for being such a noob, and Thanks for your responses!
backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.
Pirateghost said:
backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.
Click to expand...
Click to collapse
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!
AMKhatri said:
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!
Click to expand...
Click to collapse
Seriously, how hard can it be for you people to waste 5, 5!!! minutes to browse the forums.
http://forum.xda-developers.com/showthread.php?t=2377318
Thanks!
According to a friend's recommendation I used Wugfresh Nexus Root Toolkit to Root, and surprisingly didn't lose any of my data!
Once again, Thanks for all the help everyone... You've all been quite helpful.

Recovery...super confused please help.

I love this phone but recently switched to a note 3 and love it as well. However, my wife is having problems with her phone and thought it time to factory reset to remedy the problem. However I figured i should put a custom rom on her E980 if I'm going to go through all that, I'd experiment with mine. Wow, what's with installing a custom recovery? I tried numerous ways after spending countless hours yesterday and nothing seemed stable. I had to "tot" back to stock 4.4 numerous times.
Could someone explain the procedure please as after I root how do I install custom recovery and what else I need to install and what order. Also, a good stable rom for my with based off of lollipop.
mikelets456 said:
I love this phone but recently switched to a note 3 and love it as well. However, my wife is having problems with her phone and thought it time to factory reset to remedy the problem. However I figured i should put a custom rom on her E980 if I'm going to go through all that, I'd experiment with mine. Wow, what's with installing a custom recovery? I tried numerous ways after spending countless hours yesterday and nothing seemed stable. I had to "tot" back to stock 4.4 numerous times.
Could someone explain the procedure please as after I root how do I install custom recovery and what else I need to install and what order. Also, a good stable rom for my with based off of lollipop.
Click to expand...
Click to collapse
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
ShadySquirrel said:
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
Click to expand...
Click to collapse
i can't find anyway to root my phone neither i think if there is any recovery installed in my phone (idk if that's even possible) because it doesn't go to recovery at boot
I am already on stock lollipop for F240L but it have too much blootware.
edit: so it turns out recovery is installed on mobile but in an attempt to root i ran into another error. when the program(root software) it restarts Phone into recovery, i received this error. "NO command" and i cant push updates thorough ADB.
edit2: after pressing random keys it started working but when i try to push update through adb it say
"you need adb 1.0.32 or newer to sideload to this device." any help?
ShadySquirrel said:
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
Click to expand...
Click to collapse
Tayyab.Hasan said:
i can't find anyway to root my phone neither i think if there is any recovery installed in my phone (idk if that's even possible) because it doesn't go to recovery at boot
I am already on stock lollipop for F240L but it have too much blootware.
edit: so it turns out recovery is installed on mobile but in an attempt to root i ran into another error. when the program(root software) it restarts Phone into recovery, i received this error. "NO command" and i cant push updates thorough ADB.
edit2: after pressing random keys it started working but when i try to push update through adb it say
"you need adb 1.0.32 or newer to sideload to this device." any help?
Click to expand...
Click to collapse
I did it. went back to KK using download mode, rooted and now i will flash new ROM. Thanks.

[ROM] LS980 ZVI stock 5.0.2 flashable

This was tough to get as LG locked down all known exploits with the ZVI release. It took some hardware hacking to pull a clean unmodified system and kernel. Here is a flashable zip:
http://jacobstoner.com/LS980ZVI.zip
This includes a bootstack with an older bootloader and TWRP 2.8.7.3. The ZVI kernel has been bumped to work with the older bootloader. Otherwise this is completely unmodified and unrooted so if you want root then flash SuperSU after flashing this.
http://download.chainfire.eu/supersu
Thanks for sharing, i am on cyanogenmod 11, can i install it with hybrid bootstack and blestagator's bumped twrp?
It will replace your bootstack and update twrp, but it will work fine.
Thanks, man! I wait for it so long! Because I'm still on ZVG because ZVI was unrootable. So all what I need is just clean flash room in recovery and install supersu app? Without any unlockers? Downloading now, making backups and give a try!
astherion said:
Thanks, man! I wait for it so long! Because I'm still on ZVG because ZVI was unrootable. So all what I need is just clean flash room in recovery and install supersu app? Without any unlockers? Downloading now, making backups and give a try!
Click to expand...
Click to collapse
Yes, just flash in recovery and flash the supersu zip from the link above. You can dirty flash over ZVG, it will overwrite the whole system partition anyway.
Confirmed! If works! Just made clean installation 20 minutes ago & flash supersu.zip through recovery. Superuser works fine. So now I've try restore zvg & flash over it. Because I use lots of exposed modules & dorimanx kernel, titanium backup, lucky patcher, freedom etc. For this sw root is critical... Thanks a lot for latest ZVI + root! Later I link to your thread for peoples from russian 4PDA LG G2 thread. Lots of people will be happy!
ROM working well for me too. Thanks!
Not ever try to flash on installed rom! You'll receive a lots of lags after! Make app backup & flash "clean" install through recovery. I found also 1 issue in recovery: then screen goes off after you turn it on you see only blue-grey-black-white stripes with tiny squares. It happens not always but sometimes.
P.S. Previously I also used bumped 2.8.7.3 TWRP and has no problems. Also I use xposed, so when I flash ZVI on ZVG & restore apps backup has lots of lags like force close systemUI, deleted unworking software etc. So - clean install! After that - restore backup, but only user apps, not system like xposed apps, home g4 launcher, dialer etc.!
Rom
Its working fine ... but i am facing network lock issue...Kindly help
To nomansabir: what means network lock? Simlock? Or you can't switch cdma/lte?
astherion said:
To nomansabir: what means network lock? Simlock? Or you can't switch cdma/lte?
Click to expand...
Click to collapse
Dear i am facing sim lock problem.... Its showing Invalid sim card message...
SIM-unlock
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
astherion said:
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
Click to expand...
Click to collapse
Thnx astherion .... its working fine now.....
jacob019 said:
This was tough to get as LG locked down all known exploits with the ZVI release. It took some hardware hacking to pull a clean unmodified system and kernel. Here is a flashable zip:
http://jacobstoner.com/LS980ZVI.zip
This includes a bootstack with an older bootloader and TWRP 2.8.7.3. The ZVI kernel has been bumped to work with the older bootloader. Otherwise this is completely unmodified and unrooted so if you want root then flash SuperSU after flashing this.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
that's wonderful, @jacob019, thanks for sharing this highly waited zip of the ZVI, as far as i am on cloudy G2 3.3 with my LS980 for a long time and have not experienced the stock firmware after ZVG.
I have two questions in my mind if you could please clear them.
1. Is there any problem in the ZVI like most of the LG updates have not been without bugs or lagging ?
2. Can i flash this zip directly from my already installed TWRP without going back to stock ZVG or ZVE? (I have Cloudy G2 3.3 installed with blastgator's boot stack/baseband) {Cloudy G2 v3.3 is indeed a perfect ROM for my LS980 till now}
Thanks again for the great job you have done
talvigi said:
1. Is there any problem in the ZVI like most of the LG updates have not been without bugs or lagging ?
2. Can i flash this zip directly from my already installed TWRP without going back to stock ZVG or ZVE? (I have Cloudy G2 3.3 installed with blastgator's boot stack/baseband) {Cloudy G2 v3.3 is indeed a perfect ROM for my LS980 till now}
Click to expand...
Click to collapse
1. I've been using it for a couple weeks, seems quite stable but I'm a light user.
2. Yes, you can flash it directly from your already installed TWRP. No need for any other preparation.
jacob019 said:
1. I've been using it for a couple weeks, seems quite stable but I'm a light user.
2. Yes, you can flash it directly from your already installed TWRP. No need for any other preparation.
Click to expand...
Click to collapse
Thanks @jacob019 for your time and again for your great job.
I will try it as soon as the download of the zip file will be completed.
And i also must try the SIM unlock as you mentioned above because i live out of US and am using GSM network not CDMA, so i think to do that i need some preparations.
I hope there are thousands in this line to need ZVI and the SIM unlock. Hail Jacob.
What is the flashing procedure by the way? is it same as we flash custom ROM (wipe system, devlock, cache and data) or just wipe dev lock and cache and flash the zip file
Just reboot to tarp recovery, choose wipe - advanced - check all except "sdcard" - wipe and just flash zip. Also better to flash supersuper.zip if you need root. Reboot - profit!
For me it works flawlessly, slight more battery drain, but solved by dorimanx kernel, xposed & greenify app. I didn't see the even mentioned lags in this Rom. Working for me the same as ZVG & also rootable!
astherion said:
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
Click to expand...
Click to collapse
@astherion, Thanks for the SIM Unlock files, by the way rooted is OK but but what is "after correct installation" is it what the software in PC does with the mobile or something else? And developer options have to enabled or otherwise?
Edited: Thank you very much guys specially @jacob019 and @astherion, you guys rock the party. The stock Lollipop is flashed perfectly and SIM Unlock was the most simple step i have every seen in the LG world, But astherion you should have mentioned the USB debugging option as it needs to be enabled before running the simunlock.exe from the PC, and an other thing i can see Hands free activation disturbs after every reboot (i have just rebooted twice and it cameup both times) and battery level also going very fast don't know why but, this can be a major issue which may force some people like me to go back to Cloudy. My battery was at 75% and 4 hours 12 minutes remaining and after i rebooted to recovery and wiped devlock cache and data, still battery says 69 % 3 hours 3 minutes remaining. This is dangerous, the battery graph is showing like a forward slash is on the graph panel, I will attach pics.
Indeed this all made me a fan of you guys,
So I am on ZVH, rooted with TWRP installed. Can I just flash the zip files?
When doing a clean install, are you just totting back to an earlier release(ZVE or G), rooting and installing TWRP and then this zip files?
tekweezle said:
So I am on ZVH, rooted with TWRP installed. Can I just flash the zip files?
When doing a clean install, are you just totting back to an earlier release(ZVE or G), rooting and installing TWRP and then this zip files?
Click to expand...
Click to collapse
Yes, you can just flash the zip file; should be no need to wipe data if you're coming from ZVG. Also there is no need to tot back to an earlier release unless you are already on ZVI because wiping data and installing this zip will produce just as clean of an install.
@talvigi, battery is okay for me; but I'm used to stock. I'm not sure about disabling activation because I'm using it on Sprint. I'm sure you can find info on how to improve both of those issues, but there isn't anything to be done here since this is an unmodified stock rom.

Any gotchas trying to install CM13 on OH1?

Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
ejaf said:
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
Click to expand...
Click to collapse
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Here is the link to the latest, grab the first tar flash it via odin & you should be good to boot into recovery to flash roms.
https://dl.twrp.me/d2spr/
Lonelyskatter12 said:
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Click to expand...
Click to collapse
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
ejaf said:
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
Click to expand...
Click to collapse
Yes, the official thread is CM13, you don't need Cwm, pretty much twrp supports marshmallow now.
And i believe you would need root.
If there's any way for you to be able to download the files, id be happy to give you step by step instructions :good:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
ejaf said:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
Click to expand...
Click to collapse
Yeah the Unofficial thread was being maintained by a Developer, who stopped as soon as the officials came out.
And yes
1.) Wipe Data, Cache, System, & Internal Storage (So backup anything on there)
2.) Flash Rom, Gapps, SuperSu 2.71 (If you want root)
& should be good to go
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
ejaf said:
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
Click to expand...
Click to collapse
That's the order, now about the apn im not sure, i just use mine for wifi and stuff.
That Cyanogenmod build "04282016" wasn't running so well for me, so I'm on AICP for now.
But i would suggest, OctOs , AICP, or Exodus Roms. Those are the most stable roms for this device.
Same steps just different ROMs.
But i did hear Exodus gives you data right off the bat, so that'd be good to try
Interesting...thanks for the tips. Hopefully I won't have to bother any of you all again, since I really don't have much in the way of knowledge to return
E
FYI...was able to boot up into CM 12.1 over the weekend. Jury's still out on whether to go to a 6.0.1 based ROM, but appreciate all the help.
Eric
I found the APN fix didn't work with the CM13 rom (I've used it previously with 12.1 fine). I also found that the build-in cm update failed on 20160505 nightly. Not sure if this was just that day or a known bug.

Still confused about how to install Magisk/Automagisk on my HTC 10

I have been trying to Google this but am a little confused on all the steps I need to (and don't need to) take at this point, especially since I am a little behind. So I wanted to ask for help on forums, if anyone is willing to give some advice on this.
First of all, I have a Sprint version of the HTC 10. I don't know if that matters or not (I recall back when I was trying to figure out the original Magisk, someone mentioned that a Sprint model HTC 10 could be an issue, but I am not sure why).
Also, so far all I have done in terms of rooting it is:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Ummm, anyone?
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Its all there in the op of the magisk thread.
I read that thread, as I said, I still don't understand some parts.
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Have you tried posting in the dedicated Magisk thread?
Try installing leedroid nightly latest it has magisk available when you install rom
i did not try it, till now. I read something a few weeks ago.
But in the magisk thread the op said something that SuperSu is not the supported SU method? only phh superuser?!
I would ask the question in magisk thread.
Firstly: You ask a lot of semi-related questions, a lot of these are already answered, out there, in the appropriate threads.
Let me systematically try to answer your questions
What you have done:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
Click to expand...
Click to collapse
When you install the TWRP recovery, you actually install it to the recovery partition of your device.
the option the "not modify system" has nothing to do with installing TWRP, but with installing other mods/roms
It's there so you can make a backup without modifying the system partition, that way you can go back to a working isntall if you do happen to mess something up.
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
Click to expand...
Click to collapse
SuperSu *should* break safetney and thus should break android pay, as Chainfire says in the following thread: http://forum.xda-developers.com/apps/supersu/supersu-safetynet-android-pay-t3298115
"In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU."
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Click to expand...
Click to collapse
Installing SuperSu trough TWRP installs the dependencies (the actual root) and the application (which just manages the root access), the magisk guide tells you to first flash the preferred root (SuperSu or SuperUser phh's) trough recovery and then install the correct manager app trough the playstore.
This is probably so John doesn't have to keep on updating his zips everytime the makers of the manager apps update their apps, users can just download the latest version.
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
Click to expand...
Click to collapse
Resetting to stock is important for 2 reasons:
1. it cleans out all "old" root apps and methods
2. it cleans up a patched boot.img (kernel)
Then again, if you haven't flashed any other mods, you would probably be safe to install magisk on your rom.
One important thing everyone will always tell you: make a backup! (make a nandroid)
To do this, boot to TWRP and choose "backup" make sure to select: Boot, System and Data
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Click to expand...
Click to collapse
The proper steps would be:
0. Make a nandroid backup in TWRP!!
1. Open SuperSU and choose to completly unroot (somewhere near the bottom of the settings menu)
2. Boot to TWRP and flash Magisk
3. Flash the phhh superuser zip file (from the magisk thread)
4. boot android and install the superuser app from the playstore
5. boot twrp and install AutoMagisk
That's it!
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Click to expand...
Click to collapse
Radio shouldn't be broken unless you flash very old zips, don't worry about it
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Click to expand...
Click to collapse
I allmost enver use official OTA's so I can't say for certain buttttt as you used SuperSU, the root should be systemless so it should accept OTA updates..
What I would do:
1. make a nandroid
2. install OTA
3. See if everything works as expected
4. restore backup if something doesnt work properly =D
I would install the OTA before trying Magisk
Thank you, that was very helpful. I did try Googling all this, but couldn't find clear answers, which is why I am asking here.
And yes, I am definitely going to make a backup before messing with it. Is there any reason to make a Titanium backup too, or will the nandroid one be enough?
As for removing SuperSU, what would that system/boot stock reset delete? Would it delete any installed applications or application settings? Or undo updates to pre-installed system apps? Or reinstall apps that came with the phone that I uninstalled?
Got it working, thanks. (Though, AutoMagisk seems to only be available as an APK, not as a zip that can be installed from TWRP).
Seems like a few configuration settings got wiped due to the system partition being reset, but other than that most of my data seems perfectly intact.

Categories

Resources