Database Users

[GUIDE] T-Mobile G2 2.3.4 official OTA manual update

There still seem to be a few people with problems so I thought I'd try to collect the steps and add a bit more info:
Notes
- So far this is only confirmed to work on full stock 2.2. For the leaked 2.3.3 you'll need to downgrade first; see this thread: http://forum.xda-developers.com/showthread.php?t=1180733&highlight=temp+root+downgrade
- The only confirmed root so far requires s-off BEFORE you follow this guide: http://forum.xda-developers.com/showthread.php?t=1206930
- I have had no reports of anyone doing this with anything other than 100% stock recovery, hboot, etc. Please let me know if you do try and what happens; I'll update this post.
- Following this procedure will not wipe your apps or your data.
Steps
1. Download http://android.clients.google.com/p...MOUS_2.15.531.3-1.22.531.8_release_197463.zip and rename to update.zip. Turn off 'Hide extensions for known file types' and make sure it's not update.zip.zip!
2. To verify your download didn't get corrupted, check its md5sum. It should match 3c7b0c2253f72f86b06d2c85b2c8c294 (you can get a dos tool to do this here: http://etree.org/md5com.html. Run cmd.exe and type md5sum.exe update.zip from a folder that contains both files) If your result doesn't match, download again.
3. Place update.zip on the root of your SD card, not in any folders.
4. Power down your phone.
5. Press and hold both VOLUME DOWN and POWER until you get a menu
6. You may not be able to navigate the menu yet. Wait for 10-15 seconds until it says it's checking some files, then automatically returns to the menu. Now you can use VOLUME UP/DOWN to choose menu options.
7. Choose Recovery from the menu by highlighting with VOLUME UP/DOWN and pressing POWER.
8. Wait until you get a picture of a phone with a red triangle and !
9. Press & hold VOLUME UP, wait one second, then also press POWER. You should get a menu with blue text.
10. You will see "E:Can't open /cache/recovery/command" at the bottom of the screen. This is OK!
11. Again with VOLUME UP/DOWN and POWER, select "Apply sdcard:update.zip"
12. From this point, just wait until it tells you to reboot and choose that menu option. If you get any errors here, consult the troubleshooting below.
13. There are several more automatic reboots and wait screens to go. Be patient!
Troubleshooting
- "E:failed to open /sdcard/update.zip (no such filler or directory)" - your file isn't named update.zip! Reboot your phone and use Astro or another file manager to make sure you've got the name right.
- "E:failed to seek in /sdcard/update.zip (Invalid argument)" - your download probably got corrupted! Check the md5sum again, redownload, and try again!
- "assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"" - you probably don't have the latest 2.2 that this update is designed to replace. You might be on 2.3.3 or possibly the original pre-wifi-calling 2.2. To fix this, downgrade from 2.3.3 or wait for the OTA to get the newer 2.2.

Has anyone noticed any bugs in the new OTA? Waiting for bug reports before I flash.

Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App

leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.

Thank you for the link I'm updating my wife's phone tonight
Sent from my LG-P999 using Tapatalk

Cimer said:
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.
Click to expand...
Click to collapse
I don't mind losing root. I'm running stock 2.2 with s-off and clockworkmod. I just want the update to work.
The instructions above don't work for me. When I attempt an update in clockworkmod I get an error "(Status 7) installation aborted", something like that.

That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.

Cimer said:
That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.
Click to expand...
Click to collapse
Following his instructions, I get to clockworkmod recovery after step 7. I then choose update from .zip and get an error message.

attempted this with Indian HTC Desire Z and official htc update from another user with Canadian HTC Desire Z.
Getting the error: "Invalid Operation"
Why do I have an Indian HTC Desire Z ? Amazon told me it was American. I didn't know better.
How did I get the Canadian update ? A friend kept a copy of the file when he was updating his.
Ideas ?

I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
assert failed:apply_patch_check("/system/bin/dnsmasq", "0ca7c8c9c5d267665622497df4c67dec65166adb", "1d717ab5c2bfc75d16bf6a9ec7936158cdc65aef")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

