G935P Rooted but something strange is going on with the stock recovery - Sprint Samsung Galaxy S7 Edge Questions & Answers

So my Phone is the G935P It's currently Rooted and here is some other info about the phone
Software Version: G935PVPU4BQAA (7.0 Sprint)
Now there is something weird going on when ever i enter the stock recovery I can see at the bottom dm-verity error ...
But im still able to boot the phone ...
I tried looking around on Google and Xda for the past few days and i can't seem to find anything about it does anyone know why it's showing dm-verity error ... and still letting me boot the phone
The full screen when i boot to recovery on my s7 edge looks like this
Code:
[B][COLOR="Yellow"]Android Recovery[/COLOR][/B]
[COLOR="Yellow"]samsung/hero2qltespr/hero2qltespr[/COLOR]
[COLOR="Yellow"]7.0/NRD90M/G935PVPU4BQAA[/COLOR]
[COLOR="Yellow"]user/release-keys[/COLOR]
[COLOR="Yellow"]Use volume up/down and power.[/COLOR]
[COLOR="Blue"]Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off[/COLOR]
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
Can anyone explain why it shows dm-verity error...
(and before anyone asks if i know what dm-verity is Yes i know what it is it's the function of the kernel that prevents unauthorized flashing unless the packaged is signed by the factory)

Related

I need help to root a Note 3, SM-N9005 ATL Android 5.0 N9005XXUGBOL3.

Hello, I need to root a Note 3, SM-N9005 ATL Android 5.0 N9005XXUGBOL3. It is encrypted and would like to be able to recover the data that I have. Using the Smart Manager app was restarted and has not returned to start, when it start asking for the decryption key, restarts, lock screen appears and restarts again, staying at the Samsung logo, varying the tone of blue LED and vibrating as if it were to start and again restart.
When I start it in recovery mode I get the error "e:failed to mount /data (Invalid argument)".
I tried to root to see if I can make a backup of the partition /data but it is not possible, I tried flashing by Odin CF-Auto - Root, CWM Recovery, Philz_Touch and TWRP, but I always get error, can only Flash the official recovery and the phone still does not boot.
I have not activated developer mode and I don’t know if I could do it from the recovery or flashing an alternative firmware.
If I couldn’t root it, I have to find a data recovery company, I need to get messages from a Samsung SAT about another terminal that they are repairing, so I would have restored the factory settings to see if it works again.
Can anybody help me?
Thanks.
PD: Sorry for my English.

dm-verity verification failed recovery

If i modify the system partition, the recovery greets me with "dm-verity verification failed".
I do *not* get the message about the DRK being invalid. My phone works fine.
Is there a way to remove this cosmetic error?
sins07 said:
If i modify the system partition, the recovery greets me with "dm-verity verification failed".
I do *not* get the message about the DRK being invalid. My phone works fine.
Is there a way to remove this cosmetic error?
Click to expand...
Click to collapse
No promises...
http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
I suppose that will work but i want my system partition modified/themed the way it is
I've heard it has something to do with the efs partition inside /efs/prov_data/dmvt or /efs/prov_data/dev_root
Maybe i can recalculate the hash value for the system partition and inject it somewhere?
My DRK is fine. just wish to remove recovery error.
i'm on stock recovery and my unit will always boot because I have the G930P eng kernel with dm-verity disabled. Stock recovery still thinks dm-verity is enabled because it just says "dm-verity verification failed" which is normal when you modify the system partition. I'm only trying to figure out how to remove the dm-verity verification failed error.
i can do such repair remotely
I have a galaxy s7 and rooted my device and some security update, updated my phone now I'm stuck in a bootloop.
I have tried Samsung smart switch and it wont take my model name. What do I do next?
kenny08vt said:
I have a galaxy s7 and rooted my device and some security update, updated my phone now I'm stuck in a bootloop.
I have tried Samsung smart switch and it wont take my model name. What do I do next?
Click to expand...
Click to collapse
Go to recovery mode. factory reset. should boot now.
Hello, Is there any update about how to fix?
Any way to fool your kernel/recovery into thinking dm-verity is just fine?
Samsung s7 says dm-verify verification failed after been reset

S7 Edge Bootloop + TWRP stuck loading Unable to format HELP PLS

Hi, I think I f***** up badly...
I wanted to root my S7 Edge SM-G935F running android 7.0 so I enabled USB debugging and OEM unlock.
I used Odin to flash a CF auto-root I found for the 935F for android 7 and the site just said I had to install SuperSU after that but it was just boot looping.
After that I installed TWRP for my phone and installed the zip with Superuser. I kept receiving the error "failed to mount /data (invalid argument)".
I googled it and found a video that said I had to change my system "file system" from EXT4 to FAT. It was stuck so I rebooted the phone...
Now I can't load TWRP (it's stuck at the loading screen) to do a factory reset and when I do a normal boot it doens't go further than the S7 Edge screen, it doesn't go to the flashing SAMSUNG screen.
Now when I choose to reboot in Odin mode it says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I tried to do that but it says "unsupported device" and it doesn't see my phone in the Emergency Software Recovery tab.
I could have done a factory reset before but it's not the first time I root a phone and I never had a problem so I didn't back anything up but I have some very important pictures on my phone for school.
I enabled adoptable storage so I couldn't just take out the 128gb Samsung Pro + micro sd and copy the pictures on my pc.
Can somebody please tell me how to factory reset my S7 Edge even if I lose all my data. Sorry for my English it's my third language.
Thanks in advance
If I can remember correctly the "An error has occurred while updating th......." screen is actually the same as download/odin mode, so you can odin flash back stock rom.
Your data has probably already been lost during file system changing which automatically format /data.
Also I have never seen any phone run on FAT file system. S7 only support EXT4 and F2FS(required custom rom and kernel). So be careful next time.
AFAIK, there's currently no root available on stock nougat touchwiz rom unless you use modified kernel&rom.
For TWRP to be able to read /data.
/Data need to be FORMAT in TWRP once to remove encryption, so that TWRP can read it.
Sent from my SM-G935F using Tapatalk
yeah iv done the same
so turns out i have done exactly the same as you did here
what did u do to fix this
MatthieuB said:
Hi, I think I f***** up badly...
I wanted to root my S7 Edge SM-G935F running android 7.0 so I enabled USB debugging and OEM unlock.
I used Odin to flash a CF auto-root I found for the 935F for android 7 and the site just said I had to install SuperSU after that but it was just boot looping.
After that I installed TWRP for my phone and installed the zip with Superuser. I kept receiving the error "failed to mount /data (invalid argument)".
I googled it and found a video that said I had to change my system "file system" from EXT4 to FAT. It was stuck so I rebooted the phone...
Now I can't load TWRP (it's stuck at the loading screen) to do a factory reset and when I do a normal boot it doens't go further than the S7 Edge screen, it doesn't go to the flashing SAMSUNG screen.
Now when I choose to reboot in Odin mode it says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I tried to do that but it says "unsupported device" and it doesn't see my phone in the Emergency Software Recovery tab.
I could have done a factory reset before but it's not the first time I root a phone and I never had a problem so I didn't back anything up but I have some very important pictures on my phone for school.
I enabled adoptable storage so I couldn't just take out the 128gb Samsung Pro + micro sd and copy the pictures on my pc.
Can somebody please tell me how to factory reset my S7 Edge even if I lose all my data. Sorry for my English it's my third language.
Thanks in advance
Click to expand...
Click to collapse

What would you advise Note FE died, sticks on Samsung logo; photos of recov mode

The FE forum has few visitors and it's a 7 so I hope this is OK.
Dev mode was on but not OEM whatever that is, or debugging, don't think. Never done any of that so not sure what's important.
It died overnight somehow, thought maybe an update but wasn't.
Would not boot past the small Samsung logo.
2 Photos of recovery mode and what it says.
~~~~~~~~~~
#fail to open recovery-cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB message: failed to find /misc partition
Recovery mode has the firmware and on 8.0.0
~~~~~~~~~~
I cleared cache and nothing changed.
Before I try to factory reset it, any advice?
Should I try to install the same software overtop? How to do it?
Or I would have to wait for an OTA update? Does a security update count? Do you think we'll see one soon that helps?
If a factory reset, my sd card data is kept, I assume, but what about any data on the main disc partition? Zapped into netherworld? Not sure what's kept there I might need. Moved photos already to sd.
Thank you.
I got the same issue, hope someone can help

Soft-bricked, messed up /vendor partition?

Ok, so I’m trying to fix this phone my friend messed up like a year ago and then gave up on..
Huawei P10 Lite
Build No: WAS-LX1C432B183
Bootloader: unlock
FRP: unlock
Rooted (or used to be I guess)
These are his notes from back then:
Flashed an unstable Lineage build and provided the wrong vendor.img –
tried to flash stock Nandroid backup through TWRP, which failed, phone was still running Lineage. Bugs got worse every reboot, finally stuck in bootloop on Lineage booting screen. Then did a full wipe and flashed stock ROM again - update_data_full_public.zip worked, update_full_WAS-L01_hw_eu.zip failed ("error:9")
finally flashed vendor.img the same way as with the wrong file in the beginning dd if=/external_sd/vendor.img of=/dev/block/bootdevice/by-name/vendor
now device can't mount /vendor anymore and bootlooping on the “ur device can’t be trusted” screen
Ok, so now I honestly don’t know what the last command actually does or if he got it wrong, he can't remember where he got it from and so far I didn't really find anything on it either..
I can now
• boot into erecovery, which starts but fails every time ("file does not exist"),
• do 3 button method, which gets to 5% then stuck again and returns to bootloop
• fastboot flash just about anything successfully according to logs – still bootloop
• use Unbrick option in the Multi Tool (which does the same as far as I can tell), again successful according to logs but still bootloop
• get into TWRP, flash stuff from there (stock, Lineage), also success but no change
I keep getting “failed to mount /vendor” in the logs though, and still can’t mount /vendor from TWRP and it says it’s 0MB.. I honestly don’t dare messing with partitions on my own as I’m not sure what the exact problem is..
Can someone please help?
Thanks already (and sorry this is so long..)

Categories

Resources