Database Users

[Help] OMG! Did i Brick my new note 3!? :(

Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.

Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?

Journyman16 said:
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Click to expand...
Click to collapse
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?

jthornton71707 said:
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
Click to expand...
Click to collapse
Go to Sammobile and see if you can find the version you had, sounds like an older JB if kingo app didn't trip Knox. Reflash that using ODIN.
I don't know if there was a problem with American bootloader, see if there's an AT&T Note 3 forum. Might find answers there...

jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/show....php?t=2701062
it's a way to unbrick your software.
and if the older owner of your N3 said it's on the latest firmware of kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps

Ik Knox is 0×0,then u can try samsung service centre ?
Sent from my SM-N900 using XDA Premium 4 mobile app

[Q]SOLVED Noob GT-I9505 WIFI dead after upgrd 4.4.2 searched and tried all solutions

First of all please forgive me for opening yet another S4 wifi problem after kitkat upgrade, but I have tried everything I could possibly find here, on youtube and other forums. The only thing left to try is flash the modem but I'd rather ask before I brick my phone
I'm not quite sure if this is the same issue every single time or if in my case it is due to my ignorance and errors. I was an iphone/unlock/jailbreak user until last year so please bear with me. Android is new and fun (but scary) territory to me.
Situation, what I did and possible mistakes on my side:
-I'm in Spain but I bought my factory unlocked phone on amazon and it was for the Polish market (GT-I9505 Black, 16 Gb)
-My device was rooted don't even remember how I did it last year so no useful info on that side a part of using odin for windows.
- Until yesterday I was on jellybean, not quite sure if 4.2.2 or 4.3
- Yesterday I upgraded to 4.4.2 via mobile odin and yes I checked the boxes about clearing/deleting cache or whatever it's called.
- Used a stock firmware downloaded from other site (that one starting with "S" and with a great amount of firmwares for samsung devices of several countries)
- I chose a firmware randomly (maybe this was my mistake) because I hade read that the firmware was not that important and people where usimg leaked german firmwares on on phones from elsewhere. But I did choose one that matched the country of my phone (XEO/XX Poland)
- Everything is working fine but without wifi I'm buying new Mb bundles almost every 2 hours and I'll be broke very soon
If you guys think the solution is flashing the modem which file should I use? I see lots of them with different models/codes and I'm completely lost and have read a lot about messing with bootloaders/modems etc bricking devices so I'm freaking scared and ask for your charitative help!
All the info I could gather about my device right now (now I know I should have gathered this info also before attempting to upgrade but it's too late now!
SAMSUNG GALAXY S4 GT-I9505 Black Edition
Manufacturing date: 2013-12-23
BASEBAND Version: I9505XXUEMK8
BOOTLOADER Version:I9505XXUEMK8
PDA Version: I9505XXUGNG8
CSC Version: I9505YXZGNH2
Kernel: 3.4.0-2309103
KOT49H-I9505UGNG8
Android 4.4.2
Product code: GT2I9505ZKAXEO
Original CSC: XEO
Firmsware's CSC: XEO
Active CSC code: XEO
CSC Country: Poland
Any help would be greatly appreciated, I feel so dumb and frustrated right now that any joke or insult would be accepted with humbleness lol

Forgot to add I used the *#0011# command and went to wifi menu. Tried the ping test and it states: passed
status: DISCONNECTED
SSID: Unknown SSID
( In case this info is of any use )

voxel.xyz said:
Forgot to add I used the *#0011# command and went to wifi menu. Tried the ping test and it states: passed
status: DISCONNECTED
SSID: Unknown SSID
( In case this info is of any use )
Click to expand...
Click to collapse
Relax it has solution . The problem becomes coz the baseband and the bootloader are olds (android 4.3).
SAMSUNG GALAXY S4 GT-I9505 Black Edition
BASEBAND Version: I9505XXUEMK8
BOOTLOADER Version:I9505XXUEMK8
PDA Version: I9505XXUGNG8
CSC Version: I9505YXZGNH2
* Quick solution for recover WIFI:
1. Reflash the STOCK I9505XXUGNG8 (XEO) firmware via ODIN.
2. Let the process finish and reboot normally.
3. Dial *#1234# and have to appear this:
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505YXZGNH2
4. Reflash again if not. Good luck

Thank you so much for your helpful reply Joku1981 !!!!! You made my day!!!
Can I do that with Mobile Odin??? My PC broke (Graphics card burnt) and until a couple of months won't be able to buy a new one.
To make sure I understand you: You mean Flash again the same firmware I used to upgrade to 4.4.2 in the first place?
I used this Firmware: I9505XXUGNG8_I9505YXZGNH2_XEO
should I try Flashing that same Stock Firmware again? and if does not work keep reflashing until the baseband and the bootloader get updated?
Why did they not update ? is this common or an error on my side???
I hope it can be done with mobile Odin since I can keep my root status, If I have to do it in Desktop Odin do I have to Re-Root after flashing???
Thank you so much for you kind help!!!!!!
Joku1981 said:
Relax it has solution . The problem becomes coz the baseband and the bootloader are olds (android 4.3).
SAMSUNG GALAXY S4 GT-I9505 Black Edition
BASEBAND Version: I9505XXUEMK8
BOOTLOADER Version:I9505XXUEMK8
PDA Version: I9505XXUGNG8
CSC Version: I9505YXZGNH2
* Quick solution for recover WIFI:
1. Reflash the STOCK I9505XXUGNG8 (XEO) firmware via ODIN.
2. Let the process finish and reboot normally.
3. Dial *#1234# and have to appear this:
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505YXZGNH2
4. Reflash again if not. Good luck
Click to expand...
Click to collapse

SOLVED!!!!!
After nobody answered if I could use again "mobile Odin" to flash once more and try to fix my wifi not working I opened mobile odin and it gave me a warning about my version and having a wrong bootloader as a possibility of soft bricking my phone so I decided to stay away of mobile Odin this time.
I used desktop Odin (at work since my pc broke) and exactly the same firmware file downloaded from sammobile (but re-downloaded it just in case) and had to flash twice, the first time it went through the whole process ok right until the end where it showed the FAIL message.
I didn't know if I should turn off the phone stuck in download mode and with the process bar at 100 % or retry flashing without turning it off. So I decided not to turn it off (afraid it would get soft bricked or something). I closed mobile Odin but left phone On with download mode screen active and opened mobile Odin again got the "added"message and the blue color showing it was properly connected to the phone and started flashing process again....
I started getting red error messages saying the progress bar display was wrong (and it wasn't updating/kept stuck in the previous 100%) but after it finished it was flashed and everything was ok. WIFI WORKED!!!!!!
Now the weird part.....in case this happens /helps someone else:
- My phone DID NOT get wiped. My launcher and my apps stayed intact (I thought flashing even the same firmware always wiped data, I'm I wrong???)
- All my root apps (root explorer, titanium backup, so on and so forth) where there and working fine. One root checker stated I was rooted and another one stated I wasn't but even my launcher (nova) was working just as if I never flashed the phone.
- Since I was unsure of my "root" state and I did not have "supersu" app in my apps drawer I tried installing it via playstore but It always gave an error message (the application could not be installed in the default location)
- I rooted again just in case and the root process finished without errors but still I had no "supersu" app and one root checker said I was rooted and the other I wasn't. Tried installing "supersu" from the playstore but same error and could not get installed.
- I searched here and in other forums for similar problems/solutions but nothing worked until I tried several things that fixed the problem. Not really sure which fixed it so I will write them down in the order I did them:
1. Opened folder mount which I already had installed and it gave me an error and asked me to try the fix which I did.
2. Opened linked2sd which I already had installed also previous to the firmware flash. It gave me an error and asked me which was the partition to use (as when I first installed it) in my case it was ext4. And it seemed to start working as it normally does. No further error when reopening it.
3. Rebooted the phone and tried entering recovery mode to wipe cache etc but It never entered recovery mode. I get the message about going into recovery mode (top left corner small red letters) But right after that it reboots and I get the samsung logo and my home screen.
4. Tried reinstalling supersu again and no success. (By the way before I did all this steps I tried rooting again but got to the same point. No supersu on my apps drawer)
5. Downloaded BusyBox install (opened it but did not use it in any way, maybe something in the installation fixed my problem)
6. Opened mobile Odin just for curiosity sake and it opened fine and asked for downloading of the extra stuff as when I installed it the first time. After that I closed it
7. Rebooted normally (no recovery mode since I'm stuck without it)
8. Tried installing "supersu" and NOW it worked!!!
9. Checked in both root checker apps and both confirm I'm rooted and supersu started asking for granting permissions to apps again as it normally does!
10. Everytime I attempted flash, root, and even after some reboots I took the battery off (since I read in several threads it helped/was mandatory)
Conclusion now my WIFI problem is fixed, my root problem (that appeared doing the reflash for fixing my wifi problem) is also fixed. The only thing I could not fix is not being able to get into recovery mode.
Does anyone know a solution for recovering the ability to get into recovery mode????
Thanks to Joku for lighting me into re flashing once and again until my wifi was fixed!

Back button not working after software update?

Hi everyone. I just flashed back to stock (Koodo official firmware) to sell my Note 3 and now my back hardware button isn't working. I have searched the web and to no avail. Could someone please give me an idea of what I can do to fix this? Thank you!!

Which note 3 is it?

SM n900W8

I have the same model. I haven't used it for a while. I powered it on a few days ago to take the update from doc4 to doh1. I just tried the back and menu buttons using the doh1 ROM and they seem to work fine.
A friend of mine has the same phone and he flashed the doh1 ROM from sammobile.com over a rooted doc4 RIM and he also has no problems.
Both of us were using custom ROMs with a 4.4.2 bootloader and we both flashed back to stock using sammobile.com's doc4 ROM before moving to doh1.

I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!

Glad you got it fixed but I'm not sure I was much help.

Partially solved..
Hi.
I have done everything trying to solve this and can confirm the next:
1st: If you go back to Kit Kat, the capacitive buttons start to work again. Then you are offered a couple of OTAs (one after the other to get you to DOH1). After the first OTA, the buttons stop working again.
So first solution: stay on Kit Kat (probably not what we want).
2nd: Flashing a custom Cyanogenmod based firmware works, I used latest temasek's build, I am testing it to see if I can keep it.
3rd: I tried erasing almost every single partition (system/cache/dalvik(art?) cache) and flashing from scratch DOH1... wont work.
According to what I have read all around there is a system file that controls the capacitive buttons, probably that file is getting weird with the upgrade, I still need to install a official rom, root it and try to edit such file.

It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.

audit13 said:
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
Click to expand...
Click to collapse
I wasn't running anything custom. I was on Official ROM (no root no anything, just Stock Samsung Software) as always with my Note 3. It was just that the DOH1 update make the damages.
Now I think I gotta stick to Cyanogenmod given this problem, unless Samsung says something and fix the thing.

Does this happen with TW-based custom ROMs too?

Dont know. As of now, I am trying to flash DOH1 again on top of KitKat 4.4.2

[/COLOR]http://www.askmefast.com/I_have_a_n...art_any_idea_what_can_be_done-qna1982335.html
They say clearing the Cache of the Samsung Keyboard fixes the thing. Wont be able to test by myself til tomorrow

Edited
I have N900W8 bell version, using it on Virgin network.
worked flawlessly with KitKat (either with Bell or Virgin version).
I've only experimented with Note-based custom roms (KitKat only), since I need the pen functionality.
First attempt:
I have experienced the same, not properly working menu button and not working back button.
I was on rooted stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version), rooted with Chainfire CF-auto root (Build ID:KOT49H.N900W8VLUCNB7) using Odin. (all the buttons working properly)
Upgraded to Lollipop 5.0 (N900W8VLU2DOH1) with Odin, rooted same way with CF-auto root (Build ID:LRX21V.N900W8UBU2DOL1). (Buttons do not work)
Second Attempt (No rooting involved what-so-ever):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version, clean flash), all the buttons working properly.
Did OTA update through Wifi to, assuming, N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
For both of above attempts, buttons are working properly with KitKat, whether it was rooted or not, and not with Lollipop, whether it was rooted or not. I'm thinking it's just the lollipop issue.
Third attempt (using N900W8VLUCNB7 Firmware Bell version):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Bell version, clean flash), all the buttons working properly.
Did OTA update through Wifi to N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)

wy2sl0 said:
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Click to expand...
Click to collapse
Do you have the link for the stock Tom zip?
Sent from my SM-N900W8 using XDA Free mobile app

Ok. Pretty much tried everything while staying on stock firmware.
However, everything else seems to work okay other than the touch button.
So now im gonna root the stock lollipop and use xposed and gravitybox to manually remap the 2 touch keys. Will update

Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.

rocked_out said:
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
Click to expand...
Click to collapse
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.

SS604 said:
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
Click to expand...
Click to collapse
Hey , has anyone firgured out how to get rid of the "unfortunately Knox has stopped working" ? I had the same issue with the softkeys not working. This fix works but I get this message. I was also told to try flashing a PIT file with stock firmware to fix the softkey issue, but this did not work.

Maybe flashing supersu from TWRP will allow supersu to disable knox?

not to bring back a dead thread, but this is exactly what I needed. I needed to root to fix screen mirroring so I just used root uninstaller to delete knox.

Samsung Galaxy Note 4 SM-N9109W (China) Bootloop - No Access to Recovery

Hello everyone, I'd like to start off by saying I am a complete newcomer to all this so please explain literally all of the terminology/jargon you intend to use and correct me when I use it wrong.
I have a Chinese version of the Samsung Galaxy Note 4 SM-N9109W and up until yesterday it was running out of the box on android 4.4.4. I care not for any of the data on the phone nor the warranty as there was none to begin with when it was gifted to me.
I attempted to "root" it as I didn't want any of the Chinese apps/restrictions on it but have failed miserably and now my phone is stuck in a bootloop.
I was following this guide if it helps: http://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948 and downloaded the appropriate Snapdragon version (SM-N9109W).
I cannot enter recovery mode by holding down *power+vol up+home* as it just keeps on rebooting. I can, however, get into the downloader by holding down *power+vol down+home*.
I have tried for the entirety of today to find a specific guide for the Chinese note 4 on xda, youtube and google but to no avail - nothing that I can find is identical to my situation and I am hesitant to do anything further to it by following a similar guide in case I make it worse.
I have repeatedly seen suggestions to "flash" stock rom and as I can get into the downloader I believe this would be a great starting point, but once again I am afraid to do anything without a specific guide for the N9109W.
A few people have referred to SamMobile to download stock rom, but a search for SM-N9109W lists 8 files for 4.4.4 and I believe I have no way of working out my PDA or CSC, yet again I don't know what these even are and they might not be relevant?
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience,
Ryan

If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.

ithehappy said:
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
Click to expand...
Click to collapse
Thank you ithehappy for the reply,
When I search for the stock firmware on SamMobile, I type in my exact model number (SM-N9109W). This search returns with a list of multiple different versions for my phone, of which 8 are 4.4.4 (my initial version).
Does it matter which version I download and install?
To my knowledge, I have no way of finding my CSC or PDA unless you know of a database I can use to search the information that is physically on my phone? Once again, does it matter that I know what these are or can I simply download, for example, version 5.1.1 and flash that on instead of my original 4.4.4? Or, will this just cause further possibly unfixable problems?
Thank you for your help

Anyone?

No, you can download any one you want.

Thank you for the help, ithehappy. I now have a working phone!
For future readers, I downloaded the latest version of 4.4.4 that SamMobile had (2015-03-27) for my model (SM-N9109W):
PDA: N9109WKEU1ANL3
CSC: N9109WCTC1ANL3
It failed the first time I tried flashing with Odin 3.10.7, but whilst I was hastily taking screenshots of my problem to post here I accidentally started the transfer again and it successfully installed that time.
I followed the instructions on SamMobile for the installation.
This version of the firmware I installed does not have any google services (thank China for that), so keep that in mind.
Thank you

"Sim card removed" error with CM 12.1 on Samsung Galaxy S4 GT-I9505

First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound

undersound said:
First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound
Click to expand...
Click to collapse
1) Yes, of course.
2) No.
3) Don't know what you are talking about.
Odin is used to flash stock roms on Samsung devices. That is the only way.
There are links to guides in the help thread in the Q&A section.

Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk

