[Q] Help with removing CWM or identifying root or not - Fire TV Q&A, Help & Troubleshooting

I just purchased a unit that has TV AddOns Custom Wizzard Edition that was advertised to be rooted with the latest custom rooted firmware installed. The unit shows up as having the latest 4.0 Amazon firmware on it and yet the seller says that it's a custom image and that the unit is indeed rooted. I honestly can't tell, but Super SU won't work on the unit and I'd like to downgrade the firmware to a rootable custom version and remove what he has on it to install my more familiar standard XBMC setup to it and then lock updates.
Can someone point me to a guide for downgrading the firmware or better yet removing the entire setup so that I can configure the unit in the manner to which I am accustomed to? I'd certainly appreciate any help....I honestly do not believe this unit is rooted, but he's swearing that it is and that the latest firmware that I'm seeing on it is a custom rooted firmware. I really need help here in finding out if it really is rooted and would greatly appreciate anyone's advice on downgrading the firmware or removing the setup entirely without losing root if it is in fact rooted. I'm in the dark as to cwm since I've never worked with it....
Thanks in advance for any help anyone can offer!

Use the Fresh Start program in TV Addons to remove all of the Custom Wizard stuff in XBMC.

Adb connect to the unit and then
Adb reboot recovery.. If cwm loads it's probably rooted as I don't think u can run stock Roms with it.. If it's on stock recovery.. Then u are on stock firmware.. Don't flash anything either way.. Just reboot the machine bacj to the fire os and Goto manage applications and uninstall the tv addons version. . Then side load xbmc.. Or kodi I guess it's called now. I always preferred not running any wizards that modify xbmc.. I like my splash screen the way it is thanks.

nhumber said:
Adb connect to the unit and then
Adb reboot recovery.. If cwm loads it's probably rooted as I don't think u can run stock Roms with it.. If it's on stock recovery.. Then u are on stock firmware.. Don't flash anything either way.. Just reboot the machine bacj to the fire os and Goto manage applications and uninstall the tv addons version. . Then side load xbmc.. Or kodi I guess it's called now. I always preferred not running any wizards that modify xbmc.. I like my splash screen the way it is thanks.
Click to expand...
Click to collapse
Thanks guys.... As I suspected it was not rooted......another eBay seller who either doesn't know what rooting is and simply uses it in his title since others do or is pulling a scam. It was his only unit....not a bulk seller so I think it's more ignorance than anything else. In any case....back it goes!
I appreciate your help... for a non rooted unit I actually like the Custom wizard xbmc add on....being pre configured makes it quick and simple to load a unit and not have to change too much to have what you want. Different story on a rooted unit.... I have a backup that loads with all the repos and shortcuts already installed. It's almost as quick as using the wizard edition and is setup to exactly what I personally want.
As always though.... it was great to get a quick and accurate response from those who know so much more about this than I.
Thank you again!

fxbill said:
Thanks guys.... As I suspected it was not rooted......another eBay seller who either doesn't know what rooting is and simply uses it in his title since others do or is pulling a scam. It was his only unit....not a bulk seller so I think it's more ignorance than anything else. In any case....back it goes!
I appreciate your help... for a non rooted unit I actually like the Custom wizard xbmc add on....being pre configured makes it quick and simple to load a unit and not have to change too much to have what you want. Different story on a rooted unit.... I have a backup that loads with all the repos and shortcuts already installed. It's almost as quick as using the wizard edition and is setup to exactly what I personally want.
As always though.... it was great to get a quick and accurate response from those who know so much more about this than I.
Thank you again!
Click to expand...
Click to collapse
glad you got it all straightened out. you can still adb push your backup files on a clean xbmc install.. so you just sideload xbmc then adb push your backup to the correct location, i forget that exact location at the moment tho.. theres alot of good instructions on the xbmc wiki. http://kodi.wiki/view/Amazon_Fire_TV#Copying_files . the xbmc backup addon also works from what i was reading, i havent personally tried it myself.

Related

[GUIDE][ROOT][CWM] ARCHOS 97b Platinum HD

