Related
for some reason, i can connect to kies with no problem, but when i go to upgrade the firmware to the newest JI6 official, it fails and shows the attached picture. any ideas? I need to get this update because my vibrant is acting up pretty ba and as far as I know, this is the only current fix. I dont want to use the samfirmwares.com version because I want the official version. Help!
What version of Kies are you on? I'm on 1.5.1 and I never see an update. Maybe 1.5.3 can see the update?
Just updated mine about an hour ago through kies. Worked fine.
Kies Version: 1.5.1
Prior Rom: Bionix 1.4
Kernel: Stock
im on 1.5.3 and it still wont work, i just tried it again. I tried rebooting the pone and computer and still nothing worked. it just keeps saying unable to update. when you installed kies, did you install it as the UK as your country or US?
Mine says "PC Connection only available in idle screen Close running applications" when I try to connect with Samsung Kies mode???? What am I doing wrong?
Back out of everything on the phone, make sure you are in Kies mode. Run Kies first, then connect phone.
I have yet to see on the forum where somebody went from the JI5 from Kies to JI6 either OTA or through Kies. I've tried 1.5.1 and 1.5.3.81 for Kies and neither will update my phone.
Updating through Kies right now. I had to do the regedit fix for Kies 1.5.3.
EDIT: Whew, phone isn't bricked. Just made it past the Vibrant screen.
is it possible that kies may brick the phone?
How long is the Kies update taking for you guys? I'm pretty sure I'm hung up. It made it through the downloading, and now it's about a 1/4 of the way through the upgrade bar, but hasn't moved for an hour and a half.
I am totally stock. No mods, no nothing.
nateball said:
How long is the Kies update taking for you guys? I'm pretty sure I'm hung up. It made it through the downloading, and now it's about a 1/4 of the way through the upgrade bar, but hasn't moved for an hour and a half.
I am totally stock. No mods, no nothing.
Click to expand...
Click to collapse
that's not good. if i'm in your condition maybe i'm already sweating. maybe just wait a little more.
i tried to do this but the kies hung up when it's copying my contacts.
Well, it's not gonna do me any good to sweat. I'm over two hours now of just watching it sit there 25% done. No movement at all, computer's cpu is at 0% use. I think I have to pull the plug and then call Tmob if the phone is messed up.
Just to be clear, I was 100% stock, no root, no fixes, nothing other than apps installed from the marketplace. Here goes nothing...
nateball said:
Well, it's not gonna do me any good to sweat. I'm over two hours now of just watching it sit there 25% done. No movement at all, computer's cpu is at 0% use. I think I have to pull the plug and then call Tmob if the phone is messed up.
Just to be clear, I was 100% stock, no root, no fixes, nothing other than apps installed from the marketplace. Here goes nothing...
Click to expand...
Click to collapse
what happened? me too, i unplugged my phone before anything goes wrong.
ive made the backup of my contacts, but after that it cant continue to update, it fails every time, i guess i am stuck waiting for the ota unless someone has a fix for kies
My phone now only shows an image of a mobile phone and a desktop with a caution sign in between them. The same image shows if I restart using the power button, pull the battery, shake it vigorously, etc. I do believe I am now the proud owner of a non-functioning phone. Kies will not recognize it, nor does windows recognize it when it is plugged in. Crap.
I guess I'm off to the T-mobile store to try and get a replacement.
im in same boat i have no clue what im doing wrong? im i missing steps here?
if has any idea what i need to please help.
im a bone stock
Well, I'm pretty sure that we are now lacking functioning firmware on the phone. I'm thinking a new phone is the way to go, but maybe they can do something at the store.
Anyone where the update is stuck, you will probably have a soft brick at this point. However, this does not mean your phone is broken completely, it just means you will probably have to get into Download Mode and Flash via Odin.
Have fun
nateball said:
My phone now only shows an image of a mobile phone and a desktop with a caution sign in between them. The same image shows if I restart using the power button, pull the battery, shake it vigorously, etc. I do believe I am now the proud owner of a non-functioning phone. Kies will not recognize it, nor does windows recognize it when it is plugged in. Crap.
I guess I'm off to the T-mobile store to try and get a replacement.
Click to expand...
Click to collapse
that was my experience using kies too (whether 1.5.1 or 1.5.3). since then, i've used odin (v1.3) about 6 times (not a lot, i know) with all successes. don't let it scare you.
to get into download mode just do the following.
1) pull battery then put it back in so the phone is completely off
2) disconnect usb from phone (but leave it connected to pc)
3) while holding down volume up and down buttons together, insert usb cable
that should take you straight to download mode.
then load up odin (check the bible for flash instructions -- pretty simple though). what i did was flash to JFD, then flashed to JI5. worked like a charm.
honestly, kies was a nightmare to get working and once it did, it messed up. odin has been simple and painless. one note, after flashing with odin, first boot may be slow. when i flashed JI6 OTA over JI6 leaked, it took about 10 minutes, at least, to boot.
good luck!
I know it's not helping you guys: but my Kies update (newest release) was smooth sailings after I did the registry fix.
I did none of the backups suggested (I tried so many times before so they were already done this time)
Let me know if you want details about my config.
Sent from my SGH-T959 using XDA App
Thanks for all the suggestions everyone, but I did make judicious use of the search button and google before I took it back to the store. I tried every single combination of button presses for every single mode, from every single forums posts I could find. No luck at all. The T-mob guys also had no luck, and it just so happened that a Samsung rep stopped by to see how the Vibrant was being received by the public and he couldn't get any recovery mode to work either. (He had no idea about when Froyo might be out though..... just in case you were wondering) Anyhow, I'm pretty sure that I for one believe in the myth of the hardware locked Vibrants.
I think we need a new Poll for anyone that needs to change their answer after upgrading to JK4...Perhaps give JK4 a few days to make sure it's running smoothly before voting...
(Thanks Electroz for the original Poll!)
I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty...
I don't think there are any issues with Kies or Odin for flashing. I've flashed many times, sometimes 4 times in one day and I've never had any issues. There does seem to be the usual SD issues but I also think there is a USB communications issue. There have been many reports of data corruption while writing to internal/external SD with large files. I personally had an issue pulling large files off of internal/external SD. I think if this problem occurs while flashing new firmware it could cause some corruption that could be noticeable right away or after a bit of use. The partitioning on this device seems to be more sensitive than others and a hiccup while flashing could cause some major issues.
trinitonesounds said:
I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty even though I'm on Rogers...
Click to expand...
Click to collapse
They don't care.
I went today and they just took it and didn't ask anything that sounds like they cared about if I am not with Bells.
I gave them my bro's phone number and info since he is with Bell, just to avoid any problems.
Just don't say something like the phone is "unlocked" lol...the phone is dead so they won't find out anyways if you don't tell them. They won't ask either.
Just tell them that you upgraded through kies and it got the problem.
it's a hardware defect, if it dies it dies
after all the evidence we've seen (all the reports by our members)
if it's good it will work regardless of what firmware you use, and regardless of the way you flash the firmware
the lag fixes and froyo just accelerates the problem and makes it more evident sooner than later
which is good in a way, it's better to find out before your warranty runs out
ok im pretty sure mine is a full brick. maybe you can tell me.
less than 24 hours after updating to 2.2 i started getting all of these errors in various programs, so i rebooted the phone, but after it plays the little intro thingy the screen just goes black and thats it. cant do anything else. i tried a factory reset and still the same thing. so is that it?
also. i bought this phone at best buy, but network unlocked it to use on rogers. should i be contacting samsung directly about a replacement/fix? anyone here done that? im REALLY scared that are gonna give me a phone that i am unable to network unlock.
thanks for any info.
some one welcome me to the club of defund Bell Internal SD
http://forum.xda-developers.com/showthread.php?t=867157
@evil-doer
I am in the exact same boat as you! I bought from Best Buy, then unlocked to use on Rogers. Last night, I updated to official Froyo through Kies, and then it just died on me today (many app force closes and then just drop dead). When I get into recovery mode, it says can't mount the SD card.
I think I will just go to a Bell Store tomorrow and see what happens. I will let you know how it goes. Please let me know how yours go too. Thanks.
Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.
i did not have Force Close, the phone just got really really hot during batch restore of TitaniumBackup
jdrom said:
Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.
Click to expand...
Click to collapse
how did you load up 2.1? i can put my phone in download mode but nothing happens after that. and how do you get in to recovery mode?
Well I can load up 2.1 with Odin and with the auto reboot option checked, it'll go straight to recovery mode after flashing (for whatever reason). Otherwise I can't get to recovery mode.
Success so far... 12 hours after upgrade.
I sucessfully upgraded to Froyo yesterday.
I had problems with Kies at first and had to do a factory reset before the upgrade. The FileSearcherforKiesFix.exe altough it detected two bad files wasn't enough to make Kies happy.
This phone was bought in october and had the voodoo lagfix installed from the begining. I disabled the lagfix before the froyo upgrade.
My previous samsung phone; the GT-8000 (Omnia II) did have an internal SD card failure after a few months of operation... Also a Bell phone. I'm really concerned by that trend with Samsung and Bell...
I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.
Well... you're going to have upgrade eventually so best to do it now while you are under warranty in case something happens...
nemethb said:
I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.
Click to expand...
Click to collapse
How's that the case?
Stock JG9 w/ OCLF -> Stock JH2 (kies,voodoo lagfix) -> JK3 (Odin, Speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix) -> JK4 (hacked kies, speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix)
No SD failure so far, touch wood. Original phone purchased day after launch.
Mine died today, started getting FC and then the whole thing froze. I tried restarting it but after the samsung splash screen all I had were glowing buttons.
It ran fine for about a day on JK4 before that on JH2 it never gave any problems.
BTW it was stock updated through Kies.
The guy at the Bell store told me they never get these phones returned, this was a first for him. Either it was his first day on the job or it's typical Bell BS.
Just had my second phone die. The first one died after 28 days with no upgrade. This one after 8 days, 2 days after upgrading to Froyo...
Same thing happened to me this morning.. Froyo was working fine for just over a day and then this morning I turn on my phone, get a bunch of FCs.. I reboot.. get another bunch of FCs.. reboot.. and now it won't go through the "S" splash screen. When the screen disappears I press the buttons and it just glows..
I don't know if it's bricked or what.. when I run recovery I get this error.
E: can't mount /dev/block/mmcblkOp1 (I/O Error)
E: Copy_dbdata_media:can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
Is this what everyone else is getting? And what are my alternatives?
If my phone is pooched then I'll be pretty pissed since this is my 3rd SGS, I gave the SGS up when it had issues in low reception and the 850 band lock fixed it. If this totally pooches my phone I'm never buying another Samsung mobile product again.
My wonderful wife gave me an Acer a500 for Christmas. Awesome gift. I had rooted it immediately with no problems, since all of my phones and families phone are rooted, it just seemed to be the natural thing to do.
As someone that "plays" with their android a lot I did all of the backups. Well, the time came to have my tablet "approved" for use at my company and also have the appropriate "encryption" software and keys added. Just as a precaution I decided to restore the original backup and unroot the tab.
All was going well until I received the update message. I went ahead and downloaded the update and ran it. During the install process it froze. I thought it was just busy so I left it for a good 20 minutes and finally realized it was frozen. I rebooted and it went through a couple of reboots and finally settled on the lock screen. But now I find the touch screen unresponsive.
I plugged in a mouse and keyboard in hopes that I could get back into it and start over, but, although, the mouse shows up, it is jumpy sluggish and will not grab the lock to slide open and eventually freezes.
I have tried all of the "update.zip" files I could find and they all fail at one point or another.
ADB allows me to explore in shell but since I unrooted, I cannot get su privileges.
Acer is of course, useless and the vendor it was purchased from is worthless.
I have been through every thread I could find and tried every trick I could come up with. Now I'm just stuck.
Any help is appreciated
I've had this a couple of times already. Usually just turning the screen off and on a couple of times does the job (the issue seems to be with the driver, also on various custom roms). Just try it after each off-on cycle, most of the time it takes no more than two or three tries, though there are exceptions.
Thanks, but it has been rebooted many many times since it's demise.
Decided to skip sleep tonight and keep plugging away.
I found an update.zip recovery file for an a501. Figured I can't do much worse so I went ahead and ran it.
It froze at about 95% but.........
Good News:
The tablet is responsive and touch panel works again.
Bad News:
It boots straight into system settings and although you can open the settings menu, nothing actually launches.
Decided to try all of the old update.zips and still everything fails.
No more ADB response.
When you originally unrooted your device did you revert back to the stock recovery or did you leave cwm on your device?? If you left cwm on your device that may be the problem with the update.zips and OTAs.
You are sooo right. I've never gone back to a stock rom before and I completely forgot about reverting to the stock recovery.
As a matter of fact, I was on Civato's Flexstriker 3.2.1 rom with the new CWM before I reverted back to the stock rom.
Well, at least we've determined my stupid mistake, but now the question lies: "How do I get back to any working rom?"
Here's an update. I did find an update.zip file that also begins to load but does not finish. It stops at 95% still.
I will attach the photos in case someone notices something otherwise I am at a loss. In addition to all of the above, I tried everything I could to get into APX mode but nothing. I am willing to try almost anything at this point, so all suggestions are appreciated.
Something I noticed was the recovery for the a501 was android with gears spinning in the body. The recovery I have now is a package with an arrow. The recoveries are different. The current update file is Acer_A500_1.145.05_COM_GEN1
So this brings me to a question: Can I put Thor's 1.6 CWM back on the a500 and at least work from there? I do have my original backups and thought I might be able to get somewhere that way.
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
RawSynergy said:
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
Click to expand...
Click to collapse
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
DeadlySin9 said:
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
Click to expand...
Click to collapse
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
RawSynergy said:
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
Click to expand...
Click to collapse
NB1 is the only one you can get, just try downloading either one again.
DeadlySin9 said:
NB1 is the only one you can get, just try downloading either one again.
Click to expand...
Click to collapse
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
RawSynergy said:
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
Click to expand...
Click to collapse
When you plug in the phone in Download Mode, does the blue box in Odin light up? If not, reinstall samsung drivers
Sent from my SM-N910G using Tapatalk
I have completely stock ONN 8 that I've had since launch. It has never received an OTA, and in the past trying to update it with the OTA updates in another thread never worked. For the first time today, the tablet had a notification that there was an OTA update available. The notification says the update has been paused and click resume to continue. When I click "resume" nothing happens and it goes back to paused a few seconds later. I tried factory resetting the tablet and using several different networks, and it will not download the OTA. Any ideas?
just lou said:
I have completely stock ONN 8 that I've had since launch. It has never received an OTA, and in the past trying to update it with the OTA updates in another thread never worked. For the first time today, the tablet had a notification that there was an OTA update available. The notification says the update has been paused and click resume to continue. When I click "resume" nothing happens and it goes back to paused a few seconds later. I tried factory resetting the tablet and using several different networks, and it will not download the OTA. Any ideas?
Click to expand...
Click to collapse
Same behavior for months. Spent time trying to resolve and came to the conclusion the back end mechanism to notify and initiate OTA's is on a different platform (server, url, whatever) than the delivery mechanism. The latter appears to be non-responsive; no one is watching the hen house.
DB126 said:
Same behavior for months. Spent time trying to resolve and came to the conclusion the back end mechanism to notify and initiate OTA's is on a different platform (server, url, whatever) than the delivery mechanism. The latter appears to be non-responsive; no one is watching the hen house.
Click to expand...
Click to collapse
Thanks. My suspicion was that it was server related.
There's like a new update ONA19TB002_20200416.
EDIT Even downloaded and installed. Kind of regret using that Mediatek tool to install 2019111 from the stock/image/ota thread as ever since then the wifi's mac address keeps changing on each boot or wifi is turned off/on.
htcplussony said:
There's like a new update ONA19TB002_20200416.
Click to expand...
Click to collapse
Interesting. Maybe someone will grab the OTA fie and upload it. Unfortunately, it probably won't do me much good, as my tablet doesn't have the November update installed.
I would avoid the update if you can - I came home last night to find mine updated and the screen was mirrored (everything is backwards, including text). A forced reboot didn't do anything. It's basically like looking at it through a mirror as everything is backwards. The odd part is, the touch locations are still in their original locations. So if on the screen, an app is now on the left side (again, backwards), I have to touch the right side of the screen to use it (with the same behavior inside the app - controls all backwards). The update basically made my tablet useless. 100% stock.
no99sqrd said:
I would avoid the update if you can - I came home last night to find mine updated and the screen was mirrored (everything is backwards, including text). A forced reboot didn't do anything. It's basically like looking at it through a mirror as everything is backwards. The odd part is, the touch locations are still in their original locations. So if on the screen, an app is now on the left side (again, backwards), I have to touch the right side of the screen to use it (with the same behavior inside the app - controls all backwards). The update basically made my tablet useless. 100% stock.
Click to expand...
Click to collapse
My update is still "paused". At this point I don't really care. This tablet is so slow it is virtually useless. I doubt an update is gonna make it any better anyways.
My FOTA doesn't even give any updates, just that it's "fully updated." I wonder if I got a test model, as it also came with a multitouch test, had a chinese "factory mode", and had a strange MTK debug mode when I tapped custom build mode.
My unit had an FOTA to the May 2019 but no more updates while on that firmware. The Nov FOTA from the Stock Backups thread wouldn't take and I had to flash the full stock image. It gave me the April 2020 when they released one.
New Update
I know this thread is old, but I received a new update today. It has the July security patch, and the kernel is dated 8/14/2020. It's the first update that actually installed since I got this tablet at launch last year.
Does anybody know how to overcome the problem of getting the latest OTA. I get an error after reboot and trying to flash it, here is the log:
script aborted: unable to use metadata to correct errors
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system image corrupted, attempting to recover...
script aborted: unable to use metadata to correct errors
E1004: system partition fails to recover
E:Error in /sdcard/Android/data/com.adups.fota/files/adupsfota/update.zip (Status 7)
W:failed to read uncrypt status: No such file or directory
25.10 solved the problem by reflashing the stock image from may 2019