Related
Okay, rooted my phone last night, she was working fine, updated the Rom this morning with cyanogen 7.1 I believe, and installed a gapps package for market, hated it, lost alot of things and just generally wasn't working how I wanted it to, went into the CWM and tryied to restore my phone from a back-up, went to re-boot and now it gets stuck on the samsung galaxy s GT-I9000 screen and doesn't go any further, tried deleting the cache, someone please help!
Oh btw, the phone was on 2.3.3 gingerbread, and was fine! Rooted it with odin btw!
What I really want to do is get rid of all of this and put her back on a stock ROM
Please help! Much apprieciated!
I'ma newbie here and not sure if I've put it in the right spot :S
bondiboi said:
Okay, rooted my phone last night, she was working fine, updated the Rom this morning with cyanogen 7.1 I believe, and installed a gapps package for market, hated it, lost alot of things and just generally wasn't working how I wanted it to, went into the CWM and tryied to restore my phone from a back-up, went to re-boot and now it gets stuck on the samsung galaxy s GT-I9000 screen and doesn't go any further, tried deleting the cache, someone please help!
Oh btw, the phone was on 2.3.3 gingerbread, and was fine! Rooted it with odin btw!
What I really want to do is get rid of all of this and put her back on a stock ROM
Please help! Much apprieciated!
I'ma newbie here and not sure if I've put it in the right spot :S
Click to expand...
Click to collapse
1.Link to stock ROMs HERE
2.also tutor to use Odin for flashing here
3.flash Froyo then use Kies to check for update just an idea
4.why not to post in I9000 threads...
5.or do like this
-go to sammobile.com and make account there
-then go to samfit
-fill in the fields with Product Code/ PDA and press Send
to search for latest firmware for your phone also get flashing software
Enter *#1234# in dialer for PDA Code i.e. I9000BOJS5
Enter *2767*4387264636# in dialer for Product Code i.e. SGH-I9000ZKBKPNi9000DXID1
bondiboi said:
Okay, rooted my phone last night, she was working fine, updated the Rom this morning with cyanogen 7.1 I believe, and installed a gapps package for market, hated it, lost alot of things and just generally wasn't working how I wanted it to, went into the CWM and tryied to restore my phone from a back-up, went to re-boot and now it gets stuck on the samsung galaxy s GT-I9000 screen and doesn't go any further, tried deleting the cache, someone please help!
Oh btw, the phone was on 2.3.3 gingerbread, and was fine! Rooted it with odin btw!
What I really want to do is get rid of all of this and put her back on a stock ROM
Please help! Much apprieciated!
I'ma newbie here and not sure if I've put it in the right spot :S
Click to expand...
Click to collapse
If you can get into CMW, install CM7.1 again, and after that do factory reset. Then reboot, and install last Gapps package, than do factory reset again and reboot.
Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend
Throws a signature verification failed error.
Try again with the new method
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Why go to 2.3.6? It´s better than 2.3.5 customized?
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.
narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.
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
I am very new at this, so I apologize in advance. I have the Virgin Mobile Galaxy S3 SPH-L710 running 4.3.
I simply wanted to root it so i could get rid of the bloatware and install Sixaxis and play emulators, but I didn't really know where to start, so I started looking around and found this
http://forum.xda-developers.com/showthread.php?t=2546505
So I basically did everything on there. I used Odin to install PhilZ Touch 6 Recovery (CWM 6.0.4.7) Did factory reset, wiped cache/dalvik. then installed the Odexed MK5 stock rooted zip, wifi fix zip, SuperSU update zip, and then the knox app remover zip.
Everything flashed just fine and it started right up. It had the Super Su app, but when I tried to install apps that need root permission it would say I don't have root access. I couldn't delete bloat apps and Super Su didn't show any apps and there isn't much I can do with it. So I guess it didn't work? Either way I wanted to try a different rom. Was gonna give Cyanogenmod a try. But every time I try to install it I get the little "Android bot laying on his back" thing and it says status 7. I tried to flash CM10, CM10.1, CM10.2, CM11. Nothing worked, same thing every time. Even tried different SD cards just in case of a mess up.
The phone itself works fine for now, calls and text work, wifi works. And it says there is an update, but when i hit accept, it reboots to recovery mode, does the "android fallen over" then boots back up.
Now here is my stupid part, I didn't backup the original cause the guide didn't say to. (Not blaming them, i should have know better) So I am assuming I have a messed up version of 4.3 and Cyanogenmod doesn't know what to do with me. I'm not sure. Here is where I am stumped and I have no idea where to go from here.
I posted this by accident in the wrong forum here
http://forum.xda-developers.com/galaxy-s3/help/tried-rooting-s3-didnt-help-t2879278
But someone decided to help me anyways (thank you so much). They said all i need to do is update my recovery. so I went here
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
And now I am running PhilZ 6.48.4, but I am still getting status 7 when I try to install CM11. I have tried CM10, CM10.1, CM10.2 and CM10.2.1 as well. I have been at this for days and i am going crazy because nothing I do seems to work. Does anyone have any idea what is wrong with my phone? Thank you so much in advance.
Mumonk said:
I am very new at this, so I apologize in advance. I have the Virgin Mobile Galaxy S3 SPH-L710 running 4.3.
I simply wanted to root it so i could get rid of the bloatware and install Sixaxis and play emulators, but I didn't really know where to start, so I started looking around and found this
http://forum.xda-developers.com/showthread.php?t=2546505
So I basically did everything on there. I used Odin to install PhilZ Touch 6 Recovery (CWM 6.0.4.7) Did factory reset, wiped cache/dalvik. then installed the Odexed MK5 stock rooted zip, wifi fix zip, SuperSU update zip, and then the knox app remover zip.
Everything flashed just fine and it started right up. It had the Super Su app, but when I tried to install apps that need root permission it would say I don't have root access. I couldn't delete bloat apps and Super Su didn't show any apps and there isn't much I can do with it. So I guess it didn't work? Either way I wanted to try a different rom. Was gonna give Cyanogenmod a try. But every time I try to install it I get the little "Android bot laying on his back" thing and it says status 7. I tried to flash CM10, CM10.1, CM10.2, CM11. Nothing worked, same thing every time. Even tried different SD cards just in case of a mess up.
The phone itself works fine for now, calls and text work, wifi works. And it says there is an update, but when i hit accept, it reboots to recovery mode, does the "android fallen over" then boots back up.
Now here is my stupid part, I didn't backup the original cause the guide didn't say to. (Not blaming them, i should have know better) So I am assuming I have a messed up version of 4.3 and Cyanogenmod doesn't know what to do with me. I'm not sure. Here is where I am stumped and I have no idea where to go from here.
I posted this by accident in the wrong forum here
http://forum.xda-developers.com/galaxy-s3/help/tried-rooting-s3-didnt-help-t2879278
But someone decided to help me anyways (thank you so much). They said all i need to do is update my recovery. so I went here
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
And now I am running PhilZ 6.48.4, but I am still getting status 7 when I try to install CM11. I have tried CM10, CM10.1, CM10.2 and CM10.2.1 as well. I have been at this for days and i am going crazy because nothing I do seems to work. Does anyone have any idea what is wrong with my phone? Thank you so much in advance.
Click to expand...
Click to collapse
only thing i can think of Is Odin the stock rom and start all over with trying to root......
I don't know how to explain it, but now everything is working perfectly....
I went back to the first site I posted about, Redownloaded everything, did the whole thing over, and root worked just fine. So I thought I would try my luck with CM11 and BOOM, working perfectly.
I have been tearing my hair out trying to get this to work for days and days and now, poof, it's all working. I dunno how, but I will take it. Thanks for the advice in both threads.
Mumonk said:
I don't know how to explain it, but now everything is working perfectly....
I went back to the first site I posted about, Redownloaded everything, did the whole thing over, and root worked just fine. So I thought I would try my luck with CM11 and BOOM, working perfectly.
I have been tearing my hair out trying to get this to work for days and days and now, poof, it's all working. I dunno how, but I will take it. Thanks for the advice in both threads.
Click to expand...
Click to collapse
Get towelroot, is an apk that root your phone with one click, after that just download your favorite super user from the market and done.
Just some background: Running an unrooted Galaxy S4 since the S4 first came out w/ T-mobile and everything was ok. Sometime this summer T-mobile came out with the 4.4.2 OTA update and since then everything went to hell. On my 2nd replacement phone from T-mobile and the issue of the phone suddenly not being able to make or receive calls after a successful Bluetooth car connection persists. Everything else works BUT that. I'm just no longer comfortable in pulling off on highway shoulders to speak on the phone. T-Mobile did a shoulder shrug and told me to deal with Samsung directly...which i wont even bother with. So..... I'm ready to flash the phone. My question is. What is the MOST stable, least loaded with bloatware ROM that is available (where all the functions work). I currently run the NOVA launcher and plan to do same. I do not care about the ROM having specific graphical functions and just prefer the stock T-mobile ROM look. Thank you guys in advance (if someone can direct me to a link with FLASH instructions I'd appreciate it too... (haven't flashed since my Evo3D a few years back) Once again, Thank you for your time.
At lunch now so just time for a few quick thoughts:
You might as well update to 4.4.4 first to get the latest LTE modem.
Then use Odin to flash the latest TWRP recovery.
Look into the Google play edition or slimkat ROMs. They are debloated and tend to be safe choices.
Sent from my SGH-M919 using Tapatalk
First thing is to backup your phone on your pc, since you don't have a custom recovery.
http://forum.xda-developers.com/showthread.php?p=55374113
This is simple and debloated, stock with some developer features.
Or you can flash stock samsung and debloat yourself.
Plenty of material on YouTube to get you started.
I'm currently running factory stock debloated, no knox, no samsung junk or tmobile junk. Also running CWM recovery. Everything works, bluetooth works perfectly on my Kenwood ddx 714.
Pp.
PanchoPlanet said:
First thing is to backup your phone on your pc, since you don't have a custom recovery.
http://forum.xda-developers.com/showthread.php?p=55374113
This is simple and debloated, stock with some developer features.
Or you can flash stock samsung and debloat yourself.
Plenty of material on YouTube to get you started.
I'm currently running factory stock debloated, no knox, no samsung junk or tmobile junk. Also running CWM recovery. Everything works, bluetooth works perfectly on my Kenwood ddx 714.
Pp.
Click to expand...
Click to collapse
Pancho, how does one backup phone to PC?
Thanks for the link on the debloated ROM. Are there step by step instructions on how to flash it from stock? I havent done this in a while. Thanks.
All you do is copy your internal/external sd's to a folder, you never know what can happen. make sure you sign into google/play store so all your apps/contact info can be restored. You will find instructions in rom tread Op and from other members as they post. You Tube is very handy also.
Pp.
KEVIN88GT said:
Pancho, how does one backup phone to PC?
Thanks for the link on the debloated ROM. Are there step by step instructions on how to flash it from stock? I havent done this in a while. Thanks.
Click to expand...
Click to collapse
Samsung KIES product will backup your phone:
http://www.samsung.com/us/kies/
And, installing it will install the drivers that you need for when you need to use ODIN.
Rob
Kies can be cantankerous if your not stone stock, once you root kies won't recognize your phone but you should be able to access the backed up files with windows explorer. I use it with my wife's note 3 only because its stock, never rooted, and it works OK.
Pp.
PanchoPlanet said:
Kies can be cantankerous if your not stone stock, once you root kies won't recognize your phone but you should be able to access the backed up files with windows explorer. I use it with my wife's note 3 only because its stock, never rooted, and it works OK.
Pp.
Click to expand...
Click to collapse
Since the OP is running un-rooted stock, KIES should work fine for backing up the phone. Now, when/if he roots, and installs a custom recovery/ROM, then it may not.
So, OP, use KIES to backup what you have now with stock. Then, when/if you install a Custom Recovery, you can do a NAND backup to the SD card.
Rob