As some have noticed once you move onto the LK8 firmware and try to revert back to previous firmware versions you get Hands Free Activation or Chameleon Force Close errors upon every reboot.
This is what I have done to fix these errors and be able to go back to older firmware (pre LK8) if needed.
Not sure if this "fix" works beyond LK8 firmware as i'm not playing the flashing game any longer...The Note 2 works fine as is (MA7).
(Standard YMMV and i'm not responsible for trashing your phone)
No root or custom recovery needed.
1.) Install older firmware, in my case, I used the original LJ1 firmware provided by Viperboy found here.
2.) Once the firmware is installed on first boot it will give you the HFA & Chameleon errors, and that's fine and its where we will put the stop to it.
3.) Transfer the Chameleon.apk file below to your phone (Extracted out of the LK8 update) and install (overwrite) the existing one on your phone.
4.) You'll have to dial ##72786# to activate your phone, let it go through the motions (you may need your MSL, although I didn't need to enter it).
5.) Once the phone reboots it goes though HFA, PRL & Profile update, it will reboot and then no more issues (hopefully).
I have rebooted the phone over a dozen times with no issues, and the phone updated itself from LJ1 to LJC and again to MA7, no problem.
Please let us know if this works for you, or any suggestions to add to this..... Merry Christmas.
** As an update this issue is being investigated further on in this thread with the hopes it will be fixed in future firmwares.
You sir, are awesome. 'Nuff said.
(I don't personally have the issues anymore, since I was lucky enough to get a new replacement, but others have not. So this is perfect. )
Sent from my calculator watch.
Actually last night I went to a restaurant that we go to all the time that has free WiFi and with the LK8 firmware I wasn't able to connect (completely open, no passwords) which made me try to figure out how to fix this... I'm sticking to LJC until the next confirmed to completely work update arrives. And I get so much from this site i'm happy that I can contribute something no matter how small. I hope it works for others as well. Thank you and happy holidays.
Worked for me installed and rebooted with no issue ... thanks for this
Sent from my SPH-L900 using xda app-developers app
Awesome. Thank you for this. I was also fortunate enough to get sprint to replace my phone but this will be helpful to all and even myself when I break my phone again!
Sent from my SPH-L900 using Tapatalk 2
Thanks! Worked perfect!
Worked but can't do update profile or prl now
Sent from my SPH-L900 using xda premium
I just tried and both work fine.
Sweet it worked.
I found the fix for it!!!
Hey all, I hate to hijack the thread, but I found the actual fix for this.
flash the stock recovery, or stock rooted rom .....YOU HAVE TO BE ROOTED AND ON STOCK RECOVERY
use root explorer
mount r/w
when you open root explorer, scroll up to carrier
open /carrier
delete .chameleon.hash
delete chameleon.xml
back out of root explorer
go to dialer and ##72786#
the phone will reboot, do hands free, and should work....it will reboot again and check for firmware update, etc.....all updates worked for me.
Hit the freaking thanks button
once i follow your procedure can i go back to LK8 and LK8 won't give anymore errors? I am on LK8 now but my activation not working and i think that causes my inet not to work
shiftr182 said:
Hey all, I hate to hijack the thread, but I found the actual fix for this.
flash the stock recovery, or stock rooted rom .....YOU HAVE TO BE ROOTED AND ON STOCK RECOVERY
use root explorer
mount r/w
when you open root explorer, scroll up to carrier
open /carrier
delete .chameleon.hash
delete chameleon.xml
back out of root explorer
go to dialer and ##72786#
the phone will reboot, do hands free, and should work....it will reboot again and check for firmware update, etc.....all updates worked for me.
Hit the freaking thanks button
Click to expand...
Click to collapse
very interesting! Im curious, what happens if you re-flash a stock rom. (Or actually, any rom) do you have to fix again?
Sent from my calculator watch.
jameslee2 said:
once i follow your procedure can i go back to LK8 and LK8 won't give anymore errors? I am on LK8 now but my activation not working and i think that causes my inet not to work
Click to expand...
Click to collapse
Just remove the files and ##72786# should work. Im on LK8 too, but now handsfree works and I can update my prl/profile.
shiftr182 said:
Hey all, I hate to hijack the thread, but I found the actual fix for this.
flash the stock recovery, or stock rooted rom .....YOU HAVE TO BE ROOTED AND ON STOCK RECOVERY
use root explorer
mount r/w
when you open root explorer, scroll up to carrier
open /carrier
delete .chameleon.hash
delete chameleon.xml
back out of root explorer
go to dialer and ##72786#
the phone will reboot, do hands free, and should work....it will reboot again and check for firmware update, etc.....all updates worked for me.
Hit the freaking thanks button
Click to expand...
Click to collapse
I wonder if deleting the .hash and .xml while still on LK8 and then odin back to stock would stop the errors once the odin was done?
Anyone on LK8 willing to try?
Sent from my SPH-L900 using xda app-developers app
shiftr182 said:
Hey all, I hate to hijack the thread, but I found the actual fix for this.
flash the stock recovery, or stock rooted rom .....YOU HAVE TO BE ROOTED AND ON STOCK RECOVERY
use root explorer
mount r/w
when you open root explorer, scroll up to carrier
open /carrier
delete .chameleon.hash
delete chameleon.xml
back out of root explorer
go to dialer and ##72786#
the phone will reboot, do hands free, and should work....it will reboot again and check for firmware update, etc.....all updates worked for me.
Hit the freaking thanks button
Click to expand...
Click to collapse
Which stock Rom and do you have link stock recovery??
Sent from my MASSIVE Galaxy Note® II...*
shiftr182 said:
Hey all, I hate to hijack the thread, but I found the actual fix for this.
flash the stock recovery, or stock rooted rom .....YOU HAVE TO BE ROOTED AND ON STOCK RECOVERY
use root explorer
mount r/w
when you open root explorer, scroll up to carrier
open /carrier
delete .chameleon.hash
delete chameleon.xml
back out of root explorer
go to dialer and ##72786#
the phone will reboot, do hands free, and should work....it will reboot again and check for firmware update, etc.....all updates worked for me.
Hit the freaking thanks button
Click to expand...
Click to collapse
Doesn't fully work. I went back to unrooted LJC and rerooted(without adding the custom recovery) and deleted the 2 files. It DOES stop the Chameleon FC but it still wants to do the hands free activation every reboot. I can't stop that from occuring with the above method.
**EDIT**
The method in the original post does work but every time you wanna load a new ROM, you gotta do this all over again.
Someone needs to find a way to fix this right.
Chuck_IV said:
Doesn't fully work. I went back to unrooted LJC and rerooted(without adding the custom recovery) and deleted the 2 files. It DOES stop the Chameleon FC but it still wants to do the hands free activation every reboot. I can't stop that from occuring with the above method.
**EDIT**
The method in the original post does work but every time you wanna load a new ROM, you gotta do this all over again.
Someone needs to find a way to fix this right.
Click to expand...
Click to collapse
I posted what worked for me. I had chameleon has stopped, and hands free activation on every boot. My phone wouldnt update profile, and would never activate. I got creative, and noticed that those two files hadnt changed since the day I got my phone activated, so I decided to delete them and see if that changed anything. My phone went hands free and actually worked, rebooted and checked for firmware, then updated the profile. I can update the profile once again, and no hands free, or chameleon errors anymore. Feel free to try finding your own solution.
Chuck_IV said:
The method in the original post does work but every time you wanna load a new ROM, you gotta do this all over again.
Someone needs to find a way to fix this right.
Click to expand...
Click to collapse
Although I did go from LJ1 to LJC without any issues, no reinstalls, so custom roms? And yeah I would agree but at least we got a workaround.
dannys.ser said:
Which stock Rom and do you have link stock recovery??
Sent from my MASSIVE Galaxy Note® II...*
Click to expand...
Click to collapse
Hi i did what you say but the same thing happens during hands free activation it just says please wait and it still gives error 1500
---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------
I am currently on LK8 using H2o rom. And i Noticed first instruction was:
flash the stock recovery, or stock rooted rom .....YOU HAVE TO BE ROOTED AND ON STOCK RECOVERY
How do i do the above? Where do i download the files? And do i go back to the old version ? if so won' this lk8 rom won't work?
bookmarked!
Related
Hey guys, first time Android user here.
I got my phone on release day...a few weeks later I decided to root it. Went very smoothly with no issues, then I accepted an update and lost the root so now when I try to root again I always end up with all kinds of stop errors. Anyone have any thoughts on why that might be? Ive tried restoring my phone to factory settings and rooting but it makes no difference, always blows up with error after error.
Saying you reset to factory settings, did you ODIN back to stock?
jeeper11 said:
Saying you reset to factory settings, did you ODIN back to stock?
Click to expand...
Click to collapse
No sir, just used the reset tool built into the phone....are you saying I need to find the stock firmware and load it through ODIN first?
I would strongly suggest using the ODIN method back to to stock, and then start your rooting process again
Odin to stock, rooted LG1
Dl OTA root keeper from market, using it to back up root
Let the ota update do its thing
Restore root with root keeper
mrhaley30705 said:
Odin to stock, rooted LG1
Dl OTA root keeper from market, using it to back up root
Let the ota update do its thing
Restore root with root keeper
Click to expand...
Click to collapse
Is this the name of the correct file that will work? root69_ATT_I747UCALG1.tar
Ive used this before and its one of the ones that caused my phone to pop up with stop errors.
That is a pre-rooted firmware.you need one of the ones from here http://forum.xda-developers.com/showthread.php?t=1968625 to go completely back to stock, just make ure you grab the one for your provider
jeeper11 said:
That is a pre-rooted firmware.you need one of the ones from here http://forum.xda-developers.com/showthread.php?t=1968625 to go completely back to stock, just make ure you grab the one for your provider
Click to expand...
Click to collapse
Ok thanks for the help so far. Im downloading the file now but the next question is once I install this and the phone is fully stock which file should I use to root?
If you are AT&T THEN use the one you mentioned above, if not use the appropriate one for you,
jeeper11 said:
If you are AT&T THEN use the one you mentioned above, if not use the appropriate one for you,
Click to expand...
Click to collapse
Thanks guys. Will try it now.
Lato9905 said:
Thanks guys. Will try it now.
Click to expand...
Click to collapse
Ok just finished step number one (flashing stock rom) and its the same outcome that ive been getting. As soon as the phone comes on this error pops up unfortunately the process android.process.acore has stopped and it just pops up every ten seconds.
Try clearing you contacts cache, under application manager.
That helped me when I got this error. Never got it again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
scav1180 said:
Try clearing you contacts cache, under application manager.
That helped me when I got this error. Never got it again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yep you are correct. Just did it and fixed my issues, now rooted again and working. Thanks for the help gentlemen.
Dang.... Wish this conversation was 2 days ago. I had the same exact error after trying to get root, I had to pull battery and do factory reset from stock recovery then flash stock with root and flash the OTA to end up where I wanted to be! . Oh well we live and learn right!
Sent from my SAMSUNG-SGH-I747 using xda premium
The official OTA link is http://d-h.st/3j0.
The update script checks for all the original .apks, .odexs, etc. Update fails when any of the original files are missing.
Sorry..not familiar with Moto..Gonna update wife's phone. What's the next step... Rename to update.zip and place in root of sdcard? Phone is stock not rooted.
Sent from my SCH-I535 using Tapatalk 2
caifan said:
Sorry..not familiar with Moto..Gonna update wife's phone. What's the next step... Rename to update.zip and place in root of sdcard? Phone is stock not rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Correct.
Rename "Update.zip"
Place in root of sdcard "/mnt/external1/"
Reboot into recovery
-Shutdown
-Press Volume-Up and Power simultaneously until Motorola logo appears
-Press Volume-Up and Volume-Down simultaneously when you see the android with the ! from his open chest
-Scroll down to and select "Apply Update from External Storage"
-Scroll to and select "Update.zip"
-Grab a beer and wait
ThunderThief said:
Correct.
Rename "Update.zip"
Place in root of sdcard "/mnt/external1/"
Reboot into recovery
-Shutdown
-Press Volume-Up and Power simultaneously until Motorola logo appears
-Press Volume-Up and Volume-Down simultaneously when you see the android with the ! from his open chest
-Scroll down to and select "Apply Update from External Storage"
-Scroll to and select "Update.zip"
-Grab a beer and wait
Click to expand...
Click to collapse
dont even have to rename. just drop on sd and apple update. thanks for the upload OP.
Doesn't work if you are on the leak. Complains about build.prop not matching. Haven't tried changing it though...
Sent from my XT907 using xda app-developers app
So this is the official jelly bean update without any bugs or anything?
Sent from my XT907 using Tapatalk 2
sototallycarl said:
Doesn't work if you are on the leak. Complains about build.prop not matching. Haven't tried changing it though...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Don't try. You got to sbf.
Sent from my XT907 using Tapatalk 2
Edit: Nope, no need for SBF on a Safestrap phone, just go back into Safestrap and uninstall the recovery.
I was getting a Status 7 failure from logwrapper but it does not require SBF to fix. Hooray!
Paramemetic said:
Edit: Nope, no need for SBF on a Safestrap phone, just go back into Safestrap and uninstall the recovery.
I was getting a Status 7 failure from logwrapper but it does not require SBF to fix. Hooray!
Click to expand...
Click to collapse
Did you uninstall any bloat apps? If so, did you restore a backup or is everything just working for you? I am rooted on JB leak and uninstalled many bloat apps and just trying to figure out what my next step is here. And what does SBF stand for? Sorry for the ignorance, never owned a locked bootloader phone before so this is all new lol.
00McD00 said:
Did you uninstall any bloat apps? If so, did you restore a backup or is everything just working for you? I am rooted on JB leak and uninstalled many bloat apps and just trying to figure out what my next step is here. And what does SBF stand for? Sorry for the ignorance, never owned a locked bootloader phone before so this is all new lol.
Click to expand...
Click to collapse
I only disabled bloat apps, didn't uninstall any. It checks to make sure all system apps are present (but not enabled). Your only option if you've uninstalled bloat apps using something like TiBu and if you've installed the JB leak is to revert to ICS factory image. SBF is "system boot file."
You're going to need to grab the ICS fastboot file from the dev forum and install it before either the OTA or this will work.
Root on its own is not a problem but if you have changed system apps (bloat is all "system") you'll need to do that.
If you installed safestrap that's fine, but you have to uninstall the recovery using the app before this will work because it checks the boot sequence.
Is the official update going to be worth it if we already have the leaked jellybean? All the sites I've read provide the same information regarding the new features for the update (all the same as the jellybean leak). If anyone has updated to the official jellybean from the leaked can you provide any information regarding the differences between the two
Confirmed working, and according to the Verizon PDF this official version has improved 4g reception as well as less drops on signal, improved WiFi and Bluetooth its running fine for me, going to try root and safe strap now
---------- Post added at 06:18 AM ---------- Previous post was at 06:07 AM ----------
Root not working which means safe strap is not working.... reverting back too old jb leak for the time being
Installed and working great.
OTARootkeeper backed up root then temp uninstalled root. Booted into stock recovery, flashed OTA from sd card, booted up, restored root, made sure entitlement_check was still set to "0"....tested stock hotspot app and works great.
Thanks OP for providing the link.
Can't wait for a non Verizon version of this. The RAZR M has to be my favorite android phone so far - great form factor and great hardware... just being stuck on ice cream sandwich is a bit **** but I'm prepared to wait
Sent from my XT905 using xda app-developers app
jarzy00 said:
So this is the official jelly bean update without any bugs or anything?
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Yes, this is Verizon's official OTA. I haven't been running long so I will not comment much on stability. For the first few minutes one system app continuously force closed and restarted and the notification bar / soft keys disappeared. A reboot solved those problems.
got556 said:
Installed and working great.
OTARootkeeper backed up root then temp uninstalled root. Booted into stock recovery, flashed OTA from sd card, booted up, restored root, made sure entitlement_check was still set to "0"....tested stock hotspot app and works great.
Thanks OP for providing the link.
Click to expand...
Click to collapse
The SU binaries were deleted during my install, despite OTARootkeeper. However superuser responded to app requests giving the appearance of root.
And you are welcome.
ThunderThief said:
The SU binaries were deleted during my install, despite OTARootkeeper. However superuser responded to app requests giving the appearance of root.
And you are welcome.
Click to expand...
Click to collapse
Root checker stated I was rooted. May have to check again to make sure the binaries are still there. Will mess w/ her (g/f's) phone when she's done using it.
Just went back to Jellywiz from Paranoid on my S3 w/ some new radios we got leaked, so been busy setting all my crap back up.
Really hoping we can get Pimp My Rom on the M soon.
I also had no issues re-rooting with OTA Rootkeeper after manual update. I think I'm enjoying project butter the most!
If I install this like other people did with the leaked version, will I have any issues if there is ever another update?
techfellow said:
If I install this like other people did with the leaked version, will I have any issues if there is ever another update?
Click to expand...
Click to collapse
I don't think that will be a problem.
Got my JB update today, I was rooted stock before, and the install went fine without any problems.
After the update, my Quadrant score went down dramatically, from 4500 (stock rooted ICS) to 3700 JB.
So I did a factory reset and all hell breaks loose. I dont seem to have 4G anymore, although the 4G signs is showing on the top. Play store, Maps, Navigations, etc wont load (maybe since I dont internet it wont load?). After noticing all these problems, I did another factory reset.
And now I cant even sign in to Google.
Seriously, I never thought an OTA upgrade would mess up my phone.
Can anyone shine a light my way?
Thanks.
I had a similar problem with the OTA LH2 on a rooted stock ICS , I couldn't connect WIFI, a lot of apps weren't working properly. After 4-5 factory resets, still no go. My only option was to use ODIN and reinstall the complete firmware that way, and all was back to normal. Im pretty sure this happened because of OTA over a rooted device. Worth a try I think.. Good luck.
Odin the update like above then enter recovery and wipe again, sucks you got a messed up download.
Sent from my SGH-T999 using xda premium
Roamin64 said:
I had a similar problem with the OTA LH2 on a rooted stock ICS , I couldn't connect WIFI, a lot of apps weren't working properly. After 4-5 factory resets, still no go. My only option was to use ODIN and reinstall the complete firmware that way, and all was back to normal. Im pretty sure this happened because of OTA over a rooted device. Worth a try I think.. Good luck.
Click to expand...
Click to collapse
Thanks! Yup, wifi wont work, 4G wont work. I think, like you, ODIN is my only option at this point.
Should I use this: http://forum.xda-developers.com/showthread.php?t=1991255
So how do I odin that zip file to my phone?
arthaz28 said:
Thanks! Yup, wifi wont work, 4G wont work. I think, like you, ODIN is my only option at this point.
Should I use this: http://forum.xda-developers.com/showthread.php?t=1991255
So how do I odin that zip file to my phone?
Click to expand...
Click to collapse
Unzip the odin file, turn the device off, holding volume down, home button and then the power button, the phone should go into download mode, start odin up, connect the phone via usb, hit the pda option, then browse to the file you downloaded and unzipped, the md5 file should be the only file showing up, select it and hit start.
Phone will auto restart upon completion.
Edit: Don't use that file, use this: https://hotfile.com/get/179444770/50a3b770/48ddf5f/T999UVDLJA_T999TMBDLJA_TMB.zip
arthaz28 said:
Got my JB update today, I was rooted stock before, and the install went fine without any problems.
After the update, my Quadrant score went down dramatically, from 4500 (stock rooted ICS) to 3700 JB.
So I did a factory reset and all hell breaks loose. I dont seem to have 4G anymore, although the 4G signs is showing on the top. Play store, Maps, Navigations, etc wont load (maybe since I dont internet it wont load?). After noticing all these problems, I did another factory reset.
And now I cant even sign in to Google.
Seriously, I never thought an OTA upgrade would mess up my phone.
Can anyone shine a light my way?
Thanks.
Click to expand...
Click to collapse
I was stock rooted. Updated. Cwm said it failed but it gave me the option to flash untrusted zip. Flashed. Works flaws less. No problems
Sent from my SGH-T999 using xda app-developers app
Dark Nightmare said:
Unzip the odin file, turn the device off, holding volume down, home button and then the power button, the phone should go into download mode, start odin up, connect the phone via usb, hit the pda option, then browse to the file you downloaded and unzipped, the md5 file should be the only file showing up, select it and hit start.
Phone will auto restart upon completion.
Edit: Don't use that file, use this: https://hotfile.com/get/179444770/50a3b770/48ddf5f/T999UVDLJA_T999TMBDLJA_TMB.zip
Click to expand...
Click to collapse
Welcome dark!
Im a lil salty myself. I love the update except i get a little screen flicker when i scroll up and down sometimes (disabling hw overlay aka project butter fixes) and the call quality kind of downgraded slightly. I love everything else so far.
Mobile Odin is your friend to the OP. Took me 10 min or so
Sent from my
Stock Jellybean SGS3
Perfect example of why I always say to do firmware upgrades either OTA (if 100% stock unrooted) or Odin.
Sent from my SGH-T999 using Tapatalk 2
Dark Nightmare said:
Unzip the odin file, turn the device off, holding volume down, home button and then the power button, the phone should go into download mode, start odin up, connect the phone via usb, hit the pda option, then browse to the file you downloaded and unzipped, the md5 file should be the only file showing up, select it and hit start.
Phone will auto restart upon completion.
Edit: Don't use that file, use this: https://hotfile.com/get/179444770/50a3b770/48ddf5f/T999UVDLJA_T999TMBDLJA_TMB.zip
Click to expand...
Click to collapse
Is that file the stock rooted JB OTA? I downloaded the root66 stock rooted OTA: http://www.androidfilehost.com/?fid=9390169635556426451
But the file that I downloaded has *.7z thus unrecognizable by ODIN's PDA option.
I will download your file now and give it a shot.
Thanks!
arthaz28 said:
Is that file the stock rooted JB OTA? I downloaded the root66 stock rooted OTA: http://www.androidfilehost.com/?fid=9390169635556426451
But the file that I downloaded has *.7z thus unrecognizable by ODIN's PDA option.
I will download your file now and give it a shot.
Thanks!
Click to expand...
Click to collapse
Thats 7zip. Download from 7zip.org and use to extract.
If you want thst stock unrooted on, get it from my fw thread. The download should be a LOT faster than using hotfile
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Thats 7zip. Download from 7zip.org and use to extract.
If you want thst stock unrooted on, get it from my fw thread. The download should be a LOT faster than using hotfile
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok, I downloaded the *.7z file, extracted, flash it through ODIN and get my wifi to work, and my 4g to work for a brief moment.
Then my 4g stopped working again, and i notice that when i go to Status option in the setting, my device is listed as Modified, whereas for a few minutes after i flashed, it was listed as Normal.
When my device was listed as Normal, my 4g would work, then it switched itself to Modified and it seems that Samsung or Tmo locked my device.
Ugh, I am so bummed!
Modified ststus is jusy becsuse your rooted. It goes away if you revert.
It shouldnt have any bearing on your data though.
What does it say for baseband, network type, and is your imei there?
Sent from my SGH-T999 using xda app-developers app
I am on stock ICS (Android version 4.0.4)
My baseband version is T999UVLEM
I rooted my phone when I got it at launch, and then put off all the incremental updates until official JB was released for Tmobile. Now that it's released, I'd like to update to. What is the proper way for me to do this? Flash through odin I assume? Will I still be able to keep my root or root the device after JB is installed?
Thanks in advance, I just don't want a nightmare situation like the OP if I flash incorrectly
Darmokk said:
I am on stock ICS (Android version 4.0.4)
My baseband version is T999UVLEM
I rooted my phone when I got it at launch, and then put off all the incremental updates until official JB was released for Tmobile. Now that it's released, I'd like to update to. What is the proper way for me to do this? Flash through odin I assume? Will I still be able to keep my root or root the device after JB is installed?
Thanks in advance, I just don't want a nightmare situation like the OP if I flash incorrectly
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1949687
Sent from my
Stock Jellybean SGS3
GalaxyS3Guy said:
http://forum.xda-developers.com/showthread.php?t=1949687
Sent from my
Stock Jellybean SGS3
Click to expand...
Click to collapse
Thanks for that, it pretty much covers all of my questions.
One that I'm still wondering about though, is can I go straight from rooted UVALEM to the latest JB firmware? Or do I flash back to stock UVALEM and THEN flash JB? Or do I need to flash each incremental update before finally finishing off with JB?
Darmokk said:
Thanks for that, it pretty much covers all of my questions.
One that I'm still wondering about though, is can I go straight from rooted UVALEM to the latest JB firmware? Or do I flash back to stock UVALEM and THEN flash JB? Or do I need to flash each incremental update before finally finishing off with JB?
Click to expand...
Click to collapse
Yup! Just Odin flash the full firmware file, not the ota. Use the root66 version to stay rooted.
Sent from my SGH-T999 using xda app-developers app
GalaxyS3Guy said:
http://forum.xda-developers.com/showthread.php?t=1949687
Sent from my
Stock Jellybean SGS3
Click to expand...
Click to collapse
Thanks GG, been a while dude, I've no issues so far with the update, everything is smooth, my playstore acted weird for a bit, then after adding my accounts, it worked fine, weird. Otherwise, I gotta admit I'm loving it.
DocHoliday77 said:
Yup! Just Odin flash the full firmware file, not the ota. Use the root66 version to stay rooted.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Or they can use the regular firmware file, flash it via mobile odin which roots it for ya, without the hassle and is much faster, I used it so I can say clearly it did an excellent job.
Note: if hotfile is too slow and there are no alternatives, I can upload the full firmware odin file to dev-host for everyone.
Dark Nightmare said:
Thanks GG, been a while dude, I've no issues so far with the update, everything is smooth, my playstore acted weird for a bit, then after adding my accounts, it worked fine, weird. Otherwise, I gotta admit I'm loving it.
Or they can use the regular firmware file, flash it via mobile odin which roots it for ya, without the hassle and is much faster, I used it so I can say clearly it did an excellent job.
Note: if hotfile is too slow and there are no alternatives, I can upload the full firmware odin file to dev-host for everyone.
Click to expand...
Click to collapse
I always use mobile odin pro. My favorite app! But not everyone wants to pay for it and the free version doesnt have EverRoot.
I usually recommend it, but too many people were updating today so I wanted to stick with what everyone should be willing to do!
Ive already got the stock fw hosted from my account if that helps.
Was one of the first things I did after release. Check the firmware thread in my sig for that Plus more!
Sent from my SGH-T999 using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
DocHoliday77 said:
Modified ststus is jusy becsuse your rooted. It goes away if you revert.
It shouldnt have any bearing on your data though.
What does it say for baseband, network type, and is your imei there?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It turns out there was a 4g blackout around my area last night. But I did odin'ed your root66 TMO JB version and it's awesome! I was wondering if you're gonna make the same version with UMS included?
Thanks!
Whats going on guys? I'm running into a mindboggling issue with my fiance's T-mobile Galaxy S2. I'm going to run down exactly what happened, and if anyone has any suggestions or insight... please share it with me.
Ok first things first, I installed the firmware upgrade through Kies to 4.1.2 the same exact way I did on my S2 just a few minutes before... Except this time, as soon as the phone powered up I got the com.google.process.gapps not working error. I did a little research on it first through here and the most common thing i found was to enable download manger... HOWEVER, under her apps list there isnt any form of a download manager on it. So i checked my phone, just to see if it was a firmware problem, but my phone has DOWNLOADS, as Well as DOWNLOAD MANAGER. There was no way for me to download one through the Google Play on her phone because the phone force closes Google Play as soon as you press it.
From there I downloaded all of the drivers, and odin, so that i could just upload the old 2.3.6 stock rom back on the phone... That worked correctly as well, but as soon as the "Press the Andriod" to setup appeared, I encountered the same error message as before. "(com.google.process.gapps not working) as well as setup wizard not working, and now its not allowing me to set the phone up at all. Does anyone have any insight on this? All help would be greatly appreciated.. Thanks!!!
******edit********
I've figured out where i went wrong... I didn't move su-3.0.5-efgh-signed.zip or Superuser-3.0.7-efghi-signed.zip onto the internal memory before I flashed the 2.3.6 stock rom through odin... Now that i cant get past the "TOUCH THE ANDRIOD TO START SETUP" screen... is there any way i can put it onto the internal memory?
THEREHEGO said:
Whats going on guys? I'm running into a mindboggling issue with my fiance's T-mobile Galaxy S2. I'm going to run down exactly what happened, and if anyone has any suggestions or insight... please share it with me.
Ok first things first, I installed the firmware upgrade through Kies to 4.1.2 the same exact way I did on my S2 just a few minutes before... Except this time, as soon as the phone powered up I got the com.google.process.gapps not working error. I did a little research on it first through here and the most common thing i found was to enable download manger... HOWEVER, under her apps list there isnt any form of a download manager on it. So i checked my phone, just to see if it was a firmware problem, but my phone has DOWNLOADS, as Well as DOWNLOAD MANAGER. There was no way for me to download one through the Google Play on her phone because the phone force closes Google Play as soon as you press it.
From there I downloaded all of the drivers, and odin, so that i could just upload the old 2.3.6 stock rom back on the phone... That worked correctly as well, but as soon as the "Press the Andriod" to setup appeared, I encountered the same error message as before. "(com.google.process.gapps not working) as well as setup wizard not working, and now its not allowing me to set the phone up at all. Does anyone have any insight on this? All help would be greatly appreciated.. Thanks!!!
Click to expand...
Click to collapse
Root it with odin and flash the stock rom, thatll fix u right uo
Sent from my SGH-T989 using xda premium
soupysoup said:
Root it with odin and flash the stock rom, thatll fix u right uo
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Can you read the edit i put in the first post and give me any info if possible?
THEREHEGO said:
Can you read the edit i put in the first post and give me any info if possible?
Click to expand...
Click to collapse
U don't need the su file at all, all that file does is give superuser permissions, try using Odin to flash the stock 4.1.2 firmware to the device that should fix it, like I said u don't NEED the su file, that's only for root, u could Odin a twrp recovery and use that to flash a stock ROM with working gapps, my guess is u just had a faulty kies upgrade and it didn't quite update right, kies is funny sometime, and when u use Odin u need to make sure there is NO trace of kies running at all, remove it from the PC if u can, download the twrp2.6.tar file from http://techerrata.com/browse/twrp2/hercules and use Odin the same way u did the GB firmware, this will give u custom recovery from there download a stock ROM from here, or go get cl3keners tw-speed-stock ROM from goo.com, mount storage through twrp and move the ROM to ur external SD card, go back to main screen in twrp and select install, find the ROM and flash it, now u will be on stock rooted firmware and should have no issues, pm me if u need further help
Sent from my SGH-T989 using xda premium
soupysoup said:
U don't need the su file at all, all that file does is give superuser permissions, try using Odin to flash the stock 4.1.2 firmware to the device that should fix it, like I said u don't NEED the su file, that's only for root, u could Odin a twrp recovery and use that to flash a stock ROM with working gapps, my guess is u just had a faulty kies upgrade and it didn't quite update right, kies is funny sometime, and when u use Odin u need to make sure there is NO trace of kies running at all, remove it from the PC if u can, download the twrp2.6.tar file from http://techerrata.com/browse/twrp2/hercules and use Odin the same way u did the GB firmware, this will give u custom recovery from there download a stock ROM from here, or go get cl3keners tw-speed-stock ROM from goo.com, mount storage through twrp and move the ROM to ur external SD card, go back to main screen in twrp and select install, find the ROM and flash it, now u will be on stock rooted firmware and should have no issues, pm me if u need further help
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I appreciate it!!! That worked flawlessly... Thanks for taking time out to help.
THEREHEGO said:
I appreciate it!!! That worked flawlessly... Thanks for taking time out to help.
Click to expand...
Click to collapse
Anytime man, I needed help once too, I'm just glad it worked for u...
Sent from my SGH-T989 using Tapatalk 4 Beta
This is work in progress, have got some ideas to disable Knox(only if you are rooted). Will be updating this thread tomorrow after testing the steps on the loserskater 4.3 release.
This may work but only time will tell.
Don't forget to set SELinux to permissive
Remove the following files:
Code:
(along with any associated .odex files)
/system/app/ContainerAgent.apk
/system/app/ContainerEventsRelayManager.apk
/system/app/KLMSAgent.apk
/system/app/KNOXAgent.apk
/system/app/KnoxAttestationAgent.apk
/system/app/KNOXStore.apk
(entire folders)
/system/containers
/system/etc/secure_storage/com.sec.knox.store
(doubt this one is necessary)
/system/lib/libknoxdrawglfunction.so
And I'm not sure SELinux set to permissive is actually necessary. Been running enforced with root and haven't had any issues yet.
Root persisted through reboot?
mrhaley30705 said:
Root persisted through reboot?
Click to expand...
Click to collapse
Just removed knox, rebooted, restored TiBU, rebooted, and root is still intact.
That is very good to hear :thumbsup:
loserskater said:
Remove the following files:
Code:
(along with any associated .odex files)
/system/app/ContainerAgent.apk
/system/app/ContainerEventsRelayManager.apk
/system/app/KLMSAgent.apk
/system/app/KNOXAgent.apk
/system/app/KnoxAttestationAgent.apk
/system/app/KNOXStore.apk
(entire folders)
/system/containers
/system/etc/secure_storage/com.sec.knox.store
(doubt this one is necessary)
/system/lib/libknoxdrawglfunction.so
And I'm not sure SELinux set to permissive is actually necessary. Been running enforced with root and haven't had any issues yet.
Click to expand...
Click to collapse
Can i just rename this files ?
EDIT: I renamed and restarted. Root are present after restart..
loserskater said:
Just removed knox, rebooted, restored TiBU, rebooted, and root is still intact.
Click to expand...
Click to collapse
Have you or anyone else tried Root->freeze Knox in TiBu as an alternative?
stoobie-doo said:
Have you or anyone else tried Root->freeze Knox in TiBu as an alternative?
Click to expand...
Click to collapse
I tried this, but SuperSU is still crashing. So no root for apps that didn't get root access before you installed 4.3.
norbarb said:
Can i just rename this files ?
EDIT: I renamed and restarted. Root are present after restart..
Click to expand...
Click to collapse
Did you root with CF AutoRoot or Kingo?
Evilweasel47 said:
I tried this, but SuperSU is still crashing. So no root for apps that didn't get root access before you installed 4.3.
Click to expand...
Click to collapse
Update samsung security and SU will work. Just after SU FC go to notification and there is policy info, click on it and agree to update. After this SU should work just fine.
Sent from my GT-N8013 using XDA Premium HD app
---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------
stoobie-doo said:
Did you root with CF AutoRoot or Kingo?
Click to expand...
Click to collapse
With CF-Auto
Sent from my GT-N8013 using XDA Premium HD app
norbarb said:
Update samsung security and SU will work. Just after SU FC go to notification and there is policy info, click on it and agree to update. After this SU should work just fine.
Sent from my GT-N8013 using XDA Premium HD app
---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------
With CF-Auto
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
stoobie-doo said:
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
Click to expand...
Click to collapse
I am able to authorize new apps. However after removing Knox supersu fcs. I do not receive a prompt as mentioned above.
stoobie-doo said:
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
Click to expand...
Click to collapse
No i did not notice this.. I just tryed app with root requairment and no problem. Everything working like before update.
Just wanted to add more information to the table
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
tyrantsbane said:
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
Click to expand...
Click to collapse
I think you have to agree to securituy polices before you remove/dissable/rename knox files.
Edit: i post pictures to see that my SU is working fine and no problem. I did what i post allover this forums.
ali3n8 said:
I am able to authorize new apps. However after removing Knox supersu fcs. I do not receive a prompt as mentioned above.
Click to expand...
Click to collapse
I think you can somehow agree to new polices before you remove knox files and in security in settings... (sorry but i don't realy know how). All i know you need to agree in order to SU work until someone will find some other way. I did same with my S4 and last update to 4.3 and twice to leak to on S3 MJ6.
BTW: I got sim card out on my S3 this maybe case and is wort to try.
tyrantsbane said:
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
Click to expand...
Click to collapse
To revert back to a fresh state on 4.3 I had to CF autoroot to get the stock recovery installed. Then while in stock recovery I selected apply update from external sdcard. I have found that when using a custom recovery I was not able to go back to a stock 4.3 state. First boot after doing this will take a bit and may even require a reflash.
so...
Does anyone know how to reset the security policies so I can test some more methods?
Or do I need to Odin down again and trudge my way back up
tyrantsbane said:
does anyone know how to reset the security policies so i can test some more methods?
Or do i need to odin down again and trudge my way back up
Click to expand...
Click to collapse
do not use odin to downgrade after installing the ota!!! You will brick your phone