Database Users

[Solved] 6.2.2 Bricked Please Help

Ok, so I did something stupid, I tried to install a slider lock theme on my kindle and probably screwed up the Framework-Res. I did not have TWRP or a backup of any kind.
Now the kindle just sits at the boot splash screen.
The device was running on 6.2.2 and most tutorials seem to be made for 6.2.1
I have tried a few manual commands but remount is just say "Operation Not Permitted" (I cant figure out how to fix this either.
Running automated programs like Unbrick Utility just don't work, it says it has completed but you can see a bunch of errors saying it could not copy or not permitted etc...
At this point I just want my kindle fire back even if that means a complete restore, can someone please try to help or point me in the right direction I am about to go insane.
Added Info: To be more exact, I tried to use metamorph to install a slider lock theme, nothing seemed to happen so I closed the app. I thought everything was fine so I put the kindle to sleep, but I could not wake it up. I tried restarting it and that's how I got to were I am now.
Update:
Thanks to b63 I was able to get this fixed, I cant thank him enough.
Ok here is how I got it fixed
First I followed the directions given to me below by b63
he told me to refer to this http://forum.xda-developers.com/show...8&postcount=29 which I did, however When I got to 8 I did something different, I did not need to re install the whole Rom because I had only messed up the Framework-res.apk
So instead I pulled the Framework-res.apk from /system/framework in the official kindle 6.2.2 update.zip
I then used these commands to replace the broken apk on the device and restart in normal boot mode.
4. "adb remount"
5. "adb push framework-res.apk /system/framework/framework-res.apk"
6. "adb shell chown root /system/framework/framework-res.apk"
7. "adb shell chmod 644 /system/framework/framework-res.apk"
8. "adb shell idme bootmode 4000"
9. "adb reboot"
I know that this explanation is not super descriptive but most of what you need can be found below in the thread.
This problem is rather specific to my situation so if you are having the same problem and you can't figure it out send me a PM or reply to this thread.

Anyone? I'm starting to think i should just try to return it.

would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?

b63 said:
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
Click to expand...
Click to collapse
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB

Damieok said:
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Click to expand...
Click to collapse
ok i see a lot out of this - thanks
would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693

b63 said:
I would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Ok so I renamed the "Kindle Fire Utility" folder to "kfu" moved it to C:\
(if this is incorrect please let me know.)
And good news, adb shell responds with $, were should I go next. (also I have access to my normal computer now)
Thanks again for helping me out with this.

great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there

b63 said:
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
Click to expand...
Click to collapse
Im a little confused at this guide are the commands being entered into adb or in kfu? Were does kfu come into play?
Sorry the guide is a little hard to understand

it' not so complicated as it sounds ...
open a elevated command prompt and cd to c:\kfu\tools
here are all commands you need and where kfu comes in play
- you don't need kfu itself - only the tools folder
- leave the command window open all the time

[Q] Bricked Kindle Fire 6.2.2. Stuck on static KF screen

I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out

try this
Symberlei said:
I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out
Click to expand...
Click to collapse
I had the same thing happen to me (do not use Fastboot in recovery). This worked for me give it a try ; Kindle Fire Unbrick posted on liliputing. You'll need a PC with Windows. Just be sure you have the Kindle Drivers available, otherwise your USB may not see the Kindle.
Good luck

Why were you using Windows emulator to begin with?
Just use terminal and cd to your android sdk tools folder where adb and fast boot are and type: (with device plugged in and turned on)
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
Chances are that it will hang at "rebooting". If so just hold the power button down until it shuts off then turn it back on. It should start normally.
Sent from my Amazon Kindle Fire using xda premium

CD?
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"

Symberlei said:
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"
Click to expand...
Click to collapse
A quick intro:
cd is "change directory"
pwd is "present working directory"
ls is "list directory contents"
What you see in the prompt above is...
mac-users-macbook-pro-1634 - the name of your mac
~ - your pwd
macuser - your username
~ is shorthand for your home directory. i.e. '/Users/macuser'
e.g. If you type 'pwd' you'll get '/Users/macuser'
cd will change your pwd to what you specify
e.g. type 'cd Documents' and you'll change to that directory. This is analogous to opening up your Documents folder in the Finder.
If you then type 'pwd' at the next prompt you'll get '/Users/macuser/Documents'
If you then type 'ls' at the next prompt, you'll get the contents of your Documents folder listed
What the previous poster wants you to do is change directories to wherever you have the fastboot program so you can run it in the terminal. You can do this on the mac by typing "cd " (that's cd followed by a space) and then dragging the folder that contains the fastboot program into the terminal window. The terminal will automatically paste in the complete path (directory location) of the folder for you.
I suggest doing some more reading...
http://osxdaily.com/2007/02/07/basic-command-line-utilities-tips-commands/

Thank you but
Thank you so much that was incredibly helpful =D
it brought up the fastboot program and it says the following
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
mac-users-macbook-pro-1634:~ macuser$
What should I do after this?

*Bump* I still need help D=
I still don't know what to do after that last step or even if I'm in the wrong place. I'd like to have my kindle fire back up and unbricked before the weekends over. Please and thank you

OK so assuming you have terminal open and your current directory is your Android SDK tools folder...
it should read something like iMac-HD~ platform-tools "yourUsername"$
...all you need to do is type:
./fastboot -i 0x1949 oem idme bootmode 4000
Hit enter, then:
./fastboot reboot
It will say "rebooting". If it doesn't reboot right away just hold down the power button until it shuts off, then restart.
If you aren't sure you are in the right directory to start off in, type:
ls
That's "Ls" not "is"...you should see, among other things, adb and fastboot. If you are not in the right directory (edit: type cd in the terminal) find the Android SDK folder and drag it to your terminal window hit enter and type:
cd platform-tools
That should get you going in the right direction
Sent from my Amazon Kindle Fire using xda premium

ERROR:could not get pipe properties
Okay well I finally got all my directories sorted out so those are fine and I entered in your commands which worked fine (THANK YOU SO MUCH) but now I'm getting this error
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
./fasERROR: could not get pipe properties
< waiting for device >
^R
./ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
_____________
I've tried it again and now I'm just getting "..." and it's not doing anything. :/
mac-users-macbook-pro-1634:~ macuser$ cd /Users/macuser/android-sdk-macosx/tools
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
...

Success wooooo
OMG THANK YOU SO MUCH! I LOVE YOU! I seriously don't know what in the world I would have done without your help! I'm so happy right now! =D
If you ever need anything digitally designed hit me up at [email protected] I owe you one

Exact same problem resolved, my issue and solution
I've spent the past several hours banging my head against this problem. MBP and an iMac both running OS X 10.7.3 and VM Fusion 4.1. This thread seemed like the best place to share what I learned in case anyone else has a similar issue.
NOTE: I try and run everything inside vms to keep my base OS clean and just revert to snapshots frequently. Also I've rooted/modded a couple android phones with both these vms recently without incident.
Fought with two different XP Pro vms to get the ADB/Fastboot drivers installed. Kept getting an error about unsigned drivers. At some point the SDK drivers did install and I rooted successfully with KFU 0.9.3. Then I tried the TWRP install and had the same issue as the op. Stuck at the static Kindle Fire image. XP refused to recognize my KF and the drivers would not reinstall properly. Fastboot would remain at the "<waiting for device>" prompt when I used the fastboot -i 0x1949... bootmode command. I tried another route and booted a new OS X 10.7.3 vm and installed ADB/Fastboot. The same "<waiting for device>" prompt.
The problem had to do with the vmware usb implementation. I installed ADB/Fastboot to a non-vm install of 10.6.8 and my KF immediately responded to the bootmode command.
So if you're having a problem with the ADB/Fastboot drivers take a hard look at your usb setup.

Stuck in TWRP? ADB won't recognise device? Try this!

I was one of those sorry suckers that somehow got my Kindle Fire stuck in TWRP and I couldn't reset the bootmode to normal. ADB wouldn't recognize the Kindle while it was in TWRP no matter what I tried. Here's how I got it booting again.
1. Download Kindle Fire Utility here.
2. Unzip and open a command prompt in the "tools" folder inside of the unzipped kindle fire utility folder. Do this in Windows 7 by double clicking on the KFU folder and then doubleclick on the tools folder. Next find an empty space in the folder and hold down "shift" on your keyboard and then click your right mouse button. Select "Open command window here".
3. Type in this command and hit enter:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
When that properly executes it will say < waiting for device >
4. On the Kindle Fire inside of TWRP select Reboot -> System.
5. During the reboot process the fastboot command will execute and set you back to normal mode. Now type this in your command window on your computer and hit enter:
Code:
fastboot -i 0x1949 reboot
That ought to do it for ya.
*edit* Wish I could change the title somehow. I misspelled "recognize"

Thank you!!! it worked perfectly. I think this happened because once in the ICS rom I select to reboot into recovery using Room Manager and got stuck on it (bootmode 5001). Anyway this solved the problem in a blink!

You rock!!!! took me two days to find this post..... ugh

Kafluke said:
Wish I could change the title somehow. I misspelled "recognize"
Click to expand...
Click to collapse
LoL...just tell everyone you're British

[Q] ADB Can't Read Sideload

So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?

UpsideDownAce said:
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
Click to expand...
Click to collapse
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...

uncleswoop said:
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
Click to expand...
Click to collapse
Just to be sure, you've apply sideload from adb in the recovery, correct?

ducatic said:
Just to be sure, you've apply sideload from adb in the recovery, correct?
Click to expand...
Click to collapse
I'm in the same boat! I tried, today, several times to sideload the update but I'm constantly getting the cannot read sideload error message. I guess I'm off to other sites to see what the fix is.

I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]

YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Click to expand...
Click to collapse
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:

I might be just an idiot but why are you guys trying to SideLoad a system update?
AFAIK... sideload is merely to install apps into your rom that Jellybean or the Playstore doesn't like.
I think you guys want to use "ADB Fastboot" commands instead. Get a guide before you attempt to do this though. I used Wugs Toolkit to install the bootloader from 4.2.2 update.

fede01_8 said:
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
Click to expand...
Click to collapse
:laugh: true
For clarity:
- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.
Code:
adb sideload update.zip
- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img

fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.

fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
fede01_8 said:
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
Click to expand...
Click to collapse
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:

teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.

brandnewyc said:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
Click to expand...
Click to collapse
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:

Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'

I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!
Please help!!

Same problem...fixed
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~

jihoon526 said:
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
Click to expand...
Click to collapse
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!

Fix
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.

hkleiner said:
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
Click to expand...
Click to collapse
are you on the same directory as your file?

teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"

DigitalOSH said:
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Click to expand...
Click to collapse
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.

[Q] HD2 don't see of the pc when in fastboot mode (menù of clk)

Hello to all.
I am writing here because surely one of you will help me.
I have a notebook with windows xp 32bit, on which I regularly installed java jdk and android sdk (with whom I have downloaded the google usb drive).
When the phone is switched on (ROM started to understand), from the command prompt, running the command "adb devices" everything works perfectly, but as I enter fastboot (menu 'clk) and launch the command "fastboot devices" or tend to flash a recovery or simply to update clk, out the word "waiting of device" and does not go forward.
I state that I position it in the folder C: \ ....... platfotm-tools (where there are the files that I need).
thanks

g.andy said:
Hello to all.
I am writing here because surely one of you will help me.
I have a notebook with windows xp 32bit, on which I regularly installed java jdk and android sdk (with whom I have downloaded the google usb drive).
When the phone is switched on (ROM started to understand), from the command prompt, running the command "adb devices" everything works perfectly, but as I enter fastboot (menu 'clk) and launch the command "fastboot devices" or tend to flash a recovery or simply to update clk, out the word "waiting of device" and does not go forward.
I state that I position it in the folder C: \ ....... platfotm-tools (where there are the files that I need).
thanks
Click to expand...
Click to collapse
did you install fstboot drivers ? you should install fastboot drivers for install recovery on cLK do U
You can found the drivers here
http://cyanogenmod.arif-ali.co.uk/tools/windows/google_android_sdk_fastboot_adb_drivers.zip
or
You can use cLK 1.5 it is have recovery inside and allow you power off charge u can download it from here
http://www.fileswap.com/dl/oeioqdavTA/CLK_1.5.zip.html
hit Thanks if i helped Sorry for my bad english

AladdinSy said:
did you install fstboot drivers ? you should install fastboot drivers for install recovery on cLK do U
You can found the drivers here
http://cyanogenmod.arif-ali.co.uk/tools/windows/google_android_sdk_fastboot_adb_drivers.zip
or
You can use cLK 1.5 it is have recovery inside and allow you power off charge u can download it from here
http://www.fileswap.com/dl/oeioqdavTA/CLK_1.5.zip.html
hit Thanks if i helped Sorry for my bad english
Click to expand...
Click to collapse
I have CLK 1.5.1.6 with recovery touch b8, bit i want to upgrate at last version with not change recovery (the new version have twrp) and it is possible only with fastboot
I have unstalled fastboot driver(download with sdk), infact ADB work great, but fastboot don't see the telephone
Inviato dal mio HD2 - Pixeldroid v3.0 aokp JB 4.2.2

g.andy said:
I have CLK 1.5.1.6 with recovery touch b8, bit i want to upgrate at last version with not change recovery
Click to expand...
Click to collapse
Hi,
Try this:
On your device, enter recovery and connect via usb cable to your pc.
On your pc, download the latest Black-cLK (black_lk_20130314.img) and put it in the same folder you have adb.
Do a [Shift+RightClick] in that folder and select "Open command window here".
Execute these commands:
Code:
adb push black_lk_20130314.img /sdcard/black_lk_20130314.img
adb shell erase_image lk
adb shell flash_image lk /sdcard/black_lk_20130314.img
*I don't remember if the recovery you have now, has the erase_image & flash_image binaries. If not, you can take them from a rom and push them to your device.
Regards!

kokotas said:
Hi,
Try this:
On your device, enter recovery and connect via usb cable to your pc.
On your pc, download the latest Black-cLK (black_lk_20130314.img) and put it in the same folder you have adb.
Do a [Shift+RightClick] in that folder and select "Open command window here".
Execute these commands:
Code:
adb push black_lk_20130314.img /sdcard/black_lk_20130314.img
adb shell erase_image lk
adb shell flash_image lk /sdcard/black_lk_20130314.img
*I don't remember if the recovery you have now, has the erase_image & flash_image binaries. If not, you can take them from a rom and push them to your device.
Regards!
Click to expand...
Click to collapse
I will try. Thanks.
Inviato dal mio HD2 - Pixeldroid v3.0 aokp JB 4.2.2
EDIT:
Thank you all for the advice.
Honestly with ADB from recovery I have not tried but I solved by using another pc with w7. The only thing I do not spego is that with nthe same procedure on my pc does not work while on another it works perfectly.
I'll probably have to change pc.