[Q] Stuck in CWM, factory cable help - Kindle Fire General

I tried to prevent my phone from updating to 6.2.1 by changing /system/etc/otacerts.zip to /system/etc/otacerts.zip.bak. When I did this it rebooted into CWM and looks for update.zip (i renamed it b/c i didn't need it). now it loops because I can't choose to anything other than install update.zip
ADB won't find the device so I can't rename the file or push a new one. I built a factory cable which appears to work but I still can't see my KF. When I run lsusb it shows 1949:0006 Lab126 as the device.
Any ideas?
using Ubuntu 10.10
<update>
I can adb shell now. however, no adb functions seem to work. Anyone know how I can keep cwm from hi-jacking my boot? I would gladly go stock to get going again.

Related

Clockwork Recovery is Installed, Won't Load, missing recovery partition.

I'm putting this in General because this is my first time I've actually posted on XDA and I hope someone will move it to wherever it needs to be.
I've rooted my Nexus S a long time back when it was new, originally had some trouble with fastboot hanging on "waiting for device" I want to say trying PDANet fixed my problem then. I'm not foreign to the flashing/rooting process. And I know this is a long post but If you can please read it all it would be appreciated.
My Story:
>ICS was released and while Google said Nexus S would get an official update I saw some on XDA that were promising ports.
>I downloaded We Scream for Ice Cream Beta 9 and installed through Rom Manager
>About a month later I'm fed up with all the force closes and missing features the thread didn't inform me on and went to find another ICS Port.
>Downloaded and about to install through Rom Manager I'm informed that I need Clockwork (strange because I already have it) so within Rom Manager I flashed a new one.
>Install via SD Card and my phone reboots and then instead of loading recovery and doing its stuff I wait at the Bootloader screen. I try entering recovery myself and my phone restarts and again I'm at the bootloader screen.
>At the very bottom of the screen in gray lettering it says Fastboot FAILEDcommand
(As of now it displays the Google Logo with the unlock icon and hangs)
>At this point I decide I' going to flash over clockworkmod myself via adb. This should be the magic formula: via addictive tips (new user, can't include hyperlinks)
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
>Adb gives me an error similar to won't link after the mount/remount command. Also trying to cp the flash image to bin fails to work.
>I boot my phone, open Total Commander and try to copy the flash image myself to the bin folder in my root and it fails
(As of now I get error: device not found)
Then i think alright, maybe it's my drivers. I tried several different drivers from different tutorials because perhaps they are different in some slight way. >Whenever I try a new driver I can pick "adb Composite" "bootloader" or vanilla "adb interface".
>My device appears as "Android Phone" as the first entry in the Device Manager and the icon is a monitor with a small PCB chip in the corner.
>When the divers are completely uninstalled it appears in Other Devices with a yellow exclamation point.
>My understanding is that while it will automatiaclly grab the driver for USB mode, I have to force it to install the bootloader driver for when my phone is in the bootloader screen.
>And USB Debugging has been checked for everything I've done.
>Now i try to use PDANet, first I uninstall the drivers and install PDANet. Message appears saying there is already an Android Driver installed, I choose reinstall, select Samsung, pop says are you sure you want this driver, publisher cannot be confirmed? I click yes, I beleive that happens twice, it installs and then runs. It installed the vanilla "adb interface" driver.
(This is where I'm at now, the Fastboot FAILEDcommand is also gone.)
So now I'm like well there's fastboot, let me see if it recognizes it.
>Fastboot devices: nothing appears
>fastboot flash recovery recovery.img : it hangs on waiting for device.
>Same goes for other commands like OEM unlock.
All the while ROm Manager insists I have clockwork recovery verison 5.x - only it wont load and none of my PC options are recognizing the phone. So I can't flash over a different recovery image, and there;s nothing under alternate recovery in Rom Manager.
And the strangest of them all which may be Rom Manager's problem is that Super User FCs as soon as I try running it. Rom Manager states Super User gives it power at the end of the clockwork recovery flash, however, still says it's successful.
Before this entire thing my phone tried to OTA update to 2.6.7 for Google Wallet and where it would normally respond I got the Android Guy with a box and a yellow exclamation. This is also what I got when I first had some problems rooting months back before I flashed over images and roms. I figured it wouldn't update because it needed the stock recovery image and wasn't compatible updating with clockwork mod (however i think my phone has updated before with this method.)
I wouldn't mind rolling back to my stock deodexed version of Gingerbread at this point because the ROM I have now for ICS NFC and Bluetooth wont work among a slew of problems. And NFC was the major update in 2.6.7 in regards of tap to share and Wallet.
So I either need ADB and Fastboot to recognize my device to try reflashing clockwork and an Entirely new ROM remotely (if that's possible) or get clockwork mod on my phone to open.
More Details
Also when I load the recovery image and it loops back into the bootloader I get the message up top saying I don't have a boot image or recovery image. yet my phone still boots fine.
I really want my phone to work %100 again, can anyone help me?
I didn't read all you wrote, but if you're having trouble getting adb or fastbook to work correctly just use ROM Manager. Even if it says you have it installed, do it a few times. You can also go into settings and check off the format or erase recovery option before flashing.
It will eventually work. Just keep trying it.
Thanks
I know I've read things where flashing several times gets it to work. But I'm wondering if because SuperUser force closes without opening it's unable to give RomManager the permissions needed to complete the flash.
I've tried a few times ever once in a while. Still waiting, but adb will recognize my phone on my guest login but still no fastboot.
What rom you on? Have you tried going into app manager and then clearing data for superuser? Try that and then reflash the recovery a few times from rom manager.
If you're using CM9 alpha 11 or any of the builds by Koush, and superuser FC's from fresh flash. Clear the data, use root explorer or another app that has root access (it will prompt you for root access even if superuser UI won't open) then you can go into /system/app/ and delete or rename superuser.apk.
Once that is done, get the latest one from the market. Soon as it installs, clear the old data from the previous one by using app manager again. Then your superuser app should be working normally.
What's your phone model? (I guess it's I9020T)
When you boot into bootloader, does the fastboot devices command see the device properly?
You should use fastboot to flash your recovery. You probably have driver issues. Check the rooting guide at nexusshacks.com.
Sent from my Nexus S using XDA App
Fixed
Thanks to everyone and heir suggestions.
Eventually I downloaded another set of Fastboot and ADB registered with my phone and I was able to flash a new ClockworkRecoveryMod.
My only explanation is that the two tools where in the same folder this time - that was the only part that was different.
However ROM manager will still tell me I do not have Clockwork on my phone and when it 'flashed' it over it actually breaks my recovery partition all over again.
Thank god for ADB and Fastboot.

not sure what to call this problem

Ok, so rooted (razorclaw) ics 4.0.3 tf-101.
fully charged
when powering on, stalls at the eee pad screen. (sounds like a boot loop, but it doesn't go to recovery)
Cold boots fine, works great, no random reboots (yet)
Will not boot into recovery, has ww_epad-9.2.1.11-20120221 bootloader
stalls at "booting kernel image" I assume there is no recovery installed.. Tried to get cwm onto it but I cant get apx working, it wont recognize the device at all.
I didn't root it, someone else did and I have no idea what recovery is/was on it.
I bought the tablet used, and would like to fix it.
Once recovery is installed would this boot normally.
Ive been searching on here/transformer forums for a couple weeks and have thought I found the answer multiple times. I need a push in the right direction.
Tried to fix this for a while a couple months ago when ics first launched and gave up. (did the same thing when It had honeycomb on it)
edit::
the only solution I can come up with is using NVFLASH to try to restore it. Working on this right now, hopefully this is a sbk1//not working, cant seem to get the computer to recognize the device in apx mode. (win 7)
If your TF is rooted, you may want to give the RecoveryInstaller app a go.
http://forum.xda-developers.com/showthread.php?t=1346180&highlight=recovery
I forgot to add that I have tried that (tried it again just now.. twice, just incase it happened to work but it didnt.)
following these instructions:
"click the button and the Superuser app will ask for permissions. Then the tablet reboots and to enter it you have to keep the Volume - key pressed and when it the TF writes "Booting into recovery" on the screen press Volume + once"
also tried it without holding volume buttons when it reboots.
When I run it, and click the button to install recovery, it grants superuser permissions and then reboots, sticks at the eee pad screen again and it stalls at booting recovery kernal image. Anything Im missing?
Reflash a recovery image .sos and bootloader .ebt if the recovery image doesn't work.
Download any cwm flashable recovery and extract it twice to get the recovery blob out:
put the recoveryblob on your computer somewhere.
adb push C:\Location\Of\Blob\blob.blob /sdcard/
adb devices
adb shell
su
dd if=/sdcard/blob.blob of=/dev/block/mmcblk0p4 -
reboot
--
this should fix recovery.
Thanks for breaking that down! Im going to try this once I can get adb working.
Going to try another computer now. I'm beginning to wonder if the usb cord for my tf has gone bad.
You can do it on your tf too, via terminal emulator app since you can coldboot.
Download blob somewhere on tf, download term em. and run this part:
su
dd if=/Path/to/recoveryblob of=/dev/block/mmcblk0p4 -notice path/to is where you placed on Tf's INTERNAL storage.
reboot
Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"
Is BusyBox installed?
That it is, just reinstalled 1.20.. should i use a different version perhaps?
Ro.secure set to 0?
see the guide to flashing an insecure boot.img if it isn't, this may be the problem.
if you're on a rom this isn't the issue..
Try a different version of BB I suppose
simplywinter said:
Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"
Click to expand...
Click to collapse
Suggest you try method 3 in the following post.
http://forum.xda-developers.com/showthread.php?t=1622628
It does not require rooted TF. If you do everything right but still not working, you may have a faulty device.
^^ My peri runs that method, so that didn't work. :/
I think borked hardware, try NvFlash
just did this
ls - l /system/xbin/su
getprop ro.secure
returned: 0
So it is indeed set to 0.
NVflash.. well I would do that if I could get the usb connection to the computer working.. Still trying that.
Also, kokopopz
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.
simplywinter said:
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.
Click to expand...
Click to collapse
The following guide will be useful for setting up ADB.
http://forum.xda-developers.com/showthread.php?t=1071584
For the USB driver, you can try the naked driver.
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked
Note: I am a linux user. I set up ADB on my linux box. I did not try the above myself. I just came across them. They maybe useful to a Windows user.
Windows drivers are finicky, make sure you totally uninstall and reinstall them too. Took forever to get right on my computer.
no go with windows. I still cant seem to make this work... I have ubuntu on my laptop though. Can I even do this on Ubuntu? its 11.04
You can do this with Ubuntu no drivers required, just pick up the Nvflash wheelie for linux and get yourself a reflashed ROM.
Also you can still do this on TF. I had a very similar issue that I was able to fix by using Rayman's Blobtools (you can pickup blobunpack for windows in my bootsplash screen change guide).
Download the latest stock ROM for your device, and extract the 'blob' file out of it.
Put the blob in the same folder as blobunpack.exe, then open a command prompt and cd to the directory, then run:
Code:
blobunpack blob
After that you will see that there are now many blobs, one of them is called blob.EBT, this is your bootloader blob. What you want to do is copy that to /sdcard/ on your tf via mass storage or 'adb push blob /sdcard/' (You Have to remove the .ebt extension, it's just there as an ID, so it should just be 'blob')
Once that's there flash it through the staging partition (In terminal emulator or adb shell):
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
Then it shouldn't get stuck at the Eeepad screen anymore!
If it still does, you might have that weird problem where nothing flashed through staging partition sticks, so you'll need to run Roach2010's fix.
after trying that.. twice. It doesn't seem to stick. Roaches 2010 fix it is, searching for it right now.
If you can get adb shell access (I'm assuming yes) PERI has the fix bootloop option. Otherwise run roaches fix AFTER flashing a new recovery and EBT partition but BEFORE rebooting.
how do i run roaches fix. i Dont understand that part. I understand the rest though.

Problems with adb

Hello,
So a few days ago my nexus 4 got a virus that started hijacking my text messages and made it so that the phone would not mount as mass storage to a computer. Also adb wouldn't work and i did have usb debug on. Anyway so I have TWRP installed so I just did a storage format totally wiping android and the virus from the phone. After I did that I tried pushing a nandroid backup that I have over and adb told me that the device was not found. I tried pushing the file in the bootloader, the recovery and when its trying to boot an android that's not there. Then I tried re-installing all of the usb drivers and adb. Still nothing. The I tried the adb sideload in TWRP. Still nothing. So dose anyone have any ideas about what this could be?
Thanks a bunch,
You can't use adb commands in fastboot. You should be able to do an adb push while sitting in recovery; don't use sideload unless you are sideloading something. If you can't get it to work, flash a rom and do it from within android.

[Q] Nexus 4 can get to TWRP, but no image/not able to communicate with PC

OK. I have spent the last 8 hours reading and trying my darnedest to get my phone up and running.
I wiped everything, and formatted data accidentally.
Now the phone wont mount the USB so I can put a ROM on it. I cannot get drivers to make either the skipsoft toolkit or the WugFresh tool kit to work.
I have read on ADB side loading, but cannot figure out how to get the phone to get recognized in order to connect with it. As it sets right now, I am stuck at the bootloader image, or TWRP recovery. No image on the phone, and I cant seem to get the drivers to allow my PC to see the phone. (Ive used WugFresh drivers, naked drivers)
Any help you guys can give me would be awesome.
Thank you
Mark
Hey there,
Our phones are MTP devices and because of that (I think) we can't mount them as a usb drive. But yea you can use adb sideload to get yourself up and running again.
For the drivers try this: http://forum.xda-developers.com/nexus-4/orig-development/toolkit-skipsoft-android-toolkit-nexus-t1995688
On your Phone:
1. Boot into TWRP,
2. Tap advanced,
3. Tap adb sideload,
4. Swipe to start sideload.
Once it says its waiting or something like that, it's ready to sideload from the PC.
On your PC:
Put the rom you wanna flash in the same folder as adb. So if adb is in C:\adb\ then put the file there.
In CMD type in adb sideload filename.zip (filename.zip is the name of your file you want to flash)
So an example would be:
Code:
c:\adb>adb sideload CARBON-JB-NIGHTLY-20131117-1149-mako.zip
It'll take a bit to transfer the file, but once it finishes you should be able to boot into the rom and use it normally again.
Hope it works for you, regards...
You can use Wugfresh to restore to stock and start over.

Can't copy files to /sdcard/

Hello everyone,
I recently decided too install the LineageOS.
Everything went fine, but I forgot Gapps and didnt want too use my phone without them so I decided too install the ROM again but this time with the apps.
I followed the linageos guide but accidently wiped everything before I could
Code:
adb push filename.zip /sdcard/
(dunno if thats the problem)
Im using TWRP 3.1.1-1. I can get into Recovery Mode. While in fastboot modus my pc detects my phone as an OnePlus, in Recovery modus its just android.
Code:
fastboot devices
shows my serial number. OEM is unlocked.
while in recovery mode
Code:
adb push filename.zip /sdcard/
gets me
Code:
No such file or directory
Code:
adb push C:\User\...filename.zip /sdcard/
gets me
Code:
failed to copy.. remote couldnt create file
while in fastboot mode I get
Code:
no devices/emulator found
Copying by dragging the file into internal storage doesnt work neighter.
I dont know what I did different besides the wipe before the copying. Maybe the wipe deactivates USB Debugging?
Maybe someone sees where my problem is.
Thanks
r717
I guess you don't have an OTG Drive.
you could always go 100% stock again and then flash LineageOS
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.13/
well first thanks for your reply. I flashed the original recovery and tried 2 sideload now. Seems to be driver problems. So I have to try every solution with Win10 and OP5 drivers I guess?
Make sure the Android drivers on your computer are up to date and also that you don't have any old drivers from a previous phone. I accidentally wiped everything on my OP5 once but when I connected it to my Windows 10 computer the OP5 was still recognized as a storage device--but I used TWRP not the stock recovery and also used the file explorer in TWRP. With the stock recovery you should still be able to side load flash the stock ROM from your computer. If you can't it's likely a driver issue.
I had once a similar issue, although not exactly this, just something with drivers.
A long process to fix was to install Linux as a virtual machine in Windows and that worked well. I could do all I needed, the phone was quickly recognized.
Virtualbox or VMware both are free/have a free version and I used Ubuntu.
Give it a try if all else fails.

Categories

Resources