jimmyoh said:
Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this

undersound said:
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this
Click to expand...
Click to collapse
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.

GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Click to expand...
Click to collapse
That's good to know, thanks. I was trying this with an extended usb cable so it can be the definitely the case.
Will try later today with a direct connection to a backport.

GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.
Click to expand...
Click to collapse
Managed to return to stock firmware, yay!
In case it helps someone else, here are my steps:
1. By dialing *#1234# on a similar phone I checked what ap/cp/csc version I needed
Code:
AP: I9505XXUHOF2
CP: I9505XXUHOF2
CSC: I9505OXAHOF2
2. Downloaded the correct firmware image (http://www.sammobile.com/firmwares/download/50091/I9505XXUHOF2_I9505YHNHOF2_PHN/)
3. Extracted the firmware file
4. Opened Odin v3.10.7
5. Rebooted Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6. Connected phone and waited until I got a blue sign in Odin
7. Added the firmware file to AP / PDA
8. Made sure re-partition was NOT ticked
9. Clicked the start button
10. Then I got a PASS!
So I guess there can be 2 reasons my first attempt of flashing stock firmware did not worked:
1. The firmware I used the first time was not correct for this phone (http://www.sammobile.com/firmwares/download/64897/I9505XXUPOL1_I9505PHNPOL1_PHN)
I did not know at that time about checking my ap/cp/csc described in Step 1 above so I was just downloading the firmware which seemed the most appropiate according to the country / provider.
What helped me a lot was when I found the explanation of the parts of the version number:
Code:
I9505XXUHOF2
I9505 = phone model
XX = country/region code
UHOH2 = modem
2. The second attempt I followed GDReaper suggestion and I used the usb cable directly on of the backports of my pc so that could have helped as well.
Another thing that was not clear to me at first were the providers code. Or well, they were clear to me that they were abbreviations for telecom providers but I did not bought these phones from a provider so I was not sure which one to pick. After a while I came to discover that I needed PHN which means Unbranded
Code:
---------------------
PHN = unbranded
TNL = Tmobile
VDF = Vodafone
Thanks all for the help