Develop Bugs

[Q] Pre & Post root questions

Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!

wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
Click to expand...
Click to collapse
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?

wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Click to expand...
Click to collapse
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.

buhohitr said:
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
Click to expand...
Click to collapse
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!

deV14nt said:
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
Click to expand...
Click to collapse
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!

wha2do said:
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
Click to expand...
Click to collapse
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk

wha2do said:
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
Click to expand...
Click to collapse
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.

22sl22 said:
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks - that was the post had been reading through - appears after the kitkat OTA, latest posts mentioned problems with SU when running the original CF-AUTO Root method (flashing autorootp600mj4.tar.md5). Wondering if flashing the "newer" CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5
would be best. At this point feel confident either way!
deV14nt said:
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
Click to expand...
Click to collapse
Yep, will be downloading TWRP v2.6.3.3 and flash it and SuperSU after rooting. After rooting, will be curious to see where I sit with superuser (sorry, reading the latest posts kind of muddy whether a SU app is already installed or not, lol)...
Thanks everyone for all the great input & help!!

HTC One M8: Root/Bootloader Unlocking failed? "No SU binary"

Root/Bootloader unlocking failed? "No SU binary"
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back) and tried to root and unlock the bootloader but failed so I just stored it away .
I followed these videos. Can't paste links...new xda account:
youtube:
HTC One M8 : How to Unlock Bootloader & Root - Easiest Method
HTC One M8 : How to Root & Install TWRP Recovery - Easiest Method
I believe the first video, unlocking the bootloader, was successful(says "Software status: Modified""**Unlocked**" in bootloader mode).
In the second I believe TWRP was installed successfully (It opens up via Recovery) but the SuperSU app was not successful . I don't remember exactly what happened (it was months ago) but when I hit the SuperSU app I think it failed to update as seen in the second video at 2;29. As of today, when I try to open SuperSU, I'm presented with a message that says: "There is no SU binary installed, and superSU cannot install it. This is a problem! If you just upgraded to Android 5.0, you need to manually re-root" hit ok and SuperSU closes.
I found various fixes and such but I'm not sure which is the safest.
Sorry I'm new to android and I just don't want to ruin my device.
SOLVED
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Delete this thread I guess.

If you used the toolkit as shown in the Youtube video, that was your main problem.
The toolkit uses obsolete (and by obsolete, I mean over a year) versions of both:
SuperSU (current version is 2.46)
TWRP (current version is 2.8.7)
Using outdated versions of either/both of these with a stock Lollipop M8 will cause some major issues. Before doing any mods, its best to read and research to make sure you are using the most up-to-date procedures and files. Youtube should not be your only modding resource. Also, keep in mind that the "easiest" way, is not necessarily the "best" way.
huura said:
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Click to expand...
Click to collapse
Making a TWRP backup before flashing anything would have minimized any risk.
---------- Post added at 01:20 PM ---------- Previous post was at 01:20 PM ----------
huura said:
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back)
Click to expand...
Click to collapse
M8x is the Taiwanese, higher CPU clocked variant.

That makes sense. Thanks for all the info. woo slightly higher clock speed variant!
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?

huura said:
T woo slightly higher clock speed variant!
Click to expand...
Click to collapse
On a side note. Only thing to be aware of, the M8x can't have other versions' radios flashed to it, even with s-off; as confirmed by a few users here (including one very knowledgeable one).
By extension, this probably also means that you can't "convert" to another version by running that version's RUU.
Probably not a major issue, as all other common mods (TWRP, root, flashing custom ROMs) should work fine on the M8x. Just something to keep in mind.
huura said:
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Click to expand...
Click to collapse
My advice would be to learn how to use fastboot to install TWRP, and skip the pointless middle man apps. Doing it by fastboot is easy, and much more reliable.
huura said:
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
Click to expand...
Click to collapse
No benefits that I know of. 2.46 roots the phone (on Lollipop) just fine, no need to have any "benefits" beyond that.
Marshmallow is a different story.

Ah ok. I'll keep note of that quirk, thanks.
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?

huura said:
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
Click to expand...
Click to collapse
Its a good trick to know (as well as other fastboot commands) as it allows you to flash recovery without a working OS (not an unheard of situation, if you mess with flashing ROMs and other things enough times).
The process is pretty simple, as you most likely already have fastboot setup on your computer if you unlocked the bootloader. So flashing a recovery is simply a matter of:
1) Download the desired recovery .img to your fastboot folder (where fastboot.exe is located)
2) Connect your phone to the computer, and boot into bootloader-fastboot mode
3) Open a command prompt on the computer
4) Issue the proper fastboot command
5) Drink beer
huura said:
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
Click to expand...
Click to collapse
I haven't messed with Xposed for a while, but I think you just need to:
1) Make a nandroid of your current working setup
2) Install the Xposed apk
3) Open the Xposed app and install the desired frameworks

Figured it out, was straight forward

Nexus 7 wont mount files in TWRP

