All code changes needed for N Preview have been rolled into the BETA releases starting v2.71 BETA. This thread is now closed. If a new N Preview release comes out, or N Final is released, this thread may be re-opened. For now, proceed to the BETA thread!
OLD CONTENT
This thread is dedicated to SuperSU on N Preview. With the first few releases I'm not merging it directly with the BETA branch, as there have been some invasive changes under the hood regarding SELinux handling, and there should be a little bit more testing done before going there. Still, I expect this to be done within the next week or two.
I've only had the chance to test on the 5X so far, so there is some risk involved. If you're not comfortable reflashing everything due to bootloops, crashes, etc, wait for others to play the guinea pig.
RC-SuperSU-v2.70-20160314191951.zip
As this hasn't been merged with the BETA branch yet, I'm not updating the main CF-Auto-Root distribution either. But as TWRP isn't working yet on all N Preview devices either, attached are test CFAR versions.
Note that you are also welcome to flash this SuperSU version on pre-N firmwares, and report back if everything still works as expected.
If you have tried other methods of rooting, you need to at least flash back your stock boot.img before flashing SuperSU.
Depending on how much you have played around, reflashing /system may also be a wise move.
If you came from SuperSU v2.69, you need to reflash via TWRP or CFAR. Installing just the APK and updating binaries will not fix all the issues!
--- reserved ---
--- more reserved ---
Im using now phh should i flash over it?
Sent from my Nexus 6 using Tapatalk
Thanks Chainfire , good job, downloading
When trying to flash CF-Auto for Shamu using windows-fastboot i get a double oem unlock pop up on my phone after i click the first yes unlock although im already oem unlocked it will then pop right back up. to which my bootloader will then freeze for a few min then come responseive again but nothing was flashed i would receive a error while looking at the .bat it has the oem unlock twice in the codeing is this on purpose ?
Nexus only?
That's quick, thanks for all your contribution to this.
hamada samir said:
Nexus only?
Click to expand...
Click to collapse
For sure Nexus only, N preview is not available on any other phones.
Techno Peter said:
For sure Nexus only, N preview is not available on any other phones.
Click to expand...
Click to collapse
Thanks my brother ❤
This version is working fine on my Nexus 6P with MM MHC19I.
Ohh yeah. Back in business
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
N6, RC-SuperSU-v2.69-20160313161431.zip through TWRP 3.0.0.1 seems OK. Testing in progress.
How are ya'll flashing? I can't get any version of TWRP to run on my N9, it just keeps restarting recovery, and I don't know what else I would try.
Can i flash it over phh cause i already root?
Sent from my Nexus 6 using Tapatalk
N6P
Worked on N6P, NPC56P
Thank You
Chainfire said:
This thread is dedicated to SuperSU on N Preview. With the first few releases I'm not merging it directly with the BETA branch, as there have been some invasive changes under the hood regarding SELinux handling, and there should be a little bit more testing done before going there. Still, I expect this to be done within the next week or two.
I've only had the chance to test on the 5X so far, so there is some risk involved. If you're not comfortable reflashing everything due to bootloops, crashes, etc, wait for others to play the guinea pig.
RC-SuperSU-v2.69-20160313161431.zip
As this hasn't been merged with the BETA branch yet, I'm not updating the main CF-Auto-Root distribution either. But as TWRP isn't working yet on all N Preview devices either, attached are test CFAR versions.
Note that you are also welcome to flash this SuperSU version on pre-N firmwares, and report back if everything still works as expected.
If you have tried other methods of rooting, you need to at least flash back your stock boot.img before flashing SuperSU. Depending on how much you have played around, reflashing /system may also be a wise move.
Click to expand...
Click to collapse
Thank you @Chainfire! Does this root method reside in the System Partition, or is it Systemless. Also, do we need to type in adb commands in TWRP before installing to force Systemless installation?
Thank you again:laugh:
Hey Chainfire!
Just a few question again from one of your supporters
Is it possible to receive OTA's after rooting N with your method? Or is their another way (like for example via your app "Flashfire")?
And can you flash new preview builds over a rooted build?
Thank you in advance
Help The Peace said:
Hey Chainfire!
Just a few question again from one of your supporters
Is it possible to receive OTA's after rooting N with your method? Or is their another way (like for example via your app "Flashfire")?
And can you flash new preview builds over a rooted build?
Thank you in advance
Click to expand...
Click to collapse
Android N OTA`s - it`s full system images, so it doesn't matter your device rooted or not.
Kameechewa said:
How are ya'll flashing? I can't get any version of TWRP to run on my N9, it just keeps restarting recovery, and I don't know what else I would try.
Click to expand...
Click to collapse
unzip and run root-windows.bat, or mac or linux sh file, depends on you OS.
ohad129 said:
Can i flash it over phh cause i already root?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Read first post
Related
Meet EZToolkit for the HTC First
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
-Unlock the bootloader
-Flash TWRP (Flyhalf205 thanks for your hard work )
-Flash CWM (Flyhalf205 thanks for your hard work )
-Flash your own recovery
-Root with SuperSU
-Install HTC Drivers
-Install GApps
-Push files to the phone's SDCard/Internal Storage
-ADB Commands
-Fastboot Commands
-Enter your own custom ADB/Fastboot Command!
-Flash boot.img
-Check for ADB Devices
-Check for Fastboot Devices
-EZ UI
-Simplistic Metro look
-Super small! Small screen size friendly.
-Noob friendly
I will make a step-by-step guide on how to use it soon. I am currently working on it.
This supports the HTC First.
Temporarily removed dl link due to new update coming in September.
-I do my absolute best to code this without bugs and I try it out before I release it. I spent quite a while going through making sure the toolkit works. If you find any bugs, glitches, typos, button not working, script not working, etc. or simply want me to implement a feature into the toolkit, PLEASE LET ME KNOW ^^ (This was over 570 lines of code in Visual Studio 2013 you know, and I am a human being ). While this is what I do on my side, as with most tools, you use EZToolkit at your own discretion.
-Wizzrah
Email Support: [email protected]
Nice, this covers the basics perfectly!
Finaly. i was about to make a picture guide on how to do this manually without the program.
should i still do it?
If you want
russian392 said:
Finaly. i was about to make a picture guide on how to do this manually without the program.
should i still do it?
Click to expand...
Click to collapse
Only if you want to. I decided to make a toolkit because:
1. I was bored.
2. I thought it would be cool.
Thanks!
killall-q said:
Nice, this covers the basics perfectly!
Click to expand...
Click to collapse
Yep! I will hopefully post my other toolkits as well as make more for other HTC Models.
wizzrah said:
Introducing Wizzrah's HTC First Toolkit v1.0
Click to expand...
Click to collapse
Please see PM
Hey guys, an update for this toolkit is coming. Thanks for your participation.
Update
I have updated the toolkit!
This will definitely be of great help by speeding things up!
abrahammmmmmm_ said:
This will definitely be of great help by speeding things up!
Click to expand...
Click to collapse
Thanks. I'm already working on a new project for EZToolkit where one toolkit will support multiple devices. I will update this toolkit soon. I have a lot planned so more features are coming
Hi guys, I'm going to fix the website. Links will be down for a little bit. Thanks.
Link Fixed. Move it to a temporary download page while I work on the website.
I appreciate this...working on it..from stock I'm trying to figure out what to do first...it won't reboot into recovery to root
Sent from my SAMSUNG-SGH-I747 using Tapatalk
rjcormier said:
I appreciate this...working on it..from stock I'm trying to figure out what to do first...it won't reboot into recovery to root
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Are you on the rooting process? Are you trying to boot into recovery to flash supersu?
Sent from my One Xl using Tapatalk
Yes...so I realized I have to unlock the boot loader first...time spent on HTC website... Then it wasn't showing up in adb so I have to figure out the drivers or adb issues first
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I already have CMW installed, can i flash supersu 1.89, without any compatibility problem ?
xtreme2020 said:
I already have CMW installed, can i flash supersu 1.89, without any compatibility problem ?
Click to expand...
Click to collapse
I don't see why you would have any problems.
Perhaps someone here can help me. I did an RUU on my phone after I had already rooted and installed a custom ROM because I was having some problems with music playback. The RUU fixed the problem and I thought I should try to unlock the bootloader again to begin the rooting process but when I did my phone got stuck in a bootloop. I was able to install a recovery after unlocking but I was not able to flash a boot.img to my phone again. Any help would be great. Thanks!
lastrastuff said:
Perhaps someone here can help me. I did an RUU on my phone after I had already rooted and installed a custom ROM because I was having some problems with music playback. The RUU fixed the problem and I thought I should try to unlock the bootloader again to begin the rooting process but when I did my phone got stuck in a bootloop. I was able to install a recovery after unlocking but I was not able to flash a boot.img to my phone again. Any help would be great. Thanks!
Click to expand...
Click to collapse
Hello. Did you flash a ROM in recovery?
-Wizzrah | Sent from my AT&T HTC One X running CodefireX 4.4.2
Works! Thanks for making this tool!
kprice8 said:
Geohot will not be releasing any further updates. He is now working for Google to find and patch these and other exploits in not just Android code, but anything computer based that touches the internet.
Click to expand...
Click to collapse
landshark68 said:
Read back in the thread a few pages - 1) GeoHot works for Google now. Hired to find and close exploits like the one towelroot used to root devices; 2) towelroot used a specific vulnerability in kernels dated before June 3. If your kernel is dated after June 3, the vulnerability has been patched and there is nothing GeoHot can "fix" to make towelroot work on your device; and related to that 3) either your phone has the vulnerability or it doesn't and towelroot either works to root your device or it doesn't and there is nothing GeoHot can do to fix towelroot to make it work for your device. Plus, like I said before GeoHot works for Google now so he can't create programs or apps that root phones by exploiting vulnerabilities he is supposed to now be fixing. Now that this same question has been answered for the 1,000,000th time in this thread, can we please get it closed?
Click to expand...
Click to collapse
I was looking forward to being able to snatch OTAs while still rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@EMSpilot please don't sell your tablet... at least until Android L releases for the Tab S and you've released a stock, rooted ROM running it.
Oh well....there's nothing stopping those who's already rooted from flashing a future custom Android L rom, right? D
kenkiller said:
Oh well....there's nothing stopping those who's already rooted from flashing a future custom Android L rom, right? D
Click to expand...
Click to collapse
As long as dev support is there, will be good. But dev support is what has me worried.
Sent from my SM-G900P using Tapatalk
Y.G. said:
As long as dev support is there, will be good. But dev support is what has me worried.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Look on the bright side. We needed CM and other AOSP variants in the past because most devices performed like crap. Now while not as smooth as stock Android, still rather speedy. Customization can be done with xposed mods.
Even if stuck on stock, it's not really that bad, to be honest.
You guys need to start learning something... for the sake of development...
kenkiller said:
Look on the bright side. We needed CM and other AOSP variants in the past because most devices performed like crap. Now while not as smooth as stock Android, still rather speedy. Customization can be done with xposed mods.
Even if stuck on stock, it's not really that bad, to be honest.
Click to expand...
Click to collapse
No, I'm with you. I don't flash AOSP ROMs. I'm just afraid of not being able to upgrade to a stock, rooted TouchWiz Android L ROM.
But you're right, Samsung has put in the work and optimized TouchWiz over the years. I have no complaints with the performance.
I've just root my T705.
edan1979 said:
You guys need to start learning something... for the sake of development...
Click to expand...
Click to collapse
Sometimes we're just lazy. I'll be honest. Different priorities take over. For me it's a kicking 3 month old baby.
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
Y.G. said:
No, I'm with you. I don't flash AOSP ROMs. I'm just afraid of not being able to upgrade to a stock, rooted TouchWiz Android L ROM.
But you're right, Samsung has put in the work and optimized TouchWiz over the years. I have no complaints with the performance.
Click to expand...
Click to collapse
I don't see why not. We're rooted with custom recoveries. As long as someone released a proper rom it can be flashed.
Otherwise just use Odin to flash the stock rom and root it again.
i feel the same last time... until the tab 7.7 was kind of forgotten... so i start to learn basic thing... dont wanna see that on tab s... (but i think its going to be the same)
edan1979 said:
i feel the same last time... until the tab 7.7 was kind of forgotten... so i start to learn basic thing... dont wanna see that on tab s... (but i think its going to be the same)
Click to expand...
Click to collapse
At least you had the 3G model and official JB (Asia only) . My Wi Fi model was thrown into the dung heap by Samsung after less than 12 months and no official JB or support theater.... Thanks to bodivas for the initial port to the P6810, I could then work from there with newer contributions.
They just ignore the GPL license to support devices for at min of 18 months. There are other OEM that refuse to provide full source too. What does Google do, nothing....
The only way is as you implied, to be proactive and help ourselves (and others) where skill/knowledge and time permit
Good modding !!
More than one way to skin a cat also....
I think they will have support for android L since the specs of the tab S match the requirements of the OS
it's easier for samsung to develop android L for exynos device . i hope my tab will have android L teeheehee
On which webpage provide SAMSUNG there (patched) opensource?
At least recovery image include binary which can't compiled from android source...
As of now, only the L720T tri-band http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy
As usual, the 720 is the "red headed stepchild"....no lollipop yet...
NOOOO!!!! Why can't they just release both... I've been waiting for this
Sent from my GT-I9505G using Tapatalk
lol. the 720 will be lucky to get the update a month from now unless Sprint mysteriously forgets it all together... wouldn't surprise me
The RDF for the 720 is also at OD1 so sprint has is near completion. I just don't know why they won't push both at the same time
Sent from my GT-I9505G using Tapatalk
Did anyone receive the update yet or is anyone able to pull it to possibly share and test?
Well, strangely enough, Sprint has now pulled the update and it has been removed from the update list page. WOW Sprint! Pretty pathetic....
troyboytn said:
Well, strangely enough, Sprint has now pulled the update and it has been removed from the update list page. WOW Sprint! Pretty pathetic....
Click to expand...
Click to collapse
This is really getting ridiculous now.
Sent from my GT-I9505G using Tapatalk
So perhaps something came up on one or more of the test devices not previously seen, it happens.
If that is the case, I personally prefer the that they pull it to fix the issue before it makes it out too thousands of users phones. And suspending rollout makes more business sense than causing customers problems, perhaps even severe problems. :good:
link for Samsung lollipop open source release.
this is the link.
click on the SPH-L720T_NA_LL_Opensource.zip.
h t t p://opensource.samsung.c o m/reception/receptionSub.do?method=search&searchValue=SPH-L720[/
RP-88 said:
So perhaps something came up on one or more of the test devices not previously seen, it happens.
If that is the case, I personally prefer the that they pull it to fix the issue before it makes it out too thousands of users phones. And suspending rollout makes more business sense than causing customers problems, perhaps even severe problems. :good:
Click to expand...
Click to collapse
OD2
720: http://device.sprintpcs.com/Samsung/SPH-L720-SPRINT/OD2.rdf
720T: http://device.sprintpcs.com/Samsung/SPH-L720T-SPRINT/OD2.rdf
troyboytn said:
lol. the 720 will be lucky to get the update a month from now unless Sprint mysteriously forgets it all together... wouldn't surprise me
Click to expand...
Click to collapse
i'm thinking more and more that this will be the case.
even more insulting would be for them to release 5.0.0 and then stop there.
Spades2006 said:
i'm thinking more and more that this will be the case.
even more insulting would be for them to release 5.0.0 and then stop there.
Click to expand...
Click to collapse
I hope not... They should release both updates at the same time.. It's most likely going to be 5.0.1 and possibly the last update. I find myself checking the sprint support page almost 3 times a day for the past month.
imaxuout said:
this is the link.
click on the SPH-L720T_NA_LL_Opensource.zip.
h t t p://opensource.samsung.c o m/reception/receptionSub.do?method=search&searchValue=SPH-L720[/
Click to expand...
Click to collapse
Can this Zip file be installed like a ROM or with ODIN?
ActorMike said:
Can this Zip file be installed like a ROM or with ODIN?
Click to expand...
Click to collapse
Neither, it's source code. You can't install it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Neither, it's source code. You can't install it.
Click to expand...
Click to collapse
I have a stock rooted Sprint ROM whats the best way to get the official Lollipop on it?
ActorMike said:
I have a stock rooted Sprint ROM whats the best way to get the official Lollipop on it?
Click to expand...
Click to collapse
Wait until it's released
Is there any change on the root impossibility without flashing rooted rom? I've been away from the game forever. Sorry
We won't know until it is released. This update hasn't been released yet. Most likely the typical root method work (cf atuo root and towel root) supersu is already up to date for lollipop OS so if you are rooted just wait till someone makes the stock rom a flashable zip or if you are stock just use any method to root. Remember to back up internal storage as unlocking the bootloader wipes everything.
robogoflow said:
We won't know until it is released. This update hasn't been released yet. Most likely the typical root method work (cf atuo root and towel root) supersu is already up to date for lollipop OS so if you are rooted just wait till someone makes the stock rom a flashable zip or if you are stock just use any method to root. Remember to back up internal storage as unlocking the bootloader wipes everything.
Click to expand...
Click to collapse
Considering every other Samsung phone on Lollipop, including the S6, has been rooted the same way as KitKat (CF Auto Root or flash SuperSU.zip in recovery), I think we'll be fine. "Unlocking the bootloader wipes everything"? There are so many things wrong with that statement. Odining a stock tar is the only thing that wipes internal storage (and not all of them do). There is no unlocking of the bootloader on Samsung phones. You flash a custom recovery or if using CF Auto Root it flashes the su binary to system/bin... no wiping on either.
bilgerryan said:
Considering every other Samsung phone on Lollipop, including the S6, has been rooted the same way as KitKat (CF Auto Root or flash SuperSU.zip in recovery), I think we'll be fine. "Unlocking the bootloader wipes everything"? There are so many things wrong with that statement. Odining a stock tar is the only thing that wipes internal storage (and not all of them do). There is no unlocking of the bootloader on Samsung phones. You flash a custom recovery or if using CF Auto Root it flashes the su binary to system/bin... no wiping on either.
Click to expand...
Click to collapse
Lol sorry. Haven't Odin back to stock in a while. All i remember was i did something in the "hook my phone up to pc " step then days of grief that i lost everything on my internal storage ...
SUPER EARLY RELEASE -
System image ONLY must be flashed thru fastboot - please dont do anything with this if you are not comfortable working in fastboot and restoring factory images.
Here it is
OmniRom for PixelC
Instructions:
Extract zip it is not flashable!
flash system.img with fastboot - ie fastboot flash system system.img
boot twrp
wipe data/cache
flash opengapps - the arm64 android 6.0 version I used stock
restart the device
there will be error dialogs due to bad permissions for the new gapps - its not my fault
tap ok often on those prompts and enter settings between them,
now navigate to apps and tap the three dots at the top left and show system apps
tap setup wizzard and give it all its permissions
give other google services apps permissions as well
enjoy your tablet
Known bugs
Permissions bug with gapps on fresh install
Settings app crashes when you tap the "more" button under interface
Settings performance options can not be set because ramdisk needs to be modified to support the feature
Some screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wallpaper not included grab it here https://www.eso.org/public/usa/images/eso0934a/
Wow ! Congratulations ??
So we are getting a custom ROM finally Thank you very much!
It's a shame: The Pixel C ist the best Android Tablet on the market but it gets almost no community support, because it costs a few bucks more than the usual cheap china crap
i think the bootloader situation is more detrimental to us than the lack of pixel c owners. even chainfire won't mess with it and he owns a pixel.
nice to see a custom rom finally, but it puts the navigation buttons in the middle. that's a step backwards in my opinion.
BaristaBot said:
i think the bootloader situation is more detrimental to us than the lack of pixel c owners. even chainfire won't mess with it and he owns a pixel.
nice to see a custom rom finally, but it puts the navigation buttons in the middle. that's a step backwards in my opinion.
Click to expand...
Click to collapse
Nav bar tablet mode is a changable feature in settings
I was at work for 13 hours today so no time for anything else, I can upload a system.img tomorrow if anyone is interested it just needs flashed thru fastboot then you gotta manually wipe data and flash gapps and manually set permissions for gapps I'll see how much time I can set aside later this week for a better method. I pulled the source for depth charge and I'll dig in and see if I can figure out how to use it it's kind of annoying that there's no documentation included how hard is it to write a readme sheesh
randomblame said:
Nav bar tablet mode is a changable feature in settings
Click to expand...
Click to collapse
Yeah, scanno originally ported that to Omnirom for the N10 from the Pixel C code base [emoji106]
Sent from my Moto X
does this ROM contain cifs or nfs ?
hagbardceline23 said:
does this ROM contain cifs or nfs ?
Click to expand...
Click to collapse
This isnt a full rom yet so much as a system.img it still uses the stock kernel so you get whatever that supports for now.
I'm uploading JUST the system.img right now I'll link it shortly.
*and it's up check first post.
Awesome!!!
I'm patiently waiting for updates because I'd love to use this without the listed bugs This tablet really needs a bad ass ROM to unlock it's full potential. Not rushing you obviously, good work takes time!
Sent from my Pixel C using Tapatalk
Sorry been swamped I picked up a 2000 beetle for $600 and am ripping the cylinder head off it now, and I've been working my usual 50-60 hours a week too. Ive been running this daily it works great installation is a bit messy tho I'll get to it as soon as I can
My C just arrived today. I'm very happy to see an Omini ROM available. I run Omni as my DD on my Nexus 6. Can't wait to try this.
I am very excited to see where this ROM goes.
Much excite! Impatiently waiting with patience.
BaristaBot said:
i think the bootloader situation is more detrimental to us than the lack of pixel c owners. even chainfire won't mess with it and he owns a pixel.
nice to see a custom rom finally, but it puts the navigation buttons in the middle. that's a step backwards in my opinion.
Click to expand...
Click to collapse
What exactly is causing the issue with the bootloader?
acdcking12 said:
What exactly is causing the issue with the bootloader?
Click to expand...
Click to collapse
Pixel C was developed as a Chrome OS device, so it has a Chrome OS bootloader. Don't know the implications of that, but apparently it complicates things.
Why should I flash this?
Is there any feature list I missed? Wifi/Touchscreen fixed?
Termynat0r said:
Why should I flash this?
Is there any feature list I missed? Wifi/Touchscreen fixed?
Click to expand...
Click to collapse
Idk what to tell you man. Haven't tried it myself, but usually, the reply is to just flash and see
Here are stock kernels that I have modified to not force encryption. Any time you flash back to stock then boot up, your data becomes encrypted forcing you to wipe in TWRP in order to read your internal storage. Flash an insecure boot.img right after you flash a stock rom and you'll stay unencrypted
Miui 8 8.1.1.0 China Hydrogen
https://drive.google.com/file/d/0B5I_q70mNuR4V2Vod1d2U0M2anc/view?usp=sharing
Miui 8 8.1.1.0 China Helium
https://drive.google.com/file/d/0B5I_q70mNuR4dzJoYkRlclVaVmM/view?usp=sharing
Nice, any chance we can get a hydrogen version?
bryan065 said:
Nice, any chance we can get a hydrogen version?
Click to expand...
Click to collapse
I'm pretty sure both kernels are exactly the same as they are the exact same size but I did a Hydrogen kernel as well. It's in the OP.
Awesome! That forced encryption was getting annoying. Would this cause any problems with the newer beta releases/final release? Would it require an updated kernel?
bryan065 said:
Awesome! That forced encryption was getting annoying. Would this cause any problems with the newer beta releases/final release? Would it require an updated kernel?
Click to expand...
Click to collapse
As the newer betas are released I'll update the kernel but from what I see they all look to be the same.
ajsmsg78 said:
As the newer betas are released I'll update the kernel but from what I see they all look to be the same.
Click to expand...
Click to collapse
Hi,
Thanks so much for sharing this no force encryption boot img, I hope you can continue doing this with the future weekly betas.
Best regards!
William
Hello.
Last days I tried to install TWRP on my Mi Max. After that I booted (as described in tutorial) into recovery in order to install SuperSu and get Root rights. No folder was shown and sd card and everything was shown as empty. I even couldn't boot into system (stuck at Mi Logo)
Now my question: would flashing this Kernel would change these problems I had? And how can I install it without being able to install TWRP?
Any help would be very appreciated as I'm new to Miui/Xiaomi.
Best regards
Michael
Sent from my MI MAX using XDA-Developers mobile app
Louis235 said:
Hello.
Last days I tried to install TWRP on my Mi Max. After that I booted (as described in tutorial) into recovery in order to install SuperSu and get Root rights. No folder was shown and sd card and everything was shown as empty. I even couldn't boot into system (stuck at Mi Logo)
Now my question: would flashing this Kernel would change these problems I had? And how can I install it without being able to install TWRP?
Any help would be very appreciated as I'm new to Miui/Xiaomi.
Best regards
Michael
Sent from my MI MAX using XDA-Developers mobile app
Click to expand...
Click to collapse
Since you're currently encrypted you're gonna end up having to wipe your data in twrp (Wipe--->Format Data--->type in yes) then reboot recovery and you'll be decrypted. I would back up your internal storage if you have anything important on it before you do this. As long as you flash a decrypted boot.img when you flash back to stock you won't get encrypted again.
Thank you very much ?. Oh once again full wipe......what a pity?
Sent from my MI MAX using XDA-Developers mobile app
ajsmsg78 said:
As the newer betas are released I'll update the kernel but from what I see they all look to be the same.
Click to expand...
Click to collapse
Hi,
Any chance we can get the newest 6.8.25 no forced encryption kernel for hydrogen? I tried using your 6.8.18 kernel (which booted fine) but cannot connect to wi-fi.
Thanks and best regards!
William
cmk7128 said:
Hi,
Any chance we can get the newest 6.8.25 no forced encryption kernel for hydrogen? I tried using your 6.8.18 kernel (which booted fine) but cannot connect to wi-fi.
Thanks and best regards!
William
Click to expand...
Click to collapse
Yeah I'll do that tonight if I can. It's a long weekend as it's my friends bachelor party and.......well....you know lol
ajsmsg78 said:
Yeah I'll do that tonight if I can. It's a long weekend as it's my friends bachelor party and.......well....you know lol
Click to expand...
Click to collapse
Thanks. Have a great weekend :good:.
ajsmsg78 said:
Yeah I'll do that tonight if I can. It's a long weekend as it's my friends bachelor party and.......well....you know lol
Click to expand...
Click to collapse
Hi,
Would appreciate it if you can work your magic for no force encryption boot for the latest beta 6.9.1 Global Developer (Hydrogen).
Thanks!
Request CIFS.ko for mi max.
I hope since you're working at kernel level, you can maybe please compile a CIFS. Ko implementation for us plebians?
auldthief said:
I hope since you're working at kernel level, you can maybe please compile a CIFS. Ko implementation for us plebians?
Click to expand...
Click to collapse
He is not working on kernel level... We don't have kernel source... All we can do for now is manipulate root fs.
Stable Build released for hydrogen can u update please ?
Sent from my MI MAX using XDA-Developers mobile app
Hi,can you add KCAL support please?
Thank you in advance...
http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
link dead?
link not working
divyesh43 said:
link not working
Click to expand...
Click to collapse
Links updated with the latest versions.
Dear @ajsmsg78! This can be used only for stable 8.1.1.0?
I do not know what is this, but I sent you (and I hope really for you) an adfree gift.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}