Received the following error:
assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"
and a bunch of other gobbletygook...ending with
E: Error in /sdcard/update.zip
(status 7)
Installation aborted

OP needs to add "Status 7" error to OP.
You cant use clockworkmod recovery to update using the official OTA update.zip.

no - i don't have clockwork or any mods at all.. I think I screwed up the downgrade slightly, anyhow, what happened was shortly after posting this i got an OTA update that updated my system - but it didn't update it to 2.3.4 just to a newer 2.2 evidently. THEN I was able to use the update file and force it so now I have 2.3.4! (albeit still without my apps..)

wireless hot spot
can anyone tell me if wireless hotspot still works with this update?

All i know is some devs need to rip this stuff apart and get to cooking up some CM type features into it and it's my new daily driver

leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
It looks like you can't use a custom recovery to apply this update. It likely tries to verify the recovery image. You could open the update up and remove the file version verification, and various other things to prevent it from taking away your S-Off and SuperCID. You would then HAVE to apply it with a custom recovery with signature verification off.
A quick look in the firmware.zip portion of the update and you find this in an info file:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
As well as hboot_7230_Vision_GEP_0.82.0008_110413.nb0
I don't know if that info file actually does anything, but I would still start with changing cidnum to 11111111.
The real meat of what is going on is in the Meta-inf folder, that is what handles copy files and performing updates. You can simply remove things you don't want updated. If modified correctly, you could then apply a superuser su.zip before rebooting and keep root with your update.
Unfortunately, I don't know enough to trust my own handywork. Maybe some people more familiar with the innards of Anroid could help out the Vision/G2 community?