Recently I got a nexus 7 2013 5.1.1 LMY48I which I tried to root with NRT. Long story short like many other people I cant get TWRP to mount the files it needs(I get to the automated step that is suppose to open TWRP and install some files from a ZIP archive and it hangs up). First off I have a USB OTG cable coming within a couple days. I have looked for the past couple hours for a solution and keep coming up empty. Basically I have two questions, 1. what files do I need to have transferred so that I can get my Root permissions installed properly and 2. should I wait for the USB OTG calbe or should I try to use abs push

I'm in the same boat, really would like to get this thing rooted. I have been all over the WugFresh Forum, as well as Android Central and this one too of course. I have not found an answer to this problem yet. If I come across one I will post here, please do the same.

Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
https://www.reddit.com/r/AndroidQue...e_to_mount_partitions_after_flashing_twrp_on/
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating

gorilla p said:
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
Click to expand...
Click to collapse
So what version of Android are you running now. I am on 6.0.1 and want to root it. Did you apply this to to Lollipop or Marshmallow? Thanks for the info.
UPDATE: This worked for me I am now on MM 6.0.1 and rooted. Thank you for the find.

Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562

sgtfoo said:
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Click to expand...
Click to collapse
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.

AngryPotato said:
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
Click to expand...
Click to collapse
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.

diggitydogg said:
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
Click to expand...
Click to collapse
so update to 6.0.1 stock then root or flash a rooted rom?

AngryPotato said:
so update to 6.0.1 stock then root or flash a rooted rom?
Click to expand...
Click to collapse
I did a clean flash of stock 6.0.1. Then flashed the multirom version of TWRP since I have one of the newer chipsets of the Nexus 7. Then I flashed the beta SU. All was good. The issue I am having now is that I can't get the restore from within TWRP to work. I backup fine, but when I restore it gets partway through the system part and then just says Failed. Not really sure what the deal is there. I am guessing it has to do with this multirom version of TWRP, but I'm not really sure...

Rooting on Sense Marshmallow

Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Any ideas?

On Marshmallow you could try to use the beta 2.66. This version has a nice to accomplish systemless root, were root is written to boot.img and /data instead of system partition.
As I'm on Maximus HD which comes prerooted with v2.65 I can tell that this version works flawlessly on Marshmallow devices.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Freaksterz said:
Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Click to expand...
Click to collapse
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).

redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
So let's say I'm in marshmallow with trwp 3.0.0
Which version of supersu should I flash and which MOD should I choose ?

ofir_a said:
Which version of supersu should I flash and which MOD should I choose ?
Click to expand...
Click to collapse
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!

redpoint73 said:
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!
Click to expand...
Click to collapse
Thanks a lot

redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
Thanks for the insights. I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu. No matter what I do I am stuck in the htc logo bootloop. I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it. How do I go about it? I've been trying to find a solution for the last 4 hours, it's 3 in the morning. Help.

post.ratz said:
I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu.
Click to expand...
Click to collapse
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
post.ratz said:
No matter what I do I am stuck in the htc logo bootloop
Click to expand...
Click to collapse
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
post.ratz said:
I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it.
Click to expand...
Click to collapse
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.

redpoint73 said:
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.
Click to expand...
Click to collapse
Hey, thanks for the reply. It probably was too late at night and my mind had stopped functioning, a little common sense was all that was needed. The bootloop had only occurred because of me flashing the lower version of SuperSu. The good rule of thumb, forgive my lack of knowledge, I had no idea that a rooting of a device may change with the upgraded version of the OS. Woke up, took my external memory card out, transferred the SuperSu 2.65 on it and later flashed it though recovery.
Rest assured, I'll never go for a phone that does not have expandable storage option.
Thanks

Installing SuperSU on stock 3.35.401.32

Hey all,
Tried flashing SuperSU 2.78, and phone went boot-looping.
Tried flashing SuperSU 2.46, and this time it got stuck on the white screen, and booting was not possible (had to wait until the battery drained out).
I'd appreciate it if anyone could explain why this happens, and of course a version which should work.
Thanks!
* Firmware 3.35.401.32
* TWRP twrp-3.0.2-0

I can't explain why it happens. Try 2.66 first and if that doesn't work then try 2.65.

I have a similar problem.
Installed 2.78 and 2.76 and it went to boot-loop. 2.46 rebooted successfully but no root access.
Sunshine says it cannot get temproot access. Please advice.

It's been stated so many times and there seem to be about 1000 threads here in the Q&A section which all deal with this topic. Is there a specific reason why nobody uses the search function?
Firmware versions up to 2.x require you to use SuperSU 2.49. Firmware 3.x on the other hand only works with SuperSU 2.64 or 2.65. (I'm talking about the flashable zips. Updating via play store afterwards is absolutely no problem.)
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
It's been stated so many times and there seem to be about 1000 threads here in the Q&A section which all deal with this topic. Is there a specific reason why nobody uses the search function?
Firmware versions up to 2.x require you to use SuperSU 2.49. Firmware 3.x on the other hand only works with SuperSU 2.64 or 2.65. (I'm talking about the flashable zips. Updating via play store afterwards is absolutely no problem.)
Click to expand...
Click to collapse
Thanks!
I really did try and search for a solution. Honestly! Maybe I need to work on my searching skills.

I used 2.76 and sunshine ,twrp 3.02 hima , I had no problems at all ??