[Q] App/Tweak to force reboot - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi, I'm new to this whole android thing. I got a Kindle Fire HD 7" it's rooted with SuperSU and Google Play store on it successfully!
My main issue is it seems many tweaks like a reboot after installation, but my power button is completely missing. I can plug the device in to turn it on, and open/close the cover to put it to sleep.
Are there any tweaks around where I can like slide to power down, or force reboot how you would if you were to press the power button?
Alternately, I'd also like to remove the ad lock screens and potentially install a live wallpaper on either the lock screen or the home page. And maybe have an actual android grid set up. I know you need a secondary launcher to do this kind of thing, but all the ones I looked at screamed brick, and I got a bit worried. Could anyone point me at some basic tutorials? (I've jailbroken my Ipad rather extensively, but this seems to be a bit more in-depth to the actual operating system)
ETA: I haven't Used QMenu Just the ABD Drivers and the Root_with_Restore_by_Bin4ry_v33

If this is the 2012 model with a camera you can flash cm 11 on it and use maromi's kernel, it has double tap to wake, and cm also has double tap corner to sleep.
There are apps in the Google play store for rebooting methods that I believe allow for reboot normally as well as to fastboot and recovery, I know CM's built in power menu has those option if you enable them, but then there's the issue of getting to them with a broken power button.
Sent from my Amazon Tate using Tapatalk

It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.

Dovetail said:
It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.
Click to expand...
Click to collapse
hehe wow this is a first, ok cm 11 is cyanogen mod 11. its a rom you can flash instead of amazon's original os, it is way faster and more up to date and is more like pure android. Flash basically means we are overwriting the system files and such that came with the device. It can have any launcher, set wallpaper, is already rooted and has alot of cool things like themes and performance options you can set, much better than stock amazon os. You seem quite new to the concept of flashing a rom though so i advise you to read the tutorial thouroughly and as long as you don't mess up you shouldnt need a fastboot adapter even though its always advised to have one anyways. Heres a link: http://forum.xda-developers.com/showthread.php?t=2271909
Let me give you some advice so you don't end up with a red screen brick. Make sure when you follow this that when you see the red text at the top of fireflash(you will understand this when you start this part) that you check that box off thats either to the side or above the red text, this is a vital step you must follow or you will need a fastboot adapter to fix. I also recommend grabbing the cm rom and its corresponding gapps ahead of time.
Feel free to ask questions.
Also if you install a launcher on amazon os you will need root and you must copy and paste the app into the system folder and set the permission to a certain way or it will bootloop. I think titanium backup has a convert to system app button that does it for you. Wallpaper doesnt defaultly work without my fix either.

Nevermind, it finally worked

stunts513 said:
Feel free to ask questions.
Click to expand...
Click to collapse
Thank you so much for being patient with me!
I had been doing the app thing, but it seems like such a pain to do that with every app. I removed the installer, it wasn't doing much of what I was wanting anyways, the CM11 sounds much more like what I'm wanting to get to.
I'll give the tutorial a good read through and update this post with any questions I have!
Question 1: "commonly associated .... higher without first flashing the Amazon OS 7.2.3 bootloader" With flashing the cm11 do I need to (or do you recommend I) first restore or go back to the 7.2.3 or can I continue with 7.4.8? I will obviously be making backups as it seems that's the only way to recover with a standard usb cable.
Question 1A: If you are NOT on the 7.2.3 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 7.2.3 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on. Is this the box you mentioned? It seems like this saves the hassle of going to 2.3 THEN flashing.
Question 2: "Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry," I used this method in the first place. I had some issues with the ABD drivers not being recognized but got them working when I used amazon's direct ones. Furthermore, when I did get rooted (I used an app to check that it was and since nova worked I assume it was correct) superuser wasn't installed. I went and installed superSU manually. will this be an issue? (things have asked for and been granted permission and show as such in the superSU app)
Question 3: I'm using my work computer which runs through a server. when I go to back up through cmd it says the folder will be in C: and to then transfer it. The server shouldn't matter, right? I guess I can always just do a search for the file name and it'll turn up somewhere.
Question 4: Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP I did find an app called "reboot" which allows me to reboot (shocking!) without the power button. Can I still use that app at this point?
Question 4A: Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache.After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot This section calles to wipe some sections, will this also wipe my apps? it calls later on to reboot again. If the first bit wipes the apps, then I wouldn't be able to reboot at this point. (aside of waiting for the battery to die)

Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thank you so much again! I'm excited! I'll let ya know how it goes.

