My galaxy J⁷ crown has been booting twice for a while. I know there is no more updates. And I also have it set to encrypted startup. Is there an extra sdk loaded to my bootloader? It is not rooted either. Did my phone got hacked? Or possible an sdk sent to my phone using the nfc?
Related
A few weeks ago I rooted my Verizon Galaxy S4 using a simple method found on this forum. I didn't really do much with the phone other than uninstalling some preinstalled apps that I don't use, and I added a multi window manager to add some apps to the multi window function. I unrooted the device using the full cleanup for unroot in supersu before installing a verizon update about 2 weeks ago.
I am still unrooted, however when the device boots up it no longer shows the galaxy s4 screen. It now shows "Samsung" with an image of a lock that is unlocked and it reads "custom" underneath.
I was prompted to update about 2 days ago. it is the update to 4.3. I cannot install this update. When I try it almost immediately fails. Again, I am not rooted any more. I'm assuming that the few small changes I made are the reason.
My main question is how can I just get the phone back to stock. I just want it to be configured the way it was before I even rooted it. I'm at a point that I wish I hadn't done that. Is it possible to flash it back to factory 100% or am I pretty much screwed?
ytsejam6922 said:
A few weeks ago I rooted my Verizon Galaxy S4 using a simple method found on this forum. I didn't really do much with the phone other than uninstalling some preinstalled apps that I don't use, and I added a multi window manager to add some apps to the multi window function. I unrooted the device using the full cleanup for unroot in supersu before installing a verizon update about 2 weeks ago.
I am still unrooted, however when the device boots up it no longer shows the galaxy s4 screen. It now shows "Samsung" with an image of a lock that is unlocked and it reads "custom" underneath.
I was prompted to update about 2 days ago. it is the update to 4.3. I cannot install this update. When I try it almost immediately fails. Again, I am not rooted any more. I'm assuming that the few small changes I made are the reason.
My main question is how can I just get the phone back to stock. I just want it to be configured the way it was before I even rooted it. I'm at a point that I wish I hadn't done that. Is it possible to flash it back to factory 100% or am I pretty much screwed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2265477
Its been a few months since Ive bothered trying to figure out how to fix my Galaxy Tab 4, SM-T230NU, but Im finally getting around to fixing it. It sat in my closet for a few months simply because I did not have the time to fix it. It's soft bricked (loads the Samsung Galaxy Tab 4 bootscreen, but stays stuck on the single Samsung logo). Its not hard bricked as power turns on, but it is soft-bricked. Will running NE2 I found in the firmware section fix the soft-brick? I just downloaded odin 3.09, and right now NE2 is downloading through Mega.nz......any help would be appreciated....
jxcorex28 said:
Its been a few months since Ive bothered trying to figure out how to fix my Galaxy Tab 4, SM-T230NU, but Im finally getting around to fixing it. It sat in my closet for a few months simply because I did not have the time to fix it. It's soft bricked (loads the Samsung Galaxy Tab 4 bootscreen, but stays stuck on the single Samsung logo). Its not hard bricked as power turns on, but it is soft-bricked. Will running NE2 I found in the firmware section fix the soft-brick? I just downloaded odin 3.09, and right now NE2 is downloading through Mega.nz......any help would be appreciated....
Click to expand...
Click to collapse
Flash the right firmware for your device and see if it boots. If it doesn't boot within 20minutes after flashing, simply reboot into recovery and factory reset.
-DUHA
When I rooted the device, gaining root on the 230NU was abit of work, so I had to go through a lot of in and out holes just to root the sucker, and then a week or two later there are many different ROMs available for the 230NU...I'm shocked that someone finally found a workaround for the marvel processor in the 230NU because the 8 I believe has a snapdragon and/or euronoyx (however you spell it)
jxcorex28 said:
When I rooted the device, gaining root on the 230NU was abit of work, so I had to go through a lot of in and out holes just to root the sucker, and then a week or two later there are many different ROMs available for the 230NU...I'm shocked that someone finally found a workaround for the marvel processor in the 230NU because the 8 I believe has a snapdragon and/or euronoyx (however you spell it)
Click to expand...
Click to collapse
It works, im running 4.4.2 stock....Im about to look into some information about rooting.....When I got everything running smooth I got a system update message, so right now it's going through a system update......Do you have any good source of information for rooting the SM-T230NU ???
jxcorex28 said:
It works, im running 4.4.2 stock....Im about to look into some information about rooting.....When I got everything running smooth I got a system update message, so right now it's going through a system update......Do you have any good source of information for rooting the SM-T230NU ???
Click to expand...
Click to collapse
Here
The other day I swapped my batteries an upon reboot, got a splash screen indicating an update was being installed. I had been rooted for over two years and I had SDM frozen via Titanium Backup. There was no confirmation prompt or ability to defer the update offered. After boot, SU had been uninstalled and Titanium Backup wouldn't run at all.
Has anyone else had this happen? Verizon pushing past disabled SDM to pwn a phone?
Sent from my SM-T520 using Tapatalk
Danzdroid said:
The other day I swapped my batteries an upon reboot, got a splash screen indicating an update was being installed. I had been rooted for over two years and I had SDM frozen via Titanium Backup. There was no confirmation prompt or ability to defer the update offered. After boot, SU had been uninstalled and Titanium Backup wouldn't run at all.
Has anyone else had this happen? Verizon pushing past disabled SDM to pwn a phone?
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
this is a serious problem , since for the vzw the bootloader unlocking usually take place on bpb1's and it would make sense that they would aim there first. I think it might be time for you to update your bootloader or switch over to custom roms instead of staying on samsung's firmware , and also this post just saved me from thinking of switching back to stock for the time being so now im def staying on nougat and hope android can be brought to the S5 as well.
I'm surprised there isn't anyone else reporting this. It seems VZW has a secondary backdoor into the stock firmware that isn't SDM or Knox. I didn't have the Verizon app installed either. On a different build on another S5 phone, the Verizon app asked for root from SU, and I shut it down immediately, figuring it wss trying to insert a backdoor.
It's just strange after two years of zero updates to my image, it suddenly allows VZW in to perform non-consentual sodomy on my phone...
Sent from my SM-G900V using Tapatalk
Danzdroid said:
I'm surprised there isn't anyone else reporting this. It seems VZW has a secondary backdoor into the stock firmware that isn't SDM or Knox. I didn't have the Verizon app installed either. On a different build on another S5 phone, the Verizon app asked for root from SU, and I shut it down immediately, figuring it wss trying to insert a backdoor.
It's just strange after two years of zero updates to my image, it suddenly allows VZW in to perform non-consentual sodomy on my phone...
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
its because the s5 is still widely used all over the world , its just another tactic for them to screw up older samsung devices to get users to upgrade to the latest ones. which is why using samsung software is not always a good thing. Injecting micro-codes are not UN-common for companies
I wanna know how they did that so it can be prevented.
Hey guys,
Tried updating my phone today and it said my system is modified. This was a brand new device when I bought it, in download mode it still says Official and I have never attempted to root the device. I've got Adhell installed but that's as far as I go. What gives? I can't do an official update. Any suggestions?
Edit: Samsung Pay and Secure Folder still both work.
Sent from my SM-G950F using Tapatalk
I need some very basic help rooting a Samsung J7 (SM-J700T).
I am trying to set up a basic (and inexpensive) Samsung phone for my father, that will be relatively easy for him to use (he is mid 80s) and that won't be a big loss if he misplaces it. I also would like to set it up so that we have root access (to delete or freeze the apps that will never be used).
I got a used (but nice) Samsung SM-J700T (Exynos Octa 7580) and got it updated to Android version 7.1.1. I downloaded a number of versions of Odin3, and the version of TWRP for this phone from (https://dl.twrp.me), as well as SuperSu.
I understand that it is important to have the right TWRP version for a particular phone, but is it so critical to have a particular version of Odin3 or SuperSu?
Using Odin3, I installed TWRP to the phone (unticked 'auto reboot') and got the green 'Pass!' notification, pulled the battery, pushed Up + Power + Home to get into recovery mode, but now I get nothing but the "Galaxy J7" logo, whether I try to get into the download mode, recovery, or just turning it on with the power button.
How serious is the problem?
I would appreciate some advice... thanks in advance!