Related
Hello, I've recently installed Temasek's CM 13 nightly marshmallow build to my bootloader unlock note 3. I'm having a difficult time acquiring root after the install. I've flashed SuperSu to no avail. I've even tried the Aramaic tool method with no luck. Is there anything I can do to get root back on this phone or am I screwed?
Look for SuperSU in the settings menu.
Not sure if you need to turn on developer options for it to appear there or not.
[Edit]Did you install CM with a custom recovery, or with flashfire?
Your post doesn't say one way or another, but if you have an unlocked bootloader you can flash a custom recovery using Odin... meaning that you always have root, so long as you preserve the unlocked bootloader.
Having only a single root (locked bootloader and no custom recovery) and using FlashFire to install a ROM puts you at constant risk of root loss.
.
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
cblendz said:
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
Click to expand...
Click to collapse
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
bftb0 said:
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
Click to expand...
Click to collapse
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
cblendz said:
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
Click to expand...
Click to collapse
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
bftb0 said:
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
Click to expand...
Click to collapse
Thanks a lot that was it. Finally got root. I wish CM would bake root in their Roms but all is good now. Thanks.
Hello and thanks for reading.
Well, I installed the TWRP on my Letv 1S X500 to flash the gapps and can use play services but as I had the recovery installed I wanted to test some customs rom. The problem is that I can go back to my stock rom or even other rom. Actually I could installed other rom but I can not do it more. (First I installed RR, after some hours many apps stop so I have to make wipes (Cache, dalvik, System and data) three times and I could installed lineage OS, but I can not use Snapchat so I wanted to install the S26 again so I tried to use the backup but the TWRP does not find it, it just does not appear. I did two backups, one when I had the S26 and other when I had RR and any of both appear when I press restore. I also tried to install the rom, not make a restore but, it says This package is for "X3" devices; this is a "x3". error 7. I already did the trick of deleting the semicolon or all the lines with the "assert" word but it is the same.
I have thought on installing the stock recovery and rename the s26 to "update.zip" but I do not know if it is just like that.
What could I do to fix this problem?
I want to have the stock rom, but if the problem with snapchat has a solution I could keep using LineageOS.
I have this recovery 3.1.0-0
The first backup was with TWRP 3.0.1 and the second one with my current TWRP 3.1.0-0
I am downloading other stock rom to prove, the 17S. I hope this work.
I just know, I am not a root user, I have not installed superSU. Is it important?
diosshu said:
I just know, I am not a root user, I have not installed superSU. Is it important?
Click to expand...
Click to collapse
No, it is not important.
Seems like you changed twrp, to restore the backup created by one version of twrp you need the same twrp to restore.
Hello,
Did you solve a problem?
I have same problem.
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.
Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
CptUnicorns said:
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
Click to expand...
Click to collapse
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Striatum_bdr said:
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Click to expand...
Click to collapse
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
CptUnicorns said:
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
Click to expand...
Click to collapse
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Striatum_bdr said:
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Click to expand...
Click to collapse
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
CptUnicorns said:
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
Click to expand...
Click to collapse
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
OhioYJ said:
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
Click to expand...
Click to collapse
That does clear up things for me, I've either mis-read or not read that when on slot A you are actually flashing slot B and Visa versa.
I'll be flashing both my slots to 10.3.1 just so they're fully updated. ( A is my main)
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
CptUnicorns said:
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
Click to expand...
Click to collapse
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Great stuff. Thought I understood from how you explained it. I'll check that guide as well and have it to hand just incase.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Something didnt want to play when I was flashing... Got to flashing gapps and magisk, gapps flash gave me a error 64 and i got magisk installed, booted, now I've got no twrp and when I use fastboot it just softbricks then restarts after about 5 minutes, I'm gonna try booting from 3.2.3-2 as that was fine and hope I can boot into recovery and just go lineage I think for something new
EDIT
So I used fastboot --set-active=a, managed to get back to twrp so now its flashed on both again. In the process of flashing lineage now, hopefully this wont chuck another error at me for gapps
Hi all
I experience kinda weird behaviour with my OP6T.
I wiped and upgraded to Android 10 a few days ago (10.3.1). I installed TWRP and immediatyl flashed Magisk using @mauronofrio all-in-one tool. I boot up, installed what I needed and all was going good.
By using the phone I noticed that in drawer there was 2 file manager app: one I think was from Google. So I downloaded an uninstaller and deleted it. After that I discovered that, without "File" (app name) I was unable to give folder access to Poweramp scan function (it was just saying the File app keep crashing).
I tried to install it again but nothing.
Now, the good stuff. Keep in mind root was working good. I also successfuly rebooted phone multiple time with no issues.
After I tried to install File app, I restarted my phone and, surprise, it keep stuck on bootloader warning screen for like 30 seconds and after it goes into recovery (TWRP).
I tried to flash recovery again together with Magisk but nothing. Same result (sometimes it wasn't even boot in TWRP but standard fastboot screen). In the end, I tried just flashing TWRP without Magisk and surprise: it booted. Without root of course.
I did some other tests, tried again (including trying to boot from slot B but that doesn't work and no decrypt message appear).
I don't understand what is going on.
What can I do further ? On Android 9 I experienced something like that but with a normal TWRP/Magisk flash it was returning all normal. It's strange because the advice from AIO says to flash TWRP and Magisk otherwise I brick the phone.
Recap:
Only TWRP installed on partiton A/B -> Phone boot with no root
TWRP (partion A/B) + Magisk (only partition A ?) -> Phone doesn't boot and go in recovery
Thanks
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
mauronofrio said:
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
Click to expand...
Click to collapse
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
rootgen said:
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
Click to expand...
Click to collapse
So maybe is something else
mauronofrio said:
So maybe is something else
Click to expand...
Click to collapse
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
rootgen said:
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
The installer patch both slots regardless of everything
Hmm, I might have missed it but after you flashed trwp to your phone did you reboot back to recovery then install root.. just asking..