• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Galaxy Rush[kRom LV.5 ROM]Build.prop[DISCONTINUED]

pyro_guy0001

pyro_guy0001

Android Enthusiast
Noticed:
|This build.prop is edited only for Galaxy Rush 4.1.2|
This file for kRom V.5 Beta.
This may cause major issues if you not running this ROM.
[/CENTER]

UPDATE: when K Rize updates the kRom, I might stop on this thread.
I sent him the file and ask and he will put it in the update.
|I'm using kRom V.6 so this thread is stopped unless I have better build.prop, thank y'all who used my build :)
~Features
 
Hello and welcome to the forums . If you have a problem like this in the future all you need to do is just reflash the rom/build without wiping anything
 
I'm running This rom (kRom v.5 Beta) Just did another fresh install because the no boot problem. & I wanted to know if I Flashed A kernel v2.3 would it still let me use the build.prop , or should I just keep the stock kernel for kRom v.5
 
You can use any build dot prop. All u have to do is edit the prop and just copy and paste information to the prop just have a backup and when you get a good one keep it. Just make sure if its a speed kernel you edit battery collapse :eek::D
 
It is many build dot prop editors in the playstore . Romtoolbox lite and paid version . And many more
 
Just get a copy of a build. Prop and move to a special location using a file / root explorer . I used es. Since it came out . But u open as text editor learn what each prop is . Some you dont mess with if you see ro.ril . The ril control the radio interface. But its easy
 
The reason you bootlooped is probably, because you didn't set the permissions before you rebooted

kRom v.5 already has the akernel2.3 installed, but if you want the stock kernel back, you can find it in the how to get to jellybean thread, 3 post down.

You should also read the whole forum before attempting to move files around, so you can learn from others, and also know what is going on
 
K Rize said:
The reason you bootlooped is probably, because you didn't set the permissions before you rebooted

kRom v.5 already has the akernel2.3 installed, but if you want the stock kernel back, you can find it in the how to get to jellybean, 3 post down.
Click to expand...

& how do I set the permissions exactly? I usually don't have to so I don't worry about it, Only permissions I know of is the Fix Permissions in CWMR
 
Sorry if I caused issues but u gotten be on kRom becuz the kernel its using. But I hope your issues be fixed. And it be in kRom V.6 so don't worry.
 
Well I might start my own ROM due to k Rize is no longer making updates on the kRom. So I may make my own but from his last update
 
Thnx but it be harder becuz I'm my own and if I get a lot better I wanna be part of a team creating a good harass rom
 
OK sure I'll help but k rize is teaching me but I may still make a good themed ROM but IMA learn. I didn't taken it personal lol
 
You must log in or register to reply here.
Back
Top Bottom