yashsingh1/xdaforums huggingface dataset:
[Nexus S Q&A, Help & Troubleshooting] albundy2010:
How about instead of making a thread with no one helps me in capital letters and bumping it over and over again. You actually put info in your thread. Like what you did. Examples. Unlocked via fastboot with sdk flashed so and so recovery and so on

Or you could have just searched the forum/read another thread about how to fix a phone stuck at google logo because of user error.

Frankly you are lucky anybody even bothered to help you at all.
[Samsung Galaxy Gio GT-S5660] Ax.:
Hola quería hacer una consulta sobre hacer el overclock al samsung gio actualmente lo tengo a 864Mhz pero mi duda es esto acorta mucho o no afecta tanto la vida útil del teléfono. O alguien tendrá unos ajustes que me pudiera proporcionar para darle el mejor perfomance a mi movil.

Actualmente cuento con esta rom:

[ROM] Cy4noobsMod-7.1.3.1

Gracias por sus respuestas.:D
[Samsung Galaxy Gio GT-S5660] Rayhananthaaa:
Use english please dude, and i'll reply your question...
[Samsung Galaxy Gio GT-S5660] voetbalremco:
I can read it, a bit .. You mean you dont feel an increased performance when overclocking and using your phone?

Well you can use tweak packages for that, adrealine engine is good
[Samsung Galaxy Gio GT-S5660] voetbalremco:


Translated with google ;)

You want to know if its bad for the live of your phone..?

It can be bad actually, but I havent got problems with it, clocked at 902 mhz as stable as normal., I dont think it goes less long than if I wouldnt overclock it, but I can test that anymore, as I didnt buy 2 gio's at the same time and didnt overclocked one :)
[Samsung Galaxy Gio GT-S5660] GuestX0026:
I use stock with custom kernel, overclocked to 921 MHz. Perfectly stable with good battery life (about 15 hours with constant Internet access) and very smooth.
[Samsung Galaxy Gio GT-S5660] czkwg8:
i think 806MHz is enough for me:D

中国人正在尝试提高！

(translation:Chinese people are trying to improve themselves！)
[Galaxy S II Q&A, Help & Troubleshooting] xMini:
I want the stock kernel for JPKH8

PLEASE !! I searched the whole web but I couldn't find it :( !!

I have the ROM itself but I want the Kernel
[Galaxy S II Q&A, Help & Troubleshooting] cooza:
Its on the SamMobile site.Sign up for free and download the ROM.If its a PDA only file flash it anyway to get the kernel back.

http://www.sammobile.com/
[Galaxy S II Q&A, Help & Troubleshooting] Silverwolf2:
I can't find Claro Peru firmware.

Someone knows something?
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
Really? The WHOLE web?

But seriously, if you have the ROM, you should have the kernel already, right? It's IN the ROM.

Carrier firmwares are here. I didn't see one for Claro specifically for Peru, but search that thread. Someone else there may know if one of the other countries may work or not.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] impy101:
How do I get my note into recovery mode? I flashed the Rocket Rom but it won't get passed the loading screen. How do I boot in to recovery mode?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] anandpo:
Keep Pressing power+ vol up+ home
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Pinnacle74:
How did you flash ROCKET ROM, and which version?

Did you follow the instructions in the OP in ROCKET ROM thread?

Also it can take quite a long time to get past the boot animation the first time...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Minimalcriminal:
http://xdaforums.com/showthread.php?t=1329360

i used method 2 : root+cwm , its simple and easy, follow the steps based on your kernel.. http://xdaforums.com/show....php?t=1331784

ROCKET ROM, use previous version before updatin to v21. There will be bootloop after FullWipe! So if you do a FullWipe, flash v20 (or other LA4-ROM) afterwards, REBOOT, then flash v21 without wiping anything!

http://xdaforums.com/showthread.php?t=1380284
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ranjan.alva:
Turn off your device by removing battery and put it back

Hold Volume up + home + Power for 5 seconds

and you can see recovery screen , then do a wipe/factory reset

then do a wipe cache

after that just reboot normally,

this time it boots up.
[Galaxy Tab 7.7 General] Dragonn90:
Hi,

Touchwizz is great but it's laggy, did anyone try to use the stock apk launcher from the xoom or the asus transformer?

I found an apk but the installation doesn't work :(

Ps: i'm not root
[Galaxy Tab 7.7 General] maconsultant:
Im curious about this too although i hate touchwiz... i would love to be able to get a stock build of ICS on the Galaxy Tab 7.7 and do away with touchwiz completely..

Sent from another Galaxy...

Tab 7.7
[Galaxy Tab 7.7 General] clubtech:
Not sure abut stock launcher but ADW EX is as smooth as butter. Give it a try.
[Galaxy Tab 7.7 General] Jade Eyed Wolf:
+1 on this one.

ADW EX is really fantastic!

The problem with TouchWiz is that it's much more than just a launcher; it affects the entire system from the way menus look, transition effects, the buttons at the bottom, etc.

If you really want a stock Android experience, we need someone to develop an AOSP ROM of some sort. Here's to hoping that the Cyanogemod team builds us a version of CM9!!!
[Galaxy Tab 7.7 General] Dragonn90:
I have tried, but it's like gingerbreab and i love the holo theme of honeycomb(and ics) (the transitions and animations)
[Galaxy Tab 7.7 General] kazuni:
ADW Launcher EX supports Themes, and in the market there are themes for Holo HC theme you mentioned.
[Kindle Fire General] CarpeNivem:
Firstly, I'm sorry for creating a new thread, but please know that I searched everywhere (here and around the Internet) first. I barely slept last night. I have read and read. I'm still stuck.

I was able to root following these instructions - http://xdaforums.com/showthread.php?t=1410223 - and all was good for a little while, until I made a bone-headed mistake in the File Expert app while trying to install Google Market. I changed the permissions to /system/app and I'm sure that if I was able to change them back, I'd be fine. I just can't figure out how to do that.

What I can do is connect to the device via ADB, but if I go to adb shell, the prompt is a $. As I understand it, I need that to be a #. I can't get a # prompt, because when I run "su", I get an error that says "Segmentation fault su". (Sometimes I get a different error message, but I'm sorry, I forget what that is right now.)

Anyway, so because I'm not superuser, when I attempt to run "chmod 755 /system/app" (which is what I know I need to do), I get an error "Unable to chmod ... Read-only file system."

In order to get around that error, I know I need to mount as readwrite. However, when I try to run "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system", I get an error that says, "mount: Operation not permitted."

No doubt, I cannot chmod or mount because I'm not su. In an attempt to regain su, I tried to run BurritoRoot2.bin again (I don't know if that makes sense, but I decided to try it anyway, because BurritoRoot2 is what worked for me last night, and everything really was fine until I messed up those permissions). Anyway, that was last night. Today, BurritoRoot2 won't work anymore. Now I get an error says, "android.util.AndroidException: Can't connect to activity manager; is the system running?"

Well, no. The system is not running. That's sort of my problem.

I have no idea what to do now. I do not have TWRP installed. If I did have that installed, I might be able to flash a completely stock 6.2.1 or 6.2.2 ROM, thus restoring everything to "out-of-the-box" condition, which would be fantastic right about now. I don't know if I can install TWRP at this point, however, since my access to the device is so limited.

PLEASE help me... Where, exactly, should I go from here?

(Thank you for reading this. I'm sorry it's so long; I wanted to be thorough.)
[Kindle Fire General] b63:
you have to install fff and twrp therefore you have to get to fastboot:

http://xdaforums.com/showthread.php?t=1414832

then install twrp:

download from http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img

install with:

fastboot -i 0x1949 boot recovery\twrp-blaze-2.0.0RC0.img

and reboot:

fastboot reboot

now you can flash one of the prerroted stock roms or cm7 - whatever you like

would not use the stock rom from amazon cause you'll loose fff, twrp and root
[Kindle Fire General] CarpeNivem:
Okay, so far so good! Thank you so much for that information.

It seems as if fastboot has been enabled without complication. I'm moving on now to the download and installation of TWRP and FFF. I'll let you know how it goes! :D
[Kindle Fire General] CarpeNivem:
Well, crap. Now I'm stuck at the yellow triangle and "press power button for recovery", except pressing power does not start recovery.

AND, I can no longer access the device via ADB. The drivers appear to be invalid now. :`-(

I'll be working my way through this thread now - http://xdaforums.com/showthread.php?t=1408056 - and again, will report back later.
[Kindle Fire General] b63:
you'll have to update the driver - some did up to 4 times to get the right driver for each boot mode

in short:

normal boot -> android composite adb interface

fastboot -> android adb interface

adb is'nt working in fastboot mode and you'r still in fastboot mode

once you got twrp installed correctly, the drivers updated and correctly recognized you can force to recovery mode:

fastboot -i 0x1949 oem idme bootmode 5001

fastboot -i 0x1949 reboot

btw. to get to twrp you have to press the button repeatently (not holding,not once) till the button gets orange
[Kindle Fire General] CarpeNivem:
After rebooting the Kindle several times, it is now appearing in Device Manager as "Android ADB Interface" (which, if I'm understanding your most recent post, is correct). However, it is not listed when I type "adb devices", so that's troubling. And, when I try to run the "fastboot oem idme bootmode 4000" command, I get an error that "AdbWinApi.dll is missing from your computer".

So far I've only searched the forums briefly, but that error seems to be related to improper drivers, which means I'm even MORE confused, since the drivers appear correct now. Well, they appear correct in terms of what I see in Device Manager. I'm still uncomfortable about "adb devices" not returning anything, though.
[Kindle Fire General] b63:
just updated my last post

got it - from where do you run the commands kfu tools folder or sdk ?

if you use kfu tools folder (would recommend cause there are all necessary files) then move kfu to something like c:\kfu - it don't like spaces in pathname
[Kindle Fire General] CarpeNivem:
ah-HA!! :D

Thank you. I was running the fastboot from "C:\Kindle Fire Utility v6\", which was clearly wrong. First I renamed that folder to C:\kfu\ and then tried from there (but I was obviously still misunderstanding your post at that point). THEN, I read your post again, and realized I needed to be in the C:\kfu\tools\ folder. From there, I ran...

fastboot -i 0x1949 oem idme bootmode 5001

fastboot -i 0x1949 reboot

...and I am now inside TWRP! It is working.

To be abundantly clear (for any others who many be reading this in the future), after typing those commands, the Kindle rebooted itself. I then waited a little while, and the green light changed to orange (I had tried waiting before, but nothing happened previously). Shortly after the light turned orange, the Kindle rebooted itself again (on its own). It was on that reboot that TWRP started.

And that's where I stand now. I don't have time to actually use TWRP at the moment, though. I'm going to have to come back to this later.

But thank you again SO MUCH for getting me this far. I might just be able to take it from here.
[Kindle Fire General] b63:
to get to normal boot once your finished maybe you have to issue adb commands since adb is working in recovery

adb shell su -c "idme bootmode 4000"

adb reboot

and:

glad to help ...

please mark the subject of the topic (edit first post) with [Solved]

good luck !
[Kindle Fire General] CarpeNivem:
HOT DAMN, I have a Kindle again!!

Alright, so once I had TWRP installed, I noticed there was a menu choice labeled "Fix Permissions". Since all I really wanted to do was undo the mistake I made with /system/app, I wondered if clicking that would do it. So I tried it.

When that finished, I connected via adb shell and checked the permissions on /system/app. They were still wrong. But, I also had a # prompt now, not a $. So then I thought, well, I bet I can use chmod now.

And I could! "chmod 755 /system/app" worked! At this point, I thought that might be good enough. I may not need to flash a ROM after all. I mean, changing those permissions is all I really wanted to do last night. Well, that and sleep.

At this point, I tried leaving the shell and running "adb shell su -c "idme bootmode 4000"" from cmd, as instructed, but that didn't work. It said "su" was not found. Hmm. On a whim, I decided to go back into the adb shell, and just type "idme bootmode 4000" right from the # prompt. It seemed to accept that. Then I typed "reboot" from the next # prompt.

The Kindle rebooted. At first, it went to the yellow triangle with the "press power button to enter recovery" screen. I didn't press anything. I just stared at it and waited. Eventually, it rebooted itself. On this reboot, it went to the Kindle Fire logo!! I wondered if it was working again, or just stuck back where I had been this morning. So I waited, tensely. I have mixed emotions about that logo animation now, ya know. ;)

AND THEN IT BOOTED TO THE NORMAL LOCK SCREEN!!! :D

AND THEN I SWIPED TO UNLOCK, AND EVERYTHING WAS JUST AS I LEFT IT!!! :D

See? I told you it was just those permissions. I knew it all along. ;)

Anyway, b63 is the best ever! Thank you SOOO much. If you're even in Denver, let me know. I owe you at LEAST a beer! Or if you have PayPal, seriously, I'll hook you up that way too. I really, really appreciate it!

(And... Original title edited. "Solved"!)
[Kindle Fire General] Daniel_Fate:
I tried following the fix but I am lost at the part that says:

then install twrp:

download from techerrata.com/file/twrp2/twr...e-2.0.0RC0

install with:

fastboot -i 0x1949 boot recovery\twrp-blaze-2.0.0RC0.img

and reboot:

fastboot reboot

I do not understand what that means. Plus, I now have the yellow triangle and ADB does not recognize my kindle.
[Kindle Fire General] b63:
that is normal - your kf should be in fastboot mode now - adb is'nt working here

regarding the driver you have to reinstall the driver at this point - in fastboot mode it should be "android adb interface" in device manager - here is how to do:

-Go to device manager

-right click on the exclamation mark kindle

-Choose update driver software

-choose browse my computer for driver software

-choose let me pick from a list of devices on my computer

-Then select have disk

-Then select browse

-direct to where you downloaded the usb driver

-Select ok and ok

then resume with the downloads and the commands
[Kindle Fire General] Daniel_Fate:
I just tried, that, but it said that the driver was the same one installed. Is there a different driver that I am supposed to be using? I selected the one I used to root it in my .android file. Is that the right one?

---------- Post added at 05:50 PM ---------- Previous post was at 05:43 PM ----------

Well, I think I just FUBARed it. I uninstalled the driver, reconnected, and not it is not letting me re install the driver because windows says its broken.
[Kindle Fire General] b63:
no it is'nt - let's start at the beginning and check the precautions:

1. it would be good to know on what computer you are (os/bit)

2. download last kfu from http://xdaforums.com/showthread.php?t=1399889

3. extract it to c:\ and rename from "kindle fire utility" to "kfu" that it is c:\kfu

4. the driver is now at c:\kfu\drivers\kindle - the file is android_winusb.inf

now you have all what you need

tell me if you'hv got it - i'll guide you further
[Kindle Fire General] Daniel_Fate:
AHA! I got it back, ill follow what you asked. I am running Win 7 64 bit.

---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------

Alright, I downloaded, unzipped, and renamed the KFU. I went into device manager and selected update driver software, went and browsed and selected the kindle folder for the drivers. It started to install, asked if I trusted this unknown source, then started installing. At the end of the install it said:

"Windows found the driver software for your device but encountered an error while attempting to install it.

Android ADB Interface

This device cannot start. (code 10)"

Now my kindle is tethered and on. The screen is just the static kindle fire logo. thoughts?
[Kindle Fire General] b63:
still trouble with the drivers - try to run install_drivers.bat from c:\kfu\

the status of the kf is ok on the logo - it's fastboot
[Kindle Fire General] Daniel_Fate:
Here's what I did:

Opened cmd

entered "cd c:\kfu\"

entered "install_drivers.bat"

A window popped up saying "Welcome to the Kindle Fire Driver Installer. This will

walk you through updating your Kindle Fire. Click Next."

Clicked next

Says "drivers were successfully installed on your computer: Androidusbdeviceclass"

Clicked finish

Went to device manager

Still have yellow triangle.

Am I missing something here out of stupidity/ignorance?
[Kindle Fire General] b63:
no - you don't miss something - it's allways a hassle with win7 espacialy 64 bit

try to unplug - replug
[Kindle Fire General] Daniel_Fate:
I unpluged, and replugged about 5 times, each time it came up as an unknown device. I then unplugged it, shut it off, plugged it back in, then turned it back on, and it became a yellow triangle ADB.
[Kindle Fire General] b63:
sounds not bad - let's test it:

you still have the command prompt open in c:\kfu\tools

issue the following command:

"fastboot -i 0x1949 getvar product" - it should return "kindle"
[Kindle Fire General] Daniel_Fate:
It says:

< waiting for device >

BTW me being a new user makes it so I can only reply 5 minutes apart.
[Kindle Fire General] wapbravo:
Hi guys,

I have done everything mentioned before. However, when I enter the command

C:\kfu\tools>fastboot -i 0x1949 boot recovery\twrp-blaze-2.0.0RC0.img

I get this error message:

cannot load 'recovery\twrp-blaze-2.0.0RC0.img'

I appreciate your help. I have also messed up the permissions on the KF.
[Kindle Fire General] ghaffaria:
my kindle fire not work!!!!!!!

I want root my kindle fire with "Kindle_Fire_Utility_v0.9.6" , so I follow this instruction:

theunlockr.com/2012/07/23/how-to-root-and-flash-twrp-recovery-on-the-amazon-kindle-fire

after

"Install Permanent Root with Superuser"

my kindle reboot and stop on default kindle logo...:rolleyes:

and I wait and wait, but nothing happened.

now what should I do?

1 week I search about this but I couldn't find any thing and any solution.

also after that my kindle not recognized.

please help me....:(:(:crying:
[HTC Sensation] ghosy:
Hello everybody, can anyone tell me how to use the tv out? What Kind of settings and Hardware I need?
[HTC Sensation] delacerda:
You will need an MHL adapter such as this one sold by T-Mobile. Pretty much plug-n-play.
[HTC Sensation] ghosy:
Thank you!
[HTC Sensation] akbisw:
I bought on from eBay $8 and it works ok. But HTC one is a lot better and reliable

Sent from my enhanced HTC Sensation XE
[Galaxy S II General] anshmiester78900:
Well to be straight on point i dont think we even have as mush as development as the previous Galaxy S1 . Just look at their android development thread and on the first page itself you can find 3 ICS roms . Two of them usable for daily driver , one is CM9 which is still buggy (So is ours ), I mean to say that we are dependent only on the CM9 team for the ICS and we dont have anyother dev to do that for us . :(

Your views ?
[Galaxy S II General] zabihjan:
simple reasong

samsung galaxy s2 is a perfec phone with perfect firmware.

reason ppl coming here is to change the looks and play around with their perfect phone when there is nothing else to do.

the reason for no ics is because ICS is still buggy on its own so there is no point making roms untill google fixes the base.
[Galaxy S II General] fred_up:
If you desporately want more ICS development, then get developing.

If I had the brains to do, I would do. But I don't, so I can't.
[Galaxy S II General] shotta35:
Its pretty hard to develop anything without code. :p They work with what they have and if what they have is crappy, so yeah. :)

The SGS1 is similar (or almost exactly the same) as the Nexus S so since source is out for that they just took some stuff there and used it on the SGS1. Makes it much easier. We don't have a phone similar to ours that we can borrow bits and pieces from. They tried that with the Galaxy 7.0 Tab Plus but didn't work out so well.
[Galaxy S II General] rj3005:
Actually this is the first Smartphone where I don´t feel the need to change much. It´s already damn good.
[Galaxy S II General] dumbdroid:
ICS is still buggy? I had daily drivers ics Roms on my nexus s backup in october!
[Galaxy S II General] DirkTeur Velserbroncx:
Same here best phone ive ever had so far, only things needed to change

where optical and removed the unneeded apps.

ICS seems nice once it's stable and bugfree untill then........
[Galaxy S II General] Sandman2749:
Not sure I would agree.

I am running the Simplistic ICS ROM RC3 as my daily driver. Everything is super smooth from my limited experience. Granted, these are based on Sammy leaks but it beats the deadlock I saw over on the RAZR forum.

Pretty happy overall.
[Galaxy S II General] BigMrB:
Very happy with my current rom, so yes I am happy overall with development
[Galaxy S II General] blunted09:
Nothing really I would change. Even with ics out, I prefer the majority of stuff touchwiz has. Simple tweaking is pretty much it.
[Galaxy S II General] anshmiester78900:
Common guys i think ur not getting me i mean to say that we have less developers
[Galaxy S II General] wurzelsepp3:
I think it's because the original Galaxy S is older and developers have more experience with the hardware. For example it took almost a year before Cyanogengenmod was available for the Galaxy S.
[Galaxy S II General] adamski123:
I have to agree with the OP. Seeing as a galaxy s2 is such a popular phone u wuld expect more aosp roms for ics :L

sent from my iPhone 4S.

haha I bet that confused ya ;)
[Galaxy S II General] anshmiester78900:
Damn and they got ICS so easily ? :eek:
[Galaxy S II General] buzzboy:
I tend to agree, the Original Galaxy is more established.

The trouble is, the S2 is sandwiched between the Galaxy S, and The upcoming S3. (Stuck between a rock and a hard place)

A lot of Devs and Users will no doubt be waiting to upgrade to the S3 upon launch, and maybe leave the S2 in the shadow somewhat.

Also unfortunately I would imagine a lot of Developers are staying away, considering some of the Flaming that happens on here.

We shall see. But Overall I'm more than satisfied with the Development.

Regards
[Galaxy S II General] Entropy512:
Judging the level of development of a device just based on ICS is utterly stupid - did you look at all at the Gingerbread development that happened on this phone?

ICS for the original Galaxy S is a FLUKE. It's almost unheard of for an AOSP bringup to succeed on a higher version of Android than what is released for the phone due to lack of compatible binary blobs for vendor-proprietary parts.

The Galaxy S is lucky and VERY unusual - it has a high number of hardware similarities with the Nexus S, which is by its definition, a phone that has as many components open-sourced as possible. As a result, much of the Nexus S source code was adaptable to the Galaxy S as part of the CM7 bringup process.

The I9100 doesn't have this hardware commonality with a Nexus device. The RIL architecture and interfaces are completely different, the GPU is completely different, etc.