Hello to all the kernels Devs,
I just want to share with you all the initramfs I use in my kernels.This initram has scripts that run on boot to give root and installs the Superuser.apk and Busybox along with a script that will allow people to easily remount the /system filesystem read write if changes need to be made I think this is the best way to run root on the Epic that way there is no need for rom devs to have to setup a rom to be rooted.The scripts in it are run from init.rc and sets up the phone for root and installs Busybox with a full compliment of applets.It is in working order and will work with Rom Manager.If you have any questions about it let me know.
Link to my initramfs.
http://www.mediafire.com/?aynk2gd05xuv6c0
Another link in case mediafire doesn't feel like working.
http://www.sdx-downloads.com/devs/skeeterslint/Epic-4G-initramfs.tar.gz
Updated to latest stable busybox version 1.17.3
does root explorer and metamorph work with this?
Root explorer will work when he updates it on the merket is is bugged right now, metamorph I can't say I never used it, Titanium Backup will work without having to install busybox through the app all root programs will work without issues. It sets su in /system/bin and /system/xbin so as to not break any root apps. The root script is in /sbin it is run from init.rc during startup, the busybox install is also run from init.rc and gets setup in /bin.
Sent from my SPH-D700 using Tapatalk
Metamorph works fine for me.
[email protected] said:
Metamorph works fine for me.
Click to expand...
Click to collapse
I thought it only worked with Cyanogen - what ROM/kernel are you using?
If root explorer has a bug and needs an update, is the same true for connectbot?
ragnarokx said:
I thought it only worked with Cyanogen - what ROM/kernel are you using?
Click to expand...
Click to collapse
Works with twiz also(worked on my behold 2) but not all themes work.
skeeterslint said:
Hello to all the kernels Devs,
I just want to share with you all the initramfs I use in my kernels.This initram has scripts that run on boot to give root and installs the Superuser.apk and Busybox along with a script that will allow people to easily remount the /system filesystem read write if changes need to be made I think this is the best way to run root on the Epic that way there is no need for rom devs to have to setup a rom to be rooted.The scripts in it are run from init.rc and sets up the phone for root and installs Busybox with a full compliment of applets.It is in working order and will work with Rom Manager.If you have any questions about it let me know.
Link to my initramfs.
http://www.mediafire.com/?q4n2mgb4d2l6ucv
Click to expand...
Click to collapse
Wont flash in clockwork,is this for odin?
Ummm no this is for kernel devs to build kernels with. It is the ramdisk that is inside the kernel.
Sent from my SPH-D700 using Tapatalk
Bump,
Joeys root exploit was never ment to be permanant was just a hold out till the source code was released and we could root with the kernel.its worth trying it out at least once
skeeterslint said:
Bump,
Joeys root exploit was never ment to be permanant was just a hold out till the source code was released and we could root with the kernel.its worth trying it out at least once
Click to expand...
Click to collapse
Hey bro I tried integrating your ramdisk into my kernel, but theres a few issues.
For one, ADB can still run as root, and I can get into it thru a shell, but I lose all root access in usermode. SetCPU fails. My Search2Play app fails. Nothing can get root. I believe its because of the SU binary you're using.
Any ideas?
Geniusdog254 said:
Hey bro I tried integrating your ramdisk into my kernel, but theres a few issues.
For one, ADB can still run as root, and I can get into it thru a shell, but I lose all root access in usermode. SetCPU fails. My Search2Play app fails. Nothing can get root. I believe its because of the SU binary you're using.
Any ideas?
Click to expand...
Click to collapse
Go into the default.prop and remove this ro.secure=0 thats a setting that koush had in it it gives a root shell in adb and that is probably what is breaking it.TThe su binary I am using is the the one that comes with Superuser.apk that you can download through Rom Manager.I don't seem to have any issues losing root on my phone.
skeeterslint said:
Go into the default.prop and remove this ro.secure=0 thats a setting that koush had in it it gives a root shell in adb and that is probably what is breaking it.TThe su binary I am using is the the one that comes with Superuser.apk that you can download through Rom Manager.
Click to expand...
Click to collapse
I didn't even know Koush had added that lol I'd had it in mine since day one. That would make since. But I'm not sure its the best idea. Then you can't adb remount or adb push to /system since it'll be in secure mode.
What path does your search2play use to find cp?Thats what fails on my phone I guess its not checking the whole path that is setup in init.rc which is export PATH /sbin:/bin:/system/sbin:/system/bin:/system/xbin.
Geniusdog254 said:
I didn't even know Koush had added that lol I'd had it in mine since day one. That would make since. But I'm not sure its the best idea. Then you can't adb remount or adb push to /system since it'll be in secure mode.
Click to expand...
Click to collapse
To be honest I thought i had changed that before I packed it up.Oh and whats up with setcpu it works fine for me other then being a bit unstable on any other setting except conservative which isn't the initram that cuases that its the phone its always been a bit unstable on the galaxy s from reading the other forums?
Initramfs is updated for DI18.
Updated again to fix issues with bluetooth.
skeeterslint said:
Updated again to fix issues with bluetooth.
Click to expand...
Click to collapse
How'd you fix Bluetooth? Was it just a change in the modules?
Geniusdog254 said:
How'd you fix Bluetooth? Was it just a change in the modules?
Click to expand...
Click to collapse
No was either sonething in init.rc or the init binary itself becuase the release i just replaced had the modules in it already.
skeeterslint said:
No was either sonething in init.rc or the init binary itself becuase the release i just replaced had the modules in it already.
Click to expand...
Click to collapse
I new to the whole kernel development, just starting out but how would I install this? Would I use menuconfig?
Right now I have me my kernel development environment all setup, and compiled my first working kernel for the epic. Thanks in advance.
Related
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
is busy box installed?
is SU working?
feefeeboomboom said:
is busy box installed?
is SU working?
Click to expand...
Click to collapse
I haven't done anything since flashing the 2.1 RUU. What steps do I need to do to get busybox and su working?
if you installed the RUU that was just 'leaked' (from what i understood our 2.1 builds are based off this ruu already). The build does not include busy box or anything for that matter that is required for wireless tether-
damageless said:
Here is a link to the latest RUU from Sprint.
You cannot simply extract it. This still has root since it is a test release. I recommend just doing an adb pull of your system directory after you flash it. Don't do this when the final one comes out or else you might be stuck without root.
You will need to add busybox, patch sh and su, and make sure that you do another recovery image and such. I also recommend adding Superuser.apk and stuff. If you use the Desire build.prop, you can get most of the protected apps working.
Enjoy.
http://dl.damagedroms.com/2.0/RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe
Leak, I know who you are.
Click to expand...
Click to collapse
http://benno.id.au/blog/2007/11/14/android-busybox
Busy Box link for you, I'm not really sure how to get it working but it's a start, alot of results come up if you google "busybox for android", so I hope that helps ya out bud
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
dwertz said:
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
Click to expand...
Click to collapse
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root
Click to expand...
Click to collapse
Who told you that the RUU was rooted already? It's not. Why would it be? Sprint has no interest in you being root.
As for why do you have to install busybox? Because the application requires it.
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
mobilehavoc said:
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
Click to expand...
Click to collapse
Here is the superuser.apk You have to have root.
Put superuser.apk in your C:\AndroidSDK\Tools\
adb remount
adb push superuser.apk /system/app/
mobilehavoc said:
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
Click to expand...
Click to collapse
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
Not sure what you mean but I was able to push a new build prop onto the phone using adb with no issues.
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
The leak actually is rooted. It's an engineering leak, so root can work his magic- but only from the adb shell.
why do you need superuser?
superuser requires root, if you had root, you wouldnt need it.
you can just dl the wifi tether for root from the market
program and it would work right?
10 chars and a poke
This is the latest Sprint Rom based on the latest RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
I have verified that A2SD is working as I downloaded and installed a couple of programs from the market. The programs are being stored in /system/sd/app.
Here's the link: http://www.darktremor.info/files/2.1/2.1-ruu-a2sd-signed.ziphttp://www.darktremor.info/files/2.1/sprintstock-21-a2sd-b-signed.zip
This one now has adb rooted (thanks to nfinitefx45 for his assistance) and does flash (heard complaints on the symlink issue...never sure what causes that, but ended up starting over and porting the files from the previous build).
This is for those people who want to keep with the stock installation but want the addition of A2SD. If you want a customized look, faster performance and A2SD support, I suggest a custom rom. Fresh 2.1.2 or FreshToast is a good one to use.
Note: It will not affect recovery.
Enjoy and I'll answer any questions you may have (if I can answer them).
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
tkirton said:
This is the latest Sprint RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
This is definitely an RUU as when I go into adb shell, I get the dollar sign as a prompt rather than the pound sign...I'm pretty certain it is not rooted.
.
Click to expand...
Click to collapse
<<<snip>>>
This makes no sense at all.
Good point about the Rom vs RUU. Edited to correct.
As for the init.rc. Mainly it was init.rc edit.
regaw_leinad said:
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
Click to expand...
Click to collapse
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
wctom said:
<<<snip>>>
This makes no sense at all.
Click to expand...
Click to collapse
tkirton said:
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
Click to expand...
Click to collapse
Thanks, I'll just use your boot image for RegawMOD 2.5. saves me a few minutes
working perfectly all apps installed and 132 megs still open internal
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
sandboxlove said:
is it a general consensus that if you want to run a2sd successfully you should use a class6? i currently have a class4
Click to expand...
Click to collapse
right now, I switched back to my class 4 and its working great
nvmchars....
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
sandboxlove said:
i just want to be clear...this is the latest sprint leak? you seriously deodexed the whole thing?
i thought vince was crazy for trying, your completely BANANNAS
Click to expand...
Click to collapse
yeah, i thought I'd post it in here. Didn't think since it's the same thing as he posted but deodexed that I should make another thread.
and yes, the latest sprint leak. you should test this. I can't right now.
Oooh...cool. Enhancements. I like enhancements.
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
tkirton said:
Oooh...cool. Enhancements. I like enhancements.
Click to expand...
Click to collapse
Well, I like your work, so that's for you
did anyone test it out to make sure it boots?
Sorry to be such a noob, but what is "deodexed" a ROM mean?
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
Well I flashed it and stuck on the HTC screen. Flashed the non deodexed version and loads fine.
So apparently i f***ed up deodexing lol. I guess that ROM that I did wont work..
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Now that the A2SD stuff is behind me, I'll take a look at that. Flipzmode or Toastcfh may be able to shed some light on how you get this image rooted correctly, especially Flipz since he's using the latest leak for Fresh 2.1.1.
The original goal was to get A2SD working on a stock rom, which I did....but it is rather annoying that it isn't rooted (or fully rooted).
Damage said in his point that it was rooted, but I got the same thing you did...no root when doing adb.
I'll talk to Flipz or Toast and see if they can point me in a direction to go.
nfinitefx45 said:
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Click to expand...
Click to collapse
well this is a piece from some of the reading I've been doing I beleice this needs to be done with in the boot image. I dont know if this will help in your research,
-------------------------
You also need to modify the ROM update script to change the default permissions for /system/bin/su so it can be used to elevate privileges to root. The script is in $WKD/dst/META-INF/com/google/android/update-script. Open it in your favorite editor and find the line starting with set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh and after it add the following set_perm 0 0 04755 SYSTEM:bin/su
=======================
Hi tkirton,
Nice job on this and thanks for all your hard work on everything! I am also wondering what dedoxed means? Is it like where application data is also stored on the SD card instead of on the phone itself?
Thanks!
but where the fugg is "su".
I pushed superuser.apk no prblem but were is this extensionless su app??
Reason:
I rooted my gf's hero and need to run titanium to backup all her apps before I flash Fresh 2.1.2 to it. After lots of searching I se I need to put SU on it. Can soeone shed some light...?
scirio said:
but where the fugg is "su".
I pushed superuser.apk no prblem but were is this extensionless su app??
Reason:
I rooted my gf's hero and need to run titanium to backup all her apps before I flash Fresh 2.1.2 to it. After lots of searching I se I need to put SU on it. Can soeone shed some light...?
Click to expand...
Click to collapse
hmm.. you could just use another backup program that doesnt need root. i personally use astro to back up my apps.
assuming that just pushing superuser.apk works, then you should get a prompt when you try to use titanium back up that asks for root access.
su should be in /system/bin and I believe /system/xbin. I had to cp su /system/xbin for Metamorph to work a while ago...
Code:
adb shell
cd /system/bin
ls
see if su is in this folder. if it is then
Code:
cp su /system/xbin
But wait till someone else confirms this...
Also, if you are getting the black super user request screen make sure that you have USB Debugging turned on. Settings>Applications>Development>USB Debugging Mode
"su" is not an app.. "su" is command for "super user"..
"su" is root access.. If the rom you are using is not rooted it will never have "su".. Because the rom will not allow sudo access
*search for appsaver to get the apps from an unrooted rom..
azyouthinkeyeiz said:
"su" is not an app..
"su" is root access.. If the rom you are using is not rooted it will never have "su"..
Click to expand...
Click to collapse
Have to kind of disagree with you here.
he is refering to the SU file that lives in //bin/
Which is technically "executable" when setting suid bits.
But you are correct in that the rom should have that. And if it doesn't...she's not rooted...and you'll need more than just SU eventually...you should go ahead and get busy box installed for TIbackup to use.
Kcarpenter said:
Have to kind of disagree with you here.
he is refering to the SU file that lives in //bin/
Which is technically "executable" when setting suid bits.
But you are correct in that the rom should have that. And if it doesn't...she's not rooted...and you'll need more than just SU eventually...you should go ahead and get busy box installed for TIbackup to use.
Click to expand...
Click to collapse
The su file that lives in //bin/ allows the rom to interact with busybox and supermissions.. It is not an APP just a directory file.. That's like saying on a PC that the DLL files for each program is a program.. It does "execute" but there is not a single file on your computer that isn't "executable" in someway.. I was just saying in layman's terms that he can't do what he wants..
You can't just install that on a Sprint Rom.. He cannot just push busybox into his rom because it is lacking the su file.. And it cannot interact with the Sprint Rom even if you did get it installed somehow...
Yes he rooted the phone, but the ROM is still locked in by sprint until you flash a custom rom.. You have to repackage the rom and reflash it to get those parts into the rom.. Which would not help this guy with what he wants..
*again.. Search for appsaver.. it is the easiest solution for you OP
azyouthinkeyeiz said:
The su file that lives in //bin/ allows the rom to interact with busybox and supermissions.. It is not an APP just a directory file.. That's like saying on a PC that the DLL files for each program is a program.. It does "execute" but there is not a single file on your computer that isn't "executable" in someway.. I was just saying in layman's terms that he can't do what he wants..
You can't just install that on a Sprint Rom.. He cannot just push busybox into his rom because it is lacking the su file.. And it cannot interact with the Sprint Rom even if you did get it installed somehow...
Yes he rooted the phone, but the ROM is still locked in by sprint until you flash a custom rom.. You have to repackage the rom and reflash it to get those parts into the rom.. Which would not help this guy with what he wants..
*again.. Search for appsaver.. it is the easiest solution for you OP
Click to expand...
Click to collapse
I knew it wasn't an "app" but I also figured you guys were smart enough not to hassle me about symantics
Ended up just flashing Fresh 2.1.2 and to hell with her apps.
scirio said:
to hell with her apps.
Click to expand...
Click to collapse
I tell ya what, every time I wipe my wifes phone and wipe out that "My Days" app. She wants to kill me. You'd think she has that schedule memorized...lord knows I do.
THERE IS A NEW FLASH PLAYER ON THE MARKET I WOULD RECOMMEND NOT UPDATING UNLESS YOU REALLY WANNA RISK LOSING HULU
-----------------------------------------------------------------------------------------------------------------------------------------------
These fixes are no the actual hulu app or even a change to the hulu app at all. It is a fix which roles back the version of stagefright which just so happens to be the fix for the demon voices.
This may negativity effect Youtube, Pandora, and xm radio.
I MADE AN UPDATE ZIP THAT
I HAVE CONFIRMED WORKING BY donnyevo4g and several others
I have tested it myself
So try it out I need feedback!!
Make a Backup first just flash and your done. (The zip is called Hulufix.zip)
This zip roles back stagefright and fixes demon voices.
****IF THIS WORKS DISREGARD ALL BELOW****
*****MAKE A NANDROID BACK UP BEFORE ANY OF THIS*****
Here are basic instructions for using adb. Thank you rutter9 for the files and how he did it.
1. Unzip the contents into your android-sdk tools folder
2. adb reboot recovery
3. In recovery go to partitions and select mount\system
4. adb remount
5. Than use these adb commands
Code:
adb push libstagefrighthw.so /system/lib/libstagefrighthw.so
adb push libstagefright_omx.so /system/lib/libstagefright_omx.so
adb push libstagefright_color_conversion.so /system/lib/libstagefright_color_conversion.so
adb push libstagefright_avc_common.so /system/lib/libstagefright_avc_common.so
adb push libstagefright_amrnb_common.so /system/lib/libstagefright_amrnb_common.so
adb push libstagefright.so /system/lib/libstagefright.so
6. In partitions menu unmount/system
7. adb reboot
------------------------------------------------------------------------------------------------
The other way for those who don't like or use clockwork recovery. This time i'm giving thanks to JTNiggle (who has done a lot on this thread thanks )
Okay, i'll give this my best shot here, not my fault if your phone burns down your house. As always, nandroid before, during, after and in between.
First, download the attachments from this post. Unzip Hulu Working Stagefright.zip and place it's contents in your sdk tools folder. Also place Hulu.apk and flash-fixed.apk in the sdk tools folder.
Part 1 (If you don't already have hulu app with flash fix)
On ur phone, open Root Explorer, (or whatever file manager you use but Root Explorer is the best) and navigate to /system/app, make sure you have full permissions set and mounted as r/w. Find all the flash apk's, some ROM's have two, some have one. Their actual names vary, so look thoroughly. Just rename them to something like flash.apk.old, this way you can rename them back if something goes wrong.
Now, still in Root Explorer, navigate to /system/lib, make sure you have full permissions set and mounted as r/w. After that, close the explorer and plug your phone into your pc.
Open up a command promt and navigate to your sdk tools folder where you placed the downloaded files.
Run these commands, one at a time, tapping enter after each one.
Code:
adb push flash-fixed.apk /system/app/
adb push Hulu.apk /system/app/
Now, on your phone, go back into Root Explorer, and navigate to /system/app, find the apk's you just pushed. Tap each one and pick install, follow prompts from there to finish the install. Close the explorer when finished.
If you want, at this point, you can try and open up Hulu on your phone, and see how it's running. The video should start playing fine, but you'll have the demon voices, no biggie, we'll fix that in a minute. If the video wont play at all, and you get a message like, not optimized for your device, or not supported on your platform, then Flash did not install properly. Check everything and re-do the above steps until you get video playback on Hulu. I've had to run through it twice to get it to work sometimes.
Part 2 Once you have hulu and you want to fix demon voices
Now, back to the command promt from your sdk tools folder. Run these commands one at a time, tapping enter after each one.
Code:
adb push libstagefright.so /system/lib/
adb push libstagefright_amrnb_common.so /system/lib/
adb push libstagefright_avc_common.so /system/lib/
adb push libstagefright_color_conversion.so /system/lib/
adb push libstagefright_omx.so /system/lib/
adb push libstagefrighthw.so /system/lib/
Now that all the files are in the proper places, you can reboot, so run
Code:
adb reboot
once your phone boots up, it should be good to go. If not,
This may provide mix results. This is a temporary fix
Good Luck
Confirmed working or not working
****THIS IS WITHOUT ANY MODIFICATIONS TO Stagefrght****
Fresh 3.2 NOT WORKING
AVA'S V7 NOT WORKING
CM 6 Final NOT WORKING
Stock pre 3.28 WORKING (only with stock kernel)
Evio 1.2 NOT WORKING
Evio 1.2beta WORKING
Evio 1.1 WORKING
Burnt droid 1.1 WORKING (with 4.1.9.1 netarchy kernel)
Confirmed working after JTNiggle fix
AVA's V7 (with stock kernel and KiNgxKernel #8 #9)
Burnt Droid 1.1
OMJ 3.1
Fresh 3.2
Confirmed working with My fix .zip
Ava's V7
to help/add to list:
fresh 3.2 and final_flash.apk NOT WORKING properly. (audio studder)
Cm6 final + hulu doesn't work either...it has the demon voice and audio is out of sync
Sent from my Htc Evo 4g
I think its more of a kernel issue than a Rom issue. I know it worked on the stock pre 3.28 ota Rom. No luck with the updated stock kernel.....
Now that I find interesting.
Could I see your build props from before and after flashing a custom kernel
Sent from Evo via mysterious entity
Stalte said:
Now that I find interesting.
Could I see your build props from before and after flashing a custom kernel
Sent from Evo via mysterious entity
Click to expand...
Click to collapse
I don't have the before. Deleted. I know it also worked with the stock Rom running kings #6 BFS318-2.6.32.15. I think you'll find all the new roms people are reporting it not working with are using the updated kernel.
Evio 1.2 not working
Working fine with evio 1.2 with bfs #8. Voices fine. Video smooth at 1228mhz.
Edit: that was 1.2beta before the build was changed. Also had it working no problem on evio 1.1.
Sent from my PC36100 using XDA App
burnt droid 1.1
4.1.9.1 netarchy kernel
runs smooth no problems
Also, I believe the actual hulu app has nothing to do with this. Isn't is just a glorified browser to the hulu mobile widget?
I read on flipz site that he attributes it to the new stagefright .....
GadgetMonger said:
I read on flipz site that he attributes it to the new stagefright included in the new kernel.....
Click to expand...
Click to collapse
That's exactly what it is. The problem was already solved by downgrading it. Not really sure what there is to fix in the hulu "app"
rutter9 said:
That's exactly what it is. The problem was already solved by downgrading it. Not really sure what there is to fix in the hulu "app"
Click to expand...
Click to collapse
Question. Can you rollback stagefright without downgrading the kernel? Or is stagefright a component of the new kernel? Hulu working on the new kernel is what I was hoping for....
GadgetMonger said:
Question. Can you rollback stagefright without downgrading the kernel? Or is stagefright a component of the new kernel?
Click to expand...
Click to collapse
Well you can try this. Here are my library files for stagefright. Mount system/lib as r/w through adb. Pull your stagefright lib files (as a backup) then overwrite with the working ones. Then reboot in adb. Worth a shot.
GadgetMonger said:
Question. Can you rollback stagefright without downgrading the kernel? Or is stagefright a component of the new kernel? Hulu working on the new kernel is what I was hoping for....
Click to expand...
Click to collapse
Thats what im trying to fix or at least disable parts of stagefright to make it work
rutter9 said:
Well you can try this. Here are my library files for stagefright. Mount system/lib as r/w through adb. Pull your stagefright lib files (as a backup) then overwrite with the working ones. Then reboot in adb. Worth a shot.
Click to expand...
Click to collapse
I'm in class right now but could someone try this and let me know if it works?
Stalte said:
Thats what im trying to fix or at least disable parts of stagefright to make it work
I'm in class right now but could someone try this and let me know if it works?
Click to expand...
Click to collapse
Right but it has nothing to do with the hulu app. You just need to patch stagefright.
rutter9 said:
Right but it has nothing to do with the hulu app. You just need to patch stagefright.
Click to expand...
Click to collapse
I agree now if I knew how to change the title of the post I would change it to "working on a way to fix stagefright in new kernels and roms"
Stalte said:
Thats what im trying to fix or at least disable parts of stagefright to make it work
I'm in class right now but could someone try this and let me know if it works?
Click to expand...
Click to collapse
Give me a minute... I'll see what I can do.
Stalte said:
Thats what im trying to fix or at least disable parts of stagefright to make it work
I'm in class right now but could someone try this and let me know if it works?
Click to expand...
Click to collapse
I tried to roll back stagefright last night, wouldn't boot up, frozen then looped. But that was flashing the update patch zip. I'll try it manually later today.
This is on Ava v7 with the new HTC kernel.
rutter9 said:
Well you can try this. Here are my library files for stagefright. Mount system/lib as r/w through adb. Pull your stagefright lib files (as a backup) then overwrite with the working ones. Then reboot in adb. Worth a shot.
Click to expand...
Click to collapse
Nope. Froze up at the white HTC screen on boot.
Hi,
A while back I rooted my phone because I had had enough of missing out on xposed modules and had had enough with all the Ads!! When did Android become so riddled with adverts. (i know its not android itself before you say anything)
Anyway I managed to root my phone using the methods highlighted in the forum. I've got xposed working perfectly but I am still seeing averts in apps and on web pages. Correct me if I'm wrong but I should be able to hide these now. I've come from Galaxy S4 which I had rooted from day 1 so I never saw a single advert (in app or webpage) but now on my rooted Z5 I am still seeing a lot. Many apps (baconreader for example) have had the ads in there hidden but many still persist.
I've tried all the options I can see to be available to me
In no particular order and never installed at the same time incase they conflict.
- Adaway (this errors when applying the host file saying the copy failed)
- Adblock plus (app not browser)
- Adfree (this is what I used on my S4)
- MinMinGuard (tried different modes on this one and still no luck and no errors to speak of)
None of them error apart from AdAway.
Have any of you guys got a totally adfree experience on the Z5? If so how have you managed this?
I am using Adguard, it costs 8$ a year. That's almost free I think.
I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk
Funkmasterchilla said:
I am using Adguard, it costs 8$ a year. That's almost free I think.
Click to expand...
Click to collapse
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?
TimDawg said:
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?
Click to expand...
Click to collapse
AdAway is working for me.
Like I said ensure you can remount /system as r/w.
Sent from my E6683 using Tapatalk
_Dennis_ said:
I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers
TimDawg said:
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers
Click to expand...
Click to collapse
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk
See MOAAB (mother of all ad block) in Android Development and Hacking. Costs 0 bucks and blocks hosts. That's the best if you are rooted bro
_Dennis_ said:
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I get an error saying no such directory. if i try to create it manually it fails...
TimDawg said:
I get an error saying no such directory. if i try to create it manually it fails...
Click to expand...
Click to collapse
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk
_Dennis_ said:
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.
TimDawg said:
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.
Click to expand...
Click to collapse
What super user app do you use? How was it installed?
_Dennis_ said:
What super user app do you use? How was it installed?
Click to expand...
Click to collapse
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.
TimDawg said:
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.
Click to expand...
Click to collapse
Probably your best bet. Sorry I couldn't be of any help.
Sent from my E6683 using Tapatalk
How did you rooted your z5?
luisfillipe said:
How did you rooted your z5?
Click to expand...
Click to collapse
I used the method for Z5 dual SIM posted in the dirty root thread in development section. There are other simpler methods for the regular Z5, again in development section. It requires bootloader unlocks for all of them and that causes you to lose some Sony DRM keys.
Sent from my SM-T710 using Tapatalk
I tried Adblock since i'm not rooted, but it occasionally drain battery in sleep mode so I removed it..
I've always used Lucky Patcher for that. It has hosts blocking as well as disabling google ad modules inside apps, making everything clean and bull$hit free.
Gotta say I was starting it get a be pissed off with how much more complicated it is to do root this phone than any other android phone I've tried to do in the past...
so I came to the assumption that I'm supposed to be booting into recovery and installing the zip through there like I used to do to install ROMs on my older android phones.
I've flashed a few AndroPlus kernels and no luck. One of them left me stuck in bootloop which I let go around roughly 10 times until I decided it was getting nowhere. I did eventually manage to get one installed without a bootloop.
I wanted to know what Kernel I was running so I installed 'Kernel Adiutor' which required BusyBox to be installed alongside it. I found I was unable to install BusyBox which I guess was caused by the same thing causing all my other issues.
I've tried going through this whole over complicated process again and I hit a problem was trying to execute these two lines:
Code:
adb shell mount /dev/block/platform/soc.0/by-name/system /system
adb shell mount /dev/block/platform/soc.0/by-name/userdata /data
I read through everything I could find again to see if I could work out what was going on. While looking for this I can across this line of code:
Code:
fastboot flash boot boot.img
which is to be run if you want to flash the kernel via adb. (you need to extract the zip provided by AndroPlus)
Once this line had been executed I booted up again and was able to install BusyBox which let me see which kernel I had which showed AndroPlus (v3 incase you're interested) so I then tried AdAway again.
BINGO
Only thing is on some websites, particularly xda there is still a gap showing where the Advert would be displayed if not blocked. This I can live with.
I can't beleive how much more complicated this phone is to root compared to my HTC Desire, Galaxy S2 & S4. All of them were plug phone in. Click a few times and the jobs done. Is there a reason this hasn't been done for the Z5?
Just want to say thanks to all that have tried to help.
Thanks to AndroPlus for his kernel which has sorted me out.
Not so much thanks to Sony as this whole process has put me off ever getting another Sony phone. Mainly the fact I've lost some functionality what with having to unlock the bootloader. Overall I'm happy though.
Cheers