Related
My computer died in the middle of rom flash, which caused my T-Mobile SGS4 to nearly brick. I attempted several recoveries (CWM, TWRP, and OUDHS) and several custom & stock roms (including odin) before I was finally able to see some life in it. Because of this, the baseband is the official stock after the update (uvuamdl), and the build number is the official stock prior to the update (uvuamdb). I don't think this would normally be a problem, but now I am unable to flash a custom or stock rom so I think it may be the reason. The phone does not run very smooth, and a notification asking me to reboot because of errors keeps popping up. It is now rooted as well. Is there a way or method to bring everything back to stock?
Thanks,
Ant
ams77 said:
My computer died in the middle of rom flash, which caused my T-Mobile SGS4 to nearly brick. I attempted several recoveries (CWM, TWRP, and OUDHS) and several custom & stock roms (including odin) before I was finally able to see some life in it. Because of this, the baseband is the official stock after the update (uvuamdl), and the build number is the official stock prior to the update (uvuamdb). I don't think this would normally be a problem, but now I am unable to flash a custom or stock rom so I think it may be the reason. The phone does not run very smooth, and a notification asking me to reboot because of errors keeps popping up. It is now rooted as well. Is there a way or method to bring everything back to stock?
Thanks,
Ant
Click to expand...
Click to collapse
If you can get into Download Mode, use ODIN to bring everything back to stock.
ams77 said:
My computer died in the middle of rom flash, which caused my T-Mobile SGS4 to nearly brick. I attempted several recoveries (CWM, TWRP, and OUDHS) and several custom & stock roms (including odin) before I was finally able to see some life in it. Because of this, the baseband is the official stock after the update (uvuamdl), and the build number is the official stock prior to the update (uvuamdb). I don't think this would normally be a problem, but now I am unable to flash a custom or stock rom so I think it may be the reason. The phone does not run very smooth, and a notification asking me to reboot because of errors keeps popping up. It is now rooted as well. Is there a way or method to bring everything back to stock?
Thanks,
Ant
Click to expand...
Click to collapse
I had the same problem and all you need to do is Odin the new stock firmware again. You can get the firmware here in the android development area.
So I rooted my s3 t999 so I could get cyaneginemod. I used the flashing rom way, and it didn't work,(i used twerp recovery) it kept saying failed, and then I went to the easier way of installing the rom with, the new cyaneinge mod app, (I'm still rooted). Then after waiting for it too finish my phone rebooted, but cyaneinge was not on it, instead it came with a page that said root missing I clicked on yes fix the missing root, n well nothing happens I was back on touchwiz, superuser was their but Samsung Knox kept it from doing anything but I used supersu to disable it. I thought that knox was keeping the cyaneinge mod app from working, so I decided to downgrade to 4.1 when knox didn't exist, bless that time, but I couldn't since odin kept failing at flashing a stock rom, I did this soo msoon times I went through every firm ware n back to 4.3, it kept failing, im pretty sure its boot locked, but the root is also limited, every time I reboot n go to recovery n leave it asked me if it should fix the missing root, but yes or no, it wont change, n every time I reboot it says optimizing apps 0 of 48, it takes at least 5 min to go through. N after going through every forum, YouTube video, asking friends, I still can't find a solution, n im stuck on a screwd up root version of 4.3 plz help
You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?
serio22 said:
You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?
Click to expand...
Click to collapse
i don't remember but I used twrp n as I Was flashing through rom it said failed, same thing when I flashed 4.3 stock firmware on odin later
If you have Kies that will give you problems with Odin. And make sure you have latest twrp
Reflash your current firmware with Odin. Then flash recovery, then the rom. No need to root first.
If the rom flash fails, you need to post the exact error it gives, and attach the recovery.log or theres little we can do to help.
We could start throwing out guesses, but there could be dozens of things potentiality causing your problem.
To anyone more of an expert than myself on these matters (which I presume to be a large portion of users here), I'd greatly appreciate any help that can be provided. I'd also like for this thread to be a central collection of baseband/modem functions, behaviors, troubleshooting, etc...
I've had a T-Mobile S4 (SGH-M919) for a while now and have mostly used CyanogenMod derived ROM's and as of lately, more Google Play Edition/Nexus type ROM's (which generally appear to be written for the international i9505 and hence show the model number of my phone to be such; this may or may not be relevant). All of the sudden, the other day during a phone call I received, there was no audio on either end of the call. I couldn't hear the caller nor could the caller hear me. This also happens if I initiate the call. I know for a fact that the media speakers (speakers used during speakerphone) as well as the earpiece speaker are perfectly functional so it's not a case of hardware failure where it works on Bluetooth or speakerphone only. As soon as a call initiates, you hear no ringing or audio once the caller answers other than the tone when the call ends/disconnects. First thing I tried was switching from ART back to Dalvik just for the sake of troubleshooting. Second, I tried clearing the cache (and Dalvik, just for the hell of it). Still no success. So next I try a completely different ROM. I was presently on a GPE ROM with the Samsung kernel so I switched to plain CyanogenMod with a custom kernel. I even went back to a stock ROM! No success either way!!
It was at this point I decided that it had to be a hardware/firmware issue since the issue remained when changing ROM's so I naturally assumed baseband/modem. I don't understand why this issue just magically occurred one day when I hadn't changed anything, but I thought that if I reflashed a clean modem image or and updated one, then maybe it would fix it... I was on MDL so I reflashed the MDL modem. No success. Then (and here's where I f****d up), I tried flashing what I THOUGHT was a stock NB4 firmware file in ODIN. Turns out that despite being labeled as stock, it had a custom kernel built-in and tripped my KNOX counter (FFFFFUUUUUUCCCCCKKKK!!!) Well, since I really only intend to use AOSP/CM based ROM's, it's not such a huge deal for me but still, it sucks.
Here's where I had a break: Yesterday, I tried flashing the MDL modem again, then that didn't work so I tried flashing the MK2 modem. I booted up, made a call, and it worked! First time! Well, that was short lived success because I tried another call immediately after to verify and it started all over again. Now, even reflashing MK2 won't get it to work even once like it did this one time.
Does ANYone who understands baseband and modem firmware much better than I do have any insight or instruction on what I can do? Because of this one issue, I have an otherwise perfectly good S4 that I can't use just lying around. I've had a Nexus 5 for almost a year and love it but I just destroyed the screen after a drop the other day and wanted to switch to the S4 temporarily until the Nexus 6 comes out. ANY IDEAS????
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
faiyo said:
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
Click to expand...
Click to collapse
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
thair7391 said:
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
Click to expand...
Click to collapse
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
faiyo said:
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
Click to expand...
Click to collapse
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
thair7391 said:
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
Click to expand...
Click to collapse
I really have no idea about aosp roms for this device because i only used touchwiz to keep samsung features.. so i have no knowledge about firmware compatibility. I would think the creator of the rom should specify any firmware requirements.
On the thought of hardware failure, and i know you said the speakers work, but did you test the sim card slot? Perhaps it needs to be cleaned? Maybe the sim card is partially failing so try a different card? Maybe you cut it and it's loose (you wont believe the crooked sim cards i've seen). I think it's worth pursuing since you said it worked once and not again.. maybe you had just taken the cover off while flashing stuff and touched/pressed it but it's losing contact again after flexing during use. I dunno dude, the kind of call audio issues i've had were always resolved with a reboot & making sure the modem matches the touchwiz build.
Please make sure you are running a full stock firmware package & keep the touchwiz rom consistent with it. Some firmware packages are partial components
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
For starters, up until a few days ago, I ran all types of ROM with an MK5 boot loader and 3 different modems and never had a call issue. After that said, I read a few months ago about a guy had your same issue. He ended up getting a new sim card and he got is audio back. He also had reception issues before getting the no audio issue.
thair7391 said:
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
Click to expand...
Click to collapse
Try flashing the firmware again, some have to flash it twice for the bootloader to update, which may the trouble. If that doesn't work try a new sim like it was suggested before me
I know it's been a while but I basically gave up and just recently came back to it. I've since bought a Nexus 6 so it's not a priority issue anymore however I would still like to fix this otherwise perfectly fine Galaxy S4 that I have lying around! I seemed to believe that there was a special combination of custom ROM and specifically the MK2 modem that would sometimes cause the audio to intermittently work but it appears I was wrong. I flashed the full stock NH7 firmware/baseband etc back to my phone twice as suggested and NY audio worked! For a few calls that is... Then it stopped working again. Sometimes I could clear cache and reboot and it would work! Once or twice anyways before crapping out again... The bottom line is that there isn't a pattern aside from a cleared cache that makes the audio work again before it stops soon after which unfortunately leads me to believe it's a deep rooted hardware issue in the baseband itself. Anyone else have ideas?
Other than trying a new sim, I can't really think of anything else except to make sure the bootloader really did update. Download Samsung phone info from play store and check bootloader info to make sure it was updated to NH7
Unfortunately it is completely updated. I tried a new SIM and everything works still except audio in phone calls, including ringing. I guess it's hardware... Guess now I just have an internet browsing MP3 player with web browsing capabilities.
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
What are the links to all these incorrect firmwares?
Posting the links would be more informative than suspicions.
Pp.
wallacengineering said:
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
Click to expand...
Click to collapse
Yes, could you post the links that you say have the issues?
AxAtAx said:
Yes, could you post the links that you say have the issues?
Click to expand...
Click to collapse
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
wallacengineering said:
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
Click to expand...
Click to collapse
I just put that stock rom on my wifes phone a few days ago, and it defaulted to Note 3 on hers. well, never mind, as you have seem to have got it rolling now.:good::good:
I must be taken crazy pills.
Pp. :what:
Can i ever unbrick my note 3
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
boofydon said:
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Ravoz88 said:
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Click to expand...
Click to collapse
Thank you for your time. I flashed it with a new stock from sammobile but it's still in a boot loop state even though odin always show pass. And when I flashed it with twrp my note 3 was unable to enter recovery mode.
So i just spent the last 4+ hours trying to figure out what the latest firmware for the Samsung Galaxy S3 SPH-L710 since google was not my friend tonight.
So i had L710VPUDNJ2 installed on my phone... rooted, TWRP, unlocked bootloader.
I kept getting prompts about an update for the phone, and finally decided i couldn't ignore it anymore, so my journey began to get rid of it.
1st Headache; What is the latest firmware for the phone?
Well according to Sprint's Website for the SPH-L710 the latest version available is L710SPTBMK5.
OK, cool, this should be easy.
Go find a flashable ROM; [ROM][MK5][STOCK][ODEXED/DEODEXED] and flash it to my phone.... Stuck on boot... ****...
2nd Headache; Latest Flashable ROM is CRAP!
Boot back into TWRP and decide to say **** it and do a full wipe.
Wipe System/Data/Dalvik/Cache
Flash MK5 Rom
Reboot phone
Success!
Phone boots up and i can start tweaking it back to my standards... but wait... what's this? No cell signal at all...
Ok this is strange, but it's Samsung after all, so i expect it to be **** and have issues.
I go into Settings and look at the Mobile Networks settings... No Network mode selected.
I choose LTE/CDMA, the phone says it needs to reboot, i tell it OK
Thinking this was the problem and i am smarter than i apparently am, i started to smile and give myself a good pat on the back when the phone booted back up and still no signal.. WTF!?!?
At this point i'm convinced that XDA forums has the dumbest people in the world posting Roms on it and i decide to take on a new approach.
3rd Headache; Finding and downloading everything
So i know that L710VPUDNJ2 is a legit version for the SPH-L710 to work with Sprint.
So i find the ODIN download for it; [STOCK][ODIN][TAR] L710VPUDNJ2 PC Odin Flashable ( Sprint )
I download the latest version of Odin; Odin3 v3.10.7 (this version might change over time just fyi)
I downloaded the latest version of USB drivers for the phone; USB (Driver) ver.1.5.45.0 (this version may also change over time)
And then proceeded with the following
Install Latest drivers
Reboot PC
Put phone into "Download Mode" (Vol Down + Home + Power)
Ran Odin3
Clicked on AP and selected the NJ2 tar file (after extracting it from the .zip file of course)
Connected the phone to my PC
Clicked START after Odin3 recognized the phone
Well, low and behold after 20 mins or so, i have a working phone again! :good:
I go into the phone's settings and force it to check for an update, and wouldn't you know it, it found one!
I download and install the update, wait for it to come back up, and then immediately go to check what version it's on.... L710VPUDOH1
Well that's nice and all, the sprint website did say that was a version after L710VPUDNJ2, but it's not the LATEST version according to Sprint.
So, i go back and force the phone to check for updates.... Nothing!
So there you have it. Don't believe everything you read on the internet.
TL;DR: Sprint website lies. Use the links above to get on the latest version.
Well, you can't update with a rom zip. To update, you always have to use a .tar in odin. The .tar files contain the modem and bootloader files, which are required for an updated phone to boot.
You are lucky you didn't try an mk5 tar, you would have a hard brick. That is pre Knox firmware (4.3 jellybean). I heard there was a new mk5 too, I don't know for sure. But the first mk5 was the boost and virgin Mobile version of mk3. But someone posted they got an mk5 update that said stagefright patches, so.... Not sure. But oh1 and oj1 are the newest, I believe, for sprint, and boost/vm. Respectively
That thread you linked for the mk5 flash able zip clearly said jellybean 4.3 and that date was a couple years ago. Clear indication that it was not new.
There is supposedly a new MK5 that is supposed to fix Stagefright completely as opposed to a half fix from OH1.
L710SPTBMK5
Previous was L710VPUDOH1.
However, I suppose at this point, most of the userbase has already upgraded to a new phone or installed a custom ROM, so anything on this forum that's not 2015 and says MK5 is too old.