Hi folk.
I wanted to know a few thing.
As many ppl I have buy a cheap phone ( SC6820 based ), it is already rooted and everything work nice atm.
But since I was dev ( I have made 3 years study in IT university, then I become nertwork manager / architect) I rly want something but something that can be impossible ( I have poor knowledgement in android )
http://forum.xda-developers.com/showthread.php?t=2121128
Explain how to port android 4.X on other device, bit since there has been only few changes since android 2.X
I wanted to know if I can make the same to use a CM7 with my andro device ?
I already know few things :
Partition are not the same than standard android, so I will have to change them ( I will have to change fstab files but IDK what exactly )
They also use non standard frame buffer so I will have to load the correct driver ( /system/lib/modules -- /system/lib/hw I guess )
but I have already see that boot loader can be a serious problem I know what it is in computer but in phone ? use the standard kernel of the device will be enought ?
This is my main project.
but since CM9/10 can be run with 2.6XX kernel why not try that ?
can it be apply with this rom ?
http://forum.xda-developers.com/showthread.php?t=1374691
I think yes but since I don't have source of my kernel i don't rly know if it is rly doable.
Galaxy 3 is less powerfull than my device so if it run nice on galaxy 3 no reason it doesn't run on my phone.
This are only trick but since I have my dev environment already build, I can make effort, compiling, modding etc etc
the phone :
h**p://www.dhgate.com/supply-mini-i9300-phone-3-5-inches-sc6820/p-ff8080813d7cbab5013d8b6afc952695.html
Any answer or question are welcome here
Hello guys , I'm starting this thread with full of responsibility of the working Camera on CM10 (on which the camera still haven't got fixed )
Firstly I want to give Credits to the DEV , and to my friends that really helped me on the way :
# @TheWhisp (Who made possible CM10 & CM10.1 , also for the libraries he has provided on his cm-10-20130720-UNOFFICIAL-jena.zip build , and also for the AutoFocus fix which he has provided with a hw library,also for the hints he gave to make the VOip work .Hints taken by his own https://github.com/TheWhisp/android_device_samsung_msm7x27a-common/issues?page=1&state=open )
# @vickyg.coolest for the list of libraries he told me to replace , and for his help
# @Bassel Bakr who made a Torch app which makes the Flash work on CyanogenMod ROMs
# @davideddu96 (who made possible FlashLight work on CM10.1 & CM10 )
First download all the libraries shown below ,
Then download the CM10 build of Trebon here : http://goo.im/devs/thewhisp/trebon-cm10/cm-10-20130506-UNOFFICIAL-trebon.zip
Extract it anywhere , then replace the libraries as shown below :
libcamera.so ' libcamera_client ' liboemcamera.so to system/lib
camera.msm7x27a.so system/lib/hw
ZIP the ( system,META-INF,boot.img)
Boot into the ROM , and then go to **Terminal Emulator and write sysctl -w kernel.randomize_va_space=1 , then go to Camera (it will crash for the First time , but if you open again , it will work )
If you want the flash to WORK , you must download the app Torch made by Bassel Bakr (thanks to him) , turn the flashlight ON , then it will PROMPT to Allow/Deny on SuperUser , you should ALLOW it to Work (this happens always when you Turm ON the flashlight , so if you want to fix this , go into SuperUser , Preferences/Security tap on Automatic Response and select Allow)
VOip Fix
You will probably have problems with VOip , especially with Viber (which I am using ) , your sound will not be sent to other party , neither you will hear other party's sound .
So just copy and replace the libraries attached below , and copy as shown below :
audio_policy.conf to system/etc
This is it , the camera should work until your next reboot , because when the device reboots the PIE Enables by its own way .
**these stars mean that you have to do this on every boot/reboot ( go to Terminal Emulator and write sysctl -w kernel.randomize_va_space=1 )
Full credits go to :
TheWhisp
Vickyg.coolest
Bassel Bakr
Davideddu96
Again, I didn't do anything! All the credits go to TheWhisp! I just noticed that file in the sysfs!
Can we use cm 10.1 kernel on cm 10? Since arm pie has been permanently disabled in cm10.1.
mon_iker said:
Can we use cm 10.1 kernel on cm 10? Since arm pie has been permanently disabled in cm10.1.
Click to expand...
Click to collapse
Will try and report
Edit' Tried taking the CM10.1 kernel , but got a bootloop , so sorry , also tried TweakNOS , did nothing , if we use the CM10 , we should still execute that command after every reboot /boot . Sorry guys , I'm not a Developer that can fix this issue , if someone can help , write down here , or try to ask thewhisp how to disable ARM_PIE permanently .
Sent from my GT-S7500 using xda premium
davideddu96 said:
Again, I didn't do anything! All the credits go to TheWhisp! I just noticed that file in the sysfs!
Click to expand...
Click to collapse
If you wouldn't tell us that command , maybe we (trebon users) couldn't even know what is that camera_rear_flash until now , so you are a contributor too .Thanks anyway for that command
Great work Bro. finally I can use mobile data and also working camera (partially) on one ROM!
tried multiple times but black screen comes and camera stop:crying:
jatin3 said:
tried multiple times but black screen comes and camera stop:crying:
Click to expand...
Click to collapse
Most probably you're doing something wrong , just write here the steps you did
So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.
Can i flash it on android one device running on 6.0.1
Yes. If you have any issues, please let me know!
rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:
It works great. thanks.
my bad for not following the instructions.
Hello guys. This is my first post. I've been looking around a way to install kali net hunter on my s7. However i did not found a tutorial video in which kali net hunter was set up as a secondary ROM. I installed the app " Dual boot patcher " and downloaded all the file needed for this installation : hydrarom and the other 3 files needed ( the kernel, nethunter and its update ) . I found many problem :
1) nethunter is supposed to be flashed over a pre-installed rom. I have to patch and flash hydrarom and then flash nethunter. How can i flash a file over a non-primary rom?
2) i have also to change the kernel file , however the app does not allow me to change the kernel to a chosen one. Do I have to change the primary's kernel , set up this one from the app and then restore the first one for the primary ROM ? In other words, I want to have kernel A for primary ROM and kernel B for the second one. Is this possible?
3) If I manage to end this madness, will i see a bigger battery usage?
Sorry for my bad english, hope all of you have a great day
As you guy know , Google hate root , either Samsung . I know you guy are try making ROMs on these Samsung phone but you don't know ...
GOOGLE IS TRYING TO HIDE GOOD ROMs FROM US !!
So the ROMs are hidden from Google search are the very old one : Breeze + and Firehound
Why ?
Because we can EASILY modify the system through those ROMs
PROVE : TRY USE " LIVEBOOT " OR MODIFY THE /SYSTEM ( except : build.prop and apps ) you will see your modifications doesn't work and it's just keeping reverse
+ my phone can't even install ViperFX driver in app
If u're a modder , you should know /sbin/.core/mirror/system . I always have to mod through it , I can't mod the system in the usuals path !
So we should find a solution :
1 . Disable that symlink between /sbin/.core/mirror/system and /system ( I'm not sure but I think the problem is the kernel )
2 . Tell magisk to symlink every modifications from /system to /sbin/.core/mirror/system
3 . Tell other to update their app + mod to modify that path ( but they are to many ! )
So what are you guy idea ? I'm confusing a lot ! :/
Vipxpert said:
As you guy know , Google hate root , either Samsung . I know you guy are try making ROMs on these Samsung phone but you don't know ...
GOOGLE IS TRYING TO HIDE GOOD ROMs FROM US !!
So the ROMs are hidden from Google search are the very old one : Breeze + and Firehound
Why ?
Because we can EASILY modify the system through those ROMs
PROVE : TRY USE " LIVEBOOT " OR MODIFY THE /SYSTEM ( except : build.prop and apps ) you will see your modifications doesn't work and it's just keeping reverse
+ my phone can't even install ViperFX driver in app
If u're a modder , you should know /sbin/.core/mirror/system . I always have to mod through it , I can't mod the system in the usuals path !
So we should find a solution :
1 . Disable that symlink between /sbin/.core/mirror/system and /system ( I'm not sure but I think the problem is the kernel )
2 . Tell magisk to symlink every modifications from /system to /sbin/.core/mirror/system
3 . Tell other to update their app + mod to modify that path ( but they are to many ! )
So what are you guy idea ? I'm confusing a lot ! :/
Click to expand...
Click to collapse
I mean we can't mod the new ROM but the old one can ! :/