Need some help on this.
Here are the steps that I have taken so far:
git clone git://android.git.kernel.org/kernel/experimental.git
cd experimental
git branch -r
git checkout --track -b 2.6.32 origin/android-msm-2.6.32-test1
I then have the correct 2.6.32 kernel checked out from git.
I then adb pull /proc/config.gz .
zcat config.gz > .config
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
export KERNEL_DIR=/full/path/to/kernel
then:
make oldconfig
(hit enter to accept all defaults)
make
Problem is I then encounter an error on USB ether.c. I am able to comment out enough of the code to get it to compile the zImage, but after repacking using a stock boot.img ramdisk, does not boot.
Any tips on either solving the USB issue or getting the kernel to boot would be appreciated!
You can make mahimahi_defconfig to get the default android kernel config and add stuff on from there with make menuconfig. Not sure about the usb issue. Swetland said there could be issues with the .32 kernel since they just started working on it.
I used the .32 kernel over the weekend. Overall I found I got worse battery life, The auto brightness adjust doesn't work since the sensors don't work with it yet, and the button backlights were very flaky. I went back to .29 and decided to hold off on .32 till the android devs tuned it up for the N1.
Not trying to persuade you not to use it. Just wanted to let you know what my experience was.
I can confirm the issue. I just tried compiling and I get the same issue.
Code:
CC drivers/usb/function/ether.o
drivers/usb/function/ether.c: In function 'usb_ether_setup':
drivers/usb/function/ether.c:295: error: 'struct net_device' has no member named 'open'
drivers/usb/function/ether.c:296: error: 'struct net_device' has no member named 'stop'
drivers/usb/function/ether.c:297: error: 'struct net_device' has no member named 'hard_start_xmit'
drivers/usb/function/ether.c:298: error: 'struct net_device' has no member named 'get_stats'
make[2]: *** [drivers/usb/function/ether.o] Error 1
make[1]: *** [drivers/usb/function] Error 2
make: *** [drivers] Error 2
Edit:
After looking through the .config I yanked off the phone with cyanogen's addon, I found CONFIG_USB_FUNCTION_ETHER=y. I switched it to no and it has compiled fine. No clue on if it boots yet, still trying.
Sorry if this is a dumb question. But will this kernel implement more or all of the n1's available ram?
A really nice way you can test if your kernel boots without having to overwrite your old kernel is this command
fastboot boot /path/to/zImage
If it doesn't boot, you can power cycle your phone and you're back to the kernel that you had before. Once you've tested the kernel and want to flash it
fastboot flash zimage /path/to/zImage
staulkor said:
Edit:
After looking through the .config I yanked off the phone with cyanogen's addon, I found CONFIG_USB_FUNCTION_ETHER=y. I switched it to no and it has compiled fine. No clue on if it boots yet, still trying.
Click to expand...
Click to collapse
Aha. Doing that, compiling, then fastboot boot zImage worked!
Thanks all
EDIT: Wow, this thing is really really fast. Animations and overall performance while running the Nexus livewallpaper are equivalent to the 2.6.29 kernel on non-live wallpapers. Don't have working backlights on the 4 touch buttons, assume this is a lib/hw/sensors.so issue. Also can't compile the Wifi module without it erroring out as well. Looking forward to seeing rom's based on this!
jairuncaloth said:
A really nice way you can test if your kernel boots without having to overwrite your old kernel is this command
fastboot boot /path/to/zImage
If it doesn't boot, you can power cycle your phone and you're back to the kernel that you had before. Once you've tested the kernel and want to flash it
fastboot flash zimage /path/to/zImage
Click to expand...
Click to collapse
WOW that saves a lot of time! Thanks for the tip
I was using the packaging method at the bottom of this wiki page http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
It that the correct method on making the correct boot.img? Whenever I tried it I couldnt get it to boot. I just did the direct zImage boot and it worked fine, nothing changed.
Edit: Got my zImage booting with the fastboot method. Haven't tried the "traditional" way. And Wow! It is so much faster with the live wallpapers. I can confirm the 4 touch button backlights dont work along with auto dim and proximity sensor. It is also still only seeing 217352 kB of ram. I saw the "High Memory" option in the .config. I will play with that and see if I can enable all 512mb on this sucker
staulkor said:
WOW that saves a lot of time! Thanks for the tip
I was using the packaging method at the bottom of this wiki page http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
It that the correct method on making the correct boot.img? Whenever I tried it I couldnt get it to boot. I just did the direct zImage boot and it worked fine, nothing changed.
Edit: Got my zImage booting with the fastboot method. Haven't tried the "traditional" way. And Wow! It is so much faster with the live wallpapers. I can confirm the 4 touch button backlights dont work along with auto dim and proximity sensor. It is also still only seeing 217352 kB of ram. I saw the "High Memory" option in the .config. I will play with that and see if I can enable all 512mb on this sucker
Click to expand...
Click to collapse
Were you able to compile the wireless driver?
Yes, wireless is working fine. The module is put in drivers/net/wireless/bcm4329/bcm4329.ko. Just push it to /system/lib/modules/bcm4329.ko and reboot and your wireless should work.
staulkor said:
Yes, wireless is working fine. The module is put in drivers/net/wireless/bcm4329/bcm4329.ko. Just push it to /system/lib/modules/bcm4329.ko and reboot and your wireless should work.
Click to expand...
Click to collapse
I don't reboot after pushing the wifi driver and haven't had any trouble out of it.
jairuncaloth said:
I don't reboot after pushing the wifi driver and haven't had any trouble out of it.
Click to expand...
Click to collapse
The module is loaded when wifi is turned on, so yeah, no reboot needed. I sometimes try to turn on wifi after updating the kernel, see it fail, push the driver module, try again and off it goes.
So it does. Just tried it and what do you know
Any luck with you guys getting the sensors working?
staulkor said:
So it does. Just tried it and what do you know
Any luck with you guys getting the sensors working?
Click to expand...
Click to collapse
Unfortunately no. No light sensor also means no proximity sensor which is awful when making phonecalls.
swetland said:
The module is loaded when wifi is turned on, so yeah, no reboot needed. I sometimes try to turn on wifi after updating the kernel, see it fail, push the driver module, try again and off it goes.
Click to expand...
Click to collapse
Done that a few times as well
humancyborg said:
Unfortunately no. No light sensor also means no proximity sensor which is awful when making phonecalls.
Click to expand...
Click to collapse
I can't live without the proximity sensor
That thing has spoiled me from the cliq and now n1
TheDudeOfLife said:
I can't live without the proximity sensor
That thing has spoiled me from the cliq and now n1
Click to expand...
Click to collapse
Woah man. Been wondering what happened to you. lol You gonna be devvin' up the N1?
good work everyone now I need to remember my programming from college and such to help work out some bugs can't wait to get mine tomorrow!
Anyone know how or where the /lib/hw/ sensor files get built? Is there source available?
humancyborg said:
Anyone know how or where the /lib/hw/ sensor files get built? Is there source available?
Click to expand...
Click to collapse
Not yet. Last I checked it was a bunch of empty projects. I'm hoping they'll have it soon.
I see two new commits in the experimental tree today regarding the CM3602 (light and proximity sensor for Nexus).
Going to do a git pull and see if it works.
Also noticed that the accelerometer is not working either using 2.6.32.
EDIT: SUCCESS! Light, proximity and accelerometer sensors are now working with this new build!!
Related
Any of us still on stock FRF91 with mac addresses not starting with 00:* are dealing with the bug where wi-fi disconnects when the phone goes to sleep:
(sorry, my account is too new to properly link the bug thread)
google.com/support/forum/p/android/thread?tid=01a47ff5b0a92d52&hl=en&start=120
This is fixed in the latest CM6 nightly builds, but I don't think it's possible to get the .ko from that build to work on stock FRF91.
I backported the fix from git (android.git.kernel.org/?p=platform/system/wlan/broadcom.git;a=commitdiff;h=5a838529e6197475cbe8f5a4557fbd31f90586a6) to the earlier version of the driver.
I've been testing this for the last 30 minutes and haven't been kicked off wi-fi once after the screen went to sleep.
How to install:
Make sure you're on FRF91 and have rooted yourself
adb shell and get root via 'su'
Copy your old driver to /data/local: cat /system/lib/modules/bcm4329.ko > /data/local/bcm4329.ko.old
Check that the MD5 of the unzipped .ko is 959dda656228b4191f8e97b920482ae2
From your system, adb push the attached bcm4329.ko (unzip it first) to /data/local/bcm4329.ko.new
adb shell and get root via 'su' again
Copy the driver over top of the old one: cat /data/local/bcm4329.ko.new > /system/lib/modules/bcm4329.ko
Reboot
You'll probably screw up future OTA updates if you manually patch this, but it's easy enough to undo (just flash the stock FRF91 or replace the old driver). Also, it worked fine for me, but you'll be doing this at your own risk, etc, etc etc.
---
mmastrac, unrevoked
Does this work?
I'm at work without access to a usb cable and wonder if this is worth looking at later today.
I like this alot too bad am too bad at the shell stuff, can't this packed and flash it from recovery ?
nevermind that, I thought it's something different than normal push pull stuff.
Can do this through Root Explorer very easy and less hectic.
This doesn't work on CM 6RC1. get a wireless error can't start wireless.
I don't have the problems that my nexus logged of the wifi network while screen is off.
But when I make a ping to nexus one everything is fine when screen is on, but it become very unresponsable with screen off and has connection time out.
Is this the patch for that problem?
Can more people test this out? Some people report that the latest CM doesn't fix this issue.
kindiboy said:
This doesn't work on CM 6RC1. get a wireless error can't start wireless.
Click to expand...
Click to collapse
CM6 ships with a different kernel, so this .ko won't work for those builds. This is only for those on the stock FRF91 build who can't use the updated driver from the latest tree.
For CM6 users, it should be fixed in the latest nightlies here:
hxxp://mirror.kanged.net/cm/nightly/passion/
Formel-LMS said:
I don't have the problems that my nexus logged of the wifi network while screen is off.
But when I make a ping to nexus one everything is fine when screen is on, but it become very unresponsable with screen off and has connection time out.
Is this the patch for that problem?
Click to expand...
Click to collapse
This patch should fix this issue. The broadcom driver in stock FRF91 filters out traffic to the device when the screen is off due to a bug in the implementation that was supposed to filter out traffic to other devices instead.
I can ping my device even while the screen is off with this patch in place. You may also have to change your wi-fi sleep policy to get the best results.
mmastrac said:
This patch should fix this issue. The broadcom driver in stock FRF91 filters out traffic to the device when the screen is off due to a bug in the implementation that was supposed to filter out traffic to other devices instead.
I can ping my device even while the screen is off with this patch in place. You may also have to change your wi-fi sleep policy to get the best results.
Click to expand...
Click to collapse
Hi man, maybe you can check out the my thread about this issue here:
http://forum.xda-developers.com/showthread.php?t=731395
I hear there are people with the latest nightly build still finding the problem exists. And their MAC address starts with actually 00?
How about your case? Did your phone have this problem before and its MAC address, I suppose, begins with 38?
hbkmog said:
Hi man, maybe you can check out the my thread about this issue here:
I hear there are people with the latest nightly build still finding the problem exists. And their MAC address starts with actually 00?
How about your case? Did your phone have this problem before and its MAC address, I suppose, begins with 38?
Click to expand...
Click to collapse
My n1 has a 38:* MAC address, so I was seeing wifi disconnect almost as soon as the screen went off (and getting disabled in some cases).
There are other wifi issues on the n1 phones. This patch just fixes the worst one.
Yes, and my NexusOne has a MAC starting with 00.
WiFi doesn't disconnect, but I can't hear stream audio....
I try this fix here now.
But, what I wanna know:
Kernel updates includes this bcm***.ko, too.
Can you share your fixes, that the kernel devs can use them, too?
I tested this and seems to be working fine, thanks a lot.
Just wanted to add another thank you. I tried this and it's worked great.
Hm, it doesn't work on enoms rom.
Now I'm sad.
Formel-LMS said:
Hm, it doesn't work on enoms rom.
Now I'm sad.
Click to expand...
Click to collapse
Possibly because enoms rom is using a different kernel. I suggest you request enom to update the driver source in his rom.
Hi guys
someone can upload a modified stock (FRF91 or FRG33) with the fix?
i don't know how to fix it and i will be very grateful
thank you!!
@mmastrac
thank you
it works only on original FRF91 ROM
can you make ist for FRG33 ?
I just tested the new FRF83 (2.2.1) and it includes this fix. Pings now go through when the wifi sleep policy is set to never, as they should.
I'm not really sure about this part, but looking at the new bcm4329.ko binary it appears this patch was included:
http://android.git.kernel.org/?p=ke...ff;h=8097ca0f92819b977472381f46315de15633361c
nachod0g said:
I just tested the new FRF83 (2.2.1) and it includes this fix. Pings now go through when the wifi sleep policy is set to never, as they should.
Click to expand...
Click to collapse
Thanks heaps for confirming. I guess there isn't much stopping me from going to the new firmware other than another 1-click root method.
Hi all,
Inspired by the post made by crnkoj, Fix for nonworking WiFi on Simunlocked ATT Atrix 4G I decided to exploit this method and avoid the backdraws it has.
It worked very well for me on my 1.5.2, i don't see any problems with other versions as well.
Instead of restricting access to the settings.db file I decided to use db triggers to restrict changes for wifi_country_code.
The script (I modified the script from GladRoot4.2) can be found here
Many thanks to crnkoj, who came up with this solution and GladRoot team for the script.
DISCLAIMER
THIS IS ALL ON A BASIS OF INFORMING PEOPLE
I AM NOT RESPONSIBLE FOR ANY DAMAGE, LOSS OF DATA, OR BRICKED DEVICES IN CONJUNCTION OF TRYING OUT THESE STEPS
DO IT ON YOUR OWN RISK.
Instructions for the fix:
1.Do the factory reset with non-working sim in the phone.
2.Boot and register MotoBlur with wifi.
3.Switch wifi off!!!
4.Switch the device off and insert your sim card. Power the device back on.
5.Without switching on the wifi enter your MotoBlur details again (no need for internet connection).
6.Root the device.
7.Apply fix.
8.Reboot.
You should be fine. Switch on wifi and enjoy. I had to switch wifi on and back off twice to make it work.
Best regards,
Kiza
Great job Alexander!
I'm assuming this doesn't work on the Bell Atrix.
Great job Akizakian! I was looking into that way 2 weeks ago or so but i have almost no sql programming skills, so it was out of my league to do it. I think this fixes it all
I devised a better solution to this one. The problem lies in the WLAN drivers in the /system/etc/firmware/wifi/ the three binary files. I exchanged those with the driver files from the optimus lg 2x/speed and now everything works without any restrictions on the settings.db, i must test the situation if all wifi routers work with it, but i think there shouldnt be a problem, eventually someone can try to only change 1 by 1 the driver and see which one is the problem, so in the end effect the true solution would be just to exchange one driver binary. if there is interest post here so ill upload the 3 drivers i used, otherwise i wont bother, its a pretty straight forward procedure tho. oh racecar this solution should almost 100% work for the bell atrix aswell. And once the international atrix comes out and we get our hands on an international system dump/drivers we can just use that driver.
crnkoj said:
I devised a better solution to this one. The problem lies in the WLAN drivers in the /system/etc/firmware/wifi/ the three binary files. I exchanged those with the driver files from the optimus lg 2x/speed and now everything works without any restrictions on the settings.db, i must test the situation if all wifi routers work with it, but i think there shouldnt be a problem, eventually someone can try to only change 1 by 1 the driver and see which one is the problem, so in the end effect the true solution would be just to exchange one driver binary. if there is interest post here so ill upload the 3 drivers i used, otherwise i wont bother, its a pretty straight forward procedure tho. oh racecar this solution should almost 100% work for the bell atrix aswell. And once the international atrix comes out and we get our hands on an international system dump/drivers we can just use that driver.
Click to expand...
Click to collapse
There is intrest. I tried your solution using the files in my galaxy, that didnt work. wifi wouldnt even turn on. I would like to try yours.
pm me your email, ill send you the files attached. the thing is lg optimus 2x has basically the same board as moto atrix and luckyly the same broadcomm wlan/bluetooth chip with even fm radio on it....
wargame1 said:
There is intrest. I tried your solution using the files in my galaxy, that didnt work. wifi wouldnt even turn on. I would like to try yours.
Click to expand...
Click to collapse
crnkoj, this is really a great job! It's the best solution we could find! PM-ing you my email, please send me the files too.
crnkoj said:
I devised a better solution to this one. The problem lies in the WLAN drivers in the /system/etc/firmware/wifi/ the three binary files. I exchanged those with the driver files from the optimus lg 2x/speed and now everything works without any restrictions on the settings.db, i must test the situation if all wifi routers work with it, but i think there shouldnt be a problem, eventually someone can try to only change 1 by 1 the driver and see which one is the problem, so in the end effect the true solution would be just to exchange one driver binary. if there is interest post here so ill upload the 3 drivers i used, otherwise i wont bother, its a pretty straight forward procedure tho. oh racecar this solution should almost 100% work for the bell atrix aswell. And once the international atrix comes out and we get our hands on an international system dump/drivers we can just use that driver.
Click to expand...
Click to collapse
can you please send me the files, the motorola atrix wifi is not working, and non of the solution they have mentioned worked so far. email: [email protected] i hope your method can solve the problems
hello,
the method did not work, tested couple of times, however wifi refused to work period, please try to check if there is something can be done to with your patch
Have you done the factory reset before trying this method? It will not work if reset is not done.
i replaced the original wifi files with the lg optimus ones and now i cant unlock my phone(unlock swipe doesnt work) no matter how many times i pull out battery and put back... any help will be really appreciated.. thank u
i replaced the original wifi files with the lg optimus ones and now i cant unlock my phone(unlock swipe doesnt work) no matter how many times i pull out battery and put back... any help will be really appreciated.. thank u
i replaced the original wifi files with the lg optimus ones and now i cant unlock my phone(unlock swipe doesnt work) no matter how many times i pull out battery and put back... any help will be really appreciated.. thank u
Thx
great job
its working good
here is the link to a tutorial how to fix it with drivers:
http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
can someone please post the wifi drivers for one of the newer htc phones (like evo 4g).. the lg optimus drivers dont seem to work here neither doe the wifi fix patch
Well obviously this is an atrix fix not an htc evo4g... it could very much me something totally else
yes
yes i have an atrix and ok i didnt know u needed drivers from a tegra 2. n im in Ghana. i keep getting a message on command prompt saying "bad mode" after i chmod to 755 or 0755..
thanks
well do such:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
cd /system/etc/firmware/wifi/
chmod 755 *.bin
that must work, if you copied them over properly ...
I have been trying to port a crespo 2.3.5 Rom to the galaxy player 5, I have used the Cosmos .01 Rom as a base and the Crepso being the port. I dont plan on posting this ROM so dont yell at me for stealing or anything. Anyways, I followed a guide here on xda that is supposed to be universal for all devices and that didnt work. So now I used one that was made specifically for the galaxy players. After following all instructions, I get a bootloop. I havent ever done a logcat before and I would be happy to look if someone would let me know how it works. I was just wondering what the main or most likely causes for a bootloop is. That way I could fix it.
A logcat will tell you why it's looping by displaying error messages
Sent from my Galaxy Nexus using xda app-developers app
I knew that part. Is there any way to get to the logcat other than by using the sdk because I dont really have room to install any more software on here.
Sparx639 said:
I knew that part. Is there any way to get to the logcat other than by using the sdk because I dont really have room to install any more software on here.
Click to expand...
Click to collapse
If you don't want to install the sdk, you can always try the automated tool located at my siggy to get the logs(its just ~900kb) and the logs is just around 0.1 - 3mb usually depending on how long have you logged it(the longer you log, the bigger the size)
Thanks, I'm going to have to wait until tomorrow though cause I want some sleep. Typically I can find my own answers on Google but this could be anything and I didn't know how to get a log cat until just recently
Sparx639
I was able to get the tool to work but after flashing the nexus ROM, it fails to boot so how am I supposed to enable USB debugging and retrieve the log cat?
Logcat
To get a log cat, just plug your device into your computer while it's bootlooping, (make sure the drivers are installed, just install Samsung Kies to get drivers), open CMD and CD to you adb directory, and type "adb logcat". You will see an output, it will probably keep repeating the same thing over and over again.
K, I thought the device had to be fully bolted before you can obtain a logcat
Sparx639
After all that time, I have the device booted and everything works except for when recording video and I can't find anything on how to solve it. Any of you guys know what's wrong?
Sparx639 said:
After all that time, I have the device booted and everything works except for when recording video and I can't find anything on how to solve it. Any of you guys know what's wrong?
Click to expand...
Click to collapse
I believe you need to modify media_profiles.xml in/system/etc. The camcorder profile seems to be missing or incorrectly defined. I've just had a quick glance at the Logcat do I might have missed some other stuff
Sent from my Nexus 7 using XDA Premium HD app
Hey guys,
I compiled a kernel from the official sources and combined it with the ramdisk pulled from the stock kernel from my phone.
After clearing the dalvik cache and cache partition, I rebooted in download mode and flashed the kernel using ODIN.
The problem is that my device now gets stuck at the boot screen, and using adb to try and check the logcat isn't working (keeps waiting for the device to connect). USB debugging is on and it works again once I flash the stock kernel.
So my question is, how can I know what's wrong without logcats?
I'm certain everything I've done is correct to compile it (it's worth noting, however, that the sources' read me are the same for the Galaxy Y, which I thought is normal since my device is a galaxy Y in an ace's body).
Also, the flashlight flashes briefly before the boot screen appears, which I thought is weird.
Thanks a lot.
EDIT: Issue solved. I was using the wrong config file (the instructions bundled with the kernel were wrong).
You should try to get a ksmg not a logcat
Sent from my EVO using Tapatalk 2
thicklizard said:
You should try to get a ksmg not a logcat
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't think getting a dmesg would be possible since adb isn't initializing properly, considering the device is never detected (and none of the adb commands work).
GermainZ said:
I don't think getting a dmesg would be possible since adb isn't initializing properly, considering the device is never detected (and none of the adb commands work).
Click to expand...
Click to collapse
kmsg and dmesg are different beasts. Chances are your kernel panics before reaching the point where adb is initalized. You could try to get early printks using the serial console. Which device are you trying to debug? You will probably need a USB to serial converter to extract the early printks for debugging.
Bought a ZTE V965 because it was a special offer and I wanted to give android a try. Nice phone for the money, hardware wise, but software wise it needed some work. No google apps! I rooted the phone with vroot, worked fine. Installed SuperSU and CWM, seemed fine, but CWM is not fully functional. When I boot in restore mode, it doesnt mention CWM, it seems to be the native restore mode.
Tried to install google apps as APK's, but this didnt work. Play store closes instantly. Can't login chrome. Tried to install gapps.zip in recovery mode, error message, not working. I gave the phone a factory reset a few times during all this, and that worked fine.
Then I read a guide for manually installing gapps to the system app folder.
http://forum.xda-developers.com/showthread.php?t=2428314
So I installed root explorer, and put several gapps files in the system app folder:
OneTime Initializer.apk
GoogleLoginService.apk
Google Services Framework.apk
Setup Wizard.apk
Gmail.apk
Still not working though, gmail app crashes.
So I wanted to factory reset again, to start with a blank canvas. Big mistake!!! After the factory reset, the google files are not removed! Now when I boot the phone the setup wizard starts and crashes. I haven't found a way to get around it. What makes things worse, the phone is no longer detected when connected to my PC. Before ADB toolkit would detect the phone, no problem. Now nothing.
Any ideas what I can do? All that is necessary (I expect) is that this setupwizard is killed/bypassed/whatever, but I can't figure out how to do it.
I can get into the emergency number dialer, maybe something is possible from there?
Well, as always, immediately after posting, I made some progress! I booted the phone, and got a low battery warning, from which I could access the settings and enable USB debugging. Now I have ADB toolkit connected again. Also, I went into application settings, to kill and disable all these gapps. I managed to do this for all but one, the biggest problem: setupwizard.apk. Maybe because it's running i can't disable it? The option is greyed out. So when I reboot, I still get the setup wizard that crashes.
However, I do have what i believe is a stock ROM (from a chinese website, hard to be sure, but the name suggests it). Might try to flash that one using adb-toolkit.
Finally managed to fix it using linux shell. Killed the setupwizard task, deleted all gapps from system/app, problem solved.
Still would very much like to have working Gapps though. Hopefully this phone will become more popular outside China, so more people will look into flashing it. I've tried, but I can't do it. No fastboot drivers, and the native flash method (putting update.zip on phoen storage) doesn't work. For now I'll stick with the stock ROM and just use it in it's very limited state.
chance you can put a link to that stock ROM you found?
jethrofox said:
chance you can put a link to that stock ROM you found?
Click to expand...
Click to collapse
ROM:
http://www.romjd.com/Rom/Detail/17086
Root & Flash tool (I suspect):
http://dl.vmall.com/c0xa12brvo
I am still trying to figure out that romaster tool. Rooting is simple, but i can't manage to flash a ROM. Please keep me updated if you make any progress
Managed to fix everything + install CWM + flash ROM + install google apps. Will make a topic for this phone soon, when I've finished testing everything.
For now, check this one:
http://forum.xda-developers.com/showpost.php?p=48789159&postcount=15
Please my hero! Share your knowledge with me!
Byte_Me said:
Managed to fix everything + install CWM + flash ROM + install google apps. Will make a topic for this phone soon, when I've finished testing everything.
For now, check this one:
http://forum.xda-developers.com/showpost.php?p=48789159&postcount=15
Click to expand...
Click to collapse
Hello Byte_Me,
I've been looking for weeks how to get GApps on my ZTE V965 and tried everything I could, but each time with a different error. Today you made my day to let me know that I'm not the only one with this problem. Since no-one seems to use this device I wasn't able to find any working tutorial to fix Google Apps on this chinese android. I really hope you can tell me soon how you did this, so I can finally move on. Could you please send the link to your topic when you publish it? Thanks in advance and have a MERRY CHRISTMAS and a HAPPY NEWYEAR!!!
Thys-Its said:
Hello Byte_Me,
I've been looking for weeks how to get GApps on my ZTE V965 and tried everything I could, but each time with a different error. Today you made my day to let me know that I'm not the only one with this problem. Since no-one seems to use this device I wasn't able to find any working tutorial to fix Google Apps on this chinese android. I really hope you can tell me soon how you did this, so I can finally move on. Could you please send the link to your topic when you publish it? Thanks in advance and have a MERRY CHRISTMAS and a HAPPY NEWYEAR!!!
Click to expand...
Click to collapse
all info is already in the link you quoted, just not very organized. The topic will take some time, on holidays now.
followed your instructions, now thank god the Google Play works, but the Google search bar and Gmail app are still crashing...
you had similar things ?
---------- Post added at 06:01 PM ---------- Previous post was at 05:16 PM ----------
sctrach that - just updated the buggy apps through the Google Play.
Woo-hoo!
Nice to hear that, it makes the phone a lot more usable, doesnt it?
Any problems? I am still not satisfied, but I guess it's a work in progress.
Annoyances:
- not recognizing callers, some incompatibilities caused by country prefixes in my address book
- no badge notifications on icons, makes it harder too see missed calls, have to look at status bar
- some other stuff i can't think of now
Nice to hear that, it makes the phone a lot more usable, doesnt it?
Any problems? I am still not satisfied, but I guess it's a work in progress.
Annoyances:
- not recognizing callers, some incompatibilities caused by country prefixes in my address book
- no badge notifications on icons, makes it harder too see missed calls, have to look at status bar
- some other stuff i can't think of now
Byte_Me said:
Nice to hear that, it makes the phone a lot more usable, doesnt it?
Any problems? I am still not satisfied, but I guess it's a work in progress.
Annoyances:
- not recognizing callers, some incompatibilities caused by country prefixes in my address book
- no badge notifications on icons, makes it harder too see missed calls, have to look at status bar
- some other stuff i can't think of now
Click to expand...
Click to collapse
Tried reading through all the links, still can't get the light to turn green on mtk tools. V 965 is rooted by the Romjd app. Downloaded the rom rated 9.5. Installed the Vcom driver.
Can't load scatter files in sp flash tool..
Quite the noob at this stuff and guidance would be great. I did install ZTE driver when i connected the phone. Was that a mistake?
Tonypas said:
Tried reading through all the links, still can't get the light to turn green on mtk tools. V 965 is rooted by the Romjd app. Downloaded the rom rated 9.5. Installed the Vcom driver.
Can't load scatter files in sp flash tool..
Quite the noob at this stuff and guidance would be great. I did install ZTE driver when i connected the phone. Was that a mistake?
Click to expand...
Click to collapse
I never used SP flash tool.
Make sure phone is rooted.
Use MTK tools to install CWM zip package (just follow the instructions: http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417)
Boot into CWM and install google apps zip package.
I think USB debugging must be switched on in settings.
Byte_Me said:
I never used SP flash tool.
Make sure phone is rooted.
Use MTK tools to install CWM zip package (just follow the instructions: http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417)
Boot into CWM and install google apps zip package.
I think USB debugging must be switched on in settings.
Click to expand...
Click to collapse
Ok Thanks, I will try again.
I used SP flash tool because the yellow light never turned green. Which version of MTK Tools did you use?
yo, anybody managed to work with the GPS?
mine acts as if there isn't a GPS antenna at all.
Tonypas said:
Ok Thanks, I will try again.
I used SP flash tool because the yellow light never turned green. Which version of MTK Tools did you use?
Click to expand...
Click to collapse
252b
no green light means no root, but rooting is just one click.
jethrofox said:
yo, anybody managed to work with the GPS?
mine acts as if there isn't a GPS antenna at all.
Click to expand...
Click to collapse
Mine was very slow, fixed it with mobileuncle
Byte_Me said:
252b
no green light means no root, but rooting is just one click.
Click to expand...
Click to collapse
Its definitely rooted something else is missing.
jethrofox said:
yo, anybody managed to work with the GPS?
mine acts as if there isn't a GPS antenna at all.
Click to expand...
Click to collapse
Check with engineer mode that actual gps driver is loaded. Some roms don't have that driver such as lewa5 to my knowledge. Attached a pic below
Tonypas said:
Its definitely rooted something else is missing.
Click to expand...
Click to collapse
Color doesn't really matter, in you're rooted you should be able to log into the terminal feature in MTKtool. Try it
Help please
Guys whatever i soft or hard bricked my v965. It's stuck on the opening ZTE logo. I can't get into recovery mode to wipe the cache.
The ZTE drivers are not loading i guess cause its not in usb debugging mode. Been at this hours and i'm lost.
Any advice?