[HELP] Encryption Unsuccessful - Android Q&A, Help & Troubleshooting

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:

Related

Folio Mod help: Acess denied

Hello there,
I'm having many difficulties doing the folio mod.
Up untill now, i've been able to root folio 100 using SuperOneClick, and titanium backup works now.
I can also see folio with ADB, device being 161c10c944008217 (using adb devices)
Now my major problem: this folio has the latest update, that makes folio mod quite hard.
I tried using the normal power up into recovery, and updating with update.zip on the SDcard, it never worked, giving an error (E:signature verification failed).
I tried using http ://bb2k.org/folio100wiki/index.php/FolioMod_Issues, however, at
"How to Install foliomod after last toshiba flash upgrade - method 2 (all using ADB/USB)"
at the command
"adb push psneuter /data/local/tmp"
i get a permission denied.
Using
"How to Install foliomod after last toshiba flash upgrade - method 1"
at the command
"cat /data/recovery.img >/dev/block/mmcblk0p7"
I also get permission denied. They talk about using the "su -" command before, but i still get the same error, but it takes about 10 seconds.
Lastly, on the
"LOST or Destroyed partitions - METHOD 2 - ADB USB"
on the command
"fdisk -l dev/block/mmcblk0"
i also get permission denied!!
I use Air plane mode, USB debbuging on and USB to PC sharing off.
Could you help me and tell me what i'm doing wrong? It's the same error for the 3 methods, i guess i'm using the sudo command incorrectly, how should i do it?
Thanks for your help!
Try with fastboot
Sent from my IDEOS S7 Slim using XDA App
Thanks, that did the trick
Sent from my IDEOS S7 Slim using XDA App

[Q] - exec '/system/bin/sh' failed: Exec format error (8) -

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.

Geriatric NOOB fighting soft-bricked Kyocera Brigadier from an OpenSuse 12.3 desktop

This week Verizon pushed a firmware update for Kyocera Brigadier to Lollipop. We have two. One processed successfully.
Mine did not. Once the firmware downloaded and ran, my phone ended up stuck in the endless boot loop.
I can get it to the:
Android System recovery <3e>
LMY47V
recovery screen.
I run OpenSuse 12.3 on my computer. No Windows available. I installed ADB tools.
When I open a shell I get:
[email protected]:~> adb get-dev-path
unknown
[email protected]:~> adb usb
error: device not found
[email protected]~> adb root
error: device not found
[email protected]:~>adb start-server
[email protected]:~> adb root
error: device not found
[email protected]:~>adb reboot-bootloader
error: device not found
[email protected]:~> adb get-state
unknown
I had previously installed Kingroot on my phone and rooted it. Then uninstalled that and has SUuser for root access. When I started the update I had root access for the user not active and I did have the USB option for debugging active on my phone.
So I have a phone that I can move through the wipe data/factory reset successfully and the wipe cache partition successfully. I can power down. I can reboot to bootloader. When I select view recovery logs I get a lot flying through the screen, but most of that seems available.
Help Please! I haven't found a thread that helps me understand not finding the phone with adb. I haven't found a thread that answers whether TWRP, Fastboot, ADB, or what can assist me with restoring it.
Kyocera wants me to send it to them for 10 to ??? days for $20-$50??? bucks for an answer.
Thanks in advance, for directions to the right threads, the right answers, even if it means throwing it off a bridge.
Ken
Well, tried computer as root doing lsusb. The phone does not show up at all. It seems that answers that, eh?
I realize this thread is two years old, but for anyone else who may stumble across this:
Kingroot is Chinese government spyware. DO NOT USE KINGROOT.

[SOLVED]Stratos 2 - outdated firmware but no newer available / 'too many links' error

