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

Root [Virgin Mobile] [ROM][MK5][STOCK][ODEXED/DEODEXED]- Virgin Mobile/Boost Mobile

Thanks JD for this rom!! It saved me!

By the way, after updating to 4.3 via the stock ota zip my SE for Android status was in "enforcing" mode.. but after completely wiping and installing your mk5 zip, SE for Android status has changed to "permissive".. just thought I would pass that along :D :thumbup:
 
TheBritton said:
Thanks JD for this rom!! It saved me!

By the way, after updating to 4.3 via the stock ota zip my SE for Android status was in "enforcing" mode.. but after completely wiping and installing your mk5 zip, SE for Android status has changed to "permissive".. just thought I would pass that along :D :thumbup:
Click to expand...

Enforcing mode can be changed to permissive with Terminal Emulator if need be as well: open program, type "su" (no quotes when typing), enter key, then "setenforce 0" press enter and then close program. Make sure to actually close and not just back out because it will run in background and drain battery.
 
struckn said:
Enforcing mode can be changed to permissive with Terminal Emulator if need be as well: open program, type "su" (no quotes when typing), enter key, then "setenforce 0" press enter and then close program. Make sure to actually close and not just back out because it will run in background and drain battery.
Click to expand...

Thanks. Not sure if the mode affects tether blocking but I'll give it a go again :)
 
Quick Noob question.
just picked up my gs3 ungraded to 4.3 with Knox during initial start up :( can i flash this over the existing stock knox 4.3 with out Bricking? if so will this knox garbage be removed?
 
John762 said:
Quick Noob question.
just picked up my gs3 ungraded to 4.3 with Knox during initial start up :( can i flash this over the existing stock knox 4.3 with out Bricking? if so will this knox garbage be removed?
Click to expand...

You may flash any ROM that is 4.1.2 or higher. You may be able to remove the Knox apps only. Not the bootloader. But don't worry about the bootloader. It only shows that your warranty has been void and connot change. Yes you may flash any ROM with removed knox apps without bricking. :)
 
peter counias said:
Can I flash this rom an your rom if I have the knox bootloader ??
an am on 4.3 already !
Click to expand...

Yep! I just did that. I was on 4.3 with Knox already. I screwed up my system by editing the databases trying to get tether to work. I did a full wipe and installed this rom easily. In fact, it's smoother now than it ever was.

EDIT: Oops, this is an old question but it looked recent in my Tapatalk app. Oh well, I guess I'll leave it here for the sake of information ;)
 
struckn said:
Enforcing mode can be changed to permissive with Terminal Emulator if need be as well: open program, type "su" (no quotes when typing), enter key, then "setenforce 0" press enter and then close program. Make sure to actually close and not just back out because it will run in background and drain battery.
Click to expand...

And then to revert to enforced mode one would type "setenforce 1"?
 
TheBritton said:
Thanks JD for this rom!! It saved me!

By the way, after updating to 4.3 via the stock ota zip my SE for Android status was in "enforcing" mode.. but after completely wiping and installing your mk5 zip, SE for Android status has changed to "permissive".. just thought I would pass that along :D :thumbup:
Click to expand...

Yeah, I changed the script in the init.rc of the ramdisk to make se permissive. One more step to kill the Knox
 
Darien153 said:
You may flash any ROM that is 4.1.2 or higher. You may be able to remove the Knox apps only. Not the bootloader. But don't worry about the bootloader. It only shows that your warranty has been void and connot change. Yes you may flash any ROM with removed knox apps without bricking. :)
Click to expand...

Just make sure you don't try to flash another boot loader using Odin. You'll brick solid. You're stuck with the Knox boot loader, and when you flash the custom recovery, you've voided the warranty, but at least you can flash stuff. But don't try changing boot loader...that would be bad
 
jdsingle76 said:
Just make sure you don't try to flash another boot loader using Odin. You'll brick solid. You're stuck with the Knox boot loader, and when you flash the custom recovery, you've voided the warranty, but at least you can flash stuff. But don't try changing boot loader...that would be bad
Click to expand...
didn't change loaders followed instructions phone stuck on samsung screen after the VM flash screen
oops

Scratch that just took 10 minutes to get past the screen
 
John762 said:
didn't change loaders followed instructions phone stuck on samsung screen after the VM flash screen
oops

Scratch that just took 10 minutes to get past the screen
Click to expand...

Yes! Sorry for the late reply I saw this and was going to mention that the first boot takes a while. Especially if you wipe dalvik cache beforehand :)
 
flashed this rom about 2 days ago, and everything was working great, but this evening my sms have stopped sending??

However I can recieve sms and send/recieve mms :confused: anyone else run into this or have any ideas?

btw AWESOME work JD and thanks for the help the other day, all you guys are really great I wish i had more I could contribute but im android stoopid lol
 
ok new one up and running no performance issues :) Great build
however the VM default config keeps trying and failing any thoughts?
 
