Develop Bugs

[Q] Samsung Galaxy S2 Epic Sprint - Help Unrooting

Okay so I just bought this phone from craigslist. It was rooted when I got it. I factory reset the data but then restarted the phone and got stuck in a boot loop. So, I decided to unroot it and put it back to it's original state. I downloaded the original stock kernal - acs-eb30-stock-kernal-pulled.tar - and I loaded it on via Odin. I then followed the command prompt steps to fully unroot the phone and it was successful. I'm not stuck in a boot loop anymore however I can't access the main home page, the settings, get a wifi connection, anything really. It just keeps asking me to put in my google account settings but I can't connect to wifi. I can't get to the home screen page. It's almost like maybe that was the wrong kernal? I was looking for the stock kernal and people were saying it's EG30 not EB30. Any suggestions?

That's probably for another Samsung phone. There was never a EB30 for this phone. It shipped with EG30.
I suggest you use the EK02 ODIN One-Click in my signature. Use the full version that resets your user data.

Sfhub to save the day yet again
Sent from my SPH-D710 using XDA App

Steps please (to remove ROOT and flash with Stock ROM)
Hi,
I have a similar issue. I rooted my phone (Sprint Samsung Galaxy 2 (also called Epic Touch) after I got it in early 2011.
Now I want to remove the root to sell it so it seems I need to "flash a stock ROM". I am not exactly sure how to do that. Can anyone give me steps?
Where do I get ODIN?
Where do I get the stock ROM for this phone?
How do I flash with that Stock ROM using Odin?
Thanks so much in advance. :good:
Ken
sfhub said:
That's probably for another Samsung phone. There was never a EB30 for this phone. It shipped with EG30.
I suggest you use the EK02 ODIN One-Click in my signature. Use the full version that resets your user data.
Click to expand...
Click to collapse

Help!! Sprint Galaxy S3 will not upgrade

Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app

I really hope someone helps with this, because oddly enough, I just had the exact same problem!
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse

I suggest you should go check out the Sprint Samsung s3 forum under the Android development section the check out for the stock rom, try using the 1 click Odin or check out in there the proper way to restore your device, then continue reading the forums to check out when or how is the proper way to apply that update it could be that its bugged or that your device lost some permissions so best way to solve it should be to restore it to its original state.
Sent from my SPH-D710 using xda app-developers app

rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You cant install an OTA update unless you have the official stock rom and the stock recovery because custom recoveries will install it and I believe im correct when I say that to flash an OTA update you have to odin to stock and then do the update.

There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way

Most custom touchwiz roms will allow updates, but you have to flash stick recovery 1st. The 157mb update is for mb1. You could just change your build prop to get the notification nag to go away
sent from my GS3 using XDA app

If you're on stock rooted with no apps removed, do what I did. Plug phone into odin, flash stock recovery, update, flash custom after update done, re root, done.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.

Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.

tazfanatic said:
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
Click to expand...
Click to collapse
Yup, if you just wanna make it go away, go into your build.prop and change all instances of "LJ7" (or "MA6" ) to "MB1"

CNexus said:
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Click to expand...
Click to collapse
That's all I do. Once an update comes out I just head over to Freezas page and update my rom. Stock look and feel with the root in place.
Sent from my stock rooted Galaxy S3

Any update on this? I have the same issue.
Thanks

coderaja said:
Any update on this? I have the same issue.
Thanks
Click to expand...
Click to collapse
There's several ways to fix this issue posted on the other page. Use one of them.
D

New system update 05-01-13

Hey guys,
I have searched the forums for a while but I can not find the exact answer or procedure to help me out. I just rooted my phone yesterday for the first time and early this morning I received a notification to update my system. Can someone please respond in a helpful way to guide me in actually installing the new system updates and remaining rooted with the rom I am running. I understand this may not be possible without going back stock from what I have researched on the forums but any clarity in the situation would be appreciated.
I have the SPRINT GN2 SPH-L900 running Android 4.1.2 L900VPAMC2 and MacksROM Allstar! 3.5 MA7
I would like to install system updates if possible. If it is not explain why. If I can, how I do that and keep rooted with roms I like.
Thanks

If you're running MC2 Baseband, there's nothing you can update until Mack pushes out an MC2-built ROM. Consider the update notification a phantom and ignore it.

I'm running macks 3.5 w/MC2 and kept getting the update system notification and read to just install it and it would go to your recovery (twrp in my case) and it would fall to install. So that's what I did and didn't get the update since then, a few days now. I flagged another rom lady night and now just got the update message again. I will just accept it and it should disappear again. Hope I helped.

redrob820 said:
I'm running macks 3.5 w/MC2 and kept getting the update system notification and read to just install it and it would go to your recovery (twrp in my case) and it would fall to install. So that's what I did and didn't get the update since then, a few days now. I flagged another rom lady night and now just got the update message again. I will just accept it and it should disappear again. Hope I helped.
Click to expand...
Click to collapse
Back when I was on stock with a custom recovery and root. There was a different method that has been mentioned in the forums before, however if I would try to hit restart & install it would just sit there at 0 seconds and never would be able to actually go into the custom recovery. So I just finally decided to go back to stock in update to mc2 and then redo the whole custom recovery and root process.
Sent from my SPH-L900 using xda app-developers app

Well I tried to accept the update but this time it just stayed at the system will reboot screen but nothing ever happened, it never went into recovery or anything like that, however, I haven't got a update message since then.

redrob820 said:
Well I tried to accept the update but this time it just stayed at the system will reboot screen but nothing ever happened, it never went into recovery or anything like that, however, I haven't got a update message since then.
Click to expand...
Click to collapse
Are you trying to take the ota recovery?
Sent from my Amazing Galaxy Note 2!

Not bricked but won't get past initial start up screen

Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)

