Related
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.
Hey all!
EDIT:
overscrollglow_reboot.zip - V20C reboot item and oversroll glow.
overscroll_glow_v20e_by_trapacska.zip - V20E for NEW ROM!!! OverScroll Glow only! and! flashable with cwm.
oglow_and_reboot_v20e_by_trapacska.zip - overscroll glow and reboot, V20E, flash with CWM
after flashed via cwm, first startup may take longer.
reboot item only in progress...
and flash build.prop edits via cwm too.(with selectable opts)
And very important! Everything else is working without framework mod, lockscreen or smooth mod. If you only want stock lockscreen, you don't have to flash overscrollglow, just edit build.prop.
I just made mods for (currently) V20C gingerbread.
- Overscroll glow & reboot item in power prompt
- default AOSP lockscreen
- disable shutdown animation
- disable boot animation, power on or off sound
- some performance-boost
1. Overscroll Glow&Reboot Item(because both is in framework.jar)
if you push framework.jar only to /system/framework/, reboot item will not show in power prompt.
otherwise just push android.policy.jar and framework.jar to /system/framework/
1.1 Go to ClockWorkModRecovery
1.2 Mount /system in mounts and storages option.
1.3 in adb shell cmd, just "adb push framework.jar /system/framework/"
"adb push android.policy.jar /system/framework/"
1.4 "adb reboot"
-first boot will take longer
2. Default Aosp LockScreen
2.1 Go to ClockWorkModRecovery
2.2 Mount /system in mounts and storages option.
2.3 use "adb pull /system/build.prop"
2.4 edit build.prop file and change
Code:
user.feature.lock_andy=true to
user.feature.lock_andy=false
2.5 then save and "adb push build.prop /system/"
3. Disable ShutDown animation
3.1 Go to ClockWorkModRecovery
3.2 Mount /system in mounts and storages option.
3.3 use "adb pull /system/build.prop"
3.4 edit build.prop file and change
Code:
user.feature.lgpoweroff=true to
user.feature.lgpoweroff=false
3.5 then save and "adb push build.prop /system/"
4. Disable BootAnimation, power on or off sound.
-to disable bootanimation
4.1 Go to ClockWorkModRecovery
4.2 Mount /system in mounts and storages option.
4.3 use "adb shell rm /system/media/bootanimation.zip"
-to disable power on sound
4.4 use "adb shell rm /system/media/audio/poweron/PowerOn.mp3"
-to disable power off sound
4.5 use "adb shell rm /system/media/audio/poweroff/PowerOff.mp3"
5. Performance boost
5.1 Go to ClockWorkModRecovery
5.2 Mount /system in mounts and storages option.
5.3 use "adb pull /system/build.prop"
5.4 edit build.prop file and ADD lines to end
Code:
debug.sf.hw=1
windowsmgr.max_events_per_sec=60
5.5 and change
Code:
dalvik.vm.heapsize=48m to
dalvik.vm.heapsize=32m
5.6 then save and "adb push build.prop /system/"
windowsmgr.max_events_per_sec=60 -for faster and smoother scrolling(in lists or in launcher)
debug.sf.hw=1 -it shares with all of services and apps to use GPU instead of CPU for animating.
dalvik.vm.heapsize=32m -it's good enought for everything, and you will have some more free ram.
for developers, if you only want reboot item, just say and i will share my sources and i give you my source. and more if you want, i can tell you how to change reboot item icon. and don't forget to attach my name into your changelog
if you like my work please press Thanks.
Awesome job, I'm still sticking to CM7, but congrats anyway
trapacska said:
debug.sf.hw=1 -it shares with all of services and apps to use GPU instead of CPU for animating.
Click to expand...
Click to collapse
Nope, just disables all GL extensions, making alot of games not work.
with debug.sf.hw=1 flashplayer is smoother and muffin knight too...
no lag at all when playing (all game works for me) ^^ nice found thx
If this is the same flag used by VorkKernel time ago....it has been massively tested by community and then deprecated...as it had no real gain and only issues
Sent from my Optimus 2X using XDA App
kiljacken said:
Nope, just disables all GL extensions, making alot of games not work.
Click to expand...
Click to collapse
maybe for you, but i know all of sources in framework and libs, and I know that what does mean. just try debug.sf.hw=0 and you will se the difference everything will be flickery, from games to launcher.
trapacska said:
maybe for you, but i know all of sources in framework and libs, and I know that what does mean. just try debug.sf.hw=0 and you will se the difference everything will be flickery, from games to launcher.
Click to expand...
Click to collapse
Show me the source then. We've tested it with vorkKernel, and no real performance boost was experienced. Only placebo
EDIT: Hmm, actually does something. Not just a whole lot I think
kiljacken said:
Show me the source then. We've tested it with vorkKernel, and no real performance boost was experienced. Only placebo
EDIT: Hmm, actually does something. Not just a whole lot I think
Click to expand...
Click to collapse
Source for overscroll glow, and reboot. others are searched via google,and i tested. these are working. its 100%. if you think it is placebo, just dont use that placebo. everybody can decide to use it or not. thanks.
It's good. Thanks
Its possibble to place "reboot recovery" ?
Good job, i include in my rom
Sent from my LG-P990 using Tapatalk
Anyway to get flashable zip pls?
hey, sorry if this will be once again a noob question, but how exatcly do i get into adb shell ?
if i type "adb shell" in cmd when my phone is plugged in the PC (phone is in cwm recoevry, system mounted), but cmd sais its an unknown command.
do i need some drivers or how is it ?
thanks
xilw3r said:
hey, sorry if this will be once again a noob question, but how exatcly do i get into adb shell ?
if i type "adb shell" in cmd when my phone is plugged in the PC (phone is in cwm recoevry, system mounted), but cmd sais its an unknown command.
do i need some drivers or how is it ?
thanks
Click to expand...
Click to collapse
You need to install android SDK and if you are on windows LG drivers. Google will rapidly lead you to how to make it..
Topogigi ROM 1.3
Ok i am on 20e. I know the first post mentions the package is for 20c but I like living dangerously. Anyway, to save 20e testers the hassle, it doesn't work. So err..any chance we can get this working on 20e? I really want the aosp lockscreen. Thanks!
bullyfrog said:
Ok i am on 20e. I know the first post mentions the package is for 20c but I like living dangerously. Anyway, to save 20e testers the hassle, it doesn't work. So err..any chance we can get this working on 20e? I really want the aosp lockscreen. Thanks!
Click to expand...
Click to collapse
yes don't work =(
Ill try to create this stuff for v20e too
ok, but i plan to make these mods, if official GB will be released.
trapacska said:
ok, but i plan to make these mods, if official GB will be released.
Click to expand...
Click to collapse
Ok
I think that edited XML's from this rom can be used on the "final/official" GB rom
bullyfrog said:
Ok i am on 20e. I know the first post mentions the package is for 20c but I like living dangerously. Anyway, to save 20e testers the hassle, it doesn't work. So err..any chance we can get this working on 20e? I really want the aosp lockscreen. Thanks!
Click to expand...
Click to collapse
hey! to use stock lockscreen, just edit your build.prop
Code:
user.feature.lock_andy=true to
user.feature.lock_andy=false
my framework.jar and android.policy.jar ONLY for reboot item and overscroll glow.
everything else is working without framework mod.
trapacska said:
hey! to use stock lockscreen, just edit your build.prop
Code:
user.feature.lock_andy=true to
user.feature.lock_andy=false
Click to expand...
Click to collapse
Thanks! Done. Never knew the the aosp lockscreen was already present
So.. is anyone making it compatible with the 20e release, i realy liked the mod ;-)
Good day.
I have unrooted HTC incredible S (4.0.4, kernel version 3.0.160-gfa98030) and when I have tried to install tun.ko with "Tun.ko Installer" - an error occured : "Cannot find a compatible tun module for Your device! Please try again later"
I looked for "tun.ko" in that forum and searched only this article http://forum.xda-developers.com/showthread.php?t=1327969&highlight=tun+ko , but I am not real linux user.
Where could I get tun.ko?
Thank You
This module is kernel specific, it must include the module when it is compiled.
Nonverbose said:
This module is kernel specific, it must include the module when it is compiled.
Click to expand...
Click to collapse
This is obvious. But maybe anyone already have thi module?
beelesnik said:
This is obvious. But maybe anyone already have thi module?
Click to expand...
Click to collapse
Really? If it's that obvious then it should be even more obvious that you need to root your phone and put a custom kernel on it that includes the tun.ko module. The stock kernel was not built with this module.
Nonverbose said:
Really? If it's that obvious then it should be even more obvious that you need to root your phone and put a custom kernel on it that includes the tun.ko module. The stock kernel was not built with this module.
Click to expand...
Click to collapse
Could I build tun.ko following http://forum.xda-developers.com/showthread.php?t=1327969 ?
I have downloaded kernel source from htcdev and compiler for arm too.
Is this working method?
beelesnik said:
Could I build tun.ko following http://forum.xda-developers.com/showthread.php?t=1327969 ?
I have downloaded kernel source from htcdev and compiler for arm too.
Is this working method?
Click to expand...
Click to collapse
First you should check that you even need tun.ko built as a module. According to the defconfig in the source code, tun is already built into the actual kernel itself
Code:
1107 CONFIG_TUN=y
Also if you are going to root (which you will have to do anyway, to flash the new kernel you plan to make with the tun.ko) you might find it easier to use a kernel where this is already configured.
Nonverbose said:
First you should check that you even need tun.ko built as a module. According to the defconfig in the source code, tun is already built into the actual kernel itself
Code:
1107 CONFIG_TUN=y
Also if you are going to root (which you will have to do anyway, to flash the new kernel you plan to make with the tun.ko) you might find it easier to use a kernel where this is already configured.
Click to expand...
Click to collapse
Thanks a lot for Your advices.
My phone has HBOOT 2.02.002 and many ways to root it are useless.
I have got a root with such instructions In English:
1) Download the archive 4EXT.zip
2) Extract the root of drive C
3) Connect to the computer IS in charge mode enabled mode "debug USB" (!).
4) At the command prompt, go to the folder with the files from the archive: cd c: \ 4EXT
5) At the command prompt, enter the adb reboot bootloader
6) The phone will reboot into bootloader
7) At the command prompt, enter the fastboot flash recovery recovery.img
8) Modified Recovery please!
9) In the root of the card copy the file Superuser-3.0.7-efgh-signed
10) Hold the power button and volume down
11) In the menu, select the item Recovery - phone will reboot into a modified Recovery
12) Select Install Zip and set Superuser-3.0.7-efgh-signed
I only use Superuser-3.1.3.
But in the end of this instructions are strings "You get Root. But You cannot to flash custom biulds - you should lower version HBOOT!"
And now I am not sure could I use custom kernels?
What custom build with tun.ko do You suggest? Is there simple way to flash it to my phone?
To root your phone, best guide would be from lynt in general section on which you don't gain s-off.
To get s-off follow nonverbose's guide(general section)
Easy and perfect ways!
Sent from my vipervivo1.0.0-Google Now
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
nsboot - NinjaSwag Bootloader/Installer
WILL REPLACE smackme2 and kexecboot!
Source: https://github.com/willcast/nsboot
Kernel source: https://github.com/willcast/ubuntu-kernel-tenderloin/tree/kexec (kexec branch, not Ubuntu)
Binary: https://docs.google.com/file/d/0B4WUjKii92l2Ukl4TE1EM1pjTDg/edit?usp=sharing
I have been working on this for about 2 weeks...
Features
Touch screen based interface
Able to boot kexec kernels
Able to install Android and Native Linux OSes, kexec tar files, and uImage kernels
Able to back up entire volumes as .tar.gz (with permissions & ownership)
Directly compatible with smackme and kexecboot config files
Can replace moboot entirely with the touch of a button.
Integrated file browser
Software touch keyboard available
Haptic feedback
uImage is < 4 MiB
Loads 3x faster than kexecboot
Has integrated ADB server so you can push and pull files from any mounted FS, or run a local shell.
Known issues so at this time
Colors are messed up in included TWRP recoveries
Things still to be tested
nothing as of now
kexec images for reference
webOS 3.0.5: https://docs.google.com/file/d/0B4WUjKii92l2WU9fdkNZa0V5NUk/edit?usp=sharing
Arch Linux ARM: https://docs.google.com/file/d/0B4WUjKii92l2YWRFUWJoMkpXRzg/edit?usp=sharing
Ubuntu: https://docs.google.com/file/d/0B4WUjKii92l2MXlEVmxQUHoyUzg/edit?usp=sharing
Slackware: https://docs.google.com/file/d/0B4WUjKii92l2MnRwMGRyTmRQcW8/edit?usp=sharing
Fedora untested: https://docs.google.com/file/d/0B4WUjKii92l2S3pVUkZNNzNSQUU/edit?usp=sharing
Android 2.2 Froyo: https://docs.google.com/file/d/0B4WUjKii92l2d2cwQlBtVVd4aGM/edit?usp=sharing
Android 2.3 Gingerbread: https://docs.google.com/file/d/0B4WUjKii92l2UGtETzBwNnNvckU/edit?usp=sharing
Android 4.0 Ice Cream Sandwich: https://docs.google.com/file/d/0B4WUjKii92l2UDc2cVZ2TjBWM2s/edit?usp=sharing
Android 4.1 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2d3g0U3p6c0l4NFk/edit?usp=sharing
Android 4.2 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2dlFzcFBacThSVXc/edit?usp=sharing
How to test
Code:
novacom boot mem:// < uImage.nsboot
To install, copy it to /boot (/dev/mmcblk0p13). It can also install itself if you put a copy of it on the SD card, and go Installer menu -> install uImage and navigate to it.
Screenshots are attached.
YouTube demo of a earlier version with only the boot working and a simpler menu: http://www.youtube.com/watch?v=0oQhSa4sqPU
Updates:
All OSes now boot (At least on my TP.)
Those which have had their kexec archives revised on GDrive since the first post are in italic.
Android 4.2
Android 4.1
Android 4.0
Android 2.3
Android 2.2
Android Recovery (included with all Android kexec archives)*
webOS
Ubuntu
Slackware
Arch Linux
Fedora
* The colors are still out of whack in recovery. It's mostly unneeded at this point with Built-In ADB support and zip installation, but I included it for those who want its more obscure or advanced features, or are more comfortable with its UI. Testing it specifically is appreciated because I don't have any plans to develop a test suite for it.
Compatibility list
Android ROMs
4.2
There is currently an issue with installing later Android 4.2 ROMs. The following 4.2 ROMs will install and boot:
Evervolv nightly 05-15-2013
The following 4.2 ROMs get stuck in a fairly serious bootloop (logcat shows at least surfaceflinger, mediaserver, and zygote segfaulting). I have tried different kernels.
CM 10.1 unofficial nightly 06-02-2013
Schzoid 2.0 nightly 04-23-2013
Other 4.2 ROMs are untested.
4.1
The following Android 4.1 ROMs have been tested and work:
JCSullins' CM 10 preview, 12-16-2012
Schzoid 1.2, 03-06-2013
4.0
The following Android 4.0 ROMs have been tested and work: CM 9 nightly, 01-06-2013
2.3
The following Android 2.3 ROMs have been tested: CM 7 Alpha 3.5
Issue: When the screen is woken up in CM7, nothing shows up on the display. The backlight does turn on.
2.2
The following Android 2.2 ROMs have been tested and work: my Froyo kang, version 0.4 and 0.3 (0.4 is on google drive on top of 0.3)
Native Linux
Ubuntu
The following Ubuntu releases have been tested and work: Ubuntu 13.04 final, Ubuntu 12.10 final.
Others are welcome to be tested, but I will probably not take issue with anything before 12.10 beta not working.
Arch Linux
Arch Linux boots, and seems to work. Wi-Fi has not been tested.
Slackware
Slackware boots and seems to work. Wi-Fi and Bluetooth have not been tested.
Debian/Bodhi
I am unable to locate any tar.gz archives to test for this distribution, nor a kernel of any sort. If anyone wishes to step up and send one to me or even host it, I would be grateful and also I'd probably get it booting within a day.
Fedora
These haven't yet been tested. They are theorerically installable with the new "tar.gz to custom LV" feature, but I would need to find a way to free more space on my TP to install them (my media partition is currently about 10 GB, 6 GB used for music, and 2.5 GB used for testing files.
Thank you
Good Job! I will test it tomorrow.I have been looking forward to ArchLinuxArm for a long time.Thank you.
Looks really good, I'll give it a spin.
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Same here! But i Can Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
After I made the webOS image, I noticed that it's a bit... finicky. Just reboot from nsboot main menu. Then try loading webOS again.
If you need to get to recovery mode, the way to do it is to reboot like that, holding down VOLUME UP.
imapjonny said:
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you installed CM to the logical volumes named /dev/store/cm-*, you need to back up and reinstall it from nsboot. As for booting CM recovery from nsboot, if you haven't done that yet, a feature I put in already lets you make .tar.gz archives from volumes (including Android ones.) I just enabled the extraction of them to Android volumes (used to only allow others), so you could use that to "move" your Android.
Minimum System Sizes to use for android partitions:
2.2 (froyo): 256MB
2.3 (gingerbread): 320MB
4.0 (ics): 320MB
4.1 (jellybean): 450MB
4.2 (jb mr1): 480MB
Step by step instructions:
Upgrade nsboot. Just released a new one. Either scp/adb it from a running OS or redo the install procedure except for the replace moboot part, after downloading it again.
Get the kexec tarchive for your android version onto the SD card. You could scp or adb push it. If needs be, find your old Android recovery image, and boot it via novacom:
Code:
novacom boot mem:// < uImage.ClockworkMod
Boot nsboot.
Go to Utilities - create volume tarchive.
Select "cm-system". Name the backup "System".
Repeat last two steps for "cm-data" if you want to keep your data partition. I don't recommend backing up "cache".
Go to Utilities - create volume set.
Name the new Volume Set depending on your Android/CM release: Use the names "android22", "android23", "android40", "android41", or "android42".
Format the new volume set: go to Utilites->format volume set, and select it. Click Confirm/OK.
After the set is created, go to Installer menu -> install .tar.gz to existing volume. Navigte to /mnt/media/nsboot/backups. You will find your two backups. Select "System" to restore to "androidXX-system", depending on the version you just created. Make sure you use a big enough size - see above table.
Repeat the last step for data, if you made such a backup.
You now need to find the kexec archive you copied to your SD card (it's mounted in /mnt/media.) Install it. If you chose the right volume set name, it will work.
Reboot or rescan boot items and you should see the Android version in your boot menu. Tell me if it doesn't work.
If it does work, go to utility menu -> delete volume set and select "cm" as your set. This will remove the old cm set, and leave the new androidXX one.
After that, if it did work, go to utility menu -> reclaim media space to get back any lost space for your media/sdcard partition.
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
imapjonny said:
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
So when you guys who are having trouble with webOS try launching it, do you get to the screen that says 'please wait, booting...' or the HP logo that pulsates? Where does it reboot? I'm thinking I might have uploaded an old, non-workable tar file for that OS.
FYI: After testing every boot option, I discovered a problem with Android 4.1 (only 4.1). I'm looking into it.
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
superboy123 said:
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
Click to expand...
Click to collapse
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
castrwilliam said:
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Click to expand...
Click to collapse
Okay everything is working well with this new tar.
Sent from my GT-I9300 using xda app-developers app
Make sure your pad is fully charged. I have had problems before during partially charged tp
John 3:16
castrwilliam said:
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
Click to expand...
Click to collapse
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Okay, try the volume up button. If that doesn't work, try holding power + volume up + home (rebooting it), ignoring the boot loop. I only said to delete one uImage... wait, uImages are the only files you deleted, not anything else in /boot, right?
Do you ever see the HP logo?
If you touched "boot.bin" (among certain other possible files in /boot) you'll probably need the debrick program. This isn't nsboot's fault... link to program is here: http://forum.xda-developers.com/showthread.php?t=2010270
If you use that program, follow its instructions TO THE LETTER, if there is anything you need clarification on, ask here - I've never had to use it, but I've heard of it fixing TPs that don't even show anything on the LCD. That said, if something goes wrong with it, it has the opportunity to make the problem far, far worse.
castrwilliam thank you for your work
Rock on dude
loving your work man keep it up dude:good:
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Is the pad fully charged? I would strongly suggest letting it charge for twenty four hours.
P.S. don't panic
Sent from my Galaxy Nexus using Tapatalk 2
Is it possible to install Ubuntu 13.04 and 12.10 at the same time?
Sent from my GT-I9300 using xda app-developers app
I am a little confused on the install process, would you mind elaborating.
Sent from my Galaxy Nexus using Tapatalk 2