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

Root [Boost Mobile] Rooted "A" or "B" what's the difference??

droidagnostic

droidagnostic

Newbie
Rooted "A"
Odin NDC
Odin Philz
Root with Philz and SU.

Rooted "B"
Odin NDC
Odin Philz
Flash Stock 4.4.2 Odexed

Are these 2 different paths to the same place?

Either way u wind up with a rooted odexed stock kitkat. Right?

If not what's the difference in the end result?

TIA
 
Basically the only difference is you have a choice between deodexed or odexed. Which path you choose to travel ends with the same outcome. A rooted S3 with Philz recovery.

Personally, I didn't even bother rooting the stock ROM. I had a custom ROM already on my sd card and flashed it as soon as I had Philz. If you're gonna use an S3, why not run a ROM that releases the phone's full potential. The stock ROM doesn't offer that. ;)

Food for thought. :)
 
wetbiker7 thanks for verifying that.

I'm having some strange FC's and some other issues on jdsingle76's deodexed rom, so i went backwards to see if i could figure out the source.

Stock email & stock browser both FC with "stopped working" errors right after launching them.

TiBU and MyBackUp Pro both giving me "can't write to sd card" errors when trying to restore stuff like call logs/sms. That error makes no sense to me for the internal card which is where they're trying to write.

Still getting the FC's though even with odining the stock tar, which should be as clean an install as i can get. That fixed the card read problem though.

"...PHREAKAY"
 
droidagnostic said:
wetbiker7 thanks for verifying that.

I'm having some strange FC's and some other issues on jdsingle76's deodexed rom, so i went backwards to see if i could figure out the source.

Stock email & stock browser both FC with "stopped working" errors right after launching them.

TiBU and MyBackUp Pro both giving me "can't write to sd card" errors when trying to restore stuff like call logs/sms. That error makes no sense to me for the internal card which is where they're trying to write.

Still getting the FC's though even with odining the stock tar, which should be as clean an install as i can get. That fixed the card read problem though.

"...PHREAKAY"
Click to expand...

I highly recommend either Wicked-X or Conquest. Both are amazing ROMS and are stable.

One reminder. If you're having force close issues do a factory reset, wipe cache, and then go to ADVANCED and do a Dalvik wipe. That should take care of the force closes. These steps should also be taken before flashing a new ROM. It ensures there is no leftover data that can interfere with the new ROM.

If I were you I would try the 2 TouchWiz ROMS I recommend above. Both come with the KT 747 custom kernel too.

If you have any questions just let me know.
 
wetbiker7 thanks for the info.

I was trying to get a fresh install of Wicked-X 7.3 working when the issues were first observed so i backtracked numerous wiping steps all the way to stock tar trying to ID the problem. I'm using latest Philz which provides wipe for new ROM and factory reset functionality plus all the wiping steps you mentioned and i used them all.

I think I have ID'd the problem but not sure i can totally prove it yet. I am currently pointing the finger at Exposed Installer or it's latest update (2.6.1).

I had installed that Exposed update in my first install of Wicked and then, because I liked some of the options provided by Wanam Exposed I added the Exposed Installer to each of my backtrack installs. That's why I could not get rid of the problem.

So I went back and installed Wicked 2nd time again yesterday everything working great (YAY!!!). Got all account info back in and played with it for a while everything still working great (YAY!!!). Went and downloaded update and installed in Exposed Installer went to use the browser and got FC, Email same thing (Words i cant post!!!).

Froze Exposed with TiBU and Internet and Email apps both working again.

I couldn't remember if I had Exposed working with v2.6 or started at v2.6.1 so I tried to uninstall Exposed 2.61 update to step back to 2.6. Currently looks like Exposed is not installed at all but some of the Wanam features I enabled seem to still be working...:confused::confused:

If i cannot uninstall/reinstall Exposed and get it working I will probably have to step through the Wicked install again and take better notes to pinpoint the fail point.

It's my dd and it it's working now so I'm not sure how quick I'll be to play with it some more.
 
