[Q] Where in the known universe is CM7 update.zip file? - Kindle Fire General

The third sentence of first paragraph of the first post (by whistlestop) in the thread:
Amazon Kindle Fire> Kindle Fire Android Development > CM7 for Kindle Fire (aka standing on the shoulders Giants)
begins by referring to "The update.zip file available here".
Available where? I've put hours into searching for it (or for any version of update.zip other than the original one that this one supposedly replaced), but with no luck.
BTW, I couldn't post this question in the thread I'm referring to because, apparently, I haven't earned the right to post in the Developers' Forum.

from the op:
If you're coming from a STOCK ROM then use this version to flash.
If you're upgrading from an EXISTING CM7 install then use this ROM instead.
click on "this" ...

So, since I haven't changed the ROM before, presumably the one I need is the first one, update-cm7-wipeall.zip. The second one, update-cm7.zip, would only be for somebody who has a previous version of the cm7 ROM installed, then? (I also have one called update-wipeall.zip that I downloaded from somewhere, but I'm not absolutely sure it's for the Kindle Fire.) In any case, do these have to be renamed to update.zip, or can they be used with their present names?
Anyway, I haven't proceeded with any attempt to install CM7 yet. I got diverted by trying to first install TWRP 2.0, using the method at teamw.in/project/twrp2/79. Unfortunately, my KF is now frozen (hopefully not bricked) for the second time since I started on the TWRP attempt. The first time the Fire came back to life pretty-much by itself. I'm waiting to see if it does that again.
Incidentally, I have a file named cm7barebones-sdcardroot.7z that I also got from somewhere or other. Is it of any interest?

it seems you have downloaded different roms
the barebones i only one part - it needs 2
which one do you want to install ?
and what's your problem with twrp ? - you have to fix this first ! - how did you install twrp ? - manually or kfu ? - there is a failure in the run.bat of the current kfu (0.9.3) - take the one from this post:
http://forum.xda-developers.com/showpost.php?p=23536888&postcount=1007

I mentioned in my previous post that I may have screwed up and bricked my KF. At first it would freeze after boot with just the words kindle fire displayed on the screen until I would hold down the power button to force a shutdown. At that time, it could at least be seen by System Profiler on my Mac, though not by adb or anything else. But now the words kindle fire flash on and off every few seconds when it's plugged into the computer or a charger, and the KF is totally invisible to the computer! Moreover, it appears dead altogether when not plugged in.
Anyway, I don't think this forum is the right place to discuss this problem of mine, so, perhaps after taking a bit of time out to deal with the rest of my life, including my other gadgets, and somehow then getting the Kindle working again (perhaps even by 'stealing' a logic board from a busted KF), I'll come back here.
Anybody who has any suggestions for me that aren't relevant to this forum should send me a PM.

Related

Complete Video Guide and troubleshooting for root,market,recovery,etc...

