Hi I have a S7 Edge SM-G935F and I followed the TWRP and Root guide here on XDA, but i still got dm-verity triggered and I cant boot into Android without that motherf%&king error popping up about resetting. I am running the Latest stock Android 8 update, cause I just got the phone a couple of days ago so I havent tampered with it, but as soon as I try to tamper, it softbricks...
I have never had a phone with dm-verity before so yeah does anyone know a method without wiping to factory?
Related
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.
Odin to root. Xposed. Custom gapps. After about a week, multiple apps will begin to force close at random. Reboot in a bootloop on the att screen. Only solution is to master reset and start again. This has happened twice now. Is the problem in busy box? Xposed?
had this happen to me too, exactly the same deal. in fact happened just now ugh. att s7, not the edge model but whatever.
Same thing here but this is the third time. Tried different root methods each time. Xposed framework is the only common denominator so far, doesn't seem to make any sense as the phone runs great and it's always around day 7 of the root that the phone starts stopping apps and services and that's when I know I have time to move any important photos or app information and perform a complete overhaul. Any ideas what could be causing this?
has nothing to do with root. in package disabler, disable policy updates and system updates and att updater
the policy updater was doing what you are describing to my phone
Awesome! Thanks for the info, I disabled the policy updates. Appreciate the help!!
demoicurn said:
Odin to root. Xposed. Custom gapps. After about a week, multiple apps will begin to force close at random. Reboot in a bootloop on the att screen. Only solution is to master reset and start again. This has happened twice now. Is the problem in busy box? Xposed?
Click to expand...
Click to collapse
I tried to master reset my s7 edge att version and its still stuck in boot loop. Also I tried odin too. Any ideas?
demoicurn said:
Odin to root. Xposed. Custom gapps. After about a week, multiple apps will begin to force close at random. Reboot in a bootloop on the att screen. Only solution is to master reset and start again. This has happened twice now. Is the problem in busy box? Xposed?
Click to expand...
Click to collapse
I had the same problem back on android 6.0.1 and on 7.0. The problem is with the engboot. It's not stable enough to be used everyday. If you wan' t root, I recommend flashing stock firmware and waiting for this guy named Nitay Artenstein to come out with a root. He is currently testing s7 Qualcomm variants to see if his exploit works.
TomatoesOnBluRay said:
I had the same problem back on android 6.0.1 and on 7.0. The problem is with the engboot. It's not stable enough to be used everyday. If you wan' t root, I recommend flashing stock firmware and waiting for this guy named Nitay Artenstein to come out with a root. He is currently testing s7 Qualcomm variants to see if his exploit works.
Click to expand...
Click to collapse
Beyond that his exploit is aimed to be a bootloader unlock which will open the flood gates for development.
Is bootloop when it's stuck on att logo screen and pulsating and won't turn off unless from recovery? Because if so I'm having that problem. I didn't know my s7 edge was rooted until this problem started
First off.
1. There is a search button for a reason. Please use it guys.
2. The boot loop is caused by the Security policy updater trying to force the policy to update on the Engboot. The Engboot Security policy and the ATT stock Policy dont mix well when trying to be over written.
3. The engboot is perfectly fine for daily use. been using it for months with no issue. Its all the extra add ons people keep trying to Mess with and install that make it unstable.
To fix:
Odin stock firmware.
ReRoot with Engboot and disable security policy updates.
Also. There will NEVER be an unlocked bootloader for the ATT Variant of this device. Whoever tells you that they are working on a bootloader exploit is lying. Whoever says they have an unlocked att bootloader is also lying. This goes back to step one of this post. USE THE SEARCH BUTTON!!!!!!!!
Mod/Admin Please close this post.
Can anyone give me a little guidance:
UK Vodafone supplied S7 Edge, not rooted. Received Oreo update this morning, phone is now stuck in a bootloop - it will get as far as the "Android is starting... optimising applications", that goes away and then it just reboots.
I've been in to the recovery menu and tried wiping the cache partition - to which it reports "could not find /misc partition". Attempting to mount system partition reports the same thing.
Do I have any chance of resurrecting this? the firmware isn't yet on sammobile but I was wondering if updating via ADB or sdcard would help.
Grateful for any help!
install again via odin or directly on the Samsung page. with me it works super well
Can't get the ROM for Oreo as yet. Downloading 7.0 from sammobile and will try flashing that via adb and see if I can resurrect it. Anyone want to guess the chances of this working ?
Crafty77 said:
Can't get the ROM for Oreo as yet. Downloading 7.0 from sammobile and will try flashing that via adb and see if I can resurrect it. Anyone want to guess the chances of this working ?
Click to expand...
Click to collapse
That should work... download de 7.0 and install via Odin with mobile in download mode.
I always wake up my brick mobiles like this.
Have 'updated' my Ş7 with Oreo and now stuck with the boot logo.
Will they f***ing idiots from Samsung ever make a normal software without causing troubles?
My UK Vodafone supplied S7 also is stuck in a bootloop after the Oreo update.
My phone s7 is stuck in bootloop too. Don't know what to do. Nearest Samsung support is 36 miles away.
Its so hot to touch. Pressed all buttons to reset as advised but no luck.
wipe all in recovery or flash firmware through odin ,,
hope this helps.
here is the Oreo factory image for Vodafone https://androidfilehost.com/?fid=890278863836283079
only works with the latest Odin https://odindownloader.com/wp-content/uploads/Odin3_v3.13.1.zip
Galaxy S7 Vodafone here. Bootloop as well...
This update needs to be pulled. There will be thousands of people with the S7 on Vodafone most of whom won't be interested in using Odin to fix a problem caused by Samsung/Vodafone.
Just updated mine and wished I hadn't S7 edge, UK, Vodafone. Won;t leave the bootloop and cant get it to wipe cache or data. Can get it into download mode and shall be trying to reinstall
Updated my S7 Edge Vodafone - bootloop. Tried reinstalling with Odin and same result - still bootloop. This is unbelievable. Is this vodafone forcing this update or Samsung?
Any other ideas as I really don't want to wipe my phone completely? Have tried Odin reinstall twice just in case.
AndyBurmey said:
Updated my S7 Edge Vodafone - bootloop. Tried reinstalling with Odin and same result - still bootloop. This is unbelievable. Is this vodafone forcing this update or Samsung?
Any other ideas as I really don't want to wipe my phone completely? Have tried Odin reinstall twice just in case.
Click to expand...
Click to collapse
I had to wipe my phone.
Is this the only fix so far? Really don't want to do that if I don't have to as my SD encryption key is stored on the phone and I didn't decrypt it before updating...
Lammy696 said:
Is this the only fix so far? Really don't want to do that if I don't have to as my SD encryption key is stored on the phone and I didn't decrypt it before updating...
Click to expand...
Click to collapse
Hey Lammy696,
My mother is on Vodafone UK with the S7 Edge and is experiencing the bootloop. I would advise not to update for the time being.
I would strongly advise decrypting your SD card prior to updating.
I have tried wiping cache etc as per normal update process but that failed. Only options I have is to flash a custom recovery, mount the storage and backup (if I can do this) or to wipe it completely.
If you want to keep your warranty and support, do not use the custom recovery option.
Good luck.
Unfortunately I've already updated and have probably lost all that data now
Is it safe to update now?
Hello people, I need your help urgently.
A friend bought a used s8.
The old owner was still logged in with his account.
She tried in vain to achieve this, without success.
Since she is an "all alone" girl she has made a factory reset and behold, locked.
Now she started with Odin and Rome ..
End of lies, the device was stuck in an error message.
Now I got it.
Then I tried with twrp and Custom Rome, without success
The "OEM lock" is still set.
From the outside, I no longer have access.
Then I installed official Roms and at least managed to start it normally, initialized something and installed it up to another error message and slipped into a bootloop.
So, does anyone have an idea?
Because, I think that was it ..
Hi i have followed this guide (https://krispitech.com/how-to-root-the-galaxy-s10-series-on-android-11-load-magisk-on-boot/) made sure i done everything correct once the flash finishes and everything is fine the phone reboots and im stuck in a bootloop where just keeps booting back to the screen that says you have an unlocked bootloader.
i have reset it and tried again and its doing the same thing. i have tripped the knox so it must of done something. any help would be appreciated as i want to get this phone rooted now i have tripped the knox counter and voided my warranty.
Did you find a way to solve it? my s10+ is in the same state.