B303 in the UK on my wifi M3. Nothing in firmware finder but I checked system update and it was there.
Attachments
-
218.1 KB Views: 282
-
207.8 KB Views: 282
Just appeared on my tablet as well, was on B302 beforehand.Were you coming from B302? Im on B302 in the UK but have no updates to B303 yet. Have you noticed any improvements apart from security updates?
Yeah you went too far man! Wish I could help.UPDATE: Welp... I appear to be bricked beyond any help. I have modded and rooted a dozen android phones and tablets over the years and this has easily been the worst experience for me.
I can only speculate to the cause but, I was no longer able to flash anything successfully. Although the bootloader confirmed that it was fully unlocked, all methods of flashing (hard flash via sdcard and adb minimal) were not completing. I decided to try to manually flash an unpacked update.app from the last image that I knew was working. As I had the bootloader and confirmed I was connected and adb running, I thought I would try re-applying the unlock code. Now I have the "Your device can't be trusted" message and am unable to get into the bootloader. Before this, I was able to hold Volume - and plug the usb cable and it would vibrate once and go to bootloader. Now it vibrates twice and I only get the mediapad splashscreen to the unlock message. No combination of button presses seems to work, and my pc no longer registers the usb cable.
Any thoughts?
I appreciate thatYeah you went too far man! Wish I could help.
Sent from my BTV-W09 using Tapatalk
Try this and go back to 4.1 and from there up again:UPDATE: Welp... I appear to be bricked beyond any help. I have modded and rooted a dozen android phones and tablets over the years and this has easily been the worst experience for me.
I can only speculate to the cause but, I was no longer able to flash anything successfully. Although the bootloader confirmed that it was fully unlocked, all methods of flashing (hard flash via sdcard and adb minimal) were not completing. I decided to try to manually flash an unpacked update.app from the last image that I knew was working. As I had the bootloader and confirmed I was connected and adb running, I thought I would try re-applying the unlock code. Now I have the "Your device can't be trusted" message and am unable to get into the bootloader. Before this, I was able to hold Volume - and plug the usb cable and it would vibrate once and go to bootloader. Now it vibrates twice and I only get the mediapad splashscreen to the unlock message. No combination of button presses seems to work, and my pc no longer registers the usb cable.
Any thoughts?
Man... is there anyway you can assist me in getting this thing where it needs to be. I can not get the Bootloader code. I have halfheartedly tried. All I care about is the 5Ghz network. If I have to root to get it done, that fine. Been doing it since the Note 3! Man those were the days. Is there any way you can give me the steps to go through with dc-unlock. PM me if you have time or even care to go through it. Thanks in advance.Just buy a new one and switch it out. Or yeah problem solve it.
I LOVE this tablet. By far my fav. Took a LOT of work just to turn on 5ghz but now that it's done, it was worth it.
Hope you figure it out so you can have fun with it sooner than later.
Yeah as a guy who bricked his unit going for the 5ghz, my big takeaway is that getting root after EMUI5/Nougat is super dicey. The problem is that there are LOTS of firmware revisions out there (many of which do not work together) and not a lot of established documentation about which revisions work for which units. This is different from the typical ROM flashing scenario, because the recovery partitions (these have two) are incorporated into the firmware. It's tempting to find other compatible FW's and start flashing away, but it's not like trying Lineage rom vs resurrection mod- once you drop in the wrong FW, you are one or two steps from a dead end. BE CAREFUL!Hey man I can't help you really because I google a bunch of stuff and used a combination of different links. There was a lot of trial and error. Some steps worked from one guide and then I used another guide for other steps. Then I remember I had trouble with root and kept trying the same thing over and over then I did something which I forgot & it worked.