The more I look at it, the more it seems like you could just delete the recovery.img (or replace it with clockworkrecovery) from the firmware.zip and delete the assert(apply_patch_check crap from the updater-script in META-INF\com\google\android and apply the modified update.zip with clockworkrecovery (signature verification off).
You could then apply an su.zip before rebooting and you should come back up with custom recovery at least, if not root also.
No one do this just yet. Surely someone from the N1 community can guide us as to how to chop up the update.zip

Installed successfully on my stock 2.2 G2. Thanks! Was getting tired of constantly checking my phone to see if I had gotten the OTA update yet!

Well just ran this on my roomie's stock phone. Fingers crossed.........
As soon as I posted this the phone booted up. So far so good. Thanks, I was beginning to think this phone was never going to get GB.

Drthunderer said:
can anyone tell me if wireless hotspot still works with this update?
Click to expand...
Click to collapse
WiFi hotspot is working fine for me after updating.

[Q] 4.1.2 OTA update fails

Twice, actually. After the second download (courtesy of the now-warned-against 'Framework Services forcing' trick) I got the identical error message via CWM Recovery:
Code:
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Any suggestions about the next move, please?

You can't install the update from Google the natural way if you have a custom recovery. Just download the update, boot into recovery, and run the zip.

Visa Declined said:
You can't install the update from Google the natural way if you have a custom recovery. Just download the update, boot into recovery, and run the zip.
Click to expand...
Click to collapse
Thanks, I know that. I did not use CWMR for updating - The update ran - 'Installed' - conventionally both times... It made the trip into Recovery on its own where the resident tool is CWMR. Is this a known issue?
I do have a copy of the update elsewhere than in /cache in case I need to copy it back there for some possible next move.
It would be great to hear of a way to get this update to install successfully.

pofadda said:
Thanks, I know that. I did not use CWMR for updating - The update ran - 'Installed' - conventionally both times... It made the trip into Recovery on its own where the resident tool is CWMR. Is this a known issue?
I do have a copy of the update elsewhere than in /cache in case I need to copy it back there for some possible next move.
It would be great to hear of a way to get this update to install successfully.
Click to expand...
Click to collapse
This seems to be a known issue. When the update installs, it boots into recovery to install the update. If you're using a custom recovery instead of the default one, the install will fail.
The same thing happened to me. I simply copied the update .zip from /cache into a folder on /sdcard, rebooted into CWMR, backed up and installed the .zip from there. Easy peasy.

ahoyland said:
I simply copied the update .zip from /cache into a folder on /sdcard, rebooted into CWMR, backed up and installed the .zip from there. Easy peasy.
Click to expand...
Click to collapse
That's what I was trying to get the op to do in the second post of this thread, I'm not really sure if it's working for him or not

Visa Declined said:
That's what I was trying to get the op to do in the second post of this thread, I'm not really sure if it's working for him or not
Click to expand...
Click to collapse
Thank you for that, VisaDeclined & Ahoyland! I quite misread the intent of your message. 'Normal' reboot is problematic, I read, so I have downloaded 'Quick Boot (reboot)' from here (Play Store seemed to be having difficulty - maybe because I had done the 'Framework' hack earlier?) and the little thing is now done and saying 'Build No. JZ054K' . I am now a much happier bunny!
Thanks is on its way, folks.

Happiness can be so short-lived... (but good things come to those who try)
Life took a turn for the worse when I noticed that updates and downloads from Play were not getting through. The errors are:
DF-BPA-13 'trying to install',
RPC-AEC-0 'Error while retrieving information on server' &
923 (dunno)
However - THE GOOD NEWS! - I tried these two actions and all is well now:
(ex Google, the poster said)
First Make sure you're signed into Talk.
Go to setting>apps>all>Google play store
Then clear data and uninstall updates.
Then go to Google account manager, clear data and force stop.
Power off and leave it off for a minute or two, re-boot and it should work, if not go to talk and make sure you're still signed in.
Tr
y updating or downloading one thing at a time to see if it works.
Still 'RPC etc.', so
I went Settings>Accounts>Google>(account name)>(Menu)>Remove account.
Ran PlayStore,
was prompted for and re-entered my (existing) account.
Thereafter all was as before and updates were working again! :laugh::laugh:
HTH

[OTA ZIP] Pure Edition XT1095 Lollipop 5.0 22.11.6 & 22.21.11

NEW 22.21.11 OTA Zip posted on the site 12/1/14
YOU MUST BE ON 22.11.6 TO UPDATE
NEW 22.11.6 OTA Zip posted on the site 11/11/14
http://www.graffixnyc.com/motox.php
OTA is there!
Instructions:
This is ONLY for the XT1095 Pure edition.. Support priority will be given to those with a XT1095. If you have another model number you will have to figure out how/if you can run this OTA. It's not up to this thread to support devices the OTA was not meant for.
IF YOU ARE ON THE FIRST SOAK TEST OTA .5 YOU CANNOT UPDATE TO .6. IT WILL FAIL! YOU WILL HAVE TO DOWNGRADE TO 4.4.4 THEN APPLY THE .6 OTA
Follow @SolarTrans Guide found here: http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Be unaltered unrooted system. The device cannot be rooted and then unrooted.. it must be a never rooted system or the update will fail. It seems it's failing on devices that were rooted and then unrooted. On devices that were never rooted or where the user had stock back up they made prior to rooting the ota will update fine
Boot into Stock Recovery
ADB Sideload the zip
For people getting the modem error. Make sure you back up your current modem using the DD command (google if you don't know how)
After that download the AT&T modem from my website, flash it, then take the OTA. You MAY lose LTE after the update. If you do just reflash your old modem and you'll be good to go. It's also been confirmed if you reflash the AT&T modem after the update you will get LTE back.
Download Links can be found on my website: http://www.graffixnyc.com/motox.php
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....

This is going to sound really nooby but do i just flash this in recovery? Or in the bootloader?
Sorry, this is my first Moto device, have had Nexus and HTC phones before this

Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks

jellydroid13 said:
Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks
Click to expand...
Click to collapse
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?

THEindian said:
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?
Click to expand...
Click to collapse
yeah but go to recovery and sideload

I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.

dmbfan13 said:
I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.
Click to expand...
Click to collapse
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!

Can be root achieved?
sent from my Nexus 7

THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
<snip snip>
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
Same thing happened to me. I suppose we'll have to flash stock back?

THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
It seems like either the install-recovery.sh file was removed when you unrooted (SuperSU uses that file) or it detects it has been modified and is failing. You will have to ask someone to pull it from a non rooted device

I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.

Is there a guide to re-root?

will I get the next OTA if I sideload the soak test?
just wondering.

Mine is also bricked due to using unroot in supersu....

THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
I am in the same boat as you.

edwardgtxy said:
Mine is also bricked due to using unroot in supersu....
Click to expand...
Click to collapse
Yeah... mine's in a bootloop that I can't seem to stop. Holding the power button doesn't actually seem to turn it off. The screen goes black... and then eventually it just starts up again.

Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?

matt99017d said:
Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?
Click to expand...
Click to collapse
Same here.

THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
No, do not mirror my files. I like to keep count of my downloads. Get a better internet connection. I downloaded the file in less than 5 minutes as others did.
It appears you need a non-rooted system image that's never been rooted. You need to be fully stock. Not rooted and then un rooted. I believe the unrooting process still leaves files in an altered state than their original. If there is a single extra character in a file, if it's the slightest smallest difference the file is considered altered and will fail OTA checks.
Quite a few people have tried this and it has worked. It seems the ones it's failing on are ones that were rooted then unrooted. Derek Ross just told me it worked like a charm for him.

any tips to stop the boot loop? I am parking mine in recovery now to drain the battery.
Btw, it seems the OTA modified modem, system and boot. So theoretically, we can just use fastboot to go back to the your imgs, and the phone should still work right?

[ROOT, v2.0] + FireOS 4.5.4 + fully working latest GAPPS

Given, the current understanding of Fire HD, the prior instructions can be considered obsolete:
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
There is a more efficient way to get the latest GAPPS fully working, and the updates to Google Play Services no longer have to be blocked !!! Everything will be updated to the latest version. Thanks to DoLooper for helping to understand this point fully!!!
Note that the level of skill required to do this is a bit higher than just simply to get root.
0) get ADB drivers working on your PC, etc:
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Tip: A quick way to debug your adb connectivity issues is to use USBDeView : http://www.nirsoft.net/utils/usb_devices_view.html
1) Determine your FireOS version, versions up to 4.5.3 are rootable, 4.5.4 will need to be upgraded to 5.0.2 and then downgraded to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
2) Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater" http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 ),
sideload Kingroot ( http://androidxda.com/download-kingroot-application ),
and let it root. Don't bother with SuperSu at this stage, you'll get it done later.
3) install TWRP
a) either sideload "Flashify" and download the flashable image here: https://www.androidfilehost.com/?fid=24052804347756852, for convenience I attached this img in this post as well,
or
b) use this app (if it works): https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en ).
There are some other tips in this original thread by JMZ:
http://forum.xda-developers.com/fir...recovery-twrp-2-8-6-0-touch-recovery-t3129617
4) upgrade the FireOS to 4.5.4 with SuperSu and GAPPS:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
5) Optional: uninstall KingRoot app, to keep things tidy
Note that in step 4) the /system partition is formatted, so no junk from KingRoot in /system. It will still be in /data/app, so that's why you need step 5)
6) Now go explore the goodies offered by Xposed :
http://forum.xda-developers.com/fire-hd/general/twrp-xposed-modules-fire-hd-t3149990
For example, a popular request is to get wallpaper working, so read this :
http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009