Hello guys,
I've got a Chinese version of Stratos A1609, currently on 2.0.1.0. I wanted to migrate to STRATOSfied rel 7. I unlocked the bootloader and tried to boot root-friendly image but it failed each time stating 'too many links'. I waited but it did not restart itself, it just sat there in fastboot mode.
Code:
fastboot boot STRATOSfied-boot-adb-root.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
FAILED (status read failed (Too many links))
So I thought I would need to upgrade the original firmware (as per this advice https://forum.xda-developers.com/showpost.php?p=75885199&postcount=109) first to solve that 'too many links' error.
However, I cannot upgrade my FW using the Amazfit app - I get only a toast stating I'm on the newest FW. I tried older Chinese version of the android app to try and upgrade to no avail.
Would anyone happen to know:
- how to go past 'too many links' error message in order to get root and continue with STRATOSfied ROM installation
or
- where to get original chinese 2.0.17.1 firmware file so that I can manually upgrade to that one first and try STRATOSfied afterwards.
THANKS!
TF666 said:
Code:
fastboot boot STRATOSfied-boot-adb-root.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
This is the correct output when installing the temporal root. After that you have to check root typing
adb root
adb shell
And you have to get # symbol which means you already hace root access.
Your FW version is very old and could cause problems. I suggest you to update manually to a newer CN one, in this forum there is a thread here: https://forum.xda-developers.com/smartwatch/amazfit/stratos-flash-chinese-rom-2-0-7-5-t3749698
Or you can use mine from Spanish forum here: https://www.htcmania.com/showthread.php?t=1398764
Thank you very much, @Saratoga79. Great script, simple instructions. You really helped a lot.
The firmware works and so does OTA, so great work there! I just incrementally updated to Chinese ROM 2.0.17.1 and then to STRATOSfied without any problems.
Thank you again!
Cant root my Stratos
subj.
Can not root (only $ after - adb shell) my Amazfit Sports Watch 2 (so called = Stratos) manually nor by script. Please help me pro...
ROM ver. 2.0.17.1 CN, and i want an EN ver installed.
Thanks
EndDie said:
subj.
Can not root (only $ after - adb shell) my Amazfit Sports Watch 2 (so called = Stratos) manually nor by script. Please help me pro...
ROM ver. 2.0.17.1 CN, and i want an EN ver installed.
Thanks
Click to expand...
Click to collapse
Did you unlock your bootloder? How do you do the root process??
Saratoga79 said:
Did you unlock your bootloder? How do you do the root process??
Click to expand...
Click to collapse
Yes, friend, im. Via Huami_AMAZFIT_Tool and unlockamazfit_com
about root.. its link with manual at gitlab_com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install
# You need to have ADB and FASTBOOT installed and working on your PC. For ADB you will need the universal drivers from Khoush (if you use Windows). YOU MUST HAVE EXPERIENCE WITH ADB AND FASTBOOT!!!
# DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY BRICKED WATCHES, LOST DATA, HEART ATTACKS OR WHATEVER. YOU DO THIS ON YOUR OWN RISK.
# This is gaining temporary root on Huami Xiaomi AmazFit Smart Watch (A1602), AmazFit PACE (A1612), AmazFit SmartWatch 2 (A1609), AmazFit STRATOS (A1619).
# This will boot a modified boot.img running adb with full root permission.
# connect your watch to your PC
adb devices
# this should list your watch, otherwise something is wrong
# now reboot into bootloader
adb shell reboot bootloader
# when you see the fastboot logo, check that you can access fastboot
fastboot devices
# you should see your device listed, otherwise your fastboot installation is not correct on your PC
# then boot into the temporary recovery
fastboot boot XXXX-boot-adb-root.img (where xx is "PACEfied" for A1602 and A1612 or "STRATOSfied" for A1609 or A1619)
# The watch should boot (apparently) normally. When boot is finished, you can enter adb via
adb shell
# you should see only a "#", meaning you now have full root access
#
# adb root is only temporary and will be lost after next reboot
#
# ATTENTION: You have full root power. All changes you do as root via adb may persist. You may brick your device if you do stupid things in adb (e.g. deleting the system or boot partition). "With great power comes big responsibility!"
waiting 4 ur instructions, friend.
adb cannot run as root in production builds - after "adb root" cmd
and [email protected]:/ $ after "adb shell"
---------- Post added at 10:04 AM ---------- Previous post was at 09:17 AM ----------
Now moved back to the 2.0.7.5_fastboot_mode ROM and ready 4 ur instructions, friend.
Please do not leave me, thank you
While trying manually flash Stratos Stock US Firmware 2.3.2.7 (just open flash_US.bat with Edit)
12. Flashing temporal root
fastboot boot boot-US-adb-root.img - 1st failture step
with "FAILED (status read failed (Too many links))"
and then, at "adb push install_recovery.sh /data/media/0/" - 2nd error - "adb: error: connect failed: no devices/emulators found" and fastboot devices shows only <waiting for device>...
But! After "reboot" all apps were optimized well and afterall OTA updated to 2.3.2.8
So, thx, it solved for now.

unbrick Lenovo tab M10 plus (x606x)

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]

Categories

Resources