Related
Im on EB01 and i didnt remove voodoo when i was in DL09. and im trying to remove voodoo by doing making disable_lagfix folder in sd/voodoo folder. But it didnt work. and there was way of doing the adb thing and idk how to do it. can anyone tell me or teach me how to disable voodoo step by step? please. because of this i cant download anything. it says my phone memory is 0.00B. thank you. i appriciate it
If its voodoo 5 its a option in cwm.. The red one..then reboot
Rocking dj05 and jt's voodoo 5
[HOWTO] Completely Remove Voodoo Lagfix
I think this is what you are looking for.
[HOWTO] Completely Remove Voodoo Lagfix
You don't create a folder. You need to create a FILE
Sent from my Samsung Fascinate
what do u mean as in file? what kind of file? doc? txt?
There is no file extension when creating the "disable_lagfix".
1) Create a new txt document.
2) Name it "disable_lagfix". It will tell you that it will no longer be useable, blah blah. Just accept.
3) Then move it in to the voodoo folder on the sd card.
4) Reboot phone. It will take a while at reboot to un-voodoo the phone. This is normal.
Done.
I could be wrong, but I'm pretty sure the filename needs to be .disable_lagfix (notice the dot at the beginning). Oh, and the file is just an empty file, no particular format. You can create one easily with Root Explorer. If you don't have Root Explorer, I suggest buying it, as it makes it much easier to work with files on your rooted phone.
I've been having this problem for a while. The settings do not store and always get the "can't mount /dev/block/stl11" error. I first tried the disable_lagfix file and rebooted. Nothing new. Changed some settings and then rebooted. None of the system settings kept. I then tried the voodoo uninstaller in the referenced thread. The uninstaller seemed to work without error, but still get the mounting error when entering recovery mode.
I had downloaded a version of this file from a post embedded deep inside one of the threads over here (sorry can't find it right now), but upon examination of its contents, I discovered some issues:
1. The checksums on the files in contained in the the original zip file showed that B&N had at least two versions of 1.3.0 update you can download from them, and the zip I got contained an older version so I put in the latest files in there.
2. There were unnecessary files included inside the original zip file, I deleted those, and only included what was needed.
3. There were errors in the script syntax, which I corrected, so that the proper commands are run during the update, and the proper sed substitutions are made during the editing of the unpacked init.rc inside the ramdisk.
What this zip will do is replace any older version of a B&N ROM on the alternate eMMC partitions of a dual booting configurations to the latest versions. This will prevent B&N from pushing the 1.3.0 update to you OTA, and messing up your dual boot setup. Just put the zip on your sdcard, boot into CWM recovery, and apply the zip. I apologize in advance for not giving credit to the original creators of the scripts here.
Note: There have been two different protocols for a dual booting u-boot.bin, with an older one relying on the files u-boot.altimg, and u-boot.altram to specify the names of the secondary boot ramdisk and kernel, and a newer one assuming that they are named uAltRam, and uAltImg respectively. This update conforms to the new u-boot.bin protocol. If you are still using the old one, you will have to get root access to /boot and edit the two files to point to uAltRam and uAltImg.
So if you want try it out, here it is:
http://www.mediafire.com/?gcrpzzc0kdoxcjx
MD5 Sum: 51e24c1e5eff11ba5ea481a63f7404eb
Update
I have now uploaded files for B&N Update 1.4.1.
The first file (MD5 Sum: 4ff1d9764663278c3f51e2e2c9d841a6) is meant to update a pre 1.4.1 Stock B&N ROM on secondary /system through CWM:
https://rapidshare.com/files/52135913/secondary_update_NC_stock_1_4_1.zip
The second file (MD5 Sum: c1506816fbfb8c419fbbc4afe1b12887) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM without messing with recovery;
https://rapidshare.com/files/869435270/primary_update_NC_stock_1_4_1_keep_CWM.zip
The third file (MD5 Sum: ab1307c55a2c35c91d339c8037ce9a78) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM, replacing recovery and all:
https://rapidshare.com/files/2059644016/primary_update_NC_stock_1_4_1.zip
None of these files will wipe user apps and data, so if you wish to do that, boot into recovery and wipe from there. [This will work on primary /data partition only]
Please note: If the B&N Stock ROM is rooted, you will lose root upon updating.
Thanks!
This worked beautifully! I flashed it from my sdcard after booting into CWM on my primary partition on emmc.
I'm betting you got the original from jasoraso in this dual boot thread: http://forum.xda-developers.com/showpost.php?p=17122342&postcount=142
What I would love is a straight CWM-flashable 1.3 ROM, to include in my up-to-date (for now) guide for setting up the dual boot, rather than having to set up and move 1.2, then update to 1.3.
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
Click to expand...
Click to collapse
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
rajendra82 said:
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Click to expand...
Click to collapse
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Taosaur said:
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
Click to expand...
Click to collapse
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Taosaur said:
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Click to expand...
Click to collapse
No way to get around having to register the primary partition image first. Once that is done it could be moved to secondary and then updated straight to 1.3 instead of going 1.2 first.
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
yelloguy said:
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
Click to expand...
Click to collapse
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
rajendra82 said:
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Click to expand...
Click to collapse
I wouldn't know what to change and what to leave alone, myself, but I think you're making this more complicated than it needs to be. I'm talking about installing 1.3 using CWM, regardless of how the device is partitioned or what was on the primary partition previously. Like the files in this thread, but 1.3: http://forum.xda-developers.com/showthread.php?t=1050520.
I understand that you were just cleaning up jaso's update-dualboot-to-1.3 file. I used the original and it worked fine, but it would have saved me a couple steps (and would be more useful in a guide for setting up dualboot) to simply install 1.3 rather than 1.2 to the primary partition when setting up. The reason I started with 1.2 is because it is the most current stock ROM available for CWM. What I would like is to avoid a historical re-enactment of stock OS development altogether. A general-purpose, CWM-flashable 1.3 ROM would be broadly useful, but is so far lacking as far as I've seen.
1. Do you envision this to be an uprooted stock 1.3 update ROM (either as primary or the only boot option) ? I just don't see the need for this to be CWM flashable. It is very easy to get there by resetting the device to stock, and then updating the device to 1.3.0 using the B&N file, and restoring dual boot as need be. If one has any older stock ROM running on primary, the B&N update will get them to 1.3 while losing root. There is no need to apply 1.2 update first.
2. Do you envision this to be for already rooted single or primary booting 1.1/1.2 users? There is once again no need to create any file for this. One can simply apply the B&N update, and then rerun manual nooter, and restore dual booting to the secondary.
3. The only users with no clear upgrade path are those who have already moved the B&N ROM to secondary. That's why I fixed up the zip file, and shared it. I am glad the original file worked for you despite the script errors. I can see other setups where it would have failed though.
I am not trying to make this more complicated than it needs to be. The Nook Color is just capable of being set up in so many ways, there isn't simply going to be a single update method that will work in all scenarios.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Taosaur said:
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Click to expand...
Click to collapse
Then the best bet is two step process:
1. Wipe device and restore to factory stock.
2. Download B&N 1.3 update file from website and place it on the root of SD card. Let the device recognize it, and apply it.
Once the 1.3 update gets applied, you are free to reroot, install CWM, set up dual booting, or whatever the next step may be.
It is the only method that will work in all circumstance as it involves starting from scratch regardless of setup. If want to preserve any of your current setup, no one step file will work for all circumstances. Some people have the stock firmware rooted, others do not. Some have the stock as the only internal boot, others have it as primary option of a dual booting configuration, while others have it as a secondary option. Some have stock recovery and run CWM off the sdcard when needed and want to update their recovery to the latest stock version, others want to keep the CWM recovery, and not update the recovery. There simply is no way file to cope with all these options.
rajendra82 said:
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
Click to expand...
Click to collapse
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
rajendra82 said:
1. Wipe device and restore to factory stock.
Click to expand...
Click to collapse
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------
yelloguy said:
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
Click to expand...
Click to collapse
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Taosaur said:
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Click to expand...
Click to collapse
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
Click to expand...
Click to collapse
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
Click to expand...
Click to collapse
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0p1 at the temporary location you created using the command:
mount /dev/block/mmcblk0p1 <full path to the directory you created>
4. Now use Astro to go over to the directory you created and mounted mmcblk0p1 into. You should see:
u-boot.bin which is the bootloader
u-boot.bin.stock which is the backup of the old stock bootloader
uImage and uRamdisk which are your primary kernel and ramdisk
uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)
u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam
5. Rename uFImg to uAltImg, uFRam to uAltRam. And edit the contents of u-boot.altimg and u-boot.altram to match the new file names.
6. Reboot as usual into primary or secondary.
Now if an CM7 update ever replaces your u-boot.bin, you will not lose dual boot, as you have it set up as uAltImg and uAltRam per the new protocol.
Sent from my SAMSUNG-SGH-I897 using XDA App
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
Taosaur said:
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
Click to expand...
Click to collapse
I am sorry if you think I am rationalizing, but that was not my intention. I just wanted to point out that the files you linked to do not meet your own criteria.
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible IMO, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------
Taosaur said:
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
Click to expand...
Click to collapse
It would work. If you apply my zip, there will be a uAltImg and uAltRam in /boot (in addition to uFImg and uFRam). If you apply another update that pushes the CM7 bootloader, it will then look for these files with trying to do an alternate boot, and would boot into a unrooted stock 1.3.
rajendra82 said:
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0 at the temporary location you created using the command:
mount /dev/block/mmcblk0 <full path to the directory you created>
Click to expand...
Click to collapse
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
yelloguy said:
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
Click to expand...
Click to collapse
I see a typo in my command (stupid Swiftkey X). It should be:
mount /dev/block/mmcblk0p1 <some directory>
Also try typing just mount in terminal to see if /dev/block/mmcblk0p1 is already mounted somewhere else.
rajendra82 said:
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter will lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
Click to expand...
Click to collapse
Riiiiight... it would install stock 1.3 to the device. That's the intended behavior. The point is to avoid the unnecessary step of updating in any process that includes flashing stock to the sole or primary partition. One example of such a process would be a fresh dual boot setup. That it does not update or otherwise rely upon an existing install is the point.
Granted, such a file would not repartition the device, but it would install up-to-date stock in one step regardless of how a device is partitioned (1/5, 2/5, 5/1 or dual boot).
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
A little background first. Flashed stock recovery and my original first backup in order to take OTA for Marshmallow. OTA wouldn't take so I downloaded / installed MM update successfully. Currently at 6.0, 3.38.502.12. Then, re-unlocked bootloader (S-ON) and flashed TWRP 3.0.2.0. I then immediately created a full backup successfully before rooting.
Since that point, I've been unable to create another backup. I've also had countless problems trying to flash anything at all like custom ROMs and such. Keep having to revert to my unrooted backup post-MM update. The problem had to occur somewhere after my first successful TWRP backup post-MM update and now. Puzzling part is that I restored this same successful backup then without leaving TWRP, I immediately tried to do another backup and it fails the exact same way.
Recovery.log shows:
* MD5 Created.
Backing up System...
Error opening: '/system/app/Ds' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I've tracked this down and it does indeed appear to be a directory "Ds". Inside as a sub-directory called 'oat' with Ds.apk inside of that, which is the Dolby Audio service.
I'm completly stumped. Any ideas?
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
sirvalence said:
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
Click to expand...
Click to collapse
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
grandpajiver said:
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
sirvalence said:
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
Click to expand...
Click to collapse
So worth the 25 dollars. But you need your system up and rooted for that to work.
But yeah, the dev edition SID 01 worked for me.
Made it way easier to work with and taking that ruu was magic.
Oh, also, do you have an sdcard? There is always the rom.zip method... placing the appropriate 0PJAIMG.ZIP in the root of the sdcard then rebooting into download mode works nicely.
Sent from my HTC One M9 using XDA-Developers mobile app
I guess I'm a moron and can't figure this out :v
Using stock rooted Oreo, Magisk, edXposed, everything that goes with them. TWRP 3.2.3-7.
Lately, I've been using my headphones while driving to work. I need a touch more volume over stock to deal with wind noise.
The problem is, I absolutely can't get /system/vendor/etc into a writable state.
Attempts to modify mixer_paths_tavil.xml whilst booted up fail, either resulting in an unreadable file (Total Commander) or just not working (Root Explorer).
Trying to flash a modified zip (just grabbed a dual-speaker mod and replaced the xml) in TWRP results in no file being created; it doesn't seem to throw an error, just silently fails.
Manually copying the xml to /system/vendor/etc using TWRP's file manager ~appears~ to work, but attempts to set permissions results in error code 1. The file doesn't exist upon reboot.
Remounting manually as RW in TWRP's terminal doesn't seem to help. And yes, "mount System as read-only" is unchecked.
I can make build.prop changes, so I know /system is writable. The only way I can get anything written to /system/vendor/etc is restoring a full system backup.
I've modified this file before; I manually tweaked the call volume higher and enabled "fake" high-impedance mode.
So I'm sure I'm doing something really stupid here. Help.
Septfox said:
I guess I'm a moron and can't figure this out :v
Using stock rooted Oreo, Magisk, edXposed, everything that goes with them. TWRP 3.2.3-7.
Lately, I've been using my headphones while driving to work. I need a touch more volume over stock to deal with wind noise.
The problem is, I absolutely can't get /system/vendor/etc into a writable state.
Attempts to modify mixer_paths_tavil.xml whilst booted up fail, either resulting in an unreadable file (Total Commander) or just not working (Root Explorer).
Trying to flash a modified zip (just grabbed a dual-speaker mod and replaced the xml) in TWRP results in no file being created; it doesn't seem to throw an error, just silently fails.
Manually copying the xml to /system/vendor/etc using TWRP's file manager ~appears~ to work, but attempts to set permissions results in error code 1. The file doesn't exist upon reboot.
Remounting manually as RW in TWRP's terminal doesn't seem to help. And yes, "mount System as read-only" is unchecked.
I can make build.prop changes, so I know /system is writable. The only way I can get anything written to /system/vendor/etc is restoring a full system backup.
I've modified this file before; I manually tweaked the call volume higher and enabled "fake" high-impedance mode.
So I'm sure I'm doing something really stupid here. Help.
Click to expand...
Click to collapse
Don't know, but tonight or tomorrow I'll shoot you a file to test.
ChazzMatt said:
Don't know, but tonight or tomorrow I'll shoot you a file to test.
Click to expand...
Click to collapse
Appreciated, but I think something's going pear-shaped and I just need to reflash the ROM; setting up for the drive home last night, it seems I've lost the ability to use direct output in Poweramp. I don't know how, since the system+system image backup I restored is known-good and audio is otherwise working.
Good ol' bitrot, I suppose.
Septfox said:
Appreciated, but I think something's going pear-shaped and I just need to reflash the ROM; setting up for the drive home last night, it seems I've lost the ability to use direct output in Poweramp. I don't know how, since the system+system image backup I restored is known-good and audio is otherwise working.
Good ol' bitrot, I suppose.
Click to expand...
Click to collapse
See my PM.