Develop Bugs

Dealing with Sprint / HTC Preinstalled Junk - Startup Auditor or Just wait for Root?

I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!

If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.

gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?

berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.

okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it

I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.

elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.

go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?

elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D

All done!!! :-D now to flash rom... good times!
Thanks all

[Q] Kindle Fire is completely blank, except for TWRP

Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!

heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!
Click to expand...
Click to collapse
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.

Sorry, but where do I enter these commands?

soupmagnet said:
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.
Click to expand...
Click to collapse
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?

heatherrc77 said:
Sorry, but where do I enter these commands?
Click to expand...
Click to collapse
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038

heatherrc77 said:
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?
Click to expand...
Click to collapse
You need to download the Android sdk, then you can run adb from the command line.
Sent from my Amazon Kindle Fire using Tapatalk HD

heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory,
Click to expand...
Click to collapse
I know this isn't helpful now. But the original problem (I am pretty sure) had to do with the drivers with the audio. You probably had the volume all the way down, which causes the error you were receiving. If you mute it, that is fine, just don't have the volume down all the way.
----------------------------------------------
Sorry. I know this probably doesn't do you any good, but I thought I would let you know what I thought.

soupmagnet said:
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".

heatherrc77 said:
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".
Click to expand...
Click to collapse
I put a lot of thought into how I should respond to this post, so bear with what I'm about to tell you.
My previous post was not intended to "belittle" you, rather, wake you up to the reality that you might not be ready to take on such an endeavor. This is not an iPhone and it isn't as simple as plugging it in and pressing a few buttons. For new users, there is a high degree of risk involved in certain aspects of modifying the Kindle Fire, especially when it comes to repartitioning...which is what you'll need to do to get your Kindle working again.
My harshness is NOT out of ego or feeling "holier than thou". It is not to make myself feel better or to make up for some low self esteem. Treating people with kid gloves around here tends to give them a false sense of security that quite often leads to them getting into very stressful situations. Besides, a little "tough love" is better than indifference any day.
I created a thread in the General forum a while back, titled "**WARNING** You will BRICK YOUR KINDLE if you don't READ THIS FIRST!!!". The purpose of that thread is to warn owners of newer 2nd generation Kindle Fires of the DISASTROUS consequences of trying to modify those devices in the same way the 1st generation devices are. One would think, with a title like that, there would be very few people to make that mistake. Of course one would be wrong, as there are at least two individuals a week that were not prepared to deal with the situation at hand and did not give it the appropriate amount of respect, therefore their Kindles are completely worthless. Needless to say, if something I say is construed as rude yet prevents mishaps like that...so be it...and I'll consider it worth the hurt feelings.
And I agree, in order to learn, sometimes you have to get your hands dirty. But there is a big difference between tweaking some system files contained within a single partition and actually modifying partitions. And yes, you do have to start somewhere, but if you don't know that commands go in the command prompt (and I'm saying this respectfully), this is not the place for you to start. Go back, read through the links I gave you, and get a better foundation to work from before trying to fix your Kindle Fire. Not doing so, would do you a great deal of injustice.
No hard feelings,
And I wish you the best of luck.

[Q] Android Falls Over in Revovery Mode

First of all let me say THANKS to all of the dedicated folks on this website that I have found to be most useful while looking for help.
My problem may have been discussed previously, but after doing much browsing I must not be using the right keywords to find a resolution.
I am having issues with a SGH-i747 running stock 4.3 that I just purchased, so I have no clue what may have been done to it in the past.
So as the title says - The green android while booting into recovery mode just falls over with red triangle, and underneath it flashes - No command - Error - No command.
Also if I do try to flash anything - I get several RED errors in a row basically saying - E: No data folder found and a few other things before it quickly reboots and I can't see what the other errors are.
Would appreciate any ideas you folks may have - Thanks.

TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.

Odin Fails Too
BCSC said:
TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.
Click to expand...
Click to collapse
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.

Deeeno said:
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.
Click to expand...
Click to collapse
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.

BCSC said:
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.
Click to expand...
Click to collapse
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.

