Related
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
eduardo_b said:
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
Click to expand...
Click to collapse
Did you remember to factory reset (wipe /data) when flashing the stock ROM? That's the most common cause of soft-bricking in this scenario.
If not, boot into recovery (Vol Up + Home + Power) and do so, then try booting the phone again.
Do I do factory reset from desktop Odin in download mode?
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
smelenchuk said:
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
Click to expand...
Click to collapse
Ah...volume UP. But wipe data/factory reset didn't help. If I select update from external storage, would that be MD5 or...?
Okay, I wiped cache partition and I'm in business. No more softbrick. Thanks!
Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue
zerodv8 said:
Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue
Click to expand...
Click to collapse
did u try root check app to c if u r truly rooted? is ur su updated? if so try reflashing the recovery...n the root file. do u have the stock kernel?
THink I Got a fix
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
ok did read your post before trying to flash. i lost my back up and as well as my emmc. so i need a stock firmware only problem I now have is downloading one. Three quarter of links r dead and the three i have tried have had errors. Can you help me anyone with a google drive or box download of an unknown region stock firmware so I can breathe light in t o my brick please
https://db.tt/63atdfRZ Here ya go!
I'm uploading a stock firmware that can be flashed using ODEN. I have not tried this file, I just downloaded it, before I flashed anything, in case something went wrong. I'll post the link when it finishes uploading. Good luck! Post back and let us know how it went.
solved
Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
I tried your method and it worked. Another thing that works is first thing when you enter TWRP check if system is mounted, if not tick mount and then wipe the way installation of the rom suggests. This worked for me too. Thanks for ur time and the fish
Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.
Tquarter said:
Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.
Click to expand...
Click to collapse
can someone recommend a clean rom for gt-p5210
Hi all, found my old SGH-T989 and I want to turn this phone into my play phone.
I am new to rooting and all and I don't know which versions of what to use. Everytime I mess up, I have to restore the phone back to stock 2.3.6 then upgrade to 4.1.2 via Kies, then try to root and such.
Problem is... I don't know which ROMs, gapps to use and which cwm to use!!! Seems like every guide out there is outdated because I get stuck in a bootloop every single time I try to flash a ROM or I get Error 7...
Any tips?
I just want 4.4.2 at least on my SGH-T989 What are my options? What are your suggestions?
KSmooove said:
Hi all, found my old SGH-T989 and I want to turn this phone into my play phone.
I am new to rooting and all and I don't know which versions of what to use. Everytime I mess up, I have to restore the phone back to stock 2.3.6 then upgrade to 4.1.2 via Kies, then try to root and such.
Problem is... I don't know which ROMs, gapps to use and which cwm to use!!! Seems like every guide out there is outdated because I get stuck in a bootloop every single time I try to flash a ROM or I get Error 7...
Any tips?
I just want 4.4.2 at least on my SGH-T989 What are my options? What are your suggestions?
Click to expand...
Click to collapse
You need to be on 4.1.2 for this to work. I am bit responsible for what happens. You can get 4.1.2 for Odin from samfirmware.com. Download the latest TWRP from here: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar and flash it in Odin. Your phone should reboot. Boot into recovery by powering off your phone and then holding power and the two volume buttons until you hear two vibrations and then hold just the volume buttons until you see a black screen. Release all buttons. Flash @Chainfire's SuperSU in recovery ( http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip) Wipe cache ald Dalvik and reboot. You should be rooted and able to flash any KitKat ROM. AOSPA is a good choice. It is pretty stable.
Sent from my SGH-T989
I just flashed CarbonROM on my sister's phone this weekend. Rooting is not really required.
My process:
Flash TWRP (this was the most difficult of the entire process. It is still relatively easy though). I used Odin to flash the latest TWRP. TWRP provides odin flashable archives so it is really just a matter of knowing how to flash thing using Odin. This does not require root. The CWM wiki page says that Rooting is not required, nor is it the preferred method when flashing a new rom.
You can use Heimdall, but it is very hit and miss with this phone. Odin is much more "reliable" on the T989. I tried Heimdall, but I ended up having to reset my sister's phone because it flashed the recovery incorrectly.
Download the rom of your choice and its associated gapps package. Put them on your sd card
Boot into recovery. You will need to use TWRP's mechanisms to wipe/factory reset the phone. Then wipe cache and dalvik cache.
Install the zip of the rom and then immediately afterward install the gapps package. I usually wipe the cache and dalvik cache again for good measure at this point, but I understand it is not needed.
Reboot the phone. If all went well, it will take awhile to boot, but you will be sitting at the start screen of a brand new shiny rom.
Set it up and start using it. Most roms already come rooted.
The reason rooting isn't required using this method is because the download mode of the T989 essentially gives you root priviledges.
I've used this process on two T989 phones without any error. If you want to backup your phone, do that in step 3 _before_ you wipe/factory reset your phone.
Usually what I do is just use Odin to flash ClockworkMod then copy the ROMS to the sdcard. Boot into recovery then install zip from SD Card, select ROM. If you use CyanogenMod then just select your device and Google search the cyanogenmod gapps
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
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.
So I posted a thread here months ago asking for help but got no help so I'm trying again. Basically the official kitkat update from samsung severely messed up my tablet to the point where it's almost unusable. My question is, is there any way i can do like an ultimate, complete wipe of the tablet? Like wipe partitions, recovery, everything?
I've tried installing nolekat and tranchidakat with still the same problems. I've flashed both the jellybean stock rom and the kitkat stock rom through odin with still the same problems. I even clicked re-partition under odin hoping that would help but still no luck.
Also the problems I'm having are constant reboots, processes and apps just stopping such as systemui, settings, and basically all of my system apps and apps installed from the playstore.
This is a very irritating problem I'm having to the point where I just wanna destroy my tablet. I don't have the money to send it to samsung so I've been trying to find another solution.
Any help at all would be greatly appreciated!
I maybe not have the answer but the reason. How did you update you device kies or OTA. If a custom recovery was install your device it's maybe brick. Me i probably test something like flash a custom recovery only and them flash a rom through to there. Or search to unbrick flash somethings like that.
nannaniel said:
I maybe not have the answer but the reason. How did you update you device kies or OTA. If a custom recovery was install your device it's maybe brick. Me i probably test something like flash a custom recovery only and them flash a rom through to there. Or search to unbrick flash somethings like that.
Click to expand...
Click to collapse
It was an OTA. I had no custom recovery installed prior to the update