galaxy s3 At&t Keep restarting - T-Mobile, Samsung Galaxy SIII

I recently own a Galaxy s3 at&t,Version 4.0.4,I rooted it and installed CMW 5.4.4 and KtKernel,I thought to install CM11 through CMW,but i got a Status 7 error,now I've found it is because of Out dated CMW and In hurry og updating it,I flashed new.zip directly though CMW,like flashed new CMW new one via CMW,now My S3 started restarting often,I tried advanced backup through nandroid but nothing is working,Do i need to Flash new stock rom? if I have to flash new one,how can i send the file to device,it's turning on even!

Flash your devices firmware in odin. Also, this is the tmobile forum. Use the AT&T forum in the future, especially for firmware.
Sent from my SGH-T999 using Tapatalk

Related

Galaxy S3 bootloops after flashing any custom rom

So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
The status 7 error happens when the ROM ur about to flash, checks to see if the model of ur phone is compatible with said ROM. Its a good thing(safety mechanism) but can be a pain at the same time. What version of cwm are u using? Download the latest cwm recovery thru the ROM manager app and that can sometimes fix the issue. What ROM are you trying to install?
Sent from my SAMSUNG-SGH-I337 using xda premium
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
shewantsmyduck said:
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
Click to expand...
Click to collapse
Latest cwm is at 6.0.3.1
I think you're getting a little confused.
You need to be rooted to have any custom recovery installed, so right off the bat you are rooted. You shouldn't flash anything with rom manager, it can cause serious harm to your phone. Tom manager is best for just updating your recovery.
There are two main reasons for a status7 error, out of date recovery or an out of date bootloader.
Update your recovery to 6.0.3.1 and he to flash it again, if it comes back you'll need to update your bootloader a two second search in these threads will provide you with a large handful of threads where people had identical issues as you
Sent from my SGH-I747 using xda app-developers app
Checked my bootloader and it says i747UCDLK3 and I think that's the latest... I'll root and install latest CWM through rom manager once I get home
And one question though... I tried using TWRP 2.5 (the latest) and I still got the status 7 error...?
shewantsmyduck said:
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
Click to expand...
Click to collapse
Can you flash any stock modded rom's ? You state you went back to stock but what method did you use to go back to stock ?
Why oh why were you using jellybam...
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
shewantsmyduck said:
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
Click to expand...
Click to collapse
The ODIN flash to stock 4.0.4 probably installed the old ics bootloaders, and the ota update to 4.1.1 may not have included the new jb bootloaders.
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
shewantsmyduck said:
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
Click to expand...
Click to collapse
That's the right one
Sent from my SGH-I747 using xda premium
So what should I do now then :s
You're trying to flash the wrong rom for your device, or you're not using the right recovery for your device. What Galaxy S3 model do you have? On which carrier are you and where did you buy the phone?
I have an AT&T i747 that I got at an AT&T store. The Rom is correct as I've downloaded it numerous times and I've tried the latest TWRP recovery and still received the error.
I'm going to try and flash a factory image tomorrow from the development section and root afterwards. As Michael3214 pointed out in a pm, the issue may be that my phones id has changed, hopefully a factory image will fix that.

[Q] Can you flash with odin after ota update?

I just got a s3 the other day and was gonna root and install some roms. My s3 has been updated to the 4.1.2 ota. I was simply wondering if I were to root it and install a rom and decided to go back could I simply flash the odin 4.1.1 image for it and then go ahead and update ota again? Had done this with my note 2 before and was just wondering if anyone else had any insight. Thanks
****EDIT****: i decided to just try for myself seeing as my s3 is just my play around device and i always have my s4. i flashed the latest android 4.1.1 before they had the ota update UCDLK3. Odin went great and then when i booted back up i stuck at the samsung screen. but to fix just went into stock recovery and factory data reset and boom my device booted up into a clean fresh state. no problems with wifi or anything. so for those of u wanting to unlock your device but had updated to 4.1.2 or maybe just want a clean slate (my position) then i can confirm it works just fine. and then you can just do the ota again if wanted (doing this as i type ). hope this helped.
You can flash with Odin. I used the all in one. The WiFi will stop working on stock ROM. When you flash new ROM WiFi will work again. You may have a couple of bugs to work out but it is worth it. Just google to find solutions. Good luck.
Sent from my SGH-I747 using xda app-developers app

