So I totally nuked my phone this weekend. T-mobile is mailing me a new SGH-T989 because of my warranty so it's mostly good.
I wanted to update to the latest TWRP so I could flash a 4.3 ROM (Simbean) . I Odined in and flashed TWRP 2.6.3 because goo.im wasn't working. I was able to flash the Slimbean ROM but on first reboot I couldn't make it past the Samsung screen.
I can get back into TWRP but everything fails. - typical process. "Fix permissions- Success", then "Full wipe - Success" then "Fix permissions (cause I'm trying anything at this point)- Failed"
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work and boot up but if the phone sleeps it won't wake up again. I can only get back to TWRP.
I tried flashing back to stock but I hang the pink T-mobile screen.
Eventually I think I mashed the power button and the phone wouldn't even boot.
So I'm getting a new one. I want to root it and replace the stock rom of course but.... Is TWRP 2.6.3 screwed for anyone else? I've heard rumors...Is CWM still a viable choice for modern JB ROMS?
thanks.
As you'll see all over the T989 forums, people have been having lots of trouble with TWRP 2.6.3. TWRP 2.6.1.0 is recommended by most. I wiped and flashed Slimbean 4.3 without any issues using TWRP 2.6.1.0.
treefrog321 said:
As you'll see all over the T989 forums, people have been having lots of trouble with TWRP 2.6.3. TWRP 2.6.1.0 is recommended by most. I wiped and flashed Slimbean 4.3 without any issues using TWRP 2.6.1.0.
Click to expand...
Click to collapse
Awsome, Thanks.
pairustwo said:
So I totally nuked my phone this weekend. T-mobile is mailing me a new SGH-T989 because of my warranty so it's mostly good.
I wanted to update to the latest TWRP so I could flash a 4.3 ROM (Simbean) . I Odined in and flashed TWRP 2.6.3 because goo.im wasn't working. I was able to flash the Slimbean ROM but on first reboot I couldn't make it past the Samsung screen.
I can get back into TWRP but everything fails. - typical process. "Fix permissions- Success", then "Full wipe - Success" then "Fix permissions (cause I'm trying anything at this point)- Failed"
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work and boot up but if the phone sleeps it won't wake up again. I can only get back to TWRP.
I tried flashing back to stock but I hang the pink T-mobile screen.
Eventually I think I mashed the power button and the phone wouldn't even boot.
So I'm getting a new one. I want to root it and replace the stock rom of course but.... Is TWRP 2.6.3 screwed for anyone else? I've heard rumors...Is CWM still a viable choice for modern JB ROMS?
thanks.
Click to expand...
Click to collapse
i had twrp 2.6.3 and it really screwed up my phone. so stick with 2.6.1! but i have read that cwm is way better so i might switch
twrp 2.6.3.0
It seems like some people have trouble with 2.6.3.0 and some don't. I have been using it since it came out and usually flash at least one new ROM daily with not a single problem.
stormannorman said:
It seems like some people have trouble with 2.6.3.0 and some don't. I have been using it since it came out and usually flash at least one new ROM daily with not a single problem.
Click to expand...
Click to collapse
I think the problem with 2.6.3.0 is with backing up and restoring backups, not flashing ROMs.
Reposting as this was posted in wrong section:
Hi
I have been trying to upgrade from CM 10.1 (build 03212013 ) to Paranoid Android 4.4, since I see the new version has BLN support (I'd stuck with the old CM for so long due to this).
Anyways upon trying this I discovered I had to (always ran clear cache, and ran the T989 script super -wipe)
- update my modem to the latest t-mobile - upgraded to the latest which is needed - UVMC6
- was trying to install with CWM 5.8.x - but it would just 'hang' at "installing ZIP" further research indicates I need to upgrade CWM
- Upgraded to CWM 6.0.4.3 per more searching, tried erase flash, just hangs - further research indicates this CWM has a known issue
- used ODIN to goto TWRP 2.7 - flashed, and booted, tried numerous times hangs at "teamwin' screen when trying to boot into recovery
Ended up giving up and Odin flashing back CWM 5.8.1.3 and loading my old CM 10.1 build again
Anyone have any hints why this is so difficult for me?
Need some help if possible please!
thanks
Jonathan
Found work around
Just want to update
I managed to find a work around of sorts. I needed to restore my phone back to CWM 5, and to do that I needed to use ODIN to flash it.
After flashing CWM5 back to the phone, I was able to restore previous ROM (CM mod 10.x), and boot up. After that I used the rommanager to re-install CWM 6.0.4.3, and reboot the phone into recovery.
When in recovery I went to mountand storage, and formatted , /cache, /system and /data. After doing that I choose to install ZIP from SDcard, and selected the Parandoid Android 4.4.x I was trying before. This completed, and installed without any error messages.
Hopefully this helps someone else out.
Thanks,
Jonathan
Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.
Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors
audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?
At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.
You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?
The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.
IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes
I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.
I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?
Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.
Alright so I previously had Danvdh's GPE 4.4.3 and today I tried upgrading to 5.0 today. Didn't full wipe though, just did Dalvik and cache.
It worked, but then it turned into a boot loop (also didn't flash a new kernel that apparently I should have to go along with the 5.0 update..?). TWRP also either took FOREVER to load into, or basically just froze, not even sure.
Used ODIN to flash back to stock 4.4.2 (M919UVUFNB4_M919TMBFNB4_M919UVUFNB4_HOME.tar - this file) and I STILL got boot loop. At that point, TWRP also wasn't working - stuck on teamwin image (tried upgrading to 2.8 since I had something like 2.5x).
Right now, I switched to CWM and it's working. Can't format data though; it freezes on formatting data (something corrupt perhaps? I'm not an expert..)
Still on that constant boot loop and CWM can't mount external sd card, probably cause it's on exFAT format, formatting to FAT32 as we speak. CWM can read external SD now.
Note: I can get into download mode and CWM recovery
Any ideas y'all? Please? Thanks!
***UPDATE***
Finally got stock to work by flashing it via ODIN again. Used stock recovery and for some reason that allowed me to format/delete data. Now I'm loading into stock - got past the dreaded Samsung Galaxy S4 splash!
Finally have Danvdh's 5.0 on with a Googy kernel. It's all good now guys! Who thought stock recovery would help me out.
Good find.
Pp.
Was on 4.4.2 stock NJ2...Odin'ed a custom recovery like TWRP...rebooted.....NO IMEI and BASEBAND. That's about as simple, yet complex it gets. Tried reverting back to stock recovery in Odin, only to find that NO IMEI and BASEBAND still shows up. THE ONLY way I've successfully kept the IMEI/BASEBAND....is by keeping everything stock, from recovery to rom. Why would this be? I've even tried restoring the EFS folder....to no avail!!!! I'M FRUSTRATED!!!! My end goal is to be able to flash a rom, use TWRP/CWM, and KEEP the IMEI/BASEBAND!!!
ANY HELP? ANYONE having the same issue or fix?
THANKS!!!!!!:good:
Possible fix...
Make sure you have not used device encryption on the rom prior to your desired rom...
If you have then a device full wipe script is needed to clean up the phone prior to flashing the new rom...
(don't forget to check your SD card for encryption or data files that may be affected)...
Flash TWRP version 2.8.6.0 and flash your new rom....
Higher TWRP versions have been buggy for me...
Best I've got atm....g
It's because you are using TWRP 3.0.0.1, that one is broken