2nd post :
I'll fill in some details as I get a few minutes here and there. For now everything is pretty schematic ...

has any one tried the newest kingroot 4.1.0.703 on 5.0.2, ( http://androidxda.com/download-kingroot-application )

I can confirmed KR 4.1 worked fine for me, still had no problem putting SuperSU on it and wiping /system.
[edit] Only 4.5.3, does not work on 4.5.4

Are you saying KR 4.1 will work on 4.5.4?
Thanks,
Mike

I Have tried the newest kingroot on 4.5.4 and 5 with no luck, still only 4.5.3

I've uploaded my 4.5.4 update file to a Dropbox, so now the upgrade to 4.5.4 is very straightforward, no need to mess with the repackaging, please see the relevant thread :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648

I can confirmed KR 4.1 worked fine for me, still had no problem

The posted instructions work like a charm. Thank you.

It worked like a charm, thanks ! :good:
However I have one problem, I can't get the Play Store Kindle app to work.
I have managed to find a hacked older version that works, that I have also sideloaded previously when it was unrooted.
At first, I've tried to install it through the Play store, it failed.
Then I tried to install it as an APK, it failed.
So I've decided to erase the Kindle app from /system/priv-apps (along with com.amazon.kindle.otter.apk), then it installed fine through Play Store, but the app simply crashes when launched. Any thoughts ?
BTW, why do I often see "Killed ads" popup ?

After following this and installing the update 4.5.4 zip and su zip I do not have a Nav bar anymore. Is anyone else experiencing this? It is very annoying to not have a back button or home button.

tenuis said:
It worked like a charm, thanks ! :good:
However I have one problem, I can't get the Play Store Kindle app to work.
...
So I've decided to erase the Kindle app from /system/priv-apps (along with com.amazon.kindle.otter.apk), then it installed fine through Play Store, but the app simply crashes when launched. Any thoughts ?
BTW, why do I often see "Killed ads" popup ?
Click to expand...
Click to collapse
For stock Kindle to work, just keep your Amazon experience handy as per this thread (sometimes I go back to it just for kicks):
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
Basically, when you re-enable all the Amazon stuff (and otter in particular), everything works as originally, including Kindle.
junglistknot said:
After following this and installing the update 4.5.4 zip and su zip I do not have a Nav bar anymore. Is anyone else experiencing this? It is very annoying to not have a back button or home button.
Click to expand...
Click to collapse
junglistknot said:
Edit: Another thing I am noticing is when it boots it is always asking for me to choose a language and pick my wifi connection.
Click to expand...
Click to collapse
For the language choice, is it coming from the Amazon looking interface, or Google ? Basically, there is an annoying *otter*oobe*apk in priv-apps, which I blocked by renaming.
But this tell me that you made the update zip yourself? Perhaps, something else is messed up? Get my twrp update file, and re-load 4.5.4 again, it's pretty quick:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
DoLooper's suggestion to unblock almost everything is good too.

bibikalka said:
For stock Kindle to work, just keep your Amazon experience handy as per this thread (sometimes I go back to it just for kicks):
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
Basically, when you re-enable all the Amazon stuff (and otter in particular), everything works as originally, including Kindle.
For the language choice, is it coming from the Amazon looking interface, or Google ? Basically, there is an annoying *otter*oobe*apk in priv-apps, which I blocked by renaming.
But this tell me that you made the update zip yourself? Perhaps, something else is messed up? Get my twrp update file, and re-load 4.5.4 again, it's pretty quick:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
DoLooper's suggestion to unblock almost everything is good too.
Click to expand...
Click to collapse
I did use your update file that is when it all started. Now I am stuck at 5.2.0 developers preview with no root or twrp thinking I would be able to downgrade back to 4.5.3 but I can not for the life of me figure out what I should change the values too in the build.prop file to make my fire think that the downgrade zip is a more current update. I would appreciate any help. Also, I was putting everything back to stock with the adb commands and I never seen the nav bar.

No nav bar solved
junglistknot said:
After following this and installing the update 4.5.4 zip and su zip I do not have a Nav bar anymore. Is anyone else experiencing this? It is very annoying to not have a back button or home button.
Click to expand...
Click to collapse
The same thing happened to me after I wiped. Here is how I solved it.
Flash 454 update and supersu. Reboot. Choose language. Set up WiFi. Skip registration. Reboot to recovery. Flash apps.
---------- Post added at 01:40 AM ---------- Previous post was at 01:36 AM ----------
Brofreeman said:
The same thing happened to me after I wiped. Here is how I solved it.
Flash 454 update and supersu. Reboot. Choose language. Set up WiFi. Skip registration. Reboot to recovery. Flash apps.
Click to expand...
Click to collapse
*Flash gapps

Brofreeman said:
The same thing happened to me after I wiped. Here is how I solved it.
Flash 454 update and supersu. Reboot. Choose language. Set up WiFi. Skip registration. Reboot to recovery. Flash apps.
---------- Post added at 01:40 AM ---------- Previous post was at 01:36 AM ----------
*Flash gapps
Click to expand...
Click to collapse
Thanks for the help but I am now stuck on the 5.2.0 update with no root and can't get into recovery to downgrade by adb sideload method.

junglistknot said:
Thanks for the help but I am now stuck on the 5.2.0 update with no root and can't get into recovery to downgrade by adb sideload method.
Click to expand...
Click to collapse
I'm having the same issue. Everything worked fine for me up until I got to step 2), then things went astray.
See my [Q] posted in the Fire HD 6 and 7 Q&A, Help & Troubleshooting forum.

Problem with driver in recovery mode
Hi
I have my Kindle 6" driver works fine when it's in normal mode. But when I put it in recovery mode by [adb reboot recovery], and install the 4.5.3, my computer doesn't recognize the device anymore. I check in the Windowns Device manager, it becomes [ other devices > KFARWI ]. and when I type adb devices, nothing shows up.
Please help

Don't have it in front of me but steps are like this: Right-Click KFARI/update/browse (forget name of choice, but not auto) /let me pick from list/ scroll to your installed driver and click it.

DoLooper said:
Don't have it in front of me but steps are like this: Right-Click KFARI/update/browse (forget name of choice, but not auto) /let me pick from list/ scroll to your installed driver and click it.
Click to expand...
Click to collapse
Thank you! I got it fixed by this way.
Also, I have successfully rooted my kindle 6. Then I used JMZ to install gapps, and go to play store to download Youtube. But when I open utube, it asked me to update google play service. When I tried to update google play services, it pops up an error "Insufficient storage available".
Can you suggest me a solution for this ! (I already tried to clear cache, and I still have 4GB storage)

deplepxep said:
When I tried to update google play services, it pops up an error "Insufficient storage available".
Can you suggest me a solution for this ! (I already tried to clear cache, and I still have 4GB storage)
Click to expand...
Click to collapse
It means space in /system. Get DiskUsage app to easily see free space in /System. If you have a lot--close to 1 Gb, say--I'm not sure problem. But try deleting some fat apps or move to /data. (Get an app that converts system apps to user apps. Rom Toolbox works.) I deleted the office program (mOffice, i think it's called), and converted Maps and Weather.

