Database Users

Custom Recovery for ATT Samsung Galaxy TAB 4 8.0

Hello. Sorry if I sound like a COMPLETE noob here and if I posted in the incorrect place.
I am going to start from the very beginning so I can explain myself.
I am currently on a mission to be able to play Pokemon GO on my tablet and spoof my GPS without getting banned. Ill be running it on an account that I wouldn't care if it was banned so please do not just tell me to not do it.
First of all I had manually installed an update to lollipop (5.1.1) when first receiving the tablet. This was still Samsung official OS. In order to obtain my goal I had to root it. So after trial and error I managed to get my device rooted using KingRoot. Couldn't understand a damn thing because it was in Chinese but it was still successful.
This allowed me to install my GPS spoofer hider (supposed to hide GPS spoof from GO). Now it seemed promising until it told me I needed Xposed framework installed. Went to go install it however now I need a custom recovery manager to install that. I have checked with both ROM Manger and TWRP but I cant find my device. I assume its not supported by either.
Is there any decent custom recoveries that will work for my device or have I hit a complete dead end? Maybe someone might even have a COMPLETELY different approach to accomplish my goal. I don't know if you need this to answer my questions but here is everything that seems relevant in about my device.
----------------------------------------------------------------------------------
Model Number: SAMSUNG-SM-T337A
Android Version: 5.1.1
Baseband version: T337AUCU2BOH44
Kernel Version:
3.4.0-5608828
[email protected]#1
Thu Aug 13 17:01:34 KST 2015
Build Number: LMY47X.T337AUCU2BOH4
-----------------------------------------------------------------------------------
I would also like to say thank you. Not just for helping me directly in my situation but for everything. MANY of times I have wanted to do something on my phones and other android devices and I would always end up in these forums and get everything I needed. You guys are the best!

Update.
I have been reading deep in the threads. This tablet seems to be one of THE MOST frustrating android devices to try and work on.
This is what I have tried to this point.
Doing a little more research I found that I could use flashfire to get Xposed working. Thats when I ran into another problem. flashfire will not work with kingroot and will with SU.
Despite all the warnings, I tried to use SuperSUme and install superuser over the kingroot to remove it.
Softbrick..
Put it into download mode and reinstalled 5.1.1 which fixed it, buuuut now I have no root.
This led me to look into kingroot a little more and much like others, I have found kingroot to be a little too shady for me. I will not be using the kingroot path again.
1 step forward, 10 steps back.

I am currently working with someone else on the forums here to see if we can work on a way to get TWRP to work on the tablet. If we are successful then chances are I will be able to downgrade the OS back to 4.2.2 KitKat. My understanding is that OS is rootable for this tablet. After that I am going to look into a way to unlock it so I could possibly use it for cricket. I don't exactly have high hopes for it but it is worth a shot.

Custom recovery may be achievable but please do not kid yourself, you will end up with a brick if you try to downgrade the os

Us M3 updated to 5.0 but issues now

Hey Guys,
I tried updating my tablet from 4.1 to 5.0 and now i am having some issues. I have no keyboard and my fingerprint sensor doesn't work anymore. So i have no way of doing anything. When I try to bring up the keyboard i get the google voice window.Build number shows BTV-W09C128B350. Trying to understand the steps i need to do to get my tablet back and running normally. Do I need to go back to 4.1? Any help would be greatly appreciated.
Thanks
Erik

lamstang94 said:
Hey Guys,
I tried updating my tablet from 4.1 to 5.0 and now i am having some issues. I have no keyboard and my fingerprint sensor doesn't work anymore. So i have no way of doing anything. When I try to bring up the keyboard i get the google voice window.Build number shows BTV-W09C128B350. Trying to understand the steps i need to do to get my tablet back and running normally. Do I need to go back to 4.1? Any help would be greatly appreciated.
Click to expand...
Click to collapse
How did you do the update? Did you use Firmware Finder and it's DNS update or did you use the dload folder method? I used the Firmware Finder method and everything went smoothly even with an unlocked bootloader, You might try to use that method to reinstall Nougat, but you will need a keyboard to change your DNS settings to the one Firmware Finder needs and for that I suggest you try a USB keyboard connected through an OTG cable.
I will say that once you get Nougat working, the 5Ghz radio goes back to not working and the file that needs to be updated to enable it seems to have changed. So far, I can not find the correct file/setting to change to enable it. For me it is more annoying that I can't get it working than necessary because I am getting between 20 and 40 Mbs with the 2.4Ghz radio and that is plenty fast for what I ask this tablet to do.

johje said:
How did you do the update? Did you use Firmware Finder and it's DNS update or did you use the dload folder method? I used the Firmware Finder method and everything went smoothly even with an unlocked bootloader, You might try to use that method to reinstall Nougat, but you will need a keyboard to change your DNS settings to the one Firmware Finder needs and for that I suggest you try a USB keyboard connected through an OTG cable.
I will say that once you get Nougat working, the 5Ghz radio goes back to not working and the file that needs to be updated to enable it seems to have changed. So far, I can not find the correct file/setting to change to enable it. For me it is more annoying that I can't get it working than necessary because I am getting between 20 and 40 Mbs with the 2.4Ghz radio and that is plenty fast for what I ask this tablet to do.
Click to expand...
Click to collapse
i Johje,
I was able to rollback to Android 6.0 and 4.1. Do you have instructions on how you did the Firmware finder update?
Thanks again for your help
Erik

I used Firmware Finder to update to the most recent Full Update for the US version. After Selecting the firmware choose "Get an update through DNS" and follow the instructions. This will install the beta Nougat and restore your recovery partitions even if you have an unlocked bootloader. Once the tablet has Nougat installed, root by installing TWRP to the Recovery2 partition which will replace eRecovery and leave your main recovery in place. Use TWRP to Flash Magisk and PHH Superuser to root the tablet because from my experience SuperSU does not work for Nougat on this table. Once rooted you can enable the 5Ghz radio by finding the "cfg_btv_hisi.ini" file in the "cust_spec\vendor\etc" directory and then just change "band_5g_enable=0" option to "band_5g_enable=1" , after rebooting the 5Ghz wireless will be enabled.
Hope this helps

johje said:
I used Firmware Finder to update to the most recent Full Update for the US version. After Selecting the firmware choose "Get an update through DNS" and follow the instructions. This will install the beta Nougat and restore your recovery partitions even if you have an unlocked bootloader. Once the tablet has Nougat installed, root by installing TWRP to the Recovery2 partition which will replace eRecovery and leave your main recovery in place. Use TWRP to Flash Magisk and PHH Superuser to root the tablet because from my experience SuperSU does not work for Nougat on this table. Once rooted you can enable the 5Ghz radio by finding the "cfg_btv_hisi.ini" file in the "cust_spec\vendor\etc" directory and then just change "band_5g_enable=0" option to "band_5g_enable=1" , after rebooting the 5Ghz wireless will be enabled.
Hope this helps
Click to expand...
Click to collapse
I have also tried to update to 5.0. Everything seemed fine, but there is no keyboard, calc, file manager, etc. The "full..hw.." update seems to go really fast and it says it's done but there is no difference in what is on the tablet. Now I'm stuck at the point where it's A7.0, but I cannot do anything. Try getting google voice type to enter a complex email password
Any help on the second phase of the update is appreciated.
USA
C128
B350
used dload method to load.

nostep said:
I have also tried to update to 5.0. Everything seemed fine, but there is no keyboard, calc, file manager, etc. The "full..hw.." update seems to go really fast and it says it's done but there is no difference in what is on the tablet. Now I'm stuck at the point where it's A7.0, but I cannot do anything. Try getting google voice type to enter a complex email password
Any help on the second phase of the update is appreciated.
USA
C128
B350
used dload method to load.
Click to expand...
Click to collapse
Can you use Firmware Finder in your tablet's current state? If so, try updating using Firmware FInder's DNS method. You will need to be able to update your network DNS settings, though. Have you tried using a corded keyboard connected through an OTG cable or a bluetooth keyboard?
I did not try using the dload method because earlier attempts an updating Marshmallow to a more recent build always failed because of my unlocked bootloader.

johje said:
Can you use Firmware Finder in your tablet's current state? If so, try updating using Firmware FInder's DNS method. You will need to be able to update your network DNS settings, though. Have you tried using a corded keyboard connected through an OTG cable or a bluetooth keyboard?
I did not try using the dload method because earlier attempts an updating Marshmallow to a more recent build always failed because of my unlocked bootloader.
Click to expand...
Click to collapse
Unfortunately I could not fgure out how to do anything with it in that state (no keyboard, no internet, etc.). I tried to find a quality rollback for USA, but was not sure of what was out there that was correct. I ended up installing a EU version so at least it's working again (with old Android). I also realized the next day that my USB cord was bad and that's why I could not ADB or Fastboot anything. I'll try an upgrade again in the near future. Thx.

