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.
Related
Hello, when I tried to update my Magic to a new radio something went wrong. Start-up screen freezes. Only fastboot and recovery are available.
Now, when I trie to restore my nandroid backup in recovery I get the message:
E: Can't mount /dev/block/mmcblk0
p1 (or /dev/block/mmcblk0)
(No such file or directory)
E: Can't mount SDCARD:/nandroid/
And it's not the SDcard that's malfunctioning...
When I trie it with fastboot I get:
C:\AndroidSDK\tools>fastboot flash system system.img
sending 'system' (80002 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash userdata data.img
sending 'userdata' (132301 KB)... OKAY
writing 'userdata'... INFOsignature checking...
FAILED (remote: signature verify fail)
I've searched everywhere for a solution for this problem, and tried everything but nothing helped. So I hope someone can help me here...
These are the specifications of my phone:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.33.2010 (SAP10000)
RADIO-6.35.10.18
The original radio was 3.22.20.17
I had recovery-RA-sapphire-v1.6.2H, but after my failed radio update, it rebootet after 2 seconds...so now I use recovery-RA-hero-v1.6.2 to enter my recovery. This one works, doesn't reboot, but I don't have acces to my SDcard.
Thanks for you're help!
How long are you waiting after booting to Recovery before trying the restore? I think there's an issue with the amount of time it takes to mount the SDCard. Try waiting for a bit. It does work for me, but not if I immediately try to backup/restore after entering Recovery. I usually wait a couple of minutes.
well...I've waited 10 minutes...but still the same response...
If I see your specifications, I see that your phone is OFF and mine ON, in another tread someone said that the "ON"-sign was the reason for not having acces to the Sdcard... :s But I'm not sure this is true...
Even...everything I trie to flash with fastboot (so I don't need acces to my SDcard I guess...) doesn't work...due to that signature verify failure... Maybe there is a solution for that problem...?
Hey it seems you really have a problem.
The hboot version is not right for your radio version. You obviously did not follow the very clear howto by cursordroid, easily found in the android development section. I'm not sure how to solve this, but you must first look for some way to upgrade the SPL to the version that works correct with new radio.
Hi...yes... I updated the radio on a wrong way...
I already thought that this new radio and 'old' SPL were the reason why this doesn't function anymore...
I already tried to update the SPL on different ways... With recovery I don't have acces to my SD card and with fastboot I get the same response as above... I don't think there is another way... :s
I really screwed up this time...I hope someone can help me out... This is the first time this happens to me but it will be the last
Woww you're so lucky you didn't brick. Love it when people fail to follow simple instructions! And how would a nandroid restore help? Since when does that restore radio/spl. Also how did you manage to get the hero recovery on there? Did you flash the recovery then radio?
Since you're using the hero recovery, it takes some time to mount the sd card. SO wait a bit when you try this
Try this,
1) fastboot oem enableqxdm 0
2) If that doesn't work, you're sort of screwed. I'm not sure if it will work since youre s-on
3) If it works, flash the old radio in recovery.
4) I'd try goldcard if none of the above works
Hi...thanks for the help!
Well, I read somewhere that I could use that hero recovery... So I use fastboot to boot the recovery on my Magic, that's the only way to enter the recovery.
I first flashed recovery sapphire 1.6.2H, made a back-up and then I flashed the radio...
I tried what you asked and I got this:
C:\AndroidSDK\tools>fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
So...I guess I'm screwed...?
Re: Huge problem to restore nandroid backup - "can't mount SDCARD:/nandroid/"
If your phone really fails to mount the sdcard in recovery, even after waiting a while, you might still be able to flash a correct engineering spl if your recovery allows you to connect by adb. The idea would be to push the img to /cache and flash it from there, using the adb command line. I have never tried that though so no guarantees.
Sent from my HTC Magic using the XDA mobile application powered by Tapatalk
Hi, yes, I waited 30minutes...still no result... should I wait longer?
I found the correct engineering spl and I can connect by adb...
Could you tell me which commands I have to type in cmd to push the engineering spl (.zip) with adb?
Thanks!
PM me if you haven't solved the problem yet.
I haven't solved the problem yet.. Could you tell me which commands I have to type for adb in command prompt? This is the name of the .zip file "update.Engineering-SPL-HBOOT-1.33.2009-signed"
Thanks for the help man... But I didn't succeed yet...I didn't get an error message but something went wrong... This is until where I got:
C:\AndroidSDK\tools>adb shell
/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98492 0 98492 0% /dev
/dev/block/mtdblock4 81920 1192 80728 1% /cache
/ # exit
exit
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
I didn't know for sure what you ment with '(the hboot file must be present in the current folder of course)' so pasted the SPL "hboot-1.76.2007" on my SDcard and in AndroidSDK/tools
Then I did this:
C:\AndroidSDK\tools>adb shell
/ # flash_image hboot /cache/hboot-1.76.2007.img
flash_image hboot /cache/hboot-1.76.2007.img
can't find hboot partition
It could be that you did forget a 'space' between boot and cache so I tried this:
/ # flash_image hboot /cache /hboot-1.76.2007.img
flash_image hboot /cache /hboot-1.76.2007.img
usage: flash_image partition file.img
/ # reboot bootloader
reboot bootloader
When I rebooted in bootloader everything was still the same... Did I do something wrong?
Already thanks for the great help!
janximan said:
Thanks for the help man... But I didn't succeed yet...I didn't get an error message but something went wrong... This is until where I got:
C:\AndroidSDK\tools>adb shell
/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98492 0 98492 0% /dev
/dev/block/mtdblock4 81920 1192 80728 1% /cache
/ # exit
exit
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img
Click to expand...
Click to collapse
this should be
Code:
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img /cache
when the hboot file is in your tools folder. You got a usage message from the command, that means the command was malformed. So the rest couldn't work either. And no I did not miss any space in the flash_image command.
Damn, sorry to disappoint but I did some more research and I think my idea won't work after all
the Sign is on, and you have to turn it off. Use the goldcard method and use:
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
to turn it off, and start the flasshing process again for safe keeping.
Instructions:
http://translate.google.pt/translat...ss.C3.A1rio_para_fazer_o_processo&sl=pt&tl=en
If you want try flash using HTC Magic oficial update and start the process all over again for safe keeping.
Hope it helps
i was reading things better. Have you tried to download a oficially signed from HTC Hboot and in fastboot flashing it ? If you sucessed you could reverse the process
PS: does anyone know to explain me why did this exacly happened?
Jup...still no difference...
Thanks drbobb for all the effort and time! If there really is no other way to make it work than the goldcard method... I should try this one...but read it first a few times...
Jgcaap... Thanks for the help.. I explained on the first page how I get this far... Updated my radio on a wrong way :s
how did you update the radio ? Sorry to ask again but in the first page isnt expressed if you done by flashing procedure (USB) or by other method (Recovery).
Well...i don't know for sure but I think I just flashed a new radio (.zip) file in recovery... Without using fastboot...
Well according to the studies the most safe is in fastboot, in recovery you can also flash but there is always a risk since the recovery might not be 100% safe to flash. But you still havent done anything else? Please try remember because there must be a way of exploiting to make the phone work again.
Received my KF about a week ago. Just tried to root it yesterday. That was successful. The instructions I was using said this: "This will “root” your Kindle Fire. You can actually stop here but I recommend you to go to the next steps to install TWRP Recovery, which will allow you to install/backup/restore ROMs and also “unroot” your Kindle Fire when needed easily." So, silly me, without doing further research, went on to the next steps. I almost immediately got stuck, here is the code, ending with the -bash where I was stuck.
Zach:~ Zbhest$
Zach:~ Zbhest$ cd Downloads/KindleFireRootMacLinux
Zach:KindleFireRootMacLinux Zbhest$ mkdir ~/.android
mkdir: /Users/Zbhest/.android: File exists
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/.
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac kill-server
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac devices* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
08EC002600000001 device
Zach:KindleFireRootMacLinux Zbhest$ sh runmemac.sh
---------------------------------------------------------------
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified for Kindle Fire for Linux/Mac by Max Lee at RootKindleFire.com
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) enable USB DEBUGGING
from (Menu\Settings\Applications\Development)
(2) enable UNKNOWN SOURCES
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) connect USB cable to PHONE and then connect 2 computer
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1836 KB/s (23056 bytes in 0.012s)
--- correcting permissions
--- executing 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 ! 0xafd195bb 0xafd39357
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle USB DEBUGGING (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4634 KB/s (1075144 bytes in 0.226s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.038 secs (28293263 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
1508 KB/s (22228 bytes in 0.014s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
5116 KB/s (785801 bytes in 0.149s)
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
5382 KB/s (3104805 bytes in 0.563s)
Error: Could not access the Package Manager. Is the system running?
All Done, Kindle Fire ROOTED!!!
Check out RootKindleFire.com for more cool hacks!
Zach:KindleFireRootMacLinux Zbhest$
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
restarting adbd as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
260 KB/s (22228 bytes in 0.083s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod -6755 /system/sbin/su
Bad mode
Zach:KindleFireRootMacLinux Zbhest$ .adb./adb-mac shell chown 0.0 /system/xbin/su
-bash: .adb./adb-mac: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ cd Desktop/kindleFireRootNew
-bash: cd: Desktop/kindleFireRootNew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ cd desktop/kindlefirerootnew
-bash: cd: desktop/kindlefirerootnew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
877 KB/s (22228 bytes in 0.024s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
adbd is already running as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xboin/su
264 KB/s (22228 bytes in 0.081s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell cown 0.0 /system/xbin/su
cown: not found
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod 06755 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac install Superuser.apk
3818 KB/s (785801 bytes in 0.200s)
pkg: /data/local/tmp/Superuser.apk
Success
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell
# su
# idme bootmode 4002
<idme> write 4002 to offset 0x1000
# reboot
Zach:KindleFireRootMacLinux Zbhest$ ./fastboot-mac -i 0x1949 boot twrp-blaze-2.0.0RC0.img
-bash: ./fastboot-mac: No such file or directory
And now my Mac does not recognize my KF. When I unplug my KF it appears bricked (will not turn on), but when it is plugged into a wall outlet I can do the hard reset, it charges, but does not go past the KF boot screen.
Also, ADB does not recognize any devices.
Additionally, I have a windows 7 machine. I was going to attempt to pick up where I left off, but as my KF is listed as an "unknown device," I cannot update drivers (or do not know how to do so manually). I also installed this little number: http://forum.xda-developers.com/showthread.php?t=1430038
And I currently have linux loaded on my W7 machine. When I try to use the "normal_boot" command, which is advised, I get:
"Resetting bootmode to standard boot...
< waiting for device >
"
So, yeah. That is where I am at. I WOULD go on to the other directions in firekit, but would prefer not to completely void the warranty using the "usb boot mode trick".
If windows 7 is the key here, I may need a walk through for driver installation and such. Otherwise, I am not totally disinclined to call customer service and ask for a replacement. Apparently they have been good about replacing rooted kindles?
Same issue right now... already tried reinstalling windows/firekit liveusb but nothing works=\ Is there any news on this problem?
http://support.microsoft.com/kb/315539/en-us
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
I did read all those threads about such problem before. Just no matter what i do those drivers won't install. I only get unknown device on 7/xp and cannot change it coz when i manually select those drives windows says that there no device info in it=\ Thanks for help anyways
did you select adb_usb.ini ? it's just the folder with this file in it. selecting just the folder is usually enough. if you want to select the file: the driver file is android_winusb.inf. there is the harware info
if you have xp available then use this machine - it's easier
Yeah i did select that inf file (it was only one selectable in folder anyway) but it still says same stuff. I have xp right now if that gonna change something
yes xp is easier to handle because:
only 32bit -> only 1 driver version
no user access control -> don't need to do every thing as administrator
please check the following:
you have a .android folder under your user directory - in this folder is adb_usb.ini - the file has entries for device 0x1949 and 0x18D1 - if not run install.bat from the driver set i provided
check your device manager and delete every entry with kindle or adb
unplug and replug your kf - select the driver i provided manually
Got those 0x1949 and 0x18D1 in adb_usb file. And i only have unknown device every time i plug kindle in, no adb kindle at all
right click unknown device - update driver - select android_winusb.inf
if this don't work we have to cleanup old drivers -> could help per teamviewer if you like
When i try to update driver and manually use inf you provided it says that there no device info there=\ And i got unknown device since fresh windows install so idk what driver can cause it -.- I could ve try teamviewer but my windows is not english so it gonna be quite useless.
what language ?
Well it's in russian +there no laptop drivers yet coz im using xp only for this god dam kindle
ok your right - with russian i have a problem
will try to describe you the steps:
disconnect and power off (pwr ~30sec) your KF
open a command prompt
type "set devmgr_show_nonpresent_devices=1"
type "start devmgmt.msc"
Click Show hidden devices on the View menu in Device Manager
uninstall every entry with kindle, android phone or adb device
power down computer and power on again (no restart)
tell me if your done - we will resume ...
ok i did everything step by step tho there was none of adb/android phone/kindle so i just deleted my unknown device.
ok - lets resume:
you may want to delete your old driver set previously downloaded - it must be faulty
now download the one from this post and extract it to c:\
now plugin your kf (don't power it on - will do it by itself)
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
if this don't work eighter then i would think you have a faulty cable !
try an other one ...
Nope still same=\ Guess i will look for new cable tomorrow then tho this one was just fine today at transfering stuff (dam you nokia!). Well thanks for trying to help anyway.
you have the nokia cable - i have the same one
tell me the status your kf now
stuck at boot screen ?
some other tricks:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
if you'r stuck in wrong bootmode:
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
if you issue the fastboot commands and get <waiting for device> over some while power the kf off (pwr ~30sec) and on. at some point it should recognize the command
Yeah it same as before=\ I have same problem as topic starter aka device in fastboot and windows won't recognize it and install correct drivers. Fastboot commands won't work coz i don't have correct drivers and all they do is stuck on waiting for device/
xx time later = IT WORKS!!! for some weird reason it picked kindle up nothing changed in windows yet it works! Thanks again for your help time to flash recovery again.
courious - just tested on mine
when i switch to fastboot it is recognised as "android adb interface"
not the composite thing !
and i have the same drivers on xp
perhaps you want to try this one:
http://forum.xda-developers.com/showthread.php?t=1428428
sorry - no more ideas ...
UPDATE: hurraaa !!! - wish you all the best and good luck !!!
Hi All,
As some may know, current Official SDE for gen8 doesn't work on the new Froyo Gen8 v2 devices (currently: A70b / A70it2).
As we do on Gen9, there is a way to enable SDE menu in recovery for the new Archos A70S/A70it2. It's quite easy and safe, it has been used multiple times on gen9 and only use Archos commands (except of course temp root that is done by using psneuter).
Disclaimer: I'm not responsible if you blow your device with this, I'm only using existing Archos commands but this is not an official Archos release. Use at your own risks.
If you don't know about SDE, check my Gen9 thread here, it has some pictures that could help (70it2 menus are not exactly the same but are similar).
So, to enable it:
1) You must have adb working, I won't detail how to install or use it here. "adb shell" should give you a '$' prompt, if it doesn't, check your adb installation first.
2) Unzip content of the attached file to a directory (or platform-tools if adb is not in your PATH)
3) Launch enable_sde.bat script (or enable_sde.sh for linux, don't forget to chmod 755 it)
4) It should display something like this:
Code:
5800 KB/s (557962 bytes in 0.093s)
4625 KB/s (2564188 bytes in 0.541s)
5000 KB/s (728825 bytes in 0.142s)
property service neutered.
killing adbd. (should restart in a second or two)
Generating KD...
Updating KD (3293269 bytes)...
0
100
4) If it worked properly (check file sizes, some had troubles with adb push), reboot in recovery with power+vol+, you should now see the SDE boot menu. If you go to recovery, you should see the and if you go to recovery, you should see the "Developer Edition Menu". If it doesn't work for you, please report in this thread.
Next step is to install a rooted build, you can find one here.
Cheers,
LeTama
Flawless victory...excellent.
Hello!
i get the following error:
Code:
D:\test>enable_sde.bat
D:\test>adb push psneuter /tmp
failed to copy 'psneuter' to '/tmp/psneuter': Permission denied
D:\test>adb push init_zImage /tmp
failed to copy 'init_zImage' to '/tmp/init_zImage': Permission denied
D:\test>adb push init-cpio.gz /tmp
failed to copy 'init-cpio.gz' to '/tmp/init-cpio.gz': Permission denied
D:\test>adb shell chmod 755 /tmp/psneuter
chmod: /tmp/psneuter: No such file or directory
D:\test>adb shell /tmp/psneuter
/bin/sh: /tmp/psneuter: not found
D:\test>ping 127.0.0.1 -n 5 -w 1000 1>nul
D:\test>adb shell /usr/bin/kd_flasher -i /tmp/init-cpio.gz -k /tmp/init_zImage
Generating KD...
cannot open kernel file: No such file or directory
mkflashimage failed
D:\test>adb shell sync
D:\test>
it is an archos A70it2.
Honeycomb or Froyo model ?
This one is for Froyo, I changed title to reflect it, sorry. Check my sig for the Honeycomb one...
Ok, it is the honeycomb model I will try the other one - thx!
Okay...so here Iam once more driving myself insane. I'am pretty intermediate with devices and rooting and can usually do things solo or with slight help...but!!. So just received the device from a friend of mine and I actually want to unlock it to allow Simple Mobile (sim card) and services...when i Hboot it says Radio ON...to what i presume will be the freedom I need. Okay so here goes my trouble... I know that your supposed to downgrade the device to root, or temp root, I have been following the instructions to the T (or at least I'm hoping so) on http://forum.gsmhosting.com/vbb/f62...ouch-4g-2-3-4-hb-0-89-0005-stock-rom-1344617/ and even on this site which is where i also have tried following the directions. Okay so what confuses me is that one post says tools, the other says platform-tools..and if i'm incorrect the directory has both. Okay so I've opened up a command line from both and it's around
$ adb push fre3vo /sdcard/fre3vo
$ adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
that I start to have my trouble!! I was actually able to copy this...
C:\AndroidSdk\platform-tools> adb push fre3vo /sdcard/fre3vo
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <---is this the error file im supposed to get?? so I rewrite it connecting the sdcard to fre3vo and then wallah!! A whole bunch of writing like ...
C:\AndroidSdk\platform-tools> adb push fre3vo/sdcard/fre3vo
Android Debug Bridge version 1.0.31 <------------------------Right over here (excessive content so i deleted)
C:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found <---------------------------So I go down through the line of codes I'm supposed to trty and all say not found
$
Now as you can see this is where my problems arise. Every code or set of codes I get result in not found?? What am I doing wrong? I saw a tutorial on youtube and when he added this coding it was immediately followed by a massive amount of writing and then ADB seems to have shut down...Am i supposed to have ADB running while I do this? I've even tried rewriting the codes thinking that maybe a space was misplaced or such. Please help guys. Also what I did was manually created a directory at C;\Adroidsdk since there was none and placed all of the adb tools there or hope I did. Before that every time I'd open the executable the adb program would open from C\users\appdata\local\temp. I honestly don't know where i went wrong. I really want to root this phone. I went as far as spending 30 dollars on one of those bogus websites that can "root your device guaranteed" only to find that the programs they had like Superoneclick I already had on my desktop. Go figure..Ok I will sit here miserably until one of you rescues me. Thanks.
Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know
Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.
If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless
N_otori0us_ said:
Some people said they used this tool to root.
http://forum.xda-developers.com/showthread.php?t=1870652
I personally have not tried it, but hey, you never know
Click to expand...
Click to collapse
yeAh this is one of the tools the $30 dollar spot gave me. Funny because it actually says it worked..Su installed Busybox installed and once process is done..Nada..zip..is still the same now to convince them of a refund.
Relsig said:
Did you unzip the files before putting them in platform tools?
Also shouldn't you be pushing the file to the folder you are trying to chmod? It looks like you are pushing it to sdcard and I'm pretty sure it needs to be in the tmp folder:
adb push fre3vo /data/local/tmp
Instead of sdcard, but don't quote me on that I haven't done this in ages. Trying it *shouldn't* break anything... I think
If you can't push it to tmp then you are missing steps.
Edit:
Found an xda thread that verifies the file should be pushed to data local tmp
http://forum.xda-developers.com/showthread.php?t=1178912
Shame on the person who wrote the other guide.
Click to expand...
Click to collapse
Yeah, I've actually tried it this way and the other. the thing is one site says tools..the other platform tools, and then this last one sd card?? I've tried them all I think...Maybe my adb is installed in the wrong area? could that be why possibly after i chmod and start putting in the files to finally root the phone it says "file not found"? I know it's alot of writing but I'm going to copy and paste everything on a new reply to see if you or anyone can see what I'm doing wrong. I even copy and paste to the cmd and nothing.
ughoji said:
If u already got s-off (cuz u might have to downgrade) or still in fryo u can try vissionary+ method efficient stressless
Click to expand...
Click to collapse
If you could find me a place to download visionary from I'd be eternally grateful to you. It seems when they banned the app from google they must've done so everywhere else. Everytime I try to download my PC stops the download and says virus detected even with anti-virus off. Every time I go to the Visionary website and click the download link it takes me to some bogus website and never to the download link. The other sites I've found them on them on the PC says Virus detected...or maybe it's google chrome. Think I should try downloading on Internet Explorer?
what i'm gonna do guys is try the process from the xda website and then post it to see if one of you detect where I went wrong. Crossing Fingers...
now here it is ladies and gents...maybe we can find the problem here somewhere
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jorge>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Users\Jorge>cd c:\androidsdk\platform-tools
c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory <-- here also i get the no file or directory error so then i rewrite putting fre3vo and data together which follows with fre3vo/data
c:\AndroidSdk\platform-tools>adb push fre3vo/data/local/tmp
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
c:\AndroidSdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory <--when i input chmod 777 /data/local/tmp/fre3vo it says no such file...so i
$ chmod 777/data/local/tmp/fre3vo rewrite it and connect the 777 to data like chmod 777/data and then
chmod 777/data/local/tmp/fre3vo the usahe chmod ...etc.
Usage: chmod <MODE> <FILE>
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found
$ <-----I can continue and write the other passwords but it says not found.
I'm wondering if i might've installed adb in the wrong place and if so how do i change the variables? should i put C:android or as currently ANDROID_SDK_HOME then C:\AndroidSdk
There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app
N_otori0us_ said:
There's no wrong place to install adb. If your in GingerBread, I don't think visionary will work. Try ginger break. But you have to downgrade to root your phone. If your on 2.3.4, you gotta get on 2.2.1 I think
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
yeA
YEAH PHONE IS ON 2.3.4...ooops sorry for caps! so can you see where i might've went wrong? I mean is it supposed to say file not found or those things? somewhere i messed up..sigh...
c:\AndroidSdk\platform-tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
cannot stat 'fre3vo': No such file or directory
Is fre3vo in C:\AndroidSdk\platform-tools?
cause thats where you need to unzip the files to
-Nipqer
Found the problem...
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)
Playdoe said:
Thanks to you guys I went back step by step and figured out the problem . So apparently when i had originally downloaded the fre3vo and misc files they were the wrong files. I looked inside of platform tools and both files were there as applications?? yeah like actual install type applications..finally it has all seemed to work so i'll now move on to step two...won't say im done till ive succesfully rooted and ill keep you posted but thank you guys.,.for your time and dedication towards helping me :_)
Click to expand...
Click to collapse
Just in case u wanted to root an s-off phone search pd15img(2.2.1).zip got mine from 4shared rename it to pd15img.zip and move it to root of your SD card boot into bootloader navigate to the second option then OK with power on to downgrade. here is a working visionary but note most cases play store doesn't agree to download make sure u got explore or es in another phone to send it run your rooting and every.the visionary process is in the dev part its pinned
I used visionary and it worked for me
So I've tried rooting my Lenovo Thinkpad Tablet (Android 4.0.3) from Windows, and from Linux. I got what looked like close when I went through the windows Debugfs exploit, and after a while and a few reboots it announced that the machine was rooted. However, "Root checker" said otherwise - even after another reboot.
I tried Linux, but the command
Code:
adb shell /data/local/debugfs -w /dev/block/mmcblk0p3 < /data/local/debugfsinput
produces "-bash: /data/local/debugfsinput: No such file or directory" even though I entered "adb push debugfsinput /data/local/" previously. I've tried doing this as a user and as root, and get the same error.
I'm a bit stuck here: I think I've tried most alternatives, but my machine remains obstinately unrooted.
Any help, or pointers to useful web sites, would be very gratefully received!
Thanks!
Your problem appears to be with your syntax in entering the command. When you run
Code:
adb shell /data/local/debugfs -w /dev/block/mmcblk0p3 < /data/local/debugfsinput
your system only interprets the "/data/local/debugfs -w /dev/block/mmcblk0p3" portion as the parameter to adb shell. Bash is trying to parse everything after the redirect (<) as a local file rather than a file on the tablet. Try putting quotes around the whole thing:
Code:
adb shell "/data/local/debugfs -w /dev/block/mmcblk0p3 < /data/local/debugfsinput"
(That worked for me on Linux.)
I'm now getting "Permission denied while opening filesystem, followed by "Filesystem not open" for each subsequent command. But hopefully you'll have better luck!