Sweet and I thought I'd mention if you get confused on what cm 11 build to download, the unofficial builds are a little bit more dated now that the device is a officially supported cm device, I recommend the link that isn't under mirrors that goes to cyanogenmod's Tate download page. The URL has those 3 words in it so you will know it when you see it. The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon, the cool thing is whenever a update is available it can ota like a phone, I believe it will make you choose to install the update though. I was impressed by how it updates, just seemed cool to watch. Not positive if cm's updater notifies you when updates are available though.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon
Click to expand...
Click to collapse
Firstly, when I go to back up through the command prompt I get this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\admnasst>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot
0block.img"
'adb' is not recognized as an internal or external command,
operable program or batch file.
Am I missing some step? I do have ABD enabled on the kindle.
Secondly, on this site: http://download.cyanogenmod.org/?device=tate
am I wanting the download second from the bottom that says "snapshot" and ends with m6-tate
I would figure so, but I wanted to double check.

Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk

stunts513 said:
Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I ran the first line and it started. I'm going to do everything tomorrow when I have more time. I'll keep you updated! Thank you again for helping me, and being so welcoming.

https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot this was my favorite reboot app and it works well although I see your doing the custom ROM thing now.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

ROM toolbox has a quick-reboot option that is similar to respringing iOS, and it well let you create a launcher shortcut on your home screen.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<

Related

It is simply ridiculous that HALF of the Nexus One RAM is unusable in stock...

...so I am compelled to root. ALL I care about is unlocking that other 256 (himem, I think it's called) for use and apps2sd would be nice but not necessary. Any other practical enhancements would be welcome. I'm using build ERE27. So which ROM fits that description best and where are the easiest instructions with links to download? I have been all over this and other sites and there are so many tutorials and none seem identical. Try Youtube and you know what you get? The most popular root tutorial (by far) flat out tells you from the start "This is not for beginners". Well, where the **** is the one for the beginners? I've jailbroken Iphones and flashed ROM's on to WM devices but I've never seen a more convoluted method to implementing a ROM replacement for a phone. Step by step (with backup reminders at critical times during process) would be great.
For example (from CyanogenMod):
Before continuing, you should first copy all the necessary files to your SD Card. Doing so will make the entire process much easier and faster.
Files you will need:
Download the latest release of CyanogenMod for the Nexus One and the Google Addon from http://forum.xda-developers.com/showthread.php?t=623496
Download the latest release of Amon_Ra's Nexus One Recovery Image from http://forum.xda-developers.com/showthread.php?t=611829
Rename Amon_Ra's recovery file "Recovery.img", and copy all three files to the root of your SD Card
Click to expand...
Click to collapse
I'm sorry, did you not just provide me with 2 files to download? Where does the third come from? And why does every "Link" lead to a full page with 3700 more links rather than just a freaking file to download??
Even Droiddog uses a Mac during the process because a PC would have been far too convenient for the masses (Plus I don't want the Desire ROM-too borky).
Preparing myself beforehand (going through the motions of the root without rooting) led to me opening 7 windows instead of direct file downloads. 7 Windows. 7. Does it really have to be this arduous?
I'm sorry for the frustration but deciding to root was suppose to be the hard part. Now I'm just overwhelmed with the unnecessary difficulty of it all. In truth, I'll probably be posting "thanks" from a rooted N1 by tomorrow and wondering what was so hard about all of that.......or I'll be crying over a $530 brick in my hands.
I believe Cyanogen mod (latest version in the link) includes the himem by default, just install that and you'll get the more available RAM (unless there is more steps to the process), I do not use Cyanogen.
Please note this is not the iphone OS we are dealing with here, things will not be as simple as a button press.. I honestly do not know what a "noob guide" is when it comes to Android, it all seems so straightforward to me... If I rooted my G1 and I'm only 13, not even being a nerd at that (wouldn't care if I was though..), I would imagine it not being hard for anyone..
At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?
DMaverick50 said:
At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?
Click to expand...
Click to collapse
Choppy scrolling is just that launcher2, and has nothing to do with the actual phone hardware which is a good thing. I went back to an older 2.0 launcher that is MUCH MUCH faster with continuous scroll.
I will switch if continuous scroll is added to launcher2, but yeah that choppiness stinks
It's a bug the iPhone had its bugs too. One of the great things about rooting your phone is not having to wait for Google to fix bugs the devs here do it nice and quick. I waited a month then rooted my phone and I am happy I did.
Prod1702 said:
I waited a month then rooted my phone and I am happy I did.
Click to expand...
Click to collapse
Does the extra 256 of ram make a noticeable difference in the overall speed and experience of the device (you should know having gone a month with stock on it)?
I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.
jz9833 said:
I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.
Click to expand...
Click to collapse
Is this true?
CM mode unlocks a good upgrade portion of the ram, for example with 10 apps Open I used to have 60 or less MBS left of ram, after CM upgrade with Kspec theme, i have 10 similar apps open and have 200+mbs of ram left, dont believe me? I actually made a video while still pretty shocked, check it, might as well rate and sub. I think I had 230+mbs while 10-12 apps running
www.youtube.com/user/exclusivegslick = my only video.
Ok to answer a few of your questions:
Does CyanMod include more ram? YES. This bump up in ram is included in the Kernel, and all of the newest roms have this including the undervolted/overclocked kernel's as well.
You get about 400mbs after the free up.
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Ok here is a quick summary that will hopefully help the other guides make more sense. USE THE OTHER GUIDES STILL this is a conceptual map.
1) Install Android SDK to your COMPUTER which gives you ADB and the windows drivers. The drivers can also be downloaded via another thread. Search drivers/sdk drivers/adb drivers etc..
2) Download/install Fastboot to your COMPUTER
3) Download Amon Ra Recovery 1.6.3 to your Fastboot FOLDER on computer
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
*This gives you all of the proper stuff. Make sure you get ADB SDK drivers loaded I stumbled here and wasted a couple of hours*
6) Unlock bootloader via fastboot. This is a command given from your Computer in DOS prompt in the folder you created with fastboot stuff. Your phone is connected and you are in the BOOTLoader. READ the guides for exact directions or the androidandme video, or countless other things.
7) Install Amon Ra's Recovery while still in FASTBOOT from a command via your computer. Follow guides or even first post on Amon Ra's Thread.
8) Now that you are unlocked. Go into RECOVERY which is done via the bootloader. Guide will give exact direction.
9) **** MAKE A NANDROID BACKUP **** just get in the habit. It is your FAIL SAFE. This in theory makes a nandroid backup of your "stock but unlocked" setup. I always "RE" nandroid backup before making changes or when I "Like" my setup. Command is in recovery.
10) WIPE data via recovery command.
11) FLASH from ZIP - pick Cyanogenmod5.0.4.1 (file you dl'ed to your sd card)
12) Flash from ZIP - GAPPS(googleapps) (file you dl'ed to your sd card)
REBOOT the phone. VOILA. Your done.
Important notes. If you decide, IFFFF, to update the radio. NEVER EVER EVER EVER pull the battery. MD5CheckSUM the radio download. and Repeat NEVER EVER EVER EVER pull the battery until the radio is entirely installed. It can take awhile. This is how you BRICK your phone.
Anyways. that is a real high lvl overview but maybe puts things in perspective easier.
btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.
britoso said:
btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.
Click to expand...
Click to collapse
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\
I know what you mean with the "this is not for beginners", it was annoying because, even cyanogen had to unlock his first android phone some time. I followed that guide anyway, after doing as much research as possible. It didnt work though, i could not go straight from unlocking the bootloader to installing amon_ra's recovery, i had to install superboot first. I was hoping for a 30 minute root job, but it ended up taking about 4 hours all up.
I think the stock android kernel is .29 Which only recognises 256mb ram, cyanogen's mod is on the .32 then the .33 kernel which is a highmem kernel, by flashing cyanogenmod you are automatically unlocking the extra ram, no other work is required.
Also, i would suggest sticking with the ERE27 radio, i personally have no problems with reception with it, also if you don't flash the radio, your chances of bricking your phone are very very very low. If you want to do the radio, you can flash it later, when you are more experienced.
seanowns said:
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Click to expand...
Click to collapse
I downloaded the Android SDK
2) Download/install Fastboot to your COMPUTER
Click to expand...
Click to collapse
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
Click to expand...
Click to collapse
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
Click to expand...
Click to collapse
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.
whodatfever said:
I downloaded the Android SDK
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.
Click to expand...
Click to collapse
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!
Gr8gorilla said:
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!
Click to expand...
Click to collapse
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).
addon - vs mod
whodatfever said:
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).
Click to expand...
Click to collapse
The add-on was what Cyanogen made before google released the source code for android 2.1. It is not a full custom rom.
The ROM's ie. 5.0.4.1 is all the Cyanogen tweaks, highmem etc. 360 degree rotation (left right and upside down if you enable it) and all sorts of stuff.
You really should try both radios and see which one works better for you. Some people have better results with one and some the other. I have the best continuous 3G/HSPDA signal with the ERE36B radio.
On Cyanogen mod forum, go to nexus one and there is a link to get the latest stable ROM 5.0.4.1 that is what you want. You have to also download the Google add-on.
Cyan used to include them but got a nice letter from google telling him he was not allowed to "optimize" their stuff. So he puts it in a separate package as is, and you have to flash it after you flash his rom to get the google apps.
Google apps will be called: gapps-passionERE36B(2) or something very similar.
I am willing to answer any questions you have just send me a pm.
andythefan said:
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\
Click to expand...
Click to collapse
there is a thread here about your warranty and as long as you have a problem that is a legit hardware defect HTC has been replacing them, dust under screen bad battery, and a few other things.
GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.
whodatfever said:
GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.
Click to expand...
Click to collapse
Remember if and when you flash the radio, plug in phone, and whatever you do, do not pull the battery while it is doing the radio. That is the biggest NO NO. It can make a nice nexus One paperweight. As long as you dont pull the battery you will be fine. I have flashed mine about 4 or 5 times....and I have flashed roms about 1000 times.
The phone is going to reboot a couple of times during a radio flash, be patient.

[Q] Any changes to the sdcard files will not take

editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more

[REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial

Disclaimer: By following this guide, you understand and accepts that I, and any developers mentioned in this guide, will NOT be held responsible in the event that your device stops functioning or dies. While I try my best to make everything as clear and concise as it can be, accidents will happen should you not follow everything like a hawk.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial​
I'm going to lead you through installing Hashcode's 2nd-Bootloader and TWRP in order to start flashing custom ROMs and make backups. First, let's go over the basics and why I'm doing this in the first place. I wrote this guide to be used on a Windows computer, but as long as you can do the same things on Mac/Linux, the whole guide applies. If there are any issues, please first refer to the troubleshooting portion at the end of the guide. The 8.9 version of the device does not need the factory cable to enter fastboot mode.
+Note: As of Amazon OS update 8.3.1+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 8.3.1 or higher, please proceed with caution. I strongly recommend you make backups in Step 2.
===== 1. Why do we need a 2nd bootloader? =====
The stock Amazon bootloader doesn't play nice with Android even though it has Android at its core. We can still use fastboot commands with it, but other than that, it's quite locked-down. In other words, normal exploits used to unlock the bootloader on other Android devices, for example, like the Nexus series by Google or the handsets by HTC don't apply here. In order to use the same features, like a custom ROM, custom kernel, custom recovery, we must bypass Amazon's software by installing a 2nd bootloader.
===== 2. Why are you posting a tutorial? =====
I'm doing this because the lack of a guide means that people like myself, who are not proficient developers, keep running into issues and some ended up bricking their devices. This means that they end up with a heavy paperweight, with no chance of fixing, other than hoping that they're lucky with a fastboot cable (not the one that came with the device) and find their way back to the beginning. I'm sick of seeing so many questions about the exact same issues so I thought, why not just make a guide everyone can follow and thus make the world a better place.
===== 3. Do I need any special equipment/knowledge? =====
You don't need any special equipment, provided that you follow this guide word-for-word and be careful. I successfully installed the 2nd-Bootloader + TWRP and flashed CM10.1, within minutes. The key is make sure you don't miss anything, and if you're not sure, don't make any random guesses. As far as knowledge, yes, and no. Know what you're dealing with. Anything underneath the ROM has the chance to brick the device, so know what you're getting into.
===== 4. Can't I just use FireFireFire or another automatic tool to install the bootloader + TWRP? =====
Definitely not. This is the exact reason why there are so many threads in the Q&A section about bricked devices in the first place. Never use a tool that wasn't made for the version of your tablet. The Kindle Fire (1st gen), the Kindle Fire 2 (2nd gen), and the Kindle Fire HD 7" & 8.9" (3rd gen) are not the same devices, at all. Due to the way the bootloader behaves, flashing the files that are only compatible for the Kindle Fire 2 on a Kindle Fire HD 7" will definitely brick it. This is because the bootloader is so-named for a program that checks the booting process before the device actually boots, and if there are any bad sectors that don't match, the device won't boot.
How do you avoid this? By following guides like mine, and first knowing exactly what model you have. Yes, the Kindle Fire 2 and the Kindle Fire HD 7" look similar, and Amazon seriously have problems with their naming method, but a bit of research tells you that the Kindle Fire HD actually contains an HD resolution screen, 1280x800 for the 7" and 1920x1200 for the 8.9". Also, ONLY the Kindle Fire HD 7" and 8.9" models have a front-facing camera while the other models don't have one at all. If you want to be sophisticated about it, you can use working fastboot to identify the tablet.
+Note: if you know 100% that you have the right model, skip to Step 1 and begin the guide. This part is only for those with knowledge of fastboot and would like to confirm scientifically that they have the right model. You don't need to know how to use ADB or fastboot in order to successfullly complete the guide and install custom ROMs:
In CMD, type:
Code:
fastboot -i 0x1949 getvar product
Hitting enter will return with <waiting for device>. If you connect your powered-off Kindle Fire HD 7" or 8.9" at this point, it will reboot into fastboot mode, and on CMD, it will return with "tate-xxx-xxx" for the 7" and "jem-xxx-xxx" for the 8.9". I cannot stress this enough, please know your stuff before you end up crying about how you made a simple mistake that cost you $200, or however many in other currencies, but I do know that universally, it's quite a lot of money.
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
===== 6. How do I boot into fastboot mode? =====
This relies on you having a working device (as long as it can boot at all, you're good). If you wish to enter fastboot mode to flash system images like new versions of TWRP or restore Amazon OS 8.1.4 if you've got freezing or bootloops, then you need a regular USB cable that came with the device, or any other mini-USB cable that fits the device and the computer. Again, you need to have Android SDK installed before you can use fastboot. Turn the device off, and leave it unplugged. Go to your computer, open command prompt, and type this:
Code:
fastboot -i 0x1949 getvar product
Hit enter, and it should return with <waiting for device>. If it doesn't, your fastboot drivers aren't working. Install Android SDK and go from there. If it does, connect your turned-off Kindle to the computer. Two things will happen: one, the command prompt will show "jem-xxx-xxx" (something there), and two, your Kindle should reboot into fastboot mode. From here, you can begin using fastboot commands to flash to the device's partitions. To exit fastboot mode, after you finished flashing what you needed, type this:
Code:
fastboot -i 0x1949 reboot
And that's all for the basics! Let's move on to the actual process.
Step 1: Rooting​
+Note: Some users reported not being able to root on later software versions, so check for 8.1.4 in your Settings, if it's higher than that, you may have some trouble, which is why I provided 3 methods.
Before you can do anything else, you need to root the device first. Rooting is the process of acquiring superuser (administrator) access on a Linux system, allowing you to modify just about anything with regards to software. It is generally very safe to do, provided you follow the correct guides and you use the correct tools, and if there are no tools, the knowledge to manually root the device. On many other Android devices, rooting also installs a custom recovery, but the Kindle Fire HD 8.9" is different. You must root first before you do any modifications.
Go to this thread: QEMU Root by sparkym3, and download the necessary attachments. Use any decompressing software to unzip the files, and install the Kindle Fire HD 8.9" ADB drivers (this may fail, no need to worry). Then jump to your device, go to Settings and turn on ADB, then plug it into your computer. At this time, your computer should report that the ADB Composite Interface has been installed. What this means is that your ADB drivers work. Go ahead and use that thread's instructions to root the device.
Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry, same idea. Make sure your ADB drivers are working, and that ADB is turned on in Settings. Open the RunMe.bat file, choose option 1. Now it will ask for your Amazon account password to restore, go ahead and type in your password and proceed. After the device reboots, it will be sluggish, now run the first method again, and you'll be back to normal with root.
You can aso try this: Root Kindle Fire HD with Windows
To check if you're rooted, when the device is on, go to the Amazon Appstore, install "ES File Manager" or any other root application, you want to see the window asking for superuser permissions. Once it installs, open it, go to settings, and turn on root browsing. If it asks for superuser permissions, you have root access, and you can move on to the next step. If the root programs say you have root, but you don't see the window asking for the permission, remember to go to the app listing, and tap on superuser to initialize the daemon, then try to check for root again.
Recap:
1. Download the root tools from the threads
2. Proceed to root by using the provided tools
3. Check if you successfully have root access using any root application
Step 2: Grabbing Files and Backing Up​
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Step 3: Installation​
You might have noticed that Hashcode made a pretty extensive thread to help you flash the bootloader, but another coder has since developed an automatic app to do all the work for you: FireFlash. Go ahead and download the .apk file. Move that file to the sdcard, and on the device, install it using "ES File Manager" (tap on that file) or "Easy Installer" (after it finishes scanning, select it and install), both found on the Amazon Appstore. You will then find it in the applications listing, go ahead and open it.
The first thing you notice is that there are spots to plug in files for different partitions. This is where those files from Hashcode come into play. Plug the freedom-boot.img into the boot partition space, plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack". If you are NOT on the 8.1.4 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 8.1.4 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on.
Check that "disable recovery auto update" box, leave everything else alone, unplug the cable, and hit flash (the first option). You will see a progress window, and just hit OK. Then, turn off the device. Now, when you turn it on, this is the way to enter recovery every time: the moment you turn it on, you'll see the yellow Kindle title. Immediately hold down the Volume Up button (leftmost from the power button) before it turns blue, and once it does, count to three in your head and let go and you'll see the TWRP splash logo. Once you're in TWRP, you're done. Just hit reboot, and everything's finished. Now you can browse the 8.9" Development forum for custom ROMs.
If you want to save space, you can now go ahead and delete all the files we just used; you no longer have a need for any of them. Keep FireFlash, though, because in the future you might want to update TWRP, then leave everything blank, plug the update image into the recovery partition and hit flash. Only use Hashcode's TWRP builds as of now, because he specifically altered those builds to work on the Kindle Fire HD 7" and 8.9" so the official ones on the TWRP site won't work. If you flash those (especially the "blaze" codename), you will brick the device, so don't do it!
Recap:
1. Download FireFlash and install on device using file manager or installer
2. Plug in the required files in the correct areas, and check the necessary checkboxes
3. Flash, and boot into TWRP to confirm successful installation of both 2nd-Bootloader and TWRP recovery
Step 4: Flashing Custom ROMs​
This is what you've been waiting for, the ability to load custom ROMs. You have a few choices at this point in time. This list contains (somewhat, if not) stable releases only:
1. CyanogenMod 11 by Hashcode (AOSP, Android 4.4 KitKat)
2. ParanoidAndroid Port by jb2kred (AOKP, Android 4.2.2 Jelly Bean)
3. PAC-man by goldflame09 (AOKP, hybrid of CM + PA, Android 4.3 Jelly Bean)
4. CM11/SGT7 by twa-priv (CM + Samsung Galaxy Tab 7 mods, Android 4.4 KitKat)
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Now, in case your custom ROM doesn't automatically include GApps, and you would know if you boot up and you don't see Play Store or Google Maps in the app drawer, follow this. Go to this link. You will notice a table, and on the left side, you see the CM version that corresponds to the Android version number. All the custom ROMs should use the row that corresponds to the Android version. For example, CM10.1 runs 4.2.2, CM10.2 runs 4.3, so click on the one that corresponds. If your ROM runs 4.2.2, use the 4.2.2 row, etc. After you finish downloading that .zip file, move it to the sdcard, and boot into TWRP. From there, if you want to be fancy, wipe cache and Dalvik cache before flashing, but you don't have to unless there are problems after you restart. If there are problems, like freezing on boot, or crashing, then boot back into TWRP and wipe the two cache partitions.
Generally, you only need to flash the file and you're done, but you can never be too safe. This also applies to ROMs: if you're moving from ROM to ROM, say Ubuntu Touch to CM10.1, you MUST wipe EVERYTHING except the sdcard itself, and this includes the "Factory Reset" option. However, if you're moving from one update of a ROM to another, say a nightly of CM10.1 to a newer nightly of CM10.1, you can just simply flash the update over the old one, no wiping needed (this is called dirty-flashing). However, again, if you notice problems afterward, simply boot back in TWRP and wipe the two cache partitions. Remember to always make backups before you make changes to an otherwise stable build. If there are issues that you can't seem to resolve, you can always restore back to the previous build.
Recap:
1. Download .zip for ROM + GApps and move to sdcard
2. Boot into TWRP, make backups, and wipe the necessary partitions
3. Flash ROM, and wipe cache + Dalvik cache, then reboot
4. Wait for 5 minutes after successful reboot, then reboot again
5. If there's no GApps for your ROM, use the link to download the proper version.
6. Move the file to sdcard, then boot into TWRP and flash.
7. Reboot, and if there are problems, reboot back into TWRP and wipe cache partitions.
Credits: Hashcode, fattire, and verygreen for the work on the bootloader, stanga72 for the app FireFlash, sparkym3 & prokennexusa & Bin4ry for their rooting methods, and myself for the creation of this guide.​
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
rebelduke said:
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
Click to expand...
Click to collapse
Thepooch said:
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
Click to expand...
Click to collapse
I am aware of the changes, but I have not been caught up with the status of the methods and their effects on the tablets. I have placed warnings at the beginning of the guide.
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Sorry about asking about 2! I was actually putting the brackets around the local folder, but I realize now that you only had them to indicate that parameter was optional. However, the error that was occurring before wasn't about the local file...it was about the .img file which did exist. I'm baffled because now if I put the brackets back, it only fails with an error about that, not about the .img file. I realize I'm not making much sense, but I can't reproduce it so that it says the same error that I first mentioned above in 2.
I'd still like to know about 1 though. Thanks.
EDIT: I did Step 3 - Installation. I booted into TWRP and did a backup. I assumed that I did not have to do any wipes or install of any other rom yet, i.e. I just wanted to boot the existing 8.1.4 rom that was already there. However, when I "reboot system" from TWRP, it goes into TWRP again instead of booting up the rom.
I tried doing a restore of what I just backed up, but the result is the same. So does this mean I was required to do the wipes and install of another rom, rather just booting up my existing one? Or is there some other step I'm missing to make it get out of TWRP?
sga999 said:
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Click to expand...
Click to collapse
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Thepooch said:
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Click to expand...
Click to collapse
I realized more about the format of the 'adb pull' command and posted late last night. It's in my post above your response. Thank you for answering. Also, it's good to know about what boot0block is in case something fails later.
I also added another question there, wondering about why I can only boot into TWRP, not the stock rom I already had installed. I'm pointing that out again now, just because you(and others?) may not have seen it in my EDIT above.
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Thepooch said:
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Click to expand...
Click to collapse
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
sga999 said:
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
Click to expand...
Click to collapse
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Thepooch said:
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Click to expand...
Click to collapse
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
sga999 said:
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
Click to expand...
Click to collapse
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Thepooch said:
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Click to expand...
Click to collapse
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
sga999 said:
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
Click to expand...
Click to collapse
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Thepooch said:
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Click to expand...
Click to collapse
Thepooch, I'm not sure if this is interesting to you at all, but I experimented a little and learned something. As you suggested, I flashed 8.4.1 and decided to try an unusual step.
After I used Fire Flash yesterday and booted into TWRP, I immediately created a backup. But it turned out to be no good in the sense that restoring it did not help me fix the problem of not being able to boot into the 8.1.4 (old) rom (I could only boot into TWRP). But now that I was on 8.4.1, I did a restore of ONLY the data from that old 8.1.4 backup. It seems fine so far, except for Google Play app, which just exits as soon as I execute it.....it's not a big deal to fix that. (There may be other issues, but I haven't hit anything else yet).
So....it seems like something is bad in either the boot or the system portions of the backup. It's probably system since it has framework, which you had mentioned might be causing the problem. Again, this may not be interesting, but I thought I'd let you know.
Makes sense google play rarely works from my restored backups and your system was in good shape if you flashed the 8.4.1 zip prior to restoring data.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP with 8.4.3
Has anyone attempted Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP running 8.4.3? If so, were you successful? If you were successful did you follow the procedure defined here or did you have to deviate? If you had to deviate, what were the deviations? Thanks!
How to root kindle fire any version (including 8.4.3) ONE CLICK
Hi I need some help.
KFHD 8.9, non-us user, but bought at amazon, i am unsure of the exact version.
ADB worked ok, device showed there. BUT "fastboot devices" didnt really show anything at all. Still I went ahead with it. Rooted using bin4ry, qemu did not work at all, permission denied error.
I did everything up to the point of flashing the freedom-rom and twrp through fireflash. It did not have 8.1.4 bootloader, so I checked the box, checked the other one and left all else as is. It seemed to flash ok. Then I rebooted,,, and its stuck on orange kindlefire logo, forever. doesn't matter what volumes i hold. tried rebooting and everything.
Now I dont really know what to do... any ideas?
Getting errors trying to install the drivers from the QEMU zip file, so no device ( sdcard ) access from recovery and the Advanced...sideload option is not working either.
I'm on windows 8, when plugging in the KFHD89 to my laptop, I see the kindle show up, but I have the yellow explanation sign. When I try to update driver software, i get error it can't update Windows ADB.
Between windows 8 and ubuntu, I've been able to get fastboot working enough to get all the files loaded...but for the lift of me !!! my copy of CM10.1 and gapps.zip are not seen via recovery...AND...I get stuck at Blue boot logo...so I'm sort stuck in recovery and need to get drivers sorted between windows and/or ubuntu so I can copy the .zip files over.
EDIT: #6 from http://forum.xda-developers.com/showthread.php?t=2277105 helped me out. I was starting ADB Sideload and connecting USB out of sequence. Followed directions and it worked.

How to root your Samsung Galaxy Gear!

How to Root the Samsung Galaxy Gear:
Firstly:
I AM IN NO WAY, SHAPE OR FORM, RESPONSIBLE FOR THE OUTCOME OF YOU FOLLOWING THESE INSTRUCTIONS! IT WORKED FOR ME, BUT THAT DOES NOT MEAN IT WILL ABSOLUTELY, POSITIVELY, WITHOUT A DOUBT, WORK FOR YOU!
Root Guide:
Preparation:
1. Install Samsung's official ADB Drivers from here.
2. Get Cydia Impactor from here.
3. Go to your Gear's settings and enable ADB​
To Root:
1. Plug in the device and let it install all the drivers it needs.
2.Unzip the Cydia Impactor folder you just downloaded
3. Open Impactor from the folder you just unzipped
4. The default "# drop SuperSU su to /system/xbin/su" is what you need
5. Click start
6. Once the process completes, the device will still look normal, but is fully rooted!​
I will have to leave it to you guys to install a utility like SuperSU or Superuser until there is a functioning recovery for the Gear.
Though this isn't necessary, however, and in some most cases doesn't work! SuperSU or Superuser just manage what apps access the SU command, so if you trust the app, it should be ok!
Enjoy your newly rooted device!​
How to restore back to stock:
Preparation:
1. Get Odin 3.07 from here.
2. Find the proper .md5 file from here.
(If you are in the US, just select the Great Britain file.)
3. Install Samsung ADB drivers from here.​
To Restore:
1. Plug in the Gear
2.From being powered on, (Bootable or not) press and hold the button of the right until the Gear shows "Samsung Galaxy Gear Rebooting" and rapidly press the button until you get to the "Select REBOOT MODE" screen.
3. Highlight "Download" in the list by pressing the button to scroll.
4. Press and hold the button for 3 seconds (and let go! The screen won't change immediately) and let it boot into download mode.
5. Unzip the .zip file you just downloaded that contains the ROM itself.
6. Select the PDA button and open the .MD5 file in the folder you just unzipped.
7. DO NOT ALTER ANYTHING ELSE!!!
8. Click the start button, and you'll be back to stock within a couple of minutes! (Most likely with any data on /data kept and all sideloaded apps remaining.)​
Any questions? Ask below! Want to help me make a ROM or Recovery? PM me!​
I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.
Oops!
BUS DR1V3R said:
I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.
Click to expand...
Click to collapse
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!
photonicgeek said:
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!
Click to expand...
Click to collapse
I'm actually not sure what's going on with this thing now. Busybox said the device was rooted, and it installed, but I can't seem to run any commands that require root.
Are you running Superuser or SuperSU, and what version?
Does this mean i will be able to use this with my HTC one? Im a newbie when it comes to this but id love to buy this watch to use with my stock 4.2 HTC One. Thanks.
Sent from ...............
Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?
big_pongo said:
Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?
Click to expand...
Click to collapse
Haven't rooted mine yet. But seems like the unroot feature in supersu should work
---------- Post added at 06:22 PM ---------- Previous post was at 06:18 PM ----------
This is great news! Thank you sir for creating an account. Just to share ur find. Who knows this might even make it to XDA wall on home page! But I do have to ask, how did you know Cydia Impactor would do the trick?
To answer some questions...
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!
photonicgeek said:
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!
Click to expand...
Click to collapse
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?
Someone please sticky this so its easy to find
Sent from my SM-N900V using xda app-developers app
Minecraft on the Galaxy Gear!
BUS DR1V3R said:
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?
Click to expand...
Click to collapse
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom
photonicgeek said:
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom
Click to expand...
Click to collapse
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?
codeman05 said:
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?
Click to expand...
Click to collapse
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?
photonicgeek said:
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?
Click to expand...
Click to collapse
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
I figure you can try restoring again!
codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially
codeman05 said:
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially
Click to expand...
Click to collapse
Actually, I'm glad you found that!! I've been using ADB all this time!
Mods,
PLEASE pin this thread!
Hey does anyone know if
a) you can get notifications from 3rd party sms apps like handcent and
b) if you can respond to sms by typing yet? its pretty annoying when you get a text on your gear and you're somewhere loud, then you gotta take out your phone and respond. please if anyone knows these answers cant wait for this to take off....pretty excited.
this looks interesting! will have to try it on my gear :laugh:

