yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
Is your kindle turning on? If I could suggest you should put off anymore attempts to root your device till you know precisely what your doing and why. My biggest guess right now is your drivers are the greatest pitfall. You seriously don't want anything going wrong with them in the process of sending recoveries boot loaders or rooting you will end up with a really fancy paperweight. Privy to to attempting anymore you need to know that your drivers are functioning 100%.The fact that you pushed cwmr to your device after twrp should hurt a thing hopefully one should overwrite the other if all goes well . Since rooting is the primary goal go with that until you have verified root then recovery and bootloader can be done easily later with safer methods. Hold off awhile as long as your device will boot until you have found the knowledge and support to make it happen right. Start here http://xdaforums.com/showthread.php?t=1552547 then go here http://xdaforums.com/showthread.php?t=1638452 plan to use this method to root http://xdaforums.com/showthread.php?t=1568340 ask a lot of questions don't be hasty or you will spend a lot of time trying to fix it instead of enjoying it.
[Kindle Fire Q&A, Help & Troubleshooting] saybhausd:
As I said, I read all those guides already. I can use my kindle normally, but when I connect it to my computer, it is unrecognized. I tried every method I found to root, even though I just wanted to watch stuff and download a few games for my spare time(my intention was to watch stuff from premium features, but Im not really sure if root will allow me to do that from a foreign country*, so Im a little hesitant to extend premium).

I guess I wont try anything else for now because my main goal was reading, and this I can still do, but I am puzzled with the fact that I was unable to root it. Ill try to understand a bit more (hopefully with some tips). Thanks

*Geographical restrictions
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
OK well youve read the guides but in what you say it appears you are doing some of the wrong things why would you unbrick if your not bricked? Your drivers are your only issue as of this point but your methods are pushing you close to bricking your kindle. I would like to see you succeed in rooting your device and avoid bricking it.

---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------

When your around we can try to get your drivers working
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
It would be nice to know what os your running on your computer. If you are on windows 7 use system restore to roll your computer back to a date before you started messing with the drivers or anything. Once it completes plug your kindle into your computer check to see if you can access the SD card contents and if it appears as a kindle in your device manager. Important now if all is good unplug your kindle and run the .bat file that comes with kfu. Then plug your kindle in let windows install the driver. Open up kfu find the tools folder shift plus right click select open command window here. Then type adb devices if its followed by a string of numbers this shows your kindle connected via adb . At this point you should obtain some help from some of the pros here at xda at fastboot and adb commands to safely root your kindle. If you decline and still wish to use kfu then only select install permenant root. If at any point in this process it fails and you loose adb connection do not unplug your kindle run the driver file again then recheck device status with kfu I believe its option 0 to see if your back online again. Pay attention to the dialogue that takes place in the kfu window you see verbatim that says failed or permission denied then quit after that. One important thing is you need to allow installation from unknown sources in the kindle settings on the kindle under device or it won't push the required files anyway.Wait to install twrp and fff until later there are easier safer methods. If your kindle hangs for a long time at the kindle fire logo select boot mode normal in kfu before unplugging. If at anytime kfu states waiting for device do not unplug it rather power it completely off then power it back on while connected .

---------- Post added at 01:53 AM ---------- Previous post was at 01:32 AM ----------

Just a side note I have rooted 4 different times with kfu without a single failure or mishap including the ones you are experiencing. I'm inclined to feel that relates mostly to your computer and drivers which makes kfu an unsafe approach for you I'm not responsible If you brick it!!!
[Kindle Fire Q&A, Help & Troubleshooting] saybhausd:
I unbricked my device before I even came here, I tried an youtube tutorial and then it got stuck on the kindle fire logo, but after I unbricked it, it was fine. I know that something is going wrong, but Im following step-by-step the guides (at least I think so). As I said, everything was going correctly, ADB was online, Boot:4002, but when I tried to root it would be on an endless search for the file twrp.img, and after I succesfully downloaded it (I guess), my computer is unable to find my Kindle.

I run Windows 7, but it isnt properly activated (my room mate threw out the serial code), I dont know if this would interfeer in any way. When I conect the kindle, it appears to be in USB mode and says that I can transfer files, but my computer wont even find it. Ill try to restore my computer now and then Ill come back.

I know that doing this is my responsibility, but not being able to download apps is pretty annoying, so I have to keep trying.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
If you can get adb status online then, why don't you install TWRP manually? Or use the "smirkit"?

Once you get recovery installed, you're set.

Also, be sure to "disconnect" from USB storage mode before trying to use adb commands or they won't work.
[Kindle Fire Q&A, Help & Troubleshooting] saybhausd:
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Shift+right click your KFU "tools" folder and select "Open command window here"

From there, enter:

adb devices

If the output is something like:

List of devices connected
123456789ABCDEF

