I was following the directions to root my daughter's YP-GB70 using SuperOneClick from recovery and now is stuck in a boot loop that keeps sending it into recovery mode (stock Android System Recovery <3e> not a CWM recovery).
One the device, it shows the following:
Code:
-- Copying media files...
Successfully copied meida files.
# MANUAL MODE #
-- Appling Multi-CSC...
Successfully applied multi-CSC.
The misspellings are what is actually shown and that is as far as it gets.
I'm able to get to an ADB Shell, but not much else.
SuperOneClick freezes at:
Code:
Killing ADB Server...
Starting ADB Server... (daemon not running. starting it now on port 5...
Any help would be appreciated in getting out of this. Because it never got to actually root, I can't install a CWM recovery so I'm stuck with it where it's at.
Use odin or heimdall to flash the stock firmware for your device.
Related
Current issue is that I my phone will boot just fine into regular startup however it will no longer boot into recovery mode.
I have tried the below methods but the main problem that I run into is that when I issue flash_image recovery /sdcard/recovery.img(I have tried multiple img files such as the clockworkmod and SPRecovery) however none of them have worked they are receive the below message.
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
error scanning partitions
What I need at this point is either a way to get some form of recovery loaded either the out of the box version or clockworkmod version working so I can flash my phone and get gingerbread loaded. Or I need to break the OS to the point where the phone will not load past the boot loader.
Phone information:
Droid 2 Global
System Version 2.4.330.A956.Verizon.en.US
Android Version 2.2
Kernel Version 2.6.32.9-g9e2c63d
What I have looked at so far:
http://forum.xda-developers.com/showthread.php?t=912224
http://forum.xda-developers.com/showthread.php?t=687280
http://forum.xda-developers.com/showthread.php?t=739212
http://forum.xda-developers.com/showthread.php?t=912224
Please use the Q&A Forum for questions Thanks
Moving to Q&A
same problem
i have the same problem
any solution?
Like the title says, my phone won't boot to Android after disabling the boot animation using the ToolKit v1.0. I can get into CWM recovery and download mode, but the ToolKit won't recognize the phone unless it's booted into Android. I've tried flashing it with the stock ROM as the phone is recognized in Odin, but no success.
EDIT: I reflashed the stock recovery, and the phone is recognized by ADB while in recovery mode. I tried pushing the original build.prop file that TookKit edited to /system/, but I keep getting the error message "adbd cannot run as root in production builds; remount failed: Operation not permitted." Obviously I don't have root access anymore (I tried changing the permissions of build.prop to -rw-rw-rw- but that did nothing). Any way around this?
Guys,
I need help. I tried to work the solution myself and spend days reading different forums and tried different tricks but no luck.
So basically I was asked by my wife to root her Hero as she wanted a higer version of Android to install Viber and some other programmes. I did that using instructions on a Cyanogenmod wiki and everything went fine. However the new rom made the phone a bit slow and clumsy, so I thought I'd look for a different older version that works. I tried numerous roms and they all for some reason were not suitable - either wouldn't boot or were force closing etc...
So at the end of the day I read somewhere that for some ROM you need to install a CWM recovery and I was running a RA 1.7. So I tried to download a newer version of a recovery (to be honest I forgot which one - it was a week ago) and I flashed it and then I realised I have installed a recovery for CDMA and I have a GSM.
So, currently the phone boots and gets stuck at the HERO logo forever. There is no way I can boot into recovery. I have no problem to boot into fastboot, but any attempt to install a different recovery brings a failed signature error. I tried fastboot erase recovery and it did work, but no instalation is possible. When the phone is powered on and while on HERO logo I can run adb and can make it reboot from the command line, but when I try the instructions http://forum.xda-developers.com/showthread.php?t=1630519 I get past the first two lines:
Code:
adb push recovery-clockwork-2.5.0.7-hero.img /data/local/
adb push flash_image /data/local/
and then when I attempt this
Code:
adb shell chmod 777 /data/local/recovery-clockwork-2.5.0.7-hero.img
I get an error message
-exec /system/bin/sh failed no such file or directory
Please help!
PS. A screen shot in fastboot:
http://i3.photobucket.com/albums/y78/tsvet/fastboot.jpg
I managed to fix that with a stock rom and Hboot installation.
The scenario is that:
I purchased for the past year, ChainFire3d and found out to be effective. And right now I got a new phone and got it rooted. BUT, I forgot its running on 4.2.2 and ChainFire3d doesn't work on it. So, I am stuck on boot screen
I tried the following:
ADB commands to uninstall ChainFire3d, but in 4.2.2 roms, adb doesn't work in stock recovery for it has already have an alternative "update by adb support" which will let you go to adb sideload. And adb sideload mode doesn't support any other adb commands except sideload.
So, I tried to download a stock rom from a site, and tried to install it by "update by sdcard" and it says "Installation aborted" maybe because the stock recovery doesn't support the updater-script.
So, I tried fastboot, but fastboot cannot detect any device because stock recovery doesn't support adb.
And alas, I am out of options here.
Please help, somebody.
BTW, my phone is Lenovo A369i
OK... I managed to fix it.. after like... 10 hours .. whew
if you're wondering how I did it... here's how
...................
My android (jellybean) tablet was turned off in middle of update and now is in boot loop. It was rooted with USB debugging on.
I MUST recover files (PDFs, .doc, .wav .JPEG, etc ) without erasing them.
Questions:
1 Do I use Odin and TWRP together?
2 Will Odin flash Samsung stock firmware erase files on device?
3. Will TWRP .img file erase everything?
4. Are these instructions correct?
I recommend you install TWRP recovery. It's the most feature-rich of all the recoveries I have used, and I will be assuming that is the recovery you use for the rest of this.
1. Boot into TWRP. (how? TWRP is an .img file )
2. Push your ADB public key to your device to force authentication.
____On Windows, do: adb push %UserProfile%\.android\ad
bkey.pub /data/misc/adb/adb_keys
3. Reboot into Android. Try adb shell and see if you get a shell prompt. If so, great! Exit it and run adb logcat, and read the huge error log for problems. If you didn't get the shell, well, then I think you're screwed, unless someone has cooked up a recovery zip for enabling adb.
What happens after ADB logcat?
Thank you..