Related
Did you Ever Wanted your Own Custom ROM? Did you don't understand other Guides? Do you don't Like ROM Kitchens? Than this Guide is the right Guide for you! Just Try It and you can create your Own Custom ROM!
General Information
So, Before we start with this Guide, i just want to tell you some General Informations about [highlight]Custom Roms[/highlight]. When you buy your phone, you will have a [highlight]Stock ROM [/highlight]installed. A [highlight]Stock ROM [/highlight] is just that Software, your Company has created, especially for your phone. It's a Software like Android 2.3.4 with Touchwiz 4 or Android 4.0.4 with Sony UI. Those Softwares may be good, but there are many Things to Improve, for the Best Xperience, while using your Phone. A [highlight]Custom ROM [/highlight]can be complete different to [highlight]Stock ROM [/highlight], like [highlight]Cyanogenmod 10 [/highlight], or be just a improved Version of the [highlight]Stock ROM [/highlight]. To Build a [highlight]Custom ROM [/highlight] you need to know a few Words, and have a Phone with Root Acess + S-OFF / Unlocked Bootloader. So in this Guide we will concentrate on the Easy Way, the [highlight]Improved Stock ROM [/highlight]. You Can also Build a [highlight]ROM [/highlight] out of Source from Google, but thats too complicated for beginners. Setting up compile envirment can be quite complicated . So let's take a look at stuff you need to know:
[highlight]Root Acess[/highlight]
Complete Acess to all System Files, like Administrator on Windows. To Root Your Phone, search XDA. Rooting your Phone is done by putting su library to /system and manage acess with SuperSu or Superuser. When you buy your Phone, it doesn't have Root Acess. Root Acess is needed for installing CWM, mount your /system as Read & Writeable ----> You can delete system files, and installing apps to /system/app, by copying them to /system/app. By Rooting your Phone you loose Warranty, but you can reinstall stock software and no one will notice
[highlight]ClockWorkMod Recovery (CWM)[/highlight]
Recovery Mode of your Phone. In Recovery you can install flashable zips and roms, wipe and format your device, mount different partititons and fix permissions... To Get CWM search XDA. There are different Ways for every Device. You can enter recovery before your device is fully booted, and since touchscreen drivers are not yet available you need to use the volume buttons for controlling the recovery. There are different ways of entering cwm for every device.
[highlight]Rom & Kernel[/highlight]
ROM means: [highlight] Read-Only-Memory[/highlight] . The Funny Thing is that we can Read and Write on our Read-Only-Memory. Anyway, its a partition which includes large parts of the OS ----> operating system of your Phone. In a [highlight]ROM[/highlight] for Android Phones are included apps, framework, libs & many more and since android is modular, there is an app for everything (keyboard, launcher, statusbar). Together with a [highlight]Kernel[/highlight] it's the "Life" of your Phone.
The Kernel is needed for a working Phone. You Can Install Stock or Custom Kernel. When you buy a Phone Stock Kernel is preinstalled of course. The kernel includes many drivers, controlls the cpu and does many more... Just rember that word
General Information
1. Install Stock ROM to your Phone - This Can be Done by Flashing via Flashtool or Odin. You Need a Clean Base to Start. Recomnend is a Stable, Official ROM, like Gingerbread, Ice Cream Sandwich or maybe Jelly Bean.
2. Root the ROM. This Can be done with Different Tools, Very Popular is for Example SuperOneClick Tool.
Just search for "my device name root" in xda if your not sure
3. Improve Stock ROM on Your Phone. So, After You Have Installed the Stock ROM and Rooted the ROM You Can Start. Now You Need To Change Some Things, To Make the Stock ROM to a Customized ROM. You Can do a lot Things, Here are a Few Examples:
- Install Latest Superuser SuperUser
- Install Latest BusyBox Auto-Installer
- Supercharge the ROM, enable Zipalign etc.. ----> here
- Remove Bloatware. Use Es File Explorer to remove not longer needed apps in system/app partitition
- Tweak Build.prop by going with ES File Explorer to /system and editing your build.prop. now you can change the Name shown in Settings and do a lot more ----> http://forum.xda-developers.com/showthread.php?t=1227269
- Change the Bootanimation. You can find a lot of them by Going to themes and apps of your own device.
- Add or Change Apps. Check out Themes and Apps Selection of Your Device and Install a few Of Them, If You Are Allowed to use MooDeD Apps created by other Users
3.1 Now Delete/remove all backups in clockworkmod/backup folder
4. Now Make Sure You Have Installed CWM. If You Have Changed a Lot Things and You Think Your ROM is good enough, Boot to CWM, select wipe data/factory reset and Boot up again. If You Are Still able to Boot, Check the ROM for Bugs or Problems. Write them Down. Try to fix them. You can always take a logcat (adb logcat)
Than Boot again to CWM select wipe data / Factory reset ---> yes advanced ---> wipe battery stats ---> yes. Now Select backup & Restore ---> Backup.
5. Connect Your sd card to PC and go to Clockworkmod/backup folder. Now Go to the only 1 backup folder and copy "system.img" to your PC.
6. On PC Open Yaffey and Choose Open ---> system.img and than extract to empty folder called system.
7. Now You Will Get a Folder "system" which contains the System of your Phone. Now Create an Empty .zip file and paste in extracted Meta-inf folder Download and copy folder "system" inside. ROM should be flashable for NOW!
Remeber to mount /system before flashing // replace with mount Script for ur device... You can check this by dowoading any rom 4 ur device
NOTE: This has nothing to do with developmemt or original development in any way. Its theming a stock ROM in the simplest way...
Just Press thanks if this was helpfull in any way...
How to
[[ Placeholder ]]
[[ Placeholder ]]
[!][RESERVED][!]
[[ Placeholder ]]
1 year later:laugh:
Sorry... I will finish this guide later...
And so on...
Sent from my GT-S7500 using xda premium
To infinity and beyond!
saiz136 said:
To infinity and beyond!
Click to expand...
Click to collapse
Beyond Smart xD
Updated Thread and Added a First Guide
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
ruizit0 said:
so where is the guide ? lol ...
maybe make the guide before in PC and the create the thread ? .. just sayin
Click to expand...
Click to collapse
There is a guide lol
jader13254 said:
There is a guide lol
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
ahaha sorry .. i was thinking that was a little intro explaining clocklowrk and stuff .. to a coocking tutorial ahaha
maybe you can expecify more in title or something
nice tutorial to create a rom this way .. i read somewhere that the next clockwork will have this feature
Will try..
Sent from my GT-N8000 using Tapatalk 2
kaipro said:
Will try..
Sent from my GT-N8000 using Tapatalk 2
Click to expand...
Click to collapse
You need different commands for wiping on g Note, just search your device forum
Sent from my LT18i using xda app-developers app
Where is the system.img? I didnt have one when i backed up with cwm
very noob-friendly !
CovXX said:
Where is the system.img? I didnt have one when i backed up with cwm
Click to expand...
Click to collapse
check clockworkmod/backup folder... there should be system.xxxx.img
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
At the moment you can't until Google updates that feature to allow that. The multiuser is in its infancy. We will just have to wait I guess.
Sent from my Nexus 10 using Tapatalk HD
Thanks for your answer
waiting for this ...
It's actually the su binary which is tied to the primary user only at the moment... not sure how, or if, it can be built otherwise!
Furthermore, it is not even possible to enable developer settings (via build no) for second users, right?
So, without USB-Debugging no adb to backup second user apps (w/ data) using the Toolkit..
Is there any chance to fully backup second user apps? Apart from nand of course, as I would like to backup/restore apps for a switch to CM10.
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
craigacgomez said:
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
Click to expand...
Click to collapse
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
djd338 said:
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
craigacgomez said:
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
Click to expand...
Click to collapse
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
jrod091 said:
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I don't know if RC settings are global or user specific... depends of the settings... if the setting is specific to the user context, it will work, otherwise it won't...
drykc said:
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
Click to expand...
Click to collapse
If you are using SuperSu, the dialog asking for root permission shows up on the owner's user account. In SuperSu, only the owner can grant superuser privileges.
Sent from my Nexus 4
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Should probably ask in the n7 forum...
Sent from my Nexus 10 using xda app-developers app
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
The SoC in the Nexus 7 is Tegra 3, which has an ARM processor. You're fine.
Sent from my Nexus 10
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Lol of course n7 has an arm cpu!
For android phones and tablets, there's arm, mips, and x86. Any good android will 98% likely be arm. Motorola released an x86 (Intel) phone, and I'm sure there's a few other ones out there. And if you have mips, you probably got a cheapy Chinese tablet. xP
Swiped from my Nexus 10 using xda-developers app
Sorry for hijacking.
My main reason for root is to restore application data. Will I be able to restore the data on both the primary user and also the secondary user if I have root (either through the main or secondary user)
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
1234556789 said:
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
KlipperKyle said:
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
Click to expand...
Click to collapse
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
1234556789 said:
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like you have Superuser 3.3 installed and working, right? In order to use Superuser 3.3 with another user account, you need to go to its preferences and change Multi-user Mode to something other than "Owner Only."
"Owner only" means that only the owner can su.
"Owner controlled" means that the owner is the only one who can set and deny root permissions. Any filters are applied to all users.
"User controlled" means that each user can define allow/deny filters. Only use this option if you really trust other users.
Don't update to the version of Superuser on the Play Store. The version on the Play Store is 3.1.3. You already have 3.3 flashed on your system partition. Because you won't need the version on the Play Store, you can also stay away from ChainsDD's Superuser Update Fixer. (The update fixer is for an entirely different issue than the one you have.)
If you have installed these packages, you should uninstall them.
For future reference:
I should have been clearer about deleting files in custom recoveries. If you use TWRP, there is a built-in file manager under the Advanced menu. If you use ClockworkMod, you should use ADB commands: (ADB is a tool found in the Android SDK)
Code:
adb shell
cd /system
ls -al
[I](You should see a bunch of directories. If not, make sure /system is mounted.
This is an option in one of the recovery menus; I can't remember which
one offhand.)[/I]
rm app/Superuser.apk
rm bin/su
rm xbin/su
Then reflash the Superuser zip.
Hi, I tried to install viper4android sound mod but it is not installing. It says please check if the device is rooted or busybox is installed or not.
I am on PA 17th August and Franco kernel, with busybox and full root naturally. Is there any explanation or solution to install drivers?
I've tried:
°Uninstalling app and re-installing…
°changing Roms and kernels…
°turning on "safe mode" and "compatible mode" in the app
°deleting dalvik cache
°selecting A8 drivers and A9 drivers too (users said both work).
But still it won't install, it gives the same error if someone can be of help, I'd be really grateful thanks!
Sent from my Nexus 4 using xda app-developers app
Jamal Ahmed said:
Hi, I tried to install viper4android sound mod but it is not installing. It says please check if the device is rooted or busybox is installed or not.
I am on PA 17th August and Franco kernel, with busybox and full root naturally. Is there any explanation or solution to install drivers?
I've tried:
°Uninstalling app and re-installing…
°changing Roms and kernels…
°turning on "safe mode" and "compatible mode" in the app
°deleting dalvik cache
°selecting A8 drivers and A9 drivers too (users said both work).
But still it won't install, it gives the same error if someone can be of help, I'd be really grateful thanks!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Make sure that u have installed busybox by opening that busybox installer app, people get confused by installing app only.
Rest I don't know, I have install this mod yesterday only working fine.
mohitgalaxy3 said:
Make sure that u have installed busybox by opening that busybox installer app, people get confused by installing app only.
Rest I don't know, I have install this mod yesterday only working fine.
Click to expand...
Click to collapse
I also have installed busybox through the app too! :/ it still won't work xD
Sent from my Nexus 4 using xda app-developers app
I had this problem as well, try downloading supersu and updating the su binary via TWRP. viper somehow worked after that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Make sure you have the latest version by updating thru the in app settings. Also, superuser will not work. You must be using supersu for root.
Sent from my Nexus 4 using Tapatalk 4
Jamal Ahmed said:
I also have installed busybox through the app too! :/ it still won't work xD
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
no need install busybox also working perfectly on s2.
flash supersu on top superuser.
i read this post because i have the same inssue on MTK6582 phone...i have root only by irrot aplication and installed the superSU app, updated via Normal mode, but i read somewhere i only can install the viper4 driver if i update my superSU via TWRP, is true? and if i dont have the TWRP installed can i update this way anyway? i dont want my phone get bootloop or anything...plz help!
Thanks
was also having problem with driver installing, updated supersu through recovery, driver was installed successfully but still no effect on audio, driver is reporting Abnormal and not supported.
I'm also unable to install drivers due to busybox error.
Set SELinux to permissive
legodark said:
Set SELinux to permissive
Click to expand...
Click to collapse
Accurately :fingers-crossed:
Tied everything everyone else has tried still same problem including changing selinux to permissive. please anyone have a fix?
Uninstall existing Viper APK. Locate XDA thread with viper_v2.3.3.0.zip in it (it also has 2 more tweak zips) and then first flash viper_v2.3.3.0.zip and then the other two from recovery. This flash wipes davlik cache so it takes some time to rebuild on boot. Then install Viper driver and boot again. Done.
same problem on device never had before
Hjicons said:
Uninstall existing Viper APK. Locate XDA thread with viper_v2.3.3.0.zip in it (it also has 2 more tweak zips) and then first flash viper_v2.3.3.0.zip and then the other two from recovery. This flash wipes davlik cache so it takes some time to rebuild on boot. Then install Viper driver and boot again. Done.
Click to expand...
Click to collapse
I'm having this broken busybox or not rooted completely/correctly error trying to install any version of viper4android as well. I have always had viper on this tablet, latest complete install of firmware is when problem started. But I have tried all fixes as everyone else has including using a cached buybox apk from previous install just to make sure something hadn't changed in Stericson's busybox, no go.
This is a real head scratcher!
Zach
Way late, but fix found
Jamal Ahmed said:
Hi, I tried to install viper4android sound mod but it is not installing. It says please check if the device is rooted or busybox is installed or not.
I am on PA 17th August and Franco kernel, with busybox and full root naturally. Is there any explanation or solution to install drivers?
I've tried:
°Uninstalling app and re-installing…
°changing Roms and kernels…
°turning on "safe mode" and "compatible mode" in the app
°deleting dalvik cache
°selecting A8 drivers and A9 drivers too (users said both work).
But still it won't install, it gives the same error if someone can be of help, I'd be really grateful thanks!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Here is what I found that fixes this:
OK all I have a fix for installing Viper on the Tab S.
Use any file explorer and navigate to /system/vendor/etc
Copy the audio_effects.conf in that location
Navigate to /system/etc and paste the file you copied there
Once copied change the permissions to match the other files in the /system/etc folder
Install Viper and it should work this time, apparently the audio.effects.conf file is expected to be in the /system/etc location and is not there by default for some reason....*"
Even though this file was where it said to copy to, contents were different. Either way, afterwards all I had to do was open the V4A apk and it asked to install driver, BAM........!!!!!!! Worked!
Zach
Dumb question, but have you made sure that you have granted storage permission in the Apps Menu?
coolbeans2016 said:
Here is what I found that fixes this:
OK all I have a fix for installing Viper on the Tab S.
Use any file explorer and navigate to /system/vendor/etc
Copy the audio_effects.conf in that location
Navigate to /system/etc and paste the file you copied there
Once copied change the permissions to match the other files in the /system/etc folder
Install Viper and it should work this time, apparently the audio.effects.conf file is expected to be in the /system/etc location and is not there by default for some reason....*"
Even though this file was where it said to copy to, contents were different. Either way, afterwards all I had to do was open the V4A apk and it asked to install driver, BAM........!!!!!!! Worked!
Zach
Click to expand...
Click to collapse
Thanks Thanks alot for this, i was navigate for hours!!! This really works, thanks ^^
coolbeans2016 said:
Here is what I found that fixes this:
OK all I have a fix for installing Viper on the Tab S.
Use any file explorer and navigate to /system/vendor/etc
Copy the audio_effects.conf in that location
Navigate to /system/etc and paste the file you copied there
Once copied change the permissions to match the other files in the /system/etc folder
Install Viper and it should work this time, apparently the audio.effects.conf file is expected to be in the /system/etc location and is not there by default for some reason....*"
Even though this file was where it said to copy to, contents were different. Either way, afterwards all I had to do was open the V4A apk and it asked to install driver, BAM........!!!!!!! Worked!
Zach
Click to expand...
Click to collapse
OMG DUDE OMG BRO OOOOOOOMMMMMMMFFFFFFFFGGGGGGG. it worked. ****ing love you to death man
driver still not working
my audio_effects.conf file it is system/etc and viper4android is still not installing that driver. please help me
thanks button
K9-1000 said:
OMG DUDE OMG BRO OOOOOOOMMMMMMMFFFFFFFFGGGGGGG. it worked. ****ing love you to death man
Click to expand...
Click to collapse
Don't 4get the thanks button,
---------- Post added at 03:44 PM ---------- Previous post was at 03:42 PM ----------
lukzifer said:
Thanks Thanks alot for this, i was navigate for hours!!! This really works, thanks ^^
Click to expand...
Click to collapse
Don't 4get the thanks button,
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
rauul95 said:
my audio_effects.conf file it is system/etc and viper4android is still not installing that driver. please help me
Click to expand...
Click to collapse
like I said, my /etc had the file already as well, but by pasting over it, obviously changed contents, afterwards V4A installed drivers and worked.
I also found another mod that works, V4A FX, is 16ghz, but by downloading and installing V4A XHIFI, then installing the FX over it (you just activate the XHIFI, first check option under settings, then go back to FX), you get 32bit sound! Yeahhhh Baby!!!!!!!!
can anyone advise? i want to install a custom rom and root my tf300t
i have unlocked it but now i need to install the mod twrp but apparently i need a pc. is there another way? via .apk file or something...
i then need to put my rom and gapps file on sd card, reboot to recovery and install the zip files right? and i am done????
wakkaday said:
can anyone advise? i want to install a custom rom and root my tf300t
i have unlocked it but now i need to install the mod twrp but apparently i need a pc. is there another way? via .apk file or something...
i then need to put my rom and gapps file on sd card, reboot to recovery and install the zip files right? and i am done????
Click to expand...
Click to collapse
Yes you can do that, all you need is a "terminal emulator" app, there are plenty available just search for them. Depending on the custom ROM some already provide updated gapps so be sure to use the right one and not just the one given in tools like goomanager.
I would recommend the following.
1. Backup your apps + data using Titanium Backup
2. Boot into recovery and create a backup of your system
3. Wipe cache/davlik/data + system
4. be aware of the right "flashing order" FIRST the ROM file, then add more zips and choose gapps
5. enjoy your custom ROM
frankgreimes said:
Yes you can do that, all you need is a "terminal emulator" app, there are plenty available just search for them. Depending on the custom ROM some already provide updated gapps so be sure to use the right one and not just the one given in tools like goomanager.
I would recommend the following.
1. Backup your apps + data using Titanium Backup
2. Boot into recovery and create a backup of your system
3. Wipe cache/davlik/data + system
4. be aware of the right "flashing order" FIRST the ROM file, then add more zips and choose gapps
5. enjoy your custom ROM
Click to expand...
Click to collapse
Something tells me he hasnt rooted yet. If im not mistaken, he can't use a terminal app with the dd command if he isnt rooted. I know you can root using adb though with debugging enabled but im not sure he can root without a pc.
Here is a good place for him to start :
http://forum.xda-developers.com/showthread.php?t=2228613
Sent from my SGH-T889 using xda app-developers app
pyraxiate said:
Something tells me he hasnt rooted yet. If im not mistaken, he can't use a terminal app with the dd command if he isnt rooted. I know you can root using adb though with debugging enabled but im not sure he can root without a pc.
Here is a good place for him to start :
http://forum.xda-developers.com/showthread.php?t=2228613
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the correction, assumed he's already rooted sorry.
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.
I just wanted to clarify that with S-OFF this module is useless
migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk
For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.
I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).
blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.