yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
You flashed a JB kernel? Flash an ICS philz kernel to get it to boot up. Or install the rom again using Odin.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] BTICETeKS:
It was? Oh my God I should've looked it up...so that's why.

Where can I find the kernel that's fit for mine?

Sorry for my carelessness.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] forest1971:
Look for it from Philz kernel thread in Original Android Dev section.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] BTICETeKS:
But how do I know which is for my phone?

I don't understand how can I pick the kernel.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
In Philz main thread there is a topic "Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99:"... these are 4.0.4 Kernels.. Try one of these and check if the phone boots up..

OR

As you have already done wipe data, you may also install a new custom rom like Aryamod...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ThaiDai:
You wrote that you just got the Note.

So why do you want to stay on ICS and try to install things you obviously do not understand - and risking your device?

Select an JB or KK Custom Rom, follow the specific installation instructions and be happy with your new-born device.

---------- Post added at 12:54 PM ---------- Previous post was at 12:52 PM ----------

Maybe two posts with the same intention will convince him...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
You know the drill....
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] BTICETeKS:
Hmm...

I do want to install CyanogenMod...

Will the latest stable release be compatible with PhilZ?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] forest1971:
Go read the instruction from the rom thread that you want! better stay stock if you don't read or don't understand.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] BTICETeKS:
Thanks. I'll have a look at it.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] BTICETeKS:
So I downloaded the stable version of CyanogenMod: "cm-10.1.3-n7000.zip"

Is it compatible with the recovery I have?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ThaiDai:
start reading and understanding the instructions yourself.

spoon-feeding a lazy baby. for my part I quit here.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] BTICETeKS:
Yeah, well, sorry.
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
Currently S-OFF and UNLOCKED.

Just ran a 4.4.2 RUU via zip, rom is back to stock, but recovery isn't working, red triangle.

When I try to flash the firmware.zip, it returns

I also tried extracting the boot.img and recovery.img and flashing them separately, but I still get the red triangle when trying to enter recovery.

Need to return my HTC One to 100% stock to fix the purple camera issue, tried everything I could find, please help!

(Warranty expires in a week)
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
An RUU.zip has to be run as follows, not from recovery

Make sure the RUU.zip is in your adb folder.

adb reboot-bootloader

fastboot oem rebootRUU

fastboot flash zip ruu.zip

Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. *You have to issue the exact command again:

fastboot flash zip ruu.zip

The green status bar usually does not reach the 100% mark. *When the output in the command window is complete, you can reboot:

fastboot reboot

PS the red triangle is stock recovery

(Power button + volume up to enter recovery ).
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
PLZ HELP

Just tried running both the firmware.zip and ruu.zip flash commands twice, same result!

Still can't return to stock recovery(the really simple one).

Current specs:

Names of the files I used

firmware.zip [MD5：19c0fd52eb90d6e60ff2a6e9c1ee035a]

RUU_M7_U_K44_SENSE55_MR_hTC_Asia_TW_4.20.709.14.zip [MD5：04110c3e9152faf91ba661e68b34ec42]
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's

Why was you trying to flash a firmware.zip.

Also if your trying to return to full stock for warranty purpose, your phone needs to be locked not relocked and you must also remove tampered.

Follow this guide to achieve this

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

And also look here for stock rom

http://www.htc1guru.com/guides/return-stock-guide/
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
I'm trying to flash a firmware.zip because I failed at flashing the stock recovery individually.

Commands... I used just the usual ones, but tried them all at different states: LOCKED, RELOCKED, UNLOCKED...

fastboot flash recovery recovery.img

fastboot erase cache

LOCK/UNLOCK from this thread: http://xdaforums.com/showthread.php?t=2475914

Also this corrupted data partition thing by Mike of ARHD: http://android-revolution-hd.blogspot.tw/2013/10/fix-data-htc-one.html

fastboot getvar all

I can successfully flash TWRP recovery, but no luck with any other stock recovery...

