Decided to do the ota this morning, used ota root keeper to backup root, didn't unroot before update, went ahead and did ota (did not have to install manually) after update was done, I got a constant fc on launcher, rebooted, same thing, was able to get into settings (everything on the bottom bar was visible/usable but nothing above it, just wallpaper) cleared cache and data for launcher, still no go, rebooted once more, and after it rebooted, it gave me a message saying encryption was unsuccessful and none of my data was accessible, and only option it gave me was to do a factory reset, went ahead and reset it, and I still get nothing on the launcher. Any ideas?
If there's another thread on this already, please point me in that direction. Idk where they put the search button (used to be next to forum tools, now it's gone)
Related
I used the 1 click toot method and thought I may return my fascinate. I decided against it and tried to root again with no luck. The root always has a bunch of FC's and eventually gets stuck. The generic ringer also starts with no way to stop it. Only a battery pull will restart the phone afterward. I have also already really installed the Samsung drivers for the phone. Anybody have any thoughts?
Did you go back to stock via odin...if not do so...and push root manually...instead of an app.
I did through Odin. Tried to push root manually last night. The phone froze right after the push and never recovered. Had to battery pull. I had all of the files pushed and got to the chmod and wait stage when it froze.
Hmm, maybe re push to stock in odin...make sure you are doing the correct files...though it sounds like you did...a second time around sometimes seems to hit the spot...droid used to give me the same issues with sbf.
Do a factory data reset after you redo the odin recovery. Make sure you are using the verizon file when pushing each flash and doing it in the proper order. Then manually root, dont use one click or an app.
Also remember to push the files one at a time and let the phone restart between each one booting back into download mode.
Sent from my SCH-I500 using XDA App
I've been working all weekend so I havent had too much time to deal with it. I wiped data and cache in the recovery menu initially and then the phone wouldn't allow me to sign back into my Google account. It kept telling me that I didn't have a data connection on 3g OR wifi. I finally did a factory reset through the privacy menu (not in recovery) and all seems to finally be working and completely stock. Now off to root and flash voodoo...
hey i had the same problem i made a post on how to fix it though.. go to the 0.00 internal storage issue mine was doing what u said plus more but i fixed it just follow the steps i set
http://forum.xda-developers.com/showthread.php?t=804457
Got it. Just for the record: Rooted, Flashed all three files with Odin to get "back to stock". Re-OTA'd. Somehow Busybox and Su were still there so I manually removed. Then changed my mind about returning the phone and attempted to root again with no luck. Re-flashed through Odin ok, then attempted root but errors prevented finish. Cleared data and wiped cache through recovery. Then my google account wouldn't resync b/c of network connection error, even though I had a working data connection the entire time. Tried booting into recovery and clear and wipe data again. No luck. Finally decided to use factory data reset from within settings. Now all clear, rooted again, re-synced my google account and all good. You guys rock. Thanks for the help.
I have searched previous threads and can't figure this out, so excuse me if it's been asked and answered, I can't find it.
I got one of the Woot G Tablets. It had the verson 1.1-3389, as they all apparently did. As soon as I got WiFi working, it did the automatic OTA update to 3588.
A few days later I installed Clockwork Mod on it. Later still I rooted it using SuperOneClick. Got the Market going, etc. etc.
Yesterday it gave me a notice about the 4349 update. I tapped on "clear" because I wan't interested in that. Later the ! icon lit up again. This time I checked it and it said "Click here to download update 1.1-3588".
Huh???
So I checked and sure enough the version is listed as 3389. Now, I don't guess it matters how that happened. I'm just wondering, if I let it do an OTA upgrade to 3588 will I lose root?
I also hope that I don't get in an unending loop of update --> root ---> lose update ----> update ----> root ---> lose update and so forth.
Thanks in advance.
NinetyWt,
I don't think the root installation had anything to do with this
phenomenon. This sounds more like something either didn't
install and you just didn't realize it -- or something reinstalled
and old version and you didn't know it.
I am surprised that you got the update notice with CWM
installed. Usually if you have CWM on board, it won't
update.
I can suggest a course of action, but I can't guarantee
that you might not have to do some adjustments/re-installs
as a result.
1. Let it try to do the Update to 3588 -- but watch to make
sure it downloads, and watch to make sure it installs and
watch to make sure it reports that it installed. After it's
all finished, if it says it updated check that in Setting/About.
Make sure you are satisfied it updated.
2. If you are successful, then shut down. Then boot into
recovery by simultaneously pressing Power/Volume + until
you see the "Recovery Key Pressed" message. If CWM is
still installed you will get the green menu. If not, it may
look for an update and not find one. Main thing is to
find out if CWM is still installed. If not, we're good to go.
3. If success to here, then I'd play with the tablet, install
a few things, check configurations and make sure everything
is working right.
4. All things to here done, you should have a working, stock
tablet that you can do what you want to with. (BTW, don't
add any Enhancement Packs, etc. until you know things are right
Hope this helps. Let us know if it works and gets you going!!
Rev
Alrighty, thanks for the suggestions, neighbor.
1. Told it to do the update, it starts, then I get a gapps error. Force close that. (I bet I just lost Market.) Continuing to download ... done. "Apply update", something threw a force close error but I couldn't read it as the tablet started rebooting.
Now I have the android with yellow exclamation point. Trying to boot to clockwork... it's still there. (I have bekit 0.8). Will try to reboot from here.
2. Tablet boots fine, but install of 3588 is not successful (throws error "update was not applied... try again later".
Looks like, if I want 3588 back, I have to uninstall CWM.
Hah, the alert is back.
NinetyWt,
In you still have CWM v.8 working, go in and do all the cleanup routine. Go to
Advanced Menu and run Partition (2048/0), Fix Permissions and Wipe Dalvic Cacher.
Then to Main Menu and run Wipe Cache and Wipe/Reset Factory Data.
Then see what will work.
If it won't work after that, I think your best bet to is NVFlash back to stock Bekit 1105 (Version 2638) and let it OTA up to 3588. If that runs good and you can add apps, etc. then you would be good to go to do whatever you wanted.
Rev
P. S. - I did hear you about the file closes, etc. The cleanup I recommended should
put that straight.
I am with you on what to do. First I wanted to try manually installing the 3558 update. I got the file from here:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
Trying to install with CWM. It says it installed but it throws two 'unknown command' errors having to do with the bootloader. I suspect my next trick will be to wipe data.
Whatta ya know, it seems to think it's on 3588 now (Settings ... About). I no longer have the market, and Titanium Backup says I no longer have root.
I am not going to worry about that stuff right now. Thanks for your good advice Rev.
Hey, everyone, I didn't see any specific posts on this topic, combined. My new GS4 had two problems.
1) I didn't switch the su binary to SuperSU before swapping back to the stock kernel, and I got the unlocked padlock at boot with "System Status Custom" in the Download screen
2) GPS never worked
I tried going back to the stock kernel, properly rooting, etc., but could not get my phone, no matter how many reboots, to go back to "normal" and not recognizing a custom binary. This was finally resolved by a factory reset through the Accounts menu in settings. The first reboot after the full wipe the phone does from recovery still showed the unlocked padlock, but upon one more reboot, the phone boots normally again. I have not yet attempted re-rooting.
The complete factory wipe also fixed, for whatever reason, my GPS problem.
So, if you are having either/both of these issues, I can tell you that, for me, a Factory Reset seems to have resolved them both.
I'm posting this hoping any others having these issues might fast-track themselves to a solution.
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
So, starting from the beginning.
I wanted to root my Verizon G3. I didn't have access to a computer and I used king root to root the G3. I used root checker just to make sure the phone was rooted. I got rid of kingroot completely and installed super SU. SU said binary was not installed so I clicked the normal when it asked me how I want to install the binary. I pressed reboot phone and left. I came back 20min later to see that the phone said "android is updating, optimizing apps 1 of 1". I then pulled the battery out, turned the phone back on and that's when trouble started.
When the phone finished booting I swiped to unlock the phone and the screen was black, with the soft white buttons at the botom and I could still see the task bar with the battery percentage and time . I then pressed the recent apps button and tried going into chrome. Chrome was frozen. I then pulled down the Taskbar and went into settings. I wasn't to sure what was happening so I decided to factory reset the phone . I then went into data and backup and clicked on factory reset and delete all. I waited 10 minutes and nothing was happening.
I then decided to do a hard factory reset. After the reset I was met with the setup wizard . I selected English for a language and next. The Black screen, task bar and soft keys were showing up as it did earlier again and it went straight back to the setup wizard and select Language.
I tried to see if safe mode was any good, so I booted into safe mode and had the same results.
I think it's now stuck in a setup wizard loop. It seems like some files were corrupted during the SU binary install or reboot.
Any suggestions? Or clarifying questions? Thanks.
Hi!
Flash the 10B TOT using the .DLL that's extracted from the 35B KDZ. Both files are available at my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, also in my signature below.
Flashing the TOT will wipe everything including internal storage.
Then root using the Stump app that's on XDA using the brute force option, use TWRP Manager from the Play Store to flash TWRP, in TWRP wipe Cache, Dalvik/ART and Data, flash the ROM you want and the appropriate Bootstack.
Avoid Kingroot whenever possible, it's horrible and leaves things behind, and often causes problems when people try to switch to SuperSU.