[Q] changing custom ROM

Hello everyone....
I have a kindle fire HD 7" 7.4.6
I rooted and added TWRP with 7.2.3 bootloader
I installed CM11 Kitkat the ROM is a bit buggy but nice.
I tried to go from kitkat to kinology which allows use of Amazon and Google services.
But flashing failed.... I can't seem to get kinology to work.
This is the set of walkthroughs I used.
To root & add TWRP. I used a rootjunkie YouTube video ( can't post link)
To install cm 11:
also a rootjunkie video
knowing this, I tried installing kinology using this walkthrough:
Original kinology page.
No luck, does anyone know how I can move my system to kinology?
please help,
Thanks to all in advance
OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok first, thanks for the reply. Second, yes i did do a wipe before the install.
I am going to go check out your link now and see.... ill keep you posted.
Thanks again....
Quick question.... can the process in your thread be done through fire flash 11? ( i am an absolute noob at this, so it may be a silly question...)
i can follow along as to what must be done, but i dont feel comfortable doing a process without a guide.....do you know of any threads with a walk through for this?
There aren't any tutorials for this as far as I know, I got this command from Hashcode in the irc, just run the command mentioned above from a command prompt (while in recovery) while cd'd into a utility that came with a copy of adb, like my wallpaper fix for example that's in my signature. If you don't know anything of command prompt like what CD commands normally I would say read up on basic command prompt because its very simple, but because of a nice trick I remembered recently you can avoid the CD command, just shift + right click the folder with adb in it and hit "open command prompt here", then run the command I posted (while in recovery).
Sent from my Amazon Kindle Fire HD using Tapatalk

Categories

Resources