Related
Hi there, I'm new here and I need your help.
My ViewPad7 haven't an original <3e> recovery because i get it from another and it run cooked rom.
Now i want to back to the stock rom following here: http://forum.xda-developers.com/showthread.php?t=1601117 but it need an original <3e> recovery.
Could you kindly help me to get it, if you have a backup of original <3e> recovery from your ViewPad7, please send it for me.
Or you can backup your stock recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=1015005 then help me.
Thank you so much. Sorry for my English.
Anyone, please help?
For Vpad7 - do you have the "older" non-ITE or "newer" ITE (multi-touch) screen - original/stock recovery image file or whatever?
If you aren't sure - post your Vpad7's production date, which is on the printed label on the back as that should help ...
I don't know about the 'non-ITE' or ITE screen of my device. Its production date is: 28-4 2011
Please help me!
Thanks Letitride
Based on device's production date, it's "most" likely an ITE device (there is nothing certain or definitive about it ...)
Okay, calvary to the rescue for fellow XDA's.
AS - please check your PM too (you got mail ...)
Letitride said:
Based on device's production date, it's "most" likely an ITE device (there is nothing certain or definitive about it ...)
Okay, calvary to the rescue for fellow XDA's.
AS - please check your PM too (you got mail ...)
Click to expand...
Click to collapse
I'm having the same problem here. Letitride can u help me out also?
Lanfear28 said:
I'm having the same problem here. Letitride can u help me out also?
Click to expand...
Click to collapse
Have you read the following thread & try it to see if you can restore your device ?
http://forum.xda-developers.com/showthread.php?t=1601117
If not or it failed, please be a little more specific about your issues and error messages/description of bootup problem, etc. ?
sadonsu assailants
I have the cwm recovery and cant get back the original <3e> recovery to flash the original Viewsonic firmware(v3_420)
@Letitride
Works like a charm
Lanfear28 said:
I have the cwm recovery and cant get back the original <3e> recovery to flash the original Viewsonic firmware(v3_420) @Letitride ... Works like a charm
Click to expand...
Click to collapse
Restored & working w the "alternative" *.img as referenced in PM then, excellent & enjoy the Vpad7 - only wished it's a bit faster, overclocking or whatever. But, it is what it is and loved the 7" factor, much easier to slip into a pouch, pocket, jacket, etc. to take along.
Is there anybody with original Viewsonic firmware(v3_420) and with working internet thru mobile data?
i got the viewpad7 back to original with stock recovery that i extracted it from stock rom, thanks
Hello, sorry for bumping this thread but it is relevant to what I need.
EDIT: Moving to thread for visibility.
I recently rooted my Viewsonic Viewpad 7 and put on a custom ROM. I noticed that wifi was not working so I tried some fixes, which none of them worked. One of those fixes involved formatting the sd card. After formatting, I realized I made a huge mistake as my backups are now all gone.
So I have the clockwork recovery installed (v5.0.2.6) and I think it is causing problems. I tried using Software Update Tool L3 (SUT L3) in order to restore the firmware back to normal using the .nbo from the Viewsonic site but I think I need the original <3e> recovery. Whenever I try to recover using the tool, it reboots the device into Recovery mode and after a few minutes I get the error:
Error Code: 0xc60e
Error: Download fail,
Error = SE_ERR_SUT_DETECT_DEVICE_FAIL (0xC60E).
I believe this is because it is expecting the original 3e recovery and doesn't recognize the clockwork recovery. I tried to find a copy of the original recovery.img but I can't find it online anywhere. This thread is the closest I've gotten. Please let me know if there is anything I can do to fix this. Or if anyone has a copy of the original 3e recovery, it may help me out.
Thanks!
FTM Mode Info:
SWVer=3.240
MODEL:FM6-0001
HWVer:107
clandor said:
... rooted my Viewsonic Viewpad 7 and put on a custom ROM ... So I have the clockwork recovery installed (v5.0.2.6) and I think it is causing problems. I tried using Software Update Tool L3 (SUT L3) in order to restore the firmware back to normal using the .nbo from the Viewsonic site but I think I need the original <3e> recovery. Whenever I try to recover using the tool, it reboots the device into Recovery mode and after a few minutes I get the error:
Error Code: 0xc60e
Error: Download fail,
Error = SE_ERR_SUT_DETECT_DEVICE_FAIL (0xC60E).
I believe this is because it is expecting the original 3e recovery and doesn't recognize the clockwork recovery. I tried to find a copy of the original recovery.img but I can't find it online anywhere. This thread is the closest I've gotten. Please let me know if there is anything I can do to fix this. Or if anyone has a copy of the original 3e recovery, it may help me out.
FTM Mode Info:
SWVer=3.240
MODEL:FM6-0001
HWVer:107
Click to expand...
Click to collapse
Are you using the "correct" factory *.nbo file with SUTL3 (which ver.) as it looked like your model is likely an ITE (newer) model ?
Can you boot the device into CWM Recovery mode now? Does it start up with the VS Android boot animation?
I will have to look for my backups as I've them on a backup server somewhere and/or in cloud storage ... will look & see what I have?
Haven't flash/done any factory restoration work on the Vpad7 in over a year+ now but, as I recall, flashing the *.nbo file via the PC with the factory update utility will wipe the device clean and restore it to factory fresh, locked mode so it should NOT matter what recovery you have on the device now.
Please describe in greater details the steps you took in trying to restore ... it's still a joy to go back to the Vpad7 but hard to let go of the new Nexus 7 quad-core "toy" these days for me ...
Thank you for your help.
I am pretty sure it is an ITE model. It's HWVer is 107, and I used this thread to help figure that out.
I downloaded firmware (.nbo) v3_420 and v3_62 from here. (Under Downloads > Drivers)
Here are the steps I took in order to try and restore.
I started off by enabling USB debugging and plugging in the tablet.
I opened up SUTL3 v1.7.9 and selected one of the firmwares (both yield same result). The update option I set to Erase user data. Once I hit next, it says Updating the Phone software, please wait.
The device restarts into recovery mode. The recovery menu title says CWM-based Recovery v5.0.2.6 which is a custom one I changed. I do not know how to get it back to the original as I have lost the backup.
After about a minute or so, I get
Error code: 0x4000
Error: Download fail,
Error = DEVICE_NOT_CONFIGURE (0x4000).
At this point when I retry using SUT L3 without leaving the recovery mode, I will only get the error from the previous post.
I'm not sure what my options are but my goal is to get back to the original ROM or get wifi working again on the current ROM. The current ROM I am using is CleanView Ice v1.3. I tried both the ITE version and non-ITE version and there seems to be no difference.
The only thing I seem to be able to do is Install ZIP from sdcard which lets me switch between custom ROMs but it doesnt fix the wifi problem or let me go back to original.
---
Edit: I tried doing the same thing a few more times with my antivirus disabled and it's still the same.
Also, I'm not sure if this will help at all but I tried to use the Synchronization tool that shows up on the PC when plugging in the device. It gave me the error "Can't access data on handheld! Please check the connection between desktop and handheld and at least enter Contacts once if you just clear your data!" These may be related as I have accessed Contacts and even added one in to test and this error comes up every time.
Maybe some kind of driver problem?
clandor said:
I am pretty sure it is an ITE model. It's HWVer is 107, and I used this thread to help figure that out.
I downloaded firmware (.nbo) v3_420 and v3_62 from here. (Under Downloads > Drivers) ... Maybe some kind of driver problem?
Click to expand...
Click to collapse
Okay, let's see - yours is ITE (UK-based) and running the same firmware as mine (USA) and v3_62 will work too, mine is on v3_420.
You still have working CWM 5.x on your device and can boot into it (small pin hole on the button to reset, etc.)
Okay, a # of points - the SUTL3 is run from the PC together with the *.nb0 file - running Windows XP or Vista, go the Command Prompt - Vpad7 drivers are already installed, give it a try - does it work as that will restore it to factory state - it should not need the Stock Recovery to flash it (I could be mistaken as it's been a while) Unpack the Zip file so that the utility will read the *.nb0 file directly.
First suggestio, however, is that if you have working CWM - my recommendation would be to flash from custom recovery, EUv1.7-ITE firmware in Zip file format - as linked here in Dropbox account of mine, OP/developer's link is no longer accessible or available. https://dl.dropbox.com/u/64025118/EUViewpad7v1.7b-ITE.zip
Download & transfer to mSD card, reboot into CWM, wipe dalvik cache, cache & system/full reset - then, flash the zip file and it should be done in about 10 minutes, be patient and go thru the Setup - if all goes well, your ITE device is back to life again. This is my preferred ROM and WiFi works well, if necessary - do a Master Reset again from the running Rom if necessary, reboot once & then setup your WiFi again.
Turn-off Antivirus & Firewall on the PC while flashing ... let me know whether you can get into the EU Rom as it will save you the extra work of going stock and rooting, etc. if your original challenge was just trying to get a good WiFi signal.
The previous times that I tried to install the .nbo files with SUT L3, I extracted them from the zip.
Also, I got firmwares on the UK site but I am Canadian. Most likely mine is also USA-based as many of our electronics are. I just could not find the files on the USA site.
I am running Windows 7 so some drivers installed automatically. I did use Setup.exe to install some other drivers but I have noticed no difference between the two times. Running setup.exe doesn't install anything anymore.
--
Here are the steps I took after your post:
I first transferred EUViewpad7v1.7b-ITE.zip to the microSD card and after rebooted into CWM-based Recovery. I wiped Dalvik cache, cache and "data/factory reset". I then flashed the .zip file and restarted the device after it finished loading.
I noticed the new intro logo so it seems switching the new ROM was a success.
I went into wireless and network settings and I turned on Wifi in the Wifi settings. The device scans for networks for about 30 seconds, then stops and displays "Unable to scan networks" and turns off.
I know for sure there are networks in the area and the wifi was working before I swapped to another ROM.
This is where I am currently stuck.
Again, thank you for your help.
clandor said:
... Most likely mine is also USA-based as many of our electronics are. I just could not find the files on the USA site. I am running Windows 7 so some drivers installed automatically. I did use Setup.exe to install some other drivers but I have noticed no difference between the two times. Running setup.exe doesn't install anything anymore.
--
Here are the steps I took after your post:
I first transferred EUViewpad7v1.7b-ITE.zip to the microSD card and after rebooted into CWM-based Recovery. I wiped Dalvik cache, cache and "data/factory reset". I then flashed the .zip file and restarted the device after it finished loading. I noticed the new intro logo so it seems switching the new ROM was a success.
I went into wireless and network settings and I turned on Wifi in the Wifi settings. The device scans for networks for about 30 seconds, then stops and displays "Unable to scan networks" and turns off. I know for sure there are networks in the area and the wifi was working before I swapped to another ROM. This is where I am currently stuck ...
Click to expand...
Click to collapse
Great, that's major progress - first, let's check & verify a few things and do it step-by-step:
Go to Settings - About phone - check that the following is same or similiar (they should be identical or almost)
Android 2.2.2
Baseband PR3.7_125
Kernel version Apps_2.6.32.9
Build number 4027_3_420
Check under Mobile network settings -
Data enabled (it should NOT matter, only if you are using a Sim card for voice and/or data in Canada)
Under WiFi settings -
WiFi - enabled, cycled it OFF and ON again, does it see various open and/or secured networks nearby
If NOT, press the soft "Menu" key on the lower right (in landscape mode) - it should open up & show "Scan" & "Advanced"
Can you do a manual "Scan" - make sure you have a known working WiFi, either secured or open (McDonalds/Starbuck or public library, etc.)
Next - open "Advanced"
Wi-Fi sleep policy (mine is set to "Never when plugged in" - try to temporary set it to "Never" for this purposes
MAC address - the unique ID for your device should be shown
Tap the WiFi network that you wanted to connect to - check its setting/status for Security, Signal strength, Link speed & IP address
If it previously connected but no longer worked, press "Forget" to delete it, and when it attempt to reconnect (if it is a secured one) - re-enter the password to see if you can connect.
For your restoration purposes, you might want to use WEP or WPA instead of WPA2, or even temporary changed your router to an "Open" WiFi so that any devices including the Vpad7 nearby can connect insecurely, assuming that your router is assigning DHCP automatically and giving out its IP address.
If NONE of these steps are working still, go back into WiFi settings and manually delete any and ALL saved stored networks (named) on the device, leaving just "Add Wi-Fi Network" as the only option.
Next, run a TB backup of your Apps if necessary and boot back into CWM, and do a Backup first to your mSD card (and cover it to a PC if necessary, as you can always restore it back instead of going thru flashing & Set-up) and you will have working boot.img (kernel) saved along with system, etc.
Exit and boot back to ADB (Android) Go to Settings - Privacy setting, and hit "Factory data reset" - next go first into CWM again, wipe dalvik cache & cache again, then continue with regular Setup including WiFi - your device should be able to pickup a nearby & strong WiFi signal.
If all these are still not working, you will likely need to get to a PC or laptop, earlier users had reported having issues with Win7 OS running, I would recommend borrowing/using one with Vista or XP-SP3 running, make sure the USB device drivers are automatically installed first and that it recognize the device. Then, reconnect and run SULT3 and flash the factory *.nb0 file - as I also suspect that there might be other hidden USB device drivers on your existing Win7 system that's casuing the *.nb0 installation to fail.
Keep me posted on your progress and any error messages or crashes (FC) encountered.
(Apparently, some of the custom Roms ended up "corrupting" the WiFi settings and codes, leaving residual settings that casued it to stop connecting to WiFi's - if you look & check some of the posting under "Development" (for some of the Rom's) - you will see some discussions about it. The EUv1.7 custom Rom (non-ITE was initially done and ITE later on) is among the better ones with few WiFi issues to speak of, 15+ months later, still relatively bug-free and updated all the Apps and add-ons of my own from Google Market (Play Store) automatically, with working Flash Player patched, and Angry Birds happily running along - the CPU is slow but with App2SD helping, not too bad for a device running Android 2.2.2 (Froyo)
I checked the settings in the About section and they are identical to the ones you posted.
I left Data enabled however I haven't inserted a SIM card throughout this whole process. I have no data plan anyways with the current SIM card I am going to put in.
Under the advanced settings in Wifi, I changed the sleep policy to Never and the MAC address says "Unavailable". So far there is still no result. I will try connecting in an area where I know there are open networks later today as I live in a public house where I have no access to the router's settings.
Also just a note about cycling Wifi ON and OFF, it automatically turns off after the message "Unable to scan for networks" shows up and no networks actually show up in the Wifi Networks section throughout the whole process. It stays empty even though there are networks around.
There are currently no stored wifi networks either so Add Wi-fi Network is the only option. I recieved this device from someone recently and I completely formatted the mSD card to start fresh so losing any sort of data is no problem to me.
---
I used the backup option in CWM to create another backup and after that I backed up the mSD card through USB to keep the working boot.img and other stuff onto the PC.
Under privacy settings I selected Factory Reset and let the device do its thing. I noticed the intro looked like normal however the Android's "theme" is still like the EUv1.7. I went into CWM and did a dalvik cache wipe along with a cache wipe and reset the device.
I tried the wifi again at this point and still no change.
I also tried SUT L3 with the .nbo and I yeild the same errors as before (0x4000 first time when using from Android screen, 0xC60E after the first time when using SUTL3 without leaving recovery mode).
--
I will test open wifi later today and I will edit the result. I'll also take a look at the discussion on wifi not working around the development forum. Thank you.
---
Edit:
I tested it out on some wifi networks without any protection and still none showed up.
I also noticed that if you right-click the Setup.exe icon in the taskbar after plugging in the Viewpad 7 it gives you the option to uninstall everything that the setup installed. I tried uninstalling and running SUT L3 but there was no difference. Also no difference after reinstalling, just so you know.
clandor said:
I started off by enabling USB debugging and plugging in the tablet.
I opened up SUTL3 v1.7.9 and selected one of the firmwares (both yield same result). The update option I set to Erase user data. Once I hit
Maybe some kind of driver problem?
Click to expand...
Click to collapse
I re-read some of the posts about flashing & restoring factory ROM, and it mentioned turning OFF USB debugging mode (from within the device's Settings - submenu) before -
If you want are ready to give up on this donated/given to you device, you might want to try this as a last resort - then, run SUTL3 with the *.nb0 file to restore it to factory stock condition - and hopefully, get the WiFi working.
From your last description of the error MSG - MAC address unavailable, the settings are definitely corrupted / damaged. Some of the Vpad7 owners had to RMA back to Viewsonic for repairs, obviously it is beyond the warranty and not worth the expense now with this "aging" Froyo OS.
The solution, as you probably read it by now, was to wipe clean & go back to stock, root it again and then try a different custom ROM ...
* * * * * * * * P.S. Please check your PM/in-box for a special message [/B] * * * * * * * *
KWBR V4.2 custom Rom, still available for download, will work with ITE hardware - http://forum.xda-developers.com/showthread.php?t=1386469
Since your CWM is still working, give it a try by flashing and perhaps it can get your WiFi working.
I ended up fixing the problem.
I downloaded PdaNet (PdaNetA350x64.exe) and installed it. I used it to get some drivers for the Viewpad 7 when plugging it in. After that, I replaced the custom recovery menu with an original recovery menu file. Once the recovery was back to normal, I tried running SUT L3 and using the v3_420 .nbo file. It worked fine that time and my device's software was back to default.
--
Afterward, I rooted it and put on a custom recovery menu again. This time I used EUViewpad7 v1.7b ITE version and it did not break my wifi. My original cell phone broke and this device will serve as a pretty good replacement for a little while.
Thanks again for your help, Letitride.
Problem: I think I deleted my OS.
Here's what happened, i rooted my Samsung Note 10.1 using the clockwork mode with the super SU, then it went fine, I installed apps I got on net, then (after 4 months) i got a glitch wherein I cant copy/paste words, so I decided to reset to factory setting, then done. I thought of other way to root my tablet. I went to setting where it says Encrypt device, I started encrypting then interrupted it, when it rebooted it says that encryption interruped and I need to rest to factory setting then try to encrypt again, and asks to press the reset device, and I did. What happened is it keeps going back to encryption failure message and I keep on pressing reset device till it will only turn on with the SAMSUNG NOTE 10.1 Logo (the startup logo), then I tried installing clockwork mode again, and select wipe factory reset, and wipe cache partition and almsot all wiping option, so obviously i wiped my OS. I tried installing the Android 4.0 Ice Cream Sandwich following this guide on youtube Guide - How To_ Install Official Android Ice-cream Sandwich (cant post the link). When I followed it all it always failed in the end, and on my tablet it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again", and I cant connect to Kies and PC to do the firmware emergency recovery. Now I'm stuck in there and kind of thinks that I'm lost and totally broke my tablet. But still I can be in download mode.
Any brilliant answers guys. Thanks much in advance.
Back Up
Is a fast connection needed while installing the OS via Odin since it says Firmware Update Started?
And can anyone send me a links to download a functioning Android 4.0, Ice Cream Sandwich OS, please.
XENO_cohen said:
Problem: I think I deleted my OS.
Here's what happened, i rooted my Samsung Note 10.1 using the clockwork mode with the super SU, then it went fine, I installed apps I got on net, then (after 4 months) i got a glitch wherein I cant copy/paste words, so I decided to reset to factory setting, then done. I thought of other way to root my tablet. I went to setting where it says Encrypt device, I started encrypting then interrupted it, when it rebooted it says that encryption interruped and I need to rest to factory setting then try to encrypt again, and asks to press the reset device, and I did. What happened is it keeps going back to encryption failure message and I keep on pressing reset device till it will only turn on with the SAMSUNG NOTE 10.1 Logo (the startup logo), then I tried installing clockwork mode again, and select wipe factory reset, and wipe cache partition and almsot all wiping option, so obviously i wiped my OS. I tried installing the Android 4.0 Ice Cream Sandwich following this guide on youtube Guide - How To_ Install Official Android Ice-cream Sandwich (cant post the link). When I followed it all it always failed in the end, and on my tablet it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again", and I cant connect to Kies and PC to do the firmware emergency recovery. Now I'm stuck in there and kind of thinks that I'm lost and totally broke my tablet. But still I can be in download mode.
Any brilliant answers guys. Thanks much in advance.
Back Up
Is a fast connection needed while installing the OS via Odin since it says Firmware Update Started?
And can anyone send me a links to download a functioning Android 4.0, Ice Cream Sandwich OS, please.
Click to expand...
Click to collapse
I'm not sure if this will help but Heimdall might fix this problem, whenever I fix my device after stuffing up a flash (happens often so don't worry!) I use both Heimdall and Odin to fix it, I have never been completely stuffed because of those two tools. My best advice is to search the Note 10.1 forums, they normally have the stock android or a new and better ROM ready to be flashed. It's good that you can access download mode which means its only soft-bricked, so just check your forums and that should help you fix it
As an introduction: When it comes to mobile platforms I'm more or less as green as they come - so forgive my ignorance regarding... Everything
I recently misplaced my beloved Nexus 4's flipcase. The day it went missing, I managed to stumble and drop my phone a distance onto tiles . It landed at such an awkward angle that the screen not only cracked but pretty much shattered - killing what I believe is known as the digitizer with it. It won't respond to touch.
Distraught I took up my dad's old Galaxy S3 - which was only cracked and a bit eaten (puppies). I went straight into using it and due to a demanding schedule I didn't have time to recover any of the data of the N4 - which I don't know how to do anyway. I quickly learn that I hate Touchwiz and the lack of personal details wakens me to how reliant I am on my phone.
So I set aside some time to get root - load a custom ROM (pa) - and transfer all my data from the N4 to the S3. The first difficulties appear when the S3 rejects towelroot. I install the towelroot apk from the official website and run it. Towelroot tells me it's currently an unsupported device. I google the model number (i9300) and apparently it works with Towelroot. Weird - I guess I'll do it manually.
So I install odin and download what I need and get the drivers for the S3 working and get root. It works without a hitch (I think until later ). Next I look into how to get a ROM on my phone. This happens: http://forum.xda-developers.com/par...s-7-error-installing-pa-t2844044/post54744770 (that's my post btw so it's the exact scenario). I will say that while I was going through this issue I tried many things to try and get rid of the error - I played with CWM a lot - tried to update it - updating failed with unknown errors. - I tried to flash my recovery - it couldn't flash my recovery. Earlier I had tried to install the CWM recovery on it's own from the play store (again - total noob) I only got related versions of CWM from 2011-2012. All of these problems were pretty confusing - and eventually due to the generic error about not being able to flash my recovery I had no idea how to proceed so I did as advised in the thread above and installed Flashify.
Flashify told me I had root, but that it couldn't get access to SuperSU - and to delete SuperSUs memory of Flashify. I went to SuperSU and SuperSU told me that it needed to update my binaries (I don't even know what my binaries are?!). I tell it it can go ahead and it just says "installation failed" so I install SuperUser to try and replace SuperSU - and delete SuperSU. And Flashify is clinging to the remains of SuperSU. Between my odd model identification (TowelRoot - Status 7 error) and my devices seeming lack of compatibility with.. Anything really (I imagine the two are related). I decide to clean slate it with a factory reset. Which I do from the CWM BIOS (?? Volume up + Home + Power?).
So of course unlike any phone I've ever worked with - a factory reset now means wipe my SIM. (Okay that was laziness and stupidity I should have taken it out first but allow me to grieve). As I should have predicted but didn't it wiped all my backups (foolishly saved onto the internal SD card) and leaves me in the fetal position on the ground making howling noises shedding tears onto the floor.
I can't afford a new phone - or to repair my old one. I need the data off my N4 - who's touchscreen doesn't work - which is problem number 1. And I would really rather not live with touchwiz, or have to do half the process again when I otherwise find the time to get rid of it, so I want to do that now but there are so many errors and I have no idea what I'm dealing with - which is problem number 2.
So please, if anyone can help me out with a)Getting the data off my N4 (it is properly set up as a mass media device) and b)Fixing this seemingly banjaxed S3 and getting pa onto it.
Any help would be really gratefully received. It's been an awful weekend - I also lost a hard drive with all my work and a lot of personal data on it to natural causes.
Thanks - I eagerly await my knight in shining armor.
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Same issue here... Finally decided to upgrade the system from stock firmware, and got "error" when it rebooted the phone. Then "no command".
Darknezz89 said:
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Click to expand...
Click to collapse
I solved my issue by restoring Lollipop (v.39) with the tool from the wiko website and then performing the update again; the phone started again (at v.41) and I was able to download Marshmallow from the next system update.
Issue was probably caused by some configuration or application.
Still slowly downloading Marshmallow now, so cannot say anything about the next update, but I guess that will go well, since the phone is reset now.
Just to follow up: Marshmallow is working fine on my Wiko Fever, much better than Lollipop. Amazing update.
Instructions for others after having read some comments from other people experiencing issues with the upgrade:
- BACKUP all your data before upgrading from Lollipop to Marshmallow, as if you would buy a new phone; I luckily did, as I wanted to set the microSD from removable to internal
- remove the microSD and (after having a backup of all your data as per step above) format the card as FAT32 on your PC; better to have a clean MicroSD card for after the upgrade I think
- reboot the phone in recovery mode and do a: wipe cache+reset to factory settings
- once the phone is reset and started, proceed with upgrading to Marshmallow
- don't know if needed after the upgrade to do an additional wipe cache+factory settings reset, doesn't harm to do it though
- be unhappy for the hours lost in restoring the phone data + apps + reconfigure everything
- be happy of the improved phone software
Questions upon questions.
So, i got the notification for the update last week, and i saved it until today to install it. The file downloaded was just 7 mb, i had enough battery for the intallation of the update (30% recomended by the software), something got messed up and an error message with the dead android character appeared. I know i lost all my things contacts and sd card... tried to hard reset the damn thing and nothing. I already googled the problem and i found nothing similar to what i get, i'm stuck in the recovery screen and the phone doenst shut down, every time i force it, it just boots back up after 15 30 seconds. I got to be honest i tought it was just another update but aparently its a "new" operating androind system. They could have told me with a update log or something...