I'm not exactly sure what I'm doing wrong and I figured there must have been some people that have gone through this skinny4g WiFi error. I have tried flashing from a number of different starting points and granting all permissions to the dhd.ko after install. I'm in the process of flashing to 198-7 to copy the fresh dhd.ko and replace it with skinny's, but we'll see if that helps.
Has anyone had the skinny4g WiFi error and fixed it or found their simple mistake in flashing?
[SOLVED]
thanks to TrojanZulu.
If you have wifi issues with skinny4g you have to swap out skinny's dhd.ko with the normal functional one from the 198-7 .sbf. Getting the file from a .sbf can be a bit time consuming so I attached it below. Simply use 7zip (dont unzip and rezip or you will freeze up when you flash) to drag over and replace the file located in /system/lib. I'm sure winrar would do the trick too.
What is this error? How do you cause it?.. I have tried creating an error using wifi and the joker4g rom but am unable to.
The only error I can cause is trying to activate wifi while wifi tethering is running. That is more a function of wifi tethering.
Far as transfering files wirelessly, ect I have yet to cause any wifi errors.
What exactly are you doing to cause the error so maybe others can recreate the error..
Detailed information will help out..
I had this same error on both skinny4g and bootstraprocko roms.
Just follow joker's instructions about putting the dhd.ko from the 198-7.sbf in to the skinny or rocko roms and it fixed it for me.
I don't know if copying the dhd.ko from the phone or pulling it out of the sbf makes a difference but i pulled it out of the sbf, by breaking it in to the .smg files then extracting it from the .smg.
The file is in /system/lib/dhd.ko
ScottieRotten said:
What is this error? How do you cause it?
Click to expand...
Click to collapse
The error message is simply "Error" under the WiFi toggle in settings. I flash to 198-7 with rsd > root > bootstrap recovery > format system > wipe data/cache (factory reset) > flash skinnyrev14g > wipe dalvik cache > reboot. Everything else seems to work, (battery 1% increments, fast, smooth etc) but the WiFi doesn't function because of the error.
TrojanZulu said:
I had this same error on both skinny4g and bootstraprocko roms.
Just follow joker's instructions about putting the dhd.ko from the 198-7.sbf in to the skinny or rocko roms and it fixed it for me.
Click to expand...
Click to collapse
I can't seem to find a system/lib on my phone after the 198-7 flash so I'm going to try to unpack the sbf again. Do you remember which .smg the dhd.ko is in? Also, did you use MotoAndroidDepacker?
Oh, and is there any special way to repack the .zip after you plop the file in?
Its in cg60.smg
I replaced the dhd.ko and rezipped skinny4g but this new zip freezes bootstrap during the flash. Should I swap the file after I flash with the regular ROM or do i rezip a certain way?
Thanks for the help btw.
I opened the rom zip in 7zip, then dragged and dropped the dhd.ko file ontop of the existing in the zip and 7zip took care of the rest.
dlungs said:
I replaced the dhd.ko and rezipped skinny4g but this new zip freezes bootstrap during the flash. Should I swap the file after I flash with the regular ROM or do i rezip a certain way?
Thanks for the help btw.
Click to expand...
Click to collapse
I tried this and my wifi is still broken...
Related
Been using Franco's Rom and Kernel and it's been great. However, I like to update to his v.14 kernel. I did the format
1. Wipe
2. Partition, etc...
3. Load v5 Rom
4. Restart
My problem is right here, the warning is to delete the tweaks file and the script file (which I don't have one) in File Manager. I use the OI manager that comes with v5 Rom but it just wont' delete, and I don't want to load the new kernel because of all the warnings, please help :-(...
calculus1918 said:
Been using Franco's Rom and Kernel and it's been great. However, I like to update to his v.14 kernel. I did the format
1. Wipe
2. Partition, etc...
3. Load v5 Rom
4. Restart
My problem is right here, the warning is to delete the tweaks file and the script file (which I don't have one) in File Manager. I use the OI manager that comes with v5 Rom but it just wont' delete, and I don't want to load the new kernel because of all the warnings, please help :-(...
Click to expand...
Click to collapse
it wont delete cause of permissions. I use root explorer for this kind of work. In this particular case i had deleted the nececary scrips from the flash zip and i flashed afterwards. (i had a clean install)
I am trying the clean install as well, can you give the instructions or point me to somewhere where I can read more about this, thanks for your time and effort.
Do I just delete it in the Devoid.Franco v5 zip before flashing and then restart the process (the only file that I can find is tweaks.sh)
Sorry, found the init.d file as well. Would I delete those files in the zip, rezip and then start the process over?
you just delete them from the zip and you flash it as usuall. just dont forget to disable verification check on your recovery or else it will give you error
Sorry, just a newb when it comes to this.
I couldn't delete the two files from the devoid.franco.v5.zip file so I did the following:
1. Extract the zip file
2. Deleted the two files
3. Rezipped the files into a new devoid.franco.v5.zip
4. Load the zip into the micro sd card after all the wipe and partition
5. Disabled Signature check
6. Tried the flash and it said it can't open the zip because it's bad :-(...
This can't be that hard when all the other kernels was easy to install...
calculus1918 said:
Sorry, just a newb when it comes to this.
I couldn't delete the two files from the devoid.franco.v5.zip file so I did the following:
1. Extract the zip file
2. Deleted the two files
3. Rezipped the files into a new devoid.franco.v5.zip
4. Load the zip into the micro sd card after all the wipe and partition
5. Disabled Signature check
6. Tried the flash and it said it can't open the zip because it's bad :-(...
This can't be that hard when all the other kernels was easy to install...
Click to expand...
Click to collapse
Extracting a zip and re-zipping it DOESN'T work. You are not supposed to unzip the file. Just flash the rom, delete the offending files using root explorer, and then flash the kernel.
Sent from my LG Optimus One P500 using XDA App
You should't extract the file and rezip it. It corrupts it when it comes to flashing. I personally browse the zip file with winrar and simple delete the files i need. I also add files to zip this way like apks, ringtones etc
Trying winrar and it seems to work, gone to see if I can finish the entire process. Thanks so much for your time again. In the future, can I send the apps that I want directly into this zip? I can to sue something zipsigner before to get calendar, etc... Thanks again!!!
An alternative way for a clean install:
1: wipe everything
2: flash devoid.franco.v5
3: reboot (to check if everything is ok)
4: reboot into recovery
5: mount /system partition under 'mounts and storage' (clockworkmod)
6: from pc type (with phone still in recovery): 'adb shell'
7: in adb shell, type: 'rm /system/etc/tweaks.sh'
8: in adb shell, type: 'rm /system/etc/init.d/00script'
9: flash franco.kernel.v14
10: reboot
I Hope it helps,
Bye
You're welcome m8.
And yes you can have the apps you want inside the rom this way very easilly. just put them in app folder. I did this with some removed apps like browser and calendar and also removed zeam launcher and used adw launcher (personal taste) I even tried that with frameworks (aka themes) and it worked great
Thanks so much to both of your posts, it's working. One last questions, thought setcpu was already implemented in this kernel, but I don't see it anywhere? Again, thanks again for everyone's time and effort, learned so much today (wife is mad though because we need to do house work, lol, lol, better get going)... She said, "who formats their phone 5 times in 1 month, lol, lol"
setcpu is NOT included, you have to install it.
See first post in franco.kernel thread for the link.
Eh! eh! you are not in Europe, I guess if you have to help your wife NOW!!!
Barcelona-ManchesterUTD right NOW...
oh yes the wifes. my gf gets fustrated like "wtf are roms and kernels?? its just a phone!!! you call people and they call you back" rofl
One last note on setcpu. When i was using last version (2.13), every time i rebooted my phone the settings where gone and had to set them again. I switched to v2.1 and it worked like a charm. Have no idea if that is general issue or only me had it. Just thought i should tell you
Done via editing the zip with rar and all worked smoothly.
Thx all
/W
Hey all.
Been searching XDA and Google for anything on the original framework-res.apk file for the EVO3D.
I dont know what happened but after I flashed this zip from recovery, I rebooted and only see the top status/battery/timebar. NOTHING ELSE. Power button activates screen only...no lockscreen, just black screen and top bar.
Can anyone lend a hand and help me figure out if this can be reversed or uninstalled? Phone works....just cant see the screen to take calls.
Much thanx in advance.
Just download the stock ROM on your computer and pull the original apk from it. Or download the ROM you fiddled with, and pull its apk from there. You can also just try reinstalling the ROM. Or reflash it over. Just clear cache and Dalvik, then flash.
Oh and post this is Q&A next time, or the hall monitors will come and give you a ticket. Oh, and I forgot to mention a tongue lashing.
I also forgot to mention to be aware of the troll patrols. They'll troll you alive!
Sent from my PG86100 using XDA App
DDiaz007 said:
Just download the stock ROM on your computer and pull the original apk from it. Or download the ROM you fiddled with, and pull its apk from there. You can also just try reinstalling the ROM. Or reflash it over. Just clear cache and Dalvik, then flash.
Oh and post this is Q&A next time, or the hall monitors will come and give you a ticket. Oh, and I forgot to mention a tongue lashing.
I also forgot to mention to be aware of the troll patrols. They'll troll you alive!
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Thanx. Im downloading the stock rooted rom now.
The only reason I posted here was that the zip was a battery modification that for the life of me, I cant seem to remember where I got it from. Considering that it was a mod, I figured it would make sense in Themes and Apps...also figuring in that if someone who had used it as well would have knowledge of uninstall/removal.
Download's done. Will let u know if it worked. Thanx again DDiaz007!
zagman said:
Thanx. Im downloading the stock rooted rom now.
The only reason I posted here was that the zip was a battery modification that for the life of me, I cant seem to remember where I got it from. Considering that it was a mod, I figured it would make sense in Themes and Apps...also figuring in that if someone who had used it as well would have knowledge of uninstall/removal.
Download's done. Will let u know if it worked. Thanx again DDiaz007!
Click to expand...
Click to collapse
If your going to do a clean install. Your going to want to wipe...
Dalvik Partition
Cache partition
Data partition
System partition
Sent from my PG86100 using XDA App
DDiaz007 said:
If your going to do a clean install. Your going to want to wipe...
Dalvik Partition
Cache partition
Data partition
System partition
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I understand that DD. I don't plan on doing a clean install. After all, I do have a backup from about a week ago that I could restore in Clockwork as a last resort. But seeing as I have done some installs and the backup is a week old, I wanted to see if this zip can be uninstalled. I found out its from Team Xron and I downloaded it on 7/20, 5 days after I got my 3D.
My confusion gets worse now that I see that when I flashed the zip, (its contents included below) it had a META-INF file besides the .apk file. And comparing the 2 META-INF files from here and the stock Rom...they differ in size, and contents. The stock ROM META-INF does not include the RSA, SF, & MF file as does the Mod zip. Also the binary and script files differ in size.
How would u suggest going about changing it back? Should I put the .apk on my sd and push it using ADB? OR create a zip with the Stock .apk and META-INF and flash it in Clockwork Recovery as I did initially?
META-INF / CERT.RSA RSA File 1.7 KB
META-INF / CERT.SF SF File 382 bytes
META-INF / MANIFEST.MF MF File 329 bytes
META-INF / com / google / android / update-binary File 249.9 KB
META-INF / com / google / android / updater-script File 196 bytes
framework / framework-res.apk APK File 3.0 MB
creating a zip with the Stock .apk and META-INF and flash it in Clockwork Recovery was unsuccessful.
"Installing Evo 3D base rom 1.0
unpacking system..
symlinks & pemissions...
"installing kernal...
assert failed: package_extract_file("boot.img. "/tmp/boot.img")
E: error in /sdcard/download/xxx.zip
(Status 7)
Installation aborted."
Although I backed up in CWM....think im just gonna restore back to last week. If i get a wild hair and some good tech support from Xron, I might flash back and troubleshoot again. Oh well....
zagman said:
creating a zip with the Stock .apk and META-INF and flash it in Clockwork Recovery was unsuccessful.
"Installing Evo 3D base rom 1.0
unpacking system..
symlinks & pemissions...
"installing kernal...
assert failed: package_extract_file("boot.img. "/tmp/boot.img")
E: error in /sdcard/download/xxx.zip
(Status 7)
Installation aborted."
Although I backed up in CWM....think im just gonna restore back to last week. If i get a wild hair and some good tech support from Xron, I might flash back and troubleshoot again. Oh well....
Click to expand...
Click to collapse
Stop......Explain what you're trying to do and I will help you.
You want a stock framework-res file?
freeza said:
Stop......Explain what you're trying to do and I will help you.
You want a stock framework-res file?
Click to expand...
Click to collapse
I flashed a battery mod from Xron and the screen was black all for notification bar on top. Trying to "undo" that. Ive extracted the framework-res.apk and the Meta-Inf folder from the stock rom and tried flashing. Not recognizable in CWM Rec. I used the original signed .zip and replaced the contents and the results are in my last post. What else can be done?
zagman said:
I flashed a battery mod from Xron and the screen was black all for notification bar on top. Trying to "undo" that. Ive extracted the framework-res.apk and the Meta-Inf folder from the stock rom and tried flashing. Not recognizable in CWM Rec. I used the original signed .zip and replaced the contents and the results are in my last post. What else can be done?
Click to expand...
Click to collapse
That updater script is trying to install more than what you have in the zip. Your best bet would be to push through adb
Enter-
Adb push (your framework-res.apk) /system/app/
No parenthancies
Sent from my PG86100 using XDA Premium App
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
What type of zip file is it?
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
markdexter said:
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
Click to expand...
Click to collapse
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only other common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
joeykrim said:
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
Click to expand...
Click to collapse
Amazing answer, thank you so much for taking your time with me, appreciate it, I'll try the recovery log, see what I get, as you can tell I'm pretty new to this, everyone has to start somewhere!
Thanks again buddy
Sent from my HTC EVO 3D X515a using xda premium
Hi everyone,
I want to eventually create an edited ROM for an Android tablet. (Very simple stuff, really. Removing apks, adding build.prop mods)
I have a working update.zip file, which re-installs the image on the tablet, through stock recovery and the install from sdcard option.
But once I unzip it,
and then zip and even re-sign it (with the tool I found by searching the forum),
the recovery says 'installation aborted', when it is verifying the package.
1. How can I avoid this from happening? I get it that closing the update.zip is done wrong. How can I pass the verification section?
2. It IS possible to push such a .zip through stock recovery, right? I want to avoid CWM and TWRP and make it as simple as possible.
Thanks.
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
dxppxd said:
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
Click to expand...
Click to collapse
I tried this, too.
I only deleted one apk from system/app and later I tried again by deleting the apk and its odex file, too.
In both cases, instead of rejecting the update instanlty, it starts the process and then stops after a few seconds.
IS it possible that there is a filesize checker text inside the image?
(or maybe a propery inside the build.prop or updater-script ?)
Any ideas, anyone?
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
iraklisvel said:
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
Click to expand...
Click to collapse
No
Stock recovery doesn't flash custom roms
Get cwm from builder.recovery.com
Press thanks :good: I'd helped :highfive:
I have CM 10.1.3 installed on my i9100 and I flashed the ZIP file from the thread at the bottom of this post through CWM Recovery. Now, my phone is stuck at the boot screen.
I would realllly hate to reinstall my ROM and all apps, so I'd just like to fix the problem. The ZIP makes changes to the 'SurfaceFlinger' library. Could I reflash a ZIP of the original library? Any idea how I could get the file?
surfaceflinger-fix.zip
http://forum.xda-developers.com/galaxy-nexus/development/fix-lag-fix-cm10-based-roms-cm10-t1875490
SOLUTION:
The only file that surfaceflinger-fix.zip affects is libsurfaceflinger.so. So, I tried extracting this file from a copy of the CM 10.1 zip file. libsurfaceflinger.so is located in system/lib. I then created a flashable ZIP using this guide:
http://forum.xda-developers.com/showthread.php?t=2163974
I flashed the ZIP after pushing it via 'ADB push sample.zip /sdcard'. I installed the ZIP via CWM Recovery. Clear caches, reboot. STILL DIDN"T WORK.
So then I took a look a look in the META-INF folder of surfaceflinger-fix.zip and noticed some additional files that I did not have in my custom 'sample.zip'. So, I just took the libsurfaceflinger.so file that I extracted from CM 10.1 and put this file in surfaceflinger-fix.zip, replacing the original one in the ZIP file. Pushed this ZIP via ADB, everything works.
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
ghostofcain said:
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
Click to expand...
Click to collapse
This was definitely easier and this is a better fix than using a backup, but I absolutely agree with you.