Develop Bugs

[Q] Kindle Fire wifi won't turn on at all

hey everyone,
I normally don't post on here because I find the info without needing to, but I can't find this even with google fu, any help appreciated
Problem: Wifi won't turn on
ROMs tried: Orignal Kindle ROM, CM 9 (hashcode make), CM 9 (Energy mod ICS)
Other notes: My methods worked on my other KFs, but not this one.... however its an older version. I was sure to make everything factory default, wipes the two caches, and out of frustration from TeamWin deleted everything on the flash and system (except TeamWin Obviously). I have the Android SDK setup to interface with the device, so if you need me to hit it from there let me know. Everything else works, but a wifi only tablet without wifi is useless in my book.
Thanks once again for any help I will go back to google fu'n and head to wall bashing

Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.

hmm
Thepooch said:
Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.
Click to expand...
Click to collapse
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.

update
initialhit said:
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.
Click to expand...
Click to collapse
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.

final update
initialhit said:
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.
Click to expand...
Click to collapse
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!

initialhit said:
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!
Click to expand...
Click to collapse
Did the factory ROM flash correct the issue or still a no-go for WiFi?

Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.

kibusaki said:
Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.
Click to expand...
Click to collapse
Wrong device. Wrong forum.

[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] Unable to downgrade from 51.1.1.0

I will try and be vey detailed and hope this is clear. I have a stock Fire TV that is at 51.1.1.0
My router blocks all updates through URL blocking. I was able to root using ADBFire. Worked like a charm, ran towel root, SU, and installed busy box. Now would like to load rbox recovery but before I can unlock to the boot loader I need to downgrade to 51.1.0.2. I have tried to push it manually to the /cache and I have used the USB. The push seems to time out and although the usb seems to load when rebooting to apply the firmware it only goes about 1/4 of the way and then says the update failed. Wait and reboot. So I tried 51.1.01. Exact same problem. I even tried to reload 51.1.1.0 and it did work. At least I know the process is right. I know it loaded because I had to re root the box. But it will not take an older firmware and thats what I need to load the recovery. Any ideas?
Thanks in advance for any help.
John

boatguy said:
I will try and be vey detailed and hope this is clear. I have a stock Fire TV that is at 51.1.1.0
My router blocks all updates through URL blocking. I was able to root using ADBFire. Worked like a charm, ran towel root, SU, and installed busy box. Now would like to load rbox recovery but before I can unlock to the boot loader I need to downgrade to 51.1.0.2. I have tried to push it manually to the /cache and I have used the USB. The push seems to time out and although the usb seems to load when rebooting to apply the firmware it only goes about 1/4 of the way and then says the update failed. Wait and reboot. So I tried 51.1.01. Exact same problem. I even tried to reload 51.1.1.0 and it did work. At least I know the process is right. I know it loaded because I had to re root the box. But it will not take an older firmware and thats what I need to load the recovery. Any ideas?
Thanks in advance for any help.
John
Click to expand...
Click to collapse
You need to manually downgrade your stock recovery first. Take a look at http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/
There is one thing to note though... it says "Download the Fire TV Stock Recovery by Amazon file for version 51.1.1.0_user_511070220 from AFTVnews.com/software". It should say something a little clearer because it's actually 51.1.0. But anyway, that's what you need to do.

I should have read the guide more closely. I managed follow the instructions, and did each step to downgrade the firmware. But when it failed I neglected to look at the top where it said some versions are blocking the upgrade. Thats mine! I will load the recovery and work forward from there. Thanks for the help. At any rate I learned a lot in this process so it wasn't time wasted. Thanks again rbox for all you do and teach with this device.
John

1st Gen FireTV stuck an Amazon FireTV logo

I have a rooted 1st Gen with 5.0.5.1 on it
I used software ver 51.1.4.0
Now Im suck cant connect ADB

trickyrick said:
I have a rooted 1st Gen with 5.0.5.1 on it
I used software ver 51.1.4.0
Now Im suck cant connect ADB
Click to expand...
Click to collapse
Did you try clearing cache? Maybe you need to do a factory reset?

I only know how to do that when the firetv will boot. Using the remote will not work. Clearing cache also FTC needs to boot. I'm stuck on the logo
Thanks for the suggestions

trickyrick said:
I'm stuck on the logo
Click to expand...
Click to collapse
Why you flash a fireOS 3 version over a fireOS 5?
If the FireTV Boot Menu doesn't show up at boot, your box is probably dead.
Only way to recover is with a low voltage emmc adapter soldered to the EMMC, but this costs about the same as a new stick.

You may want to give the link below a try. I did the opposite by going from fireOS3 to fireOS5 without installing bueller_recovery_v2.zip first and has a similar issue. I was able to get my box working, however there are a few issues. ADB doesn't work, supersu is still running as a service. I'm stuck on software 5.2.6.3, prime video doesn't work and it tries to install os updates every time i rebooted the box.
I eventually got prime video working by installing a newer Video_com.amazon.avod.apk from one of my other box and i broken checking for updates by installing a newer DeviceSoftwareOTA_com.amazon.device.software.ota.apk and System Updates_com.amazon.device.software.ota.override.apk.
The box is running great except for os updates and adb.
https://forum.xda-developers.com/fi...ock-images-t2882337/post56987752#post56987752

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.