Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
MevNav said:
Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
Click to expand...
Click to collapse
Are you sure you have the stock firmware for the 902l and not the 903vl? The reason you didn't get the update for 6.0 is you have the 902l model. If you had the 903vl model you'd have 6.0. Straight talk never released it for the 902l model. No idea why being both models are very similar. Im not sure but if you make it back to stock on kitkat. I think you can use safestrap from the Verizon s5 to use some custom roms that run kitkat. If your bootloader is in fact unlocked and you can install a custom recovery other then safestrap. I believe you can install pretty much anything but I'm pretty sure straight talk ships the phones with the Toshiba chip so the bootloader isn't unlockable
Related
Hi everyone,
Before blasting away with comments as to why I would do this, here's my story,
I live in Canada and just brought home a i9508, a China variant of the S4. It belonged to my dad and he didn't want it so I just took it. The i9508 doesn't have Play Store, and it doesn't work on Canadian 3G network.
So to me, the phone is useless right off the start (don't intend on selling it either, who wants it?) So I had 2 options:
1) Leave the phone as it is, and probably use it once every 1-2 years when I visit HK
2) Flash custom roms on it fully aware of the risk it will have so that there's a possibility I can make it more usable
So in the end I went with option 2.
I followed a guide and flashed TWRP for i9505 using Odin onto the phone, and used TWRP to install chainfire SU, and it actually worked (but SU wouldn't open because some sort of security on the phone is blocking it)
Next step, I downloaded the CM version for i9505 and flashed onto the phone, and that worked too. Only problem I've encountered was that the phone would only boot after a fresh install. If I installed CM, turned the phone off after the initial start up, the phone wouldn't boot pass the Samsung logo.
Up until this point, I didn't make a backup, because of my arrogance, cause I have available a copy of the official firmware, in case anything happens.
So I figured at this point, maybe if I restore the original firmware, and try the whole process again, the custom rom would work. So I went into Odin, flash the firmware with PDA, and failed. It just wouldn't work. After retrying it a couple of times, and downloading different updates of the firmware, nothing worked. Only thing working right now is, I can get into Download mode, and I can get into TWRP recovery (but for some reason, I can't flash the zips that I've adb pushed onto the phone, zip can't open)
For me, if it can't be fixed, then it's really SOL. But if there's a way to fix it, I'm open to testing anything people have in mind, cause afterall, this phone is paper weight either way. I'm interested in seeing if I could enable 3G by flashing a i9505 radio, despite warnings, although, I've never actually came across a thread where someone had actually tried it before.
Either way, if someone has any idea on how to fix the phone, and wouldn't mind sharing it, that'll be greatly appreciated.
Working
I can get into Download mode, but Odin is failing (if you need the error please let me know and I'll post it)
I can get into TWRP recovery, but can't flash files
I can get into adb
This isnt the correct forum for your phone. XDA don't follow clones
Unfortunately a section for i9508 doesn't exist, so I figure the closest one would be i9505.
Anyhow, if someone has an idea of how to fix it, I'm more than happy to do testing on it, like flashing other roms or radios.
Hello everyone,
i am fairly new to the world of rooting and recently encountered a problem while flashing a rom
i have the at&t samsung galaxy note 3 N-900A running 4.3 jellybean (2 year contract expired and i got and used the unlock code)
i rooted the phone using the kingo root app, because i could not update the phone (I recently moved out of the USA so i cant connect to an at&t server to update)
i installed safestrap recovery 3.71 and it was running fine
i found a tutorial from galaxy note 3 root for the knoxraid ro
(put youtube. c o m here) /watch?v=8HDHt4xSnQY
according to the tutorial i had to install the rom over the stock rom file
so i copied the stock rom to rom slot 1
this is where i messed up, i installed the knoxraid rom over the stock rom without wiping/data factory reset first. But it gets worse, i realized i forgot to wipe the data from safestrap so before the install was even halfway completed, i pulled the battery out.
now whenever i turn it on it will go straight to recovery mode
it wont even turn off. i have to pull the battery out.
i can get to download mode and recovery mode but thats it.
im not sure about the build number because it wont boot up
all i can tell you is it is a at&t note 3 running 4.3 jellybean
please help if you can
btw: my computer wont recognize the phone because it says the PHONE does not have the correct drivers installed
however odin still recognizes it with the blue box with 0:[COM6] if that helps
so yeah please help me the phone is fairly new and i dont want to waste $600
infinitephase said:
Hello everyone,
i am fairly new to the world of rooting and recently encountered a problem while flashing a rom
i have the at&t samsung galaxy note 3 N-900A running 4.3 jellybean (2 year contract expired and i got and used the unlock code)
i rooted the phone using the kingo root app, because i could not update the phone (I recently moved out of the USA so i cant connect to an at&t server to update)
i installed safestrap recovery 3.71 and it was running fine
i found a tutorial from galaxy note 3 root for the knoxraid ro
(put youtube. c o m here) /watch?v=8HDHt4xSnQY
according to the tutorial i had to install the rom over the stock rom file
so i copied the stock rom to rom slot 1
this is where i messed up, i installed the knoxraid rom over the stock rom without wiping/data factory reset first. But it gets worse, i realized i forgot to wipe the data from safestrap so before the install was even halfway completed, i pulled the battery out.
now whenever i turn it on it will go straight to recovery mode
it wont even turn off. i have to pull the battery out.
i can get to download mode and recovery mode but thats it.
im not sure about the build number because it wont boot up
all i can tell you is it is a at&t note 3 running 4.3 jellybean
please help if you can
btw: my computer wont recognize the phone because it says the PHONE does not have the correct drivers installed
however odin still recognizes it with the blue box with 0:[COM6] if that helps
so yeah please help me the phone is fairly new and i dont want to waste $600
Click to expand...
Click to collapse
Well, this is the wrong forum to begin with.
However, head over here, http://forum.xda-developers.com/showthread.php?t=2703006 , and read very, very carefully.
sirobelec said:
Well, this is the wrong forum to begin with.
However, head over here, http://forum.xda-developers.com/showthread.php?t=2703006 , and read very, very carefully.
Click to expand...
Click to collapse
sorry, next time ill post in the right forum
thanks for the link, however this appears to be for the N900AUCUCNC2 variant, which i believe is KitKat (sry if im wrong) i need files for 4.3 jellybean firmware. (i never updated)
thanks in advance
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.
I have tried everything I can possibly think of in a short period of time, and need an answer in a hurry. The phone (Verizon Samsung Galaxy Note 3 N-900V) was rooted back when kitkat was the main OS using geohot's towelroot (or possibly kingo root I can't remember which i used after I got the phone and upgraded from ICS). I have 2 of these exact same phones, used the exact same rooting method, and unrooted by uninstalling the superuser app, rebooted, and installed the OTA update to lolipop. My phone works fine, (the one I'm typing from) however, my other phone decided to take a dump. It's a software bug between the samsung firmware and the new lolipop OS. It was working for several months, then all the sudden it wouldn't recognize/register the APN. Now it doesn't see anything just about with the phone. Not even the IMEI from the phones serial number. The sim card has been replaced twice and has worked for a matter of a few hours, however, upon restarting the phone, it goes back to no service, and nothing is registered or recognized. I reflashed the phone with the stock 5.0 Lolipop using Odin several times to no avail. My phone (one I'm using now) once did this months ago, and I was able to access the service menu and reregister the SIM card and phone has worked fine since. With this other phone, I can't get into the service menu at all because nothing is registering. So, after reflashing 4 or 5 times, factory reseting from both the OS and from recovery booting, it still has the same issue. Here is my question. It used to be when I reflashed, the custom padlock would disappear. I'm getting a new phone tomorrow, and I need to get rid of the custom padlock before I return the old phone. I can use Odin, or whatever but it has to be something, I can do while it stays stock. The knox counter has not been tripped, and the flash counter is not tripped nor showing anything on the download mode. Everything lools, and feels stock, except that custom padlock. Is there a way to get rid of that custom padlock unrooted, by reflashing? I even used a pit file to repartition, but that didn't work either. Need help A.S.A.P.!
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Hard Brick
xxperrin said:
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Click to expand...
Click to collapse
You thinking maybe a NAND erase?
Hard Brick
I've thought about flashing the wrong rom too but dunno if that will work 100%. I either need to fix it, or make it 100% unrecoverable. Any advice?
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?