At&t s3 soft-brick - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Here's the story:
I'm trying to install CyanogenMod on the AT&T Galaxy S3 SGH-I747, which has the 4.4.2 NC6 touchwiz build on it.
Everything was going fine; I rooted with towelroot, I flashed a clockwork mod recovery. And I downloaded the latest CM build and placed it on an external sd card
When I booted into CWM and tried to install CM, it gave me an error, saying "can't install over incompatible data"
Okay...so I formatted dalvik cache, cache, and I factory reset and tried flashing again. It went a little further in the installation process, but still got an error.
Then, having made a nandroid backup before, I tried to restore the backup, which seemed to work...
Until I rebooted after restore was finished. Everything booted fine, until it got stuck on the AT&t spinning globe screen thing. Then, it just stayed there...
Is there a way to fix this?????? I tried reflashing stock in odin, but that failed (a giant red FAIL at the top). Then I realized that was because you can't downgrade from 4.4.2 to something like 4.1. So I looked for a 4.4.2 tar.md5 to flash in odin, but I couldn't find any.
Please help!
Thanks...

I had similar trouble about a month ago except I was using twrp. Are you using the D2lte file?
Can you still get into recovery?
I'm the furthest thing from good at this stuff but I know the question will be asked.
Sent from my SGH-I747M using Tapatalk

Did you encrypt your phone?

skiiermike said:
I had similar trouble about a month ago except I was using twrp. Are you using the D2lte file?
Can you still get into recovery?
I'm the furthest thing from good at this stuff but I know the question will be asked.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
Yeah, I used the latest M snapshot for the D2lte on get.cm
And yes, if I do the three button combination, I'm still able to boot into ClockworkMod and do stuff.

audit13 said:
Did you encrypt your phone?
Click to expand...
Click to collapse
No, I did not encrypt the device.

darkcompgeek said:
Yeah, I used the latest M snapshot for the D2lte on get.cm
And yes, if I do the three button combination, I'm still able to boot into ClockworkMod and do stuff.
Click to expand...
Click to collapse
Where are the files located that you are trying to install?
My trouble came from my micro sd that was in my device. I tried everything and it kept giving me errors to the point that I couldn't even get into the twrp recovery and had to restore with Odin.
My solution was an external otg adaptor. As soon as I loaded cm and gapps from the otg everything went smoothly.
Sent from my SGH-I747M using Tapatalk

If it's hanging at the boot screen, reboot recovery and factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Related

Help!

So i did the ULVH1 update through ODIN, followed the instructions. Once i was on ODIN picked the file for it. Ran it at firt it said Boot! Then Pass! So phone trys to reset but i get stuck on the reboot screen! Did i just brick the phone? Im rooted and using a custom rom (jedi mind trick v7). I need help on this.
Oh onre more thing. When i was stuck on the reboot. I tried getting into CWM and it got me through. Aren't i suppose to be unrooted already once this update occured?
Reboot loop? If you can get into CWM, you can always wipe, flash, wipe cache to fix things. If you can get into CWM you're still ok.
Now the thing about unroot and recovery, there's sort of different things. You can be unrooted, but still have CWM. CWM just lets you flash new ROMs that aren't manufacturer certified, I believe. I forget the details. So booting into ICS you could be unrooted, but the recovery is still CWM/TWRP
You are much better off using TWRP then CWM.
premiatul said:
You are much better off using TWRP then CWM.
Click to expand...
Click to collapse
Would you still use TWRP to flash roms that the OP recommends using CWM or CWM Touch?
I also understand NAND backups you made with CWM won't be restored successfully by TWRP?
So I got it to work. Im a noob on this stuff, so i wasnt sure if the file that XDA had was bad or not. I used a diff. one from phandroid.com. Went through ODIN and it went through with no problem. Lost root and CWM. Basically im back to stock. I eventually rooted again and CWM. But the funny part about it is that why do i still have my pics on the gallery? I thought this deletes everything? Like i said. Im a noob! lol. Everything seems working fine. Screen shots (went back the old way, instead of Power and Volume down.) Also, ISIS is that on google play? :good:
No flashing back to stock does not erase your internal storage.
Sent from my SGH-T989 using xda app-developers app