nostep said:
Unfortunately I could not fgure out how to do anything with it in that state (no keyboard, no internet, etc.). I tried to find a quality rollback for USA, but was not sure of what was out there that was correct. I ended up installing a EU version so at least it's working again (with old Android). I also realized the next day that my USB cord was bad and that's why I could not ADB or Fastboot anything. I'll try an upgrade again in the near future. Thx.
Click to expand...
Click to collapse
How did you install the EU old version? do you have link to the ROM?

Recovery bricked after Nougat update?

First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I can´t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance

You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.

nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.

kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.

nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)

It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!

nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.

Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.

kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.

Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.

Collection of potential camera fixes for Nougat (Black screen, crashes) - Suggestions

Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a reliable solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware (no root, locked bootloader, after factory reset) and then upgraded to Nougat C432B370 using FirmwareFinder (FullOTA-MF-PV). Installation worked fine, everything running as expected except for the camera - as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting after upgrading doesn't solve the issue. After upgrading to B370, I also updated to C432B388 - but to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Could this hint at some issue? Also, checking the device info with
Code:
*#*#2846579#*#*
shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop mentioned by @danielegta : https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Edit: I tried the fix on B370 but it has no effect.
Use the fix in #3, but reflash system.img if the fix doesn't help: https://forum.xda-developers.com/showpost.php?p=70069246&postcount=26
Unfortunately this also didn't work for me
Use TWRP-flashable .zip files as given in this thread here: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
I tried this today, but unfortunately it ends up in the same state as I was when upgrading B160 -> B370 using Firmware Finder. Everything except for the camera works.
Edit: I notice that in TWRP there are always errors about not being able to mount /data and /cust. Is this normal or does it hint at some error/malfunction when updating via flashable zip?
Use TWRP-flashable .zip as in #5 but instead of flashing the two .zip without restarting the device, first flash update.zip, then restart phone, flash Nougat TWRP, flash update_data_full_VNS_Lxx_xx_xx.zip as described in this post: https://forum.xda-developers.com/showpost.php?p=70704697&postcount=7
Tried this in the following way: stock MM -> unlock bootloader and flash TWRP -> flash update.zip -> flash Nougat TWRP -> flash update_data_. Doesn't help. Also I cannot confirm what I read somewhere here on xda (some user mentioned that his camera was working when he only flashed the update.zip - this is not true for me).
Other things I tried for uprading the OS that are not necessarily meant to fix the camera issue, but might:
Use B336 as intermediate step: B160 => B336 => B370 (=> B388) as suggested by @vozilo here: https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
Unfortunately this does not solve the issue. The camera doesn't work in any of the versions flashed after B160.
Go from B160 direcly to B388: didn't help
Does anyone know of something else that might help or could someone maybe comment on the "known" fixes, especially if there might be some changes that could be done to commands/build.prop or even local.prop that eventually help?
Thank you very much,
theluk

_theluk_ said:
Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware and then upgraded to Nougat C432B370 using FirmwareFinder. Installation worked fine, everything running as expected except for the camera as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting doesn't solve the issue. Afterwards, I also updated to C432B388 to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Also, checking the device info with shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop: https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Does anyone know of something that might help or could someone maybe comment on the "known" fixes?
Thank you very much,
theluk
Click to expand...
Click to collapse
I had the same problem, and i fixed it by (un)rooting and (un)rooting again

Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly

_theluk_ said:
Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly
Click to expand...
Click to collapse
Ok so usually u should upgrade like 160>b336>b370... The problem might be that you missed a step, not sure though. Try to factory reset first, then go back to b160 and to b336 and then to b370

Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess

_theluk_ said:
Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess
Click to expand...
Click to collapse
try updating through the stock updater

mjz2cool said:
try updating through the stock updater
Click to expand...
Click to collapse
Unfortunately the stock updater doesn't show any updates. So I have to enforce this by using the proxy method provided in Firmware Finder. As I understood this is the "fully" official way of updating, since it does use the "system update" feature provided inside settings of the phone. I will try it again later today to see what could've gone wrong. Maybe I'll just try one of the other B336 firmwares that are listed as FullOTA in FF.

Major update to OP - including new stuff and new information about what I tried. Any other suggestions? I am out of ideas for now and will probably have to live with MM until Huawei has solved this issue

After a suggestion to try VNS-L21 firmware I did, after flashing the corresponding oeminfo. And indeed this worked nicely. Upgrading to Nougat B370 worked and camera is working as well.

