So, I finally figured out how to replace those dreadfully awful HTC emojis with the iPhone emojis...however, it involves deleting a file (/system/fonts/AndroidEmoji-htc.ttf). once this file is deleted, everything is fine and dandy. The HTC emojis are replaced by the stock google ones, which can then be replaced with the stock iPhone ones via an app. however, when you restart the phone for some reason AndroidEmoji-htc.ttf comes back. I have tried renaming to AndroidEmoji-htc.ttf.bak and renaming the AndroidEmoji.tff to AndroidEmoji-htc.ttf; neither of which worked. any ideas as to how I can stop this from happening? I'll buy whoever figures this out a beer. (I really don't like HTC's emojis...)
I'm guessing your rooted, without s-off. If I'm correct, you need to disable the system protection HTC has put in. It is essentially the same as the external sd block kitkat has, but on the /system partition. If you search around, you can find a module in the regular m8 dev section that disables it. Or flash elementalx kernel. Or s-off.
akitten007 said:
I'm guessing your rooted, without s-off. If I'm correct, you need to disable the system protection HTC has put in. It is essentially the same as the external sd block kitkat has, but on the /system partition. If you search around, you can find a module in the dev section that disables it. Or flash elementalx kernel. Or s-off.
Click to expand...
Click to collapse
When you say module, are you referencing an xposed module?
I mean a kernel module, which are basically small plugins that kernels use. I cannot find the link right now as I am on my phone. But I recommend searching the MAIN m8 thread for removing system protection.
akitten007 said:
I mean a kernel module, which are basically small plugins that kernels use. I cannot find the link right now as I am on my phone. But I recommend searching the MAIN m8 thread for removing system protection.
Click to expand...
Click to collapse
Okay, I downloaded elementalx kernel and am running it and I have tried numerous times to install s-off using firewater.. No success, could it be that the 4.4.3 update breaks current S-off methods?
Ghstudent said:
Okay, I downloaded elementalx kernel and am running it and I have tried numerous times to install s-off using firewater.. No success, could it be that the 4.4.3 update breaks current S-off methods?
Click to expand...
Click to collapse
I am not sure if firewater is compatible with the OTA because I already s-offed on 4.4.2. But if you have elementalx installed, the sys protection should be disabled. Just make sure the /system partition is set to write on your file manager, and try deleting the file.
PS: Removing any stock files with /system causes OTAs to fail. I recommend taking a stock backup, or make sure you download a stock backup so you don't have any OTA trouble. Just something to remember.
akitten007 said:
I am not sure if firewater is compatible with the OTA because I already s-offed on 4.4.2. But if you have elementalx installed, the sys protection should be disabled. Just make sure the /system partition is set to write on your file manager, and try deleting the file.
PS: Removing any stock files with /system causes OTAs to fail. I recommend taking a stock backup, or make sure you download a stock backup so you don't have any OTA trouble. Just something to remember.
Click to expand...
Click to collapse
For some reason elementalx broke my root, any ideas on this?
Ghstudent said:
For some reason elementalx broke my root, any ideas on this?
Click to expand...
Click to collapse
Have you tried opening the SuperSU app? If root is broken,it should show a popup to install it. And make sure you downloaded the correct version of elementalx since there is 2 sense versions, one 4.4.2 and one 4.4.3.
Ghstudent said:
Okay, I downloaded elementalx kernel and am running it and I have tried numerous times to install s-off using firewater.. No success, could it be that the 4.4.3 update breaks current S-off methods?
Click to expand...
Click to collapse
It always possible, and you should always look before making the OTA leap. See my comment #3 here: http://forum.xda-developers.com/showpost.php?p=55088843&postcount=5
Firewater hasn't worked on AT&T software for a while now. Sunshine has worked to this point (Android 4.4.2) but I'm not sure if anyone has tried with the new 4.4.3 update (software 2.23) yet.
redpoint73 said:
It always possible, and you should always look before making the OTA leap. See my comment #3 here: http://forum.xda-developers.com/showpost.php?p=55088843&postcount=5
Firewater hasn't worked on AT&T software for a while now. Sunshine has worked to this point (Android 4.4.2) but I'm not sure if anyone has tried with the new 4.4.3 update (software 2.23) yet.
Click to expand...
Click to collapse
Doesn't sunshine require a $25 donation?
Ghstudent said:
Doesn't sunshine require a $25 donation?
Click to expand...
Click to collapse
Yes.
---------- Post added at 09:45 AM ---------- Previous post was at 09:43 AM ----------
akitten007 said:
I mean a kernel module, which are basically small plugins that kernels use. I cannot find the link right now as I am on my phone. But I recommend searching the MAIN m8 thread for removing system protection.
Click to expand...
Click to collapse
I see the OP has removed the write protection with ElementalX, but for others reading this thread, this is the kernel module being referred to: http://forum.xda-developers.com/showthread.php?t=2701816
Although a custom kernel such as ElementalX will also work.
redpoint73 said:
Yes.
Click to expand...
Click to collapse
I thought so, I finally got elementalx to work, so I will stick with it. Thanks though!
Related
A friend of mine had her Eris metroflashed to MetroPCS. Calls and SMS work, but she wants me to provision the rest of it to work like i did with my own Eris on metro. I tried it to find out the Eris one click root app is not on the market anymore however i had the APK, erisone.apk. I loaded it to her SD card and downloaded Astro File Manager and attempted to install, which it proceeded to tell me it couldnt be installed on that phone. All i need is RA-Eris recovery as i will be loading a custom ROM. Is there an easy way to change the recovery on it so i can do this? I was thinking i just needed to update to 2.1 OTA (can someone provide the link? the old link from google doesnt work anymore) then the Erisone.apk will work (this apk loads custom recovery as well as a root very easily). I need to load a custom ROM before i can begin with the provisioning, what do you guys think i should do?
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
roirraW "edor" ehT said:
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
Click to expand...
Click to collapse
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Helgaiden said:
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Click to expand...
Click to collapse
You have to be rooted and have a custom recovery in order to install a custom ROM.
Editing...ignore what I had posted in this space before.
The second link (starts with "Failing that...") says it works with 1.5.
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Helgaiden said:
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Click to expand...
Click to collapse
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
roirraW "edor" ehT said:
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
Click to expand...
Click to collapse
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Helgaiden said:
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Click to expand...
Click to collapse
I'm sure they all probably do, but I'm sure they say definitively in their threads, too. Everyone who roots wants to install a custom recovery so that they can flash rooted ROMs. Most everyone, anyway. Only those who just want the stock ROM but rooted wouldn't care about the recovery, but those are a minority.
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Helgaiden said:
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Click to expand...
Click to collapse
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THIS WON'T WORK!!!!
Click to expand...
Click to collapse
roirraW "edor" ehT said:
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
Click to expand...
Click to collapse
yeah i got that much out of it. Okay, thanks for your help.
The jcase "One Click" .apk does not work on 1.5, as you discovered.
Note that the root exploit method that One Click employs does work on 1.5 - but unfortunately the One Click app itself only runs on 2.1.
The Universal Eris Root for Dummies! method will work on both 1.5 and 2.1; it uses the same (wag3slav3) rooting exploit, but does not require the 2.1 OS to be running in order to work correctly. All it does to your phone is to install the Amon_RA custom recovery - exactly what you are looking for.
This method is the same one referenced by scary alien in his post mentioned above - the second URL in his post.
I've said this before, but I'll say it again: when you say "rooted", it means different things to different people. The most general definition is that you have "installed something on your phone which gives you privileges to alter some or all of the phone software which the device manufacturer did not intend".
So - you can have an engineering bootloader on a phone, but a completely stock OS... and that would be a "rooted" phone. Same deal for a set of root tools installed in the OS, but a S-ON bootloader and a stock recovery partition. Or a stock bootloader, a stock OS, but a custom recovery - again, that is also a "rooted" phone. In all three cases, you now have the means to alter whatever you want on the phone. That's all that "rooted" really means; it doesn't necessarily mean that the OS has been kanged up.
bftb0
ahh confirmation it doesnt work on 1.5, nice haha. Well thanks. Ill look into the Dummies root method but right now im leaning toward's GRDLOCK's method. At least i know i have good valid options though, thanks!
So I rooted my EVO 4G LTE, hurray! I have a number of questions and after some tedious searching I could not find any clear and consise answers. There is just too much info out there, even the rooting was not so easy!
So I have three main issues; 1) Bloatware 2) A stuck OTA update 3) System error messages after each reboot.
Bloatware
Using ESFileExplorer and even TitaniumBackup(free) I attempted to uninstall a number of the apps that came pre-installed and that hog RAM. Each time I reboot they come back, some attempts to uninstall apps have sent the phone straight into reboot and all the apps came right back.
I am not looking to get rid of sense, this phone is a lifeline to my livelihood and its dependability is paramount, so I would like to remain as stock as possible. I just want to free it up so that it runs a bit better and less laggy.
My task manager app shows that 0.89/1.0GB is is use and that is ridicules!
OTA Update
Sometime after rooting (this was a brand new replacement device when I started) the 3.17.651.5 update got downloaded and is now showing up all the time asking to do the actual installation. Is there any way to delete the update files and prevent the message from popping up all the time?
Reboot Error
This is just really a minor nuisance, but while we are at it I figure why not ask. After each reboot since rooting I get a System Error Message saying something like 'the phone experienced an abnormal reboot'. Any way to prevent it from doing that?
Misc
Also, I cannot seem to find any instructions (that are relevant to today, all are from 2012 and early 2013) for allowing the EVO to act as a WiFi hotspot. Any tips?
Thank you all for this great resource and in advance for all your help!
You need to S-OFF. Your system is write protected, which is why when you reboot, the apps return. I'd honestly also recommend updating to the data/media partition layout and then achieving S-OFF with Rumrunner. Once you're S-OFF, everything will work fine, and as a bonus you'll have Sense 5 .
Captain_Throwback said:
You need to S-OFF. Your system is write protected, which is why when you reboot, the apps return. I'd honestly also recommend updating to the data/media partition layout and then achieving S-OFF with Rumrunner. Once you're S-OFF, everything will work fine, and as a bonus you'll have Sense 5 .
Click to expand...
Click to collapse
I just figured the S-OFF out thanks to exhaustive Google searches, now I am seeing your post about partitions and I am not sure what you are talking about.
How do I update partitions? Do I have to do that before I use the rumrunner exploit to gain S-OFF?
webby88 said:
I just figured the S-OFF out thanks to exhaustive Google searches, now I am seeing your post about partitions and I am not sure what you are talking about.
How do I update partitions? Do I have to do that before I use the rumrunner exploit to gain S-OFF?
Click to expand...
Click to collapse
All you have to do is run the 4.13.651.4 RUU. @Magnum_Enforcer has a guide that I believe will assist you.
Captain_Throwback said:
All you have to do is run the 4.13.651.4 RUU. @Magnum_Enforcer has a guide that I believe will assist you.
Click to expand...
Click to collapse
This Post?
This will simply give me JellyBean and Sense 5? Also, will I loose root? Weren't there major problems with this update?
That's the guide he's referring to, yes. Just scroll down to the section on RUU's for more info. Link to the aforementioned RUU is at the bottom of the first post. You will lose root but you can use HTC Dev to unlock and root again, and no, there were not major problems with this update.
Magnum_Enforcer said:
That's the guide he's referring to, yes. Just scroll down to the section on RUU's for more info. Link to the aforementioned RUU is at the bottom of the first post. You will lose root but you can use HTC Dev to unlock and root again, and no, there were not major problems with this update.
Click to expand...
Click to collapse
Aha, but why did HTC pull it then?
Also, will this resolve my stuck 'update pending' issue? And will I loose data? Will my installed TWRP recovery be an issue?
webby88 said:
Aha, but why did HTC pull it then?
Also, will this resolve my stuck 'update pending' issue? And will I loose data? Will my installed TWRP recovery be an issue?
Click to expand...
Click to collapse
It was never pulled, per se, but it was never released to the masses, either. The issue was how Android 4.3 was implemented on this device-that it required a RUU instead of a traditional OTA update, which is somewhat unusual but that's how the update had to be handled due to the internal storage getting re-partitioned. Anything you have on your internal storage you'll need to back up to your computer because it will be lost when the RUU runs. Also, TWRP won't be an issue. Just reinstall the modified version from @Captain_Throwback once you've updated with the RUU (you can click on the TWRP version number in his sig & it will take you to the appropriate link).
Note that there were issues with the initial Android 4.3 updates but they were resolved with the .4 RUU, which is why I don't have links to any of the previous RUU's. The issue was with the roaming option, mostly.
Magnum_Enforcer said:
It was never pulled, per se, but it was never released to the masses, either. The issue was how Android 4.3 was implemented on this device-that it required a RUU instead of a traditional OTA update, which is somewhat unusual but that's how the update had to be handled due to the internal storage getting re-partitioned. Anything you have on your internal storage you'll need to back up to your computer because it will be lost when the RUU runs. Also, TWRP won't be an issue. Just reinstall the modified version from @Captain_Throwback once you've updated with the RUU (you can click on the TWRP version number in his sig & it will take you to the appropriate link).
Note that there were issues with the initial Android 4.3 updates but they were resolved with the .4 RUU, which is why I don't have links to any of the previous RUU's. The issue was with the roaming option, mostly.
Click to expand...
Click to collapse
Ok, I get it. Thanks for taking the time to explain this!
One more question though, I see in your post a link to 4.13.651.4, but I see another thread from @Captain_Throwback here which mentions a Odex or Deodex - what is that? And all those useful mods (battery percentage, camera shutter sound, power menu, 30 step volume etc etc), which should I use?
webby88 said:
Ok, I get it. Thanks for taking the time to explain this!
One more question though, I see in your post a link to 4.13.651.4, but I see another thread from @Captain_Throwback here which mentions a Odex or Deodex - what is that? And all those useful mods (battery percentage, camera shutter sound, power menu, 30 step volume etc etc), which should I use?
Click to expand...
Click to collapse
He has rooted odex & deodexed ROM's based off the RUU. If you want to install any mods you'll need to run the deodexed version.
Hi Guys,
I have an HTC M8 International (Australia), and I was attempting to Root and S-Off my device to allow me to install the GPE Rom. Following a tutorial I found on XDA, I was able to root, and install the InsertCoin Rom, but it wouldn't allow me to run Firewater as my device is too new.
It also seems that because I am running InsertCoin, I cannot run SunShine as it doesn't recognise it as a stock ROM.
I realise I shouldn't have mucked around with it unless I knew exactly what I was doing, but I thought the tutorial would have held me in good stead.
Stupidity aside, can anyone help me get my M8 back to stock. As it stands, I now have no Wi-Fi, and charging is sporadical, needing to have permissions reset through TWRP every time I connect to USB.
I am running a Mac, and have TWRP installed on my device. Happy to provide any more information needed, I would just love someone to be able to help get my phone back into a working state!
Any way you can get a stock backup on your phone would be ideal. I know with the ATT variant I found a posted stock zip I had to extract and place in my TWRP backup folder.it can be as simple as that unless you made a stock backup than restore it and run Sunshine again
Below is a link to most all backups
Just fallow the instructions.
http://forum.xda-developers.com/showthread.php?t=2701376
jball said:
Any way you can get a stock backup on your phone would be ideal. I know with the ATT variant I found a posted stock zip I had to extract and place in my TWRP backup folder.it can be as simple as that unless you made a stock backup than restore it and run Sunshine again
Below is a link to most all backups
Just fallow the instructions.
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
I have a friend who is in the same situation. These posts should be cleaned up and made easier to understand/comprehend. I am a systems engineer responsible for XaaS integration and code heavily in Ruby and Python and even these instruction seem complicated to me.....
jball said:
Any way you can get a stock backup on your phone would be ideal. I know with the ATT variant I found a posted stock zip I had to extract and place in my TWRP backup folder.it can be as simple as that unless you made a stock backup than restore it and run Sunshine again
Below is a link to most all backups
Just fallow the instructions.
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Unfortunately, there doesn't seem to be a recovery available for my version (2.23.841.1). If I download a copy of the stock rom from Android Revolution, would I be able to flash it through TWRP, or would it still require S-Off?
ngerasimatos said:
I have a friend who is in the same situation. These posts should be cleaned up and made easier to understand/comprehend. I am a systems engineer responsible for XaaS integration and code heavily in Ruby and Python and even these instruction seem complicated to me.....
Click to expand...
Click to collapse
It's HTC for you man.I find it fun
---------- Post added at 01:34 AM ---------- Previous post was at 01:32 AM ----------
drewcaddy said:
Unfortunately, there doesn't seem to be a recovery available for my version (2.23.841.1). If I download a copy of the stock rom from Android Revolution, would I be able to flash it through TWRP, or would it still require S-Off?
Click to expand...
Click to collapse
If it states that the stock ROM can be installed using TWRP than I would think you could.I'm at work so I can't research it right now
jball said:
It's HTC for you man.I find it fun
---------- Post added at 01:34 AM ---------- Previous post was at 01:32 AM ----------
If it states that the stock ROM can be installed using TWRP than I would think you could.I'm at work so I can't research it right now
Click to expand...
Click to collapse
My mistake - it wasn't a stock ROM, only based upon one. Through a lot of playing around and flashing, I have managed to get a functioning device back up and running. I flashed with Android Revolution ROM, and that allowed me to install SunShine to gain S-Off. Also had to re-flash the firmware, as it knocked out my Wi-Fi. Following these steps was really helpful:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
For now, it's running well. I used to have a Samsung S5, and I don't recall there being as many issues as this, but it's all a learning curve
drewcaddy said:
My mistake - it wasn't a stock ROM, only based upon one. Through a lot of playing around and flashing, I have managed to get a functioning device back up and running. I flashed with Android Revolution ROM, and that allowed me to install SunShine to gain S-Off. Also had to re-flash the firmware, as it knocked out my Wi-Fi. Following these steps was really helpful:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
For now, it's running well. I used to have a Samsung S5, and I don't recall there being as many issues as this, but it's all a learning curve
Click to expand...
Click to collapse
I to have had Samsung S2,S2 Skyrocket,S4,S4 Active and the easiest of them all was my beloved Nexus 5 .now I will say it's definitely a bit more to stay on top of but is a good challenge [emoji122]
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
EDIT: New OTA [YNG1TAS17L]:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS17L-bacon/e816218e8a/cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Credits to @julian_klode:
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Note: I initially wasn't aware about the source of the base zip file that I used to pack the necessary files until julian_klode mentioned it in the Q&A thread.
There is no difference between this one and his, just the fact that I update mine manually. So, I think you should follow his thread instead.
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Outstriped! I was thinking to make Debug kernel, but they released it sooner
Thank you so much. Puzzle and Dragons doesn't like Supersu, but works perfect with CM's superuser.
works fine here, thanks!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
thank you , works perfectly!
inscythe said:
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
Click to expand...
Click to collapse
thx:good:
Works great please keep this updated with each OTA if possible!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
That did not work for me
droidextra said:
That did not work for me
Click to expand...
Click to collapse
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
srgudhka said:
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
Click to expand...
Click to collapse
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
inscythe said:
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
Click to expand...
Click to collapse
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
All good here! I went into the Supersu settings and did a FULL UNINSTALL OF ROOT. Once that was done, I went into TWRP and flashed CM zip provided by OP... Bam. Done and no problems. Thank you, OP!
Wisiwyg said:
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
Click to expand...
Click to collapse
I perhaps wasn't very clear about my above suggestion.
What I meant is that, there is an official insecure boot.img (the kernel) which I linked above and included in my zip package. I'm not telling him to install both SuperSU and the built-in root.
SuperSU has some features that is not present in the built-in root though, like logging or tapjacking protection. Privacy Guard is pretty nifty, but I still miss the old interface of SuperSU.
inscythe said:
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Click to expand...
Click to collapse
Is there any way to make this work with franco kernel r41? Thanks...
ten_tickles said:
Is there any way to make this work with franco kernel r41? Thanks...
Click to expand...
Click to collapse
I think it's the issue with Franco's own kernel... Even the nightly CM12 users with the built-in root enabled also had the root access disabled.
SuperSU works in this case because it relies on an init.d su-enabling service.
Just wait for Franco to fix it, since the CM11S versions works well with the built-in root. I am also a FK paid user, so this is a bad situation for me as well...
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
I uploaded it here sorry it's not a better host but I'm on my phone ATM lol. http://uploadmirrors.com/download/R8ADOYOG/icial-12.0-signed-YNG1TAS17L-bacon-superuser.zip All I did was get the ota URL from here and changed the ending to cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img I guess the system automatically makes the debug images when the ota rolls out. So I imagine the same thing would work for next ota. You just rename it to boot.img and replace the one in the zip from this thread and rename the zip and flash.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Not that hard to make, right? But super practical to keep this if you often jumping ROMs.
SimonTS said:
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
Click to expand...
Click to collapse
Sorry, was doing overtime at work. I've updated the OP too.
I didn't think this warranted a development thread at this point, Mods may disagree and move it. Since a few people, myself included, need some TouchWiz features and want something closer to a stock rom than Jasmine but debloated, deodexed with the Verizon wifi tether provisioning disabled, I threw this together. I'll try to answer any questions and fix any issues that pop up but I cant make any promises due to work and other projects. If I do move forward with anything I may try to port the stock Verizon Note 4/5, but that's getting ahead of myself.
Now the usual warning about your warranty being voided (as if any Note 3s are under warranty and you didn't void it rooting/flashing recovery) and me not being responsible for you bricking your device because I was stoned when I packaged this.
Download the rom here.
So far the only changes to the stock OF1 are:
Deodexed
Moderatly debloated
Wifi tether provisioning disabled
Start up sound disabled
Rooted*
Busybox added*
*SuperSu and Busybox packages are installed during rom installation.
A list of debloated files can be found here.
Coming soon
Some files were left because they are too integrated into TouchWiz. I don't want people confused by orphaned menu items or get FCs. Some stuff I left because people I know use them. If you want anything back you'll have to get it yourself for now, sorry. I'm open to suggestions on stuff to keep and stuff to remove, but I'll want a good description of their functions before I remove anything. I'm funny about not deleting stuff I don't know what it does.
For those looking for Xposed, I'm using the latest Snapdragon requestConcurrentGC version from here.
Flashing instructions are pretty simple. Boot to TWRP, make a backup, wipe system/data/dalvik/cache, flash the rom and reboot system.
All thanks go to the Yemen rooters and @beaups and @ryanbg for liberating our devices.
thanks i tried it out and its working great! however one of the apps i like is S-Note and you debloated it :/ along with galaxy store. which i cannot find a download source for either, and its needed to reinstall s-note. anyway its a crucial app for the S-pen launcher and s-pen features.
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
also im not sure if its just me but i noticed the task manager is a little strange and is missing the ram clear button. ill take a screen shot and upload later
doombuger said:
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
Click to expand...
Click to collapse
All of the stock apps are in the system.img files in the Stock Odin tar bundles (available from sammobile.com for instance)
The only trick to getting them out of there is that those (system.img) image files are "sparse" ext4 files. The Android development environment has a tool called "simg2img" which allows you to create an uncompressed image file, which can then be mounted as an ext4 filesytem (loopback mount), and you can browse through there and copy out anything you want.
All of this is more convenient to do in a Linux environment (get yourself VirtualBox and install Ubuntu), but there are workarounds using Windows too, and there are even tutorials here on XDA on how to do this both ways. (Use searches for "sparse image" or "simg2img")
An even easier way is to simply pull them out of TWRP backup files of your rooted-stock ROMs; those "system.ext4.win00x" are just tar files. Heck, you could probably even use 7-zip for that.
You do make backups, right?
Ask your devs to do things that are interesting for the dev and difficult for almost any anybody else to do; not the simple stuff like "go get me some freely available files".
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Morlok8k said:
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Click to expand...
Click to collapse
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
njdan30 said:
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Click to expand...
Click to collapse
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Neo3D said:
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Click to expand...
Click to collapse
yes you need to root 1st in order to get bootloader unlocked then head to play store for flashify the take the 1st(newest recovery)and thats it.check the yemen root http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 for of1 use that then the retail to dev unlock and enjoy,for unlock i did the adb method but think theres a 1 click unlock now also http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Problems with data
I appreciate all of your hard work. I do have a question though. Every single 5.0 and newer rom I have tried I have problems getting my data to work reliably. I get 4G after reboot but as soon as I send/receive a SMS message it reverts to 3g until the next reboot. This was a clean install and I've also tried reinstalling sim, done factory reset, cleared all data, everything under the sun I can think of. Nobody else seems to have this problem. Any ideas? Other than that this is exactly what I'm looking for.
May I ask somebody create a .tar version to use with odin.
I has no custom recovery .
Tried peazip software to convert .zip to .tar but odin always hangs when i use file
Long time first boot. thoght i made a brick Thanks mate
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
nitroevo said:
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
Click to expand...
Click to collapse
I am also looking for advice. My Note 3 is in a similar position with NC2 and Baja ROM in the stock slot of safestrap.