last week,I sent a topic,The link here
http://forum.xda-developers.com/showthread.php?p=19779397
Now,I got zhe special cable into fastboot,
I try to enter a few commands
1. fastboot -i 0x1949 flash boot boot.img
2. fastboot -i 0x1949 flash recovery recovery.img
3. fastboot -i 0x1949 -w
4. fastboot -i 0x1949 boot boot.img
fire reboot, Next pic,i'm load to here,anyboby can help me ?
http://forum.xda-developers.com/attachment.php?attachmentid=802066&stc=1&d=1322807775
Error effect:
MOUNT /CACHE Failure
http://forum.xda-developers.com/attachment.php?attachmentid=802068&stc=1&d=1322807775
/backup/backup_userdata.zip Short of
http://forum.xda-developers.com/attachment.php?attachmentid=802067&stc=1&d=1322807775
anyboby can help me ?
Well for start the picture quality is really really poor and I can't read a thing.
Related
so i keep having the disappearing status bar issue on CM7 so i booted into TWRP, fixed permissions wiped cache and dalvik and hit reboot system. now my kindle will only boot into TWRP. anyone know how to get it to boot to CM7?
Sent from my SGH-T959V using xda premium
Please use the search feature, this has been discussed countless times!! You need to set your device to boot in 'normal' mode via adb. The kindle fire utility also has an option to do this....
Sent from my Kindle Fire using Tapatalk
you said "boot to recovery" in cm7 - disable this option for the future !
http://forum.xda-developers.com/showthread.php?t=1399889
or
http://forum.xda-developers.com/showthread.php?t=1428428
or
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
b63 said:
you said "boot to recovery" in cm7 - disable this option for the future !
http://forum.xda-developers.com/showthread.php?t=1399889
or
http://forum.xda-developers.com/showthread.php?t=1428428
or
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
Click to expand...
Click to collapse
i wish i knew how to use adb commands
Sent from my SGH-T959V using xda premium
then use the unbrick utility (second link) - extract it to c:\ - run it
use option 2 - recovery loop
b63 said:
then use the unbrick utility (second link) - extract it to c:\ - run it
use option 2 - recovery loop
Click to expand...
Click to collapse
i can't as i'm on a mac and have no access to a windows computer...
i don't know about a mac
but you should have a directory where an adb executable is located
there you should open a command shell and issue the nessesary commands
this is what i found:
Android SDK Mac: http://developer.android.com/sdk/index.html
Platform tools installed: Go to the tools folder in the sdk. Make sure fastboot and adb are there. IMPORTANT: Check fastboot by doubling clicking it (make sure it doesn't say binary doesn't execute).
Adjustments: Make sure that you are using the ./ version of the commands. When it says to input SU, input su.
FAQ: Stuck at fastboot, and adb is not connecting? Depending on circumstances, answer may vary. In my case, here is the terminal log (AMA is my computer):
AMA:~ Aidan$ cd /Users/Aidan/Android/android-sdk-mac/platform-tools
AMAlatform-tools Aidan$ ./adb devices
List of devices attached
AMAlatform-tools Aidan$ sudo ./fastboot oem idme bootmode 4000
then power off / on
update:
think you can use my previous commands:
now you need to first navigate to your platform-tools folder in your android sdk folder using terminal.
Go to utilities in the applications tab in finder. Open up Terminal.
Now type the following line to navigate to the platform-tools folder.
cd ~/androidsdk/platform-tools
for me it is this because my SDK folder is named "androidsdk", if your's is named differently, insert it's name where androidsdk is.
followed by that you can start using ADB. Instead of running things as
adb root, or adb reboot, you need to include
./ before the commands, IE: ./adb root, or ./adb push
IE THE FIRST STEP IS "adb root", rewrite this is "./adb root"
from then on, include that ./ before any command.
ok so i have both fastboot and adb working, now what do i have to type in order to get this to reboot properly (i'm sorry for asking so much, but i'm a COMPLETE adb noob).
we have look what you have available - adb or fastboot
as first:
./adb devices
get a response ?
if not:
./fastboot -i 0x1949 getvar product
it should return "kindle"
gimme the results
the first time it worked and then when i did it again as a double check, my kindle started to boot (as it always does when it's plugged in and now it is stuf at the yellow triangle....
EDIT: finally got it to turn off, so fastboot registers it, what next
what commands did you exactly enter in the terminal ?
both the adb and fastboot commands you just showed me. but everything is back to normal, what do i do know that the kindle is recognized?
please copy and paste what is in the terminal window, that i can see to which command it has responded
what do you mean with back to normal ?
normal boot to os ? or to twrp again ?
basically the commands are the same as for windows - you have just to add ./ in the front:
this are the comands to set bootmode to normal:
when you have fastboot available:
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot -i 0x1949 reboot
or
./fastboot -i 0x18d1 oem idme bootmode 4000
./fastboot -i 0x18d1 reboot
or
./fastboot oem idme bootmode 4000
./fastboot reboot
when you have adb available:
./adb shell su -c "idme bootmode 4000"
./adb reboot
fastboot is the one that responded.
Code:
Macintosh:platform-tools recardeeps317$ ./fastboot oem idme bootmode 4000
< waiting for device >
...
OKAY [ 0.201s]
finished. total time: 0.201s
Macintosh:platform-tools recardeeps317$ ./fastboot reboot
but it doesnt actually reboot the Kindle. it gets hung at the triangle still. if i get it to boot back to TWRP could i just make a back up and reflash CM7?
EDIT:
finally got it to reboot into CM7 with:
Code:
Macintosh:platform-tools recardeeps317$ ./fastboot -i 0x18d1 reboot
< waiting for device >
rebooting...
finished. total time: 0.000s
ok - now we know it is responding to fastboot without the address initialisation commands (that depends on the version of fff - the bootloader)
did you try to power it off manually (pwr button ~30sec) ?
why would you like to reflash ? is it defect or now just not starting ?
and yes you can switch it to other bootmodes as well:
normal = 4000
fastboot = 4002
recovery = 5001
now it's up to you what you will like to do ...
UPDATE: hurraaa !!! congratulations ! - glad that it's working again !
please mark the subject of the topic (edit first post) to [Solved]
i was tinkering with adb and i finally got it to connect to my kindle. i typed in the commands ./adb reboot now my kindle is stuck in the firefire bootmode and i cant get adb to recognize it. your help is greatly appreciated. i tried to hold down power but it just turns off. i hold power again and it stays in bootmode, doesnt go into twrp
if it makes a difference i was on ics aosp rom with twrp recovery
maybe holding the power button for ~30sec - it should turn off completely
or would try if you can issue fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
in your case with ./ at the beginning - i assume you'r on a mac or linux
b63 said:
maybe holding the power button for ~30sec - it should turn off completely
or would try if you can issue fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
in your case with ./ at the beginning - i assume you'r on a mac or linux
Click to expand...
Click to collapse
awesome. thank you so much!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
What's the command to flash a kernel for the Kindle Fire? I've tried several fastboot commands to flash the kernel or boot.img, but it always ends up being stuck in Fastboot Mode. The commands I've tried (IIRC):
Code:
fastboot -i 0x1949 boot boot.img
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 boot zImage ramdisk.gz
fastboot -i 0x1949 boot zImage
These commands appear to indicate success (by displaying "OKAY"), but they leave the device stuck at Fastboot. I've even tried setting Normal mode and rebooting:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
I also tried setting the base address, which apparently overwrote my recovery.img because I couldn't get into TWRP after that (had to reflash recovery.img):
Code:
fastboot -b 0x80000000 -i 0x1949 flash boot boot.img [COLOR="Red"][B](DON'T RUN THIS LINE)[/B][/COLOR]
The only workaround I have is to include the zImage inside the source tree of CM9, and rebuild CM9 in order to package the custom kernel inside update.zip. Then, I flash that from TWRP. This takes quite a while (about 15 mins) even with no changes to CM9 source. There must be a way to create a flash-able update.zip with only the kernel (and ramdisk), but I haven't discovered it. Even better would be a way to do this all from the command line, so I can script it instead of using TWRP. Any ideas? Thanks
You can create a flashable update.zip file containing only the kernel. Go to the Amazon Kindle Development thread on this site, and look for the kernel thread by IntersectRaven. There's a discussion on it within that thread. You could even modify his zips (which are downloadable) with your own boot.img. Or just use his overclock-capable kernels, which are are compiled for stock installs, CM7, and CM9. Neall
I made a mistake that when I do the following commands:
Code:
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
But i forgot to copy the TWRP 2.0.img to the device.
Now KF stuck in the fbmode, i can not get out of it. Anyone know the command to get out of fbmode, I did try fastboot -i 0x1949 reboot but it always boot to fbmode.
Thank you.
*************
I try the command
Code:
fastboot -i 0x1949 oem idme bootmode 5002m
then my KF has boot into normal mode.
Problem solve. Search button win )
Code:
fastboot -i 0x1949 oem idme bootmode 4000
That should do it.
If you are trying to install it, just run...
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
u copy twrp to your fastboot folder not your kf, than do fastboot boot twrp2.0.img or whatever u have it named.
Sent from my HTC Glacier using xda premium
smirkis said:
u copy twrp to your fastboot folder not your kf, than do fastboot boot twrp2.0.img or whatever u have it named.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I did copy to my fastboot folder in my PC but didnt work, I think the correct way its copy into device root folder.
By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device
s k said:
By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device
Click to expand...
Click to collapse
hi, i also experience the same problem as u. what i did is i flash breadcrust's mm firmware and nuclea rom. it fixed the problem
But I am unable to connect via adb and fastboot to!
can you give steps to do that?
jflee said:
hi, i also experience the same problem as u. what i did is i flash breadcrust's mm firmware and nuclea rom. it fixed the problem
Click to expand...
Click to collapse
Can you give me steps or links to install correct drivers and all that stuff?
s k said:
By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device
Click to expand...
Click to collapse
You can also flash stock rom. Follow the steps:
Prerequistes :
1) Install ADB and Fastboot drivers. Instructions in the following link
http://forum.xda-developers.com/showthread.php?t=2317790
2) Download Stock rom from "cyngn.com/support"
cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
3) Enable USB Debugging in Developer options and connect your phone to pc. Grant your pc, the permission for USB Debugging.
4) Enable "Advance reboot" in Developer options.
5) Now reboot your phone into bootloader.
5) Extract the contents of " cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip" to the ADB and Fastboot folder.
6) Open command prompt in the ADB and Fastboot folder.
7) Execute the following commands one by one:
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash -S 512M system system.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash reboot
8) Now you are in stock rom.
Please confirm your doubts before you proceed.
akvpappan said:
You can also flash stock rom. Follow the steps:
Prerequistes :
1) Install ADB and Fastboot drivers. Instructions in the following link
http://forum.xda-developers.com/showthread.php?t=2317790
2) Download Stock rom from "cyngn.com/support"
cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
3) Enable USB Debugging in Developer options and connect your phone to pc. Grant your pc, the permission for USB Debugging.
4) Enable "Advance reboot" in Developer options.
5) Now reboot your phone into bootloader.
5) Extract the contents of " cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip" to the ADB and Fastboot folder.
6) Open command prompt in the ADB and Fastboot folder.
7) Execute the following commands one by one:
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash -S 512M system system.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash reboot
8) Now you are in stock rom.
Please confirm your doubts before you proceed.
Click to expand...
Click to collapse
Unfortunately, none of the solutions listed in any place worked for me (permanent solution). What I mean by that is, the airplane mode got turn off somehow while playing with safe mode. But after a couple of restarts, the airplane mode gets turned back on.
As mine is still under warranty took it to a Lenovo Service center and checked with them. They confirmed that this is a motherboard issue and it will have to be replaced. I got mine during the first flash sale in May 2016 and looks like this problem is there with that batch of phones.
Try opening *#*#4636#*#* and changing band ti your native country. I know you would have already tried it.. Just in case you forgot or it helps. ?
Sent from my ZUK Z1 using XDA-Developers mobile app
I flashed cm13 and the problem was solved!
s k said:
By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device
Click to expand...
Click to collapse
---same thing happening by me, i have gone to service center but they guys say it's motherboard issue, please let me know if you have fixed this problem?
dharam29 said:
---same thing happening by me, i have gone to service center but they guys say it's motherboard issue, please let me know if you have fixed this problem?
Click to expand...
Click to collapse
Ah long ago, flashed another rom. It will fix.
I don't have that device now, I sold it
s k said:
Ah long ago, flashed another rom. It will fix.
I don't have that device now, I sold it
Click to expand...
Click to collapse
Thanks for your quick response, what's the steps for flashed another rom?