I came upon this device on Christmas (a gift from my girlfriend to her father) and wanted to root it and also install clockworkmod recovery, so I could mess with it a bit without bricking it. Since I found a lack of tailored guides for it, I decided to write this one, although I really did no actual development whatsoever. Normally I would be posting this on general, but given the spirit of this forum, I guess I'll just leave it here. Also, keep in mind I don't have the device anymore and am writing this from memory. If I missed anything or you have any doubts, please let me know (for example, I can't recall specifically the drivers I installed to make it work properly).
Please, please read the whole guide before trying anything, and if you are a novice user, just leave this be, I don't want you to turn your tablet into a paperweight because of my shoddy instructions written from memory and you probably don't need any of this anyway as there are no custom roms yet.
!!!DISCLAIMER!!!: As stated above, anything you do is at your own risk. I provided the procedures that worked for me on a Qilive 97r tablet, which is an Auchan branded ARCHOS 97b Platinum HD, so my step by step should work for all of you. There are probably easier ways to do this, and I hint at them in the guide, but beware I have not tried them and cannot vouch for them. In fact, I cannot and will not take any responsability if you brick your device following these instructions, correctly or otherwise. You do this at YOUR OWN RISK. You have been warned!
Rooting:
I followed this guide on Windows 7 x64 and it worked perfectly.
So thanks to dhigby for that. I would just like to make a couple of remarks:
When you get to step 7 (Installing Superuser by ChainDD), don't. Install SuperSU by Chainfire instead, Use it to update the superuser binary (I think a prompt shows up) and when asked, let it delete the "other" superuser applications, that is, the chinese one. Clean and easy, you don't need to follow any more steps.
Congratulations, you now have (english language) root!
Clockworkmod Recovery:
There is no specific recovery for this device. Fortunately, thanks to AndroTab.info, there's a generic version for 3188 devices that you'll see should work quite nicely, albeight with some caveats.
What works:
Nandroid backup to/from external SDCard (won't recognize internal)
Installing zip files should also work, although I didn't try it at the time, as the device wasn't mine and I can't since I don't have it anymore, but since it mounts system partitions perfectly well I wouldn't think there would be a problem. Try it at your own risk though.
Other things probably work, give it a try.
What doesn't work:
Internal SDCard access
Probably other things
Installation:
Now that you have a rooted tablet, installing clockworkmod recovery is easy-peasy. Go to developer options and enable USB Debugging, then make sure you have a working adb daemon (look it up) that recognizes your tablet.
NOTE: I'm not sure if I had to install any specific drivers for this to work, I think if so they were installed while rooting by the chinese app. Anyhow, here's the Rockchip drivers, you might want to try to install them if you can't get a connection: http://www.rockchip.nl/downloads/
Download the file RK30GENERIC_CWM.zip from here - that's the recovery.
Now extract flash_image and recovery.img from the downloaded file above to the folder where you have your adb and follow the following commands.
Push the files to /dev partition on the device:
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Then enter root shell, like so:
Code:
adb shell
su
Now flash recovery.img into recovery partition with flash_image:
Code:
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Now power off your device. To enter recovery press volume down then the power button and keep them pressed until CWM boots. Voilá!
NOTE: The instructions above were adapted from here and all credit goes to AndroTab.info ; I posted these particular instructions because they are the ones I used and worked for me; there are other methods listed on that page which might or might not work, TRY THEM AT YOUR OWN RISK.
Backing up your original recovery (for warranty, if anything goes wrong, etc.)
To obtain a backup image of your recovery \ restore it back afterwards, follow this guide here. All credit goes to Originalas.
Don't follow it to the letter though: first and foremost, you need a working linux installation. If you don't have one, I recommend Wubi.
Then:
Follow step 1;
Ignore step 2 (it's outdated);
Follow 3;
Follow 4 - but don't expect the screen to turn on, it won't, just hold the volume down button for 10 seconds or so after plugging it in, don't press the power button!
Ignore 5, 6 and 7
Follow 8, but don't use the last command to flash the CWM recovery onto the device. This is because since it is a generic version, it relies on the original recovery kernel. Flashing the image like stated in step 8 would probably overwrite the kernel and result in no recovery at all (I might be wrong about this).
Do follow the last command to restore your own backup if you ever need to.
I am unsure if recovery dumps obtained in this way are device specific; I don't see a reason why they should be, so I'll provide you with my own backup:
ORIGINAL RECOVERY
Flash through any method of your choice, but keep in mind I haven't tried this on other devices, so, as you know by now DO IT AT YOUR OWN RISK.
Closing remarks:
There you have it. Sorry for not holding your hand through every step, but this is meant for people who know a bit of what they're doing, making it faster than having to look up and figure out all these things and quirks on their own. If you have any doubts don't hesitate to ask, but keep in mind I don't have the device anymore and don't know much more than what I have written here. I do appreciate feedback and corrections, and will gladly change the guide giving you full credit - if it's really urgent just PM me, I might not check this thread often.
Cheers!
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Newbleeto said:
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Click to expand...
Click to collapse
hi and thanx for the answer
yes i saw that it's almost stock but crappy optimized...in the very first start of the tablet i had 1.8gb occupied by nothing and clean master always notifies me that 90% of the ram is busy...meh
maybe just a kernel will fix like you say but you know, android 4.4 will be a must (rockchip already released sdk for 3188). I am not a coder (totally zero) but i will try your suggestion...just a question about the performance governor, does it drain more battery?
i am trying to backup my rom but cwm is so buggy...first was impossible, now i'm stuck on backing up boot image
there is a twrp available for this tablet?
solved
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Dump stock ROM QiLive 97R
Jammed_Death said:
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Click to expand...
Click to collapse
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Redinpais said:
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Click to expand...
Click to collapse
you can upload it on mega or gdrive or something like that
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
about the cwm, there is a way to mount sdcard?
Dump stock ROM QiLive 97R
Jammed_Death said:
you can upload it on mega or gdrive or something like that
Click to expand...
Click to collapse
Here he are...
https://www.wetransfer.com/download...556a9cf8fdbc6ddd7ab35ab820141126224717/09298e
Is only available until Decenber, 3 ,so Download it now.
Jammed_Death said:
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
Click to expand...
Click to collapse
I've been watching but I can not understand. Is confused. There are many files and do not know what to do to "fix".
If you are Portuguese, I would like to talk to you on Skype.
Can be?
Jammed_Death said:
about the cwm, there is a way to mount sdcard?
Click to expand...
Click to collapse
I don´t know how I can answer that. I'm new in android, so I sorry.
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
Try this. Sooooooooo beautiful.:good:
(Because this - "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!" i can not put link now. So ask me by Skype) SORRY
:victory:
Follow the instrutions ther and enjoy KK 4.4.2 Oma ROM Iron KK v1.2 - 24-05-2013 (My QiLive say now - Nexus 7 :angel:
Regards
Qilive 97r
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Denysorlyk said:
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Click to expand...
Click to collapse
I'm interested
please ROM stock
Hello, i need help , if somebody know where I can download original rom , and original installer, I will be thankful for that's.

[Q&A] [RECOVERY] CWM Recovery 6.0.5.1.2

Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.
So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.
Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.
Thanks!
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS
About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.

[Q] Please help - Fire Phone Screwed Up

Hello,
I use a Fire Phone Unlocked GSM running on Fire OS 4.6.1 (latest), and I've been tweaking with many things in my Fire Phone, and when I was trying to bring the stock launcher back, I failed to, and I also noticed that the keyboard was gone and the only I thing I was able to do is Voice Input (which doesn't work ;P).
So, I have adb set up and everything - I just need to COMPLETELY REMOVE EVERYTHING in my phone than reinstall the OS.
I did find a link in http://forum.xda-developers.com/fire-phone/help/fire-phone-hang-to-booting-t3131037 where it did show a US link, is this for Unlocked GSM? And by the way, how would I remove everything in my phone first before using sideload?
Please help ASAP, I need this phone to work properly! (Don't want to make this a 200$ waste)
Yes, the *.bin files from Amazon work on all devices, netlocked or not doesn't matter. There are no provider specific versions, just the one from Amazon.
Remove everything? Sideloading the image will "wipe" the device automatically, it is 'squeaky' clean after that.
Just turn off the phone and boot into recovery mode. You can use my guide from the link you already found. Hope everything goes well, best of luck to you. ^^
Bingo Bronson said:
Yes, the *.bin files from Amazon work on all devices, netlocked or not doesn't matter. There are no provider specific versions, just the one from Amazon.
Remove everything? Sideloading the image will "wipe" the device automatically, it is 'squeaky' clean after that.
Just turn off the phone and boot into recovery mode. You can use my guide from the link you already found. Hope everything goes well, best of luck to you. ^^
Click to expand...
Click to collapse
Ok, thank you very much!

Phone Inadvertently Upgraded to 4.6.4. Is downgrade to 4.6.1 via ADB Safe?

I just received two phones (from the excellent eBay deal that I'm sure will drive more popularity of this forum), and stupidly, while working on the first one (getting CM11 on which went seamlessly), I forgot to disable updates on the 2nd. When I turned to the 2nd phone, my heart sank as I saw that it was now on 4.6.4 (464000220). My immediate thought was to boot into recovery and sideload 4.6.1 (820) but I remember reading that there is danger in downgrading this way?
Can anyone shed some light if downgrading this was is safe, or if I am no royally screwed? While Kingroot has no problem rooting 4.6.4, I'm trying to get to CM11 so I need Safestrap which apparently require 4.6.1 (820).
Any advice would be much appreciated!
Thanks a bunch!
I received Fire Phone today from the eBay deal..
I was reading thru Forums before i connect to Wifi.
Could you please share how you disable updates?
So in the absence of any response, I decided to just do it, and can confirm that sideloading 4.6.1. after having updated to 4.6.4 is without any ill effects. What a relief. As the eBay deal has about 7000 purchases, I'm sure others will fall into the same hole, so I hope this is of help. I used used Minimal ADB to serve as the deskop-side bridge (largely because I already had it installed from when I flashed my HTC One M8).
I must say the flexibility and simplicity of flashing these fire phones is even better than with HTC Ones. Ability to sideload a ROM baked into stock recovery is fantastic. If only all manufacturers were as (perhaps unintentionally) flash friendly.
It's surprisingly easy. Simply go to Settings (the Gear Wheel in the menu), then on over to Manage Applications (I can't remember exactly what it says as I've flashed both my phones over). In this section, make sure to select the filter at the top to list All applications (I think it defaults to those "Downloaded"). Then simply scroll to two entries that say System Updates. Select each and select Disable. That's it!
As I mentioned, if you are looking to flash CyanogenMod (and you really should since FireOS is extremely clumsy and poorly thought out), this doesn't matter as you wiping the phone of FireOS when you do so. The good thing is that if you don't like CM, you can always flash back to FireOS per the flashable images provided in other threads here.
Hope this helps.
sakdroid said:
I received Fire Phone today from the eBay deal..
I was reading thru Forums before i connect to Wifi.
Could you please share how you disable updates?
Click to expand...
Click to collapse
godhamba said:
So in the absence of any response, I decided to just do it, and can confirm that sideloading 4.6.1. after having updated to 4.6.4 is without any ill effects. What a relief. As the eBay deal has about 7000 purchases, I'm sure others will fall into the same hole, so I hope this is of help. I used used Minimal ADB to serve as the deskop-side bridge (largely because I already had it installed from when I flashed my HTC One M8).
I must say the flexibility and simplicity of flashing these fire phones is even better than with HTC Ones. Ability to sideload a ROM baked into stock recovery is fantastic. If only all manufacturers were as (perhaps unintentionally) flash friendly.
Click to expand...
Click to collapse
hey there...
can you post a link to 4.6.1?? thanks..
Just a heads up, my phone is an unlocked model on t-mobile and it OTA updated while I was in the store to 4.6.4. and rebooted into recovery with an error message. Only operation is to sideload. Will absolutely shut that **** off when I'm done.
godhamba said:
It's surprisingly easy. Simply go to Settings (the Gear Wheel in the menu), then on over to Manage Applications (I can't remember exactly what it says as I've flashed both my phones over). In this section, make sure to select the filter at the top to list All applications (I think it defaults to those "Downloaded"). Then simply scroll to two entries that say System Updates. Select each and select Disable. That's it!
As I mentioned, if you are looking to flash CyanogenMod (and you really should since FireOS is extremely clumsy and poorly thought out), this doesn't matter as you wiping the phone of FireOS when you do so. The good thing is that if you don't like CM, you can always flash back to FireOS per the flashable images provided in other threads here.
Hope this helps.
Click to expand...
Click to collapse
I am on 4.6.1 and I disabled the 2 system updates app.
but still, its trying to download 4.6.4 update.
any idea..
How do you ADB fire phone.. I couldn't get ADB to work. I may miss drivers though.
I believe there is a third system file "DCP" that needs to be disabled. The list of apps adjusts in a couple threads here.
I would install a package called "Minimal ADB and Fastboot" which you can find on a Google search. A small and effective installation that works well.

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.

Categories

Resources