John762 said:
ok new one up and running no performance issues :) Great build
however the VM default config keeps trying and failing any thoughts?
Click to expand...

I always freeze that with Titanium Backup anyway. If you use a custom launcher, no need to worry. If you really wanted that default config then I'm not sure what to tell you because honestly I always wipe that out first thing :)

..I assume you're talking about MobileID?
 
TheBritton said:
I always freeze that with Titanium Backup anyway. If you use a custom launcher, no need to worry. If you really wanted that default config then I'm not sure what to tell you because honestly I always wipe that out first thing :)

..I assume you're talking about MobileID?
Click to expand...
Wasn't sure just what it was. It was MobileID. Problem Solved Thx
 
dm00n said:
flashed this rom about 2 days ago, and everything was working great, but this evening my sms have stopped sending??

However I can recieve sms and send/recieve mms :confused: anyone else run into this or have any ideas?

btw AWESOME work JD and thanks for the help the other day, all you guys are really great I wish i had more I could contribute but im android stoopid lol
Click to expand...

I haven't noticed this issue. I'll keep an eye on it..but maybe you can update profile/prl, reset activation?
 
jdsingle76 said:
Could you be more specific? I have no idea how I can help with this comment. What's your setup? Cwm?
Click to expand...

Yes, I flashed under latest cwm. And my internal storage which has my cwm backups and some app directories won't show up. Only new set of app directories there. But under cwm I can see all my old directories. The new set of directories is under 0/.
And I tried to update Addaway. It failed with error like ' Not enough space on the partition! Try changing the target hosts file in preferece to /data/data/hosts.'
 
infotiger said:
Yes, I flashed under latest cwm. And my internal storage which has my cwm backups and some app directories won't show up. Only new set of app directories there. But under cwm I can see all my old directories. The new set of directories is under 0/.
And I tried to update Addaway. It failed with error like ' no more space under ..\data\data..'
Click to expand...

Your sdcard should be under mnt/sdcard

As for Adaway, open preferences and select "target host file" and select data/data. It should then create a symlink between etc/hosts and data/data

If you continue to have issues perform a full wipe.. format data, system, cache, wipe dalvik cache.. and reinstall the rom.
 
Hm...
I don't have a sd card just internal storage.
mnt/sdcard is point to newly created mount point ( I guess?).
I could not see my old stuff on my internal storage in 4.3. But in recovery mode they show up. Like I said 0/ is my newly created directory.
I have tried to restore 4.12, and everything is fine.
I wiped everything data, cache and dalvik cache, then install the rom, still only sees 0/ directory.
 
infotiger said:
Hm...
I don't have a sd card just internal storage.
mnt/sdcard is point to newly created mount point ( I guess?).
I could not see my old stuff on my internal storage in 4.3. But in recovery mode they show up. Like I said 0/ is my newly created directory.
I have tried to restore 4.12, and everything is fine.
I wiped everything data, cache and dalvik cache, then install the rom, still only sees 0/ directory.
Click to expand...

Samsung titles the internal storage as "sdcard" and your sdcard as "externalsd"

Unfortunately, I'm not really sure how to help you further in this because I am not experiencing this problem :/
 
I first noticed this when I tried 4.4 first.
I went back to 4.1.2 via cmw restore. Everything is fine.
Then after 4.3 rom, it happens again.
Maybe I have to format my internal storage?
 
Honesty I wish I could help. For some reason my SD internal storage has 2 names. "Emulated" and "Sdcard0". I never really had the any storage problems though. :/
 
You must log in or register to reply here.
Back
Top Bottom