[Q] About Samsung OTA 4.3 android version

Hi all
I had a rooted S3 t999 with MOAR 6.0 installed, and I decided to flash Stock via Odin, flashed the 4.1.2 tar file for the device, and I got unrooted and went to stock...I upgraded to 4.3 when the update pushed by Samsung arrived.
I currently have my phone rooted and removed the Knox security, I want to try and flash other custom roms, will my phone get bricked if I decide to flash a 4.1.2 custom rom? I'm asking this just to make sure that I don't get a very expensive doorstep
Thanks for the advice!
Sent from my SGH-T999 using Tapatalk
Hellfireworks said:
Hi all
I had a rooted S3 t999 with MOAR 6.0 installed, and I decided to flash Stock via Odin, flashed the 4.1.2 tar file for the device, and I got unrooted and went to stock...I upgraded to 4.3 when the update pushed by Samsung arrived.
I currently have my phone rooted and removed the Knox security, I want to try and flash other custom roms, will my phone get bricked if I decide to flash a 4.1.2 custom rom? I'm asking this just to make sure that I don't get a very expensive doorstep
Thanks for the advice!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
You can flash any rom just don't odin any thing lower then 4.3 and don't flash anything to downgrade your bootloader and you will be fine.

SGS2X T989D telus update recovery?

Hello all.
Hopeing i can get some help with my old telus t989d. I recently upgraded to an S5 and am going to give my phone to a friend. problem is that i rooted the device right after i got it and havent touched or updated anything in years. It is still on the very first firmware that it came with Android version: 2.3.5 kernel: 2.6.35.11.
My first question is do i need to update the recovery it is currently running CWM v5.0.2.6 and an extreamly old version of superuser.
Second question is can i do a factory wipe and flash a new ROM like CyanogenMod 11.0 or do i need to update the stock firmware first.
thats all i can think of right now. thanks in advance for any help
Odin flash the 4.1.2 firmware.
Odin flash CWM 6.0.4.4 or newer( or TWRP 2.6.1.0 or newer).
You shouldn't have any problem installing CM11 after you do those things.
Unless your friend is into rooting and what not, I'd definitely give it to him with stock 4.1.2 installed.
Otherwise there will always be some glitches.
Thanks all for the info. Tryed to go back to stock unrooted. That worked fine but when I Tryed to update through keys I made a brick. Oh well
Sent from my SM-G900F using XDA Premium 4 mobile app

Stuck on boot after flashing most recent bootloader

today i rooted, flashed the most recent version of twrp on a stock n7100.
I did all this via Skipsoft unified android toolkit and intended to flash DItto note 4 on the n7100.
Ive done this before since i own another Note2 with Cyanogenmod X currently installed, coming from DN3.
on that phone i have current version of twrp and bootloader OD4.
I flashed the new OD4 bootloader on this newly rooted phone but i have been stuck at the samsung screen since then.
ODIN completed the flash successfully with no errors so i do not understand why i am experiencing this problem.
I have a TWRP backup though.
Can anyone help me sort this out.
THe device still boots into download mode but not into recovery.
Thanks
santet said:
today i rooted, flashed the most recent version of twrp on a stock n7100.
I did all this via Skipsoft unified android toolkit and intended to flash DItto note 4 on the n7100.
Ive done this before since i own another Note2 with Cyanogenmod X currently installed, coming from DN3.
on that phone i have current version of twrp and bootloader OD4.
I flashed the new OD4 bootloader on this newly rooted phone but i have been stuck at the samsung screen since then.
ODIN completed the flash successfully with no errors so i do not understand why i am experiencing this problem.
I have a TWRP backup though.
Can anyone help me sort this out.
THe device still boots into download mode but not into recovery.
Thanks
Click to expand...
Click to collapse
flash Philz recovery and see what happens
Will a full stock reflash fix this.
I need an urgent fix.
Please
Sent from my GT-N7100 using XDA Free mobile app

Categories

Resources