Here we have a Flashcast flashable zip with the 13300 system and kernel, which has telnet&ADB enabled, and OTA updates disabled.
Downloads:
[PwnedCast, Replacement for this ROM]: http://forum.xda-developers.com/showthread.php?t=2515799
Old Downloads:
[V1.1 - Sep 26th]: https://mega.co.nz/#!BBllzagT!K5-OenCZNz-0f7n6XJ8ubS9roOwtxEWt3Eq54GJMqE0.
[V1.0 - Sep 21st]: https://mega.co.nz/#!hZ1ClT6T!ZNBzuzlkyZUtMMivozTGnngXPzJb7ZHlNit-c7xlCV4
Install Instructions:
Setup and Install Flashcast on a Jump Drive: http://forum.xda-developers.com/showthread.php?t=2452838
Download, and put eureka_image.zip on your Flashcast jump drive. do NOT rename the file!
Plug the Flashcast jump drive into the chromecast, hold the button, and plug in power to boot the device.
Flashing will take 5~ minutes, be patient! As long as the chromecast LED is white, it is working.
Once done, the device will reboot
Enjoy a update free, rooted system!
Thanks To:
GTVHacker
tchebb
tvall
ften
Anyone Else I Missed!
Changelog:
1.1 - Added Custom Boot Animation
1.0 - Initial Release
Extras:
Custom Boot Animation: https://mega.co.nz/#!lY8GmQiZ!ORKufk5pGXyj4uhx0xGtD3wi2BtiZZEMmOPDiYlxNTE
(This is NOT a full ROM, so this must be flashed over the firmware. If you are on version 1.1, this will not change anything. Use this to upgrade from 1.0 to 1.1 without doing a factory reset)
Expect some cool new features to show up in the next release, which will be when the new OTA hits. I'm talking SSH, DHCP DNS, and some other secret goodies.
Great work! Now I can stop screwing with a device I don't own.
I tried the above steps... I had a white light then it rebooted and gave me a red light. I proceeded anyways and threw the eureka file on the drive and then held that little button down FOREVER! it was white the whole time... it then tried rebooting but no image came up. I released the button and waited... just a white light and a black screen. I yanked everything and tried just firing it up like normal... it never shows starting chromecast it just is a black screen....
(So I had your instruction page up on my TV screen but after the reboot nothing came up it was just black with a white light) and then i tried a normal boot... nothing happens. i get no starting chromecast...
any thoughts?
doctordroid said:
I tried the above steps... I had a white light then it rebooted and gave me a red light. I proceeded anyways and threw the eureka file on the drive and then held that little button down FOREVER! it was white the whole time... it then tried rebooting but no image came up. I released the button and waited... just a white light and a black screen. I yanked everything and tried just firing it up like normal... it never shows starting chromecast it just is a black screen....
(So I had your instruction page up on my TV screen but after the reboot nothing came up it was just black with a white light) and then i tried a normal boot... nothing happens. i get no starting chromecast...
any thoughts?
Click to expand...
Click to collapse
You don't need to hold the button down the entire time (although it shouldn't hurt). You should only need to hold it for about 5 seconds after you connect the power for the Chromecast to boot off USB. It sounds like you're doing everything correctly, but not waiting long enough for the image to flash. If you see both the instructions screen and a white light, FlashCast is in the middle of flashing. Unless the light turns red, it will automatically reboot when it's done.
tchebb said:
You don't need to hold the button down the entire time (although it shouldn't hurt). You should only need to hold it for about 5 seconds after you connect the power for the Chromecast to boot off USB. It sounds like you're doing everything correctly, but not waiting long enough for the image to flash. If you see both the instructions screen and a white light, FlashCast is in the middle of flashing. Unless the light turns red, it will automatically reboot when it's done.
Click to expand...
Click to collapse
I did a second time and it now showed starting chromecast but never booted up. So this time I am doing it over and I let go the light is white... When will I know it is all done flashing??? Won't the light always stay white? I am waiting for a reboot shoudl I just let it do its thing and it will automatically reboot and start up normally if all went well or do I need to disconnect the OTG cable?
Just got a Chromecast so pardon the super noob question. If the Chromecast updates itself automatically to the newest update, will I still be able to flash this? Thanks!
doctordroid said:
I did a second time and it now showed starting chromecast but never booted up. So this time I am doing it over and I let go the light is white... When will I know it is all done flashing??? Won't the light always stay white? I am waiting for a reboot shoudl I just let it do its thing and it will automatically reboot and start up normally if all went well or do I need to disconnect the OTG cable?
Click to expand...
Click to collapse
Yes, just wait for it to reboot on its own. It will boot into the normal image unless you hold the button, so it doesn't matter whether or not you have the OTG cable connected.
its working!!!! its working!!!!!!!:good::good::good::good::good::good:
---------- Post added at 08:49 PM ---------- Previous post was at 07:55 PM ----------
Gwanatu said:
Just got a Chromecast so pardon the super noob question. If the Chromecast updates itself automatically to the newest update, will I still be able to flash this? Thanks!
Click to expand...
Click to collapse
no. it will not. the updates patch the hack
flashed over fine here, setting it up now. thanks! :good:
Gwanatu said:
Just got a Chromecast so pardon the super noob question. If the Chromecast updates itself automatically to the newest update, will I still be able to flash this? Thanks!
Click to expand...
Click to collapse
someone correct me if i'm wrong, but i'm pretty sure if you've received an update you won't be able to flash (unless a new exploit has been found).
Gwanatu said:
Just got a Chromecast so pardon the super noob question. If the Chromecast updates itself automatically to the newest update, will I still be able to flash this? Thanks!
Click to expand...
Click to collapse
Any chromecast that has been updated with any official OTA will be unable to use this. All of our current root methods require the insecure bootloader, which came stock with the chromecast. any OTA would have updated, and secured the bootloader.
when reading the instructions it says to copy the eureka.zip file to the usb and install to the chromecast. my light stays red and wont install.the link to flash cast shows copy the file with win32disk imager in the .bin file format. eureka.zip is about 85 megs and flashcast.bin is about 20 megs.
what am i missing? i thought that you can only install in a .bin format.help please.thank you.
am i supposed to use win32disk imager with flashcast.bin then eureka.zip?
Hulkanator said:
when reading the instructions it says to copy the eureka.zip file to the usb and install to the chromecast. my light stays red and wont install.the link to flash cast shows copy the file with win32disk imager in the .bin file format. eureka.zip is about 85 megs and flashcast.bin is about 20 megs.
what am i missing? i thought that you can only install in a .bin format.help please.thank you.
am i supposed to use win32disk imager with flashcast.bin then eureka.zip?
Click to expand...
Click to collapse
First you win32disk the FlashCast.bin from the other thread, and then boot it on the chromecast as is. You do this to install FlashCast to the drive. After a bit, the chromecast should reboot. Once it does, take the jump drive, plug it into a PC, and then put the eureka_image.zip on the jumpdrive. Now boot the jumpdrive on the chromecast again, and it will install the ROM.
tl;dr Read this thread, and the FlashCast thread fully.
rooted 13300 via OTA
I was wondering what is blocking us from doing a DNS hijack and do the same rooted image update via OTA method?
The below thread mentions about the OTA request response:
http://forum.xda-developers.com/showthread.php?t=2450120
So can't the response be hijacked from a local webserver and serve the rooted image as update?
-morchu
morchu said:
I was wondering what is blocking us from doing a DNS hijack and do the same rooted image update via OTA method?
The below thread mentions about the OTA request response:
http://forum.xda-developers.com/showthread.php?t=2450120
So can't the response be hijacked from a local webserver and serve the rooted image as update?
-morchu
Click to expand...
Click to collapse
All official OTA updates are signed by google, so any modified zip's would fail to flash once loaded into recovery. They also check the firmwares build date to make sure no one downgrades.
Thanks. Obviously !!!
Forgot the fact that google want this to be closed system.
So I believe it is only authentican enabled at this point. Possibly the images may become encrypted in future, if google want to keep it closed.
ddggttff3 said:
All official OTA updates are signed by google, so any modified zip's would fail to flash once loaded into recovery. They also check the firmwares build date to make sure no one downgrades.
Click to expand...
Click to collapse
morchu said:
Thanks. Obviously !!!
Forgot the fact that google want this to be closed system.
So I believe it is only authentican enabled at this point. Possibly the images may become encrypted in future, if google want to keep it closed.
Click to expand...
Click to collapse
i'm hoping on one of those smart kids out here who find a way to flash the last 13300 build.
raydekok said:
i'm hoping on one of those smart kids out here who find a way to flash the last 13300 build.
Click to expand...
Click to collapse
Unless we find a way around the bootloader, flashing won't be happening any time soon. Root shell access may be possible though.
ddggttff3 said:
Unless we find a way around the bootloader, flashing won't be happening any time soon. Root shell access may be possible though.
Click to expand...
Click to collapse
Ok ok tell me how. I Will wait and see
Verstuurd van mijn GT-I9100 met Tapatalk
raydekok said:
Ok ok tell me how. I Will wait and see
Verstuurd van mijn GT-I9100 met Tapatalk
Click to expand...
Click to collapse
There is no method or way as of yet, but if anything is found I am sure it will be shared in this forum.
First of all, thank you, @ddggttff3, for all the work you, and all other devs, are putting into this device.
Got this flashed over tvall's image.
Looks like it flashed OK: saw the info screen during flash, then it rebooted and set up screen came up.
A couple of questions:
Q1: is it suppose to say in Chromecast app: Firmware 13300 ?
Q2: I can Telnet and adb into the ChromCast fine. But after flashing this, I can't ssh in anymore... is it turned off?
Thanks
Related
I have finally received my powered OTG cable and am ready to root my chromecast, which has a vulnerable bootloader and hasn't been used. When I first looked at XDA, it seemed there was only the "GTV" method of rooting the device. I now see there is a "Flashcast" method. Which method is suggested?
Medicstud007 said:
I have finally received my powered OTG cable and am ready to root my chromecast, which has a vulnerable bootloader and hasn't been used. When I first looked at XDA, it seemed there was only the "GTV" method of rooting the device. I now see there is a "Flashcast" method. Which method is suggested?
Click to expand...
Click to collapse
Flashcast is the new suggested method because it provides a lot of cool features, such as the ability to flash mods and update the kernel.
Thanks! I'm in the process of flashing now. How can I tell if when its complete?
Followup question: How do I flash additional zips as they become available such as change DNS to unlockable
Medicstud007 said:
Thanks! I'm in the process of flashing now. How can I tell if when its complete?
Followup question: How do I flash additional zips as they become available such as change DNS to unlockable
Click to expand...
Click to collapse
You can tell flashcast is setup successfully when the device reboots back to the normal firmware, and when you plug the jumpdrive into a computer, it now shows as formatted so you can put files on it.
As for flashing, put one file on the jumpdrive at a time, named eureka_image.zip, and boot the jump drive. when it is done flashing, it will reboot the chromecast normally back to the OS. so you must flash one file at a time. Multiple file flashing is a feature that I believe is currently being worked on for flashcast.
Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?
Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0
Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.
Anyone able to help?
If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.
It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.
Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....
I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!
StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky
I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app
Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.
ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.
No worries bud
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B
Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..
Hi, I just got my new phone yesterday, and I"m having issues actually turning the thing on. Yesterday, everything was going fine. Since I got the pure edition, I went ahead and unlocked the bootloader, and then ran the Auto Root program I found in the general section. After that, I installed some apps that I needed. I downloaded some videos to watch later, I downloaded some music, and then I installed AdAway.
Here's where I probably screwed up big time: I disabled some applications from the app picker (Help, E-Mail, and a few others). I was having some trouble with the Inbox app searching properly, so I re-enabled Gmail at least, but I left the others disabled. Then I connected the phone to my Coolstream Duo, which is a bluetooth audio device, and then went to sleep.
When I woke up, I was able to unlock my phone, but I unlocked it to only the back button available and Google+ on the screen. Nothing functioned, so I force powered off. Now I can't turn the device on, it either is stuck on the "Warning, unlocked bootloader" screen, or gets to the Motorola globe boot screen, playing half the animation before the screen goes black. Once, I booted and it got past all that to the "Android is upgrading" screen, and it optomized 38 apps, but then after it got to the unlock screen, the pattern wouldn't show up. I followed these factory reset instructions: https://motorola-global-portal.cust...detail/a_id/101072/p/30,6720,9197/reg/2380937 and they didn't seem to do anything. I also attempted to download the stock image for Android 4.4.4 but it said I wasn't allowed to access the file.
If anyone could recognize what I did wrong to my phone, that would be great, and if anyone could provide a link to a factory image of the phone so I can attempt to restore it, that would be awesome as well.
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Dark9781 said:
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Click to expand...
Click to collapse
Oddly enough, directly after writing this post, I stepped out of class to find my phone had booted and was on the welcome screen. But if anything bad happens again, I'll be sure to have this link ready! Thanks for the help!
Dark9781 said:
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Click to expand...
Click to collapse
Hi,
can this stock rom get flashed trough fastboot or rsd lite? Maybe you can solve my problem!
incrazyboyy said:
Hi,
can this stock rom get flashed trough fastboot or rsd lite? Maybe you can solve my problem!
Click to expand...
Click to collapse
Either. The only thing with rsd lite is that it does not like USB 3.0. Your computer will need a USB 2.0 slot.
Dark9781 said:
Either. The only thing with rsd lite is that it does not like USB 3.0. Your computer will need a USB 2.0 slot.
Click to expand...
Click to collapse
Great! I would prefer flashing trough fastboot. Could you give me the instructions please?
Tip: When you receive your Fire 2015 tablet, don't setup WiFi if you want to install custom ROM (skip WiFi setup)
Why: They are still shipping with FireOS 5.0.1 and it will autoupdate to 5.1.1 as soon as it sees Internet connection (it doesn't ask and takes over tablet)
Why is that bad: Because it's easier to install custom ROM with 5.0 and still a pain/riskier if from 5.1.1 (as of December 2015)
Why is this method easier/safer: No need to root first, no messing with original ROM (can backup first), no need to enable Developer mode, no need to grant ADB permissions
Prerequisites:
- This method will not work if tablet has upgraded to FireOS 5.1.1 or higher, only 5.0.x works
- Need fastboot tools installed on a computer (Windows tools/drivers here if needed) or (Linux/Mac)
- Download TWRP Recovery here to same computer
- Download your new ROM/support files of choice to an external SD Card
- If on Windows, to keep things simple you might place fastboot command, Recovery image in same folder/directory
Install: Fastboot TWRP Recovery from computer, Install Custom ROM from SD Card
- When you receive Fire, don't power it on (or if you do, don't setup WiFi as it will autoupdate to 5.1.1)
- Copy your downloaded ROM image and support files to an SD card, then insert SD into tablet
- Boot tablet directly into fastboot (power button and volume up button)
- USB attach tablet to computer that has fastboot tools and TWRP recovery image
- Unlock and Boot directly into TWRP image from computer terminal or command line
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot boot TWRP_Fire_2.8.7.0_adb.img
- Takes seconds to transfer file then recovery should appear
- Optional but recommended: From TWRP, Backup Stock Amazon ROM to external SD card
- Factory Reset from TWRP Recovery
- Install ROM and support files from TWRP via external SD card
- Reboot, profit
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
xenokc said:
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
Click to expand...
Click to collapse
Did you buy it from Amazon? I just ordered mine yesterday.
stef-nix said:
Did you buy it from Amazon? I just ordered mine yesterday.
Click to expand...
Click to collapse
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
xenokc said:
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
Click to expand...
Click to collapse
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
stef-nix said:
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
Click to expand...
Click to collapse
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
xenokc said:
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
Click to expand...
Click to collapse
Gotcha. As soon as I opened it, I blocked OTA updates. Rooted/installed SuperSU, and backed up the stock ROM.
I'm currently running CM12.1 and it's working perfectly.
I did not like how it auto signed into my Amazon account once connecting to WiFi (with OTAs blocked)
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Parhelius said:
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Click to expand...
Click to collapse
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
stef-nix said:
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
Click to expand...
Click to collapse
I connected to wifi and the updates came through automatically. I hadn't read threads like this one beforehand unfortunately, so I didn't realise that would happen.
Sounds like Amazon is still shipping with 5.0.1 so this method can still apply for those who catch this thread before receiving/booting their tablet. What's nice about this method is you can backup original ROM before modding and don't need to root. Sounds like many have thrashed their tablet trying to root.
Just dont connect to wifi and your fine.
Amazon having a $40 sale, if you ordered one might not setup WiFi when first receiving - re-read first post why.
http://www.amazon.com/Fire-Display-Wi-Fi-GB-Includes/dp/B00TSUGXKE
Just ordered 3 today ... Can't wait to tinker with it.
Thanks for the heads up regarding auto-update!
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
percussionking said:
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
Click to expand...
Click to collapse
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
vn33 said:
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
Click to expand...
Click to collapse
My 4th one came from Ft. Worth. I immediately booted into recovery mode but could not boot TWRP. Obviously this turned out to be a 5.1.1 system. If this had been a 5.0.1 system, the first full boot would have been to CM rather than to stock. So if 5.1.1 is installed at the factory you can't get your TWRP on this way.
Just got mine today it had 5.0.1 creating a backup now
Hi,
where can you download twrp from their page?
I see their list of devices but none of them says fire 5th generation.
https://twrp.me/Devices/
THANK YOU!
No you get twrp from here http://forum.xda-developers.com/amazon-fire/development/wip-bootable-recovery-kffowi-ford-t3238683
I just got a kindle fie and it had 5.1.1. I was about to root it and it restarted and tried doing a system update. Is there a way to stop this. every time I try to turn it on it goes into the updating system screen... I tried hard resetting to no avail. am I screwed?
bigal115 said:
I just got a kindle fie and it had 5.1.1. I was about to root it and it restarted and tried doing a system update. Is there a way to stop this. every time I try to turn it on it goes into the updating system screen... I tried hard resetting to no avail. am I screwed?
Click to expand...
Click to collapse
It is possible to delete the pending OTA file prior to being processed ... but you probably won't get the timings right. Suggest restoring FireOS 5.1.1 via stock recovery which should trash the downloaded update file. Be sure to keep WiFi off (or airplane mode engaged) until just prior to rooting to prevent reoccurrence. Note this can only be done prior to the update being processed. Any attempt to downgrade to 5.1.1/5.0.1 from 5.1.2 will brick the device.
Also no need to register refreshed device w/Amazon if you intend to immediately root and flash a custom rom.
http://forum.xda-developers.com/ama...-amazon-fire-7in-2015-5th-gen-t3285294/page19
Davey126 said:
It is possible to delete the pending OTA file prior to being processed ... but you probably won't get the timings right. Suggest restoring FireOS 5.1.1 via stock recovery which should trash the downloaded update file. Be sure to keep WiFi off (or airplane mode engaged) until just prior to rooting to prevent reoccurrence. Note this can only be done prior to the update being processed. Any attempt to downgrade to 5.1.1/5.0.1 from 5.1.2 will brick the device.
Also no need to register refreshed device w/Amazon if you intend to immediately root and flash a custom rom.
http://forum.xda-developers.com/ama...-amazon-fire-7in-2015-5th-gen-t3285294/page19
Click to expand...
Click to collapse
Thank you so much for your help. I was unable to find the instructions in the thread you posted. Is there a specific page. Thank you again in advance.
Al
bigal115 said:
Thank you so much for your help. I was unable to find the instructions in the thread you posted. Is there a specific page. Thank you again in advance.
Al
Click to expand...
Click to collapse
See first post in linked thread.
Davey126 said:
See first post in linked thread.
Click to expand...
Click to collapse
Im not able to do this. It will not boot into recovery mode...It just goes to the update screen. I was able to get to fastboot but nothing else from there. Anyother suggestions...thank you for you help
bigal115 said:
Im not able to do this. It will not boot into recovery mode...It just goes to the update screen. I was able to get to fastboot but nothing else from there. Anyother suggestions...thank you for you help
Click to expand...
Click to collapse
Accept the update then downgrade to 5.1.2 which can be rooted. Do not attempt to go lower; device will brick.