yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] cougar214:
Hey guys. I'm having major problems with my signal. Let me start at the beginning. Two weeks ago my phone started to act funny and the battery wasn't holding a charge. Then the charging port wouldn't make a connection. So I ordered a new battery and charging port. The battery came in a couple days ago and is charging fine, when the port would make the connection, and the charging port came in yesterday. I changed the charging port out and everything went smoothly. I triple checked every connection before I reassembled my phone. Everything was good. But now my signal is very weak in my house as of yesterday afternoon after replacing the port. This morning I wake up and I have no signal at all. Just the circle with the line through it. I heard that the antenna wires are very easily damaged when changing out these charging ports but I have signal, at least yesterday when I drove into town, down the road from me and it is strong. If I damaged the antenna wire somehow wouldn't I get no signal anywhere?
[Galaxy S III Mini Q&A, Help & Troubleshooting] silencar:
Hi,

since I own a S3 Mini I am into this board and the great custom roms here .. :good:

but what I still don't get: how close are the custom roms to the stock rom.

for instance:

stock for S3 mini is 4.1.2 - kernel 3.0.x?

custom roms: 4.2.2, 4.3.1 and 4.4.2 - all (maclaw roms) use the same kernel 3.0.101

but 4.4 uses linux kernel 3.3 or 3.4?

so what does this difference in the kernel versions (3.0.101 to 3.3) mean? Isn't it like using windows 95 with a windows vista or windows 7 theme?

dont't get me wrong, I love the custom roms! Using the slimrom of maclaw and like it a lot. Just wanna get it right in my head :silly:
[Galaxy S III Mini Q&A, Help & Troubleshooting] efaustino84:
custom ROM do not have any sammy related features
[Galaxy S III Mini Q&A, Help & Troubleshooting] silencar:
sammy = samsung?

thx but .. my question wasnt samsung related, more android version and the technical differences behind all that related
[Galaxy S III Mini Q&A, Help & Troubleshooting] eswarvf:
kernel version is same as linux version but according to maclaw there is not much change b/w 3.0.1 and 3.4.x
[Galaxy S III Mini Q&A, Help & Troubleshooting] AssToast:
I dont really know what are the changes in the different kernels but think of them like software updates, there may be tweaks, fixes and new features

All we have is 3.0 is because there are only 3.0 kernel sources and STE died and are not releasing kernel sources anymore
[Galaxy S III Mini Q&A, Help & Troubleshooting] silencar:
Hi,

thx for the information!

i've just read about the "STE" thing. Is it the "munjeni" - "story" in the Sony Xperia thread in this board and the legality of using leaked source code?

What a pity :(
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] kenhicg:
I was wondering if anyone has found a way to get snote to sync or share to onenote. I know you can share to evernote and gdocs but I dont use those services.

life is better with r00t
[Galaxy Note 3 Q&A, Help & Troubleshooting] mali76:
I rooted my note 3. Then installed cwm recovery through odin 3.09. Then i tried to install two different custom roms,one is 4.3 other is kit kat, using cwm recovery. They both installed succesfully but after installation i reboot and it freezes at samsung logo. Also i tried an official russion rom using odin 3.09. It opens but this time it always gives keyboard stopped working error. What must i do. I cant install any rom. Please help
[Galaxy Note 3 Q&A, Help & Troubleshooting] vrgolin:
sorry by my inglish, i will try to explane...I can see what you say, tahat you didnt flash tho csc file , that why you have that keyboard error.. you can solve that by conecting some bluetooth keyborad to your divice , and with that keyboard try to write the fields to get to playstore an donwload another keyboard for your divice like , donwload another one from playstore like swifkey, once u donwload the keyboard selected insted samsung kerboard
[Galaxy Note 3 Q&A, Help & Troubleshooting] mali76:
But i flashed scs. No way. And also i cant start any custom rom after installing throughh cmw recovery
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
So you flashed Kitkat 4.4.2? -- N900 or N9005? -- reflash your Stock ROM - need to be 4.4.2 now since you tried previously.
[Galaxy Note 3 Q&A, Help & Troubleshooting] mali76:
Yes kitkat 4.4.2. N900. I can install succesfully using cmw but after rebooting it freezes at flashing samsung logo
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Use Odin to flash stock ROM
[Galaxy Note 3 Q&A, Help & Troubleshooting] mali76:
Where can i download stock rom?
[Android Q&A, Help & Troubleshooting] Predrag_Sobota:
I have question about ROM for HD mini(Photon)..How i can install that ROM,when i download it i got _MACOSX ; META-INF ; system and boot.iso file.What to do next?Please answer,i need it..Sorry for bad English.. :rolleyes:
[Galaxy Note 3 Developer Discussion [Developers Onl] DDRFAN:
I'm not too sure if this is helpful, but with the introduction of Kitkat, the SM-N900W8 has been able to flash a custom rom/kernel and recovery without tripping Knox. I am really not sure how this is possible, but my phone is living proof of it. To my understanding we are still using the old bootloader.
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
(reserved for the future, I just had a very large edit on the top post and not very much extra data can fit there)
[Galaxy Note 3 Developer Discussion [Developers Onl] CNexus:
Just a note [MENTION=4901283]xclub_101[/MENTION]...you cannot write older/different bootloaders using the debrick method. gTan64 and I originally pioneered that method on the Sprint S3, and it was then ported to the other qualcomm S3's, and eventually to other Samsung devices.

It does not work. The phone will only boot with a debrick sdcard when the bootloader written to the sdcard has the same version as the corrupt one on the device emmc.

And even if an older bootloader sdcard COULD boot the device, it wouldn't matter because you would still need to Odin flash a non-corrupt bootloader to the device after using the sdcard, and it would still reject a non-Knox bootloader because of that.

So unfortunately that section is incorrect.
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
I can downgrade P1 to P0. It is device and carrier specific. I'm not sure what the P flag is for. RPM, SBL1, and TZ were only items modified when downgraded. All signed releases. Looking for any more information regarding these flags.
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
That is somehow true, but IMHO if all relevant partitions are wiped on the internal flash (from SBL1 to ABOOT) then all those will be read from microSD and have the code and signatures from there, and the "Odin mode" itself will be the version from microSD.

And here we have a number of interesting paths:

- the signature/hash on SBL1 itself is similar among Note 3 versions - that would result on all steps up to and including ABOOT being valid, so the "special Odin mode" will be entered; if the signature/hash on SBL1 is NOT similar between Note 3 families (or even before and after a major bootloader version) not even the "special Odin mode" will be started;

- if "special Odin mode" is started we can see another fork - if the "downgrade limitations" are part of the microSD code itself then you will be able to write any single firmware you were able to write when the internal SBL1/ABOOT was at the same version as the microSD SBL1/ABOOT - in other words you will be able to downgrade as far back as the microSD SBL1/ABOOT will let you!

- however there are some reports that the "downgrade restrictions" are actually stored in the internal flash in the "invisible/protected" regions there - and can be reset with special JTAG-like hardware:

http://forum.gsmhosting.com/vbb/f672/regarding-knox-s4-1775213/

Even in that last case there would still be a small chance that the "downgrade restrictions" might be skipped when booting from microSD since the internal flash could be considered at that point "less reliable" (or hopefully somebody at Samsung forgot to read that extra info on this special path - we can all hope :rolleyes: )

So yes, I would still like to see more detailed tests on it with detailed reports on what is failing at what point! And especially on the microSD with the N900W8 "happy bootloader" or even with some much earlier "early development bootloader" (I have seen something like that mentioned somewhere)!
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
That was on the Verizon N900V? Does that allow you to do direct downgrades or you still need some tricks? Was it still booting with the downgraded versions?
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
Downgrading is limited to the flag fuse counter values. On MJE, I can downgrade to MI9 boot image and recovery. I was able to downgrade to some pre-release engineering SBL1, RPM, and TZ because they're signed and fuse counter is only 1 for those 3. It's very benign and basic to downgrade. Just use heimdall and try downgrading an individual image. If I figure out what P is, I'll be able to test if I can flash anything related to that flag. For some reason, I can downgrade to MI9 boot and recovery, but not the system.img. I'm just starting to learn a lot about the flags/fuse counters after dissecting aboot further. If you've got any more specific questions, feel free to PM me :)
[Galaxy Note 3 Developer Discussion [Developers Onl] iamsuperuser:
For the past 2 weeks I've been following the topics on Knox reset on XDA. There is so much discussion but Samsung is not at all helping.

So I was thinking we can do something like Sony Phones

On Sony Phones the trim area i.e. TA.img is backed up to restore later to claim warranty, but this should be done only before the phone is ever unlocked.

So are there any files like TA.img on Note 3 we can backup while the Knox is still 0×0 , So that if and when there is a method to reset Knox we can be ready.

If we can do this, we can go ahead and root or mod our Note 3s

So is this possible ?
[Galaxy Note 3 Developer Discussion [Developers Onl] FeralFire:
I don't think that will be possible because knox flag is an e-fuse and not a software counter.

I may be wrong, though.
[Galaxy Note 3 Developer Discussion [Developers Onl] AndroidNoob22:
I somehow might agree to you but there's one thing about Knox which is not understandable by any means, Knox was officially introduced in Note 3 (Android 4.3) however other samsung devices had never had any hint of Knox hardware or software wise so while the official android 4.3 started rolling for other devices ie galaxy s4, note 2 etc they also got Knox and once they're tripped they cannot be reseted however I belive this should not be the case as those devices never had such thing as Knox specifically in terms of hardware and this trick has been surely done by samsung software wise and the only way to reset Knox as f now is known by samsung as few people have reported they got their Knox reset from samsung service centers, so this is kind of strange and I still believe Knox can have something to be done with software n not hardware, though I aint sure about it.........
[Galaxy Note 3 Developer Discussion [Developers Onl] siraltus:
It's implemented differently on different devices. From what I've read here and on other forums, this is why:

On Note 3 Snapdragon models, the warranty bits for the kernel and recovery are actual e-fuses stored in the QFUSE block of the Snapdragon MCU (SoC), so they're "hardware" and thus permanent. EDIT: Apparently it's not permanent, as many Snapdragon owners had the Knox flag reset during service.

On Note 3 Exynos models, they're stored in the RMPB partition on the eMMC and resettable via JTAG, as they're more or less "software," which is how it's likely implemented on the older pre-Knox devices. This is also why some European Note 3 owners got their broken Note 3s back from Samsung with the Knox flag reset back to 0x0. This isn't possible on the Snapdragon models.
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
The part on Exynos models is probably right since now there is a device that claims to do that - see my link in the first post.

The part with Qualcomm models is not 100% so - there are TONS of reports from people with Qualcomm models (not only N9005 in EU but also ALL T-Mobile models) that had their knox fixed on the same motherboard (and in most cases with ALL their customized software left in place). See also my links in the first post.
[Galaxy Note 3 Developer Discussion [Developers Onl] siraltus:
Oh, really? Awesome then, I had no idea. There is hope for us Snapdragon owners after all.
[Galaxy Note 3 Developer Discussion [Developers Onl] radicalisto:
My motherboard was replaced, that's the only way KNOX can be reset according to the UK service centre I used.
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
P flag appears to be tied to SBL1. Was able to downgrade SBL1 by itself via Heimdall. Not sure how and why. More research needs to be done.
[Galaxy Note 3 Developer Discussion [Developers Onl] st3chn0:
I don't believe that is true. I have compared my flags with other stock btu with the same bootloader and firmware all my flags other than that my P flag is still 0

Also OP needs to recheck the sources regarding knox reset these are for warranty bit on the s4 (android 4.2.2 and below) the supposed claim of knox reset only resets the flash counter. Similar to what triangle away has done in the past
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
I don't understand what you are saying, you claim that the two threads below are for S4?

One thread in T-Mobile Note 3 forum:

http://xdaforums.com/showthread.php?t=2637718

And a much larger one in International Note 3 forum:

http://xdaforums.com/showthread.php?t=2504258
[Galaxy Note 3 Developer Discussion [Developers Onl] st3chn0:
Sorry I meant the links pointing towards gsmhosting. Those are perfectly fine
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
Those are 3 links since I also wanted to keep some of the "history" on how that was discovered/announced, but the 3rd link is from the guy that actually sells the box and from what I see is saying:

"What this mean ? After replacing or WIPING eMMC and burning old bootloader on device with (KNOX Warranty: 0x01 ) You will get device with unknoxed boot and KNOX Warranty bit 0x0"

And then there is a long list of Exynos devices that are supported, including

Samsung SM-N900 Galaxy Note 3

Samsung SM-N9000Q Galaxy Note 3

and then a separate (and partial) list of the Snapdragon models that are NOT supported.

I have not tested the box personally and that is why I wrote from the very beginning in my original post "claims to be able to reset the knox flag on Exynos devices".

And to finish with that box and the claims they still make on Snapdragon - if they get (in a very controlled and non-destructive) way to remove the downgrading restrictions from the bootloader I think it might still be an interesting achievement - since that way you could revert any device with knox 0x0 to MI7, root and then go to whatever 4.3 or 4.4 you want. But of course that even in that scenario you need that box :) And on the longer term IMHO that same box might be able to reset knox on Snapdragon - yes, part of knox is in the qfuses but the final flag seems to be computed from that and some part in RPMB (which explains how Samsung resets that flags) - the really difficult part will be to find the way how the above is computed!
[Galaxy Note 3 Developer Discussion [Developers Onl] RaluSiCris:
android 5.0

did anyone tried to flash on 9005 4.3 over the 5.0 leackage?
[Galaxy Note 3 Developer Discussion [Developers Onl] Saipro:
I always run into Invalid IMEI/no signal problems when downgrading to 4.3 (JB) from 4.4.2 (KK). Tried everything in the book. Even KNOX resets with ease. The only thing which works is restoring EFS and MODEM/RADIO from my N900XXU**** backup. Of course I'm once more plagued with dropped signal strength and GPS issues ince I do that.

http://xdaforums.com/galaxy-note-3/general/how-to-roll-5-0-4-4-to-4-3-sm-n900-t3018333

ANY USEFUL help would be much appreciated
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
Are you flashing modemst1/modemst2/EFS at all?
[Galaxy Note 3 Developer Discussion [Developers Onl] JagiChan:
I understand that this method works only on Note 3, but since you have an S4, would you try if knox can be reset using this bootloader on the S4.
[Galaxy Note 3 Developer Discussion [Developers Onl] Product F(RED):
Don't EVER flash another device's bootloader to a different phone. You'll end up with a hard brick.
[Galaxy Note 3 Developer Discussion [Developers Onl] dhanmohan:
will this work on kitkat N900DDENG1 baseband?
[Galaxy Note 3 Developer Discussion [Developers Onl] jimbomodder:
Will this work on i9195?

Sent from my GT-I9195
[Galaxy Note 3 Developer Discussion [Developers Onl] sriram231092:
I tried this and Knox has been reset and the current binary is official too. But the system status still shows >>CUSTOM<<. I flashed the firmware for 4 times and wiped data&cache every time! But still it stays custom! Is there anything I could do?
[Galaxy Note 3 Developer Discussion [Developers Onl] st3chn0:
System status will show modified if you have rooted or tampered with system files. Only way to go back to normal is to flash stock
[Galaxy Note 3 Developer Discussion [Developers Onl] Joker87:
With wanam there was a fix to get it back to official
[Galaxy Note 3 Developer Discussion [Developers Onl] jimbomodder:
How exactly ?

Sent from my GT-I9195
[Galaxy Note 3 Developer Discussion [Developers Onl] Joker87:
Fake system status
[Galaxy Note 3 Developer Discussion [Developers Onl] sriram231092:
Hey! Thanks for the reply. The system status showed custom on the download mode but after booting, it actually showed official under system status. :)

---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------

Hey! Thanks for the reply. The system status showed custom on the download mode but after booting, it actually showed official under system status. :)
[Galaxy Note 3 Developer Discussion [Developers Onl] besotsima:
will this work on lollipop 5.0?
[Galaxy Note 3 Developer Discussion [Developers Onl] toastido:
All, this is an actual developers section, not a Q&A nor a users thread. Unless you're involved in actual development, you're in the wrong place.
[Galaxy Note 3 Developer Discussion [Developers Onl] al33m:
Hi Guys,

I flashed a custom rom on my new device SM-N900 using TWRP. When I wanted to revert to the stock firmware using ODIN I getting an error saying 'Power Reset or Unknown Upload Mode'.

The flashing of stock firmware is successful using ODIN but when rebooting I am getting the same error. I have tired doing everying I could searched XDA Note 3 forum, other sites as well but nothing worked.

I have even tired the below procedure to get mobile in to working condition but everything failed.

http://xdaforums.com/show...1#post52329946
[Galaxy Note 3 Developer Discussion [Developers Onl] melliwuk:
possibly stupid idea, possibly not...

this isn't the first knox reset thread ive read thru, other one was over 1000 posts! but one thing I haven't seen mentioned in ANY of the posts is if someone tried decompiling/resourcing the knox apps? after all they HAVE to check the knox flag to know whether to allow knox to run or not...

so surely there MUST be something in one of the apps that would point to where to check for the status of the knox bit???

if its a stupid idea please forgive me but it thought it might help.

Melli.
[Galaxy Note 3 Developer Discussion [Developers Onl] Muthumbi:
Note 4 N910H

Is there any way to port this file to not 4?
[Galaxy Note 3 Developer Discussion [Developers Onl] xda_Noob.:
Any progress ?
[Galaxy Note 3 Developer Discussion [Developers Onl] Astrubale:
Can it be possible with S6? Because it has Exynos.
[Galaxy Note 3 Developer Discussion [Developers Onl] Anoopvs2012:
Please tell me how to knox back in galaxy J700F exynos ????
[Galaxy Note 3 Developer Discussion [Developers Onl] headdoggy:
Has someone managed to utilize TrustZone exploit on Samsung devices?
[Galaxy Note 3 Developer Discussion [Developers Onl] MD500:
Is possible to do this in S4 GT-I9500 Exynos?
[Galaxy Note 3 Developer Discussion [Developers Onl] Arathergreendroid:
Has anyone successfully gained warranty using this to reset knox flag? Samsung still might have some tricks up their sleeve.
[Galaxy Note 3 Developer Discussion [Developers Onl] arunastan:
Hi al33m

Did you find any solution to above issue. I am having the same issue. If you have please let me know.

Thanks
[Galaxy Note 3 Developer Discussion [Developers Onl] JJEgan:
You are in the wrong forum .
[Galaxy Note 3 Developer Discussion [Developers Onl] cgaggia:
Did you ever get the chance to test this on the N9005. I'd like to trade in to Samsung in a new Note 10 but they say Knox must not be tripped on this if I want the trade in discount.
[Galaxy Note 3 Developer Discussion [Developers Onl] Mohamedkam000:
Not possible on Snapdragon, closed source.

Sorry.
[Galaxy Note 3 Developer Discussion [Developers Onl] st3chn0:
if you follow through with the thread posts four links back to another one of links. I know he states that he has reset knox, had started making claims for knox reset bounty in the general forum.I had asked for evidence as everyone XDA should show, he had then posted a video which shows resetting the warranty bit on a 4.2.2 bootloader which has no links to knox. if you do a search in that thread im sure you would be able to find this.
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
I think you are confusing what Babak initially said (who discovered the method and then also claimed it might work on Snapdragon and then admitted he was wrong) with the very final post (which as I write this is the topmost sticky) from NoName, the guy that sells the box. While for Babak it was a matter of "dev karma", for NoName is a matter of money. We'll probably soon know more.
[Galaxy Note 3 Developer Discussion [Developers Onl] Surge1223:
Heres some info that might help you guys. I've also attached viewmem in case you guys don't already have it compiled. You can use it to further investigate. View attachment viewmem.zip

Full-size image
​
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
I have another theory. The SBL1 I downgraded to was from an engineering build. It could be possible this is some sort of production/debugging flag? I know I can reproduce indefinitely the P1 flag to P0 with a simple SBL1 downgrade, but I'm not sure what the implications of this is, or why. I'm not sure what P is, but we can modify whatever it is since the rollback protection number is 0.
[Galaxy Note 3 Developer Discussion [Developers Onl] st3chn0:
Could be linked to SBL1 but I don't understand why my flag hasn't increased and I've done all updates ota. If I've had to reinstall I've used odin but I have never ticked the update bootloader option
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
I know for a fact it's linked to SBL1. Flags are device independent, based on carrier updates. They use the flag counter for milestone updates to prevent rollback. Each carrier's device will be different. I know some S4's have P6, some European devices have P3. I've been analyzing SBL1 in IDA and I can't find the counter that rolls back P to 0. I know where the counters are kept in the image blobs, SBL1 might have two, with one being hidden. It could have something to do with PBL too.