then you can install TWRP

http://xdaforums.com/showpost.php?p=23747804&postcount=3

If the output is:

List of devices connected
(null)

then you need to reinstall your drivers

http://xdaforums.com/showpost.php?p=23747671&postcount=2
[Kindle Fire Q&A, Help & Troubleshooting] saybhausd:
Thank everyone that helped me, I managed it!

Actually I was doing everything right, but I guess the problem was my computer, because when my girlfriend came over I tried connecting it to her netbook and it recognized my kindle. I just downloaded the kfu, installed drivers, reconected kindle and let it update, ran KFU and selected option 2. All done now :D

I have no idea why this didnt work before, but at least now I can really enjoy my kindle.

Thanks again!
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
Not system recovery bud system restore two different things go to accessories system tools system restore choose a date chose to restore to that point. System recovery is way way different. Glad you got it going:-)
[Galaxy S I9000 Q&A, Help & Troubleshooting] eugene690922:
Hi

I use zImage , created a tar ball, and use odin to download...

i9000 boot to GALAXY S logo and stop.

I used mkbootimg create a boot.img.

I9000 still stop at GALAXY S logo...

How to create a odin acceptable tar ball?

Or any easier way to download zImage?
[Nexus S Q&A, Help & Troubleshooting] twadda218:
Anyone know of a kernel with just cpu settings, no live oc, just one or two governers, voodoo, and garbage removed? I like francos but he doesnt have cpu or voodoo.

Sent from cold hill on Nexus S

Rom: BM ICS 4.0.4

Kernel: Air 4.2
[Nexus S Q&A, Help & Troubleshooting] Pipusz:
Either _thalamus' kernel or SimpleKernel. The first one is optimized stock, while the second one is pure stock with a couple tweaks.
[Nexus S Q&A, Help & Troubleshooting] apatal:
Try INK kernel. Download it HERE

Sent from my Nexus S
[Nexus S Q&A, Help & Troubleshooting] chronophase1:
+1 for SimpleKernel. It is what it says. I just tried thalamus' kernel on my phone and every time I streamed music, my phone locked up. No idea why. Oh well. It's still labeled as experimental so it's to be expected there will be an issue here or there. Back to SK for me and it's quick and does what I need it to do. 1000mHz should be plenty for most people. I don't see the reason for overclocking if you just need the phone for regular use like video, texting, calls, browsing, etc.
[AT&T Samsung Galaxy S II SGH-I777] Eckyx:
This is a new concept to me. There are no PCs that "just don't like Windows". With the same hardware, a PC will run the same software at the same speed with the same stability. All SGS II i777's have the same hardware, don't they?

There are of course variations in the quality (=bin) of some components, but that just sets voltage boundaries for a given clockspeed (or in extreme cases, makes a phone defective), but this shouldn't affect how a ROM runs.

What am I missing?

Why do some problems persist on what seems to be a clean install on some phones, and don't manifest on others? Do some ROMs run better because of different recoveries? What's left after a full wipe?

Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
[AT&T Samsung Galaxy S II SGH-I777] zelendel:
Simple answer is no not all devices are made the same. You see this with mass produced hardware. As for your PC ref. My brother and I have the same laptop while mine loves my set up, my brother has nothing but problems with it on his system. It comes alot down to personal set up and device. This has always been the case with mobile devices and custom roms. Stock roms are set to run on all devices the same. This is not so with custom roms.
[AT&T Samsung Galaxy S II SGH-I777] Fusion777:
Zel pretty neatly answered this, but I will also add that modern consumer electronics interact with the immediate environment far more than our pcs do. Light sensors, 3g radios, barometers, etc. are far less deterministic than our classic closed-loop pcs. Part of this perception of flux is based on this real flux, for example one of the core features people will discuss is call/modem quality, but driver tweaking vs. actual signal strength is a pretty fuzzy battle for anyone but an electrical/firmware engineer. And just like in the pc world, when you're talking under volting and over clocking your mileage will vary.

If you are methodical and read all the materials, your phone will operate tip top. It seems to me a lot (not all) of the variances often do boil down to the users configuration.

Sent from my iPad using Forum Runner
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
I have fixed a lot of computers and have been flashing custom roms for a year and ill tell you, in my personal opinion, problems are 90% user error. If people would all install properly and wipe everything completely and follow everything they're told to do and read all possible material on what they're flashing they can, a huge portion of the problems would dissapear. But is that gonna happen? I hope so :)

Heck I make mistakes too. None of us are immune to screwing up right? Good luck all, happy flashing.
[AT&T Samsung Galaxy S II SGH-I777] votinh:
Yes, they should and they do, absolutely with every ROM, stock or custom.

If they're purely, properly installed, they're all the same.

By "purely", I meant completely, virgin-like ROM without any add-on.