[OTA Update] [Oreo] Galaxy S7 Active Update to Android Oreo Guide

This Guide is one i wrote in a reply on another forum, I thought more people would see it if i posted it here as well. As usual, if you brick your phone while following this guide, it is your problem, and i take no repsonsibility for any bricked S7 Actives due to this guide. Its not likely, but in the event that it occurs, understand that it's your problem.
There is no s7 active oreo rom in ODIN flashable format available yet, but you can update by flashing nougat, and flashing two ota flashable zip files in stock recovery. If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. You can then copy this zip file to your phone's external micro sd card, without extracting it, and use stock recovery mode (turn off, then volume up + home + power) to "apply update from sd card", or if you don't have a micro sd card, click "apply update from adb" and look up "how to use adb sideload" on google. Once it's done updating, do the same thing with this zip file, using stock recovery and "apply update from sd card" or using "apply update from ADB", and you will be on android 8.0 oreo. you can always use the first file you downloaded to go back to stock nougat if you don't like oreo, but it's working great for me! Enjoy android Oreo on your S7 Active, hopefully we will see a root soon, as the nougat root just bricks my phone while it is on oreo. I do not recommend using a newer oreo OTA zip instead of the one i posted, as some of the other ones flash a newer bootloader, thus preventing a downgrade back to nougat in the event something catastrophic happens.
Reply and let me know if this worked for you, or if it didn't, tell me where the process failed.
remember to hit thanks, and if you want to support me, consider donating to me by clicking here!

