Hello, guys!
I have some problem with my A7 Lite. I wanted to turn on secured wifi option, but an error message shows up saying that device is not supported because of modified system. I have rooted it recently, but went back to stock os and relocked bl, and the message is still there. So the device still knows it was rooted even I reflashed it back with stock rom?
SykoraLukas said:
Hello, guys!
I have some problem with my A7 Lite. I wanted to turn on secured wifi option, but an error message shows up saying that device is not supported because of modified system. I have rooted it recently, but went back to stock os and relocked bl, and the message is still there. So the device still knows it was rooted even I reflashed it back with stock rom?
Click to expand...
Click to collapse
There is no way to restore Knox security once it has been removed.
ze7zez said:
There is no way to restore Knox security once it has been removed.
Click to expand...
Click to collapse
Oh man. There's no way to re-enable it?
What is your current FW version?
Abish4i said:
What is your current FW version?
Click to expand...
Click to collapse
T220XXU1BVGB
Try downgrading then flashing rom again.
Earlier versions prior to MAY patch you can disable knox security from setup screen.
Either use Samfw one click 3.31
Related
I have been searching everywhere to try and find a way to load CM11 on my USC Galaxy Mega. All I can find is a ROM for the I9200/I9205. I have been in other forums that you can flash this CM11 release on a Metro PCS Mega. Is it possible to flash this on my USC R-960 Mega or have any of you here tried?
Depends on your phone setup. You will need an unlocked bootloader and should be running knox free firmware on your phone.
If the above criteria are met, then you can try flashing after backing up your stock rom. CM11 works on a lot of Mega versions.
Silesh.Nair said:
Depends on your phone setup. You will need an unlocked bootloader and should be running knox free firmware on your phone.
If the above criteria are met, then you can try flashing after backing up your stock rom. CM11 works on a lot of Mega versions.
Click to expand...
Click to collapse
Here is my setup.
I have rooted my device and have flashed CWM. Sounds like the boat loader is a different process than above? Also havent heard of knox free firmware, is that just something you flash with odin or something?
All the latest firmware releases come with Samsung's proprietary Security feature called knox. If you install a knox enabled firmware, then you will not be able to do the following.
Flash custom rom
Go back to a older stock rom
Go back to an older nandroid backup.
Trying to do any of the following will result in an insecure kernel error which can be rectified only by flashing a knox enabled firmware through Odin.
Post a snapshot of the bootloader screen.
is this what your talking about
Looks ok. First make a backup of your custom rom. Then you can try flashing a custom rom of your choice. You may/may not get LTE to work.
I presume you have not installed any ota update from your provider.
Silesh.Nair said:
Looks ok. First make a backup of your custom rom. Then you can try flashing a custom rom of your choice. You may/may not get LTE to work.
I presume you have not installed any ota update from your provider.
Click to expand...
Click to collapse
No ota updates, even when I checked manually I got a message saying you phone is modified or something.
dpetes262 said:
No ota updates, even when I checked manually I got a message saying you phone is modified or something.
Click to expand...
Click to collapse
Thats because your system status is custom. OTA's work only system and binary status are official.
Silesh.Nair said:
Thats because your system status is custom. OTA's work only system and binary status are official.
Click to expand...
Click to collapse
so I was able to flash/cm11 for i9200/i9205 and no touchscreen at all. I then flashed slimcat, same thing no touchscreen and accelerometer was acting weird. I then restored from the backup and touchscreen is back. I have 4g but its saying im roaming now. I wiped everything before all installs too. Any ideas?
dpetes262 said:
so I was able to flash/cm11 for i9200/i9205 and no touchscreen at all. I then flashed slimcat, same thing no touchscreen and accelerometer was acting weird. I then restored from the backup and touchscreen is back. I have 4g but its saying im roaming now. I wiped everything before all installs too. Any ideas?
Click to expand...
Click to collapse
So after I booted back to my backup,I had service but could not make calls or send texts. So what I did was a factory reset from with that ROM. This restored my service completely. Now I am just wondering why the touchscreen doesn't work on the other roms.
Silesh.Nair said:
Thats because your system status is custom. OTA's work only system and binary status are official.
Click to expand...
Click to collapse
Just a side note, when I flash either Phils CWM touch version, I get no touch or if I flash any other recovery, I get no touch functionality. Does this have something to do with the ROM not having touch?
I was at work so I never got a chance to capture the D/L. It was small, around 4MB. Anyone else see it?
Probably the Nov security update posted here
McChen147 said:
november security update:
https://android.googleapis.com/pack...5f522d.signed-volantis-MRA58N-from-MRA58K.zip
Click to expand...
Click to collapse
Can install with root?
TWRP Failed to install
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
When I flashed Marshmallow, I went back to unrooted. So the OTA worked fine, but not sure if you can stall with Root.
No.
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
OTA Update
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
ImzTinoz said:
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
Click to expand...
Click to collapse
This is normal. The warning is displayed because you have modified your device. It means nothing for the functionality of your tablet.
You cannot use the OTA update if your system is modified. You must be stock unrooted, unless you used the systemless root method in which case you need to restore stock recovery and kernel, then OTA will work.
This zip is not meant to be flashed in TWRP, it's the official OTA update which needs the stock recovery and completely unmodified /system partition.
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
harryspar said:
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
1) Will I lose functions such as the fingerprint reader if the device is rooted?
if you install the stock rom you will keep this functionality otherwise you need to wait concerning CM13 build
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
there is always a risk but minor
harryspar said:
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
wickedesires said:
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
Click to expand...
Click to collapse
Right, I remember this happening with other devices, as the OTA uses a recovery script.
I wonder if there will be nag screens for OTA's. This rendered my wife's S4 so annoying to use, with a persistent notification, until I found a block method (disallowing notifications didn't work since I'd have had to disable notifications for the entire Android System UI...)
harryspar said:
I wonder if there will be nag screens for OTA's.
Click to expand...
Click to collapse
I went about 5 days before I installed the b140 update and I don't recall any annoying notifications. I know exactly what you mean though my s5 active did the same thing because I didn't want to update and lose root. I finally found a way to disable it but like you said it was very irritating.
I have unlocked my bootloader, installed TWRP, and installed AospExtended v5.1 , which worked fine, except some moto mods are not working correctly so I would like to go back to stock 7.1.1.
Is it possible at all without bricking my phone? I have EU phone, so I suppose I need the RETEU zip, but I can only see it for 6.0.1 https://mirrors.lolinet.com/firmware...fficial/RETEU/ and I have read that after updating to 7.1.1, the bootloader is upgraded to a version that bricks your phone if you try to install MM again.
So what (and how!) to do so I can be back to 7.1.1 RETEU stock? Or I'm stuck with being able to use only custom ROMs forever?
Thanks!
raymccoy said:
I have unlocked my bootloader, installed TWRP, and installed AospExtended v5.1 , which worked fine, except some moto mods are not working correctly so I would like to go back to stock 7.1.1.
Is it possible at all without bricking my phone? I have EU phone, so I suppose I need the RETEU zip, but I can only see it for 6.0.1 https://mirrors.lolinet.com/firmware...fficial/RETEU/ and I have read that after updating to 7.1.1, the bootloader is upgraded to a version that bricks your phone if you try to install MM again.
So what (and how!) to do so I can be back to 7.1.1 RETEU stock? Or I'm stuck with being able to use only custom ROMs forever?
Thanks!
Click to expand...
Click to collapse
Have you done a FULL backup from the TWRP before?
btw I also need to know how to go back to again (but just for the warranty)
him7x said:
Have you done a FULL backup from the TWRP before?
btw I also need to know how to go back to again (but just for the warranty)
Click to expand...
Click to collapse
No i didn't do any backup :crying:
I managed to go back to 7.1.1 using RETUS firmware, and it seems to work fine (Wifi, 4G ... in Spain) but it only boots if I go to the bootloader and select "Factory mode", otherwise it goes always to recovery. Not ideal. Any idea why?
raymccoy said:
No i didn't do any backup :crying:
I managed to go back to 7.1.1 using RETUS firmware, and it seems to work fine (Wifi, 4G ... in Spain) but it only boots if I go to the bootloader and select "Factory mode", otherwise it goes always to recovery. Not ideal. Any idea why?
Click to expand...
Click to collapse
Sorry, I don't know why... But the good news is that the Official 8.0 is "almost" near to be released and for sure this will fix your trouble because it will update the bootloader and all the other ROM stuff.
Just be patient and do not shut down the device :silly:
raymccoy said:
I have unlocked my bootloader, installed TWRP, and installed AospExtended v5.1 , which worked fine, except some moto mods are not working correctly so I would like to go back to stock 7.1.1.
Is it possible at all without bricking my phone? I have EU phone, so I suppose I need the RETEU zip, but I can only see it for 6.0.1 https://mirrors.lolinet.com/firmware...fficial/RETEU/ and I have read that after updating to 7.1.1, the bootloader is upgraded to a version that bricks your phone if you try to install MM again.
So what (and how!) to do so I can be back to 7.1.1 RETEU stock? Or I'm stuck with being able to use only custom ROMs forever?
Thanks!
Click to expand...
Click to collapse
Dude try this on bootloader, run:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Hi. I had rooted a galaxy s10 lite, android 11 of a friend of mine. He doesn't need root any more. If i go to settings and search for an official update, it gives me, "phone is running an unofficial firmware and can't be updated" or something like this. Phone is running official firmware but rooted actually.
So if i factory reset from settings I'll obviously loose root. Phone will boot i suppose, if nothing have changed resentlly. Will update then works? He doesn't have a PC. Or because bootloader will be unlocked, will still make update not working?
Thanks,
sosimple said:
Hi. I had rooted a galaxy s10 lite, android 11 of a friend of mine. He doesn't need root any more. If i go to settings and search for an official update, it gives me, "phone is running an unofficial firmware and can't be updated" or something like this. Phone is running official firmware but rooted actually.
So if i factory reset from settings I'll obviously loose root. Phone will boot i suppose, if nothing have changed resentlly. Will update then works? He doesn't have a PC. Or because bootloader will be unlocked, will still make update not working?
Thanks,
Click to expand...
Click to collapse
hello colleague
First of all, back up your information.
You will have to restore the s10 lite with the system from odin.
the bootloader will still be unlocked (if you previously unlocked it)
once restored from odin, you will be able to install updates over wifi.
you can try
restoring from system, but I'm not sure if it will work.
if it has twrp.
If you decide to restore from system and it works for you, you can share your experience, for future reference.
having the bootloader unlocked does not affect ota updates
Thanks.. Yes i know how to do it in odin. That's what i want to pass as I'll probably factory reset his phone without a pc to a coffee shop for example.. When I'll do it, ill post, although i think i won't do it very soon.