Huawei Y550 Cannot save build.prop - Android Q&A, Help & Troubleshooting

So I have rooted Huawei y550 and I messed up build.prop by adding qemu.mainkeys=0 in wrong pace and now when I boot up my phone its stuck at error system ui has stopped but I found a workaround by factory reseting.
So now I can enable usb debugging and stuff.
Anyway I cannot save build.prop when I edit it with root explorer.
And then I try to push it using adb it gave access denied error so I did this chmod 777 /system/build.prop
But now when I try to push the file back it says that directory (or file) is read only.
And I tried many things as adb remount and mount in shell but nothing works.
Also I cannot unloack bootloader because I cannot get code form offical site it says that my ID need to be conneced with my phone atleast 16 days but as the phone is fked I cannot do that (even if i could i have no idea how)
Any help? Thanks!
Edit heres what adb say when I try to chmod
10|[email protected]:/ # chmod -R 777 /system
chmod -R 777 /system
Unable to chmod /system: Read-only file system
10|[email protected]:/ # chmod 777 /system
chmod 777 /system
Unable to chmod /system: Read-only file system

Yeah i ****ed HUAWEI Y550 even harder, nothing works now because changed almost everything, didnt knew it was so important, because its my first android phone. now only few basic apps are running, text, calls, phonebook and chrome(old version). If you will found way to edit it back, please share. i already having this problem for two months.

Evaldas Januskevicius said:
Yeah i ****ed HUAWEI Y550 even harder, nothing works now because changed almost everything, didnt knew it was so important, because its my first android phone. now only few basic apps are running, text, calls, phonebook and chrome(old version). If you will found way to edit it back, please share. i already having this problem for two months.
Click to expand...
Click to collapse
Yes I found rom form manufacturers site, Installed thought system update and it works... Until my friend smashed it.
Here's a tutorial how to do it androidmtk. com/flash-stock-firmware-huawei-smartphone (remove spaces) but I did it bit diffrently. Hope this helps!

Related

[Q] How to ADB push?

I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.

[Q] cp: write error: No space left on device

I am trying to re-root after the 2.3.6 update, I did not remove root before the OTA update.
I made sure USB connection was set to none, and USB debugging was on. I see that is saying that I am out of space, problem is I don't know how I could possibly be able to be out of space, I have plenty of room on both the internal and external cards. Below is the output with the error. Any help would be appreciated. Thanks.
C:\moto-fastboot-win32>moto-fastboot.exe flash preinstall preinstall.img
sending 'preinstall' (30720 KB)... OKAY [ 2.682s]
writing 'preinstall'... OKAY [ 3.447s]
C:\moto-fastboot-win32>moto-fastboot.exe reboot
rebooting...
C:\moto-fastboot-win32>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: No space left on device
[email protected]:/#
same thing happened here
same here
i have the same problem, do i reboot?
any update on this?
Hi there... I had the same issue when I installed the 2.3.6 ATT OTA update when I lost root... I tried RootKeeper application but it didn't work after the OTA installation. I looked for information about this error but didn't find much or complex solutions as to free space from that system dir... so then I thought about if the copy command would have an overwrite option and it did, so I tried it and it worked for me.... I'm rooted again!
I see this is an old post but in case you still need it, it may help you too. I used line bleow to overwrite and the rest you know it.
cp -f /preinstall/su /system/bin/su
by the way, I got an error in the line "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk" telling me that the application or file already existed as I already had superuser installed... I guess it should work without re-installing it, in my case the reinstallation was to a different superuser version... anyway if you want to skip that error and proceed with the re-installation you can use option -r as shown in line below.
PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk
cheers!
avelezmtz,
Thanks for the idea, but it did not work for me, I still got the no space left error. Do you know if there a way to delete the SU file and then try to copy it? Thanks
I tried the, PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk, command and it was able to reinstall the apk which it never has before so that's good, but it's still not rooted.
If anyone else has any ideas let me know. I am thinking about backing everything up and doing a factory reset and seeing how that goes.
First... as suggestion, if you will be playing deleting files, ensure you have clockworkmod backup or anyother way to restore a previous backup just to be safe.
I think rm command should delete su, but I'm not sure if it would help since the error is not a permissions error, so the ovewrite option should work if the space in the system dir is enough... if you still wanna try the removal of su I think line below will do it.
rm /system/bin/su
Another option I saw somewhere it was about freeing up space by deleting apk files from /system/app dir which is mounted in the same volume, however it would depend on how big those files are. Of course you should back them up first maybe copying them to /sdcard/ for instance. In the post I saw that they removed swype.apk and that was enough for them but in my case it didn't help and as the ovewrite worked I didn't try removing more apps.
If you want to know the space on that dir you can use
df /system/bin/
avelezmtz,
Thanks for all the help, I am now rooted again!!
Using your suggestion I deleted Superuser.apk and Swype.apk from the /system/app directory.
After that I was able to rerun all the commands and get root back. Thanks for all the help, I appreciate it. Sure beats wiping the phone and starting all over again.
I have a problem with my Yu Yureka which running on CM 12.1 and Rooted (su) twrp
1. When I was trying to to flash any zip file like CameraNext Mod, it was flash successfully. After reboot the system, I can't find the CameraNext Mod, it was not in menu.
2. Sometime when i tried to flash other zip file like xposed framework, it was not completely installed. there was error and the error message was " cp:write error: no space left on device"
plz help me with right direction..

[Q] [help]how to get system folder permission for hdx7

