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.
Related
JH7 "congrats device has been updated" pop ups keep popping up...
whenever i change batteries
whenever i turn the phone off, then back on
sometimes during games it'll pop up
i checked for update, and it says no firmware
when i checked firmware it says 2.1 jh7 update
HOW DO YOU MAKE THE POP UP GO AWAY?
btw, phone is stock, not rooted...
I was just about to ask the same question! Mine does it too, w/ OCLF v2.1
anybody got any solutions?
No solutions, but the same problem. I've been totally stock the whole way and had no issues with the OTA update, except that it keeps congratulating me over and over that I now have it.
Congratulations!
Nobody has a solution yet????
Sent from my SAMSUNG-SGH-I897 using XDA App
Anybody find a fix to this yet?
If you had rooted, you could have installed ROM manager prior to the botched update, and would have had a nandroid backup. If you had one, then you could have restored the system to the pre update stage, and tried applying the update again. Probably the only way to get rid of crap like this at this point is to do an Odin one click flash. If you plan on going down that route, just flash the leaked Froyo on, and be done with the constant congratulations from Samsung.
Here ya go. Same thing happened to me.
Everyone:
My tablet is just loading the new 1.2.4349 OTA update -- and seeing the "2"
in the version number requires me to say be cautious on a couple of counts:
1. The last experience we had with something with 1.2 at the front of it was
the 1.2.3991 UAT. As long as folks went up from stock 3588 things were not
too bad. If I were giving advice (and I admit this is still a developing process)
I would tell folks to clean up your tablet as much as you can before going back
to stock. Then load either stock 3588, or load to something lower than that
and OTA update so that you have stock 3588 to update from!
EDIT: MAKE SURE YOU ARE COMPLETELY STOCK AND RUNNING 3588!!!
2. My tablet is up and running on 1.2.4349 now and it does have what I call
"blue recovery" on it. When you push power/volume+ to go into recovery,
it will give you a blue lettered screen that looks a whole like like CWM.
This tells me YOU SHOULD NOT LOAD CWM back on your machine until the gurus
check it out. Bekit .8 CWM didn't work with the 1.2.3991!
Other than the above two comments aimed at keeping anyone from getting
into difficulties -- it looks good so far. I flashed back to bekit 1105 (2638) and
then did back-to-back OTA updates to 3588 and the 1.2.4349 without any
difficulties whatsoever.
Good luck folks!!! Be careful and cautious!!!
Rev
P. S. To those of you who played with 3991, this looks just like that update and it really worked very well.
x2. I am doing some test scenarios, right now. I should know within an hour or so if this ROM has the same issues we saw with 3991.
Sure sounds like they updated the bootloader, which will mean all custom Roms will need updating, as well, if they want to install over this new stock.
Roe,
Looks like you got the major update you were expecting.
I did the OTA and now most of my apps are force closing. Even the default browser is having issues.
After downloading the update it reboots the tablet. My screen shows an exclamation mark in a triangle with and android icon to the bottom right of triangle.
The only thing none stock on my 3558 tablet was the nvidia enhancement pack. Any ideas
EDITED
I tried rebooting tablet and it reboots and comes up with message that says the update failed please try again later.
atakapa said:
Sure sounds like they updated the bootloader, which will mean all custom Roms will need updating, as well, if they want to install over this new stock.
Roe,
Looks like you got the major update you were expecting.
Click to expand...
Click to collapse
Yeah, and it's blowing up in my face.
Early tests show that it has the same issues as stock 3991 (which was the basis of TNT Lite 5). Most of the mods here may have issues with this stock update, but I am still testing.
SgtJake said:
I did the OTA and now most of my apps are force closing. Even the default browser is having issues.
Click to expand...
Click to collapse
Wiping user data/factory reset might be in your future. Boot into recovery and clear cache first to see if that helps before blowing all your apps with the reset.
Gaslight,
Yes, with enhancements your tablet is not completely stock.
If you are still running enough to get to Settings/Security/
Reset Factory Data -- you might see if that will help.
Rev
Yah, that didn't work. Looks like it on to a wipe and reset. My G Tab was completely stock too. No add-ons. What a pain in the butt...
SgtJake,
Are you on 1.2.4349 -- such as you've got!!??
Rev
EDIT: Sorry -- too little too late. Somebody else must have
had you do something!!
Yup. 1.2-4349.
Sarge Jake,
If the user wipe doesn't help, you may have re-partition the sdcard to 2048 and 0 to resolve the force closing of apps. BACK-UP your data first, it will get deleted.
Hey, what a great time to test the new recovery software and see if it can re-partition/ re-build the bct table correctly.
Let us know
atakapa said:
Sarge Jake,
If the user wipe doesn't help, you may have re-partition the sdcard to 2048 and 0 to resolve the force closing of apps. BACK-UP your data first, it will get deleted.
Hey, what a great time to test the new recovery software and see if it can re-partition/ re-build the bct table correctly.
Let us know
Click to expand...
Click to collapse
legacy cwm .8 may not work with 4349 (I have to confirm that).
roebeet said:
legacy cwm .8 may not work with 4349 (I have to confirm that).
Click to expand...
Click to collapse
I was talking about the new VS recovery and please, please don't tell me they didn't include a re-partition function. Viewsonic>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I'll have to test this out later. Battery is about to die and I don't have my charger. I sure wish this thing could be charged via USB.
atakapa said:
I was talking about the new VS recovery and please, please don't tell me they didn't include a re-partition function. Viewsonic>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Click to expand...
Click to collapse
They did not in 3991, but I haven't looked at 4349 (yet).
atakapa,
We went through this when the UAT 3991 came out back well before the Wooters
came on board. Roebeet literally had to pull TTX, which is based on 3991, because
so many people were crashing and burning in bad ways -- boot loops, etc.
No the "blue recovery" does not have all the functions of CWM.
Unless someone can tell me a better way, if someone has boot loops or major problems
with 1.2.4349 loaded, they need to:
1. NVFlash back to stock:
http://forum.xda-developers.com/showthread.php?t=861950
Do the procedure exactly and do not skip steps, substitute files,
etc. This will take you to Version 2638 -- called bekit 1105.
It is time proven reliable.
2. Then set up wifi and follow the OTA update process to Version
3588.
3. If 3588 installs and runs fine, then Update again to 1.2.4349.
We may have to refine this as things develop, but losing CWM makes
things harder.
Rev
For the Curious...
Quadrant Standard -- 4 runs all in the 1700-2000 range.
If this is typical, not as quick as I had hoped. At least
as tests go.
Will have to talk about perceived performance later.
Rev
I didn’t see a recovery option in the recovery menu. I was able to get it back by doing the factory data reset from the Settings | Security menu. Now I just have to put everything back.
Has anyone tried installing the market on this yet?
Thanks
SgtJake said:
I didn’t see a recovery option in the recovery menu. I was able to get it back by doing the factory data reset from the Settings | Security menu. Now I just have to put everything back.
Has anyone tried installing the market on this yet?
Thanks
Click to expand...
Click to collapse
I'm not a pro at this stuff, but all my attempts to install the market have failed and the enhancement pack results in a semi-brick.
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..
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
bobstone said:
Just froze a couple.
Click to expand...
Click to collapse
There's your problem...
Sorry mate, but I can't help myself - attention everyone, here comes a rant:
I cannot believe how many people do not backup the data on their tablets! This is the second time in as many days that I read: "Something unexpected went wrong and I cannot loose my data".
If you did not back it up the question is not if you loose it, the question is WHEN!
This is a portable device! Pre-destined to be lost, stolen, dropped, submerged, spilled upon, run over by trucks - and those are everyday scenarios which are LIKELY. Don't even want to get into freak accidents... It's so easy to protect your data now-a-days! There's Dropbox in conjunction with Dropsync, there's Google Drive and a host of other solutions. There is no excuse for having only one copy of important data...... End of rant
To your problem. Before you apply a stock update you have to replace/unfreeze all stock apps. Usually the update just fails if you have frozen system apps - I do not know what went wrong in your case.
How did you update? OTA or manually?
It sounds as if your data partition is corrupted since the stock apps (installed in /system) work, but your user apps (installed in /data) do not. But that your system apps work is the good news! At least you didn't brick your tablet.
One of the stock apps is the file browser. See if you can copy your precious data to a microSD. And I'm only talking about data like pictures, files, video, projects. Don't worry about your apps.
If the file browser cannot see your data you're gonna have to get into the area of data recovery tools - lots of research ahead of you there.....
Another possibility may be - if you can access your tablet from your PC through USB - to ADB pull files off your tablet, check if your computer recognizes your tablet.
Once you have your data safe (or given up on it) you can perform a factory reset and possibly have to reflash the firmware.
BTW, if you did not protect root with Voodoo Rootkeeper before the update or if you flashed the full firmware (as opposed to doing an OTA update) you also lost root. And Asus plugged the hole Motochopper used in the latest firmware version. At this point 10.6.1.14.10 is not rootable without unlocking.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
bobstone said:
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
Click to expand...
Click to collapse
I would just wipe and start over, even if you get it functional again you could end up with problems.
Hmmm - I too think you are going to lose your data here as I can't see how you can recover without wiping if everything is force closing now.
BTW don't worry about the kernel version being cancer that is Asus naming convention. They have been using planets and have now run out so they are now using astrology instead of astronomy which is rather odd but there you go.
Previously we had mercury, venus, jupiter, uranus etc now we have aquarius and cancer......
What don't make sense and I can't accept, I've updated this device 4 times now total and never had a problem like this. Also, I've updated a few devices with frozen apps and had no problems. Are frozen apps really the cause? I can't see it.
And if I do have to wipe, and I really don't want to, will I still be rooted after wiping and is there a way to back up things since I can't use 3rd party apps? (Also, I used voodoo)
It just seems like something went wrong with the update, say something initializing or cache problem, and im sure there's an easy fix.
Please, keep the ideas coming...
I guess, I just need to clerify , stock bootloader, stock ROM, but rooted??
Sent from my [email protected]
Sorry all was reading it on the app wow that really is not good lol
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
bobstone said:
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
Click to expand...
Click to collapse
I think you will have to wipe mate as said. Painful but can't see any other way around it.
bobstone said:
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Click to expand...
Click to collapse
Yea, wipe, and no you won't keep root on a stock rom wipe. As I said previously even if you managed to "fix" the problem you would be creating potential for lockups/forced reboots. Your also not the first to have issues when upgrading with sys apps frozen, look around the forum, its been discussed before. Sucks, but there it is.
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
boy, i can't believe how close i was to actually going forward with this OTA when it "pooped" up in the notification area. good thing i had just been reading xda forums and i saw a couple posts bout ppl losing root and whatnot with said update.
now i am a happy camper on Cromi-x =D
best bet as a few already said is to try to extract your data from the thingy, and wipe it out, if you wanna take a n00b advice, if you're close to the end of your warranty period, go ahead and unlock it then proceed to cromi-x it. i was of the same position as you back when i bought it, not interested in custom roms and whatnot, just root...... but since my warranty was expiring next month anyways, and it had grown considerably sloppy and laggy, i figured out, why not? and i gotta tell you, it was the right thing to do.
hands down
anyways, good luck on your recovery.
I wiped and downgraded to .8 and will happily stay there for now. Maybe until I unlock the bootloader in the future.
vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
If you don't have it download Titanium Backup, hit Menu and wipe Dalvic cache. Reboot. The reboot will take a while because the Dalvic has to be rebuild - so don't panic
If that doesn't do it, I'm fresh out of ideas.
I tried to wipe via the stock recovery, but all the FC's was still there, and what's worse was that because of the FC's I couldn't finish (or quit) the "Set up your tablet" thingie. I always crashed on setting up a gmail account. Didn't matter if I was connected to the internet or not, or if I declined setting it up. So I had to do everything from the stock recovery.
Downloaded the .8 firwmare, unpacked the first .zip file, renamed the second .zip (to EP201_768_SDUPDATE.zip) and put it on an empty micro SD, made sure the SD-card was FAT32, booted to recovery (Power Vol down for 5 sec) and installed it via RCK, Android stock recovery.
Thanks for the tip, though. It might have worked. I don't know.
I have an XT926 running KKBL CM11 nightlies and have been updating through Cyandelta since Towelroot gave me an unlocked bootloader (thanks Geo). I have been updating without issue until the 11/07 nightly. Ever since then, Cyandelta shows no updates but if I go through the CM Updater, it shows all of the updates released for the moto_msm8960. If I try to apply any of these updates outside of Cyandelta (either through CM Updater or flashing full zip through recovery), I can boot my phone but will start getting a persistent error saying "There's a problem with com.android.phone process and it has to close" or something to that effect. I have tried wiping both caches and even doing factory resets but the process crashing starts back within a few minutes of getting everything set up. I did notice that even though I did a factory reset, all of the apps I have installed still had data from before the wipe so I feel like the wipe is missing something that is causing the crash(?). I've been using custom ROMs for a while on a few different devices but this is the first time I've ran across this. Any advice?
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
CWGSM3VO said:
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
Click to expand...
Click to collapse
I've never had to go further than a factory reset before. Which partitions should I format?
I'd format system, data, cache and dalvik. Definitely time to flash clean.
When I had my XT926, I also found that after so many updates via Cyandelta, that I would get the same issue. I would then go back, clean flash the latest update and things would be good. I eventually stopped using Cyandelta altogether. It's a nice idea, but I just don't know if I completely trust its abilities in determining what to bring down and what not to. I'd rather go with the CM updater instead. Yeah, it means longer downloads, but which is longer: downloading the full update from CM and having it work, or downloading via Cyandelta and then having to wipe clean, install and then restore all your backups?
iBolski said:
When I had my XT926,
Click to expand...
Click to collapse
You did abandon ship!
lloydsw said:
You did abandon ship!
Click to expand...
Click to collapse
Yup, but I stated in my post (where I said my goodbyes), that I would still hang around and help out. I know there are a lot of people still on this phone, especially with CM12 now running on it.
But, loving my G3. Still on stock, though (4.4.2), but I have no reason to go to anything else right now. Runs smooth, but it is rooted so I can run TiBu and also enable SD writing. But, I have no other reason to go to CM12 at this time.
I can get at LEAST one day if not more. Usually, after 24 hours, I'm right around 50% on battery. I probably could go even longer, but definitely I get more battery life out this phone than I did on the XT926 (non-MAXX), but I was able to do the same on my non-MAXX, but only if I didn't use it much. With the G3, I can do quite a lot and make it through the day without having to recharge during the day. I love that!
In any case, I'm still lurking about these forums to see if anyone needs help.