(flashed the extracted boot.img from the same firmware.zip before flashing the recovery.img)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
That is the stock recovery!!
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
Isn't it supposed to be a very simple menu?

If it is stock recovery, how do I use it? I tried pressing POWER+VOL_UP as mentioned above but it just kept rebooting!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
stock recovery:

to get to this menu:

you need to briefly press POWER + VOLUP (or POWER+UP+DOWN), you may need to try a few times to get the timing correct.
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
Thanks I just looked it up and it's working. It was correct the whole time, I went full retard.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
no problem :)
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
When I reboot, I get a black background with red HTC and white text, and then I get the usual boot animation(with sound).

Is the first part stock or custom? Can't remember if I modded it...
[One (M7) Q&A, Help & Troubleshooting] bored_stupid:
Can you post a pic of the screen.

Did you follow nkk71's guide for returning to full stock?
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
Here's a video: http://youtu.be/jUMIhA_mKE4

I had to downgrade my hboot from 1.56 to 1.44 to get S-ON, I suppose I should upgrade it to the latest version so it matches everything else?

Edit:

I followed this guide: http://www.htc1guru.com/guides/return-stock-guide/
[One (M7) Q&A, Help & Troubleshooting] nkk71:
that video show's correct (stock) bootup and powerdown animations, but a (

possibly

) modded bootsplash.... that would be partition mmcblk0p13 and can't be flashed without S-Off

though an RUU should have taken care of that!!

PS: I say possibly, because maybe your version (HTC__621) is supposed to be like that.
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
I ran the RUU via zip not exe, maybe that's the issue? I think I'll have to S-OFF again to fix it...

And the hboot part? Should I upgrade it to a matching version for a valid warranty?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
doesn't matter if it was a ruu.zip or ruu.exe both would/should change the bootsplash... can you check the zip if it has "splash1.nb0" that would be the bootsplash.

ruu (zip or exe) contain everything so hboot and bootsplash should already by stock.

maybe it's just supposed to be that way for you??
[One (M7) Q&A, Help & Troubleshooting] theplaypig:
Checked the RUU zip and it doesn't have the bootsplash, a simplified version of RUU I guess...

So I decided to run a RUU exe, which should be more complete and thorough, 100% back to stock.

But since I couldn't S-ON yesterday, I downgraded my hboot from 1.56 to 1.44 (I thought upgrading it back to 1.56 would be simple).

Now I can't get S-OFF to run the RUU exe(can't use revone because it doesn't work with my version of something),

and some things don't match when I try to run it with S-ON.

I can't find any newer version of RUU or the latest hboot for download.

Overall, I ****ed up pretty bad and I think I'm about to send it back regardless of warranty...

Returning to stock is a lot harder than I thought, all this time put in to fix the purple camera thing...
[One (M7) Q&A, Help & Troubleshooting] antchang:
playpig, i have the exact same fone as you and i also want to unroot my fone. can you please tell me where you found the stock recovery and how u unrooted your fone? thanks in advance
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
I've tried a bunch of tutorials on here to fix this, but can't figure it out.

I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.

I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?

My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.

Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.

The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.

