Database Info

[Q] Unable to text unless my battery is in the red after the offical update

Long time lurker, but i dont think i have posted before...so sorry if this is on the wrong place/already been answered, if that is the case i would love be be redirected to where i should go.
Anyways, after updating this morning, everything worked fine other that some occasion lag. But when i opened up handcent, it was just a black screen. so i reinstalled it, and still no dice. the default messaging app had the same problem. If someone texted me i wouldnt get it, and there was no way for me to send out a text. then, when my battery went down to red, all of a sudden it worked like normal. i was able to charge it and even when the battery was full it still worked. However, when i reset my phone, it stopped working again, and resumed working when my battery got to red. Im pretty sure those are the only symptoms i noticed...Any ideas on what is going on/what i can do to remedy it?
And fyi, i was rooted before the upgrade and have rooted since. I had oclf, but disabled it before i upgraded.

Shameless bump, I really need help

Only thing I can think of is a bad install of the update. I would suggest going back to 2.1 using odin and then reinstalling the froyo update
Sent from my SAMSUNG-SGH-I897 using XDA App

So step one of http://forum.xda-developers.com/showthread.php?t=884364
Then follow the installation of 2.2 as samsungs website outlines? Would that require me to restore all of my apps and settings from tibu again?
Thanks

ahurley said:
So step one of http://forum.xda-developers.com/showthread.php?t=884364
Then follow the installation of 2.2 as samsungs website outlines? Would that require me to restore all of my apps and settings from tibu again?
Thanks
Click to expand...
Click to collapse
Yea if you are going to flash back to odin you will need to back up all user apps using titanium backup. Make sure you do not restore any system apps though as that can cause problems. Also you will lose your texts so I would recommend backing them up. I use sms backup+
Sent from my SAMSUNG-SGH-I897 using XDA App

My friend had the same problem and had to go back to 2.1 and re-install the update and then it worked. Seems like the update didn't install correctly on a handful of Captivates.

okay so i still haven't done this because of how long restoring everything with tibu takes, but if I am gonna have to go through this process again, should i just make my first venture into flashing a custom rom? Am i correct in thinking that flashing wont be messed up because of the current glitch i have because it all reverts back to stock as the first step anyways?

Updater back to saying 3588 is current

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.

[Q] Grabbed Update today and stuck

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

New 3.2 update bootlooping?

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..

[Q] Kies does not Support software Updates

I have a rooted i727 that I just updated from the stock 2.3.5 to the new 2.3.6 OTA update. Now after Update I get message in Kies saying it does not support my device for software Updates. See attachment.
Is this because my phone was rooted?? Never has said this before in Kies.

Yes it is because you are rooted and or have a custom recovery.

u must be COMPLETELY stock to get its updates, bloat, recovery, everything

I'm complete stock, including stock recovery. All bloatware present, though some frozen with TB. I also get the same message. Phone is rooted.
Prior to OTA, also didn't get this message. Was rooted then also.

jimhlt said:
I'm complete stock, including stock recovery. All bloatware present, though some frozen with TB. I also get the same message. Phone is rooted.
Prior to OTA, also didn't get this message. Was rooted then also.
Click to expand...
Click to collapse
Nothing can be frozen.

I was completly stock as well out of the box stock running gingerbread 2.3.5 and at&t sent an ota update which updated to 2.3.6 in which i was still out of the box stock. But once i did that kies would no longer work for me either. After much research what i found is since the update come from att and not samsung kies would no longer work and this is what possibly is slowing the official ics update down cause now samsung has to update kies to work for the users who did the ota update to 2.3.6 which since it was from att approved by samsung it does not void the warranty but samsung was not counting on the kies mini problem. Now thats what i read but you know how that is too dad always said beleive little of what you hear half of what you read and even less of what you see....
Sent from my SAMSUNG-SGH-I727 using XDA

xcrazydx said:
Nothing can be frozen.
Click to expand...
Click to collapse
Not sure what you mean that nothing can be frozen. Using TB, I go through the freeze process. After a reboot, the apps I froze no longer appear in my list of available applications. They do however still get market updates so are still present. Isn't that kind of the goal of freezing?

jimhlt said:
Not sure what you mean that nothing can be frozen. Using TB, I go through the freeze process. After a reboot, the apps I froze no longer appear in my list of available applications. They do however still get market updates so are still present. Isn't that kind of the goal of freezing?
Click to expand...
Click to collapse
no apps can be frozen if you want to take an OTA.

xcrazydx said:
no apps can be frozen if you want to take an OTA.
Click to expand...
Click to collapse
Ok. Now I understand what you mean. I can only say that this last OTA update worked just fine for me even with apps frozen. Also before this last update Kies was happy even with my frozen apps and being rooted. After this last OTA, Kies no longer likes my phone. Not sure if it is frozen apps or being rooted. Of course it could be a problem with Kies I suppose. I don't really want to unroot and unfreeze to find out at this point.

jimhlt said:
Ok. Now I understand what you mean. I can only say that this last OTA update worked just fine for me even with apps frozen. Also before this last update Kies was happy even with my frozen apps and being rooted. After this last OTA, Kies no longer likes my phone. Not sure if it is frozen apps or being rooted. Of course it could be a problem with Kies I suppose. I don't really want to unroot and unfreeze to find out at this point.
Click to expand...
Click to collapse
The ota is the same crap anyways. No need for it, flash a custom 2.3.6 if you like ginger.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2