I factory reset my s7edge after accidentally disabling the UI. Recov screen had fail message at bottom but phone loaded and operates great . Benched 135k+ just yesterday on Antutu .. any answers on why it may be failing ?
If you are rooted or were rooted the kernel has dm-verity disabled. The recovery still checks dm-verity and tells you that it has failed. I don't know why if you had never rooted your device.
qwewqa said:
If you are rooted or were rooted the kernel has dm-verity disabled. The recovery still checks dm-verity and tells you that it has failed. I don't know why if you had never rooted your device.[/QUO
No I haven't even attempted root.
Click to expand...
Click to collapse
Related
any one know the changelog this firmware? the changelist is very changed....i found here http://live.samsung-updates.com/index.php?device=SM-P605
p.s sorry for my english
Has anyone flashed this yet? I flashed it and it goes thru the entire installation process and the fails to complete the "write bla. bla". But it installs all the parts of the firmware. So I tried to boot it and it failed with an message saying that I should use Recovery mode in Kies bla. bla. I flashed it again thinking it might have been just a one time error but no, same thing again. It seemed like stock recovery stopped my device from trying to boot, so I flashed TWRP and rebooted. To my supprise the device went in to boot process and BOOTED!!! No issues, well stock keyboard kept chrashing, it runs just fine. SO I boot in to recovery and let TWRP install Super SU for root and boot. No messages from Knox what so ever!! Not when starting root apps, not when it asks for root access and not when Super SU prompt shows up asking me if I want to grant this app superuser rights. I have not frozen any Knox apps and Knox apps is installed. It`s been a while since I rooted a stock firmware but as I remember there was Knox alerts everytime when apps asked for root, untill Knox was deleted or froozen.
If the install fails for the rest of you, just flash a custom recovery and theres a big chance it will boot for you also. But thats when Odin completes the install of all parts and fails to complete. Would be nice to hear if someone have installed it with out issues.
nickwarn said:
Has anyone flashed this yet? I flashed it and it goes thru the entire installation process and the fails to complete the "write bla. bla". But it installs all the parts of the firmware. So I tried to boot it and it failed with an message saying that I should use Recovery mode in Kies bla. bla. I flashed it again thinking it might have been just a one time error but no, same thing again. It seemed like stock recovery stopped my device from trying to boot, so I flashed TWRP and rebooted. To my supprise the device went in to boot process and BOOTED!!! No issues, well stock keyboard kept chrashing, it runs just fine. SO I boot in to recovery and let TWRP install Super SU for root and boot. No messages from Knox what so ever!! Not when starting root apps, not when it asks for root access and not when Super SU prompt shows up asking me if I want to grant this app superuser rights. I have not frozen any Knox apps and Knox apps is installed. It`s been a while since I rooted a stock firmware but as I remember there was Knox alerts everytime when apps asked for root, untill Knox was deleted or froozen.
If the install fails for the rest of you, just flash a custom recovery and theres a big chance it will boot for you also. But thats when Odin completes the install of all parts and fails to complete. Would be nice to hear if someone have installed it with out issues.
Click to expand...
Click to collapse
could you give us a changelog (multiuser support ?) , multitouchscreen fixed ? ; ....
I've downloaded the B2 firmware from SamMobile (I tried first on your samsung update website but the flashing didn't work), the "Baltic" one with odin 3.09 and the flashing worked. I've only used it for a couple of minutes and the only difference that I can see is that the the OS runs smoother, less lag and no more wake up lag. I'm not saying the lag magically disappeared, it's just much less noticeable. But of course it's definitely worth flashing it if, like me, you couldn't stand how laggy the previous firmware was.
EDIT: nickwarn, could you please explain me how you rooted your P605 with the new firmware? I'd like to do the same (I've already installed TWRP btw). Thanks
EDIT 2: Never mind nickwarn, I re-read your post and understood that you simply booted TWRP and let it install SuperSU when it asked you to install it. Thanks anyway
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Duncan1982 said:
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Click to expand...
Click to collapse
Maybe install busybox from Ericsson
Thanks I have busy box installed, this is very odd it is like there is a security file blocking everything despite root.
Xblast works as I have the clock centred and circle battery.
I am Experienced in root, and haven't stumbled upon this before.
Was thinking it was 4.4.4 but others are having success.
Hmmmm baffled.
Maybe has something to do with the security settings?
Install if you like the Wanam module and check if Disable Secure storage is disabled.
Thats all i can think about for now.
Nope nothing, even tried changing secure storage value to false and upon hitting save it reboots and nowt.
I give up can't think of anything oh it could be AEA Kernel that perhaps is causing the problem?
The only way to find out if its the kernel you flashed. Re-flash the stock-kernel
Thanks for getting back, Yeh back to stock and same problem. Maybe for some reason only have partial root, can't see that as supersu is there and functional and I have twrp custom recovery. Hmmmmm the mind boggles lol.
Reasonably experienced root user and for the life of me I can't sus what's up.
Tried refreshing the AEA Kernel and it won't even do that now.
Not that it's important, was just after a sound mod & changing the Dpi down to 560. Tried both it won't change.
Some security thing is preventing this but what could it be?
With some 4.4.4 ROMs on the note 2, there were problems with getting "full" root using twrp. I don't know if this is relatedn but the symptoms sound similar. Solution there was to use philz recovery (which isn't an option here), or for some Roms to flash an older version of supersu in twrp and then update after starting. Could be worth a shot.
Did you make sure to open the SuperSU app after rooting and update the binary? Are you SELinux permissive?
If you are having issues, download the recovery version of SuperSU, install it, then make sure to open the app so it updates.
You could also disable SELinux through the build.prop. Having a kernel that is SELinux permissive doesn't matter if you still have everything enabled in the build.prop
Code:
(SELinux disable)
ro.build.selinux=0
(KNOX disable)
ro.config.tima=0
ro.config.knox=0
If none of that has helped, it is recommended you restore to stock and root again, making sure that reactivation lock is disabled before attempting to perform the root portion.
Hi,
I could really use some help here with the i377m Canadian S4.
Basically, I want to make sure there is no root, that the bootloader is locked and that SafetyNet passes.
Here is what I did:
1) Downloaded Optimized LineageOS 14.1 and GApps, copied them on an SD card
2) Installed Samsung drivers and Odin
3) Installed the recommended TWRP (jfltecan) for LineageOS 14.1 , which is 3.1.0.
4) Installed TWRP via Odin
5) Booted to TWRP and cleared Dalvik, etc.
6) Installed Optimized LineageOS
7) Went to Developer Options, disabled Root
8) Flashed DisableSuperUser
9) Cleared Dalvik, etc. again
Safety Net Test says "CTS profile match: false" and "Basic Integrity: false"
I tried loading Pokémon GO (one of the few uses of this older device) and get "Unable to authenticate", another clue that SafeNet failed.
Also, I am getting the "Kernel is not Seandroid enforcing" and "Set Warranty Bit: Kernel" messages during bootup.
SELinux is set to "Permissive" and I read setting it to "Enforcing". The kernels found here for this model all seem to set to Permissive. At this point though I'm not sure and I would rather ask for guidance first.
Thanks for any help you may provide!
The bootloader on the sgh-i337m was never locked.
audit13 said:
The bootloader on the sgh-i337m was never locked.
Click to expand...
Click to collapse
Thanks... One thing I don't have to worry about.
I recall that at some point, I did give TWRP full access when prompted. Could this be one of the things that are triggering the Safety Net failures?
I don't know how to revoke the access I granted.
I don't think granting access to TWRP would affect the ROM since TWRP only runs when the phone boots into recovery.
Safetynet may be failing due to a custom ROM that hasn't been signed by Samsung.
You're getting the "not enforcing" because the phone has a custom ROM and recovery.
Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool
RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data
I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).
Hello, recently I refleshed the latest stock rom using odin.
Previously I had magisk installed with xposed.
Root and xposed seem to be gone, but saftynet still fails.
Basic integrity is false and cts mismatch is thrown.
So I would like to know how can I go back to stock completly, wipe everything and reinstall stock rom.
Odin flash does not seem to delete user data.
Might there be something on the data partition left over that triggers safety net ?
I solved it by myself.
It seems that even though the system was stock the saftynet somehow remembered that the device was modified in the past so that's why it still failed.
After a factory reset safetynet is happy.
I think I will leave root alone for now as I don't really need it.