I'm at a loss. Please help.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Now I'm all screwed up. Before I saw this message, I restored my Kindle back to when it was still running the factory default OS with root, then I shut it down to enter TWRP, and it appeared on its own, but it was installing some sort of update... and when the Kindle's factory default OS appeared, my root was gone. Now I am stuck on the factory default Kindle HD 8.9" on System Version 8.4.8. Man, I should have never accepted that update and just left it as it was. Ugh. Well, for right now, there's an entry in my Device Manager that says "Kindle Fire" and when you click the arrow to bring down the submenu, it says "Android ADB Interface." The Kindle is now working when connected through USB. Now... how do I go about rooting this thing and getting TWRP on it again, because it seems the entire thing got erased. Not having my ROM installed on this thing makes it mostly useless to me. :(
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
I can't find anything. Download links are dead for KFFA. You have a link to get it through another source?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
They are up and running when I click em. You were on this thread right?: http://xdaforums.com/showthread.php?t=2096888

If that doesn't work you can always use binary's root.

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

Use the old normal method if I remember correctly.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Nah, the link is dead here. Says the file was removed. There are other members in the forum asking as well for a new link.

I managed to get ADB working, and in Device Manager, I have "Android Device -> Android Composite ADB Interface."

I open CMD and type "ADB" and it scrolls a bunch of stuff, but when I type "ADB Devices" I get a list with nothing there. It's just blank.

I tried using BIN4RY Revision 33, using Option #1, but it just keeps bringing me to a "Path not Found" error of some sort.

It looks like all I need to manage to do now is get ADB to list my Kindle device before attempting the ROOT, but how can I do that?

I still wanna give KFFA a try, but no downloads anywhere, and I don't trust random 4Share and the likes, not that it's gonna fix my problem.

I'm close... I just need this damn ADB to list my Kindle device and I think I'll be okay.

Also, I want to say thanks for the help you've given me so far. It's greatly appreciated. :highfive:

i.imgur.com/gZrrqXm.jpg
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
No problem, i like helping people fix things.

Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Unfortunately, that didn't work. I'm pretty sure one or more of my drivers are interfering with the connection to the Kindle, but this is such an old OS with so many drivers, it's hard to tell.

Right now, I have a Virtual Machine of Windows 7 up. I plugged my Kindle in and I can instantly see it. I can even enter the internal storage! I'm currently installing the Android SDK for the ADB after installing the Java SE x86 version. Once I get ADB on it, I'll see if it lists my device now. Seems promising since the VM sees and allows me to already enter the internal storage, unlike my original Win7 OS.

EDIT #1: Great news! ADB now lists my device! Thing is... Root with Bin4ry Revision 33 does not seem to want to work. This is what I get...

It doesn't give me a chance to do anything. All of that pops up as soon as I press enter. ADB and third party software is enabled on my Kindle. ADB even reads my device as:

I'm at a loss now. Any ideas?

EDIT #2: Success! The issue was I was using Root with Bin4ry Revision 33. I should have been using Root with Bin4ry Revision 30. That worked, and I am now ROOT. Mission accomplished. Now the next part of my mission... figuring out how to get TWRP on this thing.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://xdaforums.com/showthread.php?t=2128175

Everything seemed to work until I get to Step 3. I'll enter the commands but it tells me that there is no such directory or something. Something about there not being any "stack." Can't recall. I wanted to ask on the thread there but the site isn't allowing me to post there.

adb push stack /sdcard/ is where the issue occurs. Everything else worked.

I'm at a loss, and the comments don't seem to help on that thread. Please tell me there is an easier method of getting TWRP on this thing.

ERROR:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
That tutorial is for the 8.9. You want the tutorial for the 7". http://xdaforums.com/showthread.php?t=2218796
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
He's on a 8.9", he just posted in the wrong section. Use the fireflash method from seokhuns tutorial, just don't forget to check the box with red text near it or you will get a nice redscreen brick. Lemme grab a link

Edit: link grabbed! http://xdaforums.com/showthread.php?t=2277105
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
I used FireFlash, followed the instruction... now I cannot get passed the first "Kindle Fire" logo when I turn the Kindle on. It just freezes at "Kindle Fire" as soon as I turn it on. I can't seem to do anything at all, and it won't connect via USB. Any ideas?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
It's not working... it won't read at all. Device Manager doesn't see the Kindle at all. And yes it is 8.9". I think it may be bricked now. ;'(

And all because of that stupid update... ughhhh. Sucks!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
I switched over to my main Windows 7 OS and did what you said. I connected it and it showed for a brief moment in Device Manager, so I quickly loaded the driver and updated. But wen I type the command you gave me, it says <waiting for device>, so I plug it back in and... nothing. At all. Just sits there at <waiting for device>

I'd try Linux, I have several copies of different OS's, but I'm not very good at working with it or using Terminal... I can try that though, but no clue how I'd get ADB or the Kindle to read on it. :\

And yes, 100% it's the 8.9". The resolution is 1200p.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
OK the command has to be run while the device is off and disconnected, once it says waiting for device, plug the kindle in and it should work if the drivers are working. Linux is really easy to use with a kindle, it has the fastboot and adb drivers built in natively, only thing you need is the fastboot command from the Ubuntu repos if you are using Ubuntu, believe they were added to the repo in 13.10.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Well I would definitely try... but there's now a new issue. Kindle will not go on. At all. Completely shut down. It just gave up. I can't power it on at all. I know there's no coming back from that. I'm going to see if Amazon will replace it. Unless you know of another idea to get this working. I'm pretty sure I lost this baby though. :(

Thank you for being committed in helping me out. I guess something was just wrong that we couldn't control and it just crapped out. RIP Kindle Fire HD. And all of this started because of that stupid update I got for CyanogenMod! Err!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
You sure the battery didn't just die? I mean without you flashing anything chances are the battery is just dead.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Yup. Was on 80% juice last I used it and left it on the charger overnight. It crapped out. Amazon said they will send a new one though for free to replace this one. They said I am guaranteed to get it by the 27th. When I get the new one, would you like to walk me through it if I end up with an issue again? You've been a huge help.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Sure I will help if I can, I finally landed a full time job, if everything goes as planned i start orientation on the 16th, so hopefully before then.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] GogoplataMMA:
Never mind, we're all good. New Kindle rooted and flashed perfectly. Only took 10 minutes before I had the Kit-Kat mod on it. My old one must have just been messed up somehow. It took some work, but I went now from CM9 to CM11. I created a backup after installing all my main apps and choosing my settings, so if I ever have to flash-fix the Kindle again, I'll just boot back to the CM11 with all my pre-installed apps.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Good to hear it is working then.
[Galaxy S 5 General] ecopy:
11. pull the status bar ftom the top with two fingers instead of one, and you'll get the pane with all the quick-buttons.
[Galaxy S 5 General] THFourteen:
Heh this was the most useful tip for me and not even part of the OP :D
[Galaxy S 5 General] BigBugHmb:
But it's not new… The two finger status bar works here on Huawei G700 with Android 4.1.2 too. It's not a Kitkat feature.

--

best regards / MfG

René / BigBug(Hmb)

(mobile talk with Tapatalk 4)
[Galaxy S 5 General] dragon135:
Swipe down from top in anywhere will show status bar and you can drag it to see notification.

Sent from GT-I9500
[Galaxy S 5 General] simacca:
What about the text delay option? When you send a text message you can put a delay on it and cancel it before they receive it. Great for drunk texting ;)
[Galaxy S 5 General] Crafty77:
Original list is from this article : http://phandroid.com/2014/04/18/10-hidden-galaxy-s5-features/
[Galaxy S 5 General] ShadowLea:
Uh, technically this is the original source: http://global.samsungtomorrow.com/?p=35885
[Galaxy S 5 General] eyecon82:
awesome..never knew that one!
[Galaxy S 5 General] hemander:
I don't know this. Thank you so much. This is useful. :laugh:
[Galaxy S 5 General] polish_pat:
By hidden, you must mean right there in plain view...i knew about all these features just by using my phone normally. I would consider a hidden feature the flashlight samsung always put but we cant use for some stupid reason, or developper mode that can be activated by clicking 5 time in build version
[Galaxy S 5 General] shebi:
hmm learnt a lot :)

never knew many features from above ...
[Galaxy S 5 General] big samm:
How to use this feature?
[Galaxy S 5 General] eyecon82:
It's in the message app settings

-Sent from Tapatalk
[Galaxy S 5 General] lurch0101:
came to say the text delay feature is pretty neat...probably have seen all other features elsewhere at one point or another.