Hi everybody.
I have a tablet with General Mobile E-tab 4. It has been soft-brick when I install a custom rom. I guess it has been such, I removed the cable without the process is completed. I'm sure to I installed correct rom because previously I installed same rom to some model devices. I can access to the device with ADB but I haven't root access. I can use busybox because the rom includes busybox. But I can't install rom, like as I said, device hasn't root. When I enter "su" command, it says "file not found". I tried many tool to root device but none didn't work. When I tried "dd" command in busybox (it to install rom), it says you haven't writing permission.
I don't know why, fastboot doesn't work.
Also, the device hasn't external sd card slot.
How can I root or can I install rom to the this device? Please help.
Images
i.imgur.com/WhDetYC.png
i.imgur.com/QVaHhmT.png
Related
Is there a way to install APK's from any of the bootloader menus? I can install through ADB if the device is fully booted & I have enabled USB Debugging. Is that the only way?
If that IS the only way, is there a way to reset the device's "first boot" attribute back to true after the first boot, so that the manufacturer's setup software runs on the next boot?
get into recovery,run adb,type "adb install app.apk /data/app/app.apk" for installing as user app,or type "adb install app.apk /system/app/app.apk" to install as system app..
Sent from my LT18i
Awesome, I don't understand but I will try it!
If you have shell connection to the STB
Put the apk on an SD card
You must have busybox too (some devices have the applet)
while in bootloader busybox install ApkPath/ApkName /data/app/ApkName
so the first path is the sd card
Hello all,
So I am trying to install Flashex script to run some flash through DolphinBrowser. In the Process of doing that I installed BusyBox, SManager and Terminal Emulator
The problem is that everytime I try to run the Flashex in either Terminal Emulator or SManager i get the error message " Unable to confirm location of Busybox, please make sure you have busybox installed"
I have, busy box installed, re-installed it, tried installing it in /system/bin but to no avail.
I tried to reconfigure Terminal preferences as per this thread but still get same error message
I would greatly appreciate some help here as I am no expert in the inner workings of Android
PS: Device is Galaxy S4 Rooted with CF Autoroot and still on Stock ROM.
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
ewgrashorn said:
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
Click to expand...
Click to collapse
Are you using adb on Ubuntu? You have to run adb start-server as root.
Mevordel said:
Are you using adb on Ubuntu? You have to run adb start-server as root.
Click to expand...
Click to collapse
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
ewgrashorn said:
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
Click to expand...
Click to collapse
The build property ro.adb.secure=0 will override that. You can try putting it in build.prop, but if it doesn't work, you'll have to put it in /default.prop, which requires modifying the kernel ramdisk. While you're at it, ro.secure=0 will give you an automatic root shell.
I tried to root Acer B3-A10 tablet with Kingo Root.
Root is unsuccessful, however there are still file su binary files in /system/bin, /system/xbin etc.
Now I cannot enter PokemonGo 0.37 as it detects su binaries.
How can I remove those su files without having root to do it on Android?
Is it possible on Windows, Linux via shell? How?
I cannot find Linux drivers, just USB drivers for Win 7, 8 :/
I also cannot find stock rom that should be ACER_AV0L0_B3_A10_1.007.00_WM_GEN1.
Any help?
Thanks
Do you have custom recovery? You could root that way then install SuperSU and use the full unroot option. This is how I keep playing .37 and can still switch to rooted when I need it.
I dont have custom recovery or any kind of file to flash ...
Hello
My tablet is soft bricked so i want to apply update from ADB but it keep saying "E: Failed to open driver control. Permission denied"
My tablet is: Lenovo TB-X605F
I tried everything to repair this tablet but nothing work
Please help me
XX_MRBEAN_XX said:
Hello
My tablet is soft bricked so i want to apply update from ADB but it keep saying "E: Failed to open driver control. Permission denied"
My tablet is: Lenovo TB-X605F
I tried everything to repair this tablet but nothing work
Please help me
Click to expand...
Click to collapse
Do you have a custom recovery installed to sideload a stock/custom ROM flash able zip? You won't be able to use stock recovery for flashing. Usually ADB isn't accessable unless set in the default.prop file
@XX_MRBEAN_XX
What ADB subcommand returns that error?
Typically "Permission Denied" is returned when a subcommand gets invoked that only works on a R/W-mounted device or requires ROOT.
jwoegerbauer said:
@XX_MRBEAN_XX
What ADB subcommand returns that error?
Typically "Permission Denied" is returned when a subcommand gets invoked that only works on a R/W-mounted device or requires ROOT.
Click to expand...
Click to collapse
In recovery menu, i select "apply update from ADB"
Beforce i connect my tablet to my pc it's say "E: failed to open driver control. Permission denied" Stopping adb
And my tablet is not recognized in adv devices
XX_MRBEAN_XX said:
In recovery menu, i select "apply update from ADB"
Beforce i connect my tablet to my pc it's say "E: failed to open driver control. Permission denied" Stopping adb
And my tablet is not recognized in adv devices
Click to expand...
Click to collapse
That's NOT an ADB subcommand, but an option offered by your tablet's Recovery Menu.
Take note that ADB consists of three components
A client, which runs on your desktop computer
A server, which runs as a background process on your desktop machine. It manages communication between the client and the daemon running on the Android-powered device
A daemon, which runs as a background process on the Android device. FYI: That automatically gets started when device boots up if enabled in Android's system settings - keyword: system file named build.prop, there settings ro.secure=0 & ro.debuggable=1.
My advice: Download from Lenovo's website the USB-driver that matches your tablet and install it: never use any other USB-driver !
jwoegerbauer said:
That's NOT an ADB subcommand, but an option offered by your tablet's Recovery Menu.
Take note that ADB consists of three components
A client, which runs on your desktop computer
A server, which runs as a background process on your desktop machine. It manages communication between the client and the daemon running on the Android-powered device
A daemon, which runs as a background process on the Android device. FYI: That automatically gets started when device boots up if enabled in Android's system settings - keyword: system file named build.prop, there settings ro.secure=0 & ro.debuggable=1.
My advice: Download from Lenovo's website the USB-driver that matches your tablet and install it: never use any other USB-driver !
Click to expand...
Click to collapse
Okay i'll try that !
By the way, my tablet can have a microSD , can i put a zip in the microSD and flash it ? ??
XX_MRBEAN_XX said:
Okay i'll try that !
By the way, my tablet can have a microSD , can i put a zip in the microSD and flash it ? ??
Click to expand...
Click to collapse
Yes, but stock recovery may fail unless it accepts test-key signed zips. If not then you'll need a custom recovery that allows to do so or to disable a signature check
That or if your bootloader is unlocked you can modify the recovery file to replace /res/keys with a test-key one and use stock recovery to flash test-signed files
XX_MRBEAN_XX said:
By the way, my tablet can have a microSD , can i put a zip in the microSD and flash it ? ??
Click to expand...
Click to collapse
Using ADB sideload, you can easily sideload any signed and/or unsigned ROM and any signed and/or unsigned MOD zip files: no need for any external SD-card. IMHO that's the most convenient method.
Code:
adb devices
adb sideload <PATH-TO-ZIP-FILE>