I recently had some issues with my phone and tmobile sent me a new one but I have to send this one back within 7 days.
I was rooted and flashed to beastMOD2.5 and I used http://forum.xda-developers.com/showthread.php?t=1323878 to get back to the unrooted, stock rom. I thought this would put me back at out the box status so tmobile would not know if I was rooted or not. I restarted the phone and upon startup, I get the Gray Synergy Kernel screen, then it proceeds to boot up just as it does when I got it from T-mobile.
My question is, how do I get that to not pop up, or how do I get this phone back to complete UNROOTED status? Mind you that I am unrooted as of now and do not have CWR since it was not included in the stock rom I used.
Any help would be great! (Please step by step instructions, my first android lol)
le14 said:
I recently had some issues with my phone and tmobile sent me a new one but I have to send this one back within 7 days.
I was rooted and flashed to beastMOD2.5 and I used http://forum.xda-developers.com/showthread.php?t=1323878 to get back to the unrooted, stock rom. I thought this would put me back at out the box status so tmobile would not know if I was rooted or not. I restarted the phone and upon startup, I get the Gray Synergy Kernel screen, then it proceeds to boot up just as it does when I got it from T-mobile.
My question is, how do I get that to not pop up, or how do I get this phone back to complete UNROOTED status? Mind you that I am unrooted as of now and do not have CWR since it was not included in the stock rom I used.
Any help would be great! (Please step by step instructions, my first android lol)
Click to expand...
Click to collapse
Just Odin the stock kernel I believe made by bubby323. Check development section for it.
Powered by the SGSII....
I've been receiving [incessant!] prompts that an OTA update was ready to install on my phone.
So - I unrooted my phone and replaced the stock recovery using this process.
Following that, I checked that I no longer had root, and booted to recovery to confirm it was the stock recovery... and then back into the phone to finally tap the "install" button when prompted.
The phone rebooted into the stock recovery, started to install the update... then, in red text - an ERROR message (that I failed to capture because after a few minutes the phone just went to an android with a red ! triangle over it).
I had to pull the battery since the buttons didn't do anything and there were no other options. The phone booted back into recovery, and then I got some sort of confirmation message in yellow text that sounded like "success", and I was still in the stock recovery.
So, I selected the "reboot" option and booted back into the phone.
All seems well (I'm still 100% stock, not rooted), but I am completely unclear if the update worked or failed.
If I go to "system update", I get messages in all four categories:
( i ) Error
The PRL update could not be
completed. Please try again later.
If the problem persists, you may
need to contact Customer Service.
Error: (Code:4)Client Authentication
Error
Click to expand...
Click to collapse
The Update Profile, Update Samsung Software, and Update Firmware all return the same error message.
How can I check the status of my device?
Any ideas what these errors indicate?
Looking for an answer on this- either:
1) What does "Error: (Code:4)Client Authentication Error" indicate when checking for updates in the System Update category?
and/or
2) How do I check to confirm if the OTA update completed successfully?
On a side note - I'm also interested in learning what is/was in that update. The answer to 2) might help me find a thread specific to that OTA update.
Help is appreciated, thanks.
Are you using a custom recovery like CWM or TWRP?
The Root said:
Are you using a custom recovery like CWM or TWRP?
Click to expand...
Click to collapse
No. As described in the first post -
I had previously rooted my phone and installed CWM recovery (to flash a 'root from recovery' update).
Since I was receiving this update notification, I followed the process in the link I posted to unroot and restore the stock recovery. I booted into recovery to confirm the stock recovery was back. Then I accepted the OTA update, and the process went as described.
Also, Hardware Version (in 'About Device' in settings) no longer shows "modified" status. I'm still un-rooted / stock recovery.
Should the update have changed my version? I'm showing PLG8 for baseband version.
As mentioned, the appearance is that I can't force the phone to check for a new version due to the error message I get in the System Update categories, so I'm unclear whether the OTA applied, didn't apply, if it caused an issue, or if this is all normal?
What would indicate that the OTA update applied? Baseband version number? What should it be?
If you check for a System Update on your device, do you get this same message that I'm seeing?
Thanks!
geolemon said:
Since I was receiving this update notification, I followed the process in the link I posted to unroot and restore the stock recovery. I booted into recovery to confirm the stock recovery was back. Then I accepted the OTA update, and the process went as described.
Also, Hardware Version (in 'About Device' in settings) no longer shows "modified" status. I'm still un-rooted / stock recovery.
Should the update have changed my version? I'm showing PLG8 for baseband version.
Click to expand...
Click to collapse
When you went through this step what version of ICS were you on? Also, did you erase any system apps? Sometimes this can stop the update from processing. The newest version is LI3 and should be reflected in your baseband. There were like 2 updates that got you to LG8 originally so if you had restored to an earlier version you might have been getting the update to LG8, but then again if it failed obviously you wouldn't be on LG8 now... Hard to say. Would need to know more about your setup.
The Root said:
When you went through this step what version of ICS were you on? Also, did you erase any system apps? Sometimes this can stop the update from processing. The newest version is LI3 and should be reflected in your baseband. There were like 2 updates that got you to LG8 originally so if you had restored to an earlier version you might have been getting the update to LG8, but then again if it failed obviously you wouldn't be on LG8 now... Hard to say. Would need to know more about your setup.
Click to expand...
Click to collapse
Thanks.
No - All stock. LG8 I believe.
All I did was root my phone using the first two links on this thread (install CWM recovery, then root from recovery):
http://forum.xda-developers.com/showthread.php?t=1743780
And unrooted it using the last link on that original post in that thread (unroot and stock restore).
Nothing was changed, all stock.
Only rooted it to provide an emergency means of tethering if necessary on a work trip.
Superuser app was added (and was removed on stock restore), and Wifi Tether app was installed.
Is the update to LG8, or LI3?
geolemon said:
Thanks.
No - All stock. LG8 I believe.
All I did was root my phone using the first two links on this thread (install CWM recovery, then root from recovery):
http://forum.xda-developers.com/showthread.php?t=1743780
And unrooted it using the last link on that original post in that thread (unroot and stock restore).
Nothing was changed, all stock.
Only rooted it to provide an emergency means of tethering if necessary on a work trip.
Superuser app was added (and was removed on stock restore), and Wifi Tether app was installed.
Is the update to LG8, or LI3?
Click to expand...
Click to collapse
If you're on LG8 it should be the update to LI3. Have you Odined to stock, stock?
Sent from my SPH-L710 using xda app-developers app
I may be misunderstanding the question... clicking that link may help.
I was 100% stock prior to a client visit two weeks back. I rooted following the process in that link.
In brief (using files in that link)
1) installed CWM via Odin
2) use CWM to flash "root from recovery" file
This week I started getting prompted there was an OTA.
Knowing I at least needed stock recovery or it would fail,I restored back to stock following the restore process in that link.
In brief (using restore files in that link):
1) flash unroot file via CWM
2) use Odin to flash stock recovery.
I used root checker to confirm root was gone, rebooted to recovery to confirm CWM was gone, booted back to phone and accepted the OTA.
The phone then booted into recovery and events occurred as described in post 1.
Anything unusual spotted with the process?
Sent from my Nexus 7 using xda app-developers app
Here's a screen capture of the update error message:
Sent from my SPH-L710 using xda app-developers app
Why not re-root, flash CWM or TWRP, then flash the rooted LI3 ROM here: http://forum.xda-developers.com/showthread.php?p=28116723
Wish I could help with the actual error you're receiving in stock recovery, but at least this way you will have LI3, which seems to be what you're wanting to accomplish.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
DrgnRebrn said:
Why not re-root, flash CWM or TWRP, then flash the rooted LI3 ROM here: http://forum.xda-developers.com/showthread.php?p=28116723
Wish I could help with the actual error you're receiving in stock recovery, but at least this way you will have LI3, which seems to be what you're wanting to accomplish.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Click to expand...
Click to collapse
Not a bad suggestion, at least fundamentally. However - I wasn't pleased after rooting previously that my device status showed as "modified", which then caused my Google Wallet app to constantly display a warning and have transactions appearing in an "unknown" status because of 'compromised security due to modified device status', and all that. Ugly.
I also wasn't able to consistently tether, in fact more often than not could not. I can't prove this ties somehow to a 'modified' status, but since that was my primary reason for rooting (and since the tethering was for an "if needed" to VPN in on a business trip (think 'spare tire') I only want to root again if I can:
1) tether consistently and reliably (I'm traveling again on the 20th)
2) do so without the device status showing as "modified".
Otherwise, I'd prefer to leave my device stock, where at least stock apps work as supplied.
Does that method impact the device status?
geolemon said:
Not a bad suggestion, at least fundamentally. However - I wasn't pleased after rooting previously that my device status showed as "modified", which then caused my Google Wallet app to constantly display a warning and have transactions appearing in an "unknown" status because of 'compromised security due to modified device status', and all that. Ugly.
I also wasn't able to consistently tether, in fact more often than not could not. I can't prove this ties somehow to a 'modified' status, but since that was my primary reason for rooting (and since the tethering was for an "if needed" to VPN in on a business trip (think 'spare tire') I only want to root again if I can:
1) tether consistently and reliably (I'm traveling again on the 20th)
2) do so without the device status showing as "modified".
Otherwise, I'd prefer to leave my device stock, where at least stock apps work as supplied.
Does that method impact the device status?
Click to expand...
Click to collapse
I searched XDA for "Change modified status" and this was the third result: http://forum.xda-developers.com/showthread.php?p=22462960
1) I've had great success using the wifi tether app. I connect through VPN to my company all the time with it. Also, there is a plethora of support posts related to troubleshooting wifi tethering. Search "wifi tether" and start reading. If you cannot get it done though, then go back to stock & pay to use the tether service through Sprint.
2) I searched on XDA for "Google Wallet" & this was the very first result: http://forum.xda-developers.com/showthread.php?p=28679456
Rooting is not for everyone. There's no shame in being stock.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
DrgnRebrn said:
I searched XDA for "Change modified status" and this was the third result: http://forum.xda-developers.com/showthread.php?p=22462960
1) I've had great success using the wifi tether app. I connect through VPN to my company all the time with it. Also, there is a plethora of support posts related to troubleshooting wifi tethering. Search "wifi tether" and start reading. If you cannot get it done though, then go back to stock & pay to use the tether service through Sprint.
2) I searched on XDA for "Google Wallet" & this was the very first result: http://forum.xda-developers.com/showthread.php?p=28679456
Rooting is not for everyone. There's no shame in being stock.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Click to expand...
Click to collapse
I'm over the novelty of rooting, that's all, years ago. Going back to my G1 (the first Android phone ever!), I rooted that one even.
In the case of my Magic (basically a G1 without a keyboard), it was really to extend it's life, I was running custom ROMs on both the G1 and Magic (CM6), was a great option. Kept it a long time, loved that phone actually. Still miss a trackball.
Here, I rooted for a specific purpose - and actually the Wifi Tether app was the one I used, since I've had experience with it on my other phones. Always worked flawlessly, going back to the Magic days even.
But on the GS3 - I don't know if you've tried it or not - it's not reliable. You'll find threads for it (I worked through several of them in the airport trying to get it working, using different profiles, different settings, even sideloading an older APK that predated the GS3 profile, as some users mentioned that as the path. Bottom line regardless - it's just not 100% on the GS3. I spent somewhere close to 2 hours, 1 of that in the airport, reading through threads and troubleshooting suggstions, none were 100%.
And I wouldn't pay for it, we travel with MiFi devices that the company pays for. This was just a backup plan, me being a nice guy. Thought it would be easy, as it always has been in the past. There's something unique to this phone that's very different than others, not sure if this is your first, but other phones are usually simple... root, use Wifi tether. No hassle.
So, that being the case (or until an option exists for tethering that is reliable), I don't have much need for root. Even Titanium Backup. Would be nice to do nandroid backups, but if it's all stock... should be no real need.
I didn't read that thread (yet), but there's an "everything about Wallet" thread here. That one may be linked... Wallet works, I haven't had a problem with it not working, but with the device in a Modified status, it gives you some eyebrow raising warnings.
I believe that thread is actually for people who didn't read that "everything about Wallet thread", have flashed a custom ROM without clearing Wallet, and as a result now find themselves in tears with a locked/bricked Wallet. That'll make some people happy.
If my device is going to show a "modified" status, with the (hopefully few) risks inherent in that (ie. Sprint support), I'll at least go to a JB leak ROM or CM10 or similar and get some bang for my commitment, as opposed to the "least modified possible" route yet showing modified status. I just had no need to yet, not looking forward to wiping my phone, reinstalling, reconfiguring.
Triangle Away has been around a long time too - I didn't bother with it when I rooted because of this disclaimer:
- On the SGS3/Note2/etc, System->Settings->About device->Status still shows "Modified"
This is outside the scope of Triangle Away. The "system" status is not even always resettable in the bootloader. If you are going for warrenty, you need to also reflash a full stock firmware and wipe your device. If they boot up your device and find root apps, you're not going to get any warranty anyway. If you do such a full stock reflash and wipe, the "Modified" value will go away.
Click to expand...
Click to collapse
The Modified status did go away when I flashed the stock recovery back. Wallet is my only concern with that status btw, it's slick how it gives you transaction statuses, however it apparently leaves many of them as "unknown" in this state, which I'd like to fix (or stay stock for now).
Here's the situation,
My USB port has failed. I am unable to charge my phone or connect to my computer via USB. I have tried multiple USB cables, chargers and computers without any luck. I have insurance with sprint, but I am under the impression I need to revert to a stock rom (without root) in order to qualify. Here in lies the problem! I am unable to connect to odin to perform the one-click exe. that I am familiar with. I have mobile odin pro, as well as dropbox, but I am very unfamiliar with how to revert with these programs. I have read a number of threads trying to figure out the best way to go about this, but I am unsure on the order in which I need to proceed to avoid bricking my phone.
I thought about just bringing my phone in as is and seeing if they would replace it, but right now I have the yellow caution triangle at bootup, the binary counter says 1, and I am running andriod 4.2.2. I am worried that if they say I voided the warranty, I will be unable to get the phone repaired.
Right now the phone is working without any other problems, until the battery dies (25% left) and I can't charge it (again). I am running the following setup:
Baseband version: S: D710.10 S.FL24
Kernel version: 3.0.64 -CM-g31f128d, [email protected] #1
CyanogenMod version: 10.1-20130705-unofficial-d710
Build number: cm-d710-userdebug 4.2.2 JDQ39E eng.dastin1015.20130705.092856 test-keys
I also have CWM-based Recovery v6.0.3.3, but like an idiot I apparently did not create a backup before flashing 4.2.2
Questions
Can I complete a one-click exe. with mobile odin that will revert me to stock?
Which one should I choose?
Do I need to DL and install a different bootloader, modem, kernel, etc before completing the one-click?
I am still a rookie when it comes to flashing, but I am able to follow instructions well. Any advice one what steps to take is greatly appreciated!
I would not flash with that little amount of battery left. I would do one of two things. Get an external charger and flash back to stock(gb27 stock unrooted), can be flashed with MO, or flash triangle away and take it into the Sprint store. If you have more than one Sprint store in your area, I'd try the latter first, but that's just me. And one clicks install everything, modem, kernel, etc.
Sent from my SPH-D710BST using xda premium
So I decided to go with the external charger. After I had a battery that had some life again, I called sprint to switch back to my GS2 from a pile of crap flip phone I am using. Unfortunately, the sequence of numbers they told me to get the pop-up screen would not work. I assume that is because I am running 4.2.2 with the cyanogenmod phone rather than the standard dial-er. Is there anyway around this or should I just flash my device back to stock and start over from scratch? Thanks
Matt
memogensen said:
So I decided to go with the external charger. After I had a battery that had some life again, I called sprint to switch back to my GS2 from a pile of crap flip phone I am using. Unfortunately, the sequence of numbers they told me to get the pop-up screen would not work. I assume that is because I am running 4.2.2 with the cyanogenmod phone rather than the standard dial-er. Is there anyway around this or should I just flash my device back to stock and start over from scratch? Thanks
Matt
Click to expand...
Click to collapse
I would try flashing back to stock and then retrying the sequence. From what I've heard in regards to AOSP ROMs, you can't do things like update your PRL or activate that device for a mobile carrier (although i may be wrong about the latter)
If you're still having trouble with your USB cable i would suggest looking into Mobile Odin for flashing a stock kernel and firmware. You can check the second post of the Mobile Odin thread for instructions on how to do it, and if you're still unsure about the process you can drop a question in that thread and have it answered there.
EDIT: It seems that this thread sounds like some problems you're experiencing with your USB port. As for the Sprint Activation you may have to revert to a stock ROM/kernel, but you can try the method listed in that thread and hopefully it would work out and allow you to connect through USB
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
after rooting and during boot, I get the "Samsung Custom" with a unlocked padlock screen...so I assume that means it is unlocked??
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
Or are you talking about CARRIER unlocking the SIM? If so do you happen to have a reference for doing this to a Verizon Phone?
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
i got exact same problem only i can root my device so far any solution ?
Verizon locked bootloaders. I tried this with twrp and had that issue too
Sent from my SCH-I545 using xda app-developers app
I realize this a 2-year-old post, but would you happen to still have the stock firmware (I545VRUEMK2) for this thing? I have an older Jellybean unit that I need to fix (and want to keep JB as I can root it easily).
Thanks