I have spent the past week on this problem , including reading ppcgeeks & ppckitchen threads for hooouuuurrrs. And still no working phone!
What I have: ActiveSync 4.5 on an XP desktop. I successfully RUU WM6.1 onto my Alltel PPC6800, had the upgraded radio, internal GPS worked.
The problem:
From the Bootloader screen, without ActiveSync, I flash a ROM. After RUU says it was successful the Mogul resets. No LEDs light up and the screen stays off. I Hard Reset. The Green LED comes on and stays on.
I’ve removed the battery and Hard Rest and Soft Reset with the result being that just the Green LED stays on.
Whenever I use the RUU the current ROM version on the phone is not displayed. But the RUU lets me continue.
I can always get the Bootloader (tri-color) screen, which has:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
After re-flashing the stock WM 6.1 ROM, the phone gets into a reset loop with nothing displayed on the screen and the Green LED blinking.
I’ve re-flashed 2 previous Kitchen ROMs that worked originally.. No change.
I’ve removed and then reinstalled ActiveSync. Rebooted XP. Still no connection.
I’ve removed and reinstalled PPCKitchen with successful updating. Rebooted XP. No change.
I’ve tried to flash from my fats formatted 2gb SD with renaming RUU_signed.ngh to “TITAIMG.nbh” and copying it. Got the Grey screen with progress bar. Then Hard Reset. No change.
I’ve tried every combination of Soft reset, Hard reset, battery removed combination with each ROM flash.
I’ve tried the Titan Exit Bootloader exe. This was successfully executed but did not solve the problem.
I’ve tried flashing the radio but I get a Bad Command error.
Update: In an attempt to diagnose the source of the problem by eliminating my cooked ROMs as the problem, using the SD method, I Flashed third parson's cooked Alltel ROM.
By all indicators the Flash was successful. I have Hard Rest (pushing the "R" then "space bar" when told to do so) several times. (Once I removed the battery for several minutes then Hard Reset.) But I still have the same problem of after Hard Reset the Green LED stays on and the screen appears to be off.
Since I am having the same results with my cooked ROMs I believe that my Bootloadeer and ROMs are OK. (Looking for confirmation here.)
Then is the problem with the radio? Or is it a hardware problem?
Any help is appreciated!!
Maybe try updating the radio? As far as I remember there were a few radio versions that did have internal GPS enabled but are still incompatible with the latest ROMs.
What radio version are you running now?
WatchOut said:
I have spent the past week on this problem , including reading ppcgeeks & ppckitchen threads for hooouuuurrrs. And still no working phone!
What I have: ActiveSync 4.5 on an XP desktop. I successfully RUU WM6.1 onto my Alltel PPC6800, had the upgraded radio, internal GPS worked.
The problem:
From the Bootloader screen, without ActiveSync, I flash a ROM. After RUU says it was successful the Mogul resets. No LEDs light up and the screen stays off. I Hard Reset. The Green LED comes on and stays on.
I’ve removed the battery and Hard Rest and Soft Reset with the result being that just the Green LED stays on.
Whenever I use the RUU the current ROM version on the phone is not displayed. But the RUU lets me continue.
I can always get the Bootloader (tri-color) screen, which has:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
After re-flashing the stock WM 6.1 ROM, the phone gets into a reset loop with nothing displayed on the screen and the Green LED blinking.
I’ve re-flashed 2 previous Kitchen ROMs that worked originally.. No change.
I’ve removed and then reinstalled ActiveSync. Rebooted XP. Still no connection.
I’ve removed and reinstalled PPCKitchen with successful updating. Rebooted XP. No change.
I’ve tried to flash from my fats formatted 2gb SD with renaming RUU_signed.ngh to “TITAIMG.nbh” and copying it. Got the Grey screen with progress bar. Then Hard Reset. No change.
I’ve tried every combination of Soft reset, Hard reset, battery removed combination with each ROM flash.
I’ve tried the Titan Exit Bootloader exe. This was successfully executed but did not solve the problem.
I’ve tried flashing the radio but I get a Bad Command error.
Update: In an attempt to diagnose the source of the problem by eliminating my cooked ROMs as the problem, using the SD method, I Flashed third parson's cooked Alltel ROM.
By all indicators the Flash was successful. I have Hard Rest (pushing the "R" then "space bar" when told to do so) several times. (Once I removed the battery for several minutes then Hard Reset.) But I still have the same problem of after Hard Reset the Green LED stays on and the screen appears to be off.
Since I am having the same results with my cooked ROMs I believe that my Bootloadeer and ROMs are OK. (Looking for confirmation here.)
Then is the problem with the radio? Or is it a hardware problem?
Any help is appreciated!!
Click to expand...
Click to collapse
Sounds like you need to just flash a new radio to your phone.... I had the same problem at one time and that fixed it...
Problem solved??
Skippyd, Thanks for the suggestion!!
Interesting Update: I started to take more risks. (All flashing was done by SD method.)
I re-flashed radio 3.42.50. Although the flash was completed there was no change in results. I re-flashed both ROMs that had worked and ones that had no change. And still no change.
Then I decided to flash any ROMs made for Alltel (Titan) that I could find. (I wasn't really seeing if the ROMs had radios in them.)
I flashed nueROM_MTitan-201-201-spackr.rar which booted to the 2nd splash screen [AAAHHH!!! something different!!!] The following information also appeared on the screen:
Nuekernel 3.01
Build 109(c) 2008 No2chem
High Mem (camera disabled)
HTC
M09
B03
P=DCAAXAM 4350H
R=3.42.50
D=3.56
After resets and re-flashes of this ROM I could not get past the 2nd. Splash screen.
I next went to the link from: http://forum.ppcgeeks.com/showthread.php?t=22132&highlight=boot+stop+splash (post # 3)
I flashed: Alltel_titan_20273_a2.rar . However, the result was the same as my original problem.
I skipped the .exe file that was in the list.
Then I flashed Nex_5054.8_Alltel_b3.rar and SUCCESS!!! It booted. (I did not install any of the CABs listed on the screen.) I can enter all of the menues. I don't know if GPS still works. The green LED flashes like it did when I could use the phone. (I can't use the phone now because I reactivated my old phone.)
I have not tried these other ROMs that are also listed:
Nex_5054_Alltel_b2.rar
Nex_5054_Alltel_spb'd.rar
Nex_Alltel_dcd_3.0.0.rar
Nex_Alltel_superBB_chick.rar
Before I do any more test-flashes, can anyone tell me:
#1) what additional information I should copy off my phone before I try these other ROMs?
#2) can anyone tell me the differences in the ROM that works and the ones that did not (so I know why Nex_5054.8_Alltel_b3.rar works)?
And #3) Does anyone have any suggestions before I proceed with testing other ROMs or try cooking my own again?
Thanks, in advance, for your help!
This week I stalled an app which totally ****ed up my HD2. I don't remember the name of the app, but installing it resulted in the following:
-Whenever I press the home hardbutton my navipanel starts up and it is very hard to turn it off.
-Whenever I open an sms or email the screen automatically tilts to the landscape mode and doesn't tilt back.
-Whenever I open opera browser the screen automatically tilts to the landscape mode and doesn't tilt back.
-Start softbutton not working.
This is all quite annoying so I did a reset to factory settings. However this didn't solve the problem, so I am assuming that dreadfull app I installed did an override on the factory settings.
So the next thing I tried was installing the latest rom from the htc website, which should have been an easy thing. However it failed midway. Now the issue is that my computer doesn't not recognize my HD2 anymore when I connect it with the cable.
So the question is? What do I do now? I was hoping anyone could help me with this problem. Before when I was a student I had plenty of time to search the net/forums for a solution, but now I am working full time and I already spend most of my weekend trying to solve this issue. So please anyone help me out
whopper said:
This week I stalled an app which totally ****ed up my HD2. I don't remember the name of the app, but installing it resulted in the following:
-Whenever I press the home hardbutton my navipanel starts up and it is very hard to turn it off.
-Whenever I open an sms or email the screen automatically tilts to the landscape mode and doesn't tilt back.
-Whenever I open opera browser the screen automatically tilts to the landscape mode and doesn't tilt back.
This is all quite annoying so I did a reset to factory settings. However this didn't solve the problem, so I am assuming that dreadfull app I installed did an override on the factory settings.
So the next thing I tried was installing the latest rom from the htc website, which should have been an easy thing. However it failed midway. Now the issue is that my computer doesn't not recognize my HD2 anymore when I connect it with the cable.
So the question is? What do I do now? I was hoping anyone could help me with this problem. Before when I was a student I had plenty of time to search the net/forums for a solution, but now I am working full time and I already spend most of my weekend trying to solve this issue. So please anyone help me out
Click to expand...
Click to collapse
i have to leave for work in 5 minutes so i won't be able to follow this up...but..
when you say factory reset, did everything else go back to what it was as you bought it?
1- can you get to bootloader (when booting up phone hold the "down volume"-- i think it is down, may be up. try it.)
2- if so you are good.
3- in bootloader flash hspl
4- flash new rom
I performed the factory reset multiple times and by 2 methods.
-setting->return to factory settings
-turning off the device-> press down the volume up/down buttons and press cancel call button
All settings were turned back to the original settings however the 2 problems (1: tilting screens and 2: unable to detect device on computer) did not disappear.
I tried to do what jsmccabe78 said, but my device just booted up like normal. No bootloader screen or anything.
I have anyone else has an idea.
Make a backup of your contact list.
And make a Hard reset!
In difficult situations, you can maybe use/do a "Task 29"
using the second option I described is a hard reset
try reflashing a stock ROM.
whopper said:
I performed the factory reset multiple times and by 2 methods.
-setting->return to factory settings
-turning off the device-> press down the volume up/down buttons and press cancel call button
All settings were turned back to the original settings however the 2 problems (1: tilting screens and 2: unable to detect device on computer) did not disappear.
I tried to do what jsmccabe78 said, but my device just booted up like normal. No bootloader screen or anything.
I have anyone else has an idea.
Click to expand...
Click to collapse
now what do you see when you boot your phone? have you tried deleting the settings for your phone on your computer for wmdc/activsync? 0have you tried uninstalling wmdc and reinstalling? try those first.
now, if your computer still does not recognize your phone your next option is to load another rom - whether it is a newer official rom or a customized one (your choice.) if you cannot connect your phone you will need to do this with bootloader.
if you can boot your phone, you can get into bootloader.
to get to bootloader:
turn phone off.
hold "volume down" button key.
turn phone on.
this will get you to bootloader. if this doesn't work, i am out of ideas. you need a new rom and you can flash from an storage card, but you need to have hspl first.
let me know.
now you can 1- flash hspl and 2- flash new rom
Sorry for the late response jsmccabe78. Thank you for your response. I got my phone into bootloader mode which enabled me to make a link to my computer. I ran the stock rom that I downloaded from the htc website and it installed succesfully.
Unfortunately this did not solve the problems I described in the OP.
-Whenever I press the home hardbutton my navipanel starts up and it is very hard to turn it off.
-Whenever I open an sms or email the screen automatically tilts to the landscape mode and doesn't tilt back.
-Whenever I open opera browser the screen automatically tilts to the landscape mode and doesn't tilt back.
-Start softbutton not working.
Click to expand...
Click to collapse
Also my computer still doesn't not recognize my HD2 outside of bootloader mode. Reinstalling WMDC did not solve this issue.
I am still thinking these issues are software related and not hardware related. But reinstalling the stockrom should have fixed the issues if it was software related shoud it not?
So 2 questions remain;
1) How do I fix the issues in the OP
2) How do I get my computer to recognize my HD2 outside of bootloader
I hope anyone can help me solve this mystery.
Try it with no sd card in and see if you still have the problems? If you do :Take out your sd card and put it into your pc with card adaptor. Then delete the application data folder on your sd card. If that doesn't work make a back up of whatever stuff is on your sd card and then re-format it, then and copy back your apps and stuff. If you had a rough idea of what it was you installed try and leave that out when you copy your files back to sd. If you didnt have much on your sd card i would suggest to just wipe it totally and start again. Hopefully this should sort it, if not im out of ideas. Hope this helps if not soz but thought id try
I formatted my SD card, used the return-to-factory-settings function again and still the same issues. No connection to my computer and all the above issues... getting a bit desperate here...
Does anyone have an idea what could be the problem here?
I've flashed my phone to the stock ROM before flashing it to Artemis v42. However, the bootup time is extremely long and sometimes it hangs at the Windows setup screen (Preparing for first use). I've hard resetted after flashing Artemis and after a few resets it does startup (but still quite slow at the HTC screen with the radio version in the lower left corner). After I change the settings via Atemis Centre, such as No SMS Sent Confirmation and no "programs tab" in Manila 2 and reset, the phone would actually either hang at the HTC screen or hard reset by itself. I have Radio version 2.15 and flashed the stock ROM as recommended in the first post as well.
It seems that whenever there is some sort of registry modification, the HD2 would hang at the boot screen or hard reset by itself. If I don't do anything to the phone (change settings or even the wallpaper), then I can call and use the phone normally. I noticed that when I flash via SSPL, the SPL version shown is 1.42 but when I flash the stock rom, it shows SPL version 3.03. Is this normal? I even tried flashing V41 and the same things happen.
Strange behaviours include random hangs on the boot screen, disappearing files and programs that were flashed (such as wallpaper, they disappear or become inaccessible, and programs will have the "cannot be opened" problem).
Whenever I go back to the stock ROM, "RUU_Leo_S_HKCSL_WWE_3.14.831.3_Radio_15.42.50.11U _2.15.50.14_LEO_S_Ship" none of this would happen. Is there something I should try to prevent the problems? Or is my Asian HD2 not compatible with this custom ROM? Thanks!
Based on your information, the only logical explanations I can see is a wrong installation.
try it again.
I'm puzzled as to what could have gone wrong. I just download SSPL, rename the Artemis to the correct name, connect USB, flash. After flash finish, hard reset.
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.