Yay! Had trouble with the download stopping and varying speed download (mostly slow) but now that I've got it all went as normal.
Did seem to take a little longer than normal on the factory recovery updates but no problems to report there.
Up and running now but I've yet to play with it more than opening a few apps and testing features.
Now we need an unlocked bootloader!!! I miss having custom ROMs, debloat, and a real firewall...
Maybe someday. Maybe.

Hello
I recently installed the version G891AUCU2BQB2
Do I need to install all the files that appear in the link you gave?
Sorry about my English and sorry for the questions of a novice
Thank you

yossiv69 said:
Hello
I recently installed the version G891AUCU2BQB2
Do I need to install all the files that appear in the link you gave?
Sorry about my English and sorry for the questions of a novice
Thank you
Click to expand...
Click to collapse
I don't know what Jacob says about your doubt, but probably you can downgrade the build to the BQD4 and then install the updates until the BRB5. I did something similar, I downgrade the build BQF2 to BQD4 and then I installed the updates (the last was the build BRB5) to be able to install android oreo (build CRC7).
---------- Post added at 04:06 PM ---------- Previous post was at 03:59 PM ----------
jacoblong09 said:
This Guide is one i wrote in a reply on another forum, I thought more people would see it if i posted it here as well. As usual, if you brick your phone while following this guide, it is your problem, and i take no repsonsibility for any bricked S7 Actives due to this guide. Its not likely, but in the event that it occurs, understand that it's your problem.
There is no s7 active oreo rom in ODIN flashable format available yet, but you can update by flashing nougat, and flashing two ota flashable zip files in stock recovery. If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. You can then copy this zip file to your phone's external micro sd card, without extracting it, and use stock recovery mode (turn off, then volume up + home + power) to "apply update from sd card", or if you don't have a micro sd card, click "apply update from adb" and look up "how to use adb sideload" on google. Once it's done updating, do the same thing with this zip file, using stock recovery and "apply update from sd card" or using "apply update from ADB", and you will be on android 8.0 oreo. you can always use the first file you downloaded to go back to stock nougat if you don't like oreo, but it's working great for me! Enjoy android Oreo on your S7 Active, hopefully we will see a root soon, as the nougat root just bricks my phone while it is on oreo. I do not recommend using a newer oreo OTA zip instead of the one i posted, as some of the other ones flash a newer bootloader, thus preventing a downgrade back to nougat in the event something catastrophic happens.
Reply and let me know if this worked for you, or if it didn't, tell me where the process failed.
remember to hit thanks, and if you want to support me, consider donating to me by clicking here!
Click to expand...
Click to collapse
Hi Jacob, I have a doubt, do you have any problem with the HRM sensor? I can't use it. I could use it with nougat but with oreo it doesn't work (even if I test it in the *#0*# the sensor doesn't work). Thank you!!

Bro, I’m sorry, I can’t help, I accidentally bricked my s7 active last month, and it was hard bricked, I accidentally flashed the wrong boot loader, so I had to return it and I know how people feel about this, but there was a great deal on an iPhone 6s :/
???????????????

jacoblong09 said:
Bro, I’m sorry, I can’t help, I accidentally bricked my s7 active last month, and it was hard bricked, I accidentally flashed the wrong boot loader, so I had to return it and I know how people feel about this, but there was a great deal on an iPhone 6s :/
Click to expand...
Click to collapse
Haha. I'm thinking about getting a 6S as well. How's the standby battery life compared to the S7 Active?

Yeah, I can make it last a day, I got mine used, so my battery has 85% of its original health, I would think one with a newer battery in it would last longer, especially since this one lasts the whole day.... if you find one cheap, I recommend, but only the 6s/6s plus, not the 6/6 plus

Thanks, works great
Thanks so much, I was able to update my phone that has been off of any network for over a year. I update my S7 Active from BQH1 all the way through to CRD4, took a while having to manually update each OTA file. 6 updates later and I am running Android 8, so far no issues, no sim atm so can not tell if all functions are good, but seems to be so. Been 24 hours since and have not had a single issue. Even got it network unlocked and am running a T-Mobile sim, works like a charm.

jacoblong09 said:
Bro, I’m sorry, I can’t help, I accidentally bricked my s7 active last month, and it was hard bricked, I accidentally flashed the wrong boot loader, so I had to return it and I know how people feel about this, but there was a great deal on an iPhone 6s :/
Click to expand...
Click to collapse
Oh bro, don't worry, it's okay! Have a good life with your iPhone 6 :'v. Thank you bro!

When I try to install the BRA7 to BRB5 update, my phone gives this error.
Could someone that knows more than me interpret this for me and tell me what I need to do?
Installing update...
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: Permission denied
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCS2BRA7:user/releasekeys
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCU2BRB5:user/releasekeys
Build_number : QB16651846
Verifying current system...
e3005: "/system/SW_Configuration.xml" as unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
Successfully verify for dmverify hash tree
Installation aborted.

Trying to flash SM-G891A_G891AUCS2BRA7_USA_ATT_v7.0, but I keep getting a "md5 error! Binary is invalid" when trying to load the AP file in Odin3 v3.13. Is this legit?

what build are you on currently?

Traxxasman10 said:
When I try to install the BRA7 to BRB5 update, my phone gives this error.
Could someone that knows more than me interpret this for me and tell me what I need to do?
Installing update...
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: Permission denied
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCS2BRA7:user/releasekeys
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCU2BRB5:user/releasekeys
Build_number : QB16651846
Verifying current system...
e3005: "/system/SW_Configuration.xml" as unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
Successfully verify for dmverify hash tree
Installation aborted.
Click to expand...
Click to collapse
I am currently having this issue trying to update from S3BRD1 to U3CRE7. I was running CRD4 but downgraded so I could go up to CRE build, but no luck. Were you able to figure out what is causing this issue?

saintbump said:
I am currently having this issue trying to update from S3BRD1 to U3CRE7. I was running CRD4 but downgraded so I could go up to CRE build, but no luck. Were you able to figure out what is causing this issue?
Click to expand...
Click to collapse
Nope, still looking for an answer

Traxxasman10 said:
Nope, still looking for an answer
Click to expand...
Click to collapse
I gave up on trying to apply the CRE7 update and went ahead and settled with the CRE5 and it loaded just fine. Might have been a corrupt file, downloaded it 3 times. :silly:

Traxxasman10 said:
Nope, still looking for an answer
Click to expand...
Click to collapse
Just a thought, they recently uploaded a stock U3BRD1, which brings the bootloader to the newest (no root possible), then just OTA update from there.

Successfully flashed CRC7 on my S7 Active (I'm in Canada and can't get OTA updates).
However my Samsung Pay can no longer register my Canadian credit cards (it was working fine on Nougat build BRB5). Anyone in a similar situation?

Peace
Where can I find the file SS-G891AUCU2BQF2-to-S2BQG1-UP.zip
Thanks Yossi

yossiv69 said:
Peace
Where can I find the file SS-G891AUCU2BQF2-to-S2BQG1-UP.zip
Thanks Yossi
Click to expand...
Click to collapse
On my cloud folder there are all OTA updates. Here is SS-G891AUCU2BQF2-to-S2BQG1-UP.zip.
Russian post about all OTA updates on 4pda.ru for quick naviagation.

khaliullov said:
On my cloud folder there are all OTA updates. Here is SS-G891AUCU2BQF2-to-S2BQG1-UP.zip.
Russian post about all OTA updates on 4pda.ru for quick naviagation.
Click to expand...
Click to collapse
Thank you:good::good::good: