Database Info

[Q] In desperate need of help regarding S2 stock firmware!

Hello Xda! I hope you've all had a wonderful christmas eve and an even better new year! I've joined this site after headhunting and reading numerous posts touching different topics regarding one subject and one subject alone: Samsung Galaxy S2.
Now, on to the issue at hand. After tweaking and modifying my firmware, in hopes of getting Cyanogen 7 to run along with the ICS theme for it and having failed, my Sg2 has never been the same, of one simple reason: I haven't found the exact stock firmware that fits my phone. When I write "fits my phone" I actually don't refer to the fact that they aren't working as they indeed are, but no-one that's up to date.
The problem could've been easily fixed if Samsung Kies actually worked with my Windows 7 64-bit, which it doesn't, and please, don't point me in the direction of other posts such as "untick debugging mode", "reinstall Kies", "install those drivers by searching 'this' and 'that' on Google", because trust me, I've tried everything. It worked for a couple of days, but now as I really need it, and want to get out of the hellhole I call "KE2", it doesn't seem to want to help me, at all. "This device is not supported by Kies".
Now, I've visited another thread here on xda, more or less this one: http://forum.xda-developers.com/showthread.php?t=1075278 and dabbled myself through numerous versions until I finally settled for XWKE2 - Generic NEE and successfully managed it to run on my phone with Odin.
Since my phone is operator locked and I'm paying for it monthly via a Swedish operator known as Telenor I'm not able to update the firmware via About phone -> Software update either.
As I said, Kies isn't able to update my phone to 2.3.5/ KE7 (or whatever version is the newest) and I'm thusly stuck with XWKE2 & 2.33.
The most major problem I have is that I don't know which firmware to download from the topic I provided above, and I'd really like to know which one to actually download in order to have the most up-to-date version.
I'd immensely appreciate any help!
Model number
GT-I9100
Android Version
2.3.3
Baseband version
I9100XXKDJ
Kernel Version
2.6.35.7-I9100XWKE2-CL187606 [email protected] #2
Build Number
GINGERBREAD.XWKE2

T-Mobile S4 - Accept OTA Update or Root first?

I am a newbie to GSM, so bear with me
T-Mobile is offering me an OTA update to M919UVUFOK3 every 24 hours. Is it too late already to keep EFuses from blowing, since KNOX came with the MK2 on my motherboard? In which case have I got nothing to lose by accepting the OTA update? This would be the most stable, OR
Should I root the MK2, install TWRP, and upgrade via ODIN? I'm not sure if they have OK3 for modded firmware yet, at the moment, all I want to do is upgrade to the latest, most stable firmware / kernel / modem I can while keeping as many E-Fuses intact (knox bit, anything that keeps me from being able to downgrade, root, install a custom ROM, or ressurect my device if it becomes hard-bricked.
Here's what I know about my S4
About Device:
Model Number
SGH-M919
Android Version
4.3
Baseband version
M919UVUEMK2
Kernel version
3.4.0-2015522
[email protected] #1
Sat Nov 16 14:22:56 KST 2013
Build number
JSS15J.M919UVUEMK2
SELinux status
Enforcing
SEPF_SGH-M919_4.3_0010
Secure boot status
Type: Samsung
Here's what I have observed about my phone so far:
* T-Mobile finally gave me a SIM card that works
* Full eMMC dump using RIFF (anything available upon request)
* KNOX is installed
* ODEX information was found on this phone when I looked through partitions in a hex editor
* Found code amongst the boot loader partition in WinHEX, "BootLoader.Rollback.BlowFuse" <<< NOT Warm and Fuzzy feeling
So, in short, do I have nothing to lose by accepting the OTA update (I believe it is still rootable), OR should I root my current firmware and do everything by hand? OTA would ensure greatest stability, but I still want it to be MY phone. Any suggestions?
If anyone wants my full eMMC dump, *.pit file, anything let me know (as long as it's not something personal like a certificate or IMEI)
P.S. - What are these "Security Policy Updates" it constantly is asking me to enable? My friend said they are harmless (don't do any permanent castration on rollback capability). What do they do? Can they update the security - against me? (like changing the lock on my front door and stealing my house)
I'm a newbie, so if some questions sound stupid just bear with me. I just want the latest firmware, mostly stock but rooted, and not burn my bridges to go back and do anything I may learn about later. I could just keep delaying the update, but 4.4.4 ran faster on my last phone and I like it, but want to be able to keep my options open.
Thanks

If this is a stupid question, I'm a newbie just point me in the right direction.
I know how to root, I know how to use odin, I just need to know if MK2 is already too far to not trip the KNOX thing. I'm not sure if KNOX is actually installed, but I have a good bet it is, as it's listed under "Device Administrators".
It may sound a tad crazy, but everytime they fry one of these on my (originally $700) phone, they may as well have literally violated me, raped me, as if they're willing to go THAT far to control how I use... um, what is it called when you purchase something? I mean when you buy something, who's property does that become? Oh yeah, it's MY property. In Django Unchained, although his character is evil (and I'm talking electronics no offense intended), Calvin Candie said exactly how I feel about eFuses, controlling what I can and can't do with items I purchase.
"This CPU here, is MY property... and I can choose to do... with MY PROPERTY... WHATEVER I so desire!"
I'm just asking what would be the best course of action as I'm torn between stability and "Keeping my Rights". For those who do not know what an eFuse is, it's literally a fuse that's 20nm wide embedded in the snapdragon CPU itself. It's the way they can make it impossible to downgrade or reset the KNOX bits. When a KNOX bit is set, a higher voltage is applied to this fuse and it is purposely overloaded, breaking the link and setting it to a "1". If we had the RSA private key to sign our bootloader, it would be no problem. Here's some info on eFuses
https://en.wikipedia.org/wiki/EFUSE
http://paris.utdallas.edu/ssiri08/Tonti_SSIRI_eFuse_V2.pdf

Need GUIDE to ROOT my SM-J727P

It is my hope to locate the necessary files & utilities, ie., Odin, ROM, Recovery, TWRP, etc.,
to ROOT my phone, FIRST with a STOCK, DE-BLOATED firmware. If de-bloated is not an option, then a TWRP option would be the next most desirable.
It has been quite sometime (Summer 2013 on a Motorola Droid RAZR) since I flashed a phone with a custom ROM.
SO, it could be said I'm a bit rusty.
Please, TREAT ME LIKE AN IDIOT. As if I know nothing. Explain things as if talking to a child.
You CANNOT possibly hurt my feelings.
I need a clearly written, step-by-step instruction manual to perform the flashing of the phone.
I am very proficient in Windows, but am using an antique emachine running XP-SP3 with 512M of RAM, and 2.93GHz proc.
So, it has Wi-Fi to my phone, but no access to internet if the phone gets bricked.
A good backup plan, IN ADVANCE, is advisable. Suggestions are welcome.
What I have;
Samsung Galaxy SM-J727P Perx from Boost Mobile
Software Version:
J727PVPS3ARA1
Hardware Version:
J727P.02
Android Version:
7.0
Security Patch:
January 1, 2018
Kernel Version:
3.18.31-12377128
[email protected] #1
Fri Dec 29 15:40:33 KST 2017
Build Number:
NRD90M.J727PVPS3ARA1

Galaxy J727P
dbreed53 said:
It is my hope to locate the necessary files & utilities, ie., Odin, ROM, Recovery, TWRP, etc.,
to ROOT my phone, FIRST with a STOCK, DE-BLOATED firmware. If de-bloated is not an option, then a TWRP option would be the next most desirable.
It has been quite sometime (Summer 2013 on a Motorola Droid RAZR) since I flashed a phone with a custom ROM.
SO, it could be said I'm a bit rusty.
Please, TREAT ME LIKE AN IDIOT. As if I know nothing. Explain things as if talking to a child.
You CANNOT possibly hurt my feelings.
I need a clearly written, step-by-step instruction manual to perform the flashing of the phone.
I am very proficient in Windows, but am using an antique emachine running XP-SP3 with 512M of RAM, and 2.93GHz proc.
So, it has Wi-Fi to my phone, but no access to internet if the phone gets bricked.
A good backup plan, IN ADVANCE, is advisable. Suggestions are welcome.
What I have;
Samsung Galaxy SM-J727P Perx from Boost Mobile
Software Version:
J727PVPS3ARA1
Hardware Version:
J727P.02
Android Version:
7.0
Security Patch:
January 1, 2018
Kernel Version:
3.18.31-12377128
[email protected] #1
Fri Dec 29 15:40:33 KST 2017
Build Number:
NRD90M.J727PVPS3ARA1
Click to expand...
Click to collapse
Well here is one link for you to look into !
https://forum.xda-developers.com/galaxy-j7/development/recovery-twrp-3-1-1-x-galaxy-j727p-t3692663
An you will want the latest Odin an the latest SUPERSU ZIP to flash threw twrp !

[HELP] Trying to Root Samsung Galaxy J1 mini sm-j105y

I am trying to root my Samsung Galaxy J1 Mini and am not having any luck, here are some details from the About Device in settings:
Details: Samsung Galaxy J1 Mini SM-J105Y
Model : SM-J105Y
Android v : 5.1.1
Baseband v: J105YDVU0AQI1
Kernel v : 3.10.65-12258773
[email protected] #2
Thu Nov 28 13:40:24 KST 2017
Build number : LMY47V.J105YDVS0AQK1
SE For Android Status: Enforcing
SEPF_SM-J105Y_5.1.1_0073
Tue Nov 28 13:49:58 2017
Security Software Version: ASKS v1.2 Release 161011
Android Secutiry patch level: 1 November 2017
I have OEM Unlock and USB debugging enabled in developer options
I tried rooting using Kingoroot on PC and Kingroot on the phone itself, both say my phone is unsupported
I have tried to root this phone using cf-root images gathered from firmware.mobi (link https://desktop.firmware.mobi/device:483/firmware:14717 ), this comes up with the error RECOVERY IS NOT SEANDROID ENFORCING before rebooting normally
I have also tried using TWRP, but all the tutorials show pressing vol+ & menu & power to access, but this does not work with my phone either (it takes ages even to power on then just sits at the RECOVERY IS NOT SEANDROID ENFORCING until I remove the battery & reboot)
Is there any way to root this model of J1 mini? I am at the end of my tether here

Sparky Kestrel said:
Details: Samsung Galaxy J1 Mini SM-J105Y
Model : SM-J105Y
Android v : 5.1.1
Baseband v: J105YDVU0AQI1
Kernel v : 3.10.65-12258773
[email protected]4714 #2
Tue Mar 13 11:40:40 KST 2018
Build number : LMY47V.J105YDVS0ARC1
SE For Android Status: Enforcing
SEPF_SM-J105Y_5.1.1_0073
Tue Mar 13 11:50:08 2018
Security Software Version: ASKS v1.2 Release 161011
SMR Mar-2018 Release 1
Android Secutiry patch level: 1 March 2018
Click to expand...
Click to collapse
I remember having trouble finding out how to root my J1 Mini.
My device info differs slightly from yours (marked in red in the quote) so I can't guarantee we have the exact same phone. I suspect it's because I have a later firmware version than you (and my phone is rooted!).
Search for SM-J105: ROOT + TWRP Fácil! and you will find the video that got me rooted (sorry I can't post links).
When I initially rooted, the video description contained direct links to the needed files. The current video description links to a site where you can scroll down to "ROOT SM-J105Y" and download the files; I assume they are the same as the files I used.
I can't guarantee this will work so make sure you have a way to restore your phone in case anything goes wrong.
It might be worth looking up Magisk as this seems to be the new way to root phones however I haven't tried it.

Thanks for the info, but searching for that just showed a load of Youtube videos, most of which just show the exact same methods that don't work for me, so unless you can post a direct link then I don't even know what I should be looking for really.
And I looked up info on Magisk, but that requires TWRP to be installed, which as I noted above I just can not get to work no matter what.
I must have the only Samsung phone in the known multiverse that can't be rooted.

Enter firmware.mobi (desktop.firmware.mobi) and search for your sm-j105y. Chose the exact type of your phone's security patch, build date, etc. Configure CF-Auto-Root (better don't modify anything), generate the pack, wait for it to be ready, download start automatically, unpack it, read instructions very, very carefully and root your phone.
I did it successfully with my sm-j106h.

Video:
www . youtube . com/watch?v=I31ZMO35Eoo
Files:
garagemandroid . blogspot . com/2016/12/sm-j105.html
(remove spaces from links)
I've checked the files and they are the same ones I used to root my own phone.
I have since tried out magisk and it works using TWRP from the files above.
Magisk also works and seems to be a better way of rooting but I haven't managed to get xposed working with it.

@shahinul: read my first post again, I already tried firmware.mobi, I even put a link to what I downloaded there. It doesn't work.
jatan666 said:
Video:
www . youtube . com/watch?v=I31ZMO35Eoo
Files:
garagemandroid . blogspot . com/2016/12/sm-j105.html
(remove spaces from links)
I've checked the files and they are the same ones I used to root my own phone.
I have since tried out magisk and it works using TWRP from the files above.
Magisk also works and seems to be a better way of rooting but I haven't managed
to get xposed working with it.
Click to expand...
Click to collapse
Thanks for the link jatan. After loading the video, I thought "hey this looks familiar" and sure enough, my comment was there about it not working.
Since my last post, the new firmware update (the one that you already had, with the same info you marked in red above) came up, but would not install (it came up something about not having the right recovery image or something, and to take it to a Samsung repair centre), after trying a number of different methods, I finally went into recovery and wiped the cache which did the trick and allowed the latest official firmware to install successfully, so now I am on the same firmware you documented in your first post.
So, since I am on the same firmware as you, I thought I'd try again, but now, even using the package you linked to, when trying to install the image file, this time it won't even install, instead coming up with
SECURE CHECK FAIL : (recovery)
even though I still have OEM UNLOCK and USB DEBUGGING enabled in developer options.
That's it, I completely give up now. I honestly must have the only Samsung phone that is simply incapable of being rooted by every method known to man.
I think if I wanted to continue, it would be quicker and easier for me to do what a friend suggested and go to a pawn shop and pick up a second hand S4 or something.

omg so actually impossible to root j1105y and 106h; i find since few day and nothing twrp work and no roms custom available too

Help ~ getting an unbranded tablet to run google home?

Hello all, this is my first post.
I have joined the site because I am looking for help with an unbranded tablet that I have.
I would like to use this tablet as a very basic wall mounted control point for google home, in order to control my smart lights and other smart devices.
However, the tablet is old and has an old version of android. Subsequently it appears that google home cannot be installed on it.
It will also not update to a newer version, potentially because the 'firmware' is unsupported? I am unsure because this is all very new to me.
Because the tablet doesn't appear to have a 'brand', I am struggling to find any support or step by step instructions.
I know very little about 'flashing, roms, rooting etc., however I have managed to root it through kingo, but don't know what needs to happen next.
The device info is:
Model: N98
Allwinner A33 quadcore,
Android 4.4.2 (kitkat?)
Firmware: V2.0
Kernal ver' 3.4.39
Build number: astar_y3-eng 4.4.2 KVT49L 20151208 test-keys
I've also included a couple of photos of its motherboard.
Any help would be greatly appreciated and what steps I need to take just to get google home up and running on it,
thank you very much in advance