Related
Ok folks, I believe I have read 30 or 40 threads on this site and 20 or so on other sites regarding pushing to sdcard and I think it's ok I now ask for help here.
I have rooted my Kindle Fire successfully
I installed android market successfully
When I saw the people saying turn off wifi to avoid getting the 6.2.1 update I did so.
Now I want to install cm7 on my kindle so I don't have to worry about updates anymore. Ok, now onto the problem.
Downloaded whistlestops update-wipeall.zip and put it into C:\Program Files <x86>\android\android-sdk\platform-tools
Made sure device was fully powered and plugged into Windows 7 computer
went to command prompt and changed directories to C:\Program Files <x86>\android\android-sdk\platform-tools
Ran cmd prompt
adb push update-wipeall.zip /sdcard/
and problem is I get failed to copy 'update-wipeall.zip' to '/sdcard//update-wipeall.zip': Permission
denied
I have checked to make sure I am rooted and still nothing. at this point after reading and banging my head against wall I could really use some help from community.
p.s. apologies for repost not sure how planets aligned for previous to end up in Lenovo forum
I was having the same issue. I ended up installing TWRP (which took me all night to do) and flashing CM7 with that.
I have twrp installed but need to get the cm7 file to the kindle to flash. Heck I even went into twrp and did a full backup just to make sure I could restore if I needed.
So how did you get cm7 onto sdcard to flash or am I just hopelessly lost?
To push update.zip you must unmount kindle from your computer (right click on kindle disk in "my computer" and unmount/unplug)
and again, open command prompt
adb kill-server
adb devices
...bla bla bla
Thanks Kisman that did the trick.
Now I have a new set of problems but original was solved.
I went into TWRP did mount usb storage
Copied image over to kindle remounted
Went to install. There is my wonderful file, clicked the file, flash, even did the wipe as suggested in inital instructions (Thanks Whistlestop) rebooted and well nothing, I got the yellow triangle, it goes away to be replaced by nothing.
Rebooted again into twrp and restored backup (thank you twrp team)
back to square one, calling it a night now, maybe fresh eyes in morning will turn up something.
Moose66 I used this tutorial to install CM7 - and I suggest you to do the same thing
http://www.kindlefirewire.com/2011/12/06/how-to-install-cyanogenmod-7-on-kindle-fire-tutorial-video/
I copied update.zip file from this topic:
http://forum.xda-developers.com/showthread.php?t=1390773
From this topic I copied: log, last_log, stockrecovery.img and updaterecovery.img:
http://forum.xda-developers.com/showthread.php?t=1368012
Be sure you copied log and last_log without .txt extention. My firefox added extention .txt automatically
sorry for my English, good luck
I followed the whistlestop (thanks again) instructions using the first choice for unmodded roms, update-wipeall.zip to the letter. It says everything was successful but on reboot I get the yellow triangle like I should and then a backlit screen and nothing else. I waited 5 minutes and tried rebooting 3 or 4 times before I used twrp to restore the previous version.
I am not sure what I am doing wrong at this point.
p.s. appreciate all the community help I have received thus far
Write here step by step what you did exactly
Prior to 6.2.1 I had my Kindle Fire rooted with super one click. It seems like the Kindle Fire utility is the method of choice today. I would like to know if there is anything special I need to do to remove superoneclick and/or drivers before installing KFU. I'm trying to be a bit cautious here since the frequency of bricking seems to have gone up.
I was lucky that the 6.2.1 upgrade did not mess up my android market or google install – I had already upgraded to the latest version prior to the install. I would like to regain root, but I'm willing to go slow since my KF is currently rock solid and I don't really have any pressing need.
Thanks
Bruce
I didnt have any issues switching from one-click to KFU. it ran fine with the drivers i installed to use one-click. I did have one issue after installing the 6.2.1 udate and FFFm I had to reinstall the KF drivers after I updated (my windows box no longer recognized it and it got stuck in the wrong boot mode which was easy to fix from command line once it was recognized again).
Kekule
As far as I know SuperOneClick never installed anything on your Fire. It sounds like you are using a stock un-rooted 6.2.1 so you'd just proceed as any normal 6.2.1 user would. I, myself, rooted back in 6.2 with SuperOneClick and have been ever since because I installed TWRP and used the pre-rooted 6.2.1 image. I'm kind of curious if there's anything I need to know as well, though. I'd rather err on the side of caution as well.
Buffet_of_Lies said:
As far as I know SuperOneClick never installed anything on your Fire.
Click to expand...
Click to collapse
nothing more that SU, but you do have to get ADB running which requires having the android SDK usb driver to connect to the fire instead of whatever gets installed by default.
Great.. just thought I would check before I just plowed ahead as if it was a brand new 6.2.1 KF. I'm not sure when I'll get to it, but it's nice to know that I don't need to do anything unusual. I may just wait a bit to give KFU some time to mature.
btrvalik said:
I may just wait a bit to give KFU some time to mature.
Click to expand...
Click to collapse
I don't think KFU is going to change much now. Its been at 0.9.1 for some time how. I see the links to the original article are backup so the links should be good too.
Kekule said:
I didnt have any issues switching from one-click to KFU. it ran fine with the drivers i installed to use one-click.
Click to expand...
Click to collapse
Same here.
I have rooted several android phones and my fire when fired released. Lost root a few updates ago and finally want to root so I can place ICS on it. I am on 6.3 and have tried KFU 9.4 & 9.5 of 2 different computers and it when it runs run.bat it crashes.
Attempted doing CMD way but never tried that way before and prob doing something wrong.
Please help. I also restored fire to factory condition's in case previous old roots left files that are screwing it up...
Going bonkers....Rooted my Bionic this morning in 3 mins...been working no Fire for 3 hours....
If you don't currently have TWRP 2.0 installed on your kindle fire. Go to this link and follow the steps it will tell you how to root 6.3 http://forum.xda-developers.com/showthread.php?t=1568340
GramsHD said:
If you don't currently have TWRP 2.0 installed on your kindle fire. Go to this link and follow the steps it will tell you how to root 6.3 http://forum.xda-developers.com/showthread.php?t=1568340
Click to expand...
Click to collapse
This guide requires you to have adb and fastboot working FOR THE KINDLE FIRE,
How do you do that?
I am stuck at waiting for device when using KFU 9.5 , reinstalled drivers but nothing
Make a folder on yourC drive called KindleADB. Then copy the files from the tools folder in Kindle_Fire_Utility_v0.9.5. To the KindleADB folder you just made.
Also download the REQ files in the topic link I posted. Copy those files to the KindleADB folder as well cause you will need them.
If you got the driver installed like you say you do. You can just follow the steps and root the device.
I was having a similiar problem, what I had to do was plug in my kindle, and then uninstall the drivers. Then I would unplug and then plug back in and let the drivers reinstall. I also used kindle fire utility 0.9.4
ADB and Fastboot from the Kindle Fire Utility seems a little hit or miss. My desktop doesn't run any of the .bats so I was scared to try it there. My Mac in win 7 with bootcamp worked fine.
ADB and Fastboot were much easier to get working in OS X 10.7 and Linux.
When Kindle Fire Utility failed the first time I switch to OS X and did jcase's method to get root and install TWRP then i just flashed a custom rom.
Buzz4infinity said:
I have rooted several android phones and my fire when fired released. Lost root a few updates ago and finally want to root so I can place ICS on it. I am on 6.3 and have tried KFU 9.4 & 9.5 of 2 different computers and it when it runs run.bat it crashes.
Attempted doing CMD way but never tried that way before and prob doing something wrong.
Please help. I also restored fire to factory condition's in case previous old roots left files that are screwing it up...
Going bonkers....Rooted my Bionic this morning in 3 mins...been working no Fire for 3 hours....
Click to expand...
Click to collapse
We're on the same boat instead I been trying for two days I read every little. Trick I could find and it's stuck where it says please wait, bootloader if you get stuck do not unplugged blah blah? If you find a way please let me know it sound like we have the same issues. It's so frustrating because I root all the time I'm not a noob
Sent from my HTC Sensation Z710e using XDA Premium App
Well, it won't let me post in the relevant thread so I figured why not make my own. I got a brand new kindle (my old one malfunctioned, non-root related), and was attempting to root it. Mind you, my old kindle rooted fine. I went with the utility option, and it all seemed to work fine. However, upon noticing this:
Code:
1862 KB/s (327980 bytes in 0.172s)
pkg: /data/local/tmp/Calendar.apk
Success
failed to copy 'apps\system\vending.apk' to '/system/app/vending.apk': Permissio
n denied
failed to copy 'apps\system\GoogleCalendarSyncAdapter.apk' to '/system/app/Googl
eCalendarSyncAdapter.apk': Permission denied
failed to copy 'apps\system\GoogleContactsSyncAdapter.apk' to '/system/app/Googl
eContactsSyncAdapter.apk': Permission denied
I noticed that root was NOT in fact installed. Mind you, all through the Kindle Fire Utility (latest version). I thought to myself, alright, maybe the tool is bugged at the moment. I went ahead and did it the old fashion way....or not. Again, it would not root. So, while following instructions (all of which say to use a version of twrp which is not the current version) I just try again, to the letter. Never once do I encounter a "Yellow Triangle". Instead, now my kindle fire will show the "Kindle Fire" logo at boot, with a little android guy above it.
I did install super user, but without root, it's useless really.
I even factory reset, to try and start from scratch. This however did not remove what I assume is FireFireFire (The android icon over the Kindle Fire Logo) as the bootloader, so that's a problem in itself. What am I doing wrong? What can I do here? I'd love root like on my old kindle fire, I'd love to have Google Play/Market, and a real youtube app. However, none of the things on the forums are actually rooting my kindle. I've no idea where to go from here, and help would be greatly appreciated.
In short:
- Tried to root with Kindle Fire Utility (Latest Version)
- Success in running, but no root.
- Tried to root manually.
- Never got "Yellow Triangle", could boot twrp, no root.
- Tried to factory reset.
- Did not remove FireFireFire, still weird kindle fire boot up logo.
- Lost. Please halp.
I used the older version .0.9.3 I believe it was worked perfect just like it did the first time on 6.2.2
Wee update.
I searched around for the actual twrp they mention in the thread, found it, and got to the yellow triangle. Continuing my adventure of solving my own problems. Just loaded into the kindle fire, testing root. Will edit this post if success, and tell others what my problem was (for them, if they see the same problems).
Nope, still getting permission denied errors when installing the vending and what not. Still no root...At least I got the triangle though?
Thepooch said:
I used the older version .0.9.3 I believe it was worked perfect just like it did the first time on 6.2.2
Click to expand...
Click to collapse
Care to clarify of what you used the older version?
..Interesting.
Well, it seems I have finally got it rooted.
Using the kindle fire utility to install vending and whatnot does not currently work on my device (made respect to the creator, it's just not working...).
I decided to try and download/install it manually, and I now have root. I'll see if the forums will let me send him a message.
As I said, I'd mention how I "fixed" (more like just trying everything) it. It was simple. I went and found the actual TWRP the guide mentioned.
For reference: twrp-fire-2.1.0 will NOT work (at least for me) to root the kindle. You require twrp-blaze-2.0.0RC0
Thanks for those who looked, lets see if I can break it now
http://m.youtube.com/#/watch?desktop_uri=/watch?v=AZ88CYWv0FU&v=AZ88CYWv0FU&gl=US I used this method the first time I rooted mine on 6.2.2 in the video description there is further guide for 6.3 but I used kindle fire utility for my daughter's on both 6.2.2 and 6.3 and for mine as well on 6.3 but all the drivers were already in place but and it was v0.9.3 utility I really think that the better way is pushing the files via adb to your device but the utility is easier I'm using twrp 2.0 works perfect if your gonna flash wipe everything factory/data cache dalvik and system have backups done and all your files where you can find them rom and gapps read ops well for flash instructions go the extra bit with your wipes it doesn't hurt just don't reboot on accident until your done flashing because you will have no system on your device use root explorer to rename your backups without spaces or the won't restore you will find your backups under SD card/twrp/backups/ooooooo familiarize yourself good with locations in explorer so you know where to navigate to before doing anything even close to a flash initial boots take considerable time I would say anywhere from 5- 10 mins depending knowledge of what your doing is key read read ask questions
PatchesOfPlenox said:
Well, it won't let me post in the relevant thread so I figured why not make my own. I got a brand new kindle (my old one malfunctioned, non-root related), and was attempting to root it. Mind you, my old kindle rooted fine. I went with the utility option, and it all seemed to work fine. However, upon noticing this:
Code:
1862 KB/s (327980 bytes in 0.172s)
pkg: /data/local/tmp/Calendar.apk
Success
failed to copy 'apps\system\vending.apk' to '/system/app/vending.apk': Permissio
n denied
failed to copy 'apps\system\GoogleCalendarSyncAdapter.apk' to '/system/app/Googl
eCalendarSyncAdapter.apk': Permission denied
failed to copy 'apps\system\GoogleContactsSyncAdapter.apk' to '/system/app/Googl
eContactsSyncAdapter.apk': Permission denied
I noticed that root was NOT in fact installed. Mind you, all through the Kindle Fire Utility (latest version). I thought to myself, alright, maybe the tool is bugged at the moment. I went ahead and did it the old fashion way....or not. Again, it would not root. So, while following instructions (all of which say to use a version of twrp which is not the current version) I just try again, to the letter. Never once do I encounter a "Yellow Triangle". Instead, now my kindle fire will show the "Kindle Fire" logo at boot, with a little android guy above it.
I did install super user, but without root, it's useless really.
I even factory reset, to try and start from scratch. This however did not remove what I assume is FireFireFire (The android icon over the Kindle Fire Logo) as the bootloader, so that's a problem in itself. What am I doing wrong? What can I do here? I'd love root like on my old kindle fire, I'd love to have Google Play/Market, and a real youtube app. However, none of the things on the forums are actually rooting my kindle. I've no idea where to go from here, and help would be greatly appreciated.
In short:
- Tried to root with Kindle Fire Utility (Latest Version)
- Success in running, but no root.
- Tried to root manually.
- Never got "Yellow Triangle", could boot twrp, no root.
- Tried to factory reset.
- Did not remove FireFireFire, still weird kindle fire boot up logo.
- Lost. Please halp.
Click to expand...
Click to collapse
For your information or anyone else's, the yellow triangle is the old FIREFIREFIRE, the bootloader. The new version has a android guy over the kindle logo. So now that you have the yellow triangle back, you're using the old Firefirefire.
To easily update FireFireFire, or TWRP, I recommend smirkis' scripts that run right through your kindle, no computer necessary (you must have root).
http://forum.xda-developers.com/showthread.php?t=1500935
Thanks jacewt muchly appreciated
---------- Post added at 06:12 PM ---------- Previous post was at 05:56 PM ----------
PatchesOfPlenox said:
Well, it seems I have finally got it rooted.
Using the kindle fire utility to install vending and whatnot does not currently work on my device (made respect to the creator, it's just not working...).
I decided to try and download/install it manually, and I now have root. I'll see if the forums will let me send him a message.
As I said, I'd mention how I "fixed" (more like just trying everything) it. It was simple. I went and found the actual TWRP the guide mentioned.
For reference: twrp-fire-2.1.0 will NOT work (at least for me) to root the kindle. You require twrp-blaze-2.0.0RC0
Thanks for those who looked, lets see if I can break it now
Click to expand...
Click to collapse
By the way twrp does not root your device its simply a custom touch recovery for the kindle download root checker or try an app that requires root like root explorer it will ask for superuser permissions when opened just check remember and allow to grant permission
I was able to root the KF in short order with the utility -just follow the instructions to the letter, make sure ADB is functioning correctly. If you are having trouble with ADB, just make sure that it says composite, and not straight android USB. If, when you go to device manager, and the driver isn't the composite variant, unplug the kindle from the computer, delete the driver entry from device manager, and then plug the kindle back in. If you've edited the correct driver files, it should pick it up and ID it as a composite device and you'll be on your way to root in a few minutes from that point.
Also - I didn't use TWRP, instead opting for CWM. No particular reason why, I'm just familiar and comfortable with CWM and I know from experience that it "just works".
I had a windows 7 PC perfectly working in booting a Nexus 7 to flash and root etc, it did a Nexus 4 last week.
There is some problem with drivers and 4.2.2. specifically. My story was it was 4.1.2. rooted and it was refusing to OTA update but I wasn't bothered due to the bugs/performance in 4.1.1 so I waited til 4.2.2. came along. The N7 refused to take OTA 4.2.2. I got the Android icon with the Red icon out its belly and it would boot back as 4.1.2 every time.
So using Nexus Rootkit I did a "stock flash+unroot" to 4.2.1 and then let it did a OTA to 4.2.2 and that worked so I have a stock 4.2.2 but not it won't root, it would do that ADB bootloader type stuff. I've tried updating driving umpteen times but it like it simply won't obey ADB type commands? I'm not a rooting expert I just used the toolkit and howtos.
So stuck.
In hindsight as it WAS doing ADB at 4.2.1 I should have rooted and then otarootkeeper then OTA to 4.2.2. but I didn't know 4.2.2 rooting fails.
Any ideas?
same for me!!!
Help...
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
can root a stock 4.2.2 - it works!
I fixed it!
I'd been trying toolkit all of its options and none worked. So I followed this guide which contains an error which is irrelevant.
http://m.ibtimes.co.uk/root-nexus7-official-android422-jdq39-jellybean-ota-434720.html
Do its step 1. It downloads the Google USB drivers - THEY WORK. This is the problem with other guides they point to drivers which don't work.
Ignore its step 2 because you find step 1 includes fastboot so you don't need to get it separate. I lost a lot of time on that one problem because the link to that shared file fastboot.zip won't download so I hunted and found another and when I was going to copy to the required destination in step 2 I found the fastboot file alreadt there! So ignore step 2
Step 3. Now I downloaded it on the Nexus 7 itself and mine was in /sdcard/Downloads or you can copy on the PC and then copy it over to the N7 via USB cable.
Step 4. Press and hold power off you get option select power off.
Step 5. At the step 1 you'll see WHERE it is installing the SDK to, you need to go to that folder in this step 5 as described.
Step 6. As describe, press vol down and power button together and keep them hold. Then a menu screen shows mine had been unlocked from before. Now dont't touch the N7. Go to Windows machine.
Step 7. My Windows Pc doesn't have command prompt option inside a folder so I opened command prompt and CD down to where step 1 was.
Step 8. Type that command. Mine simply worked fperfectly first time. It had a copying type command which looked happy.
Step 9. Back on the N7 hit the vol up button til you see a "recovery" type word on screen.
Step 10 and 11 as described.
Step 12. Now is the next area where howto guide is wrong / misleading, I had on my screen some gibberish folders and an "update.zip" not the supersu zip from step 3. Initially I tried the update.zip and it went crazy but fortunately a hard power-off got me fixed so then next time I looked around for the supersu zip. So of the stuff on-scren where was like 0/ type folder so I selected that THEN I could see the sdcard/download folder I could go down to and then select the zip file. The /sdcard folder isn't showing firstly you have to go /0 and then you see it.
Step 13 do it.
Then get it booted and then go into Supersu app and run it and then make sure you install voodoo root keeper app and select it to preserve root.
So I've got a vanilla 4.2.2. with root and so far it all works. Features which kept me on 4.1.2 like PPP-widget simply work.
Phew.
I've spent about 15 hours on this trying to eliminate my own dumbness as the cause.
I think basically the ADB drivers in the Toolkits are bumb, ignore them they don't work I think the Android SDK with its Google USB drivers are the ones which work with 4.2.2 I guess the Toolkits need to be updated.
nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The problem seems to be drivers. The N7 stock 4.2.2 simply refuses to respond to Root Toolkit its drivers are simply not working, the N7 is ignoring to get into fastboot. I figured it out see my later post.
I think 4.2.2. is too new for toolkits and people's 4.2.2. rooting guides are buggy and relate to old old instructioned since outdated and in error. By trial+error I figured it.
nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Addtional my N7 did OTA receive the 4.1.2 to 4.2.2 update I even went into the /cache and the file name had version names to match so OTA was thinking itself capable. I think in some unlock / root past event I'd something screwed something up and OTA simply weren't working full stop. I did though manage to use Toolkit to get to stock 4.2.1 and then the drivers in the toolkit then don't work with 4.2.2, that's the broken bit. If you use Android SDK Google USB drivers, they work and you have to use command prompt fastboot as in the HOWTO I just posted to get it all working.
Toolkit drives broken with 4.2.2.
dont use a root toolkit. do it the right way, there arent any issue.
fastboot oem unlock, fastboot flash a recovery, flash the su binaries or a custom rom, reboot. thats it.
FYI - I've found that to use the toolkit (the 4.0.0 toolkit is what I used), you need to replace the adb-toolkit.exe (or whatever adb.exe is called in your toolkit) with the adb.exe that comes in the SDK (after you've updated your SDK, of course).
Otherwise, ADB shows as "offline" in the toolkit menu.
Hope that helps someone...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
The issue is what you typed is gibberish to most including me.
Sent from my Nexus 7 using xda app-developers app