Update : Oct 24, 2015 It looks like the bricking scare is over, and there is an updated guide on how to upgrade to the latest Lollipop without bricking :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
PUBLIC SERVICE ANNOUNCEMENT :
There are now several reports of super hard bricks (not even Amazon logo shows up) when people attempted to load 5.2.2 version via TWRP.
My best guess is that it has something to do with the 5.x update from Amazon that people request before downgrading to 4.5.3. If Amazon is providing a newer 5.x. update, it can be blocking the older 5.2.2 from working after the downgrade-upgrade procedure. When it bricked before, it would at least show "Amazon" logo, but now even the logo is gone.
One would have to capture this current 5.x update, and see what's in it. It's probably updating another partition out of those that were previously untouched :
http://forum.xda-developers.com/fire...idden-t3122246
All the downgrade-upgrade guides are on hold for now ... You are still safe to exist in the 4.5.x space (with root).
bibikalka said:
One would have to capture this current 5.x update, and see what's in it.
Click to expand...
Click to collapse
I assume I can capture file by reversing rename of DeviceSoftwareOTA.apk but leaving OTA updating blocked. Is that the method?
EDIT: Well, just did rename. No download yet. I've got otaverifier blocked. If nothing soon, I'll enable that and block dcp.
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
All that downloaded for me were apk update files, no .data, but device>updates shows:
10.0.42-D-20150925-NA-4 is ready to install
I ran logcat during download and a couple of manual installs (pressing Install button, but I do have updates blocked). I didn't see anything obviously related to update in the logcats, but not sure what to look for. Since I didn't get the .data, will I find anything helpful in logcat? What should I look for? thx
p.s., Or must I unblock updating to capture?
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
Yep, this is weird. I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Another poster indicated that the tablet rebooted about 3 times, and then he got new icons and Amazon launcher :
http://forum.xda-developers.com/showpost.php?p=63116048&postcount=141
bibikalka said:
I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Click to expand...
Click to collapse
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
DoLooper said:
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
Click to expand...
Click to collapse
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
bibikalka said:
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
OK, I'll try this later or tomorrow. Still wonder though, couldn't you--anyone on 4.5.5--leave OTA package blocked but rename OTAsoftware extension back to apk, allowing the update to download but not install?
)':
Hello, I am french sorry for my english
My kindle fire is bricked
how to repair !! :crying::crying:
help me please :/
bibikalka said:
. . . At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks! (Edit: NVM--I see your explanation above.)
EDIT @bibikalka, @everyone Thought the update was out for my region, but guess not: With DeviceSoftareOTA.apk named as originally and otaverifier enabled, Device>Updates just returns "no updates." Disabled otaverifier again and will wait on this.
I believe the update will download with DeviceSoftwareOTA.apk properly named--and hope it won't update with otaverifier disabled. So maybe I can get it. Anyway, I'll check for it over next few days, but maybe someone else will try this method first. (I am west-coast US and it seems always last to get updates.)
DoLooper said:
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks!
Click to expand...
Click to collapse
I think it will prepare to update by staging the required files in /cache, but then it'll try to reboot to apply those files (usually updates are applied in recovery ...). So when reboot fails (as it should with TWRP & 4.5.3 bootloaders which don't boot Lollipop), you intercept the stuff in /cache and see what it has.
Added: If this works, do wipe /cache before leaving TWRP (when you restore 5.2 bootloaders). This way it won't pick up the scripts and run them ...
See edit here. Forgot that I'm always last to get an upgrade. Hope someone who might get it sooner will use bibkalka's method so we can get this show back on the road.
After downloading the 5.0.1 update once I have been unable to get it again. My build number has not updated so its possible they pulled it. Root etc still works so it doesn't look like it applied.
Hello, just wanted to say that I can testify to the fact that after updating to 5.2.2, then downgrading and going into TWRP, flashing all the zips, and then wiping cache before rebooting..... gets you a BRICK!! I've stupidly done it.... to my replacement from Amazon! Hopefully sometime in the future someone can get me out of this one....
hello there recently my rooted fire os 5 with xposed playstore just updated to 5.0.1 by it self and i swear i did have com.amazonotaverifier blocked its weird because it updated when i left my fire hd 6 on charge
it just updated itself to fire os 5.0.1 il stay on that fire os because people are saying you get bricked if you do the whole procedure like downgrade back to 4.5.3 and root and get custom recovery and flash all the zips = brick
2nd try to get 5.0.1 update
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
------------------------
EDIT: NVM below! I'm getting # prompt because I recently set "adbd insecure" app to start at boot <doh> .
Second, I decided to start over and see if there was a different update waiting. So:
1. Went to twrp and flashed 5.2.0_stock_recovery_uboot.zip (for 5.0 stock recovery and bootloaders, i hope), wiped cache, and booted to OS.
2. Got l o o o n g startup. When OS finally loaded, "adb shell" hung CMD. I had to run TASKKILL /F /IM adb* >nul 2>&1 before adb shell was recognized. And when it was, it consistently returned # prompt: ([email protected]:/ #)
I'm definitely rooted, all google works, version still shows 5.0.0, build date July 20, but even after rebooting both tablet and computer, "adb shell" still always returns # prompt.
Can anyone tell me what's going on here? (Sorry this is tldr; hope a few of you slog through.) Thanks.
EDIT: it's late, maybe I'm nuts, but seems "adb shell" should return $ prompt, then "su" returns #.
DoLooper said:
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
.
Click to expand...
Click to collapse
These updates appear to be just individual apps, nothing to do with the system. You can google the version numbers, and it'll find that stuff.
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
bibikalka said:
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
Click to expand...
Click to collapse
Would that mean 5.0.1 would not be rootable?
Hello, I am curious, would it be possible to use "fastboot boot recovery.img" instead of actually flashing it in order to get root in the new 5.2.2 (build date sep 23)? It seems this would solve the hard brick problem with flashing twrp.
I'm on a never-rooted 2014 HD6 with gapps & OS 5.2.2. Very interested in rooting this tablet.
hi,
my Eng is not good, i don't understand the title
Stop !!! Do not upgrade to lollipop via twrp !!!
on today i'm receive Fire HD 7 from my phone provider. This is free.
i was rooted it with kingroot. It was succesfull. But i want setup it with android with vietnames because my boy are 10 age.
it run fire os 4.5.3 now.
can i upgrade to android 5.x?
thank for read
Related
Update2: Updated for FireOS 4.5.5.1. Note that you can root 4.5.5.1 directly via Kingroot. With root, you could get TWRP to work, and re-install any FireOS 4 or 5 with all the goodies. The instructions to get TWRP working are here (you need to flash 4.5.3 bootloaders if you do not start with FireOS 4.5.3 !!!) : http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Update: I had a couple of knee-jerks, but realized that I can make TWRP say "full_ariel" (I've changed the string), which enables the standard Amazon update files to work !!! I did test the modified TWRP (and the attached zips), everything works fine.
This 4.5.5 update provides no perceptible difference with 4.5.4, and everything has been running smoothly for me for the past few weeks. So out of the general principle I do recommend upgrading!
If you are just joining us, and have a pristine Fire HD, head over here to get your fire rooted and TWRP installed [all steps up to and including 3) ] :
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
With TWRP installed, there is a quicker way to install 4.5.5, without changing the update file (in contrast to my earlier instructions for 4.5.4). This is a dirty flash, and will keep all the prior settings and programs (if you have not had GAPPS yet, see additional instructions below):
0) Turn off wireless (airplane mode)
If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Boot into TWRP, flash the attached 4.5.3_twrp_recovery_full_ariel_string.zip. Reboot to recovery (TWRP)
2) While in TWRP (this modified version self-identifies as full_ariel) :
a) flash the respective Amazon ROM 4.5.x update (the latest one?): http://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102 (rename to zip before flashing)
b) Must do this (!!!) - flash attached 4.5.3_twrp_recovery_uboot.zip
c) flash attached make_space_v01_fireos4.zip to remove moffice and weather in order to increase space in /system.
d) flash Pico (Uni) GAPPS for KK http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html [if you did not have GAPPS before, skip this for now, and come back after Step 3) ]
e) wipe cache and dalvik
f) before reboot say yes to root
3) Boot into fireOS (wait for it to upgrade)
a) install SuperSu
b) disable OTA updates [in ES Explorer rename /system/priv-app/DeviceSoftwareOTA.apk to *apk_ ] - The script in make_space*zip already renamed this file automatically, so nothing to do here.
c) install Xposed. Note if you are using 4.5.5.1, you'll need to get the Xposed installer from here in order to address SDK version 19 error :
http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
d) install Busybox
Optional 4) : if you did not install GAPPS in 2), boot to TWRP, and install GAPPS
That's it! Whatever you had working before, should be working now the exact same way.
If you prefer a manual way where you repackage the 4.5.5 update file (and perhaps remove some apps from /system), see these instructions (the updater-script is the same) :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
This package is for "full_ariel" products: this is a "omni_ariel"
E:Error executing updater binary in zip '/sdcard/Download/update-kindle-20.1.5.5_user_455001420.zip'
Click to expand...
Click to collapse
Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...
bibikalka said:
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...
Click to expand...
Click to collapse
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...
Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
meatwad12 said:
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...
Click to expand...
Click to collapse
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.
I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.
DoLooper said:
I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.
Click to expand...
Click to collapse
Wow, you are a hard man to please I've put a few changes in there, trying to make it more clear.
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.
bibikalka said:
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.
Click to expand...
Click to collapse
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx
DoLooper said:
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx
Click to expand...
Click to collapse
Potentially this will supersede this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
The difference is mainly not having to mess around with the update file (which has it's uses, if one wants to shrink the size of "system").
bibikalka said:
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.
Click to expand...
Click to collapse
This worked great for me. I have 4.5.5 running with the stock amazon ROM after following these instructions. Great work thank you!
---------- Post added at 03:19 PM ---------- Previous post was at 02:24 PM ----------
One problem...
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?
meatwad12 said:
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?
Click to expand...
Click to collapse
Did you put a space in "S ervice?" There is none, but it may display that way. So if you did, do it with no space and reboot afterwards if ads don't go away immediately. The other way is JMZ fire tool, but that does a chmod on ad folder and displays the "killed ads" message with every boot.
Please let me know if the pm block pm disable works or not. Thanks!
Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.
meatwad12 said:
Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.
Click to expand...
Click to collapse
Or u can upgrade to lollipop. Ads are disabled by default on lollipop. Here is the thread to lollipop with root. http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition
mehmehmeh said:
I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition
Click to expand...
Click to collapse
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again
mehmehmeh said:
flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again
Click to expand...
Click to collapse
Well, as they say, practice makes perfect !
I am surprised it managed to install itself with TWRP present instead of the stock recovery ...
Can you please upload the attachments to a file hoster cause the servers from xda are slow 14 kbps and downloads cancels!
bibikalka said:
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
Click to expand...
Click to collapse
Thanks for the tip!
Ran into the same issue while trying to upgrade my rooted 4.5.3 gapps Firehd 7..
Mhm Ok now I'm running into issues when trying to update the google play services, it always fails saying "not enough space available".
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
I've moved all the odexed system APKs mentioned in this post to /data/apps and I have 1.5gb free on the "sdcard".
:/
*Edit*
Nvm, found the reason...it's because I allready had gapps installed through jmz's tool and it blocked play services updates from being installed, because back then a play services update would break the entire thing again.
So I had to do these additional steps from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
Click to expand...
Click to collapse
@op maybe include it in your updated guide for ppl who allready had gapps and used jmzs handy tool a couple months ago.
Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay
jayp57 said:
Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay
Click to expand...
Click to collapse
the thing is that not always the 'unroot' works for doing a system update, the unroot (have you performed the full one?) could leave behind modified binaries or maybe apps you installed have did that (for eg if you installed busybox it will leave the new binary) and the first step of the OTA update is to do a check of all the files that are going to be updated (patched) and if one of them doesn't match the sha1 checksum the update will abort (will not change anything on your tab when aborting). you can fix it by:
1. (complicated) restore the orginal files (you can check the recovery log on your cache partition to see where it failed)
2. (recommended) flash a stock rom matching your existing Android (you are on lollipop so you can use this for a stock lollipop install)
ps. factory reset doesn't save, that one just erases 'data' partition, has nothing to do with the ota (that usually updates files on the 'system' one or the 'boot/recovery/fastboot' partitions)
Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay
jayp57 said:
Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay
Click to expand...
Click to collapse
if you start with tmp_root it will open an early adb shell as root (regardless of whether your tab was or not rooted)
check after you shell in to see if the /cache is mounted (input a simple mount) and if it is not you need to mount it
afterwards you will need to go and do an adb pull on your recovery log (if i recall is on /cach/recovery ) and check inside to find on what did the ota failed
however this is cumbersome and even if you find on what it fails you still will have to find the original files (and after you try to OTA again it can fail many more times on other files as the OTA is aborted on the first non matching file and if there are many you will need to repeat these steps over again). i never did this, i am just saying that it could be done, but why would one waset maybe hours just so he can bring his system back to the same state it could bring in 3 minutes by flashing a stock rom? but if you want the complicated way feel free
if i were you i would just flash the stock rom in 3 minutes (that is how long it takes) and move along
what security reasons you are talking about?
I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.
jayp57 said:
I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.
Click to expand...
Click to collapse
oh, i see... i doubt they are tampered by anyone (except Lenovo of course ) the files i provide have already been used by others (and if they were to be tampered they would have failed future OTA's, the boot image is checked and it won't load if modified etc)
as a personal thought, to tamper a stock rom (to whatever purpose one would want) so that they cannot be detected by a future ota requires a level of knowledge that i think keeps us safe (i think one who is able to do such a thing would not 'waste' his time and resources on doing it to a normal/casual user like we are), so if you are able to take ota's you can safely assume that the files are the ones Lenovo put in there (not to say that Lenovo could not do funny things tho)
i wish you to become so important that one day this could be a real concern
yeah you are right.
thanks for your support. i managed to update my tablet.
Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.
saupiquet said:
Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.
Click to expand...
Click to collapse
the link is in my first reply here
Hi everyone,
Since Wileyfox didn't want to supply us with Recovery and Fastboot images, and the update has arrived to my phone already, I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
INCREMENTAL UPDATE (OFFICIAL LINK) (DRIVE MIRROR LINK by me) (from TOS118C to TOS163B / from aa4d5d86bc to 8eec3af77b)
Just as I have commented earlier,
linuxct said:
If you directly click (the official download link), it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX wfotaagent/2.3 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
Click to expand...
Click to collapse
Please, note the UA string has changed from rsotaua 1.0 to wfotaagent/2.3, which makes a bit more sense. Enjoy!
Thank you!
Can I update my phone with the OTA-File with TWRP?
For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
BTW, if you are using Linux (or any other OS providing wget, I have actually only used it for Linux so I'm not sure if it's available for other OS) you can easily download the package:
Code:
wget --user-agent="wfotaagent/2.3" LINK_TO_OTA_AS_I_HAVE_TO_REMOVE_TO_BE_ALLOWED_TO_POST_UNTIL_I_REMOVE_THE_LINK
I am currently downloading it although I don't know if it will be useful to me.
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.
Cappucinto said:
Thank you!
Can I update my phone with the OTA-File with TWRP?
Click to expand...
Click to collapse
mdosch said:
For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
Click to expand...
Click to collapse
You will need to reflash AOSP's recovery in order to install this update, but please do note it's an accumulative patch, not a "Patching system image unconditionally" kind of installation. If the contents of the system partition, or the boot image (yes, that's for us magisk users out there) are unexpected, it will stop the update, and probably try to roll it back.
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
mdosch said:
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.
Click to expand...
Click to collapse
It's sad that XDA does that to junior members, tbh. With ten posts they'll remove all those restrictions, though. At least to me, it'd feel bad losing the interest of advanced users that might be new to the forum, yet are experienced in the topic.
linuxct said:
Since Wileyfox didn't want to supply us with Recovery and Fastboot images
Click to expand...
Click to collapse
I'm guessing they will release those eventually, right?
linuxct said:
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
Click to expand...
Click to collapse
Hi can I have a link to the AOSP recovery please
Ok, I'll give this site a new try using a temporary fresh profile to not have to spoil my browsers settings.
After some playing around I got 7.1.2 installed and rooted. I'll write down what I did to get it finally work, but YMMV so be aware you might brick your phone.
I was using Debian 9 with fastboot and adb installed.
The steps I did:
Download and unzip the fastboot image from this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Boot to stock recovery and choose "apply update from adb"
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
After successful install wipe cache and dalvik/arts cache and reboot to system with the following command:
Code:
adb reboot "dm-verity enforcing"
When the update is configured let the phone switched on for a while (I don't know why, but it ended in a bootloop and I had to start again when I instantly rebooted)
After a while boot to bootloader.
Boot (not flash) twrp: http://twrp.me/devices/wileyfoxswift2.html
Code:
fastboot boot twrp-3.1.1-0-marmite.img
Go to "ADB -> Sideload" and install Superuser: https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Code:
adb sideload superuser.zip
Wipe cache and dalvik/arts cache and finally reboot with this command:
Code:
adb reboot "dm-verity enforcing"
I am not 100% sure if all steps are necessary but finally this worked for me and I am enjoying an up-to-date OS without loosing root.
I've downloaded the update as my 2X still hasn't updated.
I just cant get it to update via the recovery, my phone is default, no mods. I go to update from SD and it just errors with failed to mount SD. Even tried another SD card, same issue.
Am I missing something here? Cant be anything extra needed surely?
linuxct said:
I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
Click to expand...
Click to collapse
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.
boa05 said:
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.
Click to expand...
Click to collapse
I put my windows pc in router mode using the wifi adapter, and ethernet bringing internet connection. Then it was as easy as capturing just that traffic.
Deleted due to development of Android ROM version
Hi!
As Wileyfox issued another OTA today and the last time I had a hard time to find the proper information, I thought I'd start a thread that contains the update information and links for ALL OTAs in one place right at the start.
But first of all: This would not be possible without linuxct and mdosch who delivered this information in a combined effort. I added only a few things, like the new updates and put everything in one place.
1. The official update links from Wileyfox (partially from here, here and myself):
TOS118C (Recovery Image)
TOS163B (Recovery Image) Deleted by Wileyfox
TOS208G (Recovery Image) Deleted by Wileyfox
TOS249H (Recovery Image)
TOS319I (Recovery Image) Deleted by Wileyfox
TOS373J missing
UOS224B missing
UOS273C (Recovery Image)
TOS118C (Fastboot Image) Deleted by Wileyfox
TOS163B (Fastboot Image) Deleted by Wileyfox
TOS208G (Fastboot Image) Deleted by Wileyfox
TOS249H (Fastboot Image)
TOS319I (Fastboot Image)
TOS373J (Fastboot Image)
UOS224B missing
UOS273C missing
TOS089A to TOS118C (OTA Update)
TOS118C to TOS163B (OTA Update)
TOS163B to TOS208G (OTA Update)
TOS208G to TOS249H (OTA Update)
TOS249H to TOS319I (OTA Update)
TOS319I to TOS373J (OTA Update)
TOS373J to UOS224B (OTA Update to OREO 1)
UOS224B to UOS273C (OTA Update)
TOS373J to UOS273C (OTA Update to OREO 2)
2. The instructions how to make the OTA links work (taken from here):
If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible. Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string. Now here's the thing: if you want to switch the UA you'll need an extension to do so. linuxct has used this one and on Firefox I used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
As I just found out: The "User Agent Switcher" for Chrome works just as fine.
3. The instructions how to update a rooted phone (taken from here):
I'll write down what I did to get it finally work, but be aware you might brick your phone. I did this with Windows 7 and 10 successfully with fastboot and adb installed.
3.1. Download and unzip the fastboot image from point 1. Then switch to fastboot mode and flash boot, recovery and system.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
3.2. Boot to stock recovery and choose "apply update from adb". Then sideload the update.
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
This is, of course, an EXAMPLE! You have to put in the name of the actual update you want to do.
3.3. After successful install wipe cache and dalvik/arts cache and reboot to system. If you have issues with "dm verity" do it with the following command (I myself didn't need to do it):
Code:
adb reboot "dm-verity enforcing"
3.4. When the update is configured let the phone switched on for a while (I don't know why, but mdosch ended in a bootloop and had to start again when he instantly rebooted, I myself didn't need to wait). Here you can already put the SuperUser ZIP-file onto your phone via USB (or do it later via sideload).
3.5. Then boot to bootloader and BOOT (not flash) TWRP
Code:
fastboot boot twrp-3.1.1-0-marmite.img
3.6. If you have the SuperUser ZIP-file already on the phone flash it, otherwise go to "ADB -> Sideload" and install there
Code:
adb sideload superuser.zip
3.7. Wipe cache and dalvik/arts cache and finally reboot. Again, if you have issues with "dm verity" do it with the following command (I myself didn't need to do it)::
Code:
adb reboot "dm-verity enforcing"
This is how it worked for me in Windows 7 and 10 on my Wileyfox Swift 2 Plus. Neither did I brick my phone, nor did I loose ANY(!) data, neither from storage nor from any app. But as I don't know what you did with yours I won't issue any warranties here...
BTW: If you ever wondered, when you do the OTA the phone saves the zip here: data/data/com.android.providers.downloads/cache
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
And also thanks to image45 and DIMICH666 for getting hold of some more of the image links.
Thanks, wish I had found this 2 hours earlier! I had been downloading the OTA update but it was failing to install. Spent ages searching my phone for the location of the download without success. Eventually connected my phone to my laptop and did 'adb logcat' - found the URL of the OTA File download "http:\/\/ota-files.wf.bsp.ninja\/marmite\/wf-marmite-8eec3af77b-to-0fcf4099d0-signed.zip". Changed 'User Agent' as described, put the URL in the address bar and hit enter and hey presto! Good to have a repository to refer to.
Hi
I'm already on TOS163B. Can I just sideload the TOS208G OTA zip? Without reflashing the boot, recovery and system images from TOS163B?
The images from TOS208G are not available.?
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
(... I dream about Lineage 14.1)
H2Oxide said:
Thanks for this.
(... I dream about Lineage 14.1)
Click to expand...
Click to collapse
We all do, I tried an unofficial build however no WiFi yet :crying:
Even with an official build we would still have the unlocked bootloader warning screen and the dm-verity screen that threatens to switch your phone off in 30 seconds if power not pressed. I am sure it only gave you 5 seconds then just continue to boot when running on the Cyanogen ROMs
I am sure there is some ADB the resolve this for the oneplusone phones.
After initial boot the ROM got stuck on the white splash screen. After I installed Magisk via TWRP flashable zip it worked so must need dm-verity switch off.
I never updated back at the end of 2016 because I was unsure if it was a good idea but now I've become annoyed by it constantly asking me to (OTA UK). Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
quixoticduck said:
Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
Click to expand...
Click to collapse
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
However like I said at start of post what do you need from your phone/ android version?
image45 said:
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
Click to expand...
Click to collapse
Thanks, I see what you mean, about it being personal preference. The last couple years I've stepped away from rooting and flashing roms, so right now I suppose all I really want is a stable safe version. Back in 2016 I remember people being worried about the OTA update released right after Cyanogenmod's end, with people thinking the new update might be suspicious (why I never updated, and then stopped following things). So if it turned out that the OTA update was fine then I suppose the easiest and safest way to stop it bugging me about the update might just be to update xD as long as there's no risks (besides the basic risk that any update could bring). Probably makes it easier for any further updates too if any appear.
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
quixoticduck said:
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
Click to expand...
Click to collapse
You need an unlocked bootloader and custom recovery to install xposed framework. However I can jump between any of the Swift 2 ROMs when ever I wish of course.
Currently on the update right before that one, with TWRP and Magisk installed. I found the zip as instructed. Has anybody had success with Flashfire for a small OTA update like this or do you absolutely have to use adb sideload?
Don't know whether I can post links to other sites but there are instruction on how to update to 7.1.2 using the OTA file for both rooted and non-rooted devices at
http://www.stechguide.com/install-android-7-1-2-nougat-on-wileyfox-swift-2/
H2Oxide said:
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
Click to expand...
Click to collapse
Any thoughts on this? Can I force a sideload or would that be unwise...
der_dkw said:
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
Click to expand...
Click to collapse
Sure that's fine.
I really appreciate you collected all the information and created this overview.
Well I finally managed to try the adb sideload and this is what I got.
What's wrong here?
I'm using TOS163B (7.1.2) so I don't know why it says I have 6.0.1 test keys. I'm trying to sideload TOS208G
Any help is much appreciated
Jack3volution said:
What's wrong here?
Click to expand...
Click to collapse
You are using TWRP not stock recovery.
The OTA zips check your device for not being altered (like rooting or using custom recovery) this is why you have to go to a plain stock rom while flashing boot, recovery and system from the fastboot image (not the complete image as it will erase your data as well I assume).
After you have done this boot to stock recovery and adb sideload the first OTA zip then reboot and so on until you are on the latest.
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Thanks! my mistake. Yeah I still have stock recovery
Cheers
mdosch said:
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Click to expand...
Click to collapse
What's the actual different between booting TWRP and flashing please?
image45 said:
What's the actual different between booting TWRP and flashing please?
Click to expand...
Click to collapse
Booting means you boot TWRP temporarily without replacing your stock recovery. Flashing means you replace the stock recovery with TWRP.
mdosch said:
You are using TWRP not stock recovery.
Click to expand...
Click to collapse
Hmm it didn't work in stock recovery either
Jack3volution said:
Hmm it didn't work in stock recovery either
Click to expand...
Click to collapse
Did you apply the OTA zips in the correct order?
Did you alter your devices in any way like rooting or installing magisk?
You are on TOS163B you said. Did you start your device before booting to recovery? For me after sideloading the TOS163B, sideloading of TOS208G failed when I tried to install it instantly so I cleared the cache/dalvik cache booted to Android, then rebooted to (stock) recovery again and successfully sideloaded TOS208G.
Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.
Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.
Confirmed, it works on the cube (stark) as well...
That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.
Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.
2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.
How may I get the "su". It said, I don't have permision.
eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?
eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work
Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.
moving it to the right place.
anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?