I tried to restore to factory settings so I can flash another rom, it doesn't work, it also says I need a password... I tried that adb shell command or whatever and it just says no device found...
I am getting annoyed...
Related
I have bricked Kindle fire while trying to install Android Market. To the point that shell doesn't work.
I made myself a factory cable. So I can easily go into fastboot mode. I tried various ways that people post in different threads. None seem to work as expected.
Is there a way to completely flash the original amazon ROM in fastboot?
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
There seems to be very little help on how to use a factory cable. I am in a similar boat as you. Shell works for me but adb commands do not. I can't push or pull or install. I can navigate, change file names, and move files to some directories. My problem is that I don't know how to put the stock rom on and flash it. I actually have 6.2 on the sdcard but don't know what to do with it.
As for your problem, I experienced the same thing. adb devices didn't list my KF but I could see it in lsusb. I typed the usb description at $ "1949:0006 Lab126" and it called me an idiot or something but then I typed ./adb shell and vioala. I'm sure that didn't do anything and won't ever work again but there you have it.
I have a couple of open questions out there to see if we can get help and if I learn anything I will make sure you hear it next.
ToonaKan
Dmitry_G said:
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
Click to expand...
Click to collapse
You must insert cable, when switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
After kindle will be in fastboot, with Kindle Fire Utility v.6 install TWRP recovery and with recovey install stock or CM7 firmaware.
Admittedly, I am a little green when it comes to this but I never got it to list in fastboot devices either with a cable (and I am not sure I am supposed to), you can check if its connected in fastboot mode by:
fastboot -i 0x1949 getvar product
it should return "kindle"
from there I did:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot oem idme bootmode 4000
fastboot reboot
To get twrp up and running then I flashed the prerooted 6.2.1. Going back to the orginal rom should be similar
Ok. Passing "-i 0x1949" to fastboot helped and now I can communicate with KF in fastboot.
But a new problem has surfaced. I'm trying to install TWRP:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
It writes "downloading 'boot.img'" and gets stuck there. I waited for 15 minutes.
Ideas?
You need to now check to make sure your drivers are now up to date.
So it seems that I can't really do any operations with fastboot. Every command just freezes at the first thing it does. Weird.
I'm on a mac. I never installed any drivers for KF - it just worked. Do I even need a driver for KF on a mac?
There must have been something with the factory cable. I finally managed to load TWRP.
Now I'm trying to install stock ROM renamed to update.zip. I push it into /sdcard. Then in TWRP I tap on Install and select update.zip.
I get:
E:failed to mount /sdcard (Invalid argument)
E:Can't mount /sdcard/update.zip
What does that mean?
Ok guys. I found the solution. "E:failed to mount /sdcard (Invalid argument)" tells you that your sdcard is not formatted correctly. Here is the fix I did.
I already have TWRP installed and also have a factory cable. But I still have a few questions.
1. With a factory cable, is there any way to directly flash the stock firmware or do you always have to install and use TWRP?
2. From reading about TWRP, it seems that after installing it, you can then load the stock firmware onto the sdcard directory and then complete the restore operation. As a safeguard, and to make things easier, I have already put a copy of 'update.zip' on there just in case I need it. My question is - on an unrooted Fire, would it not be a good idea to stick 'update.zip' on the sdcard before rooting? That way if something goes wrong, all you need to do is get TWRP on there and the restore file is already in place. Or am I being overly cautious?
Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory
As the title says. I am trying to use ioroot25 and when I get to the recovery stage to push from adb, the iroot .bat says,
"error: device not found"
This is confusing me because each time I try to do this, I open up a separate cmd window and do "adb devices" and it tells me that my phone is connected. Not to mention that when adb DOES NOT detect my device, I can't even get to this step of ioroot.
All of this comes from me having numerous issues with CM11 (after installing from Malladus 2.0.3, had TWRP as recovery), so I decided to wipe clean and start over again. I used the LG Flash tool and flashed the correct Verizon 24a_11.kdz. Then I tried to root after checking the device was operational and adb couldn't find my device. I then did a factory reset through the phone as the restored version was acting a bit goofy, and this is where I'm at now.
Hello, i've been trying to install a custom mode but i can't because i only have access to recovery mode now because I made a backup but deleted when i wiped my data
So I tried to install my custom rom by using adb but when i type "adb devices" in cmd it just won't list it.
Do you know how to fix this?
Also, in ADB sideload, it shows me "unable to mount /usb-otg" dunno if it is important.
Thanks
EDIT : Problem solved, i went to pheriphericals and updated my G2 drivers.
My bootloader is locked and my phone's rooted I also have TWRP, and Xposed installed, so now I was trying to Stock reset my phone but it failed unconditionally. No matter how much times I've flashed the stock it failed. The error was "Failed the device is locked" so I tried unlocking it with the ADB commands but what happens is the after the passing the commands the device boots to TWRP, I tried clearing the data, internal storage, cache, and Dalvik cache and then I checked the device info via adb it's still locked. I cannot even install the stock recovery because it throws the error "Device is locked". What do I do now?
MaddySayaji said:
My bootloader is locked and my phone's rooted I also have TWRP, and Xposed installed, so now I was trying to Stock reset my phone but it failed unconditionally. No matter how much times I've flashed the stock it failed. The error was "Failed the device is locked" so I tried unlocking it with the ADB commands but what happens is the after the passing the commands the device boots to TWRP, I tried clearing the data, internal storage, cache, and Dalvik cache and then I checked the device info via adb it's still locked. I cannot even install the stock recovery because it throws the error "Device is locked". What do I do now?
Click to expand...
Click to collapse
Hello buddy,
I had the same problem on my op2 device and tried all the troubleshooting steps you mentioned in your post.
I got it fixed after figuring out another way all thanks to devs.
Twrp has an option called adb sideload.
Copy the stock rom on your pc.
Now in the click on the adb sideload option in settings whilst your phone is connected to a pc.
Simultaneously press hold the shift key on your keyboard and click the right mouse button to open a command prompt.
First command would be adb devices.
Once your phone shows up in the list type in the second command I.e
Adb side load (your rom file name.zip)
It will take some time but will load the stock rom in your phone.
i tried this but it shows an error "Invalid zip file"
okay tried it again with proper zip file but did not work
SOLVED! i just flashed the recovery.img file from stock via TWRP and later unlocked my bootloader and flashed stock rom and relocked my bootloader.
thank you for your help