Got my tablet 2 weeks ago.
I went from stock ROM->Vegan 5.1.1 (2 weeks ago)->Vegan Ginger edition 7.0.0 (yesterday)
so far so good.
However, when i tried to update to the latest kernel (see below)
"ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip
Download: boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip"
I get "wifi error" upon startup. Wifi is not recognized, nor can i add my wifi manually.
Tried going back and forth between base ROM/kernel from this forum "VEGAn-TAB GingerEdition STABLE RC1" and the latest kernel (with the usual clear data/cache/davlik cache post-install). Base kernel has wifi no probs, but any later kernel and i get wifi errors
Tried to cycle airport mode, but nothing happens - just goes into disabling wifi networks and stays grayed out
Also tried to clear cache "before" flashing kernel, as suggested by member TEK112 in the same thread. Any help will be appreciated. thanks!
xda-novice said:
Got my tablet 2 weeks ago.
I went from stock ROM->Vegan 5.1.1 (2 weeks ago)->Vegan Ginger edition 7.0.0 (yesterday)
so far so good.
However, when i tried to update to the latest kernel (see below)
"ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip
Download: boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip"
I get "wifi error" upon startup. Wifi is not recognized, nor can i add my wifi manually.
Tried going back and forth between base ROM/kernel from this forum "VEGAn-TAB GingerEdition STABLE RC1" and the latest kernel (with the usual clear data/cache/davlik cache post-install). Base kernel has wifi no probs, but any later kernel and i get wifi errors
Tried to cycle airport mode, but nothing happens - just goes into disabling wifi networks and stays grayed out
Also tried to clear cache "before" flashing kernel, as suggested by member TEK112 in the same thread. Any help will be appreciated. thanks!
Click to expand...
Click to collapse
Usually wifi not working means you flashed the wrong kernel, but it sure looks like you got the right (gb) one. You sure you're on gingerbread?
schettj said:
Usually wifi not working means you flashed the wrong kernel, but it sure looks like you got the right (gb) one. You sure you're on gingerbread?
Click to expand...
Click to collapse
hmm...wonder what's wrong then ?
I'm positive about Ginger edition though - Followed instructions from this forum - "http://forum.xda-developers.com/showthread.php?t=1031250"
Downloaded and installed "VEGAn-GE-7.0.0-RC1-Harmony-signed.zip" from http://vegantab.gojimi.com/downloads/
Home screen confirms Vegan-Tab GingerEdition - do not have the tablet with me at the moment, but can post "About Tablet" info later.
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
terrypchan said:
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
Click to expand...
Click to collapse
Thanks terrypchan...never played around with adb before, and couldn't get it to work last night, but will definitely give it a shot and post my results.
However, in previous version, when I had Vegan 5.1.1, and upgraded the kernel, i didn't have to go through the adb push of bcm4329.ko install. Even with the upgrade kernel for gingerbread7.0 (the noted issue here), there is base bcm4329.ko driver is already sitting under /system/lib/hw/wlan folder, so the adb push of this module under lib/modules will override the base ?
terrypchan said:
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
Click to expand...
Click to collapse
I've never needed to do that.
I'm wondering if he's stuck in airplane mode now that I've re-read his first post.
This is from the old version, but suggests that getting a widget that can toggle flight mode may fix it:
http://forum.xda-developers.com/showthread.php?t=951822&page=59
FYI - no need to use flight mode on a tablet, just turn off all the radios.
terrypchan said:
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
Click to expand...
Click to collapse
Can you tell me how to do that??
I am having exct same issue on Samsung Wave..
Related
It seems I cant start Wifi on my mobilephone Evo 3D GSM
I followed 2 Tutorial, one to boot an boot.img and other to flash with some file bcm4329.
Non of it suceed.
After installing completly new rom, it happens again. LeeDroid
sniperkiki said:
It seems I cant start Wifi on my mobilephone Evo 3D GSM
I followed 2 Tutorial, one to boot an boot.img and other to flash with some file bcm4329.
Non of it suceed.
After installing completly new rom, it happens again. LeeDroid
Click to expand...
Click to collapse
The tutorials sound to be on the right track.
Essentially, the bcm4329.ko file is the wifi module (drivers) for Wifi. This module file, bcm4320.ko, stored in /system/lib/modules/ must match the currently flashed kernel. If the wifi module and kernel do not match, you will receive this Wifi error.
Whenever a kernel developer compiles a new kernel, they must also compile the Wifi module, bcm4329.ko. The bcm4329.ko module file must be loaded into /system/lib/modules on the phone along with the custom kernel being flashed to the boot partition. If either of these files mismatch, Wifi will throw the error.
I walked through a lot of the logic in a separate thread troubleshooting this issue: WiFi - Error
Hope that helps!
So I've been on Ineffabilis since just about New Year's. 1.0, and on through 1.3 now.
Wifi Tether has always worked.
I use stock Kernels - always.
I recently got on Ineffabilis 1.3, and did not flash the Kernel (since I was already on the 2.01.605.11 kernel). Wifi tether works great. I use it all of the time.
So I go to turn on Wifi the other day (which I know worked on 1.1)... Error. I turn it on again.... Turns on, but 'Unable to scan for networks'.
Awkward.
So Troubleshooting 1:
Go to the Stock 2.01.605.11 Kernel and Wifi Modules thread. Flash the Wifi Modules. Flash the Kernel (again).
Still Error (won't turn on), then the second attempt, it 'turns on' (or appears to) and 'Unable to scan for networks'.
I say OK.
Troubleshooting 2:
Flashing Ineffabilis 1.3 again, and then letting it go into Bootloader, and flash its own Kernel. The kernel comes with the ROM (even though I think it's that same 2.01.605.11 version kernel - but just for the procedure). So Fresh flash of Ineffabilis 1.3. Then Flashing the kernel that comes with Ineff.
Boot up.
Same problem. Wifi gets 'error'. Then when I try to turn it on again, it's 'Unable to scan for networks'.
Am I stupid?
Should I flash wifi drivers and a kernel from 1.02 (original version, before OTA)?
Is my middle name Suzie?
I'm so confused here.
------------------------------------SOLUTION-------------
I did adb shell and deleted /data/misc and /data/local
then exit
then adb reboot
Problem solved!
I don't know what data in one of those two areas did it, but my wifi works now 100% without issue. I had already tried so much, I don't know which of the two had the problem in it, but neither one seemed to affect the data on my phone enough for me to notice, so I am happy.
You need to do a full wipe and install everything including the kernel. ROM does not like flashover.
I had this since the kernel auto-flash in this rom appears broken. You only need to flash the updated kernel with the updated libs for you to get past this.
here's the one you need- http://bit.ly/zCmQGk
flash that zip in recovery. Once it copies the new libs into place it will create a PH image and drop it onto the flash card. Reboot into hboot and allow it to update the kernel itself.
That will set you straight.
dottat said:
I had this since the kernel auto-flash in this rom appears broken. You only need to flash the updated kernel with the updated libs for you to get past this.
here's the one you need- http://bit.ly/zCmQGk
flash that zip in recovery. Once it copies the new libs into place it will create a PH image and drop it onto the flash card. Reboot into hboot and allow it to update the kernel itself.
That will set you straight.
Click to expand...
Click to collapse
I appreciate that!
Still 'Unable to Scan for Networks'. I think I need to wipe something.
Upsetting. Time to finally wipe with 112 apps.
This would be the solution though. Installing the libs and kernel should be the fix. I must have some messed up data somewhere.
Turns on, Scans for networks, and says 'Unable to scan for networks' in a toast notification like every 5 seconds, and after a few times, it goes off then on again (unlimited cycle).
I added a network for a known wifi hotspot. Didn't add in the list!
It's my Data. As soon as I restore (just my data) from nandroid, and boot up, wifi is fried.
A completely fresh wipe and flash of ROM works great. I'm trying to wipe
/data/system (didn't work)
/data/data (didn't work - but the 'Weather lockscreen was blank and all kinds of interesting icons and widgets were missing.... yet WiFi still did its thing)
So it's not in /data/data or /data/system..... hhhmmmmmm. still hunting.
and then let the data folders sync back up after the phone boots up. Trying each folder inside /data until I find which one messed up my wifi. I'm determined!!
I get this in DDMS when I try to turn it on.
http://pastebin.com/DYFF0Ft3
FOUND IT!
I deleted (just to try it)
/data/misc
/data/drm/
/data/radio
/data/local
One of those did it. I don't know if I'm going to narrow it down, or just wipe those and leave the rest of my data.
So it was in /data/local or /data/misc
I deleted them both - wifi works! Awkward.
Thanks for the help either way, gentlemen!
so i noticed that my wifi also stopped working (in addition to my bluetooth). so i tried going back to RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00 .1123r_3161E_9K_QMR_release_233635_signed.exe. i thought going back to stock would restore it, but no dice. i'd like to try deleting the folders you mentioned, is there any risk in doing this?
flash this boot into your mini5
then you can use baseband 3xx in android 2.3.3 without button flashing
but it will bring another problem ：wifi couldn't turn on
I have tried it in DSC 0.6、1.1 ，it works well except wifi
it couldn't work in miui or cm7
New baseband without wifi....What is the benefit?...
Sent from my Dell Streak using Tapatalk 2
manics, would you pull and share config from this kernel?
adb pull /proc/config.gz
this boot was not builded by me
it is from a modified version of streakmi
i found it in BBS.ZHANGKU.COM
i am trying to ask the poster
but i guess maybe it is using kernel of streakmod recovery
_n0p_ said:
manics, would you pull and share config from this kernel?
adb pull /proc/config.gz
Click to expand...
Click to collapse
N0p. Want me to flash and pull?
I dont use wifi.
I try to do it tomorrow (will be near pc, so can unpack everything without flashing).
--
WiFi simply needs corresponding driver and I might blindly guess that dhd.ko from 407 should do.
the poster says ,this boot is from the earliest 2.3.3 roms of dj_steve, but he could not remember from which one.
Checked kernel config vs 407 kernel - nothing changed except resume speedup. I wonder what code in kernel could control blinking.
Hello,
I own a 64GB P7510. It is rooted and currently it has a version of CM9 ICS installed. I have tried several versions of ICS and Stock Honeycomb as well as Tasks GalaxyTask 14.
I use Splashtop HD mostly on the tab and have noticed that it randomly freezes the tablet and crashes the device. The only way to recover it to hold the power button down and wait for the device to restart.
In Stock ROM and GalaxyTask 14 it seems to work fine. In ICS or when installing Pershoots kernel the crashes occur. The crashes are totally random and can happen when splashtop has been left along for a minute, ten minutes or not at all.
I assume this has something to do with the kernel as I experience the same problem with GalaxyTask 14 but only when I install the pershoots kernel. It also happens in all ICS versions I have tried.
Current config: Android 4.0.4, Kernel [email protected] #1 SMP PREEMPT Sat June 23 22:18:30 EDT 2012, Cyanogenmod version: 9-20120703-NIGHTLY-p4wifi, Build date: Mon Jul 2 22:00:33 PDT 2012, Build number: cm_p4wifi-userdebug 4.0.4 IMM76L eng.jenkins.20120702.220017 test-keys
Splashtop version: (Streamer) 2.0.0.4 (also tested in older streamer but same results), (Client) Splashtop 1.9.9.5 SW r21787
This make using Splashtop unusable as it randomly crashes. When I spoke to Splashtop support they said they had never heard of a problem like it.
I have looked all over the web and done extensive searches of XDA to try to find out what the problem could be, but to no avail. I also hope I have put this question in the correct forum.
The problem takes place in (and I have tested):
GalaxyTask 14 (only with pershoots kernel)
AOKP ICS
CM9 ICS
It works fine in:
GalaxyTask 14 without pershoots kernel
Stock HC ROM
Even if there is no solution, is there a way I could troubleshoot the problem.
Any help would be appreciated.
Many thanks,
Graham.
Just bumping. Has no one at all experienced this problem at all?
I reloaded Honeycomb this week and there were no problems at all, then reloaded ICS and it still crashes. I can't be on my own surely?
Graham.
on ICS (you can use 0710 experimental i posted this morning on droidbasement),
as soon as it crashes, head straight to recovery and pull /proc/last_kmsg and send it to me.
i'll see what i can do.
I will flash this now and let you know. My tab crashes quite a bit on the 07.04 CM9 nightly, and am thinking about going back to HC
Sent from my GT-P7510 using xda premium
it should not be crashing. you may have a bad app or an unstable OC doing harm. at any rate, load up 7/10 experimental, do not OC or install any other app but splashtop. if it crashes, pull the log.
pershoot said:
it should not be crashing. you may have a bad app or an unstable OC doing harm. at any rate, load up 7/10 experimental, do not OC or install any other app but splashtop. if it crashes, pull the log.
Click to expand...
Click to collapse
in fact, this is what you should do:
pull your data off /data/media, odin back to 3.2 (the whole tab will be wiped), odin CWM (found in the 7/10 experimental folder), boot CWM, wipe, flash 7/10 experimental, latest gapps, and boot in. dont restore any apps and dont OC. install only the splashtop app. observe and pull log if it crashes as i outlined above.
the added bonus from the above will ensure you don't have any more crashes from extraneous unknown factors.
When I said my Tab was crashing, I meant in general and not due to splashtop. I don't even use splashtop. I thought maybe your experimental build and giving you that one file could help troubleshoot crashing in general. Sorry about that.
Sent from my GT-P7510 using xda premium
Thanks Pershoots. I am not sure what is going on. I will have a look and send it to you. It may be next week before I get a chance.
Many thanks,
Graham.
pershoot said:
on ICS (you can use 0710 experimental i posted this morning on droidbasement),
as soon as it crashes, head straight to recovery and pull /proc/last_kmsg and send it to me.
i'll see what i can do.
Click to expand...
Click to collapse
hi pershots.
i rebooted into recovery after the last crash but i dont see where to pull that from. i am using cwm recovery. also when you talk of your 0710 experimental do you mean a newer version of the kernel?
many thanks,
graham.
medialinx said:
hi pershots.
i rebooted into recovery after the last crash but i dont see where to pull that from. i am using cwm recovery. also when you talk of your 0710 experimental do you mean a newer version of the kernel?
many thanks,
graham.
Click to expand...
Click to collapse
you need to be on 07/11 experimental rom (from droidbasement) or 07/12 nightly from get.cm.
please odin back to 3.2 (the whole tab will be wiped; make sure you back up any data you may have in /data/media), odin CWM (you can find this at droidbasement), boot it, wipe, flash either of those roms and flash latest gapps. enter in, do not restore any apps. install only splashtop and run it.
now observe.
if you get a crash, head straight to recovery and do this:
adb pull /proc/last_kmsg .
then send that to me.
I am experiencing the same problem. On stock HC 3.2 splashtop worked fine but my HDMI cable out didn't work so I flashed RS_Supremacy_AOKP v0.2 pershoots kernel 2.6.36.4-cynogenmod+, my HDMI cable worked great after that the rom is awesome I love it but only just recently noticed that splashtop now is almost useless it always freezes within 5-10mins of use and I then need to hold power button down to restart tablet. I'll be watching this thread with great interest as I don't really want to change my rom I really like this one.
Sent from my GT-P7100 using XDA Premium HD app
Ichigo66 said:
I am experiencing the same problem. On stock HC 3.2 splashtop worked fine but my HDMI cable out didn't work so I flashed RS_Supremacy_AOKP v0.2 pershoots kernel 2.6.36.4-cynogenmod+, my HDMI cable worked great after that the rom is awesome I love it but only just recently noticed that splashtop now is almost useless it always freezes within 5-10mins of use and I then need to hold power button down to restart tablet. I'll be watching this thread with great interest as I don't really want to change my rom I really like this one.
Sent from my GT-P7100 using XDA Premium HD app
Click to expand...
Click to collapse
it will not get fixed until i see logs.
Ok I'm still a bit of a noob when it comes to these things but i'll give it a try and see if I can get a log for u fingers crossed X
Sent from my GT-I9300T using xda app-developers app
pershoot said:
you need to be on 07/11 experimental rom (from droidbasement) or 07/12 nightly from get.cm.
please odin back to 3.2 (the whole tab will be wiped; make sure you back up any data you may have in /data/media), odin CWM (you can find this at droidbasement), boot it, wipe, flash either of those roms and flash latest gapps. enter in, do not restore any apps. install only splashtop and run it.
now observe.
if you get a crash, head straight to recovery and do this:
adb pull /proc/last_kmsg .
then send that to me.
Click to expand...
Click to collapse
Here you go Pershoots. I hope this is what you are looking for. I am not really up on using ADB. I could not get it to do a pull from CWM recovery or Odin recovery so I rebooted and ran USB Debug then finally got the computer to see the device. Anyhow, here is what I pulled. If I did this wrong if you could please explain or point me to somewhere to see the steps needed to ADB from recovery as I could not find anything on Google about ADB recovery galaxy tab 10.1.
Thank you for looking at this for me.
Here you go...
[ 12.526464] [DBG] upload cause : UPLOAD_CAUSE_INIT
[ 12.526479] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 12.526464] [DBG] upload cause : UPLOAD_CAUSE_INIT
[ 12.526479] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 13.162166] i2c i2c-11: sendbytes: NAK bailout.
[ 13.276914] mxt_config_settings
[ 13.852817] Failed to add route HPOUTL->Headset Jack
[ 13.886165] Tegra protected aperture disabled because nvmap is using system memory
[ 14.706771] init: cannot open '/initlogo.rle'
[ 14.712062] init: Unable to open persistent property directory /data/property errno: 2
[ 14.721883] android_usb: already disabled
[ 84.203676] SysRq : Emergency Remount R/O
[ 84.208259] Restarting Linux version 2.6.36.4-cyanogenmod+ ([email protected]) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-51) ) #1 SMP PREEMPT Sat Mar 17 18:04:36 EDT 2012
[ 84.208268]
[ 84.266040] VFS: Close: file count is 0
[ 84.884148] Restarting system.
No errors detected
You're running a really old kernel/build.
I'll be posting new test builds soon. U can retest against them.
pershoot said:
You're running a really old kernel/build.
I'll be posting new test builds soon. U can retest against them.
Click to expand...
Click to collapse
Thanks pershoots.
From looking at that output would you have any idea what is going wrong?
Graham.
medialinx said:
Thanks pershoots.
From looking at that output would you have any idea what is going wrong?
Graham.
Click to expand...
Click to collapse
not really. altho, there was a blurb about protected memory which ive since enabled in the video driver (been enabled for a while).
crash
The crash is happening in aDownloader and Splashtop... now in JB. It happens very randomly...
I have re-flashed it, re-odined it, re-stocked it many times(tried all sorts of different roms), but I get this issue always when I have pershoot kernel, and unfortunately there isn't much alternative choice on ICS / JB. It looks like this kernel issue is here since the beginning and basically I am unable to download torrents (or stream HD via splashtop) without restarting it a couple of times.
It's really strange that more people are not experiencing this issue...
Try the experimental I posted for cm9 or 10 (07/28).
Post logs if it crashes.
Hi pershoots.
I have been running jellybean with your kernel 26/7 for the last week and had only a couple of crashes. Maybe it is an ics issue as i have reflashed ics this week too and it crashed under it.
Graham.
Disclaimer: I will not be responsible if you brick your NT or your significant other leaves you for bricking theirs. As always, flash at your own risk.
Here is a full CM10 ROM with 1.2GHz OC that is 5 touch enabled. I usually build once very couple of days just to keep the CM10 base up to date. I'm not a kernel whiz so don't expect any large amount of progress not made by the kernel devs.
This ROM will now work with or without the updated firmware, thanks mik_os!. Please see this post on how to install the updated firmware http://forum.xda-developers.com/showpost.php?p=33699529&postcount=75
With that said, many huge thanks to everyone who has put so much effort into making this awesome. If I forgot you, let me know!
Kuzma30, chrmhoffman, mik_os, fattire, Hashcode, Rebellos, demetris_I, Succulent, CelticWebSolutions, eyeballer, Bauwks, CM team, TWRP team, TI, BN
Here's general instructions on how to proceed
Code:
1. Download ROM from this post and get the files from post referenced above
2. Boot into recovery and wipe data/factory reset
4. Flash the Touch update ROM
5. follow instructions in referenced post
6. If you are CWM, you can proceed with flashing the ROM from this post
7. If you are using TWRP, I recommend switching to CWM until we figure out what is causing the 'unable to mount /bootdata' error
8. boot to recovery, wipe data/factory reset, Flash ROM from this post
Here's the ROM
2012-11-12
Updates:
Update WI-LAN modules from TI
Minor build tweaks
Upstream CM sync
http://celticstorage.co.uk/cm10/cm-10-20121112-UNOFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-10-20121112-UNOFFICIAL-acclaim.zip.md5sum
2012-11-07
Updates:
Huge thanks to mik_os for fixing wifi sleep and hopefully resolve sdcard unmount issues.
OC kernel to 1.2 GHz should work on ALL devices. I previously couldn't boot oc roms but working now
Shadowgun still broken
SGX driver update
Other minor kernel tweaks
upstream CM sync
http://celticstorage.co.uk/cm10/cm-10-20121107-UNOFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-10-20121107-UNOFFICIAL-acclaim.zip.md5sum
2012-11-03
Updates:
Huge thanks to mik_os for updating touch driver to detect fw version and mirror inputs if needed. Also disable gestures which fixed dead trigger
OC kernel to 1.2 GHz should work on ALL devices. I previously couldn't boot oc roms but working now
Disable joystick driver, see if Shadowgun works!
Change back to 9100 cpuidle due to reboots
upstream CM sync
http://celticstorage.co.uk/cm10/cm-10-20121103-UNOFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-10-20121103-UNOFFICIAL-acclaim.zip.md5sum
Known issues
Infrequent reboots
SDCARD remove error when waking from deep idle. Workaround is to turn wifi off manually before sleeping or have it turn off automatically after five minutes. If you do get one, you have to reboot to make sdcard work again
TWRP is currently wonky. Please use CWM instead
Some games don't work right
2012-31-10
http://celticstorage.co.uk/cm10/cm-10-20121031-UNOFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-10-20121031-UNOFFICIAL-acclaim.zip.md5sum
I will post a 5 touch enabled TWRP as soon as the /bootdata bug is squashed. Please use CWM for time being.
Here's a 5 touch CWM (even though it doesn't use touch, doesn't hurt to have it)
flash with fastboot
CWM v6.0.1.5
http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc_5touch_recovery.img
http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc_5touch_recovery.img.md5sum
Happy flashing!
Disclaimer: I take no responsibility if anything happens to your Nook Tablet.
You and only you can take the blame if you don't follow my guide.
And don't mess with others people Tablets.
If that is clear lets get busy.
This is a guide of how to update Nook Tablet touch controller eeprom firmware with one that supports Multitouch.
1. Flash this rom from custom recovery
http://celticstorage.co.uk/cm10/Touch Firmware Update ROM.zip There is No need for Gapps .
MD5: 8BFC2C50F68CBEB6E3CD341F366BA773
2.Go into settings and disable screen sleep. Also make sure all options for keeping tablet awake are turned on
Settings > Developer Options > Stay awake should be checked + adb root access
Make a reboot and let it settle for a second.
Take a deep breath and connect it to Computer USB port and make sure you have driver installed for adb access.
Unrar firmware attached
Copy it into ext sdcard.
Then load adb shell
su
cd sdcard
echo "ft5406-sc3052-1024X768.bin" > /sys/devices/platform/i2c_omap.2/i2c-2/2-0038/fwupdate
It worked first try but it may need more tries.
You can check if all ok by issueing dmesg.
When you type echo "ft5406-sc3052-1024X768.bin" > /sys/devices/platform/i2c_omap.2/i2c-2/2-0038/fwupdate and it takes some seconds to finish its probably working.
Go into recovery and wipe everything and flash a ROM that is Multitouch enabled of your choice.
MD5 of firmware attached: 9F3177B131BCEC2B088ECB04280B1BB1
Question on this, since you mentioned simple adb commands:
Can you run this from a terminal? I ask because I've had issues getting adb working properly for my nook.
Also, what is the advantage of 5 point touch? I assume there is one, but I'd like to know.
Sent from my CM10 Skyrocket
Quando Omni Flunkus Moritati
liquidzoo said:
Question on this, since you mentioned simple adb commands:
Can you run this from a terminal? I ask because I've had issues getting adb working properly for my nook.
Also, what is the advantage of 5 point touch? I assume there is one, but I'd like to know.
Sent from my CM10 Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
apparently the 5 point touch fixes a lot of the problems with games like shadowgun and the like.
Here's a 5 touch CWM (even though it doesn't use touch, doesn't hurt to have it)
flash with fastboot
CWM v6.0.1.5
http://celticstorage.co.uk/cm10/CWM_...h_recovery.img
http://celticstorage.co.uk/cm10/CWM_...ery.img.md5sum
Happy flashing!
Click to expand...
Click to collapse
use command :
fastboot flash recovery CWM...
is it right ?
ryan.nguyentran said:
use command :
fastboot flash recovery CWM...
is it right ?
Click to expand...
Click to collapse
Yeap
Sent from my Xperia S using xda app-developers app
---------- Post added at 03:01 PM ---------- Previous post was at 02:49 PM ----------
liquidzoo said:
Question on this, since you mentioned simple adb commands:
Can you run this from a terminal? I ask because I've had issues getting adb working properly for my nook.
Also, what is the advantage of 5 point touch? I assume there is one, but I'd like to know.
Sent from my CM10 Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
In theory it should work.
Work
Thanks u :x
can i flash any rom CM10 with 5 touch firmware work ?
Yes you can and i didnt see you thanking anyone That is why Thanks button exist
Enjoy your Nook.
@Demetris: Where is the updatefw.sh? I checked on the sdcard and don't see it. I ended up copying it over from the original post with it. Is yours different?
Also, how long will it actually take for the firmware to flash once the command actually goes? I kept getting update fail, but now it is sitting at the point after the long list of numbers. It's been a few minutes.
----
Not sure if anyone else will have this problem. But after installing the Touch Upgrade ROM my device wouldn't boot. It was stuck at the CM9 loading animation.
I checked the logcat and it turned out to be an issue with SettingsProvider sqlite database being readonly, and unable to upgrade. If you run into this, just adb into the shell and browse to /data/data/com.android.providers.settings/databases. From there mv your settings.db.
You do this when the device is stuck at the boot animation.
If successful it should immediately start the OS.
demetris_I said:
In theory it should work.
Click to expand...
Click to collapse
I may give it a try.
I'm really wanting to keep the Dr Seuss apks working (I've had huge issues with them on CM10) as my kids love them, so we'll see.
Android 4.2 will be multiusers capable.
demetris_I said:
Android 4.2 will be multiusers capable.
Click to expand...
Click to collapse
That won't help me with those apks, though. I'm pretty sure that the FC is tied to some part of the kernel that is there in CM9, but not in CM10. They FC on my Skyrocket as well (I've used CM10, AOKP, a TouchWiz JB ROM, PA and CM9.1 Stable and the only one they play on is CM9/9.1).
I followed your directions, except there is no updatefw.sh, so I just put it there manually.
I have tried 50+ times and it never succeeds. It did change the VendorID, but the TPFWVER never changes, and it continually fails to update.
Any way to diagnose this?
demetris_I said:
Disclaimer: I take no responsibility if anything happens to your Nook Tablet.
You and only you can take the blame if you don't follow my guide.
And don't mess with others people Tablets.
If that is clear lets get busy.
This is a guide of how to update Nook Tablet touch controller eeprom firmware with one that supports five points touch.
1. Flash this rom from custom recovery
http://celticstorage.co.uk/cm10/Touch Firmware Update ROM.zip There is No need for Gapps .
MD5: 8BFC2C50F68CBEB6E3CD341F366BA773
2.Go into settings and disable screen sleep. Also make sure all options for keeping tablet awake are turned on
Settings > Developer Options > Stay awake should be checked + adb root access
Make a reboot and let it settle for a second.
Take a deep breath and connect it to Computer USB port and make sure you have driver installed for adb access.
Load up adb shell and type this.
1.su
2.sh updatefw.sh
If it reports: "Update fail! Try again!"
retype: sh updatefw.sh as many times as needed to flash it successfully.
Then type:
adb reboot
Go into recovery and wipe everything and flash New SGT7 cpuidle ROM that is 5 touch enabled from above or any new 5 touch enabled rom of your choice.
Click to expand...
Click to collapse
slgooding said:
I followed your directions, except there is no updatefw.sh, so I just put it there manually.
I have tried 50+ times and it never succeeds. It did change the VendorID, but the TPFWVER never changes, and it continually fails to update.
Any way to diagnose this?
Click to expand...
Click to collapse
I will update first post.
@all
Welcome to new era,
Enjoy your Nook.
slgooding said:
I followed your directions, except there is no updatefw.sh, so I just put it there manually.
I have tried 50+ times and it never succeeds. It did change the VendorID, but the TPFWVER never changes, and it continually fails to update.
Any way to diagnose this?
Click to expand...
Click to collapse
Instructions and files updated in second post for flashing FW.
The new instructions worked for me. Took about 7 tries and it finally went. Thanks again!
demetris_I said:
Disclaimer: I take no responsibility if anything happens to your Nook Tablet.
You and only you can take the blame if you don't follow my guide.
And don't mess with others people Tablets.
If that is clear lets get busy.
This is a guide of how to update Nook Tablet touch controller eeprom firmware with one that supports five points touch.
1. Flash this rom from custom recovery
http://celticstorage.co.uk/cm10/Touch Firmware Update ROM.zip There is No need for Gapps .
MD5: 8BFC2C50F68CBEB6E3CD341F366BA773
2.Go into settings and disable screen sleep. Also make sure all options for keeping tablet awake are turned on
Settings > Developer Options > Stay awake should be checked + adb root access
Make a reboot and let it settle for a second.
Take a deep breath and connect it to Computer USB port and make sure you have driver installed for adb access.
Load up adb shell and type this.
1.su
2.sh updatefw.sh
If it reports: "Update fail! Try again!"
retype: sh updatefw.sh as many times as needed to flash it successfully.
Then type:
adb reboot
Go into recovery and wipe everything and flash New SGT7 cpuidle ROM that is 5 touch enabled from above or any new 5 touch enabled rom of your choice.
Edit: This will update firmware on first try(at least it did for me)
Unrar firmware attached MD5: 9F3177B131BCEC2B088ECB04280B1BB1
Copy it into ext sdcard.
Then load adb shell
su
cd sdcard
echo "ft5406-sc3052-1024X768.bin" > /sys/devices/platform/i2c_omap.2/i2c-2/2-0038/fwupdate
It worked first try but it may need more tries.
You can check if all ok by issueing dmesg.
When you type echo "ft5406-sc3052-1024X768.bin" > /sys/devices/platform/i2c_omap.2/i2c-2/2-0038/fwupdate and it takes some seconds to finish its probably working.
Click to expand...
Click to collapse
Is it suppose to have cyanogen mod 9 show up while booting after step 1 flashing Touch Firmware Update ROM.zip. I think I screwed up somewhere.
Vector2nds said:
Is it suppose to have cyanogen mod 9 show up while booting after step 1 flashing Touch Firmware Update ROM.zip. I think I screwed up somewhere.
Click to expand...
Click to collapse
according to tonyp23 this upgrade to the 5 touch firmware requires an older kernel which in this case is the one from cm9. afterwards you can flash any cm10 rom which has the newer kernel. so what you are experiencing should be normal. i haven't tried it myself but yea...
Vector2nds said:
Is it suppose to have cyanogen mod 9 show up while booting after step 1 flashing Touch Firmware Update ROM.zip. I think I screwed up somewhere.
Click to expand...
Click to collapse
No its supposed to. It's a CM9 ROM. When you are done with that flash the CM10 ROM in OP
Do we need to install the ROM as per the instructions, or with the new addition in the 2nd post, can we just update the firmware?