_theluk_ said:
after flashing the corresponding oeminfo
Click to expand...
Click to collapse
Hello,
Sorry but I'm a noob, can you explain to me what do you mean by "flashing the corresponding oeminfo" ? Does it mean you had to somehow "trick" your phone so it believes it's L21 instead of L31 or something ?
I have the same problem on the phone of my girlfriend (although I don't recall it's a dual sim one), I'd really like to solve this.
Thank you

_theluk_ said:
...
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
...
Click to expand...
Click to collapse
Ah, one of number of my statements taken out of context. When I worked on CM13, initially only the P9 Lite was supported. After a NEMO user tested this, which was proof of concept that the nemo camera could work on my p9 lite ROM, I added support for NEMO in my AOSP ROMs. So, the reason this helped was that it restarted the camera to work with NEMO and not VENUS, for which it was originally started.
As for your problem, Developer Options -> Take Bug Report ->FULL and post?

AT&T in Australia

Hi all,
Was recently in the 'States and broke my S8 - it's now the third mobile screen I've busted since Samsung brought in curved edges, never had any issues with the S2 or S5 - who ever thought tempering glass and curving it would be a good idea??
Anyway I had the opportunity to pickup a brand new Samsung Galaxy S8 Active and did a quick bit of research. I found the most compatible version with my carriers back home in AUS was the SM-G892A from AT&T. Picked up a brand new unlocked model, stupid me didn't connect it up to AT&T while I was there. I turned it on and played around with it on Wifi for the last few days of our trip and returned home to Melbourne.
Basically I now understand AT&T are a bunch of ***** and do not allow updates to be pushed even for unlocked devices overseas. Considering a lot of the updates are for security I'm very surprised by this.
Anyway so I've notcied a few tiny bugs here and there with apps/OS and figured updating my device/OS is the way to go and might resolve the issues. I guess the easiest way to get the info I need is to put the questions I have individually, as my mind tends to jump all over the place when I'm working a problem:
1. Is there any way to get my phone updated without rooting/flashing the phone?
2. If not, what is the best option for a S8 Active? Are there any firmware versions that will enable OTA updates so I don't need to keep flashing everytime new firmware is released? I have seen some posts about T-Mobile being able to be flashed over an AT&T model or even the G892U or maybe a custom firmware that allows this?
3. Will rooting/flashing interfere with any of the carrier settings etc? Don't want to upgrade it only to find it disables an LTE band or something?
4. I am an absolute noob at flashing, have never done it but am pretty tech savvy so if there is a step-by-step procedure I wil have no dramas following it. Saying that, I would rather not make the device worse than it is so I only want to follow tried & tested procedures if that makes sense, I don't want my device to be a lab-rat.
5. If there is no way to enable OTA internationally as per Question #2 when new firmware updates become available on XDA will flashing a new update delete personalisation/settings/files etc? Or will it retain them and update like a stock model performing a firmware upgrade would? If not, that would be a pain in the ass and time consuming to have to re-apply settings and reinstall apps every time and almost makes the idea of flashing unattractive.
6. I have baseband G892AUCU1AQG4 - taking into account Question #2 what is the best way to move forward? Considering Android 8.0 is available for the S8 Active and has been available for my model from AT&T since March 1st, 2018 apparently I'm hoping there might be some way to move towards that.
Hope someone might be able to help,
Thanks in advance
UPDATE 05/05/2019
Got some answers to my original questions...
1. Rooting/Flashing are different things - rooting allows custom firmware, flashing is the procedure to install custom or OEM firmware onto the device.
2. The best option for me I think is to just update to newer AT&T firmware so I get the updates and new software features as I'm not interested in custom firmware. I still do not know if it is possible to get OTA updates for this device directly from Samsung/Google.
3. As long as you are flashing from the same model firmware as in SM-G892A to SM-G892A should be no issues, however using SM-G892U might cause issues.
4. Once I wrapped my head around how baseband versions of firmware work and what is needed to get between bootloader versions flashing from SD Card or Odin (as I suspected) was very straightforward thanks to some of the guides out there. To make this easier for anyone facing the same issue I have written how I did this below.
5. Yes, flashing for AT&T will delete everything, it's an absolute PIA and that's why I will keep searching for a way to get OTA updates enabled if at all possible. However I believe Samsung SmartSwitch is pretty good for backing up and restoring so that might be a simple way forward.
6. See my latest post, I was 12 updates behind but able to skip 7 of them using my method.

