Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
wickbok said:
Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Download the file below file to your S3 and install it via Mobile Odin to get CWM back.
Well, from what I read, you aren't rooted anymore.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
wickbok said:
Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
If I recall correctly, Status 7 means you have an older/not-supported version of CWM installed. Your best bet is going to be to download the Samsung Galaxy S3 QCom ToolKit, and use that to install the proper CWM version. Then you will be able to wipe/install a custom ROM.
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.
Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.
Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.
This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:
spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Solved
Thanks, also works for i727 skyrocket
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse
Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hello,
I'm new to rooting and I softbricked my phone last night. After reading Docs thread on the t-mobile sgh-t999l I was able to restore it to the factory settings.
I am currently running jellybean 4.3. My phone is rooted and I downloaded a CWM custom and flashed it through ODIN (computer).
When I try and install any custom roms through boot recovery I get a status 7 error code. Ive tried everything that Ive read in the other threads as far as readjusting the scripts etc.
Device info:
Baseband Version
T999LUVUBMK4
Kernel
3.031-210647
The phone itself is a T-Mobile refurbish but it might have been a sprint buy back.
When I opened the scripts for the PACMAN installer my UVUBMK wasnt even listed, so I'm not sure whether that is even an issue.
Any help is appreciated.
This seems like an awesome forum and I appreciate everyones input.
Donny
Can i just add my baseband, T999LUVUBMK4, into the script?
D
Flash the latest recovery ?
Sent from my SGH-T999 using xda app-developers app
Sorry for not fully understanding....
What recovery?
I've got the latest nightly of the PAC rom. I updated my CWM to the latest version as well.
Thanks
Donny
So I reset my phone at stock, ran superuser and disabled knox.
Flashed the latest TWRP and tried to reflash the zip.
It hangs on the asserts.
If I try and flash the file with the asserts deleted it wont work either.
Any help?
D
I just rooted my AT&T Galaxy S3
Specs:
Model number: SAMSUNG-SGH-I747
Android Verson: 4.3
I am trying to install the AOKP Rom for my device. I have it all downloaded and know how to install it but I keep getting Status error 7. What is happening? I read a little online and it says this error is for whenever you have the incorrect ROM version? Please help!!
Install the latest cwm onto your phone and flash from recovery mode.
audit13 said:
Install the latest cwm onto your phone and flash from recovery mode.
Click to expand...
Click to collapse
How do I do that?
Check page 3 in the Android development section.
BammS2 said:
Check page 3 in the Android development section.
Click to expand...
Click to collapse
That doesnt help at all /:
Originally Posted by BammS2
Check page 3 in the Android development section.
Click to expand...
Click to collapse
That doesnt help at all /:
Click to expand...
Click to collapse
If you already have a custom recovery CWM then just find the most up to date version of it. You obviously installed once already. Also are you referring to stock 4.3?
Sent from my Awesome Phone using xda app-developers app
Also getting Status 7 error
I had TWRP installed (whatever ver comes with toolbox app)
Read reply, and installed latest version of CWM Touch from: http://forum.xda-developers.com/showthread.php?t=2152769
Still getting Status 7 on two different ROMs.
Now, I had been on 4.1.1, rooted and flashed a custom ROM no problem
Had some problems with my TMO service (I have another thread in this forum) and ended up doing an ODIN flash back to stock (4.0.4)
Which I have now sitting at stock, rooted. Is it possible that I'm getting the status 7 because both of the ROM's I'm attempting to flash are 4.4.2 and that is too big of a leap from 4.0.4? I'm going to grab a 4.1.x rom now to see if any different, but wanted to share history and that I was getting same error
The easiest way for me to get 4.4.2 onto an s3 was this:
1) copy a custom rom to your sd card (internal or external)
2) use Odin to flash back to any stock rom for your phone;
3) use Odin to install the latest version of Philz Touch Recovery from here (get the tar version and flash in PDA): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att;
4) update to the most recent non-4.3 bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
5) do a full wipe in recovery;
6) flash a custom 4.4.2-based ROM from recovery.
dannymac77 said:
I had TWRP installed (whatever ver comes with toolbox app)
Read reply, and installed latest version of CWM Touch from: http://forum.xda-developers.com/showthread.php?t=2152769
Still getting Status 7 on two different ROMs.
Now, I had been on 4.1.1, rooted and flashed a custom ROM no problem
Had some problems with my TMO service (I have another thread in this forum) and ended up doing an ODIN flash back to stock (4.0.4)
Which I have now sitting at stock, rooted. Is it possible that I'm getting the status 7 because both of the ROM's I'm attempting to flash are 4.4.2 and that is too big of a leap from 4.0.4? I'm going to grab a 4.1.x rom now to see if any different, but wanted to share history and that I was getting same error
Click to expand...
Click to collapse
Your main problem is that you need an updated bootloader. Please read up on this as it has been covered in great and very extensive detail throughout these forums. One bootloader will cause you to no longer to be capable of using ODIN to flash back to any stock based ROM without bricking your phone so you need to be careful.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Read more and you will see that cwm recovery is highly recommended for flashing 4.4.2 roms. Some roms dont flash good with twrp.
When I got this note 2, it didn't have the ota to lock the bootloader. I after a year or so on the Alliance 26 rom I had some issues and wanted to upgrade to the newest one. I tried to install it and it didn't take and was stuck in bootloop.
So I used the same files in odin to flash the phone back to stock and start it again.
I was finally able to get it rooted but no recover will install. I am having a hell of a time and I don't understand what I have done wrong. Even casual wont work.
Well when I try to install recovery like twrp the install fails and on boot it says software not supported my Verizon , take to your local vzw store for repair.
Knox has even been tripped as well and it seems like the bootloader is locked. How is that possible? Don't know how, i flash with odin a stock rom as I did when I got the phone rooted and installed a recovery and than a rom. No issues what's so ever.
Now it seems everything I try it either says software not supported by vzw or bad firmware update or boot loops. I have downloaded so many files from all of these recovery threads I'm lost .
Never had the ota update, once I got the phone I flashed it to mj9 per beanstown on the original alliance rom and ran that room ever since.
I think I have tried every how to in this forum. Can someone chime in and tell me what I am doing wrong?
Sent from my SCH-I605 using Tapatalk 2
Phone info..
Sent from my SCH-I605 using Tapatalk 2