New ROMs out every day, you gotta love the "original" ones, that come usually besides the only useful rooting with A2SD+ (buggy), deodexed (space wasting) and "bash".
So, why the heck does anyone need bash? The normal user definitely does not. The advanced user (read, the one that can use adb) may occasionally feel lazy to type a command twice and uses command completion/repetition. But hey, don't we already have ash in busybox? What the heck do we need bash for? It eats some 2 MB of precious memory, without adding any real value?!
So please educate me, why does anyone adds bash into their ROMs (besides the other crap)?
Custom scripts may rely on features that bash offers that the default shell doesn't. That makes it vital for those. And Linux memory handling isn't as simple as adding up executable sizes.
teppic74 said:
Custom scripts may rely on features that bash offers that the default shell doesn't. That makes it vital for those. And Linux memory handling isn't as simple as adding up executable sizes.
Click to expand...
Click to collapse
I have yet to see a script that would rely upon bash and not running with a standard sh. And if so, someone should fix the script. So no, that's not an acceptable explanation .
I don't want to go into a holy war here, it just looks pretty silly to me that everybody who manages to start a kitchen has to press every button that is there. Without understanding what it does.
My point is, if you want to make an in any way called "official" ROM, I could go with rooting and perhaps busybox, but that's it. Anything else is unnecessary garbage. And too many cooks spoil he broth as we see here, once again.
When I wrote my downgrade tool I had to use bash explicitly to get it to work transparently on a Mac, since the default shell (sh) on OS X behaves differently. To say there's never a problem with compatibility between shells is untrue.
teppic74 said:
When I wrote my downgrade tool I had to use bash explicitly to get it to work transparently on a Mac, since the default shell (sh) on OS X behaves differently. To say there's never a problem with compatibility between shells is untrue.
Click to expand...
Click to collapse
AFAIK sh is Unix standard since the 70's or so . Same as vi.
mmaacc said:
It eats some 2 MB of precious memory
Click to expand...
Click to collapse
where did this number come from?
mmaacc said:
AFAIK sh is Unix standard since the 70's or so . Same as vi.
Click to expand...
Click to collapse
/bin/sh is not the original shell on any system, nor is vi. /bin/sh on one machine may behave differently on another. It may behave the same as bash, or it may not.
snq- said:
where did this number come from?
Click to expand...
Click to collapse
Filesize of bash
teppic74 said:
/bin/sh is not the original shell on any system, nor is vi. /bin/sh on one machine may behave differently on another. It may behave the same as bash, or it may not.
Click to expand...
Click to collapse
The reason is sh != sh. Which may be bash or zsh or csh. Depending on the OS. Still the original sh should be there if needed by a script. Again, same as vi != vim . We all understand that.
The reason for my posting was that I get really annoyed from the "original" ROMs that are already compromised by lots of "press button" kitchen changes. It just causes a lot of additional and unnecessary work to reverse such changes if you want to use a particular new version, that someone puts out as "original" messed up version as it happened a number of times recently.
mmaacc said:
Filesize of bash
Click to expand...
Click to collapse
oh please
speaking of file sizes though, linking bash against bionic is A Good Idea (tm):
Code:
$ stat -c %s `which bash`
397620
snq- said:
oh please
speaking of file sizes though, linking bash against bionic is A Good Idea (tm):
Code:
$ stat -c %s `which bash`
397620
Click to expand...
Click to collapse
Perhaps that is a dynamically linked version. If you look at the random cooked ROMs bash comes with 2.5MB+ of size (as in dsixda kitchen). And I consider this waste of precious resources.
Without trying to sound too harsh.. choose a different Rom or cook your own.
Each cook personalises there Rom to their needs although I kinda see where your coming from its unfair to criticise the very people who spend their own time customising time for our consumption.
Sent from my HTC Desire using XDA App
rosebud said:
Without trying to sound too harsh.. choose a different Rom or cook your own.
Each cook personalises there Rom to their needs although I kinda see where your coming from its unfair to criticise the very people who spend their own time customising time for our consumption.
Click to expand...
Click to collapse
You need to read the posting again. I'm not talking about people making customized ROMs. I'm just getting sick of all the wannabie "official" ones who don't know what buttons they press. And yes, I made my own .
i see your point, and i agree with you, but 2mb is next to nothing, i don't see what the big deal is.
why's your issue with bash? why not hate all the people who add wireless tethering or vpn support just because you don't use it.
cgrec92 said:
i see your point, and i agree with you, but 2mb is next to nothing, i don't see what the big deal is.
why's your issue with bash? why not hate all the people who add wireless tethering or vpn support just because you don't use it.
Click to expand...
Click to collapse
I do
Blabla...thing is, post an official ROM, keep it official. I can and do accept rooting, and busybox, for a so called "official" ROM, everything else, down the drain.
even rooting a rom or installing busybox makes it NOT official.
adding an APK or updating an existing APK makes it NOT official.
i dont know why you have such a big mouth and YOU are *defending* official ROMs throughout XDA, now you must be VERY bored to have started all this but seriously go find something constructive to do.
Why don't you just make an anti-social networking rant and start a thread protesting the file size of Facebook.apk
cgrec92 said:
even rooting a rom or installing busybox makes it NOT official.
adding an APK or updating an existing APK makes it NOT official.
i dont know why you have such a big mouth and YOU are *defending* official ROMs throughout XDA, now you must be VERY bored to have started all this but seriously go find something constructive to do.
Click to expand...
Click to collapse
I don't know what your problem is, I stated mine clearly.
Rooting a ROM is necessary to flash it and get it working properly. Busybox adds necessary features. That is as far as I could go under the tag "official" and to keep that ROM usable as a basis for other devs.
I can not accept other "press button but don't know what this is" kitchen stuff that most recent so called "official" ROMs had. Like bash or A2SD+.
And if you did not get the message by now, I made MacLite which is one of the most efficient ROMs available.
Thanks for your interest
mmaacc said:
I don't know what your problem is, I stated mine clearly.
Rooting a ROM is necessary to flash it and get it working properly. Busybox adds necessary features. That is as far as I could go under the tag "official" and to keep that ROM usable as a basis for other devs.
I can not accept other "press button but don't know what this is" kitchen stuff that most recent so called "official" ROMs had. Like bash or A2SD+.
And if you did not get the message by now, I made MacLite which is one of the most efficient ROMs available.
Thanks for your interest
Click to expand...
Click to collapse
Ooh well i'm sure everyone here is sorry they can't match up to your 'OFFICIAL ROM' standards...
Busybox is as far as you'll go..... wow..
So the message was that you made MacLite? not about Bash but you just wanted to tell the world you made a ROM, and by made you copied an 'OFFICIAL ROM', removed a few things and posted it as your own? Thank you for MAKING a great ROM!
Thread moved to Q&A.
cgrec92 said:
So the message was that you made MacLite?
Click to expand...
Click to collapse
Read the posting again. Timewaster.
Related
I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.
I'll direct to you the Q&A forum.
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?
ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App
Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.
Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk
Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App
Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?
I have, for the most part, returned from my leave of absence and hopefully this time around I will be able to provide you folks with something a bit more useful.
Admittedly, this was a fairly halfhearted attempt but, hey, it's something to start with. I branched the CM7 for Nook Color source. Part of the compilation process involves running a script (system/device/bn/encore/extract-files.sh) that extracts proprietary libraries (or something?) from stock Nook Color, so I plugged in a rooted N2E instead for this step and ripped the files off of it. Some files were missing from the N2E, so I copied those over from a Nook Color. Here's a list of those files:
Code:
/system/lib/libOMX.TI.720P.Decoder.so
/system/lib/libomap_mm_library_jni.so
/system/etc/powervr.ini
/system/lib/libpvrPVR2D_FLIPWSEGL.so
/system/lib/libusc.so
/system/lib/libpvrPVR2D_FRONTWSEGL.so
/system/lib/libOpenVG.so
/system/lib/libOpenVGU.so
/system/lib/liba2dp.so
/system/lib/hw/alsa.omap3.so
/system/usr/share/alsa/init/hda
/system/usr/share/alsa/init/00main
/system/usr/share/alsa/init/help
/system/usr/share/alsa/init/default
/system/usr/share/alsa/init/info
/system/usr/share/alsa/init/test
Compilation of the franken-nook-color source went without problems.
Unfortunately although unsurprisingly, the produced userland doesn't boot. I'll keep y'all updated with my progress; this is only the very tip of the iceberk.
I have two NST so I can use one for testing your rom if you promise no to brick it very often ;-)
I have a NST that, while the 3/4's of the screen is broken, it still functions fine and I can see anything in the top right quadrant of the screen. It doesn't do anything else for me, so you're welcome to brick it in the name of experimentation.
Thanks for the offering! I am not really in need of anything just yet but should anything come up I will PM y'all.
Anyhow, I tried again but this time excluded all the missing prop files from the build by editing them out of device-vendor-blobs.mk. It still didn't work so that means we're probably going to have to find a way to actually debug it instead of using trial and error like we have been.
Maybe there is like, a serial port or something on this thing.
klausef said:
Maybe there is like, a serial port or something on this thing.
Click to expand...
Click to collapse
Yes there is a UART on the OMAP3621.
Still, it's hard to get any info out of TI since it's an OEM part.
Does anybody have a real pinout?
Actually, unless somebody has a dead Nook that you can pull the processor off it would be hard to trace.
I guess the best bet would be to look for suspicious unused pc lands.
Can you toggle the charge light gpio as a progress indicator?
You don't need anything special.
As long as you can boot a kernel, which you can, you can do all your debugging over adb. Just enable adbd in the ramdisk.
The use for a serial console is for debugging KERNEL failures.
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
GabrialDestruir said:
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
Click to expand...
Click to collapse
Thanks for the direction, I kind of have been seeing that getting this working isn't as trivial as swapping a few files. I've been asking on some Freenode channels about what exactly makes a kernel 'CyanogenMod compatible.' There are clearly people out there who know exactly what facilities and stuff need to be backported, but such people are hard to find. Do you have any idea where this kind of stuff is documented? The CyanogenMod wiki seems a bit sparse, although maybe I haven't been looking in the right places...
If it is of any interest to anyone:
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html
I've recompiled U-Boot to call our current N2E kernel with a new `console=[...]` parameter, and recompiled the kernel with USB serial support. I figure I should be able to plug this thing into a linux box and just use `minicom` to look at the kernel's output in this manner. I know this probably won't give too much information about userspace issues but at least hopefully it will give some info on why/if/when/where init fails.
It would be nice if a spare UART could be found directly on the board.
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html said:
The USB subsystem is started rather late in the boot process, console messages printed during boot before the USB subsystem is loaded will be lost.
Click to expand...
Click to collapse
I should be more specific, it's not so much you need to make the current kernel CM7 compatible, as it is you need to make it Android Froyo Compatible, which usually involves porting features from the eclair, if you want to get specifics, try talking with people in #nookcolor or #nook-tablet on Freenode. They may be able to help point you in the right directions for porting the kernel.
Waiting for my NST to come from new continent.
Personally, I would start building original kernel source from b&n. When it works and device boots, then I would clone google repository for kernel 2.6.x and would compare its files with the files from original kernel. And then adding needed source files for booting, and needed device drivers.
I doubt I'll have free time and enough knowledge for that.
Sent from my GT-I9000 using XDA
seeing as we now have the uart http://forum.xda-developers.com/showthread.php?t=1702734 i feel its time to make a cm7 port. it would unlimit the device, and bring it into more compatible apps.
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
imachine said:
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
Click to expand...
Click to collapse
Sorry if you weren't asking me.
I don't write a single line of C code since almost twelve years. I'm a programmer in a very different environment, fact which makes me know that such a port needs a lot of dedication.
In the next weeks I'm gonna be father for the first time and this makes me set completely different goals in my life.
As far as I've understood of cyanogenmod, is that this world is made of brilliant volunteers, some accepting donations, some not. Maybe in the whole cm community, there is somebody with time and experience.
Sent from my GT-I9000 using XDA
I've been considering picking this up as a project, because I'm tired of 2.1, i would like some GB at least I doubt we will see cm9, but cm7 seems doable. I'll have to learn some to do it, but I don't see why it's not outside of reach; now that we have a serial port, and such.
tdcfpp said:
Sorry if you weren't asking me.
Click to expand...
Click to collapse
No problemas, I wasn't. I directed my message at klausef who started this thread, though anyone willing to help out would probably be beneficient from fundraising, were it to start funding a project, instead of a single developer.
If money's a problem, perhaphs starting a kickstarter (or similar) project might help out?
Donating via paypal works as well, but I don't think it's possible to allow public access to account levels in order to motivate the experience of funding, by letting people see how much the project has risen.
i can't wait to get CyanogenMod on my nook! Have you guys discovered anything new?
Cheers!
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
imachine said:
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
Click to expand...
Click to collapse
Bump. I've got a great use for a NST / N2E application, and the app is currently compiled for Android 2.2 only. I may not be able to get to the source (and may not be able to make it work in 2.1 even if I did!), so a NST with 2.2 would be ideal!
I'm curious to what the binaries mean for upcoming roms. My assuption was that the roms were from the source meaning they had everything. So what are they and what for and why would they matter now? No this is not a "i'm a noob question" I just don't know...:angel:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
They have provided th 4.2.2 binaries for building a 4.2.2 rom from aosp, that's all.
Currently, developers have been building 4.2.2 hybrid roms.
digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus
bk201doesntexist said:
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus
Click to expand...
Click to collapse
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.
digitallure said:
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.
Click to expand...
Click to collapse
Well, they do allow custom ROMs to be made, but new binaries don't necessarily mean new ROMs will be stabler. If you don't build from source, don't worry about it.
Sent from my Nexus
b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.
Electrodeath0 said:
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.
Click to expand...
Click to collapse
Thanks for the answer
Does anyone have a zip file to flash the new binaries for Maguro?
ReggieS2 said:
Does anyone have a zip file to flash the new binaries for Maguro?
Click to expand...
Click to collapse
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I read this over at Paranoid Android's G+ page so it lead me to think that I needed something
Recently the AOSP has been fully completely, all the needed drivers are supplied. We have updated AOSPA immediately of course and a couple of hours later we've had it merged.
Now i want everyone to listen up. YOU ABSOLUTELY NEED TO BE UP TO DATE. Or else your device will be incompatible, unable to make calls perhaps or who knows what. Google supplied a new bootloader, and for phones, new radios. You can get them straight from Google and install via fastboot. Or, the easier way perhaps, you go to XDA and get them as flashable ZIP files.
Either way, this concerns all 4.2.2 roms out there that include Googles new 4.2.2 hardware drivers.
SuperSU on TW ROMs running 4.3 (regardless of version, source of version and how you got it) is frustrating. Apps that need root do sometimes able to get root access, and most often than not wont' be able to.
YES !!! I have done more of my share of reading. And please do NOT treat users with less than 10 posts like idiots.
*** The only solution is to change between Default Access modes. Going from grant, to prompt. Doing so for some strange reasons wakes up SuperSU***
The following solutions DO NOT WORK (meaning the problem resists)
1. Flash Antenna (regardless of which, even with the one provided by OP on their threads)
2. Flash insecure kernel zip
3. Download the version form Play and Update
Hope this help any of you that are experiencing some crazy frustrations like me.
*** Not to offend anyone, but the rule of 10 post or less = No reply/post on dev. forum is beyond me ***
*** I have tried to report my experience with certain ROMs, but Nooooooooooo.... <10 amigo ***
--- One more, since I think I am going be booted because of offending Seniors Party Members. ---
Can anyone tell me the logic of formatting a partition 3 times ??? I found this ridiculously offending being an engineer myself.
I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible.
@mrbackdoor
Whoa Cool down Bro. Take a deep breath. Now tell me what precise are your problems ? I got the part with SuperSU making you go Ape. But what's with Roms and 10 Wipes ? I have no Idea what you are getting at.
So about SuperSU. If that app is making you go nuts, why don't you try SuperUser by @ChainsDD ? There's also a great Superuser app from CM team. But without knowing your Rom, I won't recommend it.
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
P.S. - Your Current Post Count is 1. I did respond right ?
LOL... thanks man. I am positively NOT HOT
what's with Roms
>>> TW 4.3 ATT leak on Tmobile LTElessS3
>>> I was just venting the fact that a member CAN NOT post on Development Forums because he/she has less than 10 posts.
>>> That's like filling 10 forms before you are able to download a file. Similar to registration process that just drive you nut.
>>> One engineering note is wiping a partition 3 times. The wipe process before installing a new ROM.
>>> I just don't get it... Why 3 ??? "insanity according to Albert Einstein"
Superuser..But without knowing your Rom, I won't recommend it.
>>>Superuser - NOT an option, not even working
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
>>> YES sir. Fully understood
P.S. - Your Current Post Count is 1. I did respond right ?
>>> call me up when you want a beer... or couple shots of the good sh****
@mrbackdoor
I don't have the ATT S3 Let alone the leaked Rom so can't comment. I hate TouchWiz anyway. I don't want to comment on the rules. They are there for a reason. Yes they may be an irritant but they keep Noobs away. You my dear friend is a Newb. There's a difference.
Whoever asked you to wipe the same partition 3 times needs to get their head examined. But then I am jumping ahead without knowing full circumstances. So if you don't mind, show me the thread link.
Are you trying to get the Leaked ATT Rom with a working Root ?
Now you too sir, have been guilty as well. I need to have full problem statement, which I am sorry I have not got as yet. So can you kindly explain what precisely are you trying to do and where does SuperSU come into play ?
Ok, first, please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
Yes, we want you to do as much on your own as you can. No, most of us do not consider a low post count an indicator of idiocy. We might, however, judge how much we want to help depending on the quality of your post, or any other OP by anyone. If you do your best to find your own answers, and post clearly and respectfully, it'll show.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
So if you'd care to try starting over on a better note, here are my points regarding your issues.
There is no real benefit to formatting something more than once. This is something that apparently began with some old device where the recovery wouldn't always format correctly. So people got in the habit of wiping several times rather than the king after each time. They then spread out across xda and push this practice like gospel sometimes, even though it gives no benefit and imo shortens the life of the device. I have tried to point out to folks this is not necessary, but gave up long ago! To each his own.
Enewman found a bit of a workaround for the su issues. It's not perfect but does seem to help a little.
Find these files
/etc/install-recovery.sh
/etc/init.d/dameonsu (or similar named script)
Find this line
/system/xbin/daemonsu --auto-daemon &
Delete --auto
Reboot
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
But also keep in mind that it's a combo of things, you do also need the insecure kernel. And Knox is still gonna screw with it if it's not been removed.
Also, try to remember, all of this stuff is brand new to all of us. Do not expect miracles, it takes time to relearn everything for everyone. But if it's really that bad, then consider going back to an older Rom for now.
These are after all leaked builds and should not be expected to be fully functional and bug free.
Sent from my SGH-T999 using Tapatalk
Dr. and Perseus
To you both, thank you, thank you and thank you. It would have been more appropriate on the General thread. Anyhow:
Perseus
If needed, I can point you to the threads. You are kind. I do appreciate that.
Dr.
I think you know exactly what I was talking about. So to you I do apology if my post is offended. In fact, to anyone who do feel the same. My bad.
please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
>>>No Sir, no way in any shapes or forms I do assume people are jerks. Like I stated before, I was just venting on the fact that the rule cripples members ability to contribute and alienates them as well.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
>>> Understood. Complain is absolutely not my thing. If there is a way to monitor users' footprints, you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
So if you'd care to try starting over on a better note, here are my points regarding your issues.
>>> Of course.
There is no real benefit to formatting something more than once.
>>> Got it. Now's that is at the core. That's exactly what I was looking for. Instead banging my head trying to understand how partitions are being formatted and the file system that is basically associated to the NIX for a long time . Basically what I posted is the workaround that I use for now.
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
>>> Correct.
But also keep in mind that it's a combo of things, you do also need the insecure kernel.
>>> Appreciate your time Dr.
Statement below is my initial love your developers. That has not changed. Just "kang" members that I do find .... well.... you got my drift.
"I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible."
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Again, thanks.
mrbackdoor said:
you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Click to expand...
Click to collapse
Actually your join date of May '11 is the first thing I noticed. Pretty big time Reading on your part if you didn't ask before.
I am afraid we are still missing the problem you posted for aren't we ? Or what steps Doc suggested about the leak solved your problem ?
I'm on the app most of the time, so I can't readily see post counts, join dates, junior/senior member status, etc. But anyway, thanks for the reply op. I lurked around the forums for about a year before my first post, reading and learning all I could, so I can appreciate that you seem to have done so as well!
I was slightly off earlier, when you find those files, change this:
/system/xbin/daemonsu --auto-daemon &
To this:
/system/xbin/daemonsu --daemon &
Had to go look it up again. Sorry bout that!
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Oh I see. Honestly on my 4.3.1 rom that I had, I never experienced this problem. Possible its related to the leaked Rom's implementation of SELINUX?
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers. The developers do they developing, and we do modifications to make things how we want them and hopefully others enjoy it too, that's all.
To OP, we're aware this SuperSU problem was annoying, we were one of the first few dealing with non-stop before bringing the leak from AT&T and debloating it over here.
enewman17 and his infinite knowledge did some poking around in the files and found a way to make root more persistent, albeit this is a leak, and we have Samsung KNOXing at our door. Things are bound to be broken, and especially because myself and others working on the leak are not professional Android developers nor do we ever claim to be, more like hobbyists who try to learn on their own by reading, or their own personal knowledge of NIX' and shell scripting.
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder.
All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
mrbackdoor said:
All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
Click to expand...
Click to collapse
Glad to know we could be of assistance. Glad to clear that up with you. Feel free to post more, don't be such a lurker!
Mod edit: TG link removed as per XDA's TG Chat Rules.
(TG link and home page was removed I can only see in their rules the TG link all good so adding back the home page to the home page)
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
I think that there is no value at all in this project. All anyone needs to do is run the original boot.img through magisk before they write it to the boot partition and the job is done.
In addition, if anyone was inclined to use 3rd party hosted pre-rooted (or not) boot images, I would VERY STRONGLY recommend that they DO NOT. This is simply because it opens them up to whatever other undisclosed changes happen to have been added to it.
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Gytole said:
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Click to expand...
Click to collapse
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Jacobh1245 said:
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Click to expand...
Click to collapse
Thanks for being a great sport
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
TrustAugustus said:
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
Click to expand...
Click to collapse
Yes I have had better success with safetynet since doing this they don't always work out like that but for the most part it's been better. As far as pre-rooted with pixel devices it's not too hard to do, just time consuming. I'm going to build a set of instructions tonight for my website as to how to do so yourself for those who would rather do it manually
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
TrustAugustus said:
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
Click to expand...
Click to collapse
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Jacobh1245 said:
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Click to expand...
Click to collapse
We understand, just with the new safeties built into to hardware anymore it can comicate things for some people. I am not saying prerooted is WRONG, it can just cause problems. It's not you. Lol
Yeah, some devices can, some won't. I am alware of these but also understand the risk is minimal and unlikely to be president. Reality with anything like this even down to the roms themselves have so many variables that could cause problems. Which I why I have taken the extra steps to test that I have a solidly rooted Rom
Jacobh1245 said:
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
Click to expand...
Click to collapse
For anyone who might want to know this. I have a very poor excuse for a guide on making pre rooted roms on my page now if you have a pixel device it does work. It was quickly put together and I WILL update it SOON and will add screenshots to help as well as fine tuning the wording.
What would be nice is to have the installation routinely root the boot.img if the system is pre-rooted, like Lineage 18 does on my 1+7pro.
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
96carboard said:
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
Click to expand...
Click to collapse
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Jacobh1245 said:
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Click to expand...
Click to collapse
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Lughnasadh said:
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Click to expand...
Click to collapse
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Jacobh1245 said:
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Click to expand...
Click to collapse
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Lughnasadh said:
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Click to expand...
Click to collapse
I which case testing would show that plus I'm usually pretty good at keeping up with that kind of thing. It is a valid concern but since the versions I release are going to have the correct version for them I will do the same for each rom indevidually as need to make sure they will work properly. Whenever a new version is released. That too means if you are on the same rom and dirty flash to the next one magisk will prompt you to update the app(has been tested too)