Deeeno said:
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.
Click to expand...
Click to collapse
I understand exactly what you mean, but root access can be a key to you here. Your recovery is broken or at least something in a system file is harming what recovery is trying to do. Problem is these are not accessible without root. Root is not the band aid, it's the scalpel Try fixing that car without wrenches. The problem with recovery is that it is protected. You could flash a new stock one as part of an official firmware, but if you are stock 4.3 you are going to run into bootloader issues (nevermind the fact that Samsung hasn't released one. This leaves your other fix as replacing your recovery and requires access to the root system files.
++On another note, I just found this and don't want to delete everything I just typed. See this thread here and see if it pertains to you. http://forum.xda-developers.com/showthread.php?t=2520115
Either you or someone else have already installed a custom recovery. Without root access recovery will fail, the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790

Good point on having no wrenches to fix the car --- I will head your advise, and move forward with getting it rooted.

BCSC said:
the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790
Click to expand...
Click to collapse
You nailed it on the head - I'll be sure to also hit the Thanks tab for chainfire also since he deserves credit also.
CF Auto Root did the trick and the poor little green android no longer falls over.
Moderators can mark this thread as resolved & Thanks again for all your help.

help needed please !!

Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?

Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it

Broncos15 said:
Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it
Click to expand...
Click to collapse
No if that was the case then why will the file bo .bin.html ?

Mr.Dumb said:
No if that was the case then why will the file bo .bin.html ?
Click to expand...
Click to collapse
It shouldn't have .html on the end. Check the md5 sum for the file and make sure that it is the same as it should be, you should ALWAYS do this when messing with the bootloader

Maybe you flashed wrong images.
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...

maxaurelius said:
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...
Click to expand...
Click to collapse
I actually plan on doing this for a similar reason. My sons kindle battery life is appalling as it drains faster than before and charges slower, plus kindle updates are lacking badly and some things don't work anymore.
I hope you can fix it somehow.
Happy new year.

Mr.Dumb said:
Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?
Click to expand...
Click to collapse
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike

11fan said:
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike
Click to expand...
Click to collapse
Thanks a lot friends, i surely have a jem and i tried to read ad do things intended to do for jem only (seems strange to me that link i posted is for otter though i cross checked many times not to flash other device images but may be messed up in enthusiasm)
Never mind i eventually had to end up selling this on craiglist as a friend mentioned and got a working one from ebay ( to my shock it's reported as lost and stolen) looks i have great bad luck...
Now the kindle is just nothing unless i have cm in it but i will need all you guys help so that i dont end up like before
So please help me out with links so that i do all things correctly ...please i don't have any money now to loose or fix this ...
Thanks in advance
Edit : i tried to root kindle but was not able to, its on the highest or most up to date version of fire os as per amazon
I tried to root with restore by binary, cant see superuser in app drawer, able to see it in system/apps via root explorer
Tried to install firefire.apk it shows no root & root explorer doesn't rename system apps to .bak.... So i believe i cant root..
Please @11fan help me out now i need only cm on kindle thats fine for me.......
I'd be gratful to you for the help

Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk

11fan said:
Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk
Click to expand...
Click to collapse
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy

Mr.Dumb said:
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy
Click to expand...
Click to collapse
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike

11fan said:
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike
Click to expand...
Click to collapse
Yes please help me with TWRP / CWM. Please & I want to install CM on it now

Did you get it rooted?
Mike

11fan said:
Did you get it rooted?
Mike
Click to expand...
Click to collapse
Yes
Hello @11fan
Edit : got it rooted, TWRP installed, made a nandroid backuo & tried to flash CM (chkd MD5 as well) but CM boot screen stayed for so so long...so I rebooted the device to TWRP and did a full wipe as well as format data...now have no os installed, cant mount as usb storage to copy nandroid...kooks like i've messed again....
Praying to God that I have some way again to restore...
Edit 2 : sorted via adb sideload

Glad you got it....i was going to tell you that the LONG cm screen on first boot is normal! I just loaded cm12 on mine last night and first boot took about 8 minutes, maybe longer as I forgot to time it!
Mike

Firestick 2nd gen 5.2.7.4?

My firestick downloaded 5.2.7.4 and its broke my accessibility and adb commands. I looked on amazon to see latest versions for their devices and none of em are listed to have 5.2.7.4. Not sure if anyone else is having this problem or if they are rolling out another update and I just got unlucky and got some of the first roll outs of it. I also had ran some debloat commands and not sure if the stick just ran some updates after that. But it was after that it broke. But I have since factory reset and its still broke adb and accessibility. Just wanted to make people aware and see if anyone else has found a fix for this version or any info on a fix.

I having this problem too, cant set custom launcher.. anyone help us??

The 5-6 domains did not block this update either! This update made it through!
I also am wondering about this. Not even the app I used to prevent standby works anymore!

I have been looking all over for any info on the .4 update and no one seems to care as if this update doesn't exist. I have found no info on any existence of .4 except for a select few people sharing the same problem. this update has broke my adb as well as accessibility. Virus scanner wont work custom launcher will work if manually loaded. any app that requires any adb or accessibility are completely broke. sm commands come back as doesnt exists as will as i believe pm commands. only a select few non important commands will work. trying to give details in case it helps at all. but for now just letting developers do their thing and not trying to bother them to much. would love to help more but my 2nd gen tank cant be rooted. so i cant pull a backup or anything from it. not to mention if it was able to be rooted id be golden. Hopefully if someone figures out this whole .4 thing they will be kind enough to post something about it.

https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
Adb works without any Problems.

dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.

Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.

noremy said:
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
Click to expand...
Click to collapse
Try toggling unkown sources and debugging in settings? Maybe they got turned off?
Oh and just straight usb, 1 cable? Mine wont do tether adb with an otg cable.

Done all that. Unfortunately Im stuck. I dont what else to do with this thing. ADB will still connect but all the important commands come back as missing or invalid. such as sm commands and pm commands.

With 5.2.7.4 , you need root for this commands!!!

Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.

TimmyP said:
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Click to expand...
Click to collapse
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.

Sus_i said:
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Click to expand...
Click to collapse
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.

TimmyP said:
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
Click to expand...
Click to collapse
:good:
You can fix this issue if you connect the FireISO system to the internet and run this, in order to update fb:
Code:
pacman -Sy
pacman -Sy fastboot

Ahh where were you a couple days ago!

noremy said:
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
Click to expand...
Click to collapse
So just to clarify, 5.2.7.4 OTA has taken custom launcher apart by blocking pm grant permissions in accessibility.
TechdoctorUK mentioned this too a couple of weeks back. It seems the devs at amazon have been all over him lately and have been quoting tutorials etc from his site.
I've been using the ftvlaunchx app wrote to system settings on a post Dec 2019 unrootable 2nd gen and thought I'd blocked 5.2.7.4 update but I came back in today and was fkin horrified it had updated to 5.2.7.4 (I nearly sh't myself) its still optimizing apps just now but I'm hoping, just hoping that due to the pm grant permission already being installed it maybe slip through the net. Wishful thinking I know.
Hurry up and arrive 4k firestick I NEED ROOT

Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.

noremy said:
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
Click to expand...
Click to collapse
Hi noremy, i just made a new thread there on 5.2.7.4, the cure is ftvlaunchx wrote to system settings, install atv launcher pro and set that as default launcher in the ftvlaunchx app, should work with any android tv launcher too.
Big thanks to the developers @github
Edit #### i rebooted and now the home button is not working at all
Only sending me back to amazon screen.
Regards
Sent from my SM-T580 using Tapatalk

Hi! Mine is a 2nd gen Firestick. After the 5.2.7.4 update, none of my apps are opening. It says "Amazon App Store is out of date. Please visit the Amazon website to install the latest version". When I click on the link, it says Appstore is installed & I am good to go. No matter what I do, same thing happens for each and every app. So I can't use any of the apps on my Firestick. Any suggestions on what this is? Thanks!

The only option I can think off would be to factory reset it. I know its a pain to put everything back on but not sure what else to try.