Hi,
I had installed xrecovery and tried to add JIT, but wrong xrecovery (with sdcard bug) and JIT causes this error (boot loop):
~ # [[email protected] ~]$ adb logcat
- waiting for device -
link_image[1965]: 1120 could not load needed library 'libm.so' for '/system/bin/seserve_mem_region[834]: OOPS: 1120 prelinked library 'libm.so' mapped at 0x400, not at 0xafc00000)CANNOT LINK EXECUTABLE
Before i did a backup with xrecovery, byt i cant recover it, because it gives me sdcard mount error. So I had stuck on it!
I cant use flashtool to reflash my phone, because I am on linux...And need backed up data of course...
I hope, because adb shell still works, that recovery of libraries could work, could anyone good man post for me these libraries (and binaries)?
/system/bin/dalvikvm
/system/bin/dexopt
/system/bin/logcat
/system/lib/libcutils.so
/system/lib/libdl.so
/system/lib/libdvm.so
/system/lib/liblog.so
/system/lib/libm.so
/system/lib/libnativehelper.so
/system/lib/libz.so
Thank you in advance. Hope anyone help me!
HeliumX10 said:
Hi,
I had installed xrecovery and tried to add JIT, but wrong xrecovery (with sdcard bug) and JIT causes this error (boot loop):
~ # [[email protected] ~]$ adb logcat
- waiting for device -
link_image[1965]: 1120 could not load needed library 'libm.so' for '/system/bin/seserve_mem_region[834]: OOPS: 1120 prelinked library 'libm.so' mapped at 0x400, not at 0xafc00000)CANNOT LINK EXECUTABLE
Before i did a backup with xrecovery, byt i cant recover it, because it gives me sdcard mount error. So I had stuck on it!
I cant use flashtool to reflash my phone, because I am on linux...And need backed up data of course...
I hope, because adb shell still works, that recovery of libraries could work, could anyone good man post for me these libraries (and binaries)?
/system/bin/dalvikvm
/system/bin/dexopt
/system/bin/logcat
/system/lib/libcutils.so
/system/lib/libdl.so
/system/lib/libdvm.so
/system/lib/liblog.so
/system/lib/libm.so
/system/lib/libnativehelper.so
/system/lib/libz.so
Thank you in advance. Hope anyone help me!
Click to expand...
Click to collapse
Why were you trying instal JIT?
Anyway, would it be easier to repair phone with pccompanion rather thatn do this?
Its only a suggestion, I am not savvy with linux
I was trying to install JIT because of speed up my phone. Lags more than few seconds were getting me really angry. even with few apps on background and good task manager...
You`re true, it COULD be easier. But in linux it is not possible to run PC companion or SEUS...
That`s why I am looking for files. I am not a noob
HeliumX10 said:
I was trying to install JIT because of speed up my phone. Lags more than few seconds were getting me really angry. even with few apps on background and good task manager...
You`re true, it COULD be easier. But in linux it is not possible to run PC companion or SEUS...
That`s why I am looking for files. I am not a noob
Click to expand...
Click to collapse
I never said you were, I just thought JIT was not needed on GB roms...and I have no experience with linux.
Cant you just download thos files from a custom rom, or extract them a stock fw?
Again, apologies if this is not possible on linux, but I dont have access to those files at the moment
gregbradley said:
I never said you were, I just thought JIT was not needed on GB roms...and I have no experience with linux.
Cant you just download thos files from a custom rom, or extract them a stock fw?
Again, apologies if this is not possible on linux, but I dont have access to those files at the moment
Click to expand...
Click to collapse
No need to apologize... I am discussing a lot of time with totally non experienced users (because I am linux forum administrator)
So I havent read that JIT is not needed on GB... Damn, if it is true I made a really stupid and unnessesary mistake with horrible effect...
I`ll google how it is about it, but want to recover my phone again first
Yes, I had downloaded few stock roms, but I am not able to extract files from them! Looking for some ROM dissasembler or something like that... I notice, that many windows programs (but not all - especially flash tools) works under linux properly, so looking for ANY extractor...
Maybe unyaffs will work. Doomlord had those files. Send him a pm, he is very knowledgeable about this
Also, can you not use win zip (or similar) on Linux....
Sent from my X10i using xda premium
HeliumX10 said:
Hi,
I had installed xrecovery and tried to add JIT, but wrong xrecovery (with sdcard bug) and JIT causes this error (boot loop):
~ # [[email protected] ~]$ adb logcat
- waiting for device -
link_image[1965]: 1120 could not load needed library 'libm.so' for '/system/bin/seserve_mem_region[834]: OOPS: 1120 prelinked library 'libm.so' mapped at 0x400, not at 0xafc00000)CANNOT LINK EXECUTABLE
Before i did a backup with xrecovery, byt i cant recover it, because it gives me sdcard mount error. So I had stuck on it!
I cant use flashtool to reflash my phone, because I am on linux...And need backed up data of course...
I hope, because adb shell still works, that recovery of libraries could work, could anyone good man post for me these libraries (and binaries)?
/system/bin/dalvikvm
/system/bin/dexopt
/system/bin/logcat
/system/lib/libcutils.so
/system/lib/libdl.so
/system/lib/libdvm.so
/system/lib/liblog.so
/system/lib/libm.so
/system/lib/libnativehelper.so
/system/lib/libz.so
Thank you in advance. Hope anyone help me!
Click to expand...
Click to collapse
dalvikvm
dexopt
logcat
libcutils.so
libdl.so
libdvm.so
liblog.so
libm.so
libnativehelper.so
libz.so
Thanks a lot matthew5025 ! (thanks button pressed of course )
I have rewrited all the files, which has been changed... But without effect... This is really strange, I cant understand it...
So, I have to flash, its bad...
But my first flashing ROM I`d like to flash some of custom rom (not official) - any suggestions?
I like fast and stable system, dont need any special features and apps, animations and laggy eye candy launchers.
HeliumX10 said:
Thanks a lot matthew5025 ! (thanks button pressed of course )
I have rewrited all the files, which has been changed... But without effect... This is really strange, I cant understand it...
So, I have to flash, its bad...
But my first flashing ROM I`d like to flash some of custom rom (not official) - any suggestions?
I like fast and stable system, dont need any special features and apps, animations and laggy eye candy launchers.
Click to expand...
Click to collapse
only 2 ROMS.
FXP045 (FXP will be release anytime soon this week)
Here
zdzihu ZMOD
Here
cheers
HeliumX10 said:
Thanks a lot matthew5025 ! (thanks button pressed of course )
I have rewrited all the files, which has been changed... But without effect... This is really strange, I cant understand it...
So, I have to flash, its bad...
But my first flashing ROM I`d like to flash some of custom rom (not official) - any suggestions?
I like fast and stable system, dont need any special features and apps, animations and laggy eye candy launchers.
Click to expand...
Click to collapse
I like wolfbreak's gamer's rom as it's FAST! link but you should go on a flashing spree, than choose one you like.
VMODS 5 rom +5.1 Update with doomkernel 0.5a!!
Thanks guys for your tips !
Tried both ROMs and I chose Wolfbreak`s gaming ROM, really fast
Sweet
Related
If I undertsand well with the root applied we are sticky on the old kernel. To solve the problem we could is the old kernel to boot a new one as here:
embeddedarm.com/software/arm-linux-bootloader.php
What do you think?
Ciao Angelo
Ok at the end I thinked how to load alternative rom without modifying the bootloader (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
ardf69 said:
Ok at the end I thinked how to load alternative rom without modifying the (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
Click to expand...
Click to collapse
This sounds good. Isn't it similar to HaRET for Windows Mobile?
Theres a ton of potential on the X10 i dont get why so many people don't like it..
anyways I'm working on trying to get apps on the SDcard with CM mod (I'm close)
xxsashixx said:
Theres a ton of potential on the X10 i dont get why so many people don't like it..
anyways I'm working on trying to get apps on the SDcard with CM mod (I'm close)
Click to expand...
Click to collapse
It's only because of the lack of multi-touch.
We'll be able to use froyo anyway, if we can get this bootloader running - whatever SE do. Then nearly all of the features of the X10 can be used.
Just a question concerning Android
If i got it right,
1. Android is running as a virtual java machine on top of the linux kernel
2. SE uses a newer kernel than other donut (1.6) androids
3. Java VM boots AFTER linux kernel and system
4. we have root, so we can modify the init.d (boot) files
5. so wo could let files be launched at boot time
Woldnt it be possible to insert a shell script that after booting linux kernel and before starting the java vm replaces the java vm files so that on top of the SE 2.6.29 kernel Froyo is running?
That way we wouldnt need to modify the bootloader. Only problem (?) ist that we are bound to the linux kernel settings made by SE (as we cannot overwrite the running system).
just an idea to discuss ....
Bax
I'm very very interested in deving for X10, I have extensive knowledge of linux and kernels
but anyways, android is running a Java VM? really?
Baxxx said:
Just a question concerning Android
If i got it right,
1. Android is running as a virtual java machine on top of the linux kernel
2. SE uses a newer kernel than other donut (1.6) androids
3. Java VM boots AFTER linux kernel and system
4. we have root, so we can modify the init.d (boot) files
5. so wo could let files be launched at boot time
Woldnt it be possible to insert a shell script that after booting linux kernel and before starting the java vm replaces the java vm files so that on top of the SE 2.6.29 kernel Froyo is running?
That way we wouldnt need to modify the bootloader. Only problem (?) ist that we are bound to the linux kernel settings made by SE (as we cannot overwrite the running system).
just an idea to discuss ....
Bax
Click to expand...
Click to collapse
Yes it can be done in /init.rc. A better solution (instead of copying files) could be to chroot the envinroment, so you teorically could have more rom (one for each directory in /system). Remain however the problem you cannot run a modified kernel (you need a boot loader like 2nboot-ng as I said before).
Ciao Angelo
xxsashixx said:
I'm very very interested in deving for X10, I have extensive knowledge of linux and kernels
but anyways, android is running a Java VM? really?
Click to expand...
Click to collapse
Hi!
Android is running in a Dalvik VM, similar to Java VM ...
http://en.wikipedia.org/wiki/Dalvik_(software)
Greetings from Vienna,
Bax
ardf69 said:
Yes it can be done in /init.rc. A better solution (instead of copying files) could be to chroot the envinroment, so you teorically could have more rom (one for each directory in /system). Remain however the problem you cannot run a modified kernel (you need a boot loader like 2nboot-ng as I said before).
Ciao Angelo
Click to expand...
Click to collapse
Hi Angelo!
chroot sounds goot, but could be a space/speed problem. On SD there is enough space, but it is slower - so that could be testing ground. Internal Rom is faster, but if original is not overwritten space could be limited.
Concerning modified kernel: Is that modification really necessary for running Android 2.1? If i remember it right N1 uses a similar Kernel for 2.1 as SE for 1.6?
Greetings,
Bax
Lets keep this going and hopefully get a working 2.1 system
Baxxx said:
Hi Angelo!
chroot sounds goot, but could be a space/speed problem. On SD there is enough space, but it is slower - so that could be testing ground. Internal Rom is faster, but if original is not overwritten space could be limited.
Concerning modified kernel: Is that modification really necessary for running Android 2.1? If i remember it right N1 uses a similar Kernel for 2.1 as SE for 1.6?
Greetings,
Bax
Click to expand...
Click to collapse
There are interesting patches to the kernel as overclock for example. I think we can use the original kernel at the start and then we can create a new one kernel from the sources.
Ciao Angelo
That sounds great!
Another limitation i remember is the limited RAM use in 1.6 which is probably also a kernel/driver problem ...
(i think starting from 2.0 or 2.1 the full RAM area is usable)
Bax
We might be able to use the information already tried on the motorola milestone which also has a locked down bootloader.
http://and-developers.com/motorola_milestone
this has information on the kexec option
Also the mot_boot_mode hack looks promising. I don't have any idea of the boot up process of the X10 but hopefully this would work.
"mot_boot_mode hack
A.k.a. the Newton hack. The init.rc script resides in the signed boot CG, so we cannot alter it. But it happens to exec /system/bin/mot_boot_mode, which we CAN change once we run as root, since it's located inside the system CG. By moving mot_boot_mode to mot_boot_mode.bin and creating a shell script as our new mot_boot_mode, we can get the system to run commands of our choice such as mounting partitions, etc. This is the earliest we can tap into the boot process, and it is early enough to let us introduce hacks such as APPS2SD, making better use of /cache, and other useful stuff. We could even branch to load a new kernel using kexec like mechanism."
Yes I know it is not the X10 but hopefully we can learn from work already being done on the motorola milestone.
seems like an interesting idea, I hope some of the devs have time to work on this while dealing with the issues with root. They might be taking a well deserved break which is fine.
ardf69 said:
Ok at the end I thinked how to load alternative rom without modifying the bootloader (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
Click to expand...
Click to collapse
1 is done
2 working on 2
3.is for omap cpu wont work !!
4.manualy did it and device boots works
jerpelea said:
1 is done
2 working on 2
3.is for omap cpu wont work !!
4.manualy did it and device boots works
Click to expand...
Click to collapse
Great work, jerpelea!.
I'm not sure I understand this, but does this involve loading a another kernel after the flashed one, to boot into another rom?
HunteronX said:
Great work, jerpelea!.
I'm not sure I understand this, but does this involve loading a another kernel after the flashed one, to boot into another rom?
Click to expand...
Click to collapse
I'm curious about that too. Are we talking some kind of chainloading, kexec or even something UML-like?
Yes bu not using motorolas module
Motorola has different cpu
Sent from my X10i using XDA App
jerpelea said:
Yes bu not using motorolas module
Motorola has different cpu
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Ok, thanks.
Is there a module for the QSD8250 snapdragon chipset?
I was excited about the rollout of Android 2.1 on X10 last November (it finally arrived...), then I was able to install more apps and experience more fun with upgraded os. However, here also comes the problem, I only had 40MB left in my internal memory, and App2sd can only be done with millions of steps...
So I was thinking.. if I have to put in so much effort just to get App2sd working, why not just spend the effort to install a custom ROM with Android 2.2 (where App2sd becomes a build-in capability, and I will be able to do voice actions too!)
Honestly, it was easier than I thought, but there are some details you probably want to pay attention to in the process, so I am writing this comprehensive guide here that can be easily followed (even for newbies!).
[All credits go to the CyanogenMod dev team for the custom ROM, zdzihu for xRecovery, Androxyde and Bin4ry for FlashTool, ShortFuse for SuperOneClick, Froshed Blue for themes.
Thank you all for the incredible work to make this possible! And sorry if I missed anyone...
NOTE: I WILL NOT BE RESPONSIBLE IF ANYTHING GOES WRONG.
1. Back up all your data.
- Use apps in the market such as MyBackupPro to back up all contacts, sms, call log etc. If your phone is rooted, you can also back up app+data with it (so you won't lose your progress on games or apps).
- OR you can sync your contacts etc via your Google account, and back up all apps with Astro.
- DO NOT use the backup & restore app with the stock 2.1, after you flash to 2.2, this app won't be available anymore, and there is no way you could retrive the data from the .sbf file generated by it!
UPDATE: SE Backup & Restore is now available here in the Extras section. I haven't tested it yet but if you want you can give it a try.
2. If you have already updated your phone to baseband 2.1.54 or 2.1.55, skip this step.
- Otherwise, go to here to find and download the most updated firmware (I used X10a _2_1_A_0_435 with DualTouch).
- Download FlashTool v0.29, copy the firmware you downloaded earlier to the firmware folder in FlashTool.
- Now flash your phone with this firmware, follow the instructions on the screen.
3. Root your phone.
- Download SuperOneClick v1.7 from shortfuse.org.
- Root with one simple click.
4. Install Busybox and xRecovery.
- Get Busybox from the market, once it's opened, it will tell you that your phone is rooted, install the newest version into /bin.
- Download xRecovery, rename the apk file to xRecovery.Zip.
- Unpack the file, find ./res/raw folder with 3 files - chargemon, busybox, xrecovery.tar).
- Copy these 3 files into /system/bin using app Root Explorer. (Note: this is the manual installation method, which I found more stable, or you can just use automatic install with the xRecovery.apk downloaded earlier.)
5. Copy the files for ROM installation (CM 6.1.3 V4, Google Apps Pack, and new Android market) onto your SD card.
UPDATE: CM 6.1.3 V4.5.7 is out with Camcorder working, in this step, you will copy CM 6.1.3 V4.5, CM 6.1.3 V4.5.7 instead of V4.
6. Install custom ROM.
- Reboot your phone.
- Right after the SE white text appears, press the back button a few times until xRecovery comes on (if it doesn't work, try one more time or reinstall xRecovery using the manual method if you didn't.)
- In xRecovery, use volume button to move up and down, home to enter.
- Do a Factory Reset, Wipe Cache Partition, Advance Options> Wipe Dalvik Cache, Wipe Battery Stats.
- Then install Custom Zip and choose CM6.1.3-V4.zip (or V4.5) for your SD card for the ROM. (If you are installing V4.5, install Custom Zip - V4.5.7 after this step.)
- Install Custom Zip and choose CM-V4Gapps.zip (or V4.5.7) for Google Apps.
- Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked- Login to market once, reboot your phone to xRecovery again, install Custom Zip and choose NewMarket.zip.
If you want more selections of theme, check out this thread.
Post Actions
- Restore all your information and apps.
- Get App2SD from market to easily move apps to SD or internal memory, or you can do it manually in settings>application settings>manage application. (Note: if you want to display a widget of an app, keep the app on the phone, DO NOT move it to SD as widget will not be available for apps moved to the SD.)
- MIUI Camera is included with the ROM, or you can use Camera360 (tested working). If you want camera flashlight, use Vigenette.
UPDATE: MIUI Camcorder is working on v4.5.
- Go to settings>cyanogenmod settings and settings>ADWLauncher for more tweaks.
UPDATE: ADWLauncher is been replaced by another launcher (I forgot the name) in V4.4+
_______________________________________________________________________
Read my blog for more reviews and guides of Android - http://baimandy.wordpress.com
Follow me on Twitter: MandyBai
Thanks! This kind of combined all the guide together makes it so much clearer~
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
mjrabhi said:
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
Click to expand...
Click to collapse
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
4androidonly said:
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
Click to expand...
Click to collapse
Thank you much much
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
thanx ... good guide
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
gil2004xp said:
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
Click to expand...
Click to collapse
Hmmm ... never thought of that since it doesn't concern me but if you want to change LED notification color for different apps, you can do it at CMsettings-user interface.
wasiimabbas said:
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
Click to expand...
Click to collapse
the rom is just personal preferences~ i am glad the guide helped~
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
xriel said:
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
Click to expand...
Click to collapse
really? I am not sure how to fix it since I never experienced this. But I do notice with the new 2.2 rom, it takes some time to recognize all the data on SD card at the initial start (both on the phone and on the computer).
The first time I connect to computer (USB storage mode) it took 5 mins for the computer to recognized it, and the phone was kind of froze for a while, but after that it's all fine.. maybe just try to wait a bit?
Mehn thanks for this. Soooooo easy.
becknise said:
Mehn thanks for this. Soooooo easy.
Click to expand...
Click to collapse
you're welcome
I'm just in the process of running through the guide now. Can't wait!!!
I have got a problem with completing Step 4. I have downloaded and install BusyBox from the MarketPlace but when I open it up all I get is a blank OK message and the Status: Looking for BusyBox...
Any ideas??
Also I can open xRecovery but if I click on the "Install xRecovery" button I get the little magnify glass change to a red stop circle.
Any ideas??
This is also I post of the Root Log
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1466 KB/s (585731 bytes in 0.390s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
1614 KB/s (1062992 bytes in 0.643s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock2
OK
Reading OS Version properties...
Version: 2.0
OK
Remounting system with read-write access...
OK
Pushing su-v2...
1282 KB/s (26264 bytes in 0.020s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1760 KB/s (196521 bytes in 0.109s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Thanks
Thank you!!! Your guide was very helpful to me! Sorry for my bad English
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Thanks for this. Quick question, it may seem dumb but what do you mean when you say to :
"Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked"
Where in the menu do I find "programs" exactly?
NM... I didnt realize Sysctl was an App from the market. When I first completed it, I didnt have service so I couldnt use the Market. Flashed again and it works.
Thanks!
Testsubjec said:
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Click to expand...
Click to collapse
Are you referring to the parms for sysctl? if you go to the list of all applications, there is a pre-installed app called sysctl config (it's like a penguin icon), then you will be able to set the parameters there. hopefully this answers your question!
hi,
trying to install xrecovery...
so downloaded the .apk to instal, not working (busybox newest version from market, super user rights also)
in this app are 3 parts of instalation, first and last work 2. gots a red circle and says that it cant be stated.
so i tried it manualy and copied the files via root explorer(sh, chargemon and xrecovery.tar , busybox file). rebootet pushed the back button several times nothing happend -.- just the normal booting.
try the reboot again
now press the back button or the sound button on the rigth side
you say "sh,xrecovery.tar,busybox,carmagon"
i don#t know a sh file
try to install xrecovery with the flashtool
it is here in xda you have to search for it
strange, worked with the flash tool, then updated to version 1.00 via xrecovery but after that not working :/
looks like that version 1.00 is not working well so dont update it
yep switched back,
somehow in the xrecovery menu it says something about x8 recovery tool. ans also i have to take a x8 multitouch file to work.
a lot of things from the x8 work on our device's
but MULITTOUCH would not work on our devices
chose oure dualtouch driver it's the best wich work
flex96 said:
a lot of things from the x8 work on our device's
but MULITTOUCH would not work on our devices
chose oure dualtouch driver it's the best wich work
Click to expand...
Click to collapse
but problem is that it doesnt work
Need help installing xRecovery on XPERIA X10 Mini
Hello all,
Seems there isn't much help for newbies here :-(
I browsed all of the relevant parts of the site (I think):
http://forum.xda-developers.com/showthread.php?t=859571
https://www.xda-developers.com/android/reboot-x10-into-xrecovery-from-os/#comments
And found these links outside xda-developers:
http://www.android-hilfe.de/root-ha...2488-xrecovery-nandroid-auf-dem-x10-mini.html
http://www.mobil-talk.de/android-fa...ecovery-nandroid-auf-dem-x10-mini-nutzen.html
I used the German-language page (http://www.mobil-talk.de/android-fa...ecovery-nandroid-auf-dem-x10-mini-nutzen.html) to install the files, as I'm too stingy too shell out for the applications people here seem to need to install a system tool on their phones...
There are a few things that confuse me greatly, however:
1) What is the version of xRecover (or xrecover-x10mini) that we are supposed to be installing on our phones
2) What is the impact of busybox on the process (current version from the Market installs as /system/xbin/busybox, not as /system/bin/busybox as xRecovery seems to want; I know the chargemon script has /system/bin/busybox hardcoded)
3) What is the correct button to press at boot time of the phone to get into the xRecover application?
I installed several versions of the software I found through this site:
xRecovery-minipro-0.1.1-beta.tar.bz2
xrecovery_signed.apk
Neither of those seems to work on my XPERIA X10 Mini, and I have tried the back, volume up and volume down buttons, and I have tried to change the event from event0 to event1.
I am just trying to install the CyanogenMod 6 ROMs on my phone and am getting very disappointed with the entire process. If and when I do get it to work, I shall attempt to write my experiences down so others might have an easier time than I had.
Despite all the groveling, I do appreciate the community's efforts to make all of this work. I hope I can do my bit to document it better or to help iron out some inconsistencies.
Regards
looks like my problem
for me installing with the flash tool worked. (so just download flash tool and klick the xrecovery button =) )
after that i could copy the new custom rom files to the sd card and install them with xrecovery.
just push the back button all the time while booting repeatly when you got xrecovery succesful installed it should work
hi
recently got an Olivepad VT-100 and got it rooted and clockwork Mod installed on the same and also backed up my rom .
So For those who have been struggling to get the same done like me here is a simple guide
1. Get to know that The Olivepad VT - 100 is the same as
these Models : Viewpad 7 Cherry Mobile Superion, Commtiva Linx N700, Spice MI700, and Camangi FM600( found this out the hard way)
for rooting it go here
[TOOL] Viewpad 7 Backup, Root & Recovery - By lakehousetech (thanks to his help i got it done)
Link : http://forum.xda-developers.com/showthread.php?t=1015005
one more link for the same : http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
For recovery via Rom Manager see below link (note i have not used this)
Link : http://hucqim80.blogspot.com/2010/12/how-to-install-clockworkmod-recovery.html
the superoneclick did not work for me so for those who have the same problem
take ginger break APK from attached install it on ur Olive pad and bang it works with one click
IT worked for me
thanks to Nos0x for this find
Note : i did not use ADB for the commands as im not comfy with the same
i used Terminal emulator from the Pad for the commands
update : i also tried re flashing my nand backup via CWM it worked fine for me
This worked for me as i was willing to take the risk
so remember the risk is always yours and im not responsible if you brick ur phone or anything
Important : on rooting & getting CWM 1st do a Nand backup of ur original Stock rom before trying to flash any rom.So u are always safe & can go back to ur stock Rom
Working roms on our OLivePad
hi
the below roms i have tested and the same works fine on the olivePad
pls see below links for details
1. [ROM] Viewsonic Viewpad 7 Froyo Enhanced - By lakehousetech
Link : http://forum.xda-developers.com/showthread.php?t=1008673
2. [DEV]|[ROM]+[KERNEL] [FM6 Variant (Spice Mi700 / ViewSonic ViewPad 7 etc.)] by-tj_style
link : http://forum.xda-developers.com/showthread.php?t=1093440
get the update zip from here on above post : http://forum.xda-developers.com/showpost.php?p=14384918&postcount=39
3.[14.JUL.11][ROM]CleanViewpad7 v1.0|APPS2SD|CWM - by skink123
link : http://forum.xda-developers.com/showthread.php?t=1168562
this one is real good it has app2sd and ie all u installed apps are on ur SD thus more space on ur phone Storage
note : install this after installing the ROM for 154MB phone storage(only for this ROM ie no : 3 not the others OK)
take attachment from below link and flash via CWM
Link : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
4. one more good rom take it from here : http://forum.xda-developers.com/showpost.php?p=15970641&postcount=17 - by googlehome
and add this attachment : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
via CWM after flashing the rom and u will have App2sd & 157MB free on ur phone storage
i have been using this for a long time and realy loving it
5. http://forum.xda-developers.com/showthread.php?t=1224825 - By amalgamation
this one is real good it has apps2sd in the rom and works good
Note : for 3 & 4 combos & 5 to work u need to have Ext4 partition done
u can do it via CWM
enjoy enjoy
Problem & Solutions with the Pad
hi
well this was a problem i faced today and got a solution for the same wanted to share the same
Problem
well after flashing a custom Rom today i read about a apps2sd which was available in the market i downloaded the same to my pad installed the APK on my pad its some application which said it will enable JIT i clicked on it and the phone restarted and then i had just a blank screen ie it was on but blank
i kind a got a heart attack as my pad is only around a month old but then life is about taking risk right or it wont be fun
solution
i remembered i did some thing similar to what is given below long time back with my old gene aka HTC 3400 win Mob i just tried the same & it worked for me
hold the volume buttons both of them & power button & while holding these two u need to restart by inserting a pin in the restart small hole available next to the mike
on doing the above u will be able to got to ur CWM and u can re install the os u want again that what i did
just sharing my experience in case u get the same problem
thanks
hari
reserverd
hi
for future use
Hi, I tried using super one click but I always fail to root.
This is the message I get
QUOTE
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
202 KB/s (5392 bytes in 0.026s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1033 KB/s (1062992 bytes in 1.004s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock7
OK
Reading OS Version properties...
Version: 2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
failed to copy 'D:\SOC\su-v2' to '/system/bin/su': No space left on device
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
cp: write error: No space left on device
OK
Pushing Superuser.apk...
failed to copy 'D:\SOC\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Pushing Superuser.apk... (/data/app)
failed to copy 'D:\SOC\Superuser.apk' to '/data/app/Superuser.apk': Permission denied
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
ro.wifi.channels=
ro.product.cpu.abi=armeabi
ro.product.model=V-T100
ro.build.tags=release-keys
ro.build.version.release=2.2
ro.build.description=msm7627_surf-user 2.2 FRF91 5009_3_16R release-keys
ro.product.brand=Olive
ro.product.device=vt100
ro.build.version.incremental=5009_3_16R
ro.build.type=user
ro.build.date.utc=1290718061
ro.board.platform=msm7k
ro.product.name=V-T100
ro.product.board=V-T100
ro.build.user=user
ro.build.display.id=FRF91
ro.build.version.codename=REL
ro.build.product=V-T100
ro.build.id=FRF91
ro.build.version.sdk=8
ro.product.manufacturer=FIH
ro.product.locale.region=US
ro.build.date=Fri Nov 26 04:47:41 CST 2010
ro.product.locale.language=en
ro.build.host=cmcsservice
ro.build.fingerprint=Olive/V-T100/vt100/V-T100:2.2/FRF91/5009_3_16R:user/release-keys
/QUOTE
Any help would be helpful..
Actually my problem is that I now cannot enter recovery mode at all.. It keeps hanging at the enter recovery mode screen..
Regards
Milton
hi
try the gingerbreak apk attached
install it in ur pad and clik on it it worked for me
super one did not work for me too
for clokwork see the link i gave for rommanager
goodluck
haree said:
hi
try the gingerbreak apk attached
install it in ur pad and clik on it it worked for me
super one did not work for me too
for clokwork see the link i gave for rommanager
goodluck
Click to expand...
Click to collapse
Hey, thanks for the speedy reply. I did try gingerbreak. However, though I can install ans use most root required apps, when I try to manually install busybox, it fails.. is this normal.
the bigger problem is, ever since I first tried to root my olivepad, I am not able to enter recovery mode at all. I am trying all of this just so I can use rom manager and flash into the default rom. ;-( any help here? is there any way I can restore the olivepad to stock. If I unroot the system, can I give it for service under warranty?
miltonben said:
Hey, thanks for the speedy reply. I did try gingerbreak. However, though I can install ans use most root required apps, when I try to manually install busybox, it fails.. is this normal.
the bigger problem is, ever since I first tried to root my olivepad, I am not able to enter recovery mode at all. I am trying all of this just so I can use rom manager and flash into the default rom. ;-( any help here? is there any way I can restore the olivepad to stock. If I unroot the system, can I give it for service under warranty?
Click to expand...
Click to collapse
hi
if u successfully root & get the CWM installed u can do a nand back up and restore the same but when u root u have the risk of loosing ur warranty
but to my knowledge if u re install the OS and re install ur original image
u need to backup ur oringal via ADB or termemulator pls read lakehousetech thread for details i have given the link in the 1st page
u can do this via terminal emulator or ADB & remove the superuser
i dont think the service guys go all that deep in checking if u have rooted and if u dont have the super user on ur pad i Dont thing they will find out u have rooted ur pad . this is as per my experience in India with my phone
the risk is always yours Kindly note im not responsible for any issues u get into with your Pad
note ; read this too : http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
it also has info on how to install busy box u can also get a busy box installer from the market
Hi Haree,
Thanks a lot for all the info. And honestly, I don't need to be reminded that me breaking my pad is not your mistake ;-)
Well, I will sure look into the new link.
BTW, I needed a little help understanding something. When I saw the size of my OS partition, I realized there is only 32kb of space left. Due to this, I am unable to use oneclick to copy new files into the OS partition from the sd card. Could you please confirm whether this lack of space in the OS partition is normal?
And I am still searching for a way to force modify the OS partition using some other manual pc oriented means (not the exe's). Would be grateful for your suggestions.
Again, thanks a lot.
Regards
Milton
hi
sorry i dont get ur question are u talking about SD ext part
if so it is better to have more than 1GB and u can do this with CWM
im not a techie i just read and do the needful to get the rom flashed on my phone/Pad
for more tech questions i think its best u ask lakehousetec or any of the rom developers
miltonben said:
Hi Haree,
Thanks a lot for all the info. And honestly, I don't need to be reminded that me breaking my pad is not your mistake ;-)
Well, I will sure look into the new link.
BTW, I needed a little help understanding something. When I saw the size of my OS partition, I realized there is only 32kb of space left. Due to this, I am unable to use oneclick to copy new files into the OS partition from the sd card. Could you please confirm whether this lack of space in the OS partition is normal?
And I am still searching for a way to force modify the OS partition using some other manual pc oriented means (not the exe's). Would be grateful for your suggestions.
Again, thanks a lot.
Regards
Milton
Click to expand...
Click to collapse
Hey Haree,
that's ok, I will try and ask around. Seems that no body else is facing the same issue. I might end up giving this for a service..
Thanks again
Milton
olive pad stuck in auto RTM background
any one can help me ... my olivepad can do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
help me please
blank screen .auto rtm
any one can help me ... my olivepad can do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
blank screen .auto rtm
any one can help me ... my olivepad can't do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
cikal0n7th said:
any one can help me ... my olivepad can't do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
Click to expand...
Click to collapse
hi
assuming u have ur CWM installed and that u have done a nand backup of ur original rom read the below link it is the 3rd post of mine do it and u can u can do a nand restore
http://forum.xda-developers.com/showpost.php?p=15851144&postcount=3
do this :
hold the volume buttons both of them & power button & while holding these two u need to restart by inserting a pin in the restart small hole available next to the mike
on doing the above u will be able to got to ur CWM and u can re install the os u want again that what i did
Thanks Haree, I used GingerBreak and it looks like it worked. I have installed Terminal Emulator and Im not able to get the soft keys to come up, I tried keeping menu button pressed. Can you tell me what is the keyboard software you are using and how you were able to bring the keyboard up in any of the terminal emulators? Also tried the busybox installer, it reports an unexpected error and closes.
bmvbab said:
Thanks Haree, I used GingerBreak and it looks like it worked. I have installed Terminal Emulator and Im not able to get the soft keys to come up, I tried keeping menu button pressed. Can you tell me what is the keyboard software you are using and how you were able to bring the keyboard up in any of the terminal emulators? Also tried the busybox installer, it reports an unexpected error and closes.
Click to expand...
Click to collapse
hi
Terminal Emulator use it in portrait mode to work NOT land scape Mode
press the menu button and u will get toggle keypad press this and u can use the same.busybox u need to get the tool from market and install 1.7
Make sure u take a Nand backup before trying any rom
good luck
haree said:
hi
the below roms i have tested and the same works fine on the olivePad
pls see below links for details
1. [ROM] Viewsonic Viewpad 7 Froyo Enhanced - By lakehousetech
Link : http://forum.xda-developers.com/showthread.php?t=1008673
2. [DEV]|[ROM]+[KERNEL] [FM6 Variant (Spice Mi700 / ViewSonic ViewPad 7 etc.)] by-tj_style
link : http://forum.xda-developers.com/showthread.php?t=1093440
get the update zip from here on above post : http://forum.xda-developers.com/showpost.php?p=14384918&postcount=39
3.[14.JUL.11][ROM]CleanViewpad7 v1.0|APPS2SD|CWM - by skink123
link : http://forum.xda-developers.com/showthread.php?t=1168562
this one is real good it has app2sd and ie all u installed apps are on ur SD thus more space on ur phone Storage
note : install this after installing the ROM for 154MB phone storage(only for this ROM ie no : 3 not the others OK)
take attachment from below link and flash via CWM
Link : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
4. one more good rom take it from here : http://forum.xda-developers.com/showpost.php?p=15970641&postcount=17 - by googlehome
and add this attachment : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
via CWM after flashing the rom and u will have App2sd & 157MB free on ur phone storage
i have been using this for a long time and realy loving it
Note : for 3 & 4 combos to work u need to have Ext4 partition done
u can do it via CWM
enjoy enjoy
Click to expand...
Click to collapse
The megaupload site is blocked is Malaysia, can someone upload to another site pls. Thanks in advance
syaah said:
The megaupload site is blocked is Malaysia, can someone upload to another site pls. Thanks in advance
Click to expand...
Click to collapse
hi
tell me what u want of the 4 and ill load it to my drop box and give u
here is one i think this googlehome rom take it from below link
link : http://dl.dropbox.com/u/10031257/CleanViewpad7_signed_v1.0.zip
Hi Hari,
I'm Rahul.. Have been trying to get hold of a good Custom ROM for my Olivepad for quite sometime now (Must have been blind to have ignored your posts earlier on).
Presently I'm running it on the Stock ROM rooted with z4root with CWM 2.5.1.2.
I have ROM Manager v 4.3.3.3 installed and tried to load CM 7.0.2 and later the other updates but every time it kept saying that there was an error in loading the ROM.
Assuming that I have done everything (rooting and loading CWM) correctly I'm going ahead with the ROMs suggested by you (VPAD7_signed.zip).
Shall keep this post updated on my success (or failure)
TOO MUCH TEXT!
Pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
READ THIS FIRST - THEN DOWNLOAD BELOW.
UNLOCKED BOOTLOADER ONLY!
REMEMBER TO FASTBOOT ERASE SYSTEM/FASTBOOT ERASE USERDATA AFTER INSTALLING KERNEL! (if this makes no sense to you, read the stuff in blue below)
INSTALL HELIUM ROM FIRST, THEN INSTALL DEVICE FILES - failing to do so will result in a black screen after loading CWM (just nap out the battery, reinsert and enter CWM if you forget, then install device files)
For the daring, here you go:
Helium Light ROM - http://www.mediafire.com/download/cib6c62goaq6aa6/helium-light.zip
De-Bloated (Now even smaller!) Helim Light ROM V 1.14 beta - http://www.mediafire.com/download/o2nbydf8a0aco76/helium.v1.14b.zip
COCONUT (LwW) :
Device Files: http://www.mediafire.com/download/ia974mga7u3rl39/helium-coconut-device-files.zip
Kernel: http://www.mediafire.com/download/5vaj2o871hcwks4/coconut-helium-light-v2.img
MANGO (Mini Pro) :
Device Files: http://www.mediafire.com/download/a1f5vsolggs4npj/helium-mango-device-files.zip
Kernel: http://www.mediafire.com/download/wrmbhj9f1wjrdy5/mango-helium-light-v2.img
SATSUMA (Active) :
Device Files: http://www.mediafire.com/download/miy1baois8xxmvm/helium-satsuma-device-files.zip
Kernel: http://www.mediafire.com/download/c265j08x66s03a2/satsuma-helium-light-v2.img
SMULTRON (Mini) :
Device Files: http://www.mediafire.com/download/p6vtvlhfnukkm22/helium-smultron-device-files.zip
Kernel: http://www.mediafire.com/download/d7utcoagzcp8dic/smultron-helium-light-v2.img
This ROM is based on Saqib Nazm's wonderful work, Fluorescent Feather ROM. So most of what´s right with this ROM is his work and thanks to him. : )
The ROM is based on Kappa by kast with batteryfixes added by karandpr.
If anyone wants to use this to build something else upon this, feel free to do so!
If you have no idea how to fastboot erase system/userdata, I made this file for you.
Kernel flasher - http://www.mediafire.com/download/hzn3iqh25g5pxij/Kernel_Flasher.zip
Put this where ever you want (more thanks to karandpr! : ).
Put the kernel image in the IMG folder in Kernel_Flasher. Make sure you only have ONE kernel in the IMG folder. Only put the kernel you wish to flash in the IMG folder. Putting more than one kernel in IMG folder will fail.
Right click on and run Kernel_Flashing_Tool.bat as admin. Hook up your phone. Does not matter if it is in a ROM, in CWM or in fastboot mode. The batch file will do it all.
BUT: This only works if you have the drivers in windows installed for your phone (you do if you have used flashtool to flash other kernels before).
This also makes it easy to flash "back to" a standard kernel later.
Reserved for a rainy day.
Just in case, also, mods, I have no idea what I'm doing. Please don't ban hammer me for trying to give something back to the community, but rather advice me if I'm doing something wrong or have forgotten something. : P
How can?
Verbato said:
IF IT DOESN'T BOOT - DID YOU FASTBOOT ERASE SYSTEM/FASTBOOT ERASE USERDATA?
If you did and it still doesn't want to boot then please report back and I'll make a small change to the ramdisk.
Until there is a Doppler 180, this will be the only kernel with the right layout for this ROM. You could use a regular kernel, but you'd end up with a lot of free space in /system and very little in /data.
Also, minor bug, first time you install the kernel and boot it up wireless won´t work until you reboot. Wireless modules have been added to the ramdisk. But for some reason, the very first time it boots they don´t load. No idea why. Just one of life´s great mysteries I guess. Only happens first time you boot the kernel after installing it.
If you want even more space for installing large programs or even more, insanely many, programs, then I'd recommend you use Mounts2SD. If you download the apk you could even place it in the rom's zipfile inside of /data/app, and it'll be there from first boot! : )
If anyone wants to use this to build something else upon it, feel free!
Click to expand...
Click to collapse
WT19i Lww User : It Doesnt boot.. how can get into cwm if it doesnt boot? already flash coconut kernel, cant get into cwm.. how to erase system on fastboot? can u explain it?
blackpaper07 said:
WT19i Lww User : It Doesnt boot.. how can get into cwm if it doesnt boot? already flash coconut kernel, cant get into cwm.. how to erase system on fastboot? can u explain it?
Click to expand...
Click to collapse
So... Do you use Windows or OSX? There are several guides out there on how to install fastboot.
xda explanation
Explanation on how to install fastboot in windows, with pictures and all
The commands you want to run are, simply:
Code:
fastboot erase userdata
Code:
fastboot erase system
And if you have the kernel in the same folder as fastboot you could also install it like this:
Code:
fastboot flash boot helium-coconut.img
Verbato said:
So... Do you use Windows or OSX? There are several guides out there on how to install fastboot.
xda explanation
Explanation on how to install fastboot in windows, with pictures and all
The commands you want to run are, simply:
Code:
fastboot erase userdata
Code:
fastboot erase system
And if you have the kernel in the same folder as fastboot you could also install it like this:
Code:
fastboot flash boot helium-coconut.img
Click to expand...
Click to collapse
wow this so complicated.. surely cannot install this rom.. only use windows 8.. anywhere thanks..
blackpaper07 said:
wow this so complicated.. surely cannot install this rom.. only use windows 8.. anywhere thanks..
Click to expand...
Click to collapse
Everything you haven't tried before seems complicated. Once you've tried it it isn't so difficult. : )
The last link, with pictures, is really the easiest to use.
Also, it's just a matter of installing a different kernel and your phone is fine again. So no worries. : )
Verbato said:
Everything you haven't tried before seems complicated. Once you've tried it it isn't so difficult. : )
The last link, with pictures, is really the easiest to use.
Also, it's just a matter of installing a different kernel and your phone is fine again. So no worries. : )
Click to expand...
Click to collapse
im not worry about my phone.. already try most all rom in this site for my lww.. but only this kernel need to erase data n format on fastboot.. sometimes hard to learn it.. on the screenshot looks cool.. .. but cant use it..
blackpaper07 said:
im not worry about my phone.. already try most all rom in this site for my lww.. but only this kernel need to erase data n format on fastboot.. sometimes hard to learn it.. on the screenshot looks cool.. .. but cant use it..
Click to expand...
Click to collapse
No, you have to do that with every kernel that uses a different partition layout scheme for the phone. You have to do the same with the doppler kernel (which is where I was inspired to make this, btw). But yeah, I am the first one to make a ROM dependant on this. Saves you a whole lot of space in /data though! : P
blackpaper07 said:
im not worry about my phone.. already try most all rom in this site for my lww.. but only this kernel need to erase data n format on fastboot.. sometimes hard to learn it.. on the screenshot looks cool.. .. but cant use it..
Click to expand...
Click to collapse
you have to do the same with Doppler and CM11 kernels as well, the reason being the partition sizes are modified to give you more space in the /data partition along with the ability to install more apps into the phone's storage rather than on an SD card which you would have to do if using stock partition sizes because you would quickly run out of space on the /data partition after installing only a few apps...
whew! now that's what i call a long sentence! :laugh:
nice.
but one thing.
the stock camera is better than cyber-shot (my experience)
RaphaelHam said:
nice.
Click to expand...
Click to collapse
Thank you : )
RaphaelHam said:
but one thing.
the stock camera is better than cyber-shot (my experience)
Click to expand...
Click to collapse
You think so? I've always liked cyber-shot better. But maybe you're right. : )
i test this rom in my xperia active , whit radeon kernel ,after 2 day everything is good, very fast , just reporting one bug (xperia kybord forc close) i use last version xperia kybord now.
i'm agree whit this frind RaphaelHam stock camera is much more better than cyber-shot.
roxandn said:
just reporting one bug (xperia kybord forc close) i use last version xperia kybord now.
Click to expand...
Click to collapse
Thank you! Of course it only works with mini pro (the one I have), it's made for slide-out-keyboard, and since only mini pro has that the "extra files" for that app, they are only added with the mini pro device files. Fixed now though. : )
Sorry for not realising this sooner.
Also, a minor bug no one has mentioned and hopefully not noticed, the installer-script says "installing mini pro device files" in all the roms. Which isn't true. I just copied everything to every "phone", apart from the device files which are unique for every device. This has been fixed as well, just to prevent any panic.
The device files are VERY important. Which is why I've made a rom for each device rather than a simple click-o-rama, which could lead to a simple mistake. Which could lead to a bit of work. : P
So safety first.
I'm thinking about making a "skeleton" out of this ROM and dumping it in developers. It would be nice to have a simple "skeleton-rom" that can be used to build upon. One that only has what is needed in it (a lot of the files in a lot of the roms are full of stuff and things people either don't realise are there - but unnecessary, or just have no clue what are for and unnecessarily leave in there) and is easy for any developer (or trying-out-making-your-own-rom-developer) to make what ever out of. For instance, there is a file called "dop.iso" in most of the roms /system/etc-directory. Get it? "ISO"? It's a CD-file. With a Windows program. Meant to be used in Windows. Not needed for android. Really not. Doesn't take up much space, 1.8Mb, but still. Unnecessary file. And then we have a lot of copies of "toolbox" in /system/bin, called chown, chmod, etc. Which is silly, because most scripts make symlinks to toolbox in /system/bin with those names anyways, so they just take up space, a lot of space! Better still, make symlinks to busybox instead (like I have done). Now I've even edited the ramdisks so /system/xbin is first in path. Means that busybox is found first and any command run in shell uses busybox (like ls, which now gives pretty colours!).
So... in all, there is a lot of space that could be saved. Next thing is finding out of how to save space in /system/lib... Hmmm...
Oh, well. ROMs are updated. I've moved to MediaFire btw. d-h.st didn't want to work properly on upload (the files didn't show up at all!). MediaFire has a nice upload-resume if anything goes wrong. So, MediaFire it is. Also, MediaFire doesn't delete the files if they aren't downloaded by someone within so and so a long time. Also, ramdisks are updated as well. Just a tiny change to path. That's all.
Verbato said:
Thank you! Of course it only works with mini pro (the one I have), it's made for slide-out-keyboard, and since only mini pro has that the "extra files" for that app, they are only added with the mini pro device files. Fixed now though. : )
Sorry for not realising this sooner.
Also, a minor bug no one has mentioned and hopefully not noticed, the installer-script says "installing mini pro device files" in all the roms. Which isn't true. I just copied everything to every "phone", apart from the device files which are unique for every device. This has been fixed as well, just to prevent any panic.
The device files are VERY important. Which is why I've made a rom for each device rather than a simple click-o-rama, which could lead to a simple mistake. Which could lead to a bit of work. : P
So safety first.
I'm thinking about making a "skeleton" out of this ROM and dumping it in developers. It would be nice to have a simple "skeleton-rom" that can be used to build upon. One that only has what is needed in it (a lot of the files in a lot of the roms are full of stuff and things people either don't realise are there - but unnecessary, or just have no clue what are for and unnecessarily leave in there) and is easy for any developer (or trying-out-making-your-own-rom-developer) to make what ever out of. For instance, there is a file called "dop.iso" in most of the roms /system/etc-directory. Get it? "ISO"? It's a CD-file. With a Windows program. Meant to be used in Windows. Not needed for android. Really not. Doesn't take up much space, 1.8Mb, but still. Unnecessary file. And then we have a lot of copies of "toolbox" in /system/bin, called chown, chmod, etc. Which is silly, because most scripts make symlinks to toolbox in /system/bin with those names anyways, so they just take up space, a lot of space! Better still, make symlinks to busybox instead (like I have done). Now I've even edited the ramdisks so /system/xbin is first in path. Means that busybox is found first and any command run in shell uses busybox (like ls, which now gives pretty colours!).
So... in all, there is a lot of space that could be saved. Next thing is finding out of how to save space in /system/lib... Hmmm...
Oh, well. ROMs are updated. I've moved to MediaFire btw. d-h.st didn't want to work properly on upload (the files didn't show up at all!). MediaFire has a nice upload-resume if anything goes wrong. So, MediaFire it is. Also, MediaFire doesn't delete the files if they aren't downloaded by someone within so and so a long time. Also, ramdisks are updated as well. Just a tiny change to path. That's all.
Click to expand...
Click to collapse
I had actually seen that ISO file and wondered WTF it was doing inside a ROM, then thought it must be there for a reason and let it be :laugh:
It would actually be great to have a cleaned up skeleton ROM, I'd use it as is (or maybe after deleting a few .APKs from within ) because theoretically, the less clutter the more free resources and the longer the battery life (I hope ) right?
rahimali said:
the less clutter the more free resources and the longer the battery life (I hope ) right?
Click to expand...
Click to collapse
The fewer services run at the same time, the less use there is of the CPU and the less battery it uses. Also, you could download CPU Adjuster (free) and undervolt the CPU. On mine I can make it stable at 750 between 134400 to 364800, 875 between 460800 to 768000 (but as always, your mileage may wary). That makes a whole world of difference in lasting time for the battery. What's stable beyond that depends on how lucky you are with your CPU. Trial and error.
Also, CPU Adjuster lets you have different clock speed settings depending on whether your phone is charging, discharging or in a call (or a whole lot of other circumstances, but I only use charging and discharging). So I don't use any higher clock setting than 768kHz when not charging and 1.4MHz when charging.
Sounds technical. Is really easy when you install and use CPU Adjuster.
Plz fix xperia keyboard bug for lww
Sent from my WT19i using xda premium
Good work @Verbato
dop.iso is for pc companion installation....
AFAIK ,you are compiling modified master branch of Kappa.
Before(or after your edits) use .
Code:
git cherry-pick 04516aaab7f7fe0fa248a07f73c051551c68a6e8
This is the battery bug patch of @kast in Kappa 1.7/Lite branch.
Win win for people
Also fork kappa officially and provide the links to source to comply with GPL.
Including the defconfigs you use :angel:
karandpr said:
AFAIK ,you are compiling modified master branch of Kappa.
Click to expand...
Click to collapse
I am using whatever git clone git://github.com/KaSt/Kappa is giving me.
karandpr said:
Before(or after your edits) use .
Code:
git cherry-pick 04516aaab7f7fe0fa248a07f73c051551c68a6e8
This is the battery bug patch of @kast in Kappa 1.7/Lite branch.
Click to expand...
Click to collapse
Thank you! That would really help a lot! : )
But... :-/
From a fresh git clone:
Code:
$ git cherry-pick 04516aaab7f7fe0fa248a07f73c051551c68a6e8
error: could not apply 04516aa... I2C Fixes for 100% Battery bug
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Any idea why it doesn't work? (AKA "What am I doing wrong?" : P )
karandpr said:
Win win for people
Also fork kappa officially and provide the links to source to comply with GPL.
Including the defconfigs you use :angel:
Click to expand...
Click to collapse
: )
Will do!