mlfca said:
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
Click to expand...
Click to collapse
Right off the bat, do NOT use toolkits anymore. Please. You need to learn how to use Fastboot.
The best thing to do is start completely fresh. Download latest Galaxy Nexus factory images and fastboot them.
If you have no idea how to use fastboot, I suggest going to this thread and reading up my man: [GUIDE]New To Adb And Fastboot Guide
Any other questions or help I can gladly answer.

[Q] Getting back to stock from Clean ROM

Guys
I have installed Clean ROM a year or so ago and all is working fine. Today, i dropped the tablet and for some reason it is now refusing to switch on. It will switch on when i do a soft reset, but then as soon as the screen goes into sleep mode, it will no longer switch back on when i press the home, or the on button.
I think its now got a hardware fault, so will look to send it back, but i need help to get it back to Stock ROM. Its a P600 device, and a UK model.
Unfortunately, a friend of mine installed this Clean ROM for me, and i have no idea how to get it back to the STOCK ROM so i can send for repair. Id really appreciate it if someone could talk me through it. Happy to pay a little donation if that helps?
Any takers?

Your screen problem is probably a backlight problem, same as in this thread.
To return your tablet back to stock, download the stock SM-P600 firmware for the UK from here. Follow the instructions on the page.
Note that this will NOT reset the KNOX flag. There's no way to do that.

Thank you for this - its definitely a backlight issue. Seems there is no way to fix this. All i can do is get it back to stock rom and then hope they dont notice the Knox trigger.
Is that stock rom you sent the link to the current UK one? I hope i can follow the instructions - would you mind responding if i have any queries...?

blindmanpb said:
Your screen problem is probably a backlight problem, same as in this thread.
To return your tablet back to stock, download the stock SM-P600 firmware for the UK from here. Follow the instructions on the page.
Note that this will NOT reset the KNOX flag. There's no way to do that.
Click to expand...
Click to collapse
Hi, just to confirm is the process the same even if i have clean ROM installed?

It should be the current UK one, but I'm not positive. Once you've flashed any version of the UK stock ROM, you should be able to use Kies to update to the latest version regardless.
And yes, process is the same even if you have a custom ROM installed. You might want to boot into stock recovery and do a factory reset right after flashing, just to be safe.