Hello and thank you for your help. I currently have a Samsung Galaxy J7 1st generation. The model number is SM-j727VPP.
I cannot root the phone, because no matter what I've tried the option for unlocking the bootloader will not work (I've tried every method) but the USB debugging option is available.
At some point I believed my phone had some kind of malware or rogue OS installed on it (since there is absolutely no security doing a hard installation (holding volume down, power, and home keys). Basically anybody who had access to my phone when I wasn't there could have installed some OS or malware using the download function since there is no security (i've heard the Galaxy S requires password or other validation to use hard reset/download functions.
At any rate, this is the phone I have and I want to root the phone with a custom OS to get rid of all the bloatware and use it as a Wifi phone (using a different phone as my primary phone).
So I've tried flashing with Odin, with no success and for a year now have been unable to root the phone and tried probably 10 times by now. The unlock bootloader does NOT appear in the developer options no matter what I do. Only the USB debugging options are available.
Also, if I try to do a system repair using the Samsung Verizon software repair tool it downloads the software, reboots the phone into download mode then has the following error: unsupport dev_type, and freezes at 83%.
If I hard reset the phone (holding volume up, home, and power keys it has some kind of error and displays the following messages:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
So basically, what I'm asking help with is to either (a) please help me find a way to root this device and put a custom OS on it to get rid of the bloat ware and/or (b) help me use the Samsung repair tool and get rid of the unsupport dev_type as well as these errors when I hard reset the phone:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
Thank you. ANY information and advice would be greatly appreciated.
Try This
user1003 said:
Hello and thank you for your help. I currently have a Samsung Galaxy J7 1st generation. The model number is SM-j727VPP.
I cannot root the phone, because no matter what I've tried the option for unlocking the bootloader will not work (I've tried every method) but the USB debugging option is available.
At some point I believed my phone had some kind of malware or rogue OS installed on it (since there is absolutely no security doing a hard installation (holding volume down, power, and home keys). Basically anybody who had access to my phone when I wasn't there could have installed some OS or malware using the download function since there is no security (i've heard the Galaxy S requires password or other validation to use hard reset/download functions.
At any rate, this is the phone I have and I want to root the phone with a custom OS to get rid of all the bloatware and use it as a Wifi phone (using a different phone as my primary phone).
So I've tried flashing with Odin, with no success and for a year now have been unable to root the phone and tried probably 10 times by now. The unlock bootloader does NOT appear in the developer options no matter what I do. Only the USB debugging options are available.
Also, if I try to do a system repair using the Samsung Verizon software repair tool it downloads the software, reboots the phone into download mode then has the following error: unsupport dev_type, and freezes at 83%.
If I hard reset the phone (holding volume up, home, and power keys it has some kind of error and displays the following messages:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
So basically, what I'm asking help with is to either (a) please help me find a way to root this device and put a custom OS on it to get rid of the bloat ware and/or (b) help me use the Samsung repair tool and get rid of the unsupport dev_type as well as these errors when I hard reset the phone:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
Thank you. ANY information and advice would be greatly appreciated.
Click to expand...
Click to collapse
Hi there,
Just a quick question are you able to boot into the device, like the home screen.
Sincerely
KIBS2173
KIBS2173 said:
Hi there,
Just a quick question are you able to boot into the device, like the home screen.
Sincerely
KIBS2173
Click to expand...
Click to collapse
Yes. I can boot the device and get into Android. However there is an app running called LLK agent and a user certificate called com.samsung.android.dqagent_SA_SDK that autamatically keeps reinstalling itself. There is also an app called SVC agent and BBC agent. None of them can be removed.
user1003 said:
Hello and thank you for your help. I currently have a Samsung Galaxy J7 1st generation. The model number is SM-j727VPP.
I cannot root the phone, because no matter what I've tried the option for unlocking the bootloader will not work (I've tried every method) but the USB debugging option is available.
At some point I believed my phone had some kind of malware or rogue OS installed on it (since there is absolutely no security doing a hard installation (holding volume down, power, and home keys). Basically anybody who had access to my phone when I wasn't there could have installed some OS or malware using the download function since there is no security (i've heard the Galaxy S requires password or other validation to use hard reset/download functions.
At any rate, this is the phone I have and I want to root the phone with a custom OS to get rid of all the bloatware and use it as a Wifi phone (using a different phone as my primary phone).
So I've tried flashing with Odin, with no success and for a year now have been unable to root the phone and tried probably 10 times by now. The unlock bootloader does NOT appear in the developer options no matter what I do. Only the USB debugging options are available.
Also, if I try to do a system repair using the Samsung Verizon software repair tool it downloads the software, reboots the phone into download mode then has the following error: unsupport dev_type, and freezes at 83%.
If I hard reset the phone (holding volume up, home, and power keys it has some kind of error and displays the following messages:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
So basically, what I'm asking help with is to either (a) please help me find a way to root this device and put a custom OS on it to get rid of the bloat ware and/or (b) help me use the Samsung repair tool and get rid of the unsupport dev_type as well as these errors when I hard reset the phone:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
Thank you. ANY information and advice would be greatly appreciated.
Click to expand...
Click to collapse
Make sure its a official device!
DankMemz said:
Make sure its a official device!
Click to expand...
Click to collapse
It is official. When I check the phone status it says Official.
user1003 said:
It is official. When I check the phone status it says Official.
Click to expand...
Click to collapse
Try reinstalling the Samsung drivers
Related
My wife has a stock, unrooted, developer options off Asus MemoPad FHD 10 (ME302C) that is stuck on the Asus logo. I am able to get into the bootloader which says:
IFWI VERSION: 51.33
SERIAL_NUM: 1111111111111111
DROIDBOOT VERSION: Local Build or ENG version
PRODUCT: US_EPAD
At the bottom it has:
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we skip check debricking
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we skip check debricking
FASTBOOT INIT...
FASTBOOT CMD WAITING...
I have attempted to do the Factory Reset and it says:
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we reformat now!
At this point the green progress bar pops up but stops moving and it will stay like this until the battery dies.
I have attempted "Fastboot -w" which results in it beginning to erase the user data with the progress bar moving properly but again it will stay like this until the battery dies and fastboot reports that it fails due to too many links.
I have attempted to flash recovery, and boot both ending in send ok write failed. Hopefully someone here may know what to do next.
Same problem, a next step to solve 31122014
Hello, I have the same Problem with this ASUS tablet. There is a different product type, instead of US_EPAD it shows me WW_EPAD.
One next step I found to solve the problem is, that the tablet need a connection to the Internet. In the middle of the screen there are read "No USB cable connected!. Link the tablet to the net and it is changing to "Ready for download".
I am not further which download is it, but maybe someone can tell here? Please!
Problem solved, but it takes to replace motherboard
Pierre again.
I sent tablet to ASUS-Repair in Europe. They checked functions and tried different Software updates. At the end there are no success by repairing or trying things. They changed Motherboard and the issue was solved.
Bye, Pierre
My tablet is the same IFMI VERSION: 51.33 US_EPAD the only way I fixed it was download newest firmware off ASUS support and used fastboot.exe to flash it to my tablet. Good as new. 1. fastboot -w 2.fastboot flash update <update.zip> The second on on my machine looked like this.
fastboot flash update US_ME302C-V5.0.21-0-ota-user.zip The tablet won't work if you try to flash an image older than what you had.
Dear Techies, please please help me with this. Tried all source of information available in the net to work it out. Couldn't reset my S7 edge. It once showed, moisture in charging slot, dry, etc etc. After that, when I restarted, these errors are what it shows .
(PS: Debugging option is not on
Developer options not enabled
OEM unlock not enabled )
It's my own clean unrooted phone which is past warranty.
Errors:
No support single-SKU
Supported API: 3
E: Failed to mount / EFS (Invalid argument)
E: Failed to mount / EFS (Invalid argument)
E: Failed to mount / EFS (Invalid argument)
dm-verity error
(Update from bootloader is disabled and update from SD is disabled)
I am able to enter recovery mode and download mode, that's all. FRP locked, Not recognized in ADB, Unable to root any recovery, etc.
Flashed stock ROM through ODIN and Smart switch. All firmware flashing success but errors are same.
Was on BRA9 official went to crc4 then back down to bra9 to accept the official ota.
Everything seems to be fine but in recovery I get this:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
File-Based OTA
Supported API: *3
# MANUAL MODE v1.0.0#
remove failed dir *‘/system/carrier/ATT/priv-app/AttIqi_ATT’ (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device or address
E: [libfs_mgr]Couldn’t get verity device number!
E: [libfs_mgr]Error removing device mapping: No such device or address
Successfully verified dmverity hash tree
The recovery seems to work as it could but just curious as to the cause if anyone has an idea. Especially considering it says error. Things like that incite the tinkerer in me lol
Have same issue on u3cr1 firmware
Encountered the same error after OTA update on TMobile. I did not tinker with the phone.
Now the phone is freezing and randomly rebooting at times. I have not seen the phone rebooting, but sometimes when I pick up the phone, it says you have to enter pass code instead of fingerprint as the phone was rebooted.
i have 2 error
First :: - In twrp internal storage showing 0M . And i already tried the repair method it didnt work.
Second :: - I try to install stock rom then it shows the error
" startup failed :
your device didnt startup successfully.
use the software Repair assisstant on computer to repair the device
connect your deive to your computer to get the software repair assisstant
Failed to validate boot image
ERROR:- failed to pass validation, backu to fastboot "
Please answer
@Param7183
Which device is this one? Brand / Model ?
I guess device's bootloader got corrupted.
A friend of mine gave me a phone (SM-A530F) because she bought it second hand and it asked her for a pin so I thought I would be fun to give it a try and fix it. When I powered it on it asked for no pin and I even got to insert my own SIM, log into my google account and browse the internet. The problem came when trying to make a call, when a pop up showed up telling my that the service was unavailable(?). When I restarted the phone it got into an infinite boot loop and now I can't get past the Android Recovery screen which displays the following at the bottom:
#Reboot Recovery Cause is [BL:Recovery Mode Set by key]#
Support SINGLE-SKU
File-Based OTA
Supported API:3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
dm-verity verification failed...
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible': No such file or directory
Now I'm downloading the "required firmware" from here (Spain) but I'm not really sure about what I'm doing (I'm studying system and network administration, so maybe I'm familiar with something)
Any tips? Thanks in advance <3
Friend use Odin program to flash stock rom in Samsung. I dont remember steps to flash via odin because I dont have samsung anymore but dont forget the rom binary must match your phones binary. It will give you error when trying to install wrong binary so you can see correct one