Hi,
I'm trying to root my Iconia B1-750 but still not able to do it.
I tried :
the solution in this tread http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
but got this error when the tablet reboot :
E:installer device ignored
FASTBOOT INIT ...
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type 'vfat'
E:installer device ignored
E:installer device ignored
E:No valid installer medium found.
FASTBOOT CMD WAITING...
Could not open /sys/devices/virtual/blacklight
Anyone retrieve a solution ? please help
Is it a problem of bootloader locked ?
Thanks
At2015 said:
Hi,
I'm trying to root my Iconia B1-750 but still not able to do it.
I tried :
the solution in this tread http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
but got this error when the tablet reboot :
E:installer device ignored
FASTBOOT INIT ...
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type 'vfat'
E:installer device ignored
E:installer device ignored
E:No valid installer medium found.
FASTBOOT CMD WAITING...
Could not open /sys/devices/virtual/blacklight
Anyone retrieve a solution ? please help
Is it a problem of bootloader locked ?
Thanks
Click to expand...
Click to collapse
Hello,
Same problem here, if someone that managed to make this method work, please help !
I've read somewhere that T3 option was supposed to work on the B1-750 model.
Thanks for your help.
Related
Hi everybody. I'm in very big trouble with my Jiayu G4B and I don't know what to do.
Long story short: my device freezed while I was normally using it, took off the battery and rebooted = ENCRYPTION UNSUCCESSFUL (in Chinese), so I tapped the only button available (Reset phone) and then it rebooted into stock recovery (dead androd robot with red !).
I tried to sideload latest Jiayu official rom for my device through ADB, it successfully sent update.zip to the device but then I got this on the device screen:
Now send the package you want to apply
to the device with "adb sideload filename"...
Restarting adbd...
Installing update...
symlink: some symlinks failed
Installation aborted.
"adb root" works but "adb shell" results in:
/system/bin/sh: /system/etc/mkshrc[8]: id: not found
@ANDROID:/ $
PLEASE XDA HELP ME!!:crying::crying:
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.
Soft bricked samsung p5110 tablet (ERROR on recovery --> E: failed to mount /data )
Hi there all experts,
after spending MANY hours on trying to solve this issue using this forum, i finally throw in the towel and make a post.
I have a soft brocked Samsung Tab 2 10.1 which has the following problem:
ERROR on recovery --> E: failed to mount /data (Invalid argument)
E:signature verification failed when using adb sideload to send TWRP or any other file to the device
What does/doesn't work?
i can get into ODIN mode and send files, but then i get error message that it failed to mount /data
ADB commands are not accepted because device is not found by ADB drivers
i can however use adb sideload (with p5110 in stock recovery mode with option receiving file via adb sideload
when i use adb sideload i get the signature verification error
I can't get into Android to enable USB developer option and i don't think that option is on. Therefor i think dat ADB can't find the device and maybe also the reason that ODIN can't flash TWRP recovery
Who gives me the golden tip to 'unbrick' my Samung Tab 10.1 device and let me 'format' my data partition so that stock firmware can be uploaden via ODIN again.
I already tried to upload the P5110 16gb PIT file using ODIN, it looks succesful but i still can't flash custom recoveries using ODIN
Thank you very much in advance for helping this newby out!!
Regards, Mark
Mark_70 said:
Hi there all experts,
after spending MANY hours on trying to solve this issue using this forum, i finally throw in the towel and make a post.
I have a soft brocked Samsung Tab 2 10.1 which has the following problem:
ERROR on recovery --> E: failed to mount /data (Invalid argument)
E:signature verification failed when using adb sideload to send TWRP or any other file to the device
What does/doesn't work?
i can get into ODIN mode and send files, but then i get error message that it failed to mount /data
ADB commands are not accepted because device is not found by ADB drivers
i can however use adb sideload (with p5110 in stock recovery mode with option receiving file via adb sideload
when i use adb sideload i get the signature verification error
I can't get into Android to enable USB developer option and i don't think that option is on. Therefor i think dat ADB can't find the device and maybe also the reason that ODIN can't flash TWRP recovery
Who gives me the golden tip to 'unbrick' my Samung Tab 10.1 device and let me 'format' my data partition so that stock firmware can be uploaden via ODIN again.
I already tried to upload the P5110 16gb PIT file using ODIN, it looks succesful but i still can't flash custom recoveries using ODIN
Thank you very much in advance for helping this newby out!!
Regards, Mark
Click to expand...
Click to collapse
I read something about the NAND erase all option in ODIN....might this be an option for me to use? I have the PIT file for the P5110 16g and stock firmware.....so do you guys/girls give me a reason not to use it to use it with some directions.
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
Hello everybody,
first of all I'm, sorry for my newbie's awkwardness and for my bad english too...
I'm a linux (Debian) enthusiast and I'd liked to install it on my Lenovo Tab M10 Plus; my choice felt on "Linux Deploy" but it needs a rooted device so, after an internet search for tutorials and tips and a system backup (.adb file saved on PC) I bravely tried with Magisk... and I failed (or I think so).
The tablet start in a never-end booting loop and on the splash screen appears the message
"
Orange State
Your device has been unlocked and can't be trusted
You device will boot in 5 seconds
"
I can access in fastboot mode so I tried to flash a no-rooted (downloaded) boot.img but it didn't works (the flashing process reports OKAY but the device reboot anyway in Orange Status), I tried with the flashall command that reports
"
error: ANDROID_PRODUCT_OUT not set
"
I tried to wipe and flash but it didn't works, I granted the access in some recovery mode and tried to install the .adb backup file from the SD card but the system says :
"
E: signature verification failed
E: error: 21
Installation aborted.
"
I thought to open the backup .adb file for extract the original files (I don't know if it could be done and if it could be useful) but how?
I think someday someone more skilled than me will solve the problem but, waiting for that day... any advice ?
Thanks, anyway.
Cheers, Ste.
Use official Lenovo Rescue and Smart Assistant
Same problem...lenovo tab x606F firmware is not present in Lenovo Rescue Smart Assistant and you can't add it manually!
Yes hello, sadly I am having the same issue as well. Anyone have any ideas? Here's what I've tried:
[edit]