I have googled for days and looked all over xda and I can't find anything about this specifically so please accept my apologies if this has already been covered. I did something wrong when I was rooting my transformer prime and installing busy box. I was following the directions on androlinux for mac/linux (I have a mac). Now I can't use terminal emulator or any other app like that. They just crash when I open them. The /system/bin/bash file is missing. I can't adb shell. When I attempt I get "- exec '/system/bin/sh' failed: Exec format error (8) -". I tried wiping/factory resetting to no avail. When I try to adb remount the system partition to make it writable it says "remount failed: Operation not permitted". I tried to fastboot flash clockworkmod recovery and found out that fastboot isn't working. When I boot into recovery mode I get an image of an android lying on his back with the red !triangle icon. I tried flashing clockworkmod from rom manager and that didn't work. I tried to install busybox from the busybox app and it said there was something wrong with the superuser. This is the strangest thing is some applications act as though the rooting was successful but others do not and I think it is because I broke the shell. My serial number is known and the tablet boots up and works fine (except for the fact that I can't adb shell, fastboot, CWM, root, or unlock bootloader).This seems like a lot of rambling, I know, but if anyone could help I would be incredibly grateful.
just one follow up
Also when I tried to unlock the bootloader with the app from Asus I keep getting the error message "An unknown error occurs, which may be a network connection issue. please wait and try again later." I am logged into my google account through accounts/sync. I have a feeling it has to do with the problems I described above.
You could try reloading the stock firmware, if you're OK with having the system wiped.
http://forum.xda-developers.com/showpost.php?p=23656968&postcount=20
I tried downloaded the stock rom and renamed it EP201_SDUPDATE.ZIP put it in the root of the sdcard folder restarted and held VOL DOWN + Power and when i saw the white text hit VOL UP twice. Alas, still got a red triangle android.
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:
Hello, I'm a little bit new to all this, so any help and detailed instructions are very very helpfull.
So I have Gigabyte GSmart Aku A1 device (MediaTek 6589), I don't know if it's bricked or what but apparently is not working quite well.
When I turn on my phone, it just loads and loads and loads and nothing happens (waited for about 4-5 hours), that was starting to happen after I somehow installed CWM on my device with some tutorial, CWM worked for the first time and after next reboot, it disappeared and stock recovery came back (and the problem with infinite loading screen - only showing logo).
I have ADB drivers installed, SDK aswell, tried to put stock firmware (got it from official site) and in like 1/4 of installation it says:
Code:
symlink: some symlinks failed
After that, I tried to install few versions that I downloaded from that official site, but same error again and again. (I tried to install with SD card and with ADB too. ADB is only working when I go to "apply update from ADB" in recovery. I have also used 2 different types of SD cards.)
That didn't worked either, so I got to some russian forum, and using google translator I downloaded 5-6 types of custom ROM's / Firmwares. That didn't worked either, one time when installing one of those ROM's - it said something about signature..
After that I was trying to install those ROM's with ADB and with SD Cards aswell, but turns out that every single time I get error saying: "Installation aborted.".
I have ofcourse tried to wipe data/factory and to wipe cache too, but nothing helps..
Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.
I really don't know what to do anymore, so any help would be very very appreciated. Thank you for your help in advance, if you need any videos, pictures or something, just tell me.
Edit: When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".
BUMP!
BUMP^2!
luuksa said:
BUMP^2!
Click to expand...
Click to collapse
i would look for stock rom in form of full mtkdroidtools backup and preloader drivers for your mtk chipset
and flash it using flashtool (it uses preloader[you can determine if it's available/undamaged by turning phone off and opening device manager on pc and plugging phone to pc if there will be a flash in device manager before the charging starts it will flash ])
Hello to everyone.
I have phone LG g pro 2 D838 made in Korea, that has strange symptoms. When it boots, appear screen with keyboard and input box with text ''Enter PIN/password to decrypt 30/30 attempts remaining". After I entered some code, it shows "29/30 attempts remaining, and no matter how many times wrong code is entered, still remains 29/30. First of all I did factory reset., but nothing happened. Download mode working, and I try to flash latest stock rom 10f, but nothing happened. Then I try stock roms 10a, 10b and 10d, but still nothing. Next to the download mode, I have a recovery mode, in which there is no menu. In this mode, it is possible to access phone with ADB, but everything is read only, and system is not mounted. I can list folder contents, but I can't push or pull, and when i try to use shell, I get a message " -exec '/system/bin/sh' failed: No such file or directory", because system partition is not mounted. ADB Remount generate error " remount failed: Success ". I forgot to mention that every time when i try to flash stock rom, in box on phone display was written, in red letters, 'ROOTED'. I guess that unroot is not succeeded . Also suppose that possible solution is to flash some custom rom with recovery, but i can do that only if I have it in KDZ format. Does anyone know how to make a custom rom in KDZ format, or someone already has it? Does anyone know some other solution? Does anyone know how to bypass CryptKeeper.java?
Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
Hi, I was running leedroid m9 rooted s-off with twrp and it was working great until I had some bizarre out of nowhere system app crashes earlier tonight (I guess yesterday by now). Commence boot loop. At first I was unable to access recovery and was just met with another shorter boot loop. I was eventually able to get into recovery through the bootloader menu but with a glaring fault. It gave me the prompt as if it was the first time booting into twrp, asking if I wanted to leave the partitions in read only mode. I thought "well kinda weird but ok". Then I try to restore my last post install image. It starts out with something about being unable to mount data or find the crypto header, and then it's nothing but "failed to mount x (invalid argument)". Same result for everything. Wipe, failed, adb sideload, failed, even manually attempting to mount in terminal failed (invalid argument). We even tried just completely opening up permissions (I know, very bad move for security but we were at our wits end). Unable to detect the phone via RUU or ADB in any state I can get it to boot to. I imagine something going on with encryption is to blame here? But I don't recall opting for or setting up any encryption?
Basically, is this phone beyond hope? Is there anything magical I can do through the bootloader (also not detected by adb)?
Also, looking in terminal in twrp, I'm still a root user? Don't know if that helps shed a light on this.