I'm considering importing an S8 Active AT&T and have the same questions. How did you go?

secateurs said:
I'm considering importing an S8 Active AT&T and have the same questions. How did you go?
Click to expand...
Click to collapse
Sorry for the slow reply I've only just had the time to dive into this. Yes I have figured it out.
There are two ways, incrementally update by applying OTA updates via the SD card. However trying to find all of these can be a pain.
The other way you may have read about is to use Samsung's own 'Odin' flashing software.
Because I had the very first baseband version G892AUCU1AQG4 I was way behind. The fifth-last digit designates the bootloader version, you cannot jump from v1 to v3 for example. So what you can do is use a few OTA updates to jump you from v1 to the first v2, you can then use Odin to jump you all the way up and use another OTA to get you to the next bootloader version. Hope that makes sense?
So I was able to use x2 OTA updates to get from 1AQG4 to 1AQJ2, then I was able to do one more OTA to get from 1AQJ2-to-2AQK3. Now if I was to continue using the OTA method with the SD card, I would need to run the process x8 times. This presents 3 issues:
1. Time consuming, trying to find all the correct OTA updates.
2. Even when you do get all the correct OTA updates you then have to copy each on to the SD card waiting for the phone to update and then repeat the process.
3. Even if you can find a link for a required OTA update a lot of the links are dead.
However using Odin and the flash files I was able to skip these and go directly from 2AQK3 to 2BRF2, use one OTA update and then I was onto Bootloader v3 (which is the latest version). Here is how I compressed 12 updates do into 5, good luck..
1. 1AQG4-to-1AQJ2 OTA (SD CARD): dropbox.com/s/ikor71zt1ec0nyn/SS-G892AUCU1AQG4-to-S1AQJ2.zip?dl=0
2. 1AQJ2-to-2AQK3 OTA (SD CARD): dropbox.com/s/ott9fs9qunkvf9x/SS-G892AUCS1AQJ2-to-U2AQK3.zip?dl=0
3. 2AQK3-to-2BRF2 Odin Flash : androidfilehost.com/?fid=1322778262904016415
4. 2BRF2-to-3BRG1 OTA (SD CARD): androidfilehost.com/?fid=1322778262904016441
5. 3BRG1-to-3BRL1 Odin Flash: mega.nz/#!7M42VCAJ!-FKnhzwTZG0He1kb9FzHHaPX4Aanlnj4fpn0M61DzR4

Have the s8 active outside of America and desperately want to update it
Hey ,
I'm sorry to bring up this old thread but I didn't really understand the method you used sorry I'm really new to this thing, I have the s8 active Sm-g892A ( the att) model it's on the baseband version G892AUCS2ARB1 . If you could help me out a bit with this I would be really grateful, having Android 7.0 really makes me concerned as I've heard the security patches also won't update.

None2939 said:
Hey ,
I'm sorry to bring up this old thread but I didn't really understand the method you used sorry I'm really new to this thing, I have the s8 active Sm-g892A ( the att) model it's on the baseband version G892AUCS2ARB1 . If you could help me out a bit with this I would be really grateful, having Android 7.0 really makes me concerned as I've heard the security patches also won't update.
Click to expand...
Click to collapse
So you are on Bootloader v2 (5th character from the right). So you can skip straight to Step 3. Be warned all instructions below will result in all data on your device being wiped!
Using Odin to upgrade as directed on Step 3 & 5 or future upgrades (there is now v4 software appearing):
You need to download Odin (you don't need a modified/Comsy version).
You need to enable Developer Options on your Galaxy.
Once you have developer options you need to enable 'USB Debugging'.
You need to shutdown your Galaxy.
Connect your USB cabble to your PC.
Boot into Download mode by using the Power+Bixby+Volume Down combo. OR if that doesn't work Use the Power+Bixby+Volume Up and use the menu to get into Download Mode.
Open Odin on your PC, it should say 'Added' if it detects your Galaxy correctly. If it doesn't you may need to install some USB drivers (you can Google how to do this).
Once it says 'Added' you can add the files from Step 3 and flash but be warned it will wipe everything on your device.
For Step 4 OTA:
Very simply download the ZIP file and place the complete ZIP file on an SD Card (it should not be extracted must be complete ZIP archive). Place the SD Card in the Galaxy, power off and boot into Recovery Mode Power+Bixby+Volume Up. Then simply use the Volume Up/Down and Power keys to navigate through, 'Apply Update from SD Card', find your SD card and the ZIP file and allow the update to run.