Related
Just picked up three Gtablets yesterday, and immedialty loaded up Vegan 5.1; my question is how do I go about changing the kernal in order to overclock? I went over to this thread
[Kernel] 2.6.32.38 - OC-UV-VFP_FP (1.400GHZ) - Gtab/Zpad (Update 4/20/11);
and started reading up on it, but it gets to be a little confusing. Also, I see no guides on how to install a custom kernal. Do I just do it in CWM
I went to this link http://droidbasement.com/db-blog/, and it says to flash zip through recovery, but there are a ton of files on that site; than it says
To use one of the kernel modules:...do a bunch of stuff.
I am a bit confused here as to what I need to do to get a custom kernal with Vegan 5.1.1; Can someone point me in a direction?
VEGAn 5.1 is Froyo (Android 2.2) based, so you want to download this kernel from that page:
ViewSonic Gtab/Malata Zpad (Froyo):
boot-cm_2632.38-oc-uv-xtra-vfpv3_fp-042011.zip
Download: boot-cm_2632.38-oc-uv-xtra-vfp_fp-042011.zip
As to how to install it, you just flash it in clockwork mod, the same way you installed VEGAn 5.1 on your tablet (place the file on the "sdcard", go into clockwork mod, go to install zip from sdcard, then choose to install the kernel file).
For the stuff about the kernel modules, it requires knowledge of how to use adb shell, which is a little bit complicated, so I wouldn't worry about it. The modules aren't necessary, they just add a few additional functions and settings to the kernel. You'll still be able to overclock without installing the modules. Hope this helps.
Modules without ADB
Not that it matters completely, but you can push modules to the kernel without using ADB. If you have Root Explorer, you can mount the correct subdirectory as RW, copy the files there, then use terminal emulator to chmod and insmod per Pershoot's other instructions.
raphenucleus said:
VEGAn 5.1 is Froyo (Android 2.2) based, so you want to download this kernel from that page:
ViewSonic Gtab/Malata Zpad (Froyo):
boot-cm_2632.38-oc-uv-xtra-vfpv3_fp-042011.zip
Download: boot-cm_2632.38-oc-uv-xtra-vfp_fp-042011.zip
As to how to install it, you just flash it in clockwork mod, the same way you installed VEGAn 5.1 on your tablet (place the file on the "sdcard", go into clockwork mod, go to install zip from sdcard, then choose to install the kernel file).
For the stuff about the kernel modules, it requires knowledge of how to use adb shell, which is a little bit complicated, so I wouldn't worry about it. The modules aren't necessary, they just add a few additional functions and settings to the kernel. You'll still be able to overclock without installing the modules. Hope this helps.
Click to expand...
Click to collapse
Thanks for the quick reply....I feel like a noob.....do I need to wipe before or after install? And what program do you prefer for overclocking? And what settings?
michaeljwestii said:
Not that it matters completely, but you can push modules to the kernel without using ADB. If you have Root Explorer, you can mount the correct subdirectory as RW, copy the files there, then use terminal emulator to chmod and insmod per Pershoot's other instructions.
Click to expand...
Click to collapse
What are the benefits to the kernels?
PhilPan said:
Thanks for the quick reply....I feel like a noob.....do I need to wipe before or after install? And what program do you prefer for overclocking? And what settings?
Click to expand...
Click to collapse
When flashing new kernels, it's recommended to wipe the cache partition and wipe the dalvik cache before flashing the new kernel. I do this every time to be safe, but I don't know how important it really is. I've forgotten to do it on occasion and didn't notice any problems.
I use setcpu to set the cpu range and also use it to turn down the max cpu to 216 MHz when the screen is off to save battery. The range I use is 216 to 1000 MHz. I don't overclock, because I've found it to be fast enough without it and overclocking can decrease your battery life. But I'd say try out various frequency ranges and see what you like the best.
would nvflashing back to stock 3588 FW change the kernals back to original?
yes, flashing any rom will flash the kernel for that rom.
Is there a way to Backup and Restore Original Shipped Firmware? Is we have Norton Ghost for Android then it will be good...
The purpose is to claim the phone for warranty, after flashed with customized firmware. The phone's hardware might go fault.
Well as a previous sgs user I know that the best way is to have root on ur device then u can access cwm to create a complete image (backup) of ur current os.
I don't know if there is a better way of doing so
Cheers
Sent from my GT-I9100 using Tapatalk
A lot of branded roms are posted in the Branded rom post in dev section .
jje
For an own backup, exactely as you bought the phone, here's what I did:
- flash an insecure kernel (stock kernels are available for all FWs, so restoring original stock kernel is easy)
- apply root
- dump all important partitions:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
As a more easy/convinient alternative you could flash a kernel with a custom recovery (like CF-Root, containing CWM recovery) and use the Nandroid backup feature from the recovery menu - but those root-kernels usually perform a few more changes on the /system partition, so I did my "initial stock backup" just using an insecure kernel and root applied.
HellcatDroid said:
For an own backup, exactely as you bought the phone, here's what I did:
- flash an insecure kernel (stock kernels are available for all FWs, so restoring original stock kernel is easy)
- apply root
- dump all important partitions:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
As a more easy/convinient alternative you could flash a kernel with a custom recovery (like CF-Root, containing CWM recovery) and use the Nandroid backup feature from the recovery menu - but those root-kernels usually perform a few more changes on the /system partition, so I did my "initial stock backup" just using an insecure kernel and root applied.
Click to expand...
Click to collapse
Thanks for the advice! I have a question regarding Nandroid and CWM. Restoring the image made with Nandroid is easy enough, but won't the carrier/Samsung detect that a custom recovery (CWM) has been installed and consider it voiding the warranty regardless of the stock ROM being on the device?
Thanks in advance.
techjunkieza said:
Restoring the image made with Nandroid is easy enough, but won't the carrier/Samsung detect that a custom recovery (CWM) has been installed and consider it voiding the warranty regardless of the stock ROM being on the device?
Click to expand...
Click to collapse
After restoring a stock backup via a custom recovery/nandroid, just flash a stock kernel afterwards with Odin as well.
That will restore kernel and the recovery back to stock too.
All that is then left from a rooting is two files and a few symlinks hidden in /system/xbin - unlikely they'll go and check that IMO.
HellcatDroid said:
After restoring a stock backup via a custom recovery/nandroid, just flash a stock kernel afterwards with Odin as well.
That will restore kernel and the recovery back to stock too.
All that is then left from a rooting is two files and a few symlinks hidden in /system/xbin - unlikely they'll go and check that IMO.
Click to expand...
Click to collapse
Thanks dude. I was wondering how it is done. I did not know that flashing a stock kernel will make the recovery mode default as well. I'm new to Android so please forgive the noob questions. Surely there should be a list of files in a thread somewhere which indicates which files are modified when rooting the phone?
So I take it by restoring the original ROM, flashing a stock kernel (if you have a custom recovery mode or root access), removing the files and symlinks and resetting the ROM counter that the phone will be "stock" again?
techjunkieza said:
Thanks dude. I was wondering how it is done. I did not know that flashing a stock kernel will make the recovery mode default as well. I'm new to Android so please forgive the noob questions.
Click to expand...
Click to collapse
He, I had to learn all this myself recently, the SGS2 is my first Android device as well
For the SGS2 the recovery mode is part of the main kernel (partition), so flashing a stock kernel replaces that as well.
AFAIK this a unique Samy thing, on the other Android devices the recovery actually resides on its own partition.
techjunkieza said:
Surely there should be a list of files in a thread somewhere which indicates which files are modified when rooting the phone?
So I take it by restoring the original ROM, flashing a stock kernel (if you have a custom recovery mode or root access), removing the files and symlinks and resetting the ROM counter that the phone will be "stock" again?
Click to expand...
Click to collapse
Depending on how you rooted it's just /system/xbin/su that gets replaced and /system/xbin/busybox that gets added.
Then all the symlinks busybox installs - not sure if busybox has an "uninstall" option to remove them, if not just dump all symlinks in /system/xbin, on stock FWs there are none in this dir.
HellcatDroid said:
He, I had to learn all this myself recently, the SGS2 is my first Android device as well
For the SGS2 the recovery mode is part of the main kernel (partition), so flashing a stock kernel replaces that as well.
AFAIK this a unique Samy thing, on the other Android devices the recovery actually resides on its own partition.
Click to expand...
Click to collapse
Thanks a lot for the advice. I see many people asking the same questions but no one really gives them answers. I'm guessing it's betterfor it to be on two different partitions in terms of coupling. For noobs, the Samsung way is easier.
HellcatDroid said:
Depending on how you rooted it's just /system/xbin/su that gets replaced and /system/xbin/busybox that gets added.
Then all the symlinks busybox installs - not sure if busybox has an "uninstall" option to remove them, if not just dump all symlinks in /system/xbin, on stock FWs there are none in this dir.
Click to expand...
Click to collapse
Great. Thanks. I would like to know what Android does on a low level in order to gain root access. I'm going to research that a bit.
Thanks very much for the info!
techjunkieza said:
I would like to know what Android does on a low level in order to gain root access. I'm going to research that a bit.
Click to expand...
Click to collapse
Well, once one knows what happens it's not that much magic that happens.
Basically, the stock su gets replaced with a custom one that actually has a way of allowing other user (IDs) to run as root, Superuser.apk is installed to maintain su's database of allowed (and disallowed) user IDs and last not least busybox is installed to gain some shell commands not available (or limited) on stock.
All that is done via an adb daemon (already) running with root perms - that's what the insecure kernels do, they simply let the adbd run with root perms (so the above things can be done).
Each app running has it's unique, own user ID it's running with, so root access/permissions can easiely be maintained that way.
I hope that was what you wanted to know
HellcatDroid said:
Well, once one knows what happens it's not that much magic that happens.
Basically, the stock su gets replaced with a custom one that actually has a way of allowing other user (IDs) to run as root, Superuser.apk is installed to maintain su's database of allowed (and disallowed) user IDs and last not least busybox is installed to gain some shell commands not available (or limited) on stock.
All that is done via an adb daemon (already) running with root perms - that's what the insecure kernels do, they simply let the adbd run with root perms (so the above things can be done).
Each app running has it's unique, own user ID it's running with, so root access/permissions can easiely be maintained that way.
I hope that was what you wanted to know
Click to expand...
Click to collapse
Basically, yes! You definitely deserve a thanks for all of this. I was looking for information of what you just described but couldn't find anything. Shot dude!
how to reset counter without the USB jig ?
You don't.
Best you can do is getting rid of the triangle by flashing a stock kernel, but to reset the counter you really need the USB jig.
Great post! I cannot find a clear answer to these questions as well:
1. What is the location of the so called "boot loader" and how to make a backup? On Intel architecture it's on the first few sectors of the disk block device.
2. What is the location of the "ODIN mode/Download mode" application and how to make a backup? I suspect it may be in some read only memory and there is nothing to backup?
3. What is the location of the partition table? How to backup?
I want to understand the real/core/linux/android way of doing these, not just blindly running arbitrary tools.
Thanks in advance.
HellcatDroid said:
You don't.
Best you can do is getting rid of the triangle by flashing a stock kernel, but to reset the counter you really need the USB jig.
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=1494114
I already did it on my SII running ICS 4.0.3, worked great!..., but..., read the thread and cross your fingers...
gingingingin said:
1. What is the location of the so called "boot loader" and how to make a backup? On Intel architecture it's on the first few sectors of the disk block device.
2. What is the location of the "ODIN mode/Download mode" application and how to make a backup? I suspect it may be in some read only memory and there is nothing to backup?
3. What is the location of the partition table? How to backup?
Click to expand...
Click to collapse
1, 2 and 3: they are outside of the normal partitioned space / on hidden partiions (the bootloader partition is visible in ICS though) and you should not touch them.
Backing them up is useless as when the bootloaders are corrupted/broken, you'll have no way to restore them anyways as no bootloader == no boot to run anything, hence no restoring.
One is advised to leave them alone and not touch them - usually you can't access them anyways.
2: "Download Mode" is part of the secondary bootloader (partitions /dev/block/mmcblk0p2 and mmcblk0p3).
Hence the inability to access Download Mode when the bootloaders are broken.
Does it mean that "Download Mode" can be corrupt by overwriting this secondary bootloader? What about the the primary one? Is this a sure way for "hard bricking"? I was always wondering is there a way to completely lock yourself out of SGS2, but could not get a conclusive answer in the forum. Or you can recover from any failure by having any single piece backed up?
What do update packages mean when they contain a bootloader update - is it primary or secondary bootloader, or both?
You didn't say about the location of the partition table, although it's quite often part of the updates to have a PIT file with a new layout?
And last but not least, what is the basic sequence to recover from a partition based raw backup, like the one we're discussing in the thread?
Regards,
Anton
Upon searching through various XDA forum threads, many youtube videos and other Android based websites. I finally decided to actually make a thread to help gain a better insight into what I want to do.
So, as I'm posting in this particular forum you can imagine I have a Galaxy Tab 10.1 Wifi Only [GT-P7510] Running Android Version 3.1 and I would assume I'm running the stock kernel.
I've already rooted the tab, using Odin and CWM of which are probably the only things I am a little bit familiar with. Im only really following instructions with next to no knowledge of the Android OS. I essentially want to maximise the use of my tablet but as there's so many different resources with custom roms and kernels. It's hard to figure out whats best and why it's better than another to fully utilise my tablet.
I want to run ICS on my tab, and I've been told "Pershoots" ' is the 'best' kernel around. Though how I do this, I really don't know. So, if you don't mind, here are my questions ;
-In order to put a different Rom & Kernel onto my tablet, Do I need to have them both flashed through Odin at the same time for it to work?
-Does the kernel and rom have to be specifically compatible with eachother or can you essentially mix and match them?
- Will certain kernels work across different Android devices?
- Are the Custom Rom builds specific to 3g versions (Or would they work on the device as a whole regardless of 3g/wifi?)
- Will I need to put it into downloading mode to put them onto the tab, and recovery after through CWM to use them like I did for the rooting process?
Thanks in advance for your time!
Sam, Android Novice.
Flash in recovery.
Download the latest SetCPU from this thread:
http://forum.xda-developers.com/showthread.php?t=505419
Launch it, accept root allowance and select autodetect.
ondemand will be the default governor
To install kernel modules:
Use Winrar (windows) or tar with the z option and unpack lib-2636.4.tar.gz
Push any module you desire to /data/local/modules (this is created by the update.zip)
Then, insmod it (you can do this via adb, in a gscript, or on the device in terminal.
Note:
-If you want to enable usb charging:
adb shell echo 1 > /sys/class/power_supply/battery/force_usb_charging
To disable:
adb shell echo 0 > /sys/class/power_supply/battery/force_usb_charging
Flash in recovery.
Download the latest SetCPU from this thread:
http://forum.xda-developers.com/showthread.php?t=505419
Launch it, accept root allowance and select autodetect.
ondemand will be the default governor
http://droidbasement.com/db-blog/
@Sam,
I too am new to the SGT, and looking for a clear path to ICS.
I have done a boatload of reading and feel I have a pretty decent understanding of how to do this, I can give you some answers to your questions to the best of my knowledge, but would also greatly appreciate some outside clarification.
A: To put a new ROM on your device:
There are two ways to get zip files on your device. 1. Download a file on your computer and connect the tab with the usb cable and drag/drop it onto the root of the device. or 2. Download the file using the SGT directly from the site, in this case you will want to move the file from the download folder to the root of the sd so you can find the zip easily once in CWM
Download the ROM you would like to install, make sure it is for the same android version you are currently on. (don't use a HC 3.2 ROM if you are on HC 3.1) Back up your apps with Titanium Backup > Boot your device into CWM (this is NOT download mode, you will not be connected to a computer) > Make a nandroid backup of your current ROM setup, just in case something goes wrong, you will be able to go back into CWM and restore your device with this back up > next do all the appropriate wipes per the Dev's instructions. > Go to install zip > Choose zip > Navigate to the zip file you want to intall > Install zip >Reboot > Sign in and set up your device on your new ROM
A: Kernels: Some ROMS will already have a custom kernel built into the ROM. Some will use the STOCK kernel.
You may NOT mix and match kernels at will, make sure the kernel you want to use is compatible with the ROM you are using.
You can then flash the kernel in CWM through the install zip process.
I don't think you can use kernels across different devices, but I am not sure.
A: Odin: As I understand it, You will only use Odin to install different CWM Recoveries or to flash a stock ROM if for some reason you have borked your device and can't get to CWM through the power menu
My Questions for a path to ICS
Q: 1. I am running Galaxy Task 13.1 Rom with Pershoot kernel. In order to Flash ICS I need to be using the latest CWM 5.0.2.7 correct?
2. In order to flash the new recovery, do I need to revert back to the stock kernel? If so, can I use the stock kernel found in the second post of the Task thread and flash in CWM the same as when I did Pershoot's
3. Would I be better off just restoring my stock rooted nandroid, and then ODIN flash the CWM 5.0.2.7 to that and then Flash ICS from there.
4. Once on new recovery, I will not be able to restore any nandroids from previous version and should I then want to go back to Task, I will have to just flash the ROM as a fresh install and then create new nandroids to use from there on?
Thanks
D
dxh3378 said:
@Sam,
My Questions for a path to ICS
Q: 1. I am running Galaxy Task 13.1 Rom with Pershoot kernel. In order to Flash ICS I need to be using the latest CWM 5.0.2.7 correct?
2. In order to flash the new recovery, do I need to revert back to the stock kernel? If so, can I use the stock kernel found in the second post of the Task thread and flash in CWM the same as when I did Pershoot's
3. Would I be better off just restoring my stock rooted nandroid, and then ODIN flash the CWM 5.0.2.7 to that and then Flash ICS from there.
4. Once on new recovery, I will not be able to restore any nandroids from previous version and should I then want to go back to Task, I will have to just flash the ROM as a fresh install and then create new nandroids to use from there on?
Thanks
D
Click to expand...
Click to collapse
ok guys....flashing ICS can be done on top of anything...don't need root either.
1. Get the ICS and Gapps zip on the tablet
2. Flash CWM (unless you already have it)
3. wipe data
4. flash both
5. done
nothing really too complicated
no version requirements nothing.
hope this helps
as for nandroid things
yeah made a nandroid backup on whatever recovery you are on now..nothing will change after you flash ICS...you will still be able to restore anything.
To install kernel modules:
Use Winrar (windows) or tar with the z option and unpack lib-2636.4.tar.gz
Push any module you desire to /data/local/modules (this is created by the update.zip)
Then, insmod it (you can do this via adb, in a gscript, or on the device in terminal.
Note:
-If you want to enable usb charging:
adb shell echo 1 > /sys/class/power_supply/battery/force_usb_charging
To disable:
adb shell echo 0 > /sys/class/power_supply/battery/force_usb_charging
Click to expand...
Click to collapse
That stuff went right over my head, I imagine less jargon would be helpful too haha.
I am trying to go back to stock ROM and use the Bares' Init.d Scripts Using Stock Kernel (V3).
I reflashed the stock GB ROM using flashtool, rooted and installed xrecovery 0.3. After that, I installed Bares' INIT-D-RUNNER-TWEAKS-V3.zip using xrecovery and rebooted. When ever I try to use wifi I get "Error" just below the toggle to turn it on and i does not work.
It seems like someone else had this problem, but Bares says tha wifi errors shouldn't happen, see:
http://forum.xda-developers.com/showthread.php?t=2174564&highlight=wifi
I tried reinstalling three times (install original ROM and after that apply the Init.d scripts) in an unlocked bootloader X10. I then relocked the boot loader and tried again and I still get wifi problems.
Anyone else having problems like this? Is there a work around?
Obs: I could not post in the original threas as I am a newbie here and I am not allowed to post in the development section.
pjssilva said:
I am trying to go back to stock ROM and use the Bares' Init.d Scripts Using Stock Kernel (V3).
I reflashed the stock GB ROM using flashtool, rooted and installed xrecovery 0.3. After that, I installed Bares' INIT-D-RUNNER-TWEAKS-V3.zip using xrecovery and rebooted. When ever I try to use wifi I get "Error" just below the toggle to turn it on and i does not work.
It seems like someone else had this problem, but Bares says tha wifi errors shouldn't happen, see:
http://forum.xda-developers.com/showthread.php?t=2174564&highlight=wifi
I tried reinstalling three times (install original ROM and after that apply the Init.d scripts) in an unlocked bootloader X10. I then relocked the boot loader and tried again and I still get wifi problems.
Anyone else having problems like this? Is there a work around?
Obs: I could not post in the original threas as I am a newbie here and I am not allowed to post in the development section.
Click to expand...
Click to collapse
Hi bro, we need to edit install-recovery.sh script inside zip to include wifi module, please refer to HERE.
So, please use this zip, just flash it through Xrecovery, then it should be fine.
FYI
Regards
It didn't work out
Bares said:
Hi bro, we need to edit install-recovery.sh script inside zip to include wifi module, please refer to HERE.
So, please use this zip, just flash it through Xrecovery, then it should be fine.
FYI
Regards
Click to expand...
Click to collapse
First, thanks Bares for ansewring fast. But I am sorry to say that I did not succeed. First, I tried to simply add the line
insmod /system/lib/modules/wifi.ko
in the middle of install-recovery.sh and it didn't work out. I thought the reason was that I did not add the wiki.ko file to /system/lib/modules in the generated zip and started to look for it. I found the following the stock wifi modules from here. I got the modules from the x10_gb_stock_wifi_modules.zip file and added them to my tweaked INIT.D zip but it didn't work out. Anything that I am missing?
pjssilva said:
First, thanks Bares for ansewring fast. But I am sorry to say that I did not succeed. First, I tried to simply add the line
insmod /system/lib/modules/wifi.ko
in the middle of install-recovery.sh and it didn't work out. I thought the reason was that I did not add the wiki.ko file to /system/lib/modules in the generated zip and started to look for it. I found the following the stock wifi modules from here. I got the modules from the x10_gb_stock_wifi_modules.zip file and added them to my tweaked INIT.D zip but it didn't work out. Anything that I am missing?
Click to expand...
Click to collapse
Hmmm..., this problem could be happened if the rom wasn't settled properly too.
So, please try these steps (exactly) :
- Revert back to stock and setup the phone.
- Root it with the latest Flashtool and choose SuperSU !!!
- Install Xrecovery and let the rom settled first !!!
- Check an everything including wifi !!!.
- If its all working good then flash my script (see the thread for the latest one) through xrecovery and dont get rush on the first 2~3 reboot.
- And check the result.
Regards
It still does not work
Bares said:
Hmmm..., this problem could be happened if the rom wasn't settled properly too.
So, please try these steps (exactly) :
- Revert back to stock and setup the phone.
- Root it with the latest Flashtool and choose SuperSU !!!
- Install Xrecovery and let the rom settled first !!!
- Check an everything including wifi !!!.
- If its all working good then flash my script (see the thread for the latest one) through xrecovery and dont get rush on the first 2~3 reboot.
- And check the result.
Regards
Click to expand...
Click to collapse
I tried as you suggested and it didn't work. I tried both with your V4 scripts and with my modified version to include the "insmod /system/lib/modules/wiki.ko". Both did not work after some time to settle the original ROM (with 3 reboots) and some time to settle the modified ROM (3 more reboots).
I have also tried your new STOCK-GB-MOD-RELOAD.zip update file, but it didn't work either.
One thing I noticed is that your original update files delete the wifi.ko module from the /system/lib/modules directory that exists in the stock ROM. I even copied wifi.ko to my computer and cried an small zip that can be flashed by xrecovery to restore that file, but it is not enough to get it working. I tried to read your INIT-D-RUNNER-TWEAKS-V4 to see what it was doing but I did not understand how it changes wifi (I could not even find out where wiki.ko wasw being deleted).
It is a really shame, as your new STOCK-GB-MOD-RELOAD.zip looks exactly as what I wanted.
Anything else I should try?
pjssilva said:
I tried as you suggested and it didn't work. I tried both with your V4 scripts and with my modified version to include the "insmod /system/lib/modules/wiki.ko". Both did not work after some time to settle the original ROM (with 3 reboots) and some time to settle the modified ROM (3 more reboots).
I have also tried your new STOCK-GB-MOD-RELOAD.zip update file, but it didn't work either.
One thing I noticed is that your original update files delete the wifi.ko module from the /system/lib/modules directory that exists in the stock ROM. I even copied wifi.ko to my computer and cried an small zip that can be flashed by xrecovery to restore that file, but it is not enough to get it working. I tried to read your INIT-D-RUNNER-TWEAKS-V4 to see what it was doing but I did not understand how it changes wifi (I could not even find out where wiki.ko wasw being deleted).
It is a really shame, as your new STOCK-GB-MOD-RELOAD.zip looks exactly as what I wanted.
Anything else I should try?
Click to expand...
Click to collapse
Hi bro,
The last options is by remove these 2 lines below from instal-recovery.sh script inside zip provided (STOCK-GB-MOD-RELOAD.zip) :
HTML:
#init.d runner
busybox run-parts /system/etc/init.d/
BUT, ... the problem is : you will lost init.d runner for Stock Kernel, and it cause all tweaks will not run for sure.
The result is the rom will feel a bit slower than it should be.
Note : To be honest, i'm little bit confusing here, because everything should be fine.
OR : Use custom kernel for Locked Bootloader ( Doomkernel V6 for Locked Bootloader).
OR :
Just simply unlock the bootloader (it's really safe, but you have to follow the proper procedure on this), the simply procedure is :
- Revert back to Stock Rom using PC Companion or SEUS or Flashtool (Download the latest Flashtool Version (see the thread about how to unlock for more detail info, read it carefully!!!)., and then unlock your bootloader using this Flashtool.
Note :
Don't assume if got doubt about this.
- Flash custom kernel using above Flashtool (DoomKernel V6 integrated Bootmanager V2 Auto Rooted by Championswimmer is my recommendation) , because it's using Original Sony's boot splash logo.
- Flash above zip (STOCK-GB-MOD-RELOAD.zip) through Xrecovery.
- Finally you have to flash wifi modul for above kernel (find it on DoomLord's Thread).
Hope this help
Regards
Intalling another kernel does not work...
Hi,
I had a version with a prestine Stock + STOCK-GB-MOD-RELOAD.zip[/B] through Xrecovery. And I installed championswimmer kernel on top of it (thinking it would restore wi-fi) and it didn't work. That is realluy strange. I am starting to fear that the problem is with my X10 (it has some odd behaviors, like it always become slow when using a Ferakernel).
I'll try your first suggestion (turn off init.d scripts) and let you know how it went here.
Anyhow, great thanks!
Improvement
pjssilva said:
Hi,
I had a version with a prestine Stock + STOCK-GB-MOD-RELOAD.zip[/B] through Xrecovery. And I installed championswimmer kernel on top of it (thinking it would restore wi-fi) and it didn't work. That is realluy strange. I am starting to fear that the problem is with my X10 (it has some odd behaviors, like it always become slow when using a Ferakernel).
I'll try your first suggestion (turn off init.d scripts) and let you know how it went here.
Anyhow, great thanks!
Click to expand...
Click to collapse
I tried to turn off init.d scripts and it didn't work!
It was getting into my nerves. So I decided to look inside your INIT-D-RUNNER-TWEAKS-V4.zip file to see if something was weird to me. I am an old Linux desktop user and it looked very strange a line in the update-script script inside META-INF/com/google/android:
delete_recursive SYSTEM:etc/init.d
This woudl delete the whole /etc/init.d directory, somthing that looks very dangerous from a desktop user. So I just commented it and created a new zip file (allowing the copy of your custom init.d scripts, just avoid the full deletion before hand). I was sure it would not work, but it did... Wifi is working after I install this new zip.
I plan now to take a close look at exactly what files are being deleted to find out what should remain in order to keep wifi working in my phone. I'll let you know when I get it right. Now I have to leave as real life is calling me!
I found a solution
I found the problem an the solution.
Just after installing the stock rom, rooting, and installing xrecovery, there is a single file in /system/etc/init.d. It is called 00modules (see attachment). It looks like it create symlinks from the currect kernel modules to /system/lib/modules. This file is essential to get wifi working in my X10.
Since Bare's mods, like STOCK-GB-MOD-RELOAD.zip, delete all the files in there I end up without wifi after installing them.
The solution is simple. Just add this file to STOCK-GB-MOD-RELOAD.zip in "system/etc/init.d". It will them be copied back after being erased. Wifi works and I get Bare's mod fully functional.
Thanks Bares fo your mod!
pjssilva said:
I found the problem an the solution.
Just after installing the stock rom, rooting, and installing xrecovery, there is a single file in /system/etc/init.d. It is called 00modules (see attachment). It looks like it create symlinks from the currect kernel modules to /system/lib/modules. This file is essential to get wifi working in my X10.
Since Bare's mods, like STOCK-GB-MOD-RELOAD.zip, delete all the files in there I end up without wifi after installing them.
The solution is simple. Just add this file to STOCK-GB-MOD-RELOAD.zip in "system/etc/init.d". It will them be copied back after being erased. Wifi works and I get Bare's mod fully functional.
Thanks Bares fo your mod!
Click to expand...
Click to collapse
Oooops, OMG i really really... forgot to include it, i though i was .
Really sorry, will update my script immediately, thanks you so much bro :good:.
Best Regards
[email protected]
---------- Post added at 07:49 AM ---------- Previous post was at 07:38 AM ----------
pjssilva said:
I tried to turn off init.d scripts and it didn't work!
It was getting into my nerves. So I decided to look inside your INIT-D-RUNNER-TWEAKS-V4.zip file to see if something was weird to me. I am an old Linux desktop user and it looked very strange a line in the update-script script inside META-INF/com/google/android:
delete_recursive SYSTEM:etc/init.d
This woudl delete the whole /etc/init.d directory, somthing that looks very dangerous from a desktop user. So I just commented it and created a new zip file (allowing the copy of your custom init.d scripts, just avoid the full deletion before hand). I was sure it would not work, but it did... Wifi is working after I install this new zip.
I plan now to take a close look at exactly what files are being deleted to find out what should remain in order to keep wifi working in my phone. I'll let you know when I get it right. Now I have to leave as real life is calling me!
Click to expand...
Click to collapse
I create this line below :
delete_recursive SYSTEM:etc/init.d
Just to make sure no additional tweaks on init.d (and this is for users that don't want to fresh install the rom) , so the rom will 100% run with my files, just is't.
BTW, thanks a lot for the finding bro :good:. I have update my script to the FINAL one (see my thread), and it seem will be no more update after this one.
FYI
Best Regards
Hello everyone.
Guys, I am interested in turn the stock rom of my phone in a ready-to-install rom. I mean, roms usually are .zip files with scripts that writes the customized files to the system file, overwriting the old files. I want to know how to take the stock rom of my phone and turn it in a intallable .zip file, like a customized rom.
After a normal installing the phone would be like the phone with the original rom, without changes. Do you know what I mean?
I am interested in this for make changes and costumizations in the stock rom for then reinstall it. Normally, rom porting is made by taking a compatible rom (like CM) and taking the wished to port rom and changing directories like /system, /data, etc... Am I right? Well, if a would take the original rom of my phone and would turn it in a installable .zip, I could make ports, right?
Well, this is my doubt, how can I do this?
Up.
What's wrong? No one cares about?
Noob reporting here !
You can start by installing ADB (from android sdk).
When you have ADB correctly installed , you can "rip" your phone's complete /system partition by using the "adb pull /system system/" command.
This will rip /system to a subfolder called "system" (example c:/adb/adb.exe -> c:/adb/system)
I haven't come further myself, as i`m also in the learning (reading) phase.
you can use dsixda's kitchen for that, just use a firmware file for your phone, and extract that using the kitchen, after that you can use it to make a zip file