I installed Google play on fire tv stick
Then my device started restarting indefinitely.
What should i do?:crying:
unplug it boot to twrp wipe cache dalvic cache reboot see if fixes. if not using twrp restore a backup or rbox prerooted rom
MAGINA1994 said:
I installed Google play on fire tv stick
Then my device started restarting indefinitely.
What should i do?:crying:
Click to expand...
Click to collapse
what are you using firestick 1, firestick 2, firestick 4k? Are you rooted/Unlocked? TWRP will give you options, what device you have will determine what you can do. The 4k doesnt have options yet (but it is coming), the (2, tank) can be unlocked and fixed, the one? you have options but for what it is throw it away....
Michajin said:
what are you using firestick 1, firestick 2, firestick 4k? Are you rooted/Unlocked? TWRP will give you options, what device you have will determine what you can do. The 4k doesnt have options yet (but it is coming), the (2, tank) can be unlocked and fixed, the one? you have options but for what it is throw it away....
Click to expand...
Click to collapse
thank u sir. i'm using 4k. and i'm not root my firetvstick 4k.
Michajin said:
what are you using firestick 1, firestick 2, firestick 4k? Are you rooted/Unlocked? TWRP will give you options, what device you have will determine what you can do. The 4k doesnt have options yet (but it is coming), the (2, tank) can be unlocked and fixed, the one? you have options but for what it is throw it away....
Click to expand...
Click to collapse
so just throw it away at now？? i cant find the way to fix my firetv stick 4k
MAGINA1994 said:
so just throw it away at now？ i cant find the way to fix my firetv stick 4k
Click to expand...
Click to collapse
Be patient. There is a thread to donate for unlocking. I wouldn't be surprised if it is unlocked and rooted in the next couple weeks which should give you the tools you need to fix your brick. I was saying to throw the firestick1 away. The firestick 4k is the 2nd best TV device amazon has sold and definitely worth fixing!
https://forum.xda-developers.com/fire-tv/general/please-donate-to-k4y0z-bl-unlock-twrp-t3913935
hmm i wonder if you have enough time to trigger the factory reset remote shortcut of holding back and right for 10 sec
Michajin said:
Be patient. There is a thread to donate for unlocking. I wouldn't be surprised if it is unlocked and rooted in the next couple weeks which should give you the tools you need to fix your brick. I was saying to throw the firestick1 away. The firestick 4k is the 2nd best TV device amazon has sold and definitely worth fixing!
https://forum.xda-developers.com/fire-tv/general/please-donate-to-k4y0z-bl-unlock-twrp-t3913935
Click to expand...
Click to collapse
I've solved it! It automatically repaired itself!
THANK YOU! VERY MUCH!
g422 said:
hmm i wonder if you have enough time to trigger the factory reset remote shortcut of holding back and right for 10 sec
Click to expand...
Click to collapse
I've solved it! It automatically repaired itself!
THANK YOU! VERY MUCH!
no problem was did it fix self or were you able to factory reset?
MAGINA1994 said:
I've solved it! It automatically repaired itself!
THANK YOU! VERY MUCH!
Click to expand...
Click to collapse
Can you please explain how?
I think I let it loop 20-30 times max then cut power.
Have you let it loop longer, How long?
Related
I'm trying to unroot my kindle but I'm getting the binary error every time, and on forums they said it could be a problem with twrp and therefore, I'm here trying to figure this out, Thank you!
Could you be more specific? Also, the title of the post and the content therein seem to contradict each other. What exactly are you trying to accomplish?
soupmagnet said:
Could you be more specific? Also, the title of the post and the content therein seem to contradict each other. What exactly are you trying to accomplish?
Click to expand...
Click to collapse
I'm trying to unroot my kindle fire and revert back to STOCK ROM so I can send it back to Amazon due to touch screen issues, and I've read several forums that say it's an issue with TWRP 2.5 and that I should install 2.3, but I'm not sure how to do this.
It will take some searching on your part, but typically every version of TWRP in the KFDev forum has a recovery flashable .zip posted by other users. Or you could go to the TWRP website and download an older version and flash it in fastboot.
carlybelle said:
I'm trying to unroot my kindle fire and revert back to STOCK ROM so I can send it back to Amazon due to touch screen issues, and I've read several forums that say it's an issue with TWRP 2.5 and that I should install 2.3, but I'm not sure how to do this.
Click to expand...
Click to collapse
Use COTR instead flash it using KFU.
Thepooch said:
Use COTR instead flash it using KFU.
Click to expand...
Click to collapse
Thank you but I already bricked my kindle! Looks like it's gonna be my 10th kindle.
carlybelle said:
Thank you but I already bricked my kindle! Looks like it's gonna be my 10th kindle.
Click to expand...
Click to collapse
Nice maybe don`t attempt to modify them
Thepooch said:
Nice maybe don`t attempt to modify them
Click to expand...
Click to collapse
Exactly, I don't think I'll be rooting my new kindle fire...
carlybelle said:
Exactly, I don't think I'll be rooting my new kindle fire...
Click to expand...
Click to collapse
Very likely this go around will not be a first gen device anyway and the second gen. are a bit more complex you can actually permanently brick them. Unlike the first gen device which is nearly almost impossible to permanently brick. I would think every device you bricked was able to be repaired except the last with the touch screen issue. Unless perhaps that was just an indication of a partially corrupted system.
Thepooch said:
Very likely this go around will not be a first gen device anyway and the second gen. are a bit more complex you can actually permanently brick them. Unlike the first gen device which is nearly almost impossible to permanently brick. I would think every device you bricked was able to be repaired except the last with the touch screen issue. Unless perhaps that was just an indication of a partially corrupted system.
Click to expand...
Click to collapse
Of course, I look back on my previous kindles and realize I could have definitely fixed that if only I had the knowledge I had now thanks to guys like you all at xda!
I used kfu to install twrp2.2 but you could replace the twrp2.2 .IMG to a twrp2.3 solved!!!
Sent from my Amazon Kindle Fire using xda app-developers app
It is a rooted FireTV with I believe the version before the latest prerooted stock image.
About every 45 minutes, the whole SYSTEM reboots. I have been searching online for months, but all I see is Kodi crashing. My whole device crashes, and it's so painful to sit through a movie with 4-5 reboots randomly. Can anyone please help?
@rbox
Iamandrewj said:
It is a rooted FireTV with I believe the version before the latest prerooted stock image.
About every 45 minutes, the whole SYSTEM reboots. I have been searching online for months, but all I see is Kodi crashing. My whole device crashes, and it's so painful to sit through a movie with 4-5 reboots randomly. Can anyone please help?
@rbox
Click to expand...
Click to collapse
Try updating to the latest version? Dunno otherwise. Maybe do a factory reset.
rbox said:
Try updating to the latest version? Dunno otherwise. Maybe do a factory reset.
Click to expand...
Click to collapse
Thanks for responding so quickly.
I will update to the latest version, even though it has been happening for several versions.
If I have a fully unlocked bootloader, and everything correct; can I just click factory reset in the recovery screen, and still keep my root?
What's the best way going about this?
Iamandrewj said:
Thanks for responding so quickly.
I will update to the latest version, even though it has been happening for several versions.
If I have a fully unlocked bootloader, and everything correct; can I just click factory reset in the recovery screen, and still keep my root?
What's the best way going about this?
Click to expand...
Click to collapse
Yes. Factory reset has nothing to do with root. All it does is wipe data.
rbox said:
Yes. Factory reset has nothing to do with root. All it does is wipe data.
Click to expand...
Click to collapse
Awesome!
Final question, should I hold off on this until the Fire OS 5 prerooted image comes out? Since setting up everything how I like takes some time, I would hate to waste time setting a firmware up that I am going to reset soon.
Iamandrewj said:
Awesome!
Final question, should I hold off on this until the Fire OS 5 prerooted image comes out? Since setting up everything how I like takes some time, I would hate to waste time setting a firmware up that I am going to reset soon.
Click to expand...
Click to collapse
No clue when amazon is releasing it or when i'll have the prerooted images ready.
It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo
kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!
Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/
I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/
Hello.
A few weeks ago my wife forgot her pin to unlock phone, there was no other choice than just reset phone to factory settings via stock recovery.
Eveything was nice until phone wanted me to log into the previous google account that was used before erasing everything. My wife dont remember password and login either. She created it while ago just to use the phone.
Ive got no warranty for it as I bought it used.
Is there anyway to bypass that security? Otherwise phone cant be used again.
Thank you.
Try this... maybe? https://www.youtube.com/watch?v=uYS8Y3mt0f0
Read the description
ShaDisNX255 said:
Try this... maybe? https://www.youtube.com/watch?v=uYS8Y3mt0f0
Read the description
Click to expand...
Click to collapse
This video does not help me but I found another one which let me make my way thought security.
https://www.youtube.com/watch?v=YvEb_UD1cBc
Thanks for idea!
Zwijam_Dywan said:
This video does not help me but I found another one which let me make my way thought security.
https://www.youtube.com/watch?v=YvEb_UD1cBc
Thanks for idea!
Click to expand...
Click to collapse
Whoa, you taught me something new today :good:
It's kind of a shame it's specific to the J2 Prime phone, I wonder if there are other methods for other phones similar to this
There is a method of launching a shortcut to settings via an app installation from otg at time of setup. That works.
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.