Related
Can't update to the new 1.2 ROM. Update stopped me at 3588. Went from NVFlash to 3389 and then finally 3588. Won't upgrade past that.
Maybe VS changed their mind about 4349.
jasco13 said:
Can't update to the new 1.2 ROM. Update stopped me at 3588. Went from NVFlash to 3389 and then finally 3588. Won't upgrade past that.
Maybe VS changed their mind about 4349.
Click to expand...
Click to collapse
grrrrrrrrrrrrrrrrrrrrr
Honestly, if they really pulled this then I hope it's temporary. As soon as this thing went into the wild, it's impossible to truly "undo" it from a support standpoint. Again, that's the sysdmin in me coming out.
I hadn't trouble with both mine hanging on the reboot after update and I mean for at least half an hour. Nvflashed one back to life and held power and vol + until the other one shut off. Then turned it on and it was fine with the new update. If many people had the trouble I did, not surprised they pulled it. Both were going from stock. One had never been modded the other one did have two taps for a while, but went back to 3588 before updating.
roebeet said:
grrrrrrrrrrrrrrrrrrrrr
Honestly, if they really pulled this then I hope it's temporary. As soon as this thing went into the wild, it's impossible to truly "undo" it from a support standpoint. Again, that's the sysdmin in me coming out.
Click to expand...
Click to collapse
Hi,
The update is no longer showing for me either. Was getting notification before, but not anymore. Running updater manually says that I'm current.
Jim
Yeah they pulled it. Glad I'd downloaded it. I ended up manually flashing it
Sent from my UPC300-2.2 using Tapatalk
I had a problem with 4349 hanging on the "n" screen after doing a factory reset or wipe data. Suggest doing a factory reset/wipe data after updating to 3558. Otherwise, works well.
Marshack4 said:
I hadn't trouble with both mine hanging on the reboot after update and I mean for at least half an hour. Nvflashed one back to life and held power and vol + until the other one shut off. Then turned it on and it was fine with the new update. If many people had the trouble I did, not surprised they pulled it. Both were going from stock. One had never been modded the other one did have two taps for a while, but went back to 3588 before updating.
Click to expand...
Click to collapse
+1 I thought I was boot-looping from stock recovery until I rebooted again it and Gtab was actually updated.
I have a feeling the OTA issue is going to be temporary
They released a statement on the new update:
http://www.viewsonic.com/gtablet/news.htm
That seems pretty official to me. My guess is that the OTA updater issue will be temporary.
I updated my stock gtab from 3389 last night to 3588 successfully. I then was prompted about the 4349 update and I let it download but never installed as it was late and I went to bed. Today I got home from work and was prompted that the update was ready to be installed. Instead I tried messing around with the gtab and kind of hosed myself in a way that I ended up just doing a factory reset to correct my issue.
Well now its reset and it reset back to 3588 which is fine and good but I'm no longer prompted about the 4349 update ready to install. I went to see if the update was available and says that 3588 is the latest.
So it looks like that VS might have pulled it.
Oh well back to side loading some apps from my phone for the time being. Lost all my internet bookmarks too...
Wished there was an easy way to get the google market loaded on the gtab without installing cwm. Any one know?
VDoubleUVR6 said:
I updated my stock gtab from 3389 last night to 3588 successfully. I then was prompted about the 4349 update and I let it download but never installed as it was late and I went to bed. Today I got home from work and was prompted that the update was ready to be installed. Instead I tried messing around with the gtab and kind of hosed myself in a way that I ended up just doing a factory reset to correct my issue.
Well now its reset and it reset back to 3588 which is fine and good but I'm no longer prompted about the 4349 update ready to install. I went to see if the update was available and says that 3588 is the latest.
So it looks like that VS might have pulled it.
Oh well back to side loading some apps from my phone for the time being. Lost all my internet bookmarks too...
Wished there was an easy way to get the google market loaded on the gtab without installing cwm. Any one know?
Click to expand...
Click to collapse
I'm working on it now - I posted on another thread about this.
I thought we had Gapps Enhancement Pack already? Or did that not work? I recall seeing early reports of brickage, but didn't read through all the details.
roebeet said:
I'm working on it now - I posted on another thread about this.
I thought we had Gapps Enhancement Pack already? Or did that not work? I recall seeing early reports of brickage, but didn't read through all the details.
Click to expand...
Click to collapse
I thought I found the thread earlier while I was at work but now at home I'm not having any luck. My biggest thing is that I can still get future ota updates without any issues. Ill keep looking...I've come across some threads but they were created November/December so I'm unsure they are still valid.
VDoubleUVR6 said:
I thought I found the thread earlier while I was at work but now at home I'm not having any luck. My biggest thing is that I can still get future ota updates without any issues. Ill keep looking...I've come across some threads but they were created November/December so I'm unsure they are still valid.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12939008&postcount=40
Prototype -- failed after a data wipe, so be aware of that. Not sure if it's the mod or 4349 yet.....
So is 4349 back up yet on OTA? I want to flash back to stock and try it out, but not if its not there
Thanks.
Still not showing on my stock gtab.
Don't expect to see anything till next week
I want to go to VS HQ and slap them in the face now...this s**t is annoying!
roebeet said:
grrrrrrrrrrrrrrrrrrrrr
Honestly, if they really pulled this then I hope it's temporary. As soon as this thing went into the wild, it's impossible to truly "undo" it from a support standpoint. Again, that's the sysdmin in me coming out.
Click to expand...
Click to collapse
Sound complicated, but it's not and it's FAR from impossible, it's simply a mater of flashing the 3588 with the correct bootloader, Gojimmy bootloader fix will work for that!
http://forum.xda-developers.com/showthread.php?t=1036956
Simply using the same script would work for 3588 as well... 3588 miss the line that write the old bootloader in the bct ie: write_bootloader_image("/tmp/bootloader.bin", "EBT"));
Back but not back?
I took the plunge and figured out nvflash and reinstalled the old version (bekin's) and then I got the ota update for 3588. It dfailed downloading the first time but after a reboot it tried again and there it was. I was surprised that all of my stuff was still there - wallpaper, apps, etc. I waited for the new update but nada. I ran the update app and it said I was current. I started checking the forum and discovered that the update has been pulled. Grrr I feel like going back to Calkulin's and forget it but my curiosity won't let me.
Here is what I am puzzled about. I tried to go into recovery mode to see if clockwork was still there and if that could cause me problems. It apparently is gone but it does say loading recovery kernel and then I get the animated box icon and then it just reboots and I see the tapntap stuff. I can't recall if there was any sort of menu in the stock recovery to wipe the cache, etc. Is there? Or, does it just trigger the recovery to look for an update zip on the sdcard and load it if it finds it?
when you run nvflash or install a stock update it wipes cwm
It'd be nice if viewsonic, google or even someone on XDA who can program visual basic or visual c++ would write a front end for nvflash for these devices. Make it download all the files, and provide drop down lists or check boxes for all options, then nvflash them onto the tab. It'd make screw ups like this much easier to fix. Run the app, select 3588, check "restore" box. Run, wait 15 minutes, fixed tab.
I'm still new to this and I was hoping that someone could give me some help. The phone is a rooted tbolt running stock.
I grabbed the ota update this morning. The phone reboots and starts installing the update but I get the exclamation mark with the droid guy about 40% of the way through. I power cycled the phone after the error and everything came up normally. It took a few minutes, but then the phone rebooted to try and install the update again (and fails at 40%). Seems to be a pretty annoying loop.
Has anyone else experienced this and is there any way for me to tell the phone to stop trying to update?
skeezbo said:
I'm still new to this and I was hoping that someone could give me some help. The phone is a rooted tbolt running stock.
I grabbed the ota update this morning. The phone reboots and starts installing the update but I get the exclamation mark with the droid guy about 40% of the way through. I power cycled the phone after the error and everything came up normally. It took a few minutes, but then the phone rebooted to try and install the update again (and fails at 40%). Seems to be a pretty annoying loop.
Has anyone else experienced this and is there any way for me to tell the phone to stop trying to update?
Click to expand...
Click to collapse
It's because your rooted. Th OTA can't install with the clockworkmod recovery installed. Grab the rooted OTA (google it I don't have a link) and flash that and flash the kernel via bootloader.
Sent from my rooted stock OTA MR2 Thunderbolt
After reading about the update I'm not entirely sure that I want it. Is there any way to stop the phone from trying to install the update now?
install a rom thats the main reason we root the phone in the first place
Do you have a nandroid backup? Revert to that if you do. Otherwise, the only way to get rid of that is probably going to be to flash to full RUU over again (you'll be back to 100% stock and lose data and root)
Boot into clockwork recovery and wipe cache ONLY. Might work I'm not sure, but it definitely won't hurt.
Sent from my HTC Thunderbolt
JBO1018 said:
Boot into clockwork recovery and wipe cache ONLY. Might work I'm not sure, but it definitely won't hurt.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yessir, causes the update to fail before the reboot. Thanks so much!
No prob and by the way for future reference don't flash official updates over rooted phones. It's known to cause issues. Just wait for someone to post a rooted version of the update.
Sent from my HTC Thunderbolt
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
wingnutta said:
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
Click to expand...
Click to collapse
Are you rooted? That would be why. It's not advisable to accept an OTA update when your system has been altered. Unlocked is ok, just not rooted/modded.
If you are rooted and have a nandroid backup from before the update, try to restore from there. If not, boot into fastboot and restore to your model's original stock image (from motodev) then let the OTA updates bring you up to 3.1 and then 3.2. Re-install CWM Recovery, and re-root after that with solarnz' Universal Xoom Root and go from there.
If you're not rooted and your system is just continually rebooting, you should still try the fastboot/restore stock images procedure. There may be something easier, but I'll let someone else advise you on that.
Good luck!
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
wingnutta said:
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
Click to expand...
Click to collapse
I can't think of any way to resolve this that doesn't involve a wipe of some kind. Have you checked any other Moto/Xoom forums to see if anyone else had the same problem?
My condolences on the irritating situation and the potential loss of your stuff. Actually, a good reason to root is that you can back everything up!
Well i took the plunge and wiped by unlocking. Cured the bootlooping (obviously), and so then thought - why not root aswell
All done and running Tiamat 2.2 and very happy!
Appreciate the help peeps..
Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis
I didn't. What I did have was bootlooping that started about 48 hours after installation. Stock, not rooted and very minimal apps. I ran a factory reset and it has been much better.
My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.
anbowlynn said:
My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.
Click to expand...
Click to collapse
( it was the same problem with my S5 from 5.0.1 to MM will never do same error save all yr data and do clean flash )
1- do just cache clean
2- you can flash the old MM tmb but dont flash csc flash HOME_csc
but wait for more suggestion but for me is that the only solution
hapakun said:
Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis
Click to expand...
Click to collapse
same. s7 slow and laggy as hell crappy battery life. they did this with the s5 too. slowed it down with updates until youre forced for a new phone.
This last update definitely negatively impacted my battery life. Stock, no root, and I wiped cache. I'm not in the mood to do a factory reset. Weasles.
I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL