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

Root [Virgin Mobile] [VMOBI][ROM][KERNEL] Victorious ROM + VaeVictus OC kernel (Updated 7-30-13)

crshortt said:
Yes, running Victorious for two days now, but have had some issues.

What do you mean by copying them back over? I did try a restore from Titanium Backup which never did anything except keep trying and I had to kill it. What should the permissions be? They seem to match the other apps in the folder. And where can I find the deodexed versions? Is htere a repository of the deodexed apps somewhere.
Click to expand...
FYI- It's not a great idea to restore system apps. ;)

General rule of thumb: anything in /data/app safe to restore, /system/app do not restore
 
Thanks for the advice regarding "/data/app safe to restore, /system/app do not restore". I'll remember that. Things seem to be going better with Victorious now, almost back to normal with the phone setup - though time will tell on the battery life/heat issue. So far, so good today though. Did you post a link to that new kernel yet? If so, do I just download and install from TWRP? Any other steps involved? Clear caches?

I also have a few more questions that occurred to me involving the external to internal sd switch that I would like to be very clear on:

1) As long as I'm running Victorious or updating it, I should never do any wipes other than perhaps caches, correct? Cache wipes and installs - nothing else?

2) Where should I put files I want to flash, like that kernel and the music zip? Still on the actual removable sd card which is now the "new" internal? Or should I put them on the original internal sd which is now the "new", smaller external sd?

I suspect as long as I'm not wiping anything other than caches, it probably doesn't really matter which I use? That makes sense to me, since some phones don't have removable cards and you can still root them and flash ROMs. I guess neither internal nor external sds get wiped when flashing ROMs, only /Device. Is that correct?

3) This is probably more important for me to understand correctly. If I ever want to reflash back to stock for whatever reason, or I want to flash an entirely new ROM, how do I deal with the sd swap? I am thinking I should copy EVERYTHING from BOTH cards and save to my computer before doing anything. I assume going back to stock removes the swap links and puts things back to normal with the small internal sd, and the 32GB removable reverts back to external. But what happens to the data on these cards? Does any of it get wiped during switching to something else? Or does it just end up being in the wrong place, potentially making a big mess to straighten out, depending on what all you have on them?

4) Where would I put the zip for a new ROM before flashing. The actual removable card, which is now internal - or on the original internal, which is now external? Or does it really matter?

5) Unless I am flashing directly to a new ROM that supports an ext4 partition, I assume I need to unlink all user apps from the sd card first, then reformat it back to ext2 or whatever is required by the new ROM?
 
crshortt said:
Thanks for the advice regarding "/data/app safe to restore, /system/app do not restore". I'll remember that. Things seem to be going better with Victorious now, almost back to normal with the phone setup - though time will tell on the battery life/heat issue. So far, so good today though. Did you post a link to that new kernel yet? If so, do I just download and install from TWRP? Any other steps involved? Clear caches?

I also have a few more questions that occurred to me involving the external to internal sd switch that I would like to be very clear on:

1) As long as I'm running Victorious or updating it, I should never do any wipes other than perhaps caches, correct? Cache wipes and installs - nothing else?

2) Where should I put files I want to flash, like that kernel and the music zip? Still on the actual removable sd card which is now the "new" internal? Or should I put them on the original internal sd which is now the "new", smaller external sd?

I suspect as long as I'm not wiping anything other than caches, it probably doesn't really matter which I use? That makes sense to me, since some phones don't have removable cards and you can still root them and flash ROMs. I guess neither internal nor external sds get wiped when flashing ROMs, only /Device. Is that correct?

3) This is probably more important for me to understand correctly. If I ever want to reflash back to stock for whatever reason, or I want to flash an entirely new ROM, how do I deal with the sd swap? I am thinking I should copy EVERYTHING from BOTH cards and save to my computer before doing anything. I assume going back to stock removes the swap links and puts things back to normal with the small internal sd, and the 32GB removable reverts back to external. But what happens to the data on these cards? Does any of it get wiped during switching to something else? Or does it just end up being in the wrong place, potentially making a big mess to straighten out, depending on what all you have on them?

4) Where would I put the zip for a new ROM before flashing. The actual removable card, which is now internal - or on the original internal, which is now external? Or does it really matter?

5) Unless I am flashing directly to a new ROM that supports an ext4 partition, I assume I need to unlink all user apps from the sd card first, then reformat it back to ext2 or whatever is required by the new ROM?
Click to expand...

  1. Correct, no need to wipe anything else, and in fact wiping system will cause your phone to not boot after flashing Victorious.
  2. You can put them where ever you have enough room. TWRP can flash from internal or external sdcards. However, TWRP does not have the cards swapped, so if you put it on internal while booted, it will be on external in TWRP.
  3. Copy everything off your sdcards, then undo all linked apps in Links2Sd, then you will be safe to install another ROM.
  4. see answer to 2
  5. No need to format it back to ext2, as for the rest, see answer to 3
 
Thanks a bunch! I am going to save this entire thread to Evernote for future reference, just in case I ever need it, and it for any reason disappears from this forum.
 
Madbat said:
Camcorder stopped working
Click to expand...
Reboot and try again, if it still doesn't work, let us know which camera app you are using (the stock one of the one I added which is built for Android4.3), which version of Victorious you are on, and which if any version of VaeVictus kernel you have flashed.

Mine's working fine when using the stock camera, but I have experienced issues with the 4.3 camera, rebooting always fixed it.
 
Rebooted. Still says recording failed and closes. Both stock and the one you added. I am on most current victorious and kernal. 0.2.1 victorious and voltages fixed kernal.
 
Is tgis the first time? Because at best smartassv2 is imcomplete. I had it disabled but I guess it got put in....
 
Its the first time I noticed. Haven't tried camcorder in a few days. I just moved to new Orleans from Detroit and I was working in the French quarter today and tried to tak some video and no go.
 
Just checked storage and int 2 ext isn't working. Just noticed super su auto updated when my phone connected to WiFi. Think that could be my problem?
 
Madbat said:
Just checked storage and int 2 ext isn't working. Just noticed super su auto updated when my phone connected to WiFi. Think that could be my problem?
Click to expand...
I got an update for SuperSu, so don't worry about that.

Also, I'm running the Victorious-0.2.1 and VaeVictus-Voltage-Fix, and I just tested my camera, and it's working fine, as well as my storage is swapped fine. So let's try to see what the issue is with yours...

You say your sdcards are no longer swapped? That could be a symptom of your overall problem. What do you have in /system/ect/int.d and what does it say in /system/etc/install-recovery.sh?
 
1375133345907.jpg
 
Could be that SuperSUDaemon, I don't have it. What version of SU are you running? I'm running Chainfire SuperSU Pro, not sure it the pro version has a different upgrade mechanism.

Could you post the contents of that 99SuperSuDaemon?

BTW- you don't have SuperSU linked to your sdcard via Links2Sd do you?
 
I didnt do any links 2 sd at all. I only have a 4gb card right now so it would be kinda pointless. When supersu updated it opened in my pocket. (At work) when I looked at it was asking to update binaries so I did. That may have been the mistake. I just restored from my backup in recovery. Now im gonna flash victorious again.
 
Madbat said:
I didnt do any links 2 sd at all. I only have a 4gb card right now so it would be kinda pointless. When supersu updated it opened in my pocket. (At work) when I looked at it was asking to update binaries so I did. That may have been the mistake. I just restored from my backup in recovery. Now im gonna flash victorious again.
Click to expand...
Strange, I let it update my binary by the normal mode, and it worked fine (not TWRP). Let us know how things go.
 
On my og evo supersu is giving me errors. This may be a supersu error. su also killed my kyocera hydro yesterday after an uodate binary caused it to stall on boot. :(
 
aha. i did twrp mode. wont make that mistake again. I think it recommended it and i was busy at work and did it without thinking. note to self.... dont do this stuff when youre busy!
 
You must log in or register to reply here.
Back
Top Bottom