If you choose to install somethings else, to customize your needs or set it up the way you want, then it's a whole different ball game.
[AT&T Samsung Galaxy S II SGH-I777] alacrify:
Just to chime in on the Windows thing - we buy a standard build HP computer at work for all developers. But if you put the same Windows disk in two of them and boot and install accepting all the defaults, there will always be slight variations in the way it configures itself between the two. It's probably the hardware detection that does it, but I swear you could get two of the same build lot and you'd STILL get something that didn't set up the same way. Sunspots? Power surge during the process? I dunno, but it does vary :D
[AT&T Samsung Galaxy S II SGH-I777] RatusNatus:
You cant change the disk. Your network adapter has a MAC adress on it... windows will know something has changed. motherboard also has one.

A PC component are not the same at all.

You can buy a good I7 2600k or a bad I7 2600k. There are revisions of the very same model of CPU, memory, everything and its really hard to make 1 equal another.

Another thing is that one smartphone is a lot more delicate piece of hardware and the most important, has limited power to it components.

That makes harder to change anything on it. A small change could lead you to a failure.
[AT&T Samsung Galaxy S II SGH-I777] Lucke:
just blame it on the ghosts in the machine and be done with it :p
[AT&T Samsung Galaxy S II SGH-I777] Aeltar:
This is not the case. I have tested with two different EVO 4Gs and two different SGS IIs - of the same hardware revision, even.

I performed the same steps to root and ROM both of the sets of phones, and put the same ROM on them. There were no other apps installed, nor themes/addons. I then used each as my phone for a week, making sure that I installed identical apps and even synced app data.

Both performed differently. My i777 is the faster of the two, but my EVO 4G was the slower and more bug-prone.

Yes, this is anecdotal evidence, but I at least am convinced. Take it as you will.
[AT&T Samsung Galaxy S II SGH-I777] melinerunen:
Also the phones are made with lower quality checks than desktop. ie I can oc my sgs 1 up to 1.6GHz but uv of -25, the phone well restart. But other people can't go more than 1.2 and cab apply a uv of -150 on the same step.

This is a fact. Think if every phone it's done with high quality checks the price of the device will raise pretty high.
[AT&T Samsung Galaxy S II SGH-I777] sremick:
Once of the frustrating things is that the people responding on the forums, (ROM devs and regular users) often try to have it both ways.

If you're experiencing something they aren't, it's obviously your fault because it doesn't happen on their one phone so it can't possibly be anything but your own fault. Go wipe 50 times and do other things that will take 3+ hours each time and don't come back until you do.

Oh... you've done all that already and still having the issue? Oh well, all phones are different... tough luck, bro. I'm not going to spend any time on anything my one phone doesn't do.

(Never mind that a dozen other people have reported the exact same issue, and another several dozen are experiencing it but are too scared to post about it because they see how everyone else is being flamed, castrated or even banned for daring to suggest a bug.)

One way or another, it seems a convenient way to blow off users having legit issues.

While I suppose there might be slight deviations in components once in a blue moon, I think the "all phones are different" excuse is more often than not used as a way to easily dismiss people and issues without helping. It's been repeated over and over for so long now, the majority take it as "fact" without really putting much thought into how it could possibly be as widespread and dramatic as they're pretending it is.

I don't buy it.

Even just with modems... everyone's like, "Oh well all phones are different... some modems work better on some phones, or in different areas". What kind of BS is that? How on earth could any phone manufacturer then create a mass-market phone that worked across the country without hacking? I'm sorry, but you can't chastise and criticize the manufacturers for not producing the universal "uber-phone" that works great anywhere while at the same time admitting that "all phones are different" and therefore require hacking for your specific flavor or region. It's hypocritical.

I think it's very, very rare that actual hardware differences between the exact same model phone account for issues people experience, and is more often than not either user or dev (as much as they try to paint themselves as infallible gods) error that they don't want to bother with. "All phones are different" = "F-off, I don't want to deal with this"
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Great so what you're saying is everyone that says this (especially devs) are a bunch of dicks. Nice.
[AT&T Samsung Galaxy S II SGH-I777] sremick:
That's actually not what I said at all, but I know it's a lot easier to summarize my post into one sentence that makes me look like an ass, than actually look at the points that I made.
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
I read the whole thing and that's exactly what it says.
[AT&T Samsung Galaxy S II SGH-I777] sremick:
Nope. But let me simplify it for you:

1) There can't be the level of hardware variation that people claim. It's not seen in other electronics, and it's not been seen before the recent generation of smartphones. The assumption of its existence is a recent phenomenon however if it were real we'd see it everywhere, on other electronics other than phones.

2) If it were to really exist, people would lose the ability to legitimately blame the phone manufacturers for 90% of what they currently give them crap about, especially in regards to making a quality stock ROM. What are they expected to do, create thousands of variations of stock ROMs, one for ever county in the USA to compensate for this accepted "all phones are different" theology?