[Solved] $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)

Basically this is what happened, I rooted my phone using TeamEpic-Root-from-Recovery-v5.zip and CWM-Recovery-LTE-SGS3-v5.tar.zip with Odin without any problems. Then I tried tampering with the framework-res.apk and I thought I did it correctly, I replaced it with the current res in the /system/framework folder of the internal sd. Then I rebooted my phone and bam stuck at the Samsung Galaxy S III screen. I've now tried finding a way to get into the internal sd card to replace the framework-res.apk back to original but my computer wont recognize it when in recovery or downloading mode. I have trying reflashing Clockworkmod several times and I've tried wiping the cache and factory reset. When I factory reset it says error mounting sd card, aborting. I am now out of ideas as to how to fix it and I'm not sure what to do with PIT files, which could be a possible solution. I am running Tmobile's Galaxy S3 T-999 16gb. All that being said, anyone who can help me get my phone back up and running I will reward you with $10 through paypal, because that's how desperate I am to fix my phone before someone finds out I bricked it!
Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app
camacho.kyle said:
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, what do you mean by reinstall drivers, like kies? I can't flash any rom's because I can't transfer the zip files over to the sd card since my phone won't recognize it since it won't go past the samsung screen. All I can do is flash clockwork mod from odin like .md5 and .tar. If I install a lower version of Odin what version did you use, and do you think flashing clockwork mod will be able to replace the framework-res.apk through odin?
Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
iAmYoungSpiffy said:
Thanks for the reply, what do you mean by reinstall drivers, like kies?
Click to expand...
Click to collapse
Reinstall the drivers for Odin, and you can even try reinstalling Kies too. Make sure you restart your pc after you reinstall kies and the drivers.
Sent from my SGH-T999 using xda app-developers app
Are the files you flashed for a I9300? They do not look familiar to me.
Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Aerowinder said:
Are you using a SGH-T999 or an I9300? If the former, use the links in my signature. Should fix it if it's not hosed.
Uninstall Kies (and the drivers if the Kies uninstall doesn't do it).
You may want to Odin a stock rom. If you do, it it before flashing a recovery.
Click to expand...
Click to collapse
He's using a T999
Sent from my SGH-T999 using xda app-developers app
camacho.kyle said:
He's using a T999
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Do you think changing the clockworkmod .tar.md5 file and flashing something different will have any affect? If so, what do you suggest?
Check out my signature, it has everything you should need (save the OS you want).
Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Wow thanks for that clockworck mod! It has much more features than v5 I'm gonna play around with it and see what I can come up with.
Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Thank you for the files, I'm now able to flash roms from my sd. I"ve flashed your clockwork and superuser. However, when I load up the phone I'm still getting stuck at the samsung logo
no external sdcard?
Did you try to flash another rom? What were you using, and what did you flash?
Why are you trying to fix a bricked ROM with CWM?
Just Odin a stock rom, and work from there. I don't know why you would keep trying to reflash recovery, that isn't going to do squat for you.
Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott
mt3g said:
no external sdcard?
Click to expand...
Click to collapse
I do, 64gb
Aerowinder said:
Did you try to flash another rom? What were you using, and what did you flash?
Click to expand...
Click to collapse
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?
You can't flash a rom from your external sdcard? or your internal? or either?
sbaeder said:
Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott
Click to expand...
Click to collapse
I've now tried flashing Team Epic's ROM and I've wiped all cache restored to factory settings wiped dalvik cache, no progress.
mt3g said:
You can't flash a rom from your external sdcard? or your internal? or either?
Click to expand...
Click to collapse
Now that I updated my clockwork mod I'm able to flash from my sd card. Trouble for me is finding the right ROM that is compatible and appealing. I've tried a few now and whenever I flash them I go to boot up the phone and I get stopped on the samsung galaxy s iii logo. There has to be a way to wipe everything and flash a fresh clean rom. I've stayed up till 2 in the morning only to get up at 6 in the morning two nights in a row now totaling almost 10 hours of trying to fix my phone
iAmYoungSpiffy said:
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?
Click to expand...
Click to collapse
From this quote it seems that you are flashing TWRP recovery and the flashing CWR right after it. That makes no sense. I don't use CWR on this phone but have used it before. So I'm not sure that LTE should be in the description as T999 isn't an LTE device. I could be wrong though. You can get an Odin-able version of either TWRP or CWR from this page.
Go here and download the stock image TMO T999UVDLJA. Follow the directions in the OP (make sure you unzip it first. Read and then read it again) . Fire up Odin and put the Root66 tar in the PDA slot (nothing in PIT). Flash the Root66. It will take about 5 minutes or so. Once it says Pass it should reboot. It WILL bootloop. If you have already flashed EITHER TWRP or CWR, then boot into recovery and Factory Reset. If you haven't flashed EITHER TWRP or CWR, then pull your battery and boot back into Download Mode. From there you put EITHER TWRP or CWR into the PDA slot and flash it. Pass. The reboot into recovery and Factory Reset.
First boot will take the longest bc it has to rebuild the /cache and /dalvik-cache. Let's get you up and running before you move on to flashing a custom ROM, OK?

DId I brick it?

I can't get the system to boot up after flashing the Wicked rom. It booted only once but now I am stuck at the Galaxy S4 logo screen at start up. I have tried flashing to another rom but still its not working. It stays stuck at the Galaxy S4 logo. I have done a clean wipe too just to make sure. Any suggestions on fixing this. The recovery I am using is TWRP. I tried clockwork mod but it does not mount my SD card.
driodman98 said:
I can't get the system to boot up after flashing the Wicked rom. It booted only once but now I am stuck at the Galaxy S4 logo screen at start up. I have tried flashing to another rom but still its not working. It stays stuck at the Galaxy S4 logo. I have done a clean wipe too just to make sure. Any suggestions on fixing this. The recovery I am using is TWRP. I tried clockwork mod but it does not mount my SD card.
Click to expand...
Click to collapse
Are you using a 64GB sd card in exFAT format? If so try booting without the sd card. If that don't work you might need to Odin back to stock. Using stock recovery wipe data and start over again.
Also what version of TWRP are you using?
I recommend Philz CWM version as TWRP gave me trouble when using with Aroma installer.
http://forum.xda-developers.com/showthread.php?t=2322676
baseballfanz said:
Are you using a 64GB sd card in exFAT format? If so try booting without the sd card. If that don't work you might need to Odin back to stock. Using stock recovery wipe data and start over again.
Also what version of TWRP are you using?
I recommend Philz CWM version as TWRP gave me trouble when using with Aroma installer.
http://forum.xda-developers.com/showthread.php?t=2322676
Click to expand...
Click to collapse
Didn't work. The philz does not even boot into the recovery at all. It just sits at the logo with recovery booting blue text at the top left. Basically at this point I could go back to stock just to have something usuable at this point.
Alright, no need to worry bud, as long as it turns on, you're good, ha.
If you want to go back to pure stock, flash this via ODIN: http://hotfile.com/dl/213546261/7ab...-SGH-M919-TMB-M919UVUAMDL-1366964131.zip.html
It is the full stock firmware.
You can follow my guide here: http://forum.xda-developers.com/showpost.php?p=31890391&postcount=2
But instead of downloading the file in step 1, download the one I listed above.
I had trouble using twrp also, im currently running wicked 6.1 without any issues but here's what I did when I was stuck installing. I went back and cleared data factory reset, and cleared cash then went to my nandroid back up and reinstalled backup. Then I went and downloaded cwm touch recovery installed, then I wipe data factory reset and reinstalled the rom wicked and it worked. Booted up just fine with different recovery. I was having other issues with twrp so cwm worked well. Hope this helps.
Why anyone uses TWRP boggles my mind. CWM official is all you need ^_^
dynospectrum said:
Why anyone uses TWRP boggles my mind. CWM official is all you need ^_^
Click to expand...
Click to collapse
There's two kind of people in this world.. :laugh:
I'm with you, though. CWM touch is epic, lol.
Agreed. Twrp is not stable, use cwm.
Sent from my SGH-M919 using Tapatalk 4

[Q] Android 4.3 hanging on boot

I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.
Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.
To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.
Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement
GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)
My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.
You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.

Categories

Resources