I see many people having issues that are new to this kind of thing and here is a fairly simple troubleshooting guide that I have compiled that I think will help many of you get through rooting, Installing the Market, and installing twrp with no problems. This is a complete video walk through for those of you find the videos easier. I recommend that you watch the videos thoroughly before attempting this so that you can be sure that you make no mistakes…!!!
• Start off with a stock Kindle on original 6.2.1fw
• Go to this link for a video walkthrough to root the Kindle with Jcase’s Burrito root. All of the links are in the description of this video to do so. http://www.youtube.com/watch?feature=player_embedded&v=KapnjR89ICA
• Now to install the android Market this is another video walkthrough that is from the same person once again all of the links are in the video description for downloading what it is that you need to perform this action http://www.youtube.com/watch?featur...tion_598718&src_vid=KapnjR89ICA&v=rTkegVrnAvA
• Now to install a custom recovery (aka twrp2.0) this is also another video walkthrough also made from the same individual. Once again all of the files needed are in the video description http://www.youtube.com/watch?annota...&src_vid=KapnjR89ICA&feature=iv&v=JqKZLMaRSgc
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB to get into adb shell
adb devices to make sure your kindle is connected properly
adb root to get proper permissions
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
• I have also noticed that some people also get stuck at 3:55 in this video at the firefire triangle. The fix for this is fairly easy and is explained in the video if you need a walkthrough step by step for doing this (Updating the drivers)here you go:
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
• If you also need a link for installing cm7 here is another video to do so also by the same individual. I do not recommend this as of yet until all of the bugs are worked out in this as I have heard many people have had problems with video playback or sound (mainly in ics) and usually end up flashing back to a custom rom anyway. It is your device though so it is completely up to you
http://www.youtube.com/watch?featur...tion_828059&v=L-zTJWY3CRc&src_vid=JqKZLMaRSgc
UPDATE JANUARY 3rd 2012
• Here is a link for a newer rom install called MIUI. This Rom is very smooth and the only thing confirmed not working at the moment (January 2, 2012 is video playback. There are however some individuals working on this issue and will hopefully have video working soon. Thanks to leeech for the MIUI port and nat3mil for the video. Here is the link for the easy to follow video tutorial.
http://www.youtube.com/watch?feature=endscreen&v=OqiX-If5w_4&NR=1
• Here is link on how to resize your internal storage (aka custom partitioning). This is called FireParted made by eldarerathis. This is good for those of you that think that they have too much storage in one place and not enough in another. Playing with partitions can cause you to lose data that is not backed up previously to editing partitions, so use at your own risk. I myself am going to use this to expand the storage on my sd card. Here is the easy to follow video tutorial.
http://www.youtube.com/watch?v=Bkff-bI-FrY
Big thanks for every one of these videos, made by nat3mil. So be sure to thank him and subscribe to his channel for all the latest easy to follow videos!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update January 7th 2012 This is a program to fix boot loop Problems easily (For Windows Only)
I noticed that many people are still having problems with getting stuck in a recovery boot loop, firefirefire boot loop (Yellow Triangle), Or even the kindle fire boot loop. This is a program to fix it automatically like the kindle fire Utility. I believe that it was made by Zombiepiratez, and he made this to change all of the headaches that many people are having with bootloop problems, proper file permission problems, and bricking problems, so be sure to thank him if this helps you. Once again this is a batch file made only for windows so for those of you that are not on windows, I will leave the common manual fixes below. Here is the link to his thread and download for the Fire Utility Unbrick:
http://forum.xda-developers.com/showthread.php?t=1428428
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Also for people getting caught in a recovery boot (whenever they turn on their kindle they boot into recovery without hitting the power button do this in your cmd:
adb shell
su
idme bootmode 4000
reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope that this clears up a lot of confusion for some of you weary of trying to do this to your kindle fire. I did all of this manually with my first Kindle. I have also used this method to be sure that it works and any problems that might come about when using this method and I have confirmed this to be successful. I really wanted to post this guide because I know that it is easier for some of you people new to this to follow along with a video. I know that some people say well there are a lot of tutorials out there but not one with a step by step and video links for a walk-through to do this whole procedure. If a mod could please sticky this I am sure that many would be greatful!!!
Remember that there is a thanks button…
DO not forget those who made this all possible:
Thanks to Jcase for Burrito Root & Vashypooh For KFU v.0.9.1 I would recommend that any of you that enjoy this and would like to see more mods such as these come out, to donate to these devs..
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
I was worried about doing this but now that I read your guide and seen the videos I am going to give this a try when I get settled in. Thank You!
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
You have to root the kindle before you can install the TWRP. the twrp 2.0 is used when you want to flash a rom and a few other things, (i think) you wont be able to install the twrp with out rooting first
babbabooey97 said:
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
Click to expand...
Click to collapse
I do believe that how to make a backup is on the install twrp2.0 video (the third one). I do not believe that you will have to install titanium backup like you do on your phone. I also do not believe that the sd card gets touched in the flashing process...
zwanzig said:
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
Click to expand...
Click to collapse
If you follow this guide in the order which was given everything will work out great after the first video your kindle will be Rooted. Twrp is really for creating a backup of your kindle in the current state and flashing different roms such as cm7 or ics... There are many things that you can do with a rooted Kindle really too many to name. You can run different market for starters which will give you more of a selection than what amazon has to offer. I did not mean to sound as if cm7 is not a good thing to use it is just not as stable as it could be and ics is still in the process of being worked on. I will be flashing to a different rom myself such as cm7 or cm9 or ics once they are stable with little or no bugs...
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
babbabooey97 said:
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
Click to expand...
Click to collapse
From what I understand if you are on a different rom such as cm7 you will not recieve a ota update, i could be wrong so do not quote me on that. I have however heard of people installing a modified 6.2.1 update that will help them update from the old fw to the previous one, so for them to have not gotten the update they must have either been using cm7 or turned their wifi off completely until they found a sure fix. Do a little searching on older threads you might find something when you do post back to this thread but make sure that you are sure that it does work as I would not like to have any mis-information in this thread... Thanks
[-_-] said:
From what I understand..... I would not like to have any mis-information in this thread... Thanks
Click to expand...
Click to collapse
Edited the quote for my own amusement.
What all do you use your KF for? I use mine while at work to keep from lugging my Mac around. Also for the occasional updates (socialnetworking=SN) and emailing.
Another question I would like to know is the types of differences there are when running alternatives in the ROM Dept.....fluid transitions, non changing wallpapers, and the like?
Can't give you a thanks yet because of low post count, but this is exactly the sort of thing someone needed to do.
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
guides and explanations
Its good to see your hints, because all those really awsome videos have their traps and you can easily get trapped on it, as i did and i had a hard time to find the right way.
My secret for this is to fully understand why you have to do this and that, and here all the guides lack, because there is no explanation WHY you have to do this.
This needs more love. I was successful, because i know from my old background how a chmod works, why i had to install the drivers again and so on but it really took me a while to get this all done, because i didnt read this thread in time.
I also understand that developers are excited about their custom roms and the cyanogenMod, but really who wants to have a kindle fire without sound and a mod with so many bugs ?
I am so happy to have my kindle fire rerooted again after the latest update without opening it or using a special cable.
So this all works quite well, but the guides really need some more explanations to get a deeper understanding about what we are doing here.
I am still working on that, to learn the details.
I want to say a big thank you to all who invested their free time and to spread the knowledge about this awsome device and make the kindle fire a really usefull tablet.
Please keep on the good work ! And have fun with a fully rooted device. There are so many possibilities now !
JoshuaLintag said:
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
Click to expand...
Click to collapse
You are very welcome I am glad to see that this guide helped you to get this accomplished!
Don't forget to give a big thanks to Jcase for Burrito Root and Vashypooh for Kindle Fire Utility!
BeerRunJoe said:
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Click to expand...
Click to collapse
I am glad to see that you got through this flawlessly. This thread was made just for that very reason to help the lesser experienced user with any issues they might encounter without having to post threads that may get lost in all of the other "Help Me" threads...
If there is a mod that could please sticky this thread I do believe this will answer many questions for individuals and help new users pull off a flawless root, recovery, etc...
+1 on stickying this thread. I have just been pointing people having the same basic problems here. This thread (especially the OP) seems to be helping a lot of people who need help "filling in the blanks".
Good job [-_-]!
I have also directed many of my friends to this thread and they have also gotten through their minor problems. It is kind of funny because a lot of my friends tell me I think my kindle is bricked I just laugh say I doubt it and send them here. Can you also make a guide about going from cm7 back to a the amazon rom please. I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
BeerRunJoe said:
I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
Click to expand...
Click to collapse
Yes this will work...
1.Plug in USB cable to Kindle Fire on TWRP Recovery mode.
2.Bring up Command Prompt.
3.Key in adb shell.
4.Key in idme bootmode 4000.
5.Finally, key in reboot.
There you go..!!!
Great tutorial setup. Rooted, installed Android Market as mentioned without any issues. Have not installed the Recovery yet though.
Thanks for this thread.

[Q] New kind of unfixable Super Brick?

My kindle is bricked and I have tried everything.
This is what i did: I rooted it, installed CM7, it worked fine. I then wanted to go back to the stock rom (due to countless FCs and freezing in CM) so i flashed the stock rom through TWRP. When i re-booted, the TWRP recovery screen no longer shows and it has the stock kindle fire logo on screen.
It does not show up in device manager in windows, I have re-installed the usb drivers multiple times. Any recovery methods using ADB simply result in "waiting for device" forever.
I have tried:
hard reset
fastboot commands
booting to linux live cd with firekit
kindle fire unbrick utility
None of these work because it does connect via usb
Anyone else have this problem>?
EDIT: Im fed up, ive tried every method on XDA and youtube, nothing works. I convinced amazon to replace it. Thanks anyways.
Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728
lovejoy777 said:
Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728
Click to expand...
Click to collapse
If you notice, that uses ADB shell. All of these commands result in "waiting for device" as it it not detected as a USB device
Sorry forgot to attach
Ok dont worry ive gotten my self into the same issue and lots of other ones lol
I just kept on trying different things.
it will be a driver issue Ill try to find the thread that got me out of it
---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------
Found it Try this.http://forum.xda-developers.com/showthread.php?t=1399889
I bricked mine last night and kept getting stuck at "waiting for device" and figured out Windows ceases to recognize it as something it has a driver for.
Windows Device Manager showed the Kindle with a yellow sign next to it. I right clicked and updated the driver but rather than detecting it at all I manually picked a device.
Don't have Windows in front of me right now but it was something like "Android Phone" for the device type and then the device was the first one listed "ADB Interface" or something starting with ADB anyway.
Once that driver was loaded I could issue ADB commands again and got it fixed.
Sent from my Kindle Fire using Tapatalk
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.
bg4 said:
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.
Click to expand...
Click to collapse
Well considering he already convinced amazon to send him a new one its a little too late, and others have already weighed in to help, its not very nice but its the truth. If he would have just waited more than an hour for people to try and help him he would probably have been able to fix it.
Jus a quick servh would give you the answers you're looking for. It's not bricked. So relax
HaroldBawls said:
Rooting it inst the issue, trying to put a phone OS on a tablet is the issue.
Click to expand...
Click to collapse
?
Tell that to all the Nook Color users running CM7 or to Samsung, HTC and others that shipped tablets with Android 2.2 and 2.3
googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
Troll found. Anti-Hate taser activate.
Sent from my Kindle Fire using Tapatalk
Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.
i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else
zbhest said:
Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.
Click to expand...
Click to collapse
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk
mattlgroff said:
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
This is exactly what happened. Because it didn't have the TWRP recovery screen or anything, any average tech support person wouldnt be able to tell it had been rooted. The failure actually happened after installing the stock rom so im pretty sure if they even take the time to inspect it, they wil see an unused, unrooted stock rom on the devoce
punkboyarde said:
i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else
Click to expand...
Click to collapse
Thanks, but this only works if it connects over usb. Doing this results in "waiting for device" as mentioned before

[Q] Thinking about getting a Kindle Fire...

I am thinking about getting a Kindle Fire tomorrow and was wondering(just wanting to make sure), could I use this tool(http://forum.xda-developers.com/showthread.php?t=1399889) to root and install the Android Market right out of the box?
I am not new to Android(I own an Xperia Play), just new to the tablet scene...
that is what kfu (kindle fire utility) is supposed to do
but please read the op very carefully - espacially the "known tricks" - to avoid problems
a post from vashypooh - the dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
the most challenging thing is to get drivers working
read here about it:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Since you already have Android, you also can simply load anything from the Android Market onto your Xperia and then grab it to your PC and install it to the fire using adb. That doesn't even require rooting the Fire.
b63 said:
that is what kfu (kindle fire utility) is supposed to do
but please read the op very carefully - espacially the "known tricks" - to avoid problems
a post from vashypooh - the dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
the most challenging thing is to get drivers working
read here about it:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
I read to install the drivers first before running KFU, anything else I should know?
Sent from my R800x using XDA App
not realy
maybe a little hassle with the drivers if you have bad luck
if you have a choice of computers then a 32bit system is easier to get rid of the drivers - if you have xp available it would be my first choice because you don't have to care about the uac (user access control)
if your working with it you will make your experiences and it is likely that you have sooner or later a little little problem (brick). it's called brick but mostly it is'nt realy a brick - it is simply a other bootmode - if you know how to handle it it's a matter of seconds
don't worry - i have never seen a realy bricked one besides of hardware failure
there is allways a way out ...
b63 said:
not realy
maybe a little hassle with the drivers if you have bad luck
if you have a choice of computers then a 32bit system is easier to get rid of the drivers - if you have xp available it would be my first choice because you don't have to care about the uac (user access control)
if your working with it you will make your experiences and it is likely that you have sooner or later a little little problem (brick). it's called brick but mostly it is'nt realy a brick - it is simply a other bootmode - if you know how to handle it it's a matter of seconds
don't worry - i have never seen a realy bricked one besides of hardware failure
there is allways a way out ...
Click to expand...
Click to collapse
Thank you. I am on Windows 7 64-bit. Yeah, as I said earlier, I'm not new to Android. I have a Xperia Play rooted and custom rom(the whole shibang).
What do you think the chances are of me running into issues? All I want to do is just root it and get the market, thats it
if you just root and install the market the chances to run into issues are quite low
One thing I did that caused a problem was, when it rebooted after installing firefirefire with the triangle and fire it said press power button for recovery and I did. I didn't realize that I hadn't installed TWRP yet so it got stuck on the fire screen and wouldn't boot. I finally got it fixed by running a KFU command at just the right time to get it out of the loop. So, just a tip, DON'T BE AS DUMB AS I WAS AND PUSH THE BUTTON... Anyway it should go smoothly.
KFU is a great program and the most recent version includes updates to limit bricking your device. The hardest part to it all, IMO is installing the google usb driver. I guess that depends if you use the traditional Android SDK method or the easier method available now. Make sure you use the KFU version 0.9.3 as it is tailored towards the 6.2.2 update that was recently pushed to all Kindle Fires. KFU literally roots your device and installs all necessary items in 3 or 4 button pushes. Good luck.
sanman6046 said:
KFU is a great program and the most recent version includes updates to limit bricking your device. The hardest part to it all, IMO is installing the google usb driver. I guess that depends if you use the traditional Android SDK method or the easier method available now. Make sure you use the KFU version 0.9.3 as it is tailored towards the 6.2.2 update that was recently pushed to all Kindle Fires. KFU literally roots your device and installs all necessary items in 3 or 4 button pushes. Good luck.
Click to expand...
Click to collapse
The USB driver took me like 30 min to figure out... It's such a pain in the butt, I really have thought about making a one click utility that would install it.

So I heard you can root...

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".

[dev][apx][nvflash][tegra-note-7][update]

If anybody bricks his/her device and has only the APX mode available or is trying to get an nvflash utility for a Tegra Note 7, now the solution can be found: the Advent company has published a full package including a nvflash working with the Tegra Note 7. Moreover, the package contains a signed bootloader and bct and all the other parts of the entire storage (including the system partition for a 4.3. JellyBean).
It can be downloaded from their website of adventcomputers.co.uk in the downloads section (I can't post links yet), select Product range: "Advent"; Product type: "Tablet"; and then choose "ADVENT Vega Tegra Note 7", do not be mystified by the "driver" type and download the "Advent Vega Tegra Note Factory Image (4.3)" (about 641 MB package)
Many thanks to the dev and support guys at Advent (Dixons retail plc), because they have put the final cherry on the top of the cake. The Nvidia Tegra Note 7 is now not only a top of the top devices regarding its power, but this package renders it into an unbrickable device.
(note: I'm NOT affiliated with any of the companies, I just bricked my device and had no other mode available than the APX mode. I'm posting this post due to the abovementioned reasons, because I find this quite and important source for further hacking(orig. meaning) of the devices. In fact I regard this as an utlimate source for development on this platform.)
I have tried the package (including the batchfile, that does the automation), it works for me on my Advent Vega Tegra Note 7, however Im not sure if it will work on others (EVBA for example), so please feel free to test and post your experience underneath here.
Link: http://adventcomputers.co.uk/product-download-select/296
Sent from my TegraNote-P1640 using Tapatalk
thx
Thanks for the heads up. I tried it on my bricked dodgy manufactured tablet and I was able to get the device to a new level but it still crashes trying to boot the system partition. Least now I have fastboot.
With the nvflash recovery tools you can replace the images to suit say bat-recovery or latest boot.img with menu options the older version doesn't have.
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
HEhehee. This nvflash recovery is only new to the scene so I didn't get time to check it out then inform you Shaky.
In my opinion our community can rehash these tools and make a better recovery.
Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below), but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if this forum platform and its admins do not provide support for this.
With regards
------ Original message ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks
rheingold said:
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below)., but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if the platform and its admins do not provide support for this.
With regards
------ Original mail ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks
Click to expand...
Click to collapse
Hi i dont have an issue with this, mistake on my part, I thought this was my thread lol. Ive reopened my thread and its moved to Q&A. Will work on a newer things, I have new files. Will test few things first.
Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards
After finding out after a long time about this guide,I managed to reflash the stock firmware and reset the tablet,so hurray and much thanks for sharing this guide
Sent from my HTC One X using XDA Premium 4 mobile app
Ok, I need some help if anyone can.
I erased the boot file on my Nvidia EVGA Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.
Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Hiro51 said:
Ok, I need some help if anyone can.
I erased the boot file on my Nvidia Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.
Click to expand...
Click to collapse
lizard-borys said:
Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Click to expand...
Click to collapse
Can't use usb without power. The tablet will not stay turned off now and because of that, the battery won't charge enough to usb without power from usb.
I've even plugged in the charger and gone into boot-loader and clicked on shut down, but it still won't stay off or take a decent charge.
I have tried a different computer as well as different ports with the same results.
btw, thanks for replying.
As I reread the posts, I noticed rheingold's post at the bottom says he's not sure if this will work on the (I believe he meant EVGA) model. Can anyone verify it works on EVGA?
Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.
Hiro51 said:
Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.
Click to expand...
Click to collapse
Nice work mate. I am speaking with Nvidia too see if they will do factory images like the Shield but waiting on a response for that.
Also OTA 2.4 is now Live as of 5 minutes ago.
It seems the USB cables are not of high quality just like the ports.
lizard-borys said:
Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards
Click to expand...
Click to collapse
Having the same issue here.. anyone?
I have a copy if its needed still.
Today, panic stations as I thought I had bricked my Advent Vega Tegra Note 7.
I had updated yesterday to KitKat along with additional OTA updates, but decided
to go back to 4.3 to capture the update after main KitKat update (2nd of 6 updates [EDIT: forgot to cap that one]).
I unlocked bootloader via fastboot, then flashed system.img (4.3 from Advent) and then the TWRP
recovery.img EDIT: Also locked bootloader..
On boot, it got itself stuck Powered ON at the TEGRA NOTE (white on black) screen, all was doom and gloom.
I finally figured out that holding down Volume+ then pressing the power button quickly and then
pressing again (whilst still holding the volume+ button down), I could get into the recovery menu
to access TWRP. In TWRP I did a factory reset and hoped for the best.
On reboot, all was still doom and gloom. So I thought maybe it might be necessary to have the
appropriate boot image (rather than the 4.4 boot image), and so flashed that, and Voila,
everything is hunky dory again.
I seem to have lost ability to use nvflash (APX mode) after original 4.3 flashing (which I could access
on the device doing the same dance as above but pressing both volume up and volume down keys before power).
My USB driver Vender ID and Product ID's below, I seem to have two Fastboot Id's, presumably one for stock recovery
and the other for TWRP (I blanked last 5 digits with x's just in case they could be used for nefarious deeds).
Code:
Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\052101410714600xxxxx
TegraNote-Premium Google Galaxy Nexus ADB Interface Vid_18d1&Pid_d001
Tegra NOTE TegraNote-P1640 Vid_0955&Pid_cf02
Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\15C4110C904000000100xxxxx
Advent Vega Tegra Note 7 Vid_0955&Pid_cf00&MI_00
Tegra NOTE Advent Vega Tegra Note 7 ADB Vid_0955&Pid_cf00&MI_01
Tegra NOTE USB Composite Device Vid_0955&Pid_cf00
APX NVIDIA USB Boot-recovery driver for Mobile devices Vid_0955&Pid_7535
Anyway, perhaps above is all known to you old salts, but for a newbie like me, is perhaps of use.
Also, thanks for the link
You can access APX by pressing Power plus Volume down and Volume UP at the same time and holding them.
Thanx hacktrix, I could access APX OK (was stuck with power on, ie could not power off, the dance described allowed me the access both fastboot and APX).
The problem was nvflash via flash_signed.bat.

Categories

Resources