droidagnostic said:
wetbiker7 thanks for the info.

I was trying to get a fresh install of Wicked-X 7.3 working when the issues were first observed so i backtracked numerous wiping steps all the way to stock tar trying to ID the problem. I'm using latest Philz which provides wipe for new ROM and factory reset functionality plus all the wiping steps you mentioned and i used them all.

I think I have ID'd the problem but not sure i can totally prove it yet. I am currently pointing the finger at Exposed Installer or it's latest update (2.6.1).

I had installed that Exposed update in my first install of Wicked and then, because I liked some of the options provided by Wanam Exposed I added the Exposed Installer to each of my backtrack installs. That's why I could not get rid of the problem.

So I went back and installed Wicked 2nd time again yesterday everything working great (YAY!!!). Got all account info back in and played with it for a while everything still working great (YAY!!!). Went and downloaded update and installed in Exposed Installer went to use the browser and got FC, Email same thing (Words i cant post!!!).

Froze Exposed with TiBU and Internet and Email apps both working again.

I couldn't remember if I had Exposed working with v2.6 or started at v2.6.1 so I tried to uninstall Exposed 2.61 update to step back to 2.6. Currently looks like Exposed is not installed at all but some of the Wanam features I enabled seem to still be working...:confused::confused:

If i cannot uninstall/reinstall Exposed and get it working I will probably have to step through the Wicked install again and take better notes to pinpoint the fail point.

It's my dd and it it's working now so I'm not sure how quick I'll be to play with it some more.
Click to expand...

OK. You do know the current version of Wicked-X comes with the Xposed installer and some modules, right? All you have to do is go into your app drawer, download the update and activate it by rebooting. Once activated you go into the modules, check them and do a soft reboot which is located under framework in Xposed. I never do a complete reboot when activating a module, just the soft reboot. Also, many of the modules in Xposed are not for the TouchWiz ROM. You have to read through the description carefully to make sure they're for TouchWiz.

If you have any questions regarding a module just let me know. I'll be more than happy to let you know if it's TouchWiz compatible. :)

Edit:

One more thing. You need to make sure that you grant Xposed root privileges when prompted. ;)
 
Yeah Exposed Installer app is installed in Wicked but u still need to flash the framework to activate it.

Soon as i do that i started getting issues with the other included apps Internet and Email.

Without the framework i don't think any of the modules are active. I haven't activated any modules yet and haven't loaded any other modules beyond the one's included in Wicked.

Bilgerryan built some of the Wanam Exposed features (like 4 way boot) into the v7.3 ROM that's why i thought the modules were active.
 
I have some info that might help both of you with email. I use Gmail with all the ROMS I run. With Wicked-X and Conquest my Gmail app that comes with the ROM will not send mail. To get it working I use Titanium Backup to wipe the Gmail app data and then uninstall it. I then go into Philz and wipe the cache and Dalvik cache and reboot. Once I've booted the phone back up I will download the Gmail app from the Play store and let it install. It works perfectly after following these steps.

You also need to go into the phone's settings and go to Google. Make sure the Gmail app has a check beside it and is syncing properly.

I've been having to do this with the Gmail app for awhile now. For some reason it just will not send an email when the app is installed with a ROM. It recieves fine though.

Hopefully this helps. :)
 
wetbiker7 said:
I have some info that might help both of you with email.
Click to expand...

It's just you and me in this thread so far... :D

But seriously thanks for the info. I have not encountered this cause i don't use Gmail. It the first app i dump out when i install a new system.

I have an Exchange account so i just run all my email through the email client cause then I'm just checking a single point for everything.
 
droidagnostic said:
It's just you and me in this thread so far... :D

But seriously thanks for the info. I have not encountered this cause i don't use Gmail. It the first app i dump out when i install a new system.

I have an Exchange account so i just run all my email through the email client cause then I'm just checking a single point for everything.
Click to expand...

LOL! I could've sworn another member had joined our discussion in this thread. Thanks :D
 
You must log in or register to reply here.
Back
Top Bottom