I just play andorid device a few days, but My hdx7 is a little bricked because i deleted some system app. Now I can log in fire os, have adb, usb connected and internal storge, even i can operate device setting app, but i can't open the other app because i don't have a desktop.
I compare system/app folder with the same folder in the amazon bin, found that the folder lack of scores of app, but the other system folder is the same. So I hope can adb push app folder to the system folder, but the pemission denied. I try to remount or mount, it can't work.
if adb root, then "adbd cannot run as root in production builds.
if adb push apk to the app folder, then “permission denied".
if adb remount, then ”remount failed: Operation not permitted".
and I have try adb shell like that:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system
# exit
it didn't work.
my hdx7 have rooted.
My Questions are:
1. If I could push the app folder to the system folder and reset to factory, is my hdx saved?
2. How to get the system folder rw in the situation?
thx for any prompt, although i am a rookie but i will try my best, i wish the adept can help me and will be enormously grateful. Sorry for my poor english.
It sounds to me that you had lost root.
kschang said:
It sounds to me that you had lost root.
Click to expand...
Click to collapse
So i have tried root again like "http://forum.xda-developers.com/showthread.php?t=2544965" said
But it didn't work, please see the attach, But I don't know why.
Sorry for that i'm rookie to andorid and ask so many questions.
randolphling said:
So i have tried root again like "http://forum.xda-developers.com/showthread.php?t=2544965" said
But it didn't work, please see the attach, But I don't know why.
Sorry for that i'm rookie to andorid and ask so many questions.
Click to expand...
Click to collapse
Hmmm... It says you still have root (the prompt changed after "su")
I personally don't use ADB much. I have Root Explorer (grabbed it legally for free from Amazon ages ago) and Wifi Explorer Pro (same method) so I basically WiFi myself the files I need sideloaded then move them around on the device itself. But if you've lost launcher, you have deeper issues.
Have you tried ADB push any launcher? Or even a download store like 1Mobile or Aptoide?
ADB is basically a Linux shell debug into Android, so you need to learn some Unix shell commands. I'm sure you can find ADB guides with the basic commands, like "ls", "cp", and so on.
You need to check the directory and see if the system/app and other system directories are still there. This is one reason I only play with the copy of ROM I have (see Safestrap Recovery).

help with bypasslkm for surges nc5>mk2

can someone explain how to use bypasslkm in further detail. i looked through multiple threads but im stilll not getting the handle on it,
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD app
sfgrimes said:
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
Deleted
Sent from my SCH-I545 using Tapatalk
JTSDeveloper said:
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
I had the same issue. Here is the binary from Surges dropbox https://www.dropbox.com/s/9rdz9ff6x5foech/bypasslkm
Make sure you copy it to the right directory and follow all the commands.
Sent from my SCH-I545 using XDA Premium HD app
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Surge1223 said:
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Click to expand...
Click to collapse
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
JTSDeveloper said:
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
Click to expand...
Click to collapse
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's still not working. Any ideas? Should I move it directly into /data/local/tmp
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
JTSDeveloper said:
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
Click to expand...
Click to collapse
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Solution to the 755 bypasslkm issue!!!!!
k1mu said:
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Click to expand...
Click to collapse
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
EinGlo said:
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
Click to expand...
Click to collapse
worked perfectly and all my confusion is now gone thank you.
Fix works but new issue
JTSDeveloper said:
worked perfectly and all my confusion is now gone thank you.
Click to expand...
Click to collapse
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
EinGlo said:
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
Click to expand...
Click to collapse
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Issue with auto-running my solution
k1mu said:
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Click to expand...
Click to collapse
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
update
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
I tried again.
Ok, so I figured out the coding a little bit. Im not used to this, so forgive my ignorance.
I did the code as u typed it. BUT I made a change. Because I kept getting the "file not found " error. I added ".bin" to the end of the bypasslkm code line. It generated a real response. I felt relieved. I went ahead and typed the last line of code.
THEN I was told the file already exists... I have attached a picture of what I got in android Terminal
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Question
k1mu said:
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Click to expand...
Click to collapse
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
EinGlo said:
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Click to expand...
Click to collapse
I'm sure there are programs that can be set up to run scripts as root during boot; However, that's complicated since you want this to run while the phone is booting, before there's any opportunity to allow SuperSU to ask for permission.
EinGlo said:
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Click to expand...
Click to collapse
That's a problem that's fixed by an edit to /system/etc/permissions/platform.xml, adding a stanza that permits external storage write access.
EinGlo said:
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
Click to expand...
Click to collapse
The need to run the "bypasslkm" program is because of the downgrade. If you go to a clean rooted Kit Kat ROM, it shouldn't have any issues with WiFi being enabled. That may be the easiest way to fix this.

[Q] Problem with remounting /system

Hi all.
I apologize ahead of time that this thread is so long, but I have quite a problem. I am in the process of rooting my unlocked Galaxy S4 running Android 5.0.1 lolipop, but I cannot add the su and busybox to my /system/bin folder because /system is a read-only filesystem. I have done just about everything I can think of to mount and remount, like typing adb remount and mount -o remount,rw /system, but they just give me the same answer saying permission is denied. I tried doing adb root to get the permission I needed, but I got an error message saying that adbd cannot run as root in production builds. After doing some research, I found out that the /default.prop has debuggable=0 and that may be what is not allowing me to restart adb as root. So I opened the shell and typed cat to see and sure enough it was set to 0. So I did echo and set the variable to 1. However, whenever I hit enter, I got another error telling me the same thing, that /default.prop is a read-only file. I am at a loss of what to do now. How I can mount and unmount the /system if I can't get any permission to do so? Any help would be greatly appreciated. I do ask though, please don't recommend ready made apps that can insta-root your phone like a supah-hackah because I want to do this the hard way for gratification's sake. I am just stuck and need some help to get the /system to allow writing as opposed to read-only. Thanks in advance.

Categories

Resources