3) Due to it being repeated over and over and simply assumed to be true without any actual evidence to the fact, it's become a convenient way to dismiss user issues... even in the face of mounting evidence to the contrary on a specific issue. This unfortunate trend causes lots of friction between users and devs. Even if it were true, it's now become an over-used dismissal without allowing for the chance that the user might be right.

People can't have it both ways, but right now there's a lot of hypocrisy. If it's true, there's been no evidence actually shown... just anecdotal experiences that could be chalked up to any number of other things. And whether it's true or its not, either way a massive amount of thinking and behavior would then have to then change... but right now, people behave like it's true and not true at the same time, which is nonsensical and frustrating.
[AT&T Samsung Galaxy S II SGH-I777] Kinador:
The simple answer is, there is no answer. Its the nature of the process.

I've had one click roms fail the 1st attempt only to succeed the 2nd without even closing the Odin just reconnect the phone.

Either you accept that and have fun with it. Or stick to stock and move on.
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
No you're actually wrong because sometimes things CAN go wrong with flashing stuff. And modems in fact do work better in some places than others even though they try to make them universal it is very difficult to do that. Also, if a dev doesn't see a problem, how is he supposed to fix it? Riddle me that one. Also, restoring should take at most an hour with something like titanium backup. So 3+ hours is bull.
[AT&T Samsung Galaxy S II SGH-I777] sremick:
He can start by not flaming the several people experiencing it (which scares away others also experiencing it, self-validating him and making him think the problem is less-common than it really is)

There's a difference between a problem being simply difficult for a dev to pin down and solve, and just attacking any user who dares bring up an issue that the dev himself isn't experiencing. Therein lies the hypocrisy, though: if "all phones are different", then a dev has to accept that a problem a user is experiencing might not be the result of stupidity on the user's part, and might actually be something in the ROM that simply didn't surface on the dev's phone, but is still something that needs to be addressed at the ROM level.

I totally accept that an issue the dev can't reproduce on his own phone is harder to resolve. But there are several devs who even make ROMs for phones they don't own anymore, and still manage to work with users to resolve issues. App devs do the same thing to resolve incompatibility bugs/issues with specific phone models the app dev don't own.

Not quite. Just the backup alone takes 45+ mins on my phone. The restore is the same amount, so you've got 1.5 hours right there without taking into account everything else that TB doesn't handle that needs to be reconfigured by hand, or the actual flashing, and tracking down other surprises. And because I apparently am one of the few people who care about their data, I also back up my internal SD... just in-case something goes wrong. I know the wipe shouldn't touch it... but "**** happens" and if something goes wrong during a flash and I didn't have a backup, it'd be my own fault and I'd be subsequently flamed for that. So I play it safe.

Once again, a case of users for whom its quick trying to tell everyone else they're full of BS. I accept that for some users, whether it's the # of apps, amount of data, or whatever, it goes fast for them. Lucky them. Why can't they accept the fact that it's not "10 mins" for everyone like they spread around and flame others for suggesting otherwise?
[AT&T Samsung Galaxy S II SGH-I777] zelendel:
Ok Here is the thing. I have personally been flashing and making custom roms for phones as far back as the Motorola razor v3. I have multiple phone running the exact same firmware, set up the exact same way and the have run totally differently. If all phone were made equal then there would be no returns due to issues the phone had as they would have all run the same and acted the same as the units that the OEM quality control tested. Lets take the Black Jack 2 as an example. The BJII was a WM phone that would self corrupt the system/media folder. This prevented any ringtones from working and the OS had to be reflashed. All this running on Stock firmware. This didnt happen to all of them, but became a well known glitch to anyone that did cell phone troubleshooting and repair. Did you ever stop to think why OEM and carriers dont use the roms from places like XDA? This is because things here are always under development. There will always be bugs. In the end the developers are making things for their phones and are nice enough to share it for others to use. Some do keep making roms for phones they dont have as this is overly not hard to do. They do this just to be nice. Except for the hardware drivers most of the under lying OS is all the same.

If a dev cant reproduce it then there is no way for them to fix it with the way people tend to report bugs. (The wrong way without the proper info)

Now lets jump to the present. I have 4 phones sitting on my desk. 2 are the HTC Inspire and 2 are the Samsung Captivate. Both running the exact same rom and apps, but guess what. They run very differently. On 1 Inspire and 1 captivate, I can OC to almost double, while the other 2 cant handle more then 1.2 over clock.

One of them also doesnt like the AOSP based software while the others are fine.

As for your backing up and restoring. It can take a long time if you have a TON of apps. Flashing custom roms are not for everyone. If you dont have the time or the want to learn something then you are doing it for the wrong reasons.