Related
Ok, so following on from the MeeGo thread, I have Ubuntu booting on the Nexus S using the same method and same kernel.
The Ubuntu image used is the HD2 Ubuntu image (v 0.3), loaded from a file on the internal memory (again, no flashing required - you can thank me later).
The touchscreen isn't yet working, but that's my kernel at fault. Will fix that with the MeeGo stuff.
If you want to try this yourself, first grab yourself a copy of Ubuntu for HD2, and take just the rootfs.ext2 file and drag it to your Nexus S (put it in a folder called 'ubuntu' - lowercase is important!).
Then use fastboot to boot the following image (or flash it to recovery partition if you're daring and know how dangerous that can be):
http://dl.dropbox.com/u/8657343/bootUbuntu.img
You will need to do one minor edit once the device is booted; you will see the screen output is very weird; ADB push the following file to /etc/X11/xorg.conf, and then reboot Ubuntu:
http://dl.dropbox.com/u/8657343/xorg.conf
If you're in any way interested, please click the thanks button! Otherwise, enjoy!
nice!
the next thing we'll need after getting the touch screen working
is to have a calling app daemon, and make sure internet works on both 3G and WiFi
nice, look same at Ubuntu Netbook Edition
What about Galaxy S?
Njcki said:
What about Galaxy S?
Click to expand...
Click to collapse
In theory the same stuff should work; I don't have a Galaxy S to test on or I'd try it. I don't know anything about the Galaxy S' bootloader, or how much the kernel would differ (I'm guessing not at all, since this is a stock Samsung kernel from the Android kernel source)
I did an article on my site http://www.android-ita.com/dev-port-di-ubuntu-sul-nexus-s/
Maybe some italian devs, will help you
Thanks for this, gonna have a play now
Why is it dangerous to flash the boot image to recovery? Isn't fastboot lower level than recovery, or have I got that wrong?
nice, thanks. trying this as soon as my wife gets off my phone.
Oh my god.. You are awesome good sir. Will give it a run when touch is up and running!
I'd love it to be run from Android....i dont want it natively, just to test it...booting for example from an android app
I would love to know if this will work on Epic 4G. I'm going to give it a shot to see what happens.
Great job
Could you give us the sources of your kernel ? Is it patched ?
Tyruiop said:
Great job
Could you give us the sources of your kernel ? Is it patched ?
Click to expand...
Click to collapse
There are no changes to the kernel at all so far. I changed the config file to enable VTs, that's it.
Ok, thank you, I'll try to build one myself
can this method be used to install android 2.3 on a phone running android 2.1,
especilly in the case when upgrading is difficult because of kernel and locked bootloader (like motorola devices) ? excuse me if it is a silly question, i'm not a coder.
would it be possible to make an app that re-boots into fastboot and runs the fastboot command. since we dont always have a comp available to run fasboot which makes this useless if your not at home, or have a laptop (in which case you dont need ubuntu on a phone)
works on Nexus One right now ?
--> ok I'm trying
It blocks on X screen of my nexus one.. before the classic bootanimation.zip
Someone have any idea about that ?
Ok, so I've got wifi working . Here is my solution. A little bit crappy but... hey... it's a start ! Also, I tried compiling the kernel with the module built in and it wont boot, and I don't know why ?
Howto get wifi :
1) Boot Ubuntu following stroughtonsmith indications
2) Download http://tyruiop.org/~tyruiop/wifi_nexuss_ubuntu.tar.bz2
3) push the vendor directory at the root. The path must remain (/vendor/firmware etc...) and the bcm4329.ko file wherever you want.
4) reboot under ubuntu
5) *optional, only if ifconfig -a doesn't show eth0* type insmod /path/to/bcm4329.ko
6) Type "ifconfig -a". An eth0 interface should appear. It's wireless. You can configure it with wpa_supplicant without a problem .
Uhm.. with Nexus One, Ubuntu blocks on X SCREEN (before the classic bootanimation).. Maybe something that I do is wrong ?
- Download HD2 Ubuntu
- mkdir ubuntu/
- put in ubuntu/ the fs on the archive I downloader
- put ubuntu/ in the SDCARD
- adb reboot bootloader
- fastboot boot bootUbuntu.img
Is it correct ?
hey did anyone manage to get the keys work with these kernels (KERNELS WITH KEYPAD DRIVERS AS MODULES) in any CWM build?
I try to load it using terminal like before but its not working
even the Gscript method is not working anymore, is there any other solution than restarting the device with KERNELS WITHOUT KEYPAD DRIVERS AS MODULES after each freez, the freez mostly happen after pressing the right option in the keypad or using setCPU
Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!
saobang3886 said:
Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!
Click to expand...
Click to collapse
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist
kerfooly said:
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist
Click to expand...
Click to collapse
OPP!
First, you should boot with kernel without modules keyboard, it easy to setting in first time. try setting all thing who make that build recommend!
Second, in stall Autostart and gScript app. copy autostart.sh to root of your sdcard. open terminal, remove old modules and copy autostart.sh to /data/opt like this post http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2
Then open restart keyboard script in your computer, open Gscipt in your phone, add new script, tip name is restart keyboard. Script like the file you open in computer!
after that, restart to window mobile, copy kernel with keyboard as module to your boot folder, replace old file, then reboot and it will work!
Well, after setting up all the scripts for loading and reloading of the kernel modules and then removing all kernel-modules of the old kernel (that without the drivers als module), you have to reboot your device. As part of the boot process, the new kernel modules are copied from the tar.gz-file, without deleting the old modules, this step will be skipped from the boot script.
So.
1. prepare all scripts
2. remove the old modules
3. boot the new 'KEYBOAD-AS-MODULES' kernel with it's module-archtive in place
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory ... the works quite nice and is much cooler that trying to press vol-down in the right moment ... i renamed it then to no_recovery.txt ... makes getting to recovery quite relaxed ...
Ciao
Kurt
Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.
hopsakee said:
Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.
Click to expand...
Click to collapse
Yep, here's the code from the init script that's in rootfs.img:
if [ -f /sdcard/npkboot/recovery.txt ]; then
so ... have fun with Android on your X1 .
Ciao
Klaus
Kurt Krummbein said:
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory
Click to expand...
Click to collapse
Ik works. I start into CWM. But the volume buttons still don't respond, and I need those to navigate through CWM.
Anyone a solution other than switching back to standard kernel without seperate modules?
when I type "sh /data/opt/autostart.sh" and press Enter, I get this error:
"insmod: can't read '/lib/modiles/microp-ksc.ko': no such file or directory
insmod: can't read '/lib/modiles/microp-keypad.ko': no such file or directory"
Can you help me?.
Where is kovsky keyboard modules????
I using ygge kernels with HoneyComb Froyo V.3
Hi All,
This is my first thread on this forum. Please help in resolving an error that I am facing. I could compile and link successfully franco kernel after downloading the source from franco's github!!
The only problem I face is with wifi. It displays error in the wi-fi option!! This is some what similar to what we used to get in the initial version of gingerbread kernel what Franco had made earlier!! I get the same error even with the stock GB source code of LG or with paulo's kernel source!!! Strange!!!!
The wifi driver(bcm4325) seems to be same except for some tweaks to the original GB source(In the case of Franco's)!! In either case, I am getting the error. The only difference I see is that of the compiler option -Ofast(Optimization option) was used by Franco while since I updated to the latest version of gcc, I do not get the -Ofast option!! So it uses the -Os option instead!!
Error is(logcat):
D/WifiService( 1726): setWifiEnabledBlocking : Country code is COM
E/WifiService( 1726): Failed to load Wi-Fi driver.
Same compiling options were used to compile both zImage and modules?? What could be wrong here? I am not sure what could be wrong here!!! Can anybody help me on this??
Thanks in advace.
I get this on sense too
(but I replaced all that Android wifi stuff,so on Sense,its wierd )
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App
dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!
franciscofranco said:
I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App
Click to expand...
Click to collapse
Yup franco. I copied to modules and then signed it with command:
"java -classpath testsign.jar testsign port.zip signed-port.zip"
I really can't understand why this is getting failed as the same compile options were used for both zImage and wireless.ko!! Rest all works fine except the wifi error!!! The idea i think is as long as all the executables are of same signature, then it should work fine, right?? I am confused on what could be the problem!!!
dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
Today I will try with other compile options, either O1, O2.... etc.
Strange thing is that I face this problem with all other available kernels also!! Like for ex., original GB source from LG, paulo's kernel!! All of it!!
shashi_hv said:
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!
Click to expand...
Click to collapse
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.
dr.notor said:
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.
Click to expand...
Click to collapse
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!
shashi_hv said:
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!
Click to expand...
Click to collapse
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko
dr.notor said:
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko
Click to expand...
Click to collapse
I know that notor!!!
I copied the tun.ko and wireless.ko to the appropriate folder and built the zip file which i flashed!!
The problem is very weird. I see the file wireless.ko if I browse thro' file manager. Even when i press tab in busybox, wireless.ko gets auto populated or even the ls command lists it!!
It is much more weird that if I tried to do insmode ....../tun.ko, i get the error as 'exec format error' but a 'no such file' for the wireless.ko!! Though I flashed both these of these!!
You know, go wipe the files in /system/lib/modules and flash your kernel and modules from the SAME KERNEL you have compiled.
Also, it is insmod, not insmode and generally if you are posting something, copy and paste the exact output of a command instead of telling us stories about what the output says.
Yup thats what i was thinking too.. i would wipe and try copying it once again.
Definitely i would have shown you the screen shots.. but i am not in a position to grab those and paste it here, as i am in office right now.. but the point is i understand some of linux system and familiar wirh it!!
I tried to create and flash the zip the standard way thats available on net and it did not worked!! Thats the point!! So wanted to know am i missing anything!!
Sent from my LG Optimus One P500 using XDA Premium App
Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...
dr.notor said:
Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...
Click to expand...
Click to collapse
I tried this!!!
1. su
2. rm -f /system/lib/modules/wireless.ko
3. rm -f /system/lib/modules/tun.ko
Now the files were not there in the directory. Flashed the same zip file which I used earlier and found the wireless.ko and tun.ko in the same path!!! But still the problem prevails!!
Just to confirm once again that I indeed copied the compiled wireless.ko and tun.ko and built the zip file!! No problem in that!!!
Why do not you try to do insmod of any existing file in the modules path and report what error you get?? I think even you should get the same error even in your phone too!! I tried this command on an already existing libra.ko in the same path and got the same error!!!
for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...
andy572 said:
for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...
Click to expand...
Click to collapse
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.
dr.notor said:
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.
Click to expand...
Click to collapse
On a different note, can anybody tell me who will load the wireless.ko and tun.ko at boot time? I mean is there any kind of scripts like the init.rc or any other *.sh scripts under /system/etc?
I tried to see in the init.qcom.wifi.sh script, but its based on the property 'wlan.driver.status'!! I dont see this property under getprop command, but added one using setprop, but no success!!!
Suggestion: restore the stock init **** and leave it alone. There is absolutely no need to mess with that to get WiFi working on any ROM. Others, like tun.ko, you need to load manually via initscript or whatever. Go fix your kernel compile and it will just work.
Optimus Toolkit 6 in 1 v-1.1.1 - Linux
After a few month programming here you have this 6 in 1, we say that it is the counterpart in Linux of the "All in one", though it seems.
In you program have included 6 applications essential for the day-to-day management of Optimus, partitions with the new LG-ICS configuration or the former LG-GB.
Backup/restore of the whole system, and also of the SDs, both internal and external, and stores them in ZIP format.
The program includes:
Uncompress KDZ
Unpacking AP
Backup
Restore
Flash ROM (NVflash)
Rooted
Three languages, Spanish, English and German, I hope that it will soon translate into French, Italian and Portuguese
Click to expand...
Click to collapse
An example of use:
You have a ROM format KDZ and does not the Windows program rather than failing, because well, you copy the kdz within the kdz_folder folder, run the Optimus_Toolkit 6 in 1 and choose option 1- UnPack KDZ.
After a few seconds you have the AP and CP files to Flash with Smartflash. Oh, that doesn't want to boot windows?, no problem, use option 2.- UnPack AP, and then option 4.-Flash ROM for flashing by NVflash ROM KDZ just unpack.
But before Flash want do a backup of the system, as with the 3.- Backup/Restore option, this is in Optitool 2, backup/restore DATA, SYSTEM, etc.
Click to expand...
Click to collapse
The operation is very intuitive, just follow the instructions on screen.
The program does many things, and others will in the future.
I hope that you go reporting if you detect a fault.
Changelog
V-1.1.1
- Support for German language, thanks to Cupacabra - in this version you can change language from the main menu
V-1.1.0
- Support for any language. I have included a language file that you can go adding translations to other languages - error correction. -Added you fixing of current route to run on MAC (by drag0njoe) - the only language menu exits the first runs, the language selected is memorised.
V-1.0.2 R
- UnPack KDZ - now is can copy more than one KDZ within kdz_folder/, the program will create a menu with the KDZ that is inside the folder. - Added limits so that an opcionque can not be pressed does not exist. - Automatically adapts to options with one or two figures.
- Flash ROM - remodelling of the Flash ROM menu and correction of minor errors
V-1.0.2
- Menu flasher - Two new options, [5] Flash RECOVERs and [9] Flash KERNELs. - Alternative kernels copied them to kernel folder / and the recoverys to the recovery folder. - The program will detect the kernels and recoverys withi
V-1.0.1
- Correction on menu flashing, by drag0njoe
- Added flashing Kernel, by drag0njoe
V-1.0 stable
- Fixed bug when unpacking AP
- Fixed bug when unpacking KDZ
- Fixed bug in detection of ROM
- English version, corrected spelling errors.
- Revamped graphic look.
Click to expand...
Click to collapse
CREDITS
• [email protected] introduced the 'LGExtract.exe'. the encrypyted/compressed kdz can be extracted/decrypted to AP.bin/CP.fls by LGExtract.exe
• AP.bin extractor (win32/linux)
• xonar_ made BIN/FLS extractor
and release source
• (original Java version by xonar_)
• (win32 C port by navossoc)
• [TOOL] LGExtract 0.2.1 by navossoc
Click to expand...
Click to collapse
DOWNLOAD
Optimus_Toolkit_6-in-1_V-1.1.1.tar.gz - 25.64 MB
Nice bro,
It's good to have another alternative toolkit for linux users.
New version corrected, improved and stable
Thanks for your work and collection, as a regular linux user it's very useful for me.
I have some recommendations which are might be improve the linux users experience.
I suggest you to use some kind of compression which is takes care about the extended *nix attributes, like the executable bit. For example, the 7zip and the tar.gz will be perfect.
But if you feel better, that's no problem using the proprietary rar format, in this case I have to execute these commands:
Code:
chmod +x scripts/*.sh
chmod +x tools/7za
chmod +x tools/adb_linux
chmod +x tools/adb_mac
chmod +x tools/cabextract
chmod +x tools/extract
chmod +x tools/nvflash
Or, if you think you can implement such a thing like these into your menu.
Not a big problem, just an idea how to make your work more user friendly.
The other, which is also just a minor thing, in the tools/flash_en.sh I found that in the Opti nvflash command line there is a tools/fastboot.bin, which is not corrected to the fastbootICS.bin file, so the nvflash of course does not work with.
Lastly, please consider about integrate the recovery from pengus (CWM non-touch) and tonyp (CWM touch and TWRP soon), and to implement the kernel flashing only (ex. for the kernel testers). I attached my version of your flash_en.sh with Flash ROM option 8 (because I am successfully stucked on boot with a new kernel ).
Thank you for your work!
excellent useful tool!
drag0njoe said:
Thanks for your work and collection, as a regular linux user it's very useful for me.
I have some recommendations which are might be improve the linux users experience.
I suggest you to use some kind of compression which is takes care about the extended *nix attributes, like the executable bit. For example, the 7zip and the tar.gz will be perfect.
But if you feel better, that's no problem using the proprietary rar format, in this case I have to execute these commands:
Code:
chmod +x scripts/*.sh
chmod +x tools/7za
chmod +x tools/adb_linux
chmod +x tools/adb_mac
chmod +x tools/cabextract
chmod +x tools/extract
chmod +x tools/nvflash
Or, if you think you can implement such a thing like these into your menu.
Not a big problem, just an idea how to make your work more user friendly.
The other, which is also just a minor thing, in the tools/flash_en.sh I found that in the Opti nvflash command line there is a tools/fastboot.bin, which is not corrected to the fastbootICS.bin file, so the nvflash of course does not work with.
Lastly, please consider about integrate the recovery from pengus (CWM non-touch) and tonyp (CWM touch and TWRP soon), and to implement the kernel flashing only (ex. for the kernel testers). I attached my version of your flash_en.sh with Flash ROM option 8 (because I am successfully stucked on boot with a new kernel ).
Thank you for your work!
Click to expand...
Click to collapse
I will take into account the compression, I will use the native tar.gz.
On line 101 of your flash_en.sh it refers to tools/recovery_ics-20121230.img
That recovery is that?
I'm hoping to TWRP, is a recovery which I like very much, I tried to adapt it to ICS based on modifications made by Stefan in the CWM, but I only got a tremendous brick ), is that something different from CWM works
If you think of any suggestions, they will be well received.
Stefan Gündhör said:
excellent useful tool!
Click to expand...
Click to collapse
Blessed are the eyes that you read
Homero2 said:
I will take into account the compression, I will use the native tar.gz.
Click to expand...
Click to collapse
Thank you! Maybe the newer Linux users also like it.
Homero2 said:
On line 101 of your flash_en.sh it refers to tools/recovery_ics-20121230.img
That recovery is that?
Click to expand...
Click to collapse
Yes, this is the latest recovery from pengus77, I am using his ROM, so I think this one is better for me.
Homero2 said:
I'm hoping to TWRP, is a recovery which I like very much, I tried to adapt it to ICS based on modifications made by Stefan in the CWM, but I only got a tremendous brick ), is that something different from CWM works
If you think of any suggestions, they will be well received.
Click to expand...
Click to collapse
I tried it too, the result was useless, so I really understand you
Maybe sooner or later somebody has some time to make it for the ICS layout too.
Thank you again for your excellent work, it is really useful for me!
NEW V-1.0.2
- Menu flasher - Two new options, [5] Flash RECOVERs and [9] Flash KERNELs. - Alternative kernels copied them to kernel folder / and the recoverys to the recovery folder. - The program will detect the kernels and recoverys withi
Can't get it working.
Tried running it on a mac but it ends with an End of process after selecting a language:
Escoja una opción/Type an option: [1-2,X]2/Users/ruslanmirsalihov/Desktop/Toolkit_ICS-Root_Stock-v-1.0_by_Homero/root: line 18: tools/en.sh: No such file or directory
logout
On ubuntu it says it was unable to determine my phone.
Any help?
If the "unable to determine my phone" means that when you start the flashing process you get "Nvflash started" "USB device not found" in Ubuntu, I think the problem is that you using wrong cable, or you not plug the phone into the USB while both of the volume keys pressed. Please provide exact error message and the exact menu option you used in order to get your problem solved.
About the mac you need to start Terminal from Utilities and start the script from here.
Or, alternatively, I attached a fixed menu which is working with double-click, just download and replace it your menu file with the attached one (there is a new function which doing the same thing, cd'ing into the script directory, so I just made nearly nothing, but working in linux and mac, and should working in cygwin too.)
But note that, in mac you cannot use the flashing options because of AFAIK there is no nvflash for mac. But you can use the others, such as the rooting and the back up with ADB is working.
This function (fixpath). Should we put it in the script, or just on the menu?
New version 1.1.0, with support for multiple languages, the languages are included in a separate script file.
The program memorizes the selected language, and the language menu will not appear any more
New version, with new options and I think and hope that all errors are corrected.
THanks
At last playing with my android P990 without boot Windows thanks !!!
Does this work with the P880 (Optimus 4X) as well, or is it specific to the P990?
nevermind.......
Phew, search how to nvflash!!!
Sent from my LG-E610 using xda premium
SuperSkill said:
Phew, search how to nvflash!!!
Sent from my LG-E610 using xda premium
Click to expand...
Click to collapse
Newbie here trying to flash my o2x however I am not able to enter APX mode I guess. I've removed the battery and I hold down the volume up/down and plug into USB but nothing appears.. it just says no USB devices were found? Anyone else have this issue, not sure what I am missing here but pretty hard to do anything if device is not recognized. thanks.
archish said:
Newbie here trying to flash my o2x however I am not able to enter APX mode I guess. I've removed the battery and I hold down the volume up/down and plug into USB but nothing appears.. it just says no USB devices were found? Anyone else have this issue, not sure what I am missing here but pretty hard to do anything if device is not recognized. thanks.
Click to expand...
Click to collapse
Try the all in one tool kit by spyrosk
It has the menu for installing the drivers which you need
Install the apx drivers
Sent from my LG-P990 using xda premium
First of all, many thanks for 4pda members.
It's time to post new thread for Lollipop.
This is for Kitkat me572c users.
(I can't make link so just copy the url)
● Lollipop firmware (UL-K007-WW-12.14.1.12) with root
Code:
mega.nz/#!LwJ3VBxK!4V4Ay-RzLS8x609zvyWL8IlcgI3xxfLcSqZ3gZkc52Q
● Install-Recovery.rar
Code:
mega.nz/#!C5ghzL6R!GR0WgLCumy6a429kB0ZjQOMxjPSylz07fVnHtKVm8ng
● ADB Driver
Code:
mega.nz/#!YAlxVbYS!7xfADRLuvcyO1GxRHtre3_e1TaVPmtIykqGbKCzUkkk
1) Can only be set on 4.4.2 (Kitkat). If you have already installed Lolipop, you must first revert to Kitkat. The computer should be installed ADB driver for the tablet and the tablet is turned on for the USB debugging. (no need to backup Internal memory. every data remain. but just in case, back up your data.)
2) Connect powered tablet to the computer. Download the firmware and rename it MOFD_SDUPDATE.zip, copy to the root of the memory card(MicroSd card) of the tablet. Download the archive Install-Recovery.rar and unpack it on your computer.
3) Run Install-Recovery.cmd, after the black command window turns up, volume buttons to select SD Download and power button for confirm. This will start the process of firmware.
Can anyone post instructions (in English hopefully because I'm lingual challenged) on how to revert back to KitKat if you've already upgraded to Lollipop? I didn't think that was possible...
Thanks so much!
I did a rough translation of the steps for downgrading in this thread. I haven't tried it myself, though, so I can't guarantee success.
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
does this work on ME176CX??
redhk886 said:
does this work on ME176CX??
Click to expand...
Click to collapse
I wouldn't try it. The process involves loading ROM images made specifically for the ME572C..
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
lexridge said:
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
gmaxjp said:
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
Click to expand...
Click to collapse
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
lexridge said:
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
Click to expand...
Click to collapse
Recovery is not CMW/TWRP, perhaps modified from stock.
Yep, What I did were execute series of command lines manually and crossing my fingers for several times
I'm expecting that will work in RPM based distros.
confirm, successful update using links/directions here.
kk stock rooted -> custom rooted 5.0 as above
yay!
significant speed increase in the ui animations, etc.
...google probably did a lot of support work for the moorefield
SacredMyths said:
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
Click to expand...
Click to collapse
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
gmaxjp said:
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
Click to expand...
Click to collapse
Good , no problem.
Now the only issue I'm having is a few emojis are black D:
where can i download the xposed apk for this model...
javcarbe said:
where can i download the xposed apk for this model...
Click to expand...
Click to collapse
Xposed Installer for Lollipop http://is.gd/jSVa1Q Use latest rev.
Since is a zip
How can I install a zip if I don't have a twrp recovery
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
i unzip run the bat but doesnt work i need an instructions to do it manually
C:\Temp\XposedForZenFoneLollipop_20150607>InstallXposedFramework.bat
'
'
' Connecting ZenFone ..
'
'
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
'
'
' Pushing files ..
'
'
error: device not found
error: device not found
'
'
' Installing Xposed Framework,
' please GRANT permission for this script on your phone !
'
'
error: device not found
error: device not found
error: device not found
'
'
' Done, rebooting ..
'
'
error: device not found
Instructions fail with the recovery not being able to mount the SDCard for some reason.
But the zip sideloaded just fine.
Thanks.
Also, any idea what recovery is compatible?
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
javcarbe said:
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
Click to expand...
Click to collapse
I guess you just have to turn on usb debugging, connect your device to your pc and execute InstallXposedFramework.bat and InstallXposedInstaller.bat
I did and nothing