Hi, I have bought a AW-414 from a chinese reseller and I have ton of issues with it. I'm struggling with it for a month now :silly:
I'm glad that I found this forum, it enlights my hopes.
Device: AW-414
Changes made to stock firmware (if any): I factory resetted the settings with the factory mode
What OS is on your PC if your PC was used: Linux Mint 14 / Windows 7
Issue: My bluetooth doesn't detect any devices (It does work on the chinese factory mode, but not using the android menu), I got a random boot loop that prevents my watch from being used more than 2 minutes, and my AW-414 freeze when I try to make a call.
Steps Taken: I... did a factory reset. I lost my IMEIs. I didn't know what to do at that time. I followed the tutorial to set two new IMEI of some old crappy phones that I had instead, it worked (I don't have Unknown IMEI anymore), but it didn't resolve any of my problems.
I'd like to replace my firmware, because I think that it is software related, it is my only hope :crying:
Therefore, I followed the tutorial throughfully.
I'm stucked to this step:
Go to the folder where your firmware is located and select the "scatter.txt"
Click to expand...
Click to collapse
1) I don't know which firmware to download.
I guess I'll take the latest TEST_RELEASE_Omate_2100_TrueSmart_20140314, but it is mentionned that it may have a critical security breach? Or should I take the XTCHOU WAVE-Android4.2.2-TecSync-20131216 ? What are the differences and what is your advice please?
But it may be too early to pick one of those since... :
-> I don't have a scatter.txt. The one of my watch is empty (probably because of my factory reset mistake...). Using the adb console shell, "cat /proc/mtd" renders only "dev: size erasesize name"
How should I do?
MtkToolsInformations:
Hardware : MT6572
Model : B101
Build number : ALPS.JB3.MP.V1.8
Build date UTC : 20140108-101154
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Wed Jan 8 18:09:06 CST 2014
Uboot build v : -----
LCD Driver IC : 1-s6d04d2x01
Click to expand...
Click to collapse
I hope I wasn't too long, I got high hopes, you may be the last hope for my watch. Thanks for reading.
Both firmware you are looking at are the wrong ones to be using. ALL 512/4 devices should be using the EU 512/4 working sensors firmware. After that you will want to patch it.
If after flashing the firmware and running the patch it still does not detect any BT devices then you have a bad BT antenna or the connector has come lose.
Lokifish Marz said:
Both firmware you are looking at are the wrong ones to be using. ALL 512/4 devices should be using the EU 512/4 working sensors firmware. After that you will want to patch it.
If after flashing the firmware and running the patch it still does not detect any BT devices then you have a bad BT antenna or the connector has come lose.
Click to expand...
Click to collapse
Thanks, what about the scatter.txt file? Should I still use mine which is nearly empty?
I don't want to brick my watch. Could you provide a scatter.txt file for a AW-414 someone please?
I'll try this evening to flash my watch with my empty scatter.txt then, I hope it will work
What do you think?
(sorry for the double post, I'm a bit stucked)
EU 2100 512/4 working sensors means ALL EU 2100 512/4 no matter what brand name is on it. So all you need to do is download the firmware and flash it.
Lokifish Marz said:
EU 2100 512/4 working sensors means ALL EU 2100 512/4 no matter what brand name is on it. So all you need to do is download the firmware and flash it.
Click to expand...
Click to collapse
I tried to flash it, I didn't succeed. It was stuck at the red bar "Download: 100%". I waited 6 minute, I then canceled the flashing by clicking on the cancel icon. I retried, I got the red bar "Download: 100%", and I now have an error popup which displays: "BROM ERROR : S_FT_DA_NO_RESPONSE (4001)
DA didn't send response data to FlashTool! [hint]:"
So, I can't go on, it stops the flashing.
In order to flash it, I removed the battery, otherwise Flash_Tool.exe wouldn't even consider detecting the watch (when the watch is off), because there was the charging logo instead. Between, I installed the good drivers, followed the tutorial step by step thoroughly, and used the good EU 512-4 2100 20140120 working sensors.zip version.
Do you know what to do please :s ?
Thanks you very much for your help, otherwise I would be lost
Something was missed in the steps or otherwise Flash Tools would have started flashing as soon as you hit the "OK" button to turn off the watch.
The 4001 error is usually associated with loss of data connection between the watch and the PC. That is usually caused by two things. Either the dock has issues or that back is not seated correctly.
Disconnect the dock from the computer
Have Flash Tool ready to flash the watch (select the "Download" button)
Put the battery in watch
Put the watch in the dock
Connect the dock to the PC
Flash Tool should almost immediately start flashing
If this fails, remove the watch from the dock and gently lift the pins in the dock and try again.
Lokifish Marz said:
Something was missed in the steps or otherwise Flash Tools would have started flashing as soon as you hit the "OK" button to turn off the watch.
The 4001 error is usually associated with loss of data connection between the watch and the PC. That is usually caused by two things. Either the dock has issues or that back is not seated correctly.
Disconnect the dock from the computer
Have Flash Tool ready to flash the watch (select the "Download" button)
Put the battery in watch
Put the watch in the dock
Connect the dock to the PC
Flash Tool should almost immediately start flashing
If this fails, remove the watch from the dock and gently lift the pins in the dock and try again.
Click to expand...
Click to collapse
IT WORKS !!!!! :victory: Thanks you so much... !
I had to disable quick boot first, otherwise, it was charging the watch instead of getting the connection with the computer :laugh:
So, I got the new firmware, and new softwares, and miraculuously, there isn't the boot loop anymore, that's fabulous !
Thanks you so much :laugh:!
Glad you got it working. The "disable quickboot" step is required and is often skipped.
Indeed.
I got everything working now... excepting that my Bluetooth range is... less than 2 meters
I can't pass a call with bluetooth, my headphones transmits only bribes of conversation and my correspondent fails to hear me, unless I bring my wrist to my ears
And my Wifi is pretty poor as well, I detect only 3-4 hotspots (and with poor range) out of 20 available to my laptop.
And my wifi detects a hotspot named [NVRAM WARNING: ERR 0x10]; after googling, it seems that it is due to lost IMEI, but that is not the case anymore, I got two brand new IMEI.
Anyways, I don't have any guarantee for this watch, long story, but this is because I bought it using an unknown show resaller.
Do you think that I can try to fix it myself by opening the watch, and see if the antennas are correctly wired ?
Edit: On which side of the strap is there the bt/wifi antenna pls?
Is there also an 1/8 Stock firmware you can flash or should we just use the 512/4?
Cyclone_storm said:
Is there also an 1/8 Stock firmware you can flash or should we just use the 512/4?
Click to expand...
Click to collapse
What do you mean by "1/8" Stock firmware?
shideneyu said:
What do you mean by "1/8" Stock firmware?
Click to expand...
Click to collapse
1GB 8GB edition of the 2100
Do not flash 512/4 2100 on anything but a 512/4 2100. Do not flash 1/8 1900 on anything but a 1/8 1900.
@shideneyu
So on your 512/4 if you are having BT issues it is one of two things. Defective antenna or the BT/WiFi connector is loose or damaged. The BT/WiFi antenna is on the same side as the speaker.
Lokifish Marz said:
[...]
@shideneyu
So on your 512/4 if you are having BT issues it is one of two things. Defective antenna or the BT/WiFi connector is loose or damaged. The BT/WiFi antenna is on the same side as the speaker.
Click to expand...
Click to collapse
Well, I couldn't succeed unscrewing the watch to get a look on the wrist. I don't think I can do anything about it, even if I succeed to unscrew it anyways.
Besides, for an entire day, I got no reboot, nor boot loop. But for the first time, after that I shut down the watch, it now reboot hazardously, for no reason.
I flashed it again, and it worked again for an other day. After that I shut it down again, it began boot looping again
What should I do? Should I use your security patch in order to get it works fluently ?
I also disabled quick boot, but to no avail... I'm gonna flash it again, I hope that I won't have to do that everyday
I still got the issue... Do you have any idea
So after a flash to stock and with no apps installed you are still getting boot loop issues? I think the watch may be going bad.
Lokifish Marz said:
So after a flash to stock and with no apps installed you are still getting boot loop issues? I think the watch may be going bad.
Click to expand...
Click to collapse
Lokifish Marz, oooh, I may now understand, I each time installed random apps from google play store (that I also installed), do you think that that may be why ?
I will reflash tomorrow (as now it is unusable, as it is rebooting and rebooting in loop) and wait three days without any app installed to test if it truely happen because of that.
I don't understand at all, I just flashed it, and less than 5 minutes after the first boot, it suddenly rebooted. Then I got the usual loopboot :crying:
Last but not least, I notice that before rebooting, when I finally succeed to be in the android menu, the FPS dropps, it animation becomes slow (when I try to do anything)
THIS HAS to be a product defect, but how do you explain that in factory mode, it doesn't boot loop??!
Anyways, I am lost. I got a watch that I can do nothing with...
Related
Hello everyone,
first of all, I am new on this Android world, so, any basic question I post, I ask for understanding in advance.
Trying to root my Viewpad 7 (Froyo 2.2), I come across to GingerBreak, I run it and it sucessfully root but it killed my Wifi (that's all connectivity I used, I have no mobile data plan)
as I wanted also to try new rooms, and flash a new one seems to be a only solution for the wifi problem (I have try factory settings without success). I come across Rom manager,
I download and install ROM_Manager_Premium_v4.3.2.3.apk from SD
and download CleanViewpad7_signed_v1.0.zip to my sd card
If I try to flash ClockworkMod Recovery from ROM manager, i get:
"Error while downloading from the server. Please make sure you have a stable internet conection ..." but that's no possible as I have no WIFI in my viewPad7 after root!
If I try to Install ROM from SD card (from Rom manager), the device restore in "Recovery mode" of "Andoid system recovery <3e>"; and it brakes with message "E:signature verification failed".
I have donwload it from several servers (http://forum.xda-developers.com/showthread.php?t=1168562), and all give the same error mesaage
I try to search for manual mode to install clockwork (http://forum.xda-developers.com/showthread.php?t=755379) but I can not find a way to go.
"wipe data/factory reset" inicializate the device, but it doesn't help with the wifi. it keet saying scaning->disconected->scanning->disconected ... (and of course, my wifi conection is set to remember with the password memorized)
In the cofig menu, i can see:
baseband: PR3.7_128
Kernel Apps_2.6.32.9
Build 4027_3_16R
In the FTM mode:
SWver=3.16R
Model:FM6-0001
HWVer:106
what can I do?, I just have a 7inch no apps-no connection beautifull "thing"
More: I have try two other Rooms:
EUViewpadV1.4.zip
Viewpad7 Stock EU 2.2 +rooted+CWM.zip
nothing works, signature verification failed
InTheater said:
Hello everyone,
first of all, I am new on this Android .... Trying to root my Viewpad 7 (Froyo 2.2), I come across to GingerBreak, I run it and it sucessfully root but it killed my Wifi (that's all connectivity I used, I have no mobile data plan)
baseband: PR3.7_128
Kernel Apps_2.6.32.9
Build 4027_3_16R
SWver=3.16R
Model:FM6-0001
HWVer:106
what can I do?, I just have a 7inch no apps-no connection beautifull "thing"
Click to expand...
Click to collapse
Okay, you willl be fine - just need to flash & restore it first to factory/stock ROM first, then root it and go from there - here are the steps that I would suggest:
First, save anything important on your mSD card if you need to, perhaps to a USB drive and/or computer's hard drive.
Next, use this link http://forum.xda-developers.com/showthread.php?t=1260463 to download - for the stock ROMs from Viewsonic.
The newest one is for newer ITE hardware VPAD7 (and, I believe yours is NOT if you could get CleanViewpad v1.0 to boot up & activate the screen - and a number of users are having trouble with wifi ....) To override that signature verification error message that you get, look into CWM (I'm using v3.0.2.8) under Apply update from .zip file on SD card, and there's a "toggle signature verification" switch - change it and trying applying the zip file again to flash - it should work, as I recall. Before that, make sure you wipe system/cache/dalvik & reset data, etc. for a clean(er) new installation.
FM6-316Q-*.nb0 should work with earlier, non-ITE Vpad7 and so should FM6-3310-*.nb0, whereas the FM6-3350-*.nb0 should be for newer ITE devices with either HWver 107 and/or (some) HWver 106.
To flash it, you CANNOT use CWM but must download the SUTL3 (v1.7.9 worked for me) - read & following the onscreen warnings/directions and it should be finished in less than 10 minutes (have the Vpad7 fully charged first & do NOT need to have the mSD card installed)
When it's finished, reinstall the mSD card, take a deep breath & reboot/restart, and you should be up & running with the stock ROM in a few minutes - if so, check your wifi connectivity first before going any further. Start with 316Q ROM first and if it's good, you might want to move up to 3310 next (it's newer) & recheck wifi connectivity. STOP then, as yours is non-ITE and the 3350 will NOT work. You can then flash CWM and/or root it - with SOC or GB methods, etc. etc. which you're familiar with.
I had no problems with wifi connectivity and/or 3G data (prepaid GSM 3G coverage) running the Froyo Enhanced custom ROM (non-OC version since I have ITE hardware) OS 2.2 - However, I'm running stock ROM OS 2.2.2 rooted and wifi is perfect for me. (I'm written up a quck tip/guide also - in case you didn't come across it while searching for answers) http://forum.xda-developers.com/showthread.php?t=1264647
Lastly, TJ_Style's FM6 ROM w overclocked kernel should work for you as well, it's OS 2.2 but I patched the boot.img with my saved newer 2.2.2 ITE kernel and got it working too, and, no issues with wifi access at all.
In short, check & change your Signature Verification options under CWM and try again, and, if not - restore by reflashing with SUTL3 a factory *.nb0 file, then - proceed from there.
Good luck, have a bit of patience - it's both fun & exciting, challenging & disappointment often followed by the joy of luck & success. Let us know how it go & write down any error message(s) so we can help figure it out together - plenty of "newbies" been around but still stranded at times.
Regards -
Thanks, SUTL3_v1.7.9 and FM6-3310-0-5029-A02.nb0 works like a charm, easy and bring back my ViewPad7 to work,
for anybodies info, that change my ViewPad to:
Android version : 2.2.2 (from 2.2)
Baseband version PR3.7_128 (same)
Kernel Version Apps_2.6.32.9 (same)
Build Number 5029_3_310 (from 4027_3_16R)
I got encouraged, and I try FM6-3350-0-1008-A01.nb0, that gives me:
Android version : 2.2.2 (from 2.2)
Baseband version PR3.7_128 (same)
Kernel Version Apps_2.6.32.9 (same)
Build Number 1008_3_350 (from 4027_3_16R)
Swype included !! (seems a little odd and disordered the configuration process, so skip it)
what means ITI / non-ITI ?
languajes: both nb0 are English/Spanish/French only
now I will start with rooting and so, I will let you know
once more, many thanks.
Wonderful, we are all glad to know that you had success. Is your wifi working once again with either stock unrooted ROM?
Once rooted & CWM reinstalled, do a backup first to save those *.img files, etc. so that you can easily restore/go back later on if necessary.
As I said, check out Enhanced Froyo and TJ_Style's FM6 custom ROMs, both of them should work nicely for you - including wifi (I believe, as least on mine - both solid signals in both G and N routers, WEP & WPA-2 modes. (Also, try open or unsecured mode)
Happy flashing ....
YES !!, wifi is working back to normal. At least sometimes (I have need to re-flash few time already, it has stoped working few times more, and not becouse of rooting, just installing apps from market)
I have also encoutered the next problem : http://www.youtube.com/watch?v=6XuccAxXY_8
and that shouldn't be normal behaviour?, isn't it ?
try with diferent room or return to viewsonic ?
by the way, what ITE means ?
thanks once more
InTheater said:
YES !!, wifi is working back to normal.
I have also encoutered the next problem : http://www.youtube.com/watch?v=6XuccAxXY_8
and that shouldn't be normal behaviour?, isn't it ?
try with diferent room or return to viewsonic ?
by the way, what ITE means ?
Click to expand...
Click to collapse
ITE refers to Panjit Touchscreen (Multi-Touch Resistive) used on newer Vpad7 built & shippped vs. older hardwares used on earlier models.
On that subject, I've looked at a # of youtube video reviews & posting about the device's orientation/rotation issues, and it seemed to me that it prefer to be in a landscape mode. But, there are times where we wanted to have a choice, turn it 90 degree for a vertical or straight up - not so sure it's 99% hardware problem - rather, problem caused by a mix of Android codes & Apps used. Some were defective but that's a production & quality control issue, so, anyway.
I'm not sure after seeing at your YT video what the problem is, please describe & I will have another look with my thoughts on it.
Does it happen with the stock/factory ROM or only with the ROM being runned now - I would flash a different ROM to compare the results.
Sending it back to Viewsonic is an option but you will be without its use for 2 to 4 weeks (usual timeframe, could be longer) & deal with packing, insuring, shipping & waiting - but, if it's "bad" - get authorization & exchange it or repaired.
Regards !
Bad news, as later day, wifi come alive, it went down sometimes, and as I was trying application I flash the three diferent factory rooms few times. What I didn't notice is that the wifo was disconecting more and more often: now it does connect at all.
As said, I have try the three diferent ROM in viewsonic, and also an app called FixMyWifi, nothing helps, wife is all the time "Connecting..."->"Disconected"->"Searching"->and so on
about the strange behiviour of the screen, the matter is that as soon as using two fingers, the right one, can not be in lower position than the left one. So forgot about plenty of games, drawinf with two fingers, dificulto for rotating maps (when the rotation of finger goes beyond 90 degres)
And one of the reasons I bought it is my little boy, explain that to a children of four years..., in deed he found it as "that does work well, the tank does not follow my fingers"
so, as a multitouch is basically pointless if you have to care your right finger does not go bellow your left one ...
Anything to do with the Wifi ?
rooting may help in some way?, and some terminal comands?
I am willing to try, I am just in the point before return it as faulty device.
Many thanks for all the help given.
InTheater said:
What I didn't notice is that the wifo was disconecting more and more often: now it does connect at all .... try the three diferent ROM in viewsonic, and also an app called FixMyWifi, nothing helps and so on .... as a multitouch is basically pointless if you have to care your right finger does not go bellow your left one ...
Anything to do with the Wifi ? I am just in the point before return it as faulty device.
Click to expand...
Click to collapse
Thanks for clarifying and I looked at the YT video again - perhaps you would be better off getting Viewsonic for authorization to return for repair or exchange it. On my device, the screen is responsive 98% of the time but I do realize that sometimes, when we're playing Angry Birds, that it too doesn't always readily respond to commands or launch the bird shots .... Not a big deal for games, it will usually get going again - worst case, use the Go Back key & restart the level - I figure that it could be a combination of the Froyo or Android codes written for the OS and/or along with the Angry Birds gaming itself.
Afterall, my "regular" & 2 years old smartphone, HTC Eris running a nearly identical CPU & configuration is running custom rooted GingerBread ROM - and, is must better & responsive in overclocked mode. The Vpad7 will not, I feel, be running Honeycomb but let's hope that some of the veteran xda developers will soon release a working GingerBread ROM - perhaps it will fix many of the issues across the field, so to speak. (or, if Viewsonic will release it as official update .... wishful thinking, huh - but !)
On the wifi issues, have you tried doing the SuperOneClick and/or GingerBreak apk to root, and then flash TJ_Style's custom FM6 ROM - http://forum.xda-developers.com/showthread.php?t=1264647 - this OC version with WiFi fix might work for you without any mods (patching or zip flashing the 2.2.2 boot.img)
On wifi configuration itself, is this happening with different routers - "older" G mode or newer N (faster) routers, unsecured or open network or secured (WEP, WPA or WPA2, etc.) - any issues on the host computer/router's firewall blocking ? Can you log in at a public hotspot or cafe like Starbuck ?
Go into Settings > Wireless & network settings > Wi-Fi settings > and, then, tap the Home key (the bottom of 4 keys on the device - held in landscape mode) and you should see "Scan" & "Advanced" - does it pickup a decent signal ? Click "Advanced" & look at your "Wi-Fi sleep policy" - mine is checked for "When screen turn off" - tried "Never" or "Never when plugged in" - any difference ? If you get this far, you might want to try to set up & Use "static IP" instead of using dynamic ip addressing that these devices usually count on .... it's a bit of work, but might help to "zoom" into your own router only.
I use "Wifi Analyzer" v2.5.13 from Kevin Yuan (Google Market) to help scan the spectrum for signals and possible interference, which sometimes do happen - and moved 1 of our 2 cable broadband router to a different channel so that all of our wireless (up to 15 of them, yes) devices around the house can easily connect to the hotspots. (Reading posts @ other forum sites & ran my inSSIDer v2.0 from Dell laptop for baseline, it scanned 17 active APN's with varying signal strengths, our Sony W995 picked up only 6 signals with 3 good ones, the HTC Eris picked up 6 signals also with 3 good ones, and the Vpad7 only 3 signals, 2 of them from our own indoor G & N routers plus 1 from neighbors that's marginal. It's safe to assume that our device's internal radio receiver or Baseband isn't very good with reception to begin with - you might need to flash a different "build" like mine to give it a try - and try switching your wifi channel.)
Just some of my thoughts on the wifi problem as I do run into signal problems myself every so often installing a new device or configure a guest's new gadget at home. If all else failed and along with the touchscreen problem, then I would say get it fixed via repair or exchange from Viewsonic, and then .... (a few weeks later, upon its return to you - happy rooting & flashing, etc.)
Letitride said:
Thanks for clarifying and I looked at the YT video again - perhaps you would be better off getting Viewsonic for authorization to return for repair or exchange it. On my device, the screen is responsive 98% of the time but I do realize that sometimes, when we're playing Angry Birds, that it too doesn't always readily respond to commands or launch the bird shots .... Not a big deal for games, it will usually get going again - worst case, use the Go Back key & restart the level - I figure that it could be a combination of the Froyo or Android codes written for the OS and/or along with the Angry Birds gaming itself.
Click to expand...
Click to collapse
Thanks a lot, that I have done, and ask ViewSonic for replacement, I hope they return me one fully working (by the way, sorry for so late response, I have been for 2 weeks out)
Letitride said:
Afterall, my "regular" & 2 years old smartphone, HTC Eris running a nearly identical CPU & configuration is running custom rooted GingerBread ROM - and, is must better & responsive in overclocked mode. The Vpad7 will not, I feel, be running Honeycomb but let's hope that some of the veteran xda developers will soon release a working GingerBread ROM - perhaps it will fix many of the issues across the field, so to speak. (or, if Viewsonic will release it as official update .... wishful thinking, huh - but !)
Click to expand...
Click to collapse
yes, it seems that the viewsonc doen't have so good hardware after all ...
Letitride said:
On the wifi issues, have you tried doing the SuperOneClick and/or GingerBreak apk to root, and then flash TJ_Style's custom FM6 ROM - http://forum.xda-developers.com/showthread.php?t=1264647 - this OC version with WiFi fix might work for you without any mods (patching or zip flashing the 2.2.2 boot.img)
On wifi configuration itself, is this happening with different routers - "older" G mode or newer N (faster) routers, unsecured or open network or secured (WEP, WPA or WPA2, etc.) - any issues on the host computer/router's firewall blocking ? Can you log in at a public hotspot or cafe like Starbuck ?
Go into Settings > Wireless & network settings > Wi-Fi settings > and, then, tap the Home key (the bottom of 4 keys on the device - held in landscape mode) and you should see "Scan" & "Advanced" - does it pickup a decent signal ? Click "Advanced" & look at your "Wi-Fi sleep policy" - mine is checked for "When screen turn off" - tried "Never" or "Never when plugged in" - any difference ? If you get this far, you might want to try to set up & Use "static IP" instead of using dynamic ip addressing that these devices usually count on .... it's a bit of work, but might help to "zoom" into your own router only.
Click to expand...
Click to collapse
about the wifi issue, I have try all the steps you mention before, nothing helps with my router (deliver by the telephone company). The only thing that works, sometimes, s turning off the router for several seconds, then it connect again. As absurd it sounds, it looks like the viewpad doesn't disconnect from the router even as turned off, so the router doesn't allow to negociated again a conection (and it keeps it in connected device while the viewpad is reseting or turned off)
I have try connecting a Linksys Wi-fi and connecting trought it : WORKS GREAT.
Trying in different locations, some of them same problem as the router, others works perfectly.
Solved for home with second wifi-point, I see myself one day asking Starbuchs guy to reset their router...
Letitride said:
I use "Wifi Analyzer" v2.5.13 from Kevin Yuan (Google Market) to help scan the spectrum for signals and possible interference, which sometimes do happen - and moved 1 of our 2 cable broadband router to a different channel so that all of our wireless (up to 15 of them, yes) devices around the house can easily connect to the hotspots. (Reading posts @ other forum sites & ran my inSSIDer v2.0 from Dell laptop for baseline, it scanned 17 active APN's with varying signal strengths, our Sony W995 picked up only 6 signals with 3 good ones, the HTC Eris picked up 6 signals also with 3 good ones, and the Vpad7 only 3 signals, 2 of them from our own indoor G & N routers plus 1 from neighbors that's marginal. It's safe to assume that our device's internal radio receiver or Baseband isn't very good with reception to begin with - you might need to flash a different "build" like mine to give it a try - and try switching your wifi channel.)
Just some of my thoughts on the wifi problem as I do run into signal problems myself every so often installing a new device or configure a guest's new gadget at home. If all else failed and along with the touchscreen problem, then I would say get it fixed via repair or exchange from Viewsonic, and then .... (a few weeks later, upon its return to you - happy rooting & flashing, etc.)
Click to expand...
Click to collapse
so, waiting for Viewsonic to replace my viewpad, I will inform as I have a new one in hands.
thanks a lot !!
can someone plz help me i am trying to flash this viewpad7
i get this error
error code:0x4000
error:task 2 of 3,download image fail,
error:device_not_configure (0x4000)
can you plz help me
thanks
To see this address
http://forum.xda-developers.com/showthread.php?t=1433052
Good luck
Hussein
I am writing in desperation.
My Xperia Active is about 3 months old.
It is the ST17a version but that has never made much difference to anything else.
It has been unlocked via testpoint method so warranty is not valid (plus they don't sell this phone in my country anyway).
Phone randomly reboots when it is not plugged in to power, especially when trying to bring the phone out of lockscreen standby, after using any GPS function or just unlocking the phone
The fact that this WILL NOT happen when plugged in to power is telling me perhaps it is a power management issue.
Things I have tried so far: COMPLETE REFLASH formatting all available mounts from recovery mode + format SD card and start fresh.
Combinations:
1.Spartan Rom 1.9.5 + non-oc kernel
2. Spartan Rom + Rage Kernel
3. Different baseband versions including original (56??), .66 and .62 (currently have .62 installed)
4. EX MIUI + ST17 satsuma kernel
Reboots still happen with all of the above configs
The problem started suddenly whilst using GPS SportyPal pro + Bluetooth music I have previously not had any problems in this area but now they will not stop.
I did not experience any reboots with CM9 but I did not stay in that rom very long as there was way too much stuff not working on my handset - it probably would have happened eventually. Sometimes I can get over half a day of usage without a reboot but then will get like 5 in a row.
I absolutely LOVE this phone but I bought it primarily for sports tracking and it keeps crashing and losing my workouts so I'm getting pretty pissed off.
If anybody can tell me what to look at to try and track this down I would really appreciate it. Checking logcats are no good because it will never reboot whilst plugged in to USB. Are there any other logs I should check???
OK - if not any help to identify the cause - can anyone comment on repair cost @ sony service center out of warranty?
Try fully stock 4.0.2.A.0.62 firmware, some other phones had issues with restarting all the time also, this firmware is known to fix this.
SOLVED - have carried out 5 days of testing.
I can confirm the latest version of MIUIex has addressed my reboot woes.
Have been running reboot logger 1.9 on the phone since then and have not had a single unexpected reboot. I am a happy camper.
Not sure if perhaps there is/ was a common driver or something that was causing these problems between a few of the up to date roms - I am just happy the issue seems to have passed for now.
And it's back. I switched back to Telstra, that means back to 850mhz band, reboots are back with vengeance. Might need to try and find a st17a specific Rom and radio.
bandario said:
And it's back. I switched back to Telstra, that means back to 850mhz band, reboots are back with vengeance. Might need to try and find a st17a specific Rom and radio.
Click to expand...
Click to collapse
Flash this via Flashtools: http://www.mediafire.com/?yvjnt0qctun9t6j
Is ST17a Specific ICS Firwmare. It contains ST17a specific baseband(radio).
Hope it helps
pastillero said:
Flash this via Flashtools: http://www.mediafire.com/?yvjnt0qctun9t6j
Is ST17a Specific ICS Firwmare. It contains ST17a specific baseband(radio).
Hope it helps
Click to expand...
Click to collapse
Wow, thanks!
Seems to have done the trick but now is back to vanilla flavour - seems the rooting process has gotten ridiculous lately, I wonder if it would be easier to pull this ftf to pieces and insert the radio detials etc into another rom file.
For now I guess I will use stock phone unrooted, at least it won't reboot.
THanks for your help!
i have also had that problem. I flashed the sti7a ics version and it is gone, after that you can use any rom without any prob.
bandario said:
Wow, thanks!
Seems to have done the trick but now is back to vanilla flavour - seems the rooting process has gotten ridiculous lately, I wonder if it would be easier to pull this ftf to pieces and insert the radio detials etc into another rom file.
For now I guess I will use stock phone unrooted, at least it won't reboot.
THanks for your help!
Click to expand...
Click to collapse
No prob..
You can flash any custom ROM you want, if it start rebooting again then get back to Stock..
Cheers
I had the same problem, it used to happen when signal was scarce or absent, i solved by getting a new sim card
Guys maybe you can help me, my phone is behaving very strange. It is a Tianhe H920+ with 4gb ROM, identical with Mlais MX58 Pro, Auxus Nuclea N1 and others.
Roms for Auxus Nuclea N1 are working perfectly, but, first of all i have problems with the rear camera, i am not getting any error messages, but just only the front camera is working and the switch camera option is missing, after i install some third party camera app it freezes.
Phone was suited with Tianhe ROM, build march 2014, for sure i made backup. What i have found out, when i flash the original BOOT.IMG, camera works fine, but the old kernel will be installed. I have unpacked it, checked also init, init.project files, they are totally the same, no change there, just the Zimage differs / Kernel.
All works fine but i have the old known wake up bug, i must remove the battery and start the phone again. I was searching everywhere, but i couldnt find any fix for it. I know flash firmware, but like i already mentioned rear camera is not working with other kernels, all other functions are ok. Is there any possible solution? Framework fix or something please?
Till now i have tried almost 10-15 roms, from MX58 Pro, Star, Tianhe, but non of them is suited with a kernel with working rear camera :crying:. Thank you very much.
Heyy delltech1.. I've also facing similar issue...have you found any solution to your problem?
Tianhe H920+ Wake up issue
delltech1 said:
All works fine but i have the old known wake up bug, i must remove the battery and start the phone again. I was searching everywhere, but i couldnt find any fix for it. I know flash firmware
Click to expand...
Click to collapse
Hello DellTech1.
I am facing the same issue with the pnone not waking up after it has gone to deep sleep.
I found out, that it only happens, when WLAN (WIFI) is switched on.
(For tests I had no SIM installed and the phone was reset to factory setup)
When WIFI is switched off it starts up as it should.
Could this issue be related to baseband?
Do you have more informations now?
Additional infos:
It showed, that the wakeup issue occured, when the phone was logged into a Network with WPA2 security.
Because I did not believe this, I did trials on 3 different networks with 3 different routers.
In each case, the phone did not wake up, if WLAN was active and the security settings in the router have been WAP2.
If I changed the settings in the routers to WPA, wake up was fine.
Anyway: an active WLAN connection (either WPA2 or WPA) does not allow the phone to go into Deep Sleep.
(according to CPU SPY at WPA, and my fingers touching the warm back of the phone with WPA2)
Tianhe
Eleichstetten said:
Hello DellTech1.
I am facing the same issue with the pnone not waking up after it has gone to deep sleep.
I found out, that it only happens, when WLAN (WIFI) is switched on.
(For tests I had no SIM installed and the phone was reset to factory setup)
When WIFI is switched off it starts up as it should.
Could this issue be related to baseband?
Do you have more informations now?
Additional infos:
It showed, that the wakeup issue occured, when the phone was logged into a Network with WPA2 security.
Because I did not believe this, I did trials on 3 different networks with 3 different routers.
In each case, the phone did not wake up, if WLAN was active and the security settings in the router have been WAP2.
If I changed the settings in the routers to WPA, wake up was fine.
Anyway: an active WLAN connection (either WPA2 or WPA) does not allow the phone to go into Deep Sleep.
(according to CPU SPY at WPA, and my fingers touching the warm back of the phone with WPA2)
Click to expand...
Click to collapse
Hi,
i have flashed the "new rom" from pandawillforum. But be carefull, after flashing i wasnt able to start the phone, it softbricked the phone, but i was able to unbrick it. Before you will flash it, take the PRELOADER file from a good known working rom and replace it. Then try to flash it, it will work now.
I have used the phone without the simcard, Wifi was enabled, Gmail synchronization also, i have used the phone for about 5 days, wakeup issue didnt reappeared. Camera is working also. Just search in the forum for H920 and you will find many topics, but i can also post the link here:
4GB version:
http://androidxda.com/flash-stock-rom-using-smart-phone-flash-tool
8GB version:
http://www.pandawillforum.com/soft/12J36_S131WT_H920+_8P64_20140329_JB2V1.2.V02.MP.EN.rar
Like i said, use a good working preloader, you can take it also from an older ROM, doesnt matter.
delltech1 said:
Before you will flash it, take the PRELOADER file from a good known working rom and replace it.
Click to expand...
Click to collapse
Could you recommend a good preloader?
Tianhe
Eleichstetten said:
Could you recommend a good preloader?
Click to expand...
Click to collapse
Yes you can use one from this ROM, i was using it everytime:
http://www.needrom.com/mobile/tianhe-star-h920-2/
Camera still not working
delltech1 said:
Yes you can use one from this ROM, i was using it everytime:
http://www.needrom.com/mobile/tianhe-star-h920-2/
Click to expand...
Click to collapse
I have tryed all roms from needrom and pandavile..nothing.
Now I tried the ROM that was offered in the Pandawill Forum for 8GB Version.
This ROM does include a working preloader (maybe has been changed?)
Anyway, when I flash this ROM, it works, but problems persist.
No change.
CWM 8gb ver. ROM
HI guys, Please could some one upload the 8GB rom flashable with CWM recovery I can not do it with flashtools my usb conenctor is damaged...
PLEASE HELP and save my ass I am starting to be despaired with this phone
THANK YOU for any support and have a nice day
Modified version of Note 3 yasuu ROM.
Just for the case that someone do not know how to replace boot.img (kernel 2014) and replace camera drivers I am uploading modified version of Note 3 yasuu ROM.
No flickering screen,No back camera bug or green camera,No unlock freez yet.
Only bad thing is battery usage, maybe because my USB connector is damaged.I do not know try it out and share your results about the baterry please.
LINK (CWM zip file) :
mediafire.com/download/v3n65fltmwka52z/ROM_NOTE3_Kernel_2014_H920+.+Cam.Drivers.HanyxX.zip
Gave it a try.
Installation did work, but I missed keyboard.
Did install keyboard from APK.
Then tried to root. Framaroot said "ok", but Superuser did not work.
Tried to install Superuser by CWM method, but that ended in a startup-loop.
Had to Flash back Stock-ROM to recover.
Maybe try tomorrow again.
OK, Gave it a second try. This time without trying to root.
Well, the wake up issue does not exist anymore.
Unfortunately, it´s just because the phone does not start to Deep Sleep anymore.
It reduces processor rate, but does not start Deep Sleep.
That´s the cause for higher battery consumption.
By the way:
- The package of my phone is not labeled "Tianhe", but "CGC".
- Both cameras did work with this Rom.
- My phone has 8GB of memory and stock ROM is 03/2014
Hello
Eleichstetten said:
Gave it a try.
Installation did work, but I missed keyboard.
Did install keyboard from APK.
Then tried to root. Framaroot said "ok", but Superuser did not work.
Tried to install Superuser by CWM method, but that ended in a startup-loop.
Had to Flash back Stock-ROM to recover.
Maybe try tomorrow again.
Click to expand...
Click to collapse
I have tried your rom but camera still not working for me...i have 8GB version.
---------- Post added at 01:03 PM ---------- Previous post was at 12:59 PM ----------
Hello,
I have tried the last modified version of this rom but the camera is not working for me..not frontal one,not the back one..i have tried all roms from needrom(tianhe,mlais or star...)..no one is proper to have working camera...any advice
I did reset my phone with this firmware from Pandawill Forum (8GB version). The firmware is for H920+ that are produced after March 2014.
It seems, that there has been a change of camera hardware.
http://www.pandawillforum.com/showthread.php?25569-ROM-ROM-for-Tianhe-H920&p=136188&viewfull=1#post136188
This seems to be real stock.
If your phone is produced after March, 2014 and this firmware does not solve the problem, there is a high probability that it is defective.
How to find out?
How can i find out what is the date manufacture of my phone?
about Tianhe H920+ turbo /pandawill/, rear camera problems
validoican said:
I have tried your rom but camera still not working for me...i have 8GB version.
---------- Post added at 01:03 PM ---------- Previous post was at 12:59 PM ----------
Hello,
I have tried the last modified version of this rom but the camera is not working for me..not frontal one,not the back one..i have tried all roms from needrom(tianhe,mlais or star...)..no one is proper to have working camera...any advice
Click to expand...
Click to collapse
Hello,
After trying all firmwares from panda and needrom i find that there is a hardware problem. BAD CONNECTION between board and camera conector!
Try to open the phone and press firmly camera connector to the board. Then put above something thick 1 mm (non metal) to hold the connector in same position.
It's worked fine for me. Good luck to you!:good:
delltech1 said:
Hi,
i have flashed the "new rom" from pandawillforum. But be carefull, after flashing i wasnt able to start the phone, it softbricked the phone, but i was able to unbrick it. Before you will flash it, take the PRELOADER file from a good known working rom and replace it. Then try to flash it, it will work now.
I have used the phone without the simcard, Wifi was enabled, Gmail synchronization also, i have used the phone for about 5 days, wakeup issue didnt reappeared. Camera is working also. Just search in the forum for H920 and you will find many topics, but i can also post the link here:
4GB version:
http://androidxda.com/flash-stock-rom-using-smart-phone-flash-tool
8GB version:
http://www.pandawillforum.com/soft/12J36_S131WT_H920+_8P64_20140329_JB2V1.2.V02.MP.EN.rar
Like i said, use a good working preloader, you can take it also from an older ROM, doesnt matter.
Click to expand...
Click to collapse
How do you unbrick your phone... ??? Please advise !!!
Dear Experts,
Months ago my 2y old XZU on 4.4.4 (6833, towel rooted, locked, CWM recovery) started to fail on init of LCD, when coming out of standby. LCD init not only fails when device gets waked up by "power" button, but also when power is applied (Dock connector or USB). So I guess in fact it is a firmware issue (not a defective power button or the like).
It gets worse and worse; when device is warm it sometimes needs 30 or more off/on cycles.
When LCD init fails, the screen either stays black (only backlight) or colored lines show up shortly and fade away. But in fact the device is running - only LCD is not working.
But when init is successful, the XZU can run nicely for hours (as navi).
I hope that a android FW update might help!?
Unfortunately OTA doesn't seem to work on routed devices even with still locked boot loader.
Is there a way to update directly to 5.1.1 available now? Is it possible to update in two steps?
I would not mind to loose root, but loosing the possibility to write to external SDCARD!
Any help/ideas? THANKS A LOT!
Thomas
Sounds like SOD, or Sleep Of Death. The Ultra had some issues with it back on Jelly Bean, but I hardly read about it being an issue on KitKat, but yeah, it's probably a software issue, so an update to 5.1.1 might just cure it. You have a couple of options here:
1. Update the official way by installing Sony's PC Companion app on your computer and updating it that way
2. Update it in a little less official way by updating it manually yourself with Flashtool on your computer
3. Update by flashing a customized version through a recovery system on your device (like CWM or TWRP)
I would personally update it through PC Companion if I were you, since I guess you're not that technical when it comes to flashing and troubleshooting things. PC Companion should notify you about the update as soon as you plug your Ultra to your computer. If it notifies you about the 5.0.2 update, then I guess you'll have to update to 5.0.2 first, and then you'll be able to update to 5.1.
Flashtool allows you to manually download a FTF, or the ROM file from XDA and then flash it yourself. It's a lot quicker than PC Companion, but also a lot more complicated for people who haven't used it before.
Flashing through a recovery is mainly for people who already are used to flashing and stuff like that, and know what they're (mostly) doing.
Any other questions?
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
zamzon said:
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
Click to expand...
Click to collapse
The OTA will only tell you to connect to the computer to update. And regarding SD-card, that won't be an issue. Android will ask you to grant permission to the SD-card in some cases, but I haven't had any issues with it. Most if not all file explorers works just fine, and you won't experience any issues with the SD-card.
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
zamzon said:
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
Click to expand...
Click to collapse
But that does sound like a hardware issue. The final thing you can do, before you'll have to send it in for repairs, or get a new device, is to do a full factory resetting and see if that finally helps. You just updated now, but there's still a lot of crap left over from the previous version, that might screw things up.
So my advice would be to do a wipe, check if it help, and if not either send it in for repairs or get a new device. It's not a software issue if the issue travels over several OS versions with you. It may be a faulty display connector.
I've installed the official Nougat update from Elephone using the SP flash tool. Before the update, everything on the phone was working.
After the update, the phone boots Android 7 fine, but no SIM cards are recognised.
I've tried entering Engineer Mode through the phone app to reset the IMEI (I know what they are) but the 'Connectivity' page in Engineer Mode doesn't list phone radios, only FM, Bluetooth, NFC and WiFi.
So I rooted the phone and tried entering AT commands through a terminal. But the folder /dev/radios is empty.
It's like my phone has no... well, no phone. I guess the driver is broken somehow.
Does anyone have any tips on how to proceed?
tom.k.cook said:
I've installed the official Nougat update from Elephone using the SP flash tool. Before the update, everything on the phone was working.
After the update, the phone boots Android 7 fine, but no SIM cards are recognised.
I've tried entering Engineer Mode through the phone app to reset the IMEI (I know what they are) but the 'Connectivity' page in Engineer Mode doesn't list phone radios, only FM, Bluetooth, NFC and WiFi.
So I rooted the phone and tried entering AT commands through a terminal. But the folder /dev/radios is empty.
It's like my phone has no... well, no phone. I guess the driver is broken somehow.
Does anyone have any tips on how to proceed?
Click to expand...
Click to collapse
Use maui meta 3g to restore IMEI. It is mentioned several times in these forums.
Hexyl said:
Use maui meta 3g to restore IMEI. It is mentioned several times in these forums.
Click to expand...
Click to collapse
Well, there's one who didn't read the question. This is not about restoring the IMEIs.
Alright. I know flashing nougat might break the radios and also IMEI. This includes not detecting simcards. I had this problem myself.....
I have the same problem, or similar .
I can sometimes send and recieve text messages and sometimes i can call. Data traffic seems to work ok.
Right now as soon as i try to make a call i lose connection to the mobile network.
Theres a simple fix, reflash 6.0, then do format all + download android 7, imei wont be restored, but both sims will be recognized and work normally
Ruben Craveiro said:
Theres a simple fix, reflash 6.0, then do format all + download android 7, imei wont be restored, but both sims will be recognized and work normally
Click to expand...
Click to collapse
I did this and got the sim working with data and SMS but I can't call.
Should I try again? I want to restore my imei from my box too.
Flashtool and stock roms?
How did you do Tom? Did you fix it?
Thenbay said:
I did this and got the sim working with data and SMS but I can't call.
Should I try again? I want to restore my imei from my box too.
Flashtool and stock roms?
How did you do Tom? Did you fix it?
Click to expand...
Click to collapse
are you using the usa model? its known to have issues on latest versions due to incompatibility issues with radio files
Ruben Craveiro said:
are you using the usa model? its known to have issues on latest versions due to incompatibility issues with radio files
Click to expand...
Click to collapse
No, i think i have the European version. The problem remains if I flash back to 6.0.
Thenbay said:
No, i think i have the European version. The problem remains if I flash back to 6.0.
Click to expand...
Click to collapse
then its priblably usa version.. since this has never happend to me
tom.k.cook said:
I've installed the official Nougat update from Elephone using the SP flash tool. Before the update, everything on the phone was working.
After the update, the phone boots Android 7 fine, but no SIM cards are recognised.
I've tried entering Engineer Mode through the phone app to reset the IMEI (I know what they are) but the 'Connectivity' page in Engineer Mode doesn't list phone radios, only FM, Bluetooth, NFC and WiFi.
So I rooted the phone and tried entering AT commands through a terminal. But the folder /dev/radios is empty.
It's like my phone has no... well, no phone. I guess the driver is broken somehow.
Does anyone have any tips on how to proceed?
Click to expand...
Click to collapse
Did you get your phone working again??
I have not been able to geet mine working again.
this phone has soo many problems,, why the hell they sale it like that, mine had no emie once updated to 7.0 and it has never had a speaker working. i'm dealing with warranty and this guys dont want to take responssability for their product. very frustrating !!! any how i got one of the sim cards working the second slot, also got the emie showing now but still no audio from speaker, what i did.... i flashed the android 7.0 i selected format+download and everything works just the speaker does not
DiMatador said:
this phone has soo many problems,, why the hell they sale it like that, mine had no emie once updated to 7.0 and it has never had a speaker working. i'm dealing with warranty and this guys dont want to take responssability for their product. very frustrating !!! any how i got one of the sim cards working the second slot, also got the emie showing now but still no audio from speaker, what i did.... i flashed the android 7.0 i selected format+download and everything works just the speaker does not
Click to expand...
Click to collapse
that seems like a hardware issue, i think theres a few cheap speakers and you could try to fix urself on ali express theres speaker at around 10$ it ahould be farelly easy to replace it
I've had this same problem, but only after replacing my screen due to damage. Ever since then, it'll see the sim but wont connect to my network.