I have a S4 that I am trying to upgrade to Lollipop. I tried through the AT&T Software update and keep getting "Software Update Interrupted." I remember I had rooted it quite awhile ago (towelroot)? But I am selling the phone now and just want to restore it to stock and upgrade it to lollipop. Kies says it is updated (which of course it's not). I do not have an external SD card. I did a "Factory data reset" from settings to see if that would allow me to update but it didn't. I did some reading and a lot of old Google posts said just to bring it to Best Buy. Are there any other options as those are outdated and I am doubting BB will be willing to help. Any and all help appreciated! Thanks!
Current Info
Device Name: SAMSUNG-SGH-I337
MODEL number: SAMSUNG-SGH-I337
Android Version: 4.4.2
Baseband version I337UCUFNB1
Kernel version 3.4.0-505595 [email protected] #1 Tue Feb 11 22:24:31 KST 2014
Build number: KOT49H.I337UCUFNB1
SE for Android status: Enforcing SEPF_SAMSUNG-SGH-I337_4.4.2_0004 Tue Feb 11 22:24:31 2014
Secure boot status: Type: Samsung
Security software version: MDF v1.0 Release 2
Really, no one? All I need is someone to point me to the proper thread so that I can get this thing back to stock without bricking it. Someone out there has to know the thread!
Hi, xml to put for using XDA Assist. If you're rooted or made any system changes the ota will not work. You probably have to flash the nb1 tar file in Odin and start over. See this, http://forum.xda-developers.com/showthread.php?t=2616221. Also see this, http://forum.xda-developers.com/galaxy-s4-att
Samsung Note 5
Model: SM-N920P
Android Version: 6.0.1
Baseeband Version: N920PVPS2BPD1
Kernel Version: 3.10.61-7231607/[email protected] #1/Thu Mar 31 14:24:41 KST 2016
Build Number: MMB29K.N920PVPS2BPD1
Rooted (do not remember the method I used to root)
After thoroughly troubleshooting issues with several Google Apps, I need to wipe my phone and start from scratch. I am currently running Marshmallow with OTA blocked. All of my data is already backed up. First question, once I wipe, will the phone automatically install Nougat? If not, what is the best way to manually upgrade to Nougat before wiping the phone? Second question, what is the cleanest and most effective way to root my phone once wiped and running Nougat?
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
Preamble:
Hello everyone, I'm essentially a complete novice when it comes to mobile phone operating systems and my head is spinning a bit right now. To keep a long story short: My mother came to me today and said she had managed to accidentally delete every picture on her phone (~5 years worth)...
So I've spent all night looking into the various terminology / practices for getting 'deleted' data off Android phones (Rooting, Nandroid, Bootlader, tons of recovery / root programs, etc). I'm just getting confused on all the programs for all the approaches on all the phone types (and even different builds of the same phone).
Just the question:
After doing this research, I'm not even sure if this phone can currently / ever be rooted. It seems its either got a 'rare' or new combination of system specs that no one seems to have info on, and that Verizon is apparently notorious for locking down their phones which greatly limits what I can do. So, I'm just trying to determine if there is even anything that can be done now (if not, could it be done 'later'?) and if it can be what is the most prudent course of action.
Phone Specs:
Brand:
Samsung
Type:
Galaxy S6
Model:
SM-G920V
Carrier:
Verizon
Android Version:
7.0
Android secruty Patch level:
March 1, 2018
Baseband version:
G920VVRU4DRE1
Kernel Version:
3.10.61
[email protected] #1
Mon May 14 20:52:00 KST 2018
Build Number:
NRD90M.G920VVRU4DRE1
Hardware Version:
G920V.07
What I've tried so far:
I initially tried a recovery program - DiskDigger (which is paired with OneClickRoot), it could not root properly, so I just grabbed the 'preview thumbnails' of what it did find just so I had something. I then looked at KingRoot (did not state it was compatible), then KingoRoot for both the APK and Desktop versions which do claim 7.0 compatibility (APK goes black at 90%, and Desktop failed and would fail and crash on any second attempt).
Was going to try PingPongRoot but decided I should make a real backup first (still working on that), and noticed that while this program specific seems geared to Samsung Galaxy S6s, my build isn't listed as compatible.
boddole said:
Preamble: Hello everyone, I'm essentially a complete novice when it comes to mobile phone operating systems and my head is spinning a bit right now......
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3110220
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hello,
I'm hoping someone can help me with the following issue. For a long time I used a custom ROM(NNE 3.1) and was able to call out and to be called. Until recently the Phone App just started to crash on any number I wanted to dial to. Since I haven't reset the phone for a long time, I chose to try out some newer ROMs, assuming the calling out/in problem would be solved.
However, whatever custom ROM I'm trying, calling doesn't work anymore. After re-flashing the stock firmware(Stock Samsung Android 7 - G920FXXU5EQI6_G920FPHN5EQI2_PHN) with Odin, I was able to call and to be called again.
After which I thought/hoped, maybe the stock ROM would have fixed the Phone App issue, so I tried various custom ROMs installed with TWRP, but with none of them the Phone App works. Not even with the exact same ROM I've been using for a long time. (I backed-up that ROM back then, and re-flashed the exact same file this time [NNe 3.1]).
What am I missing here? Some Samsung hardware security feature that got flipped back somehow?
Help is much appreciated...the stock firmware is so slow...
Thanks in advance!
Device: SM-920F
ROM Name: Stock
Android version: 7.0
Baseband version: G920FXXU5EQI4
Kernel version: 3.10.61-10958180 - [email protected] #1 - Sep 18 2017
Build number: NRD90M.G920FXXU5EQI6
Status SE for Android: Enforcing, SEPF_SECMOBILE_7.0_0005 - Sep 18 2017
Knox: 2.7.1
Security patch level: August 1st, 2017