I know this is 100% my fault but I was hoping that maybe the genius of XDA could help me out here.
1. Was using phone fine earlier.
2. Flashed Cyanogen 5.0.2
3. Flashed the newest radio version that Cyanogen linked in that thread
4. Didn't test
5. Started playing with 'fastboot oem' commands
6. Gave up tried to send a text message
7. No keybaord
8. Long press -> Input type -> nothing listed
9. Settings -> Keyboard and locale -> nothing about the keyboard.
10. Reflashed latest Cyanogen image
11. Still not working
I think during my fun of fastboot commands I screwed something up. The phone works perfect except I don't have a keyboard, the keypad in the dialer still works. Apparently somewhere along the line I lost my nandroid backup (yes, I know fail on me) I am currently looking for a keyboard app on the web that has a QR code so that I can install a 3rd party one from market. Will let you know how that goes.
Code:
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot flash radio
Radio_20100203_2_Signed_PASSION.img
sending 'radio' (24960 KB)... OKAY
writing 'radio'... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem -?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem secu
rity
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem s=of
f
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
... INFOtask: Parameter error
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
help
... INFOtask -1911570672 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
50
... INFOtask 80 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rtas
k 32
... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
... INFOstart keypad testing ...
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>a
'a' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot oem ?
... ^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rebo
ot
... FAILED (command write failed (Unknown error))
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
???????????? fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFOtask 8 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p
usage: fastboot [ <option> ] <command>
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
-b <base_addr> specify a custom kernel base address
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p passi
on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar
usage: fastboot [ <option> ] <command>
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
-b <base_addr> specify a custom kernel base address
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 1
getvar:1 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 2
getvar:2 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 3
2
getvar:32 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe
usage: fastboot [ <option> ] <command>
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
-b <base_addr> specify a custom kernel base address
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurity
security: on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurit
getvar:securit FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe flash hb
oot hboot-0.33.2012.img
sending 'hboot' (768 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>
Here are all of the commands that I have run since I last closed the CMD window.
Update: I have found the HTC Touch input APK and installed that on my phone. I can now long press input type and select touch input but whenever the keyboard should be coming up I get a force close. I know that on my G1 the HTC Touch input was iffy at best so I am still looking for another solution.
Another update: Got 'Better Keyboard' it works! (yay!) but when I goto click on the voice input it does not. I checked my search widget and the microphone icon is missing from there as well.
Someone posted their nandroid backup of a completely (rooted) stock n1 rom, search around for it and try installing it. I ran accross it while looking for tutorials on how to flash the stock N1 rom if that helps
Update: NOOOO!!!!!!! I did a full wipe from the bootloader (factory restore, dalvik-cache, rotate settings, and what ever that 4th one was and reinstalled cyanogen mod 5.0.2) bad news: all of my settings and applications are gone, as well as my customer ringtones. Very very sad day.
Oh yea, fixed the keyboard issue and the voice input issue. So I guess we can count this as win
Should have backed up your apps with astro or titanium
Oh I had a titanium backup, I just had to reinstall them all, and reset their locations on the home screens, and reset all of my ringtones and notification tones a process that takes a whole 5 - 10 min.
I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
usage: fastboot [ <option> ] <command>
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)
just found out my legend keeps creating files on my SD card called: qxdm_20101213_163620_1.dm
mertins said:
I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
usage: fastboot [ <option> ] <command>
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)
Click to expand...
Click to collapse
Happens sometimes when u try to flash a rom on your device.
Your phone has bricked, u now need to learn how to unbrick it.
Search the forums for how to unbrick, im sure u gonna be able to find a solution.
peace
ps don't worry its solvable
Thanks, now at least i know what is wrong
tried to follow the howto USB Unbrink-thread (mentioned it in first post) and as i said i cant even get past "step one"
I'll keep searching
mertins said:
C:\androidSDK\tools>fastboot eom enableqxdm 0
Click to expand...
Click to collapse
Right command: fastboot oem enableqxdm 0
posted at another forum and found that out
feel kinda dumb now, been trying to execute that command for three days :/
Hello,
a friend gave me hier "bricked" fon. I could get it booting again, system is up and running - but with any sdcard. Not the external and neither the internal one.
That means I cant put a SAPIMG.nph or anything else to the sdcard.
I cant download an apk or modify anything.
adb shell is working, but certainly su not.
adb push hboot_2010_signed.img /sdcard
certainly doesnt work either, there is no sdcard!
ok, I tried now different fastboot operations.
to come closer:
./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... FAILED (remote: not allow)
... etc... all the normal stuff.. nothing wortks, I usualy get "Not allowed on a production phone"
What to do now, I have no clue anymore!
here my data:
./fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x880705C0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 64
INFOTAG:hwid 0x1
INFOTAG:skuid 0x1E300
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x2
INFODevice CID is not super CID
INFOCID is VODAP102
INFOsetting.cid::VODAP102
INFOserial number: HT93YKF06262
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =346
INFOactive commandline: board_sapphire.disable_uart3=1 board_sap
INFOphire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=6
INFO4 androidboot.baseband=2.22.19.26I androidboot.cid=VODAP102
INFO androidboot.carrier=VODA-Germany androidboot.keycaps=qwerty
INFO androidboot.mode=normal androidboot.serialno=HT93YKF06262 a
INFOndroidboot.bootloader=1.33.0007 no_console_suspend=1 console
INFO=null
INFOPARTITIOM_NUM_MAX =6 Valid partition num=6
Do you see? There is the kernel option board_sapphire.disable_sdcard=1 set !!! But I cant disable it with a fastboot -c option.
./fastboot getvar version-main
version-main: 1.89.162.1
./fastboot getvar cid
cid: VODAP102C??a
#########
Any help is appreciated, thanks!
Code:
fastboot oem enableqxdm 0
Regarding root... follow my guide found in my signature..
./fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
./fastboot devices
HT93YKF06262 fastboot
[[email protected] HTC]# ./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
this seemed to get me a little further:
./fastboot oem rebootRUU
... OKAY
[[email protected] HTC]# ./fastboot -c "board_sapphire.disable_sdcard=0 board_sapphire.disable_uart3=0" reboot
rebooting...
YEAH!"
but then..... still no sdcard when the OS was up :-(
any ideas?
Type
Code:
fastboot oem h
and post here the result.
Root and recovery = follow my guide found in my signature...
Just replace all "/sdcard" paths with "/data/local/tmp"
UPDATE: It has come to my attention that zergRush root has been patched and no longer works on the most resent updates. At the moment I haven't checked to see what to use to replace it. I would advise anyone who is needing to unbrick your device to go over to this thread started by Vashypooh: http://forum.xda-developers.com/showthread.php?t=1399889. It is the Kindle Fire Utility v0.9.1 and has options to unbrick your kindle fire among many other great features. Please try his utility out as I have not been keeping up with this thread much over the holidays.
My kindle fire was stuck in a bootloop/bricked (info on what was going on prior to fixing: forum.xda-developers.com/showthread.php?t=1355371) after some complications when trying to install google apps. I may of deleted system files, really not sure what happened at this point. Anyway, this is what finally fixed it. This will get your device to the just out of the box state. Just follow along with the commands. I documented as much as I could, but if you have any questions feel free to ask. Hope this helps anyone whos Kindle Fire wont boot up!
For this to work you will need fastboot and zergRush root
get fastboot here: http://multiupload.com/TPWBYSCGM7
details on how fastboot works: http://wiki.cyanogenmod.com/wiki/Fastboot
zergRush root: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
->zergRush should be in the folder called files when extracted
Also make sure your device is charged, this will save you some time at the end!
I most likely not respond to private messages. This is a general thread so anyone can post here. It is beneficial to others since they may be experiencing the same problems as you. Being in my inbox wont help anyone.
***DISCLAIMER***: This process may not work for everyone! It really does depend on what you did to brick your kindle fire!! Also please consider thinking twice about messing with your device again after you fix it. Unless, of course, you think you can fix it on your own or are an advanced user.
PS: Read other peoples posts! Many have posted a lot of useful information, please use this to your advantage before asking questions!
PPS:What you did to brick your device is probably not unique. in order to prevent this thread from annoying those trying to help and from getting too long, we may ignore posts that ask questions or ask for solutions that have already been asked. If you don't get a reply within 24 hours, your problem probably falls under this.
PPPS:If the directions don't work and you don't see a solution in this thread already then you probably bricked your device beyond this way of recovery and need to seek other ways. If you are still having troubles please post a DESCRIPTIVE (pictures, links, anything and everything you did to get where you are at now) question/post with the problems you are facing and we can try and help you. Thank you.
---------------------------------------///------------------------------------
Hard reset may work for some people - hold power button for ~20 seconds and turn back on. If it doesn't then proceed:
---------------------------------------///------------------------------------
How to begin the how-to using cmd:
1. Download the files you need and stick them in your C:\ directory
2. stick fastboot in C:\KindleFireRoot\files directory
3. open cmd (command prompt)
4. navigate to the files directory on your C:\ drive
should look similar to this:
Code:
C:\users\userName>cd C:\KindleFireRoot\files
5. now you are in the kindleFireRoot\files directoryshould look something like this:
Code:
C:\KindleFireRoot\files>
Now you can start following the directions in the how-to and type exactly what you see to the right of the $ and # symbols. You should see them but do not type another one next to what you already see.
---------------------------------------///------------------------------------
IF YOU THINK MODIFYING PERMISSIONS ON /system/app IS WHAT CAUSED YOUR DEVICE TO BOOTLOOP THEN FOLLOW THESE STEPS:
check your permissions first
Code:
adb shell
ls -l /system/
they should look like:
Code:
drwxr-xr-x root root 1970-01-01 00:00 lost+found
drw-r-xr-x root root 2011-11-29 12:31 app
drwxr-xr-x root shell 2011-11-16 03:03 bin
-rw-r--r-- root root 2144 2008-08-01 12:00 build.prop
drwxr-xr-x root root 2011-11-16 03:03 etc
drwxr-xr-x root root 2011-11-16 03:03 fonts
drwxr-xr-x root root 2011-11-16 03:03 framework
drwxr-xr-x root root 2011-11-16 03:03 lib
drwxr-xr-x root root 2011-11-16 03:03 media
drwxr-xr-x root root 2011-11-16 03:03 tts
drwxr-xr-x root root 2011-11-16 03:03 usr
drwxr-xr-x root shell 2011-11-16 03:03 vendor
drwxr-xr-x root shell 2011-11-29 12:31 xbin
if yours do not look like this then continute:
follow the steps to temp root FIRST(steps 1 and 2 below)!
AFTER you temp root:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
then reboot
Note: this can work with any directory that has permissions messed up
---------------------------------------///------------------------------------
IF YOU CHANGED WALLPAPERS/THEME AND BRICKED YOUR DEVICE BY MESSING WITH FRAMEWORK-RES.APK TRY THIS:
if you have adb active, try
adb shell ls -l /system/framework/framework-res.apk
if you dont see it show permissions as rw-r--r--
temp root (steps 1 and 2) first then run:
adb shell mount -o remount rw /system
adb shell chown root /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell mount -o remount ro /system
adb reboot
if that does not work, then you need to go back to the old file, get it from the amazon update (download the update from their site and unzip it with 7zip or winrar, ignore the fact it's called bin and just rename it if you don't know how to do it otherwise to .zip).
then run
adb push framework-res.apk /data/local/tmp
adb shell mount -o remount rw /system
adb shell mv /data/local/tmp/framework-res.apk /system/framework/framework-res.apk
adb shell chown root /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb reboot
---------------------------------------///------------------------------------
IF NONE OF THE ABOVE APPLIES TO YOU THEN DO THESE STEPS:
//Step 1: push zergRush on the device then run chmod 755 on zergRush
Code:
$ adb push zergRush /data/local/tmp
$ adb shell chmod 755 /data/local/tmp/zergRush
//Step 2: temp root
Code:
$ adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd data/local
cd data/local
$ cd tmp
cd tmp
$ ls
ls
boomsh
zergRush
sh
$ rm sh boomsh [B]Remove everything but zergRush here, it will not matter if yours is missing/out of order compared to mine[/B]
rm sh boomsh
$ ./zergRush
./zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd195cb 0xafd3937f
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
//Step 3: reboot into fastboot
//note: 4002 for fastboot
Code:
$ adb shell
# cd /system/bin
cd /system/bin
# idme bootmode 4002
idme bootmode 4002
<idme> write 4002 to offset 0x1000
# reboot
reboot
//Step 4: clear user data and cache using fastboot
//note: 0x1949 is the device-id for the kindle so fastboot can recognize it
Code:
$ fastboot -i 0x1949 -w //this part might take a while
erasing 'userdata'... OKAY [110.203s]
erasing 'cache'... OKAY [ 28.328s]
finished. total time: 138.531s
//Step 5: change back to normal boot mode in fastboot
//note: 4000 is for normal boot
Code:
$ fastboot -i 0x1949 oem idme bootmode 4000
... OKAY [ 0.219s]
finished. total time: 0.219s
//Step 6: use fastboot to restart kindle fire
Code:
$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.016s
At this point the kindle hit splash screen for a few minutes then told me that my device needed to be charged (was at 13%) to continue. **So make sure your device is charged**, otherwise you will have to wait about 20-30 minutes depending on your charge %. The amber light finally came on while connected to PC which it wasn't doing before so this was a good sign.
After it was charged enough the next step stated: "Your kindle has detected a problem and must clear app storage.The recovery precess will erase some applications and data from your device. Apps from the appstore are stored in the cloud and can be reinstalled later. This will reset your kindle to its original factory settings. You will need to re-register your kindle prior to downloading items from your amazon account. Please press power button to proceed"
After you press the power button it shows a progress bar, reboots, hits splash screen for a few minutes then takes you to set up your Kindle Fire account YAYYYY!
Just a suggestion but perhaps one of the mods could move this to the developer's forum (or sticky it and make the links have http:// in front)? The OP could not post it there since they do not have 10 posts yet, but they're a friend of mine and we worked together to unbrick their device.
unbricking from recovery
I am going to try the method for unbricking, but not sure it will work on mine. My fire is stuck on the boot screen where it has a long message saying there is a problem with the fire and that it needs to restore the apps and bring it back to default.
It then says to press the power button continue with the restore. Then it completes, says success, then reboots right back into the same message screen all over again.
When I adb devices I get "firexxxxxSN recovery"
I am hoping fastboot can help me or perhaps I need to re-image recovery or boot.
What happened was this. I tried to follow a method to change my wallpapers using metamorph. I followed all the steps then started getting theme errors and such while in the kindle. I rebooted and was stuck in the bootloop as described here.
Being the novice I am, I thought I could then copy over a fresh copy of "system" from the fire system dump that was posted. I did this and this is where I am now.
Any help would be appreciated. It might be a good idea for us to figure this one out so that we have the procedure.
you dont need root to run idme.
But since you can get root, try clearing the /data/dalvik-cache by hand & reboot.. much quicker than a full userdata wipe.
Hi, assuming your responding to me, whats idme? Right now I cant get root just a bootloop. And when I adb devices I get my device serial # recovery where is normally says device serial # device
---------- Post added at 03:57 PM ---------- Previous post was at 03:46 PM ----------
Here is the exact message I get on the screen:
'Your Kindle has detected a problem and must clear app storage. The recovery process will erase some applications and data from your device. Apps from the appstore are stored in the cloud and can be reinstalled later.
This will reset your kindle to its original factory settings. you will need to re-register your kindle prior to downloading items from your Amazon account.
Please press power button to proceed.'
After i press the power button I get a status bar indicating the restore, it then says success, then reboots and ultimately comes back to the same restore screen as noted above.
Any help is appreciated.
Hey, can you please tell me how you get into fastboot? I went to the wiki and did everything it said there but am stuck because I am getting stuck on step 5
Boot device into bootloader - How do I do this? Is this simply powering on the fire?
Make sure the device is in FASTBOOT and not HBOOT - same question
I'm getting "zergRush: permission denied" any help?
Wow, I'm so glad I found this! You just may be my life/job saver. I'm going to try this right now and reply with status.
transfuntioner said:
you dont need root to run idme.
But since you can get root, try clearing the /data/dalvik-cache by hand & reboot.. much quicker than a full userdata wipe.
Click to expand...
Click to collapse
I tried this previous to what I explained in my fix above and it didn't work. I was still stuck in bootloop and getting the same errors in the logs.
transfuntioner said:
you dont need root to run idme.
But since you can get root, try clearing the /data/dalvik-cache by hand & reboot.. much quicker than a full userdata wipe.
Click to expand...
Click to collapse
@transfuntioner - This sounds logical and I did try this. In my specific case it didn't work either but may work for others.
Done! Thanks ubeezee your awesomeness knows no boundaries. I owe you big-time! I'ma gonna buy you a whole case of beers.
@md202000 Glad it worked for you!
justki said:
I'm getting "zergRush: permission denied" any help?
Click to expand...
Click to collapse
Can you give more explanation (i.e. what you were doing beforehand)?
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
bjanice44 said:
Hey, can you please tell me how you get into fastboot? I went to the wiki and did everything it said there but am stuck because I am getting stuck on step 5
Boot device into bootloader - How do I do this? Is this simply powering on the fire?
Make sure the device is in FASTBOOT and not HBOOT - same question
Click to expand...
Click to collapse
Don't rely on the wiki directions...those are meant for other devices (particularly phones). Just do the steps listed in the OP in that order. You won't get some screen that explicitly says FASTBOOT. You'll just assume you are there because fastboot commands will work (and the fact you told the device to go into fastboot before rebooting it through bootmode idme).
Hi, assuming your responding to me, whats idme? Right now I cant get root just a bootloop.
Click to expand...
Click to collapse
Just because you have a bootloop, does not imply you cannot do things like run adb. You need to run "adb shell" with the kindle plugged into the computer and then push over the zergRush exploit and get root and then switch the mode to FASTBOOT. You cannot as far as I know get into FASTBOOT on the device unless you are able to tell it to through temp rooting and adb first.
But since you can get root, try clearing the /data/dalvik-cache by hand & reboot.. much quicker than a full userdata wipe.
Click to expand...
Click to collapse
From trying that with ubeezee, it did nothing to help on its own. It took clearing out all user data to trigger a restore that did something useful.
bjanice44 said:
I am going to try the method for unbricking, but not sure it will work on mine. My fire is stuck on the boot screen where it has a long message saying there is a problem with the fire and that it needs to restore the apps and bring it back to default.
It then says to press the power button continue with the restore. Then it completes, says success, then reboots right back into the same message screen all over again.
When I adb devices I get "firexxxxxSN recovery"
I am hoping fastboot can help me or perhaps I need to re-image recovery or boot.
What happened was this. I tried to follow a method to change my wallpapers using metamorph. I followed all the steps then started getting theme errors and such while in the kindle. I rebooted and was stuck in the bootloop as described here.
Being the novice I am, I thought I could then copy over a fresh copy of "system" from the fire system dump that was posted. I did this and this is where I am now.
Any help would be appreciated. It might be a good idea for us to figure this one out so that we have the procedure.
Click to expand...
Click to collapse
Did you try it out?
justki said:
I'm getting "zergRush: permission denied" any help?
Click to expand...
Click to collapse
I think I know why, I forgot to add that you need to run chmod 755 on zergRush.(see updated first post)
adb shell chmod 755 /data/local/tmp/zergRush
after you push zergRush
i got to step 3 and there is no animation over the letters, so i think i am in fastboot, but i can not access the shell anymore. it appears my device is not being seen by adb? evn at a cmd prompt i tried fastboot devices and that shows nothing either.
any advice?
dingo8baby said:
i got to step 3 and there is no animation over the letters, so i think i am in fastboot, but i can not access the shell anymore. it appears my device is not being seen by adb? evn at a cmd prompt i tried fastboot devices and that shows nothing either.
any advice?
Click to expand...
Click to collapse
I'm not totally sure what you mean. Are you trying to access adb while in fastboot? Because that will not work.
When you're in fastboot, you don't use adb, you use fastboot commands to wipe all the user data (see the reference link in the OP for the commands that work on fastboot and note that it's nothing like adb). Fastboot runs a much lower level than anything you access in adb--it's like being in the BIOS for your computer more or less. It wont show "devices" or anything like that unless you explicitly run the "fastboot -i 0x1949 devices" command (I didn't bother to run that command on the kindle, I just jumped ahead and had it wiped using fastboot, since it didn't really matter if it detected it or not).
However, even if you don't run that command to show devices, you'll know it works when you run the fastboot command to wipe data and it gives you a reply. If it doesn't give a reply and just hangs, then you weren't in fastboot (or you typed the command wrong) and need to try again (press ctrl+c to cancel the command, but just FYI, it takes 3-5 minutes for it to wipe all data, so be patient before canceling).
dingo8baby said:
i got to step 3 and there is no animation over the letters, so i think i am in fastboot, but i can not access the shell anymore. it appears my device is not being seen by adb? evn at a cmd prompt i tried fastboot devices and that shows nothing either.
any advice?
Click to expand...
Click to collapse
Like yareally said, you should move on to step 4 if you are in fastboot. The only time you will need to access adb shell is when it says on the instructions.
ok, i'm sorry if i wasn't clear.
I saw the $ prompt, so I assumed the commands were run in a adb shell.
If i run the fastboot commands in a cmd window, this is the output:
C:\android-sdk-windows\tools>fastboot -i 0x1949 -w
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash 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
dingo8baby said:
ok, i'm sorry if i wasn't clear.
I saw the $ prompt, so I assumed the commands were run in a adb shell.
If i run the fastboot commands in a cmd window, this is the output:
C:\android-sdk-windows\tools>fastboot -i 0x1949 -w
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash 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
Click to expand...
Click to collapse
I'm a bit confused as to what you are doing. What were you using before to enter commands? Whatever you were using that got you to step 3, was what you need to use. There should always be $ infront of your commands.
Oh I just saw the problem, the fastboot your using is out of date. Theres no -i command. I think the one that I linked was out of date too.. I'll upload the one I have which is the most current and link it on the main post. Sorry about that! So just start over after you update fastboot using whatever you were using before to enter commands that got you into fastboot.
I finally received my device yesterday and I've attempted to unlock the bootloader multiple times.
*Developer options are on, OEM unlock and USB debug are on, all drivers are up to date. I even disabled my password in case this was affecting it
Manual Unlock via CP: My device is recognized and all commands are accepted. After I enter "fastboot flash unlock" my device never asks me to confirm, I get a listing of options on in CP but nothing happens on the device.
Wug's Nexus Root Toolkit: Recognizes the device and brings device through all steps but I'm never prompted to confirm anythings after the "fastboot flash unlock" command is entered, seconds later it reboots.
The command is "fastboot oem unlock"
Gizmoe said:
The command is "fastboot oem unlock"
Click to expand...
Click to collapse
Thank you, I just tried again using "fastboot oem unlock" and I still get no prompt to confirm. Should I be using another command after the oem unlock to verify my device wipe?
This is what i get in CP:
Command Prompt for manual input...
------------------------------------------------------------------
Try typing "adb help" or "fastboot help" for a full cmd list and syntax info.
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot dev
ices
5VT7N15xxxxxxxxx fastboot
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot fas
tbook oem unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>
Gizmoe said:
The command is "fastboot oem unlock"
Click to expand...
Click to collapse
No its not
I did read in these forums the new command prompt for the Nexus 6p is fastboot flash unlock. Has anyone experienced anything similar? Enter the correct commands but you are not prompted to accept or decline the device wipe?
akellar said:
No its not
Click to expand...
Click to collapse
Unless you have something useful to say, simply disagreeing doesn't help anyone.
If thats not the command then what is the command? That has always been the command. If it has changed on the new nexus then old guys like me are open to being corrected with the updated info.
Gizmoe said:
Unless you have something useful to say, simply disagreeing doesn't help anyone.
If thats not the command then what is the command? That has always been the command. If it has changed on the new nexus then old guys like me are open to being corrected with the updated info.
Click to expand...
Click to collapse
You could read the stickied thread that breaks it all down.
http://forum.xda-developers.com/showthread.php?t=3206928
luyshuz said:
I did read in these forums the new command prompt for the Nexus 6p is fastboot flash unlock. Has anyone experienced anything similar? Enter the correct commands but you are not prompted to accept or decline the device wipe?
Click to expand...
Click to collapse
Sry I don't have mine yet. Have to wait til Xmas to play with mine. I have always used the fastboot oem unlock before so I am new to the whole fastboot flash unlock. I assume it should be working the same way as before though.
The new command is
fastboot flashing unlock
Click to expand...
Click to collapse
akellar said:
You could read the stickied thread that breaks it all down.
http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
Now that's useful. Thanks.