Related
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
*--*--* I am not responsible for any damage that may occur to your phone by following this guide or any other guide. If you are at this step, your warranty is already void, and if you lie to Verizon to get a replacement, an angry bear will break into your house and molest you quite thoroughly. Those people are the reason why Verizon is forcing locked bootloaders, and why I had to wait two months to root my Inc2. Don't be one of those people. You might be a noob, but that doesn't excuse you from doing research. In short, anything that happens is your own damn fault, and you can't blame anyone else. /rant *--*--*
Now that that is out of the way, the steps:
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe and adbwinapi.dll, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Boot into fastboot by powering the device off, then powering back on while holding the volume down button on the side. It should boot to a white screen, similar to what you saw when you first rooted it. Plug your phone into usb if you haven't already.
6. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot".
7. Rooting the phone is only the beginning. You still need a rooted kernal, and su and busybox. Without these, rooting does you little practical good. To that end, follow RMK's guide here: http://forum.xda-developers.com/showthread.php?t=1160745. That will get you all set up to start enjoying root fully. I would recommend installing ROM Manager from the market and using it to flash the latest CWM (4.0.0.8). ****NOTE that you need to already have CWM to flash the su and then flasht he new CWM. I know, it seems silly, but that's the way things are. Also, a disclaimer: a few people have had problems with the newest CWM not working properly for them. It worked for me, though, and there is a fix on page four of this thread.
Credit goes to attn1 for the modified CWM, xgunther for posting it/original instructions, and crazythunder of Android Community for the original instructions for using fastboot with a G1. Hope this helps
Some information from supersonic that those trying this on linux will find useful. Thanks!
supersonic2.5 said:
Download this recovery: http://forum.xda-developers.com/showthread.php?t=1134520
BTW, if you havn't installed fastboot, download it here.
http://developer.htc.com/adp.html
1.First rename your android sdk folder to "sdk" just like that. Dont use quotation marks on anything fyi.
2.Next step is to move the sdk folder to your home folder.
3.Move adb, fastboot, and the recovery image from the link above into the tools folder of the sdk.
4.Open up terminal and type or copy this in there.
"cd sdk/tools" hit enter.
5. "./adb kill-server" hit enter.
6. "./adb start-server" hit enter. should look something this. (below)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7. "./fastboot" hit enter.
8. "./fastboot flash recovery cwm-recovery-vivow.img" hit enter
give it some time to flash.
9. "./fastboot reboot" hit enter
10."./fastboot adb reboot recovery" hit enter
And there you go, wait for your phone to reboot and what not and you should have CWM installed. I would immediately do a nandroid of the stock rom. after that i didnt bother messing with superuser on stock froyo because who the hell wants to be on froyo!? lol, so i installed the GB ota rooted version with superuser already because its very stable....found here http://forum.xda-developers.com/showthread.php?t=1161411 as i wait for a stable version of rewind,you can then install and update CWM through rom manager to the current version once you've done this.
there you go buddy sorry so long. if you encounter any problems let me know so i can boot into ubuntu and help out. i'd give you a little more details but im on my mac right now. hit the thanks button if i was any help
Click to expand...
Click to collapse
devator22 said:
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe, adbwinapi.dll, and ddms.bat, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot". And you should be done.
Credit goes to attn1 for the modified CWM, and xgunther for posting it/original instructions. Hope this helps
Click to expand...
Click to collapse
Just a heads up, if you are S-Off, you can enjoy these instructions on Mac, Linux, or Windows. ADB and fastboot give you options for all! <3
Here is another link i found to help out!
http://forum.xda-developers.com/showthread.php?t=1122694
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
b0gman said:
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
Click to expand...
Click to collapse
Dumbest solution ever... I was having the same problem. As long as you've installed the jdk file from the link it shows on the initial error on sdk install...
Just click 'back' then 'next' again on the SDK installer... It worked for me.
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Grouper said:
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
Click to expand...
Click to collapse
Guess I forgot to mention that this is for the people with problems with the automatic installer, including myself.
Sent from my Incredible 2 with Xda app
Clutch McWinner said:
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Click to expand...
Click to collapse
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
devator22 said:
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
I was, but it turns out I didn't have the HTC sync drivers. S-Off, Rooted, and running overclocked CM7 now!!!!!!!
This must be in Fastboot USB mode while doing?
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
SHAKEJONES said:
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
Click to expand...
Click to collapse
Should HTC Sync be opening? I think you're supposed to uninstall HTC Sync, but leave the drivers. AlphaRevX provided a link to the drivers only, so it might be easier to just completely uninstall everything and then reinstall the provided driver instead.
Just tried that and its still stuck... I'll mess with it more tomorrow
Yeah i've been having the exact same problems with the drivers. I have a completely fresh install of windows 7, and it still wont work. I installed the HTC Sync, and it still doesnt recognize my device. I tried using Ubuntu, however it makes absolutly zero sense in my mind, so unless i have a detailed instuctional text, windows is my only choice really. Its funny, this thread is for noobs, yet i can't get even do this, but other phones i've rooted without any problems, and they we're much harder for me. Blah.
I've tried all variations of connection modes, triple checked I had all the files in the right spot, and tried different usb ports and it still wont work... does someone have a more detailed guide for this?
Seriously frustrated about this. S-Off was no problem. I'm triple booted with OSX, Win XP Pro and Linux. Used linux to get s-off but didn't get a CWM install. Window won't allow the driver to install and Linux is a mystery. Anybody have luck with OSX or Linux and want to write it up?
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
devator22 said:
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
Click to expand...
Click to collapse
Thank you kind sir hahaha I JUST got done doing that and it worked like a charm! this thread will be a great help to anyone else ---> http://forum.xda-developers.com/showthread.php?t=1122694
The directions for fastboot are in the OP
Haha, yea. I guess I am a noob when it comes to writing guides. I updated the OP with an extra step for booting into fastboot.
Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.
AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!
soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA
AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
jma9454 said:
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
Click to expand...
Click to collapse
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
I have witnessed one demo unit that was completely unrootable even with the use of a factory cable. So at the end it was only good for parts and the motherboard unusable.
soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
That`s pretty much what I experienced with the demo unit that would not root, it simply would not enter fastboot no matter which approach I took. I can take a look for you but I feel it`s pretty much a moot point if it wont enter fastboot. Power the device off, open a terminal
Code:
fastboot -i 0x1949 getvar product
hit enter, when it says waiting for device, plug the kindle in. if it does not enter fastboot and return product: kindle you are dead in the water.
jma9454 said:
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
Click to expand...
Click to collapse
I've really gotta start reading the names on these posts
jma9454 said:
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
Click to expand...
Click to collapse
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
In my opinion, your best bet would be to forgo the VM, forget about the dilapidated WinXP computer and figure out a way to boot your Win7 computer into Ubuntu from a USB stick. You are dealing with way too many variables to effectively determine exactly where things are going wrong.
I 'fixed' two demo KF's, messed up a lot on the first (lucky I didn't brick it).... On the second, I used a fast boot cable and installed TWRP, had a JB ROM on it in 15 minutes.
Try this.... Send TWRP to it using the command line, when it says 'waiting on device', open another window and get it to reboot in fastboot mode. On the first KF I found the utility would only put it in fast boot for a few seconds, but it was long enough to write TWRP if you did it this way.
Not sure why some won't work at all, maybe Amazon got smart on the demo units.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7
soupmagnet said:
I've really got to start reading the names on these posts
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
Click to expand...
Click to collapse
The above statement took place from USB boot, not VMware. Also, like I said, I attempted to set it into fastboot and it just booted regularly. I tried several times with different cables and ports with no success.
Sent from my Amazon Kindle Fire using Tapatalk HD
I will stick with my original idea no fastboot = no fun. You cant push FBmode manually because installation from unknown sources is disabled by default on a large percentage if not all demo units. Regardless if the device doesn`t enter fastboot not much you can do. Taking advantage of the small window of fastboot at boot is risky if the write time isn`t long enough to get it sent and written but it could be your best bet. IMO I would not attempt this with the bootloader only recovery no harm no fowl.
Hello, I Have a Kindle Fire 1st Gen. I Had CM 10.1 on it. I was attempting to put AOSP back on it for My Wife. I did I Noobish Move at 4 am half asleep, I Did NOT go into advanced mode in TWRP and uncheck DATA in the Wipe tab. So This Screwed me "Bricked" Message comes up in TWRP when rebooting, says ( NO OS ) . I have Tried Kindle unbrick utility with no success when clicking on "Stuck at Logo" in utility I get this Error ...> PIC Attatched!>
I then Tried Using android-sdk ( I have went in and edited the files that need to be edited in program files/android...> File_android_winusb as well as in .android folder in the appdata location) Along with CMD & I get a Error So far into the process of Resetting Kindle OS. Pic Attatched as well. It Seems Like I have something missing ?!?!?
I somewhat Suck at CMD, I don't have much experience with it, so Please go slow on me,when Giving advise....
Thanks In Advance!!
If you still have access to TWRP, use it to mount your sdcard to USB.
soupmagnet said:
If you still have access to TWRP, use it to mount your sdcard to USB.
Click to expand...
Click to collapse
I Tried That. I See the Device But when double clicking, It will not let me access it.
Butt Nugget said:
I Tried That. I See the Device But when double clicking, It will not let me access it.
Click to expand...
Click to collapse
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
soupmagnet said:
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
Click to expand...
Click to collapse
My Kindle is a 1st Gen. I'm not sure If I understand what You are talking about when You say "send Commands/devices" If Your talking about in CMD I Get all the way to Seeing my Device Serial Number for Kindle. The when I type "adb shell" I get a error saying (Failed: No such file or directory <2> - ) You can see this in the screen shot I attached to this thread..
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
soupmagnet said:
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
Click to expand...
Click to collapse
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver. So Sounds possibly what I tried is totally different from what Your asking if i done? If So, Could You Explain step by step thee method with new roms or send me in the right directions 2 a how to link or video? Anything I would appreciate GREATLY! :fingers-crossed:
Butt Nugget said:
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver.
Click to expand...
Click to collapse
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
soupmagnet said:
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
Click to expand...
Click to collapse
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Butt Nugget said:
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Click to expand...
Click to collapse
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
I am attempting to understand what u are saying But I'm thinking ur not giving full step after step instructions OR this Version I have (v2.6.0.0) differs from Yours, Because there is No such OPTION as ADB PUSH..... I have ADB sideload (under Advanced Tab) which only wipes Cashe.. I've looked in every single area in TWRP and see nothing of anything You are talking about, other than "MOUNT" obviously.
soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
While Searching Google for Help I seen this..> http://forum.xda-developers.com/showthread.php?t=2361144
I'm bout to install a Pc with Linux and try pushing it that way.. Have not tried that.
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Stunt Thnx... You Helped breaking it down. I just used KFU and Fixed this within 3 minutes.. Thnx Man!:good:
My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James
getnby said:
My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James
Click to expand...
Click to collapse
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp
didn't work
stunts513 said:
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp
Click to expand...
Click to collapse
Here is what happened. It said the device was not found. In the device manager it shows adb device under kindle fire.
Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk
No luck
stunts513 said:
Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
My computer only recognizes the kindle as an adb device in fastboot mode. I haven't been able to use any of the adb commands on it with any luck. It says device not found. This only shows in kffaid version 4.1.87-beta.
*facepalm* you don't use adb commands with fastboot, you use fastboot commands with fastboot. When it is in twrp it should have adb access though...
Sent from my Amazon Kindle Fire HD using Tapatalk
I think I have a driver issue. I forgot to thank you for your help. If I could send the zip rom and gapps I could get it back to where it was. Is there anyway to start all over from the original kindle OS at this point?
Thanks you
You coukd restore it in fastboot using kffa but it seems like unnecessary work. I would boot a ubuntu 13.10 live cd/usb and just attempt it from there since there won't be any driver issues.
Sent from my LG-P769 using Tapatalk
I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks
getnby said:
I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks
Click to expand...
Click to collapse
these commands should do the trick assuming the repos are all active in the downloadable section of the software updates control panel.
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
and after that the fastboot command will work but keep in mind to give it superuser privis with sudo or it probably wont work, i had forgotten that recently on my own pc since i don't deal with fastboot too often. ex: sudo fastboot -i 0x1949 getvar product
I had to work all weekend. I tried to get access through ubuntu 13.10. I used the commands you provided (sudo apt-get update). This command worked fine. When I used this command (sudo apt-get install android-tools-fastboot) It said I had to enable universe. I did some research and got that working and tried to use this command again (sudo apt-get install android-tools-fastboot) then this one worked fine. Then I tried the last command with my kindle in fastboot mode flashing green light (sudo fastboot -i 0x1949 getvar product ). The message was cannot connect to otter-2 ... device. Same thing I have been getting all along.
I think when I wiped the system I cleared all the software to connect to any external device. I don't know if I can even get access to restore the original OS. If you haven't guessed by now I an a noob. I think you realized that with my adb commands with fastboot enabled. I got the impression you knew when I saw the *facepalm* comment the the beginning of you post. When my kindle is booted to twrp my computer does not recognize it. My computer will recognize as an adb device when in fastboot mode. My computer will recognize it as a kindle (with a yellow triangle in the device manager) when it is trying to boot with the white and blue logo. I don't know what to do at this point. Here is a screen shot with adb side load from twrp.
Interesting, seems that data didn't want to mount. Have you tried adb from Linux while in twrp? Just run "sudo apt-get install android-tools-adb" to install the command, if you can get adb access at least then I may be able to help fix this depending on what exactly is wrong. BTW I didn't exactly think you were a noon with that facepalm, I just see people get that misconception a lot about adb and fastboot commands. What exactly did that fastboot command report back, I was surprised it was an error when I saw otter2 in the error considering that was what that command was sort of supposed to report back.
Sent from my Amazon Kindle Fire HD using Tapatalk
Here is where I am. See below. Now where do I put the file in ubuntu so I can access it from the terminal window. I am running ubuntu from a live CD. I tried the push command but it says no such file or directory. I told you I was a noob!
[email protected]:~$ adb devices
List of devices attached
0123456789ABCDEF recovery
Since adb is in a system path must out it in the current directory you are CD'd into, if you left the terminal alone it should be in ~ (the home folder of the Ubuntu account) so photo the home folder and drop it in there and run "adb push filename /sdcard/"
Considering that /data doesn't want to mount and that /sdcard os technically in /data, that command might not work depending on what's going on. I reccomend seeing if you can first and if not goto the months and mount /cache if its not mounted already, and they pushing a twrp update into it to try to reflash twrp, its small enough I think it should fit into the cache, though I don't think a ROM would fit.
Sent from my Amazon Kindle Fire HD using Tapatalk
I installed ubuntu on my laptop with windows 7. It seems to work better. I put the files in the home folder and the user folder. I mounted the cache and ubuntu said instead of unable to mount it was unable to access kindle now. Here is the terminal window results.
[email protected]:~$ sudo apt-get install android-tools-adb
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
android-tools-adb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[email protected]:~$ adb push cm-10.2-20130908-UNOFFICAL-otter2.zip /sdcard/
cannot stat 'cm-10.2-20130908-UNOFFICAL-otter2.zip': No such file or directory
[email protected]:~$
Um OK well the filenames are case sensitive in Linux so lookout for that. Also if it was in your home folder then it should have worked as long as you didn't CD anywhere else in the terminal first.
Sent from my Amazon Kindle Fire HD using Tapatalk
Problem Fixed
I fixed my problem. I had to restart my kindle into recovery mode and connect the fastboot cable to the computer and kindle before it booted into TWRP. At that point while booted into TWRP I used the push command in ebuntu terminal to sideload cm11 and gapps. After I loaded them I installed them with TWRP and rebooted. Now it is restored to where it was when I wiped it. I will not do the advanced wipe again.
adb push cm-11-20140202-NIGHTLY-otter2.zip /sdcard/
adb push gapps-kk-20131119.zip /sdcard/
Thanks for your help stunts513
Click to expand...
Click to collapse