Hello
I have been doing a bunch of reading to figure out what I did and how to fix it. I have a Samsung S3 SGH-I747 and had philz touch installed and was running the custom cyagogenmod rom 12.1 but was having trouble with the screen going black during phone calls and wanted to fix this.
I did some more reading and found out that a fix for this was updating the modem. I then proceed to SamMobile and grabbed the firmware for my phone and proceed to install it using ODIN. I didn't notice that I grabbed the wrong firmware (I747M) instead of (I747). Odin said everything installed properly so the phone rebooted and now It looks like I installed the stock rom (which I wasn't trying to do but oh well). The phone hangs on the samsung logo screen now.
The phone will boot into download mode
The phone will boot into the stock recovery, I lost my philz touch.
I am not sure what to do now to get the phone working again? Is it soft bricked? I don't think it Hard bricked.
Can anyone point me in the correct direction?
I was thinking I should grab the correct firmware and try installing that via ODIN again?
Which rom did you flash?
I flashed the firmware from SamMobile which is 4.4.2 but for 747M not 747. I accidentally grabbed the wrong one.
Boot into recovery and wipe data/factory reset, wipe cache, and reboot.
audit13 said:
Boot into recovery and wipe data/factory reset, wipe cache, and reboot.
Click to expand...
Click to collapse
I will try that this evening, thanks.
I will let you know how it goes.
If you were able to flash an i747m ROM onto an i747 with everything working, that would be great as you won't have to worry about using different methods to get back to a stock ROM because all you have to do is flash with Odin.
audit13 said:
If you were able to flash an i747m ROM onto an i747 with everything working, that would be great as you won't have to worry about using different methods to get back to a stock ROM because all you have to do is flash with Odin.
Click to expand...
Click to collapse
Boot into recovery and wipe data/factory reset, wipe cache, and reboot.
I want to clarify a bit.
When I get home I will turn phone on and wipe those two thing then just let the phone reboot?
I never got into the operating system after I did the flash.
I also noticed that all my cyanogenmod flashy screens were gone during boot-up.
Yes, boot directory into recovery, wipe those two items, then select reboot system from stock recovery.
The CM screens are gone because they have been overwritten with the stock Samsung boot logos, pictures, animations, and sounds.
audit13 said:
Yes, boot directory into recovery, wipe those two items, then select reboot system from stock recovery.
The CM screens are gone because they have been overwritten with the stock Samsung boot logos, pictures, animations, and sounds.
Click to expand...
Click to collapse
Yes that worked, my phone is up and running, Thank-you.
Now I would like to install a custom ROM again but want the modem fixed.
The fact that I have did a firmware install would that mean the modem has been updated?
Or do I need to install a recovery, custom rom, gapps and modem files?
i'm not sure if sammobile firmware includes modem. excuse me @ arthur and @ pet , if you ; @PowerjacK15 dont already know your bootloader and modem version (if you do just ignore this post) may want to download this app
http://forum.xda-developers.com/showthread.php?t=2609045
"samsung info" to find out. i think ¿ starting with 4.4.2 they are suppose to match. and i believe (maybe @audit13 knows better) , but enewman used to have a thread with bootloader/modem flashable zips. makes it much easier (for me it did anyway).
anyway just a thought. good luck.
"err on the side of kindness"
What is wrong with the modem? No signal, no data, and/or wifi?
The i747m modem should give you LTE on att as Rogers, bell, and Telus in Canada support the same frequencies as att.
I was having trouble with the phone screen going black when making calls. A few threads mentioned that updating the firmware for the modem fixes this problem.
audit13 said:
What is wrong with the modem? No signal, no data, and/or wifi?
The i747m modem should give you LTE on att as Rogers, bell, and Telus in Canada support the same frequencies as att.
Click to expand...
Click to collapse
I also want to switch to a custom rom like cyanogenmod or slimkat. I may not be going about it the right way. But I thought if I updated the firmware from SAMmobile it would fix the modem then I could proceed with installing a recovery and ROM.
During a call, the screen goes black when you put the phone to your ear? When you remove the phone from your ear, does the screen light up? If the answer is yes to both questions, there is nothing wrong with the modem.
Does the phone function properly? If not, I recommend resolving these issues before moving to a custom rom as not all custom ROMs work well with i747m or i747.
No when I make a call using the cyanogenmod the screen went black and stayed black until call ended. It didn't matter if the phone was near my ear or laying flat it stayed black. Other than that one issue the custom ROM worked perfectly.
Does the screen work properly with the stock ROM? What is the baseband (last 4 characters) on the phone? Baseband can be found under settings.
Yes the phone works properly with the stock ROM that I installed yesterday. I will have to check tonight and see what the baseband is on the phone. thanks for helping me understand this.
The baseband will help determine what can and can't be flashed to the phone. Since you flashed a stock i747m ROM, the baseband will also reveal the bootloader.
The baseband is I747MVLUFOB3
Looks like you successfully converted an i747 to an i747m which is a good thing IMHO. To confirm this, boot into recovery and you should see FOB3 somewhere on the recovery screen.
If you want a custom ROM, do this:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy
Related
Hi,
I'm a half-baked noob here.
I got the Galaxy Note 2 (SGH-THM889V / t0ltetmo (unsure if tmo or vtr or anything else)) already rooted from my cousin. This is what I did with it after I got it:
1. Backed up photos, videos, mp3 to the computer
2. It was in CWM bootloader when I used it, so I flashed TWRP on it with Odin.
3. I flashed OMNI ROM on it successfully via TWRP
----------everything was working fine up till here-----------
4. I tried to unlock the phone, but I figured I had to use the stock ROM to do it
5. I forgot to wipe my cache and data before I tried to flash T889UVALJ1 on it via TWRP
6. It did not succeed
7. After different trials with the stock ROM (same link) , it worked
8. The ROM worked, but I didn't let it initialize, so everything was laggy.
9. I got frustrated because I still couldn't unlock the phone, so I wanted to flash back to OMNI ROM via TWRP
10. Now stuck it's at the loading OMNI icon
11. I tried flashing other versions of TWRP on it via Odin, wiped data, cache, delvic cache, format data, etc. several times and flashed different available ROM's on xda, but none of these worked.
Right now, I am able to load into Download target mod and load into bootloader (TWRP 2.7.0.0 right now) just fine.
I asked my programming friends, one suggested I should update the kerenel, another just said I bricked the phone (no, duh.)
What should I do? Help me, please!
maurice330 said:
Hi,
I'm a half-baked noob here.
I got the Galaxy Note 2 (SGH-THM889 / t0ltetmo) already rooted from my cousin. This is what I did with it after I got it:
1. Backed up photos, videos, mp3 to the computer
2. It was in CWM bootloader when I used it, so I flashed TWRP on it with Odin.
3. I flashed OMNI ROM on it successfully via TWRP
----------everything was working fine up till here-----------
4. I tried to unlock the phone, but I figured I had to use the stock ROM to do it
5. I forgot to wipe my cache and data before I tried to flash T889UVALJ1 on it via TWRP
6. It did not succeed
7. After different trials with the stock ROM (same link) , it worked
8. The ROM worked, but I didn't let it initialize, so everything was laggy.
9. I got frustrated because I still couldn't unlock the phone, so I wanted to flash back to OMNI ROM via TWRP
10. Now stuck it's at the loading OMNI icon
11. I tried flashing other versions of TWRP on it via Odin, wiped data, cache, delvic cache, format data, etc. several times and flashed different available ROM's on xda, but none of these worked.
Right now, I am able to load into Download target mod and load into bootloader (TWRP 2.7.0.0 right now) just fine.
I asked my programming friends, one suggested I should update the kerenel, another just said I bricked the phone (no, duh.)
What should I do? Help me, please!
Click to expand...
Click to collapse
2. It was in CWM bootloader when I used it, so I flashed TWRP on it with Odin.
-What do you mean CWM bootloader? There is no such thing.. Did you mean CWM recovery?
3. I flashed OMNI ROM on it successfully via TWRP
----------everything was working fine up till here-----------
-When you flashed this did you boot up fine? Phone worked, could see home screen, went through set up etc etc...
4. I tried to unlock the phone, but I figured I had to use the stock ROM to do it
-This is where I get confused? Do you mean unlock to use on a different carrier or unlock to flash customs roms?
I'm want to help you but either you don't really know what you did or what you have to do to flash custom roms. .
Verify those ?'s I asked and we can go from there. .
Remember rooting your phone does NOT unlock your bootloader so that you can flash a custom rom like OMNI
Sent from my SCH-I605 using xda app-developers app
When you boot into download mode do you see the word "knox" anywhere? If so that might be pay off the problem.
Also try flashing with TWRP 2.6.3.1 and see if that works. I have been working with BigBiff on am issue with 2.7.0.0 involving a pre 4.3 rom.
Hastily spouted for your befuddlement
lacoursiere18 said:
2. It was in CWM bootloader when I used it, so I flashed TWRP on it with Odin.
-What do you mean CWM bootloader? There is no such thing.. Did you mean CWM recovery?
3. I flashed OMNI ROM on it successfully via TWRP
----------everything was working fine up till here-----------
-When you flashed this did you boot up fine? Phone worked, could see home screen, went through set up etc etc...
4. I tried to unlock the phone, but I figured I had to use the stock ROM to do it
-This is where I get confused? Do you mean unlock to use on a different carrier or unlock to flash customs roms?
I'm want to help you but either you don't really know what you did or what you have to do to flash custom roms. .
Verify those ?'s I asked and we can go from there. .
Remember rooting your phone does NOT unlock your bootloader so that you can flash a custom rom like OMNI
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
-Yeah, I meant CWM recovery, not bootloader.
-After I flashed it, everything booted just fine. I could connect to wifi, go through settings such and such.
-Unlock as in using different carriers.
@Coug76
No signs of "Knox" in download mode.
It shows
Product name: SGH-T889V_NA_VTR
Custom Binary Download: Yes (13 counts)
Current Binary: Custom
System Status: Custom
----------------------------------------------------------
BTW, I didn't make any backups or recovery files
maurice330 said:
-Yeah, I meant CWM recovery, not bootloader.
-After I flashed it, everything booted just fine. I could connect to wifi, go through settings such and such.
-Unlock as in using different carriers.
@Coug76
No signs of "Knox" in download mode.
It shows
Product name: SGH-T889V_NA_VTR
Custom Binary Download: Yes (13 counts)
Current Binary: Custom
System Status: Custom
----------------------------------------------------------
BTW, I didn't make any backups or recovery files
Click to expand...
Click to collapse
I think maybe your partitions are curropt. I would odin back to stock. Find your latest firmware that is still unlockable and the pit file and flash pit and firmware thru odin..then re root and unlock your phone
Sent from my SCH-I605 using xda app-developers app
lacoursiere18 said:
I think maybe your partitions are curropt. I would odin back to stock. Find your latest firmware that is still unlockable and the pit file and flash pit and firmware thru odin..then re root and unlock your phone
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Is there a particular version of Odin I should use?
Also, what are the steps I should take?
Flash stock pit in odin -> flash stock firmware in odin -> re root and unlock -> back to normal
Update:
I tried to Odin the .pit, but it failed. However, I flashed the stock firmware for videotron via TWRP and it's running.
But here's a new problem...
-The WiFi wouldn't turn on.
-It wouldn't search for any network carriers.
-It says no SIM card detected despite having one slotted in.
-When I type *#197328640# in the dialing key pad, it brings me to the phone service management thing with no options for me to choose.
I tried flashing the videotron modem in the link, but nothing has changed.
The phone is locked to Rogers with a Rogers SIM card that has no phone service. (Stopped paying the bills)
-----------edit---------
I flashed the OMNI ROM again, now the WiFi turns on and connects. The phone service, however, still hasn't been able to detect the IMEI (shows as unkown in About Phone) or any phone carriers
I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung
The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?
nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.
brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.
nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.
-Deleted-
I apologize in advance if this is in the wrong thread or section, I'm new to this and am kind of stuck on what to do next. If it is in the wrong section can you let me know where to post?
I'm not sure what the previous version my phone was on but in the recovery menu I see KOT49H.I747UCUFNE4 so I assume it was 4.4.2
Over the weekend I tried to update my stock I747 (no root) through menus using check for update and when it completed my phone would no longer boot.
It gets stuck on the ATT logo and when I try to wipe it in recovery mode it still gets stuck on the same screen.
I have also tried to use Kies but the devise does not show up under the emergency recovery option even though my phone can connect to the computer.
However I have no problems connecting to Odin in download mode.
So what would be the best option for me if I dont want to root my device? Can I use Odin or should I be using a different program?
If I have to root should I follow enewman17 tutorial? If so what step should I start at?
Thanks!
Are you running a stock recovery? Did you wipe everything in recovery?
yep stock recovery, tried to wipe everything but i get the same problem.
If I were in your situation, I would install a custom recovery and custom rom such as cm10.2 to get the phone up and running to verify the bootloader and modem currently on the phone.
Should I be installing the recovery through odin or an sd card? Do you have a link for a tutorial, I've looked through t3chn0s1s's sticky but most instructions seem like they are for phones that can boot.
The method I see using an sd card needs a terminal but i don't think i can get one because I can't boot my phone, is that correct?
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Copy the latest CM10.2 or CM11 to your SD card. Place the SD card in the phone.
Flash Philz in the PDA section of Odin 3.07 and don't check anything except F.Reset Time. When you see "Reset" in the status window, disconnet the USB cable, pull the battery, replace the battery, boot into recovery, wipe cache, data, Dalvik, system, flash CM from the SD card, and reboot.
Thanks got it working last night!
If you want to run the latest CM11 or AOSP ROMs, you may have to update to the latest bootoader and modem.
I have a T-Mobile S4 which was running 4.2.2 (rooted). I was trying to unroot the phone, when I managed to get a hold of a bad file to flash on my phone. The file itself wasn't corrupt as the flash did work, but now my phone thinks its a Verizon phone (yep, wrong carrier). I can't make calls, no data, no wifi connection. I am currently downloading a stock 4.2.2 rom on my laptop and will attempt to flash it to the phone using Odin. If that doesn't work, I'll move the stock rom to my SD card and try to boot from memory. I have little hope for either of these methods to work.
Any help would be appreciated.
You should be good to go simply flashing via ODIN the correct firmware based on your model. Note, some people report mixed results with the first flash fully taking hold, in particular the modem. Many people recommend:
-Phone all the way off as starting point
-Boot to download mode
-Flash via ODIN with the "auto reboot" NOT CHECKED
-Following flash, do battery pull
-Reboot immediately back to ODIN mode
-Flash a second time.
-Reboot normally
Frankenscript said:
You should be good to go simply flashing via ODIN the correct firmware based on your model. Note, some people report mixed results with the first flash fully taking hold, in particular the modem. Many people recommend:
-Phone all the way off as starting point
-Boot to download mode
-Flash via ODIN with the "auto reboot" NOT CHECKED
-Following flash, do battery pull
-Reboot immediately back to ODIN mode
-Flash a second time.
-Reboot normally
Click to expand...
Click to collapse
macaco24 said:
I have a T-Mobile S4 which was running 4.2.2 (rooted). I was trying to unroot the phone, when I managed to get a hold of a bad file to flash on my phone. The file itself wasn't corrupt as the flash did work, but now my phone thinks its a Verizon phone (yep, wrong carrier). I can't make calls, no data, no wifi connection. I am currently downloading a stock 4.2.2 rom on my laptop and will attempt to flash it to the phone using Odin. If that doesn't work, I'll move the stock rom to my SD card and try to boot from memory. I have little hope for either of these methods to work.
Any help would be appreciated.
Click to expand...
Click to collapse
All you should have to do is flash a new ROM. I'm assuming you flashed via a custom recovery as Odin would either fail or brick.. As far as the "first flash not taking hold" comment, I always found that, when using Odin to revert FROM a TouchWiz ROM to the 100% stock firmware, a sure-fire guaranteed way to insure the flash to "take hold" is to flash a non-TouchWiz ROM via recovery before Odin-flashing the stock firmware.. For this purpose, I'd say SlimKat or SlimBean as, I believe, they are the smallest ROMs to download; but anything that isn't TouchWiz should work.
I've Odin-flashed stock firmware while already running a custom TouchWiz ROM and even after that, all of my user apps and data was still there.
A couple days ago, I tried to flash my i747 back to stock, but unfortunately it froze at the Samsung Galaxy S III logo, and is no longer accessible. Another mistake that I think I made was I failed to realize that my phone would go back to stock recovery with flashing the stock rom. As a result, I now can't flash any custom rom or recovery due to "signature verification failed" error. Lastly, my phone can't seem to connect to the computer, so I can't use Odin either. When I connect my phone (in download mode) to the computer, an error would pop up saying that "one of the USB devices has malfunctioned"...I already tried to use different USB cables, different computers, update driver, battery pull, wipe data/factory reset, wipe cache, etc...but nothing prevailed. I'm a newbie to the android system, and I would really appreciate any suggestion on how I might get out of this conundrum, and get my phone back. Thank you!
Before you attempted to flash back to stock what ROM were you running?
What bootloader and modem were on your device before trying to flash stock?
Which stock rom did you attempt to flash to your phone?
If you were not flashing an older bootloader than was on your phone, you may need to do a factory reset from the stock recovery and reflash the stock rom. If you attempted to flash an older bootloader than had been on the device, you may need to search the forums for a debrick image with the same bootloader that was on the device before this started.
Before you attempted to flash back to stock what ROM were you running? __Dirty Unicorns 5.1.1__
What bootloader and modem were on your device before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom); does flashing a custom rom change the bootloader/modem? if not, i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash to your phone? Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!
zynl said:
...what ROM were you running? __Dirty Unicorns 5.1.1__
...before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom);
i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Click to expand...
Click to collapse
No, flashing a custom ROM will not change bootloader and modems, but stock ROMs will.
Baseband and modem are the same thing, as is radio (in most instances). Since you had DU running successfully, in all probability your bootloader and modem were both NJ1. Everything I have seen indicates all AOSP and CM 5.x.x and their derivatives must be on at least NE4 bootloader and modem. If you can get into download mode, and their is anything on the screen about "Warranty Bit" you were on a 4.3 or higher bootloader.
Now for the negative; if you were on a 4.3 or higher bootloader downgrading the bootloader will brick the device. Once you are on any of the 4.4.2 bootloaders, NE4 or newer, you must keep the bootloader and modem versions paired. That is: they must both be NE4, or both NJ1, or both NJ2 otherwise you risk bricking the device. (This is why I think your bootloader was NJ1.) More negative is that the 4.1.1 stock rom you flashed contains the LK3 bootloader and modem.
zynl said:
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!
Click to expand...
Click to collapse
I am surprised you were able to boot at all after flashing the stock ROM. If you are still able to boot froman external sdcard, flashing a debrick image is what I would suggest next. Once you boot, install a custom recovery and verify bootloader and modem on the device from the recovery terminal if possible. The next step would be flashing the NJ1 bootloader and modem. Two threads for reference:
http://forum.xda-developers.com/galaxy-s3-att/general/solution-hard-brick-fix-amazing-t2962611
http://forum.xda-developers.com/showthread.php?t=2549068
If this doesn't work you may be looking needing a jtag service. Worse than that would be a new motherboard for the phone.
Hello
To me it look like you get stuck in boot. First you will need to download correct ATT ROM. Then you will need to select appropriate option in ODIN. Let me know if you have any question. I will help you out. Guaranteed))
If you are able to boot into recovery and download mode, the debrick sdcard method won't do any good. Not saying to not try it if you want to, but I've never seen it work unless the device is truly hard bricked (totally unresponsive). It's only in those cases that it will even look for the image on an SD.
When you boot download mode and connect to the computer, does Odin show a COM# in the upper left? Does it respond in any way at all?
Also check to make sure kies is NOT installed on the computer. It can interfere with Odin. If you still cannot connect, try an older driver version. (See my sig).
Uninstall the old first. Then install the other version and reboot. Connect the device and open device manager. Right click on the USB device that isn't working and update driver. Try auto if you want, but if that doesn't work select manual. Browse to the Samsung folder in Program files and try selecting it that way. (I can't recall the exact location, but you should be able to find it if you poke around a little).
Hope that helps.
Good luck!
Sent from my SGH-T999 using Tapatalk
thanks everyone for helping. after abt a week trying to revive my phone, i finally gave up. recently though, i bought a bricked motherboard for cheap and successfully unbricked it. everything seems to be working fine except i can't switch on the wifi. I already tried wiping cache, factory reset, and even reflashing stock rom (4.3 from samsung) via odin but nothing worked. So, i wonder what could be the source of this? (hardware?.... software??... bc the volume up button also does not work!) and is there something that i can try to possibly fix this? The phone is currently on 4.3, bootloader and modem are both i747UCUEMJB.