Hello,
I am having a major problem... earlier today i made a backup of my ics'd out v8 rom in order to try the new CM7 Kang. I got the kang running but needed to install gapps. For some reason rom manager was not letting me install it from there because it wasn't an updated version of rom manager and i couldn't get an updated version. So i figured I would go back to my ics'd rom, download gapps on the sdcard, and then go back to cm7 to install... NOPE.
Every time I try to restore my backup I get md5 mismatch error. I went through a bunch of different threads for different phones and tried all the adb stuff it said and nothing worked. For some reason when I ran the command (given here http://forum.xda-developers.com/showthread.php?t=714114) "cd /sdcard..." the pound # changed to a > and everything I typed would just be repeated back at me. The phone never even asked for superuser permission. I am pretty sure that I have the adb stuff right since when I type in "adb devices" in command I see the device, but I just have no clue how to fix this. Maybe the instructions given on this page only applies to that particular phone?
I would really like to be able to recover this backup and if anyone has instructions on how to fix this error on this phone it would be very much appreciated.
Thanks!
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Artimus009 said:
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Code:
adb push
is your friend - great way to put a file on the phone when it's in recovery
Entropy512 said:
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Click to expand...
Click to collapse
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
getbuzzin said:
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
Click to expand...
Click to collapse
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference? I mean I have done this before without issue.
Shadow12347 said:
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference?
Click to expand...
Click to collapse
Change it back and see if it works
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Well I deleted the beginning and it looked like it was going to work because it was checking md5 sums for a while and then it said md5 mismatch. But it wasn't instant like the other times.
I think I read on one of the pages that you could take the nandroid.md5 from another backup and replace it with the one in the nonworking backup, is this true and would it work?
Ok nevermind, I forgot to do the ADB thing again xD it worked... THANK YOU SO MUCH!
karth500 said:
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
Most likely.
I usually rename my backups manually to something like romname_date in ADB
e.g.
villainrom_1224
I NEVER put spaces or other characters in the rom name
Right now I think I have:
modstock_1128
villainrom_1224
uckk6_1224
one other ROM...
Ok guys I'm sorry, it happened again... except this time I think it may be a problem with ADB. When I am in adb shell, it shows up as "~ #" instead of just "#", however, typing "su" changed it to just "#". However, in both instances ("~ #" and "#") it gets an error:
~ # cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
/sbin/sh: cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
and
# cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
This is the original name, there are no spaces, I checked the driver for the phone, etc.
Anyone got any ideas?
Oops double post -_-
Try tab-completion (type part of a directory name and hit tab - sometimes it works and sometimes it doesn't, usually should work when ADBing into CWM), and use "cd" and "ls" to navigate through directories instead of just pasting the whole path.
ls = same thing as dir in DOS
Alright so I did that and found out the sdcard isn't mounting...
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
# ls
ls
acct fota.rc recovery.rc
app-cache init res
cache init.goldfish.rc sbin
config init.rc sdcard
customkernel init.smdkc210.rc sys
d init.smdkv310.rc system
data init_kernel_only.rc tmp
dbdata lib ueventd.rc
default.prop lpm.rc ueventd.smdkc210.rc
dev misc ueventd.smdkv310.rc
efs mnt vendor
etc proc
# cd /mnt
cd /mnt
# ls
ls
asec obb sdcard secure usb
# cd /sdcard
cd /sdcard
# ls
ls
#
I also went into root explorer and it said "SD card is not currently mounted"
...uhhh I feel like a noob to ask this but, how do you mount it? xD
The thing is, though, that it dismounts when I plug it into the computer to transfer files/adb, but it is mounted afterwards...
Related
If u get a md5 mismatch error During a restore thing type via command promt ( ADB iinstalled)
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53(THE name of your backup stored in /clockworkmod/backup )
# rm nandroid.md5
# md5sum *img > nandroid.md5
awesome idea
raunakrajvanshi said:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
Ok, so maybe a stupid question, but on the second line, do you change the command to your backup name?
terthii said:
Ok, so maybe a stupid question, but on the second line, do you change the command to your backup name?
Click to expand...
Click to collapse
Not a stupid question But the answer is yes (or at least it should be)
Ah, OK. Thanks!
EDIT: Ok, yet another possibly stupid question! Can I run this through a terminal on the phone, or do I need to do this through a command prompt on the computer?
EDIT 2: Er, I just looked at my recovery that I have the md5 error for. There's nothing in the backup folder! It's empty! Like, crap! Back when I made the backup, the recovery said it backed up successfully. I even recovered using that backup once before. Is this normal? Or is there something jacked up here?
great job ..well done
Command promt
terthii said:
Ah, OK. Thanks!
EDIT: Ok, yet another possibly stupid question! Can I run this through a terminal on the phone, or do I need to do this through a command prompt on the computer?
EDIT 2: Er, I just looked at my recovery that I have the md5 error for. There's nothing in the backup folder! It's empty! Like, crap! Back when I made the backup, the recovery said it backed up successfully. I even recovered using that backup once before. Is this normal? Or is there something jacked up here?
Click to expand...
Click to collapse
Command promt oviusly u need to have adb installed Did you delete it
my NT is not working, if you can please click here to help me
anyway, before that - when it was working, i tried to root it by using this method:
http://forum.xda-developers.com/showthread.php?t=1354487
at debloat menu, i chose "extreme" because i want to delete all of B&N content. i just want a normal android tablet, i know i can still read books by using the NOOK app for android.
so i chose extreme mode. and the command prompt window closed right after that.
so my NT was rooted, but not successfully, it was even worse than it was before i rooted.
i open the batch file (NookandZergy.bat) to see what the command lines are to find the reason why it didn't work. and i saw this:
adb shell rm -r /system/app/Accessories.apk
Click to expand...
Click to collapse
i opened command prompt, and typed this. and i got something like "failed because the file is not exist." -> i knew the batch script was wrong in some ways. i was going to unroot and root again with the option "full debloat" (not extreme), but before i do that, i was trying to remove netflix, i wanted to type this to the command line to see what will happen.
adb shell rm -r /system/app/netflix.apk
Click to expand...
Click to collapse
but i accidentally type adb shell rm -r /system/app/, and then it removed everything in /system/app/
i got the error in the nook tablet's screen, i don't remember what the error is, but when i pressed "force close", it kept showing me that error, i tried about 20 times but still not work.
i turned off my NT, and when i boot it, it stuck at "read forever",
that's why i created this thread.
my question is: how do i do "extreme debloat"? i want to remove everything from B&N. can you please give me the correct "command lines" to do this? and how to use that "command lines"?
prepare a sdcard to boot into ClockworkMod (CWM) which is a custom recovery (replaces stock recovery). And from there flash this ROM, for extreme-debloat is easy you can modify the script just to debloat or i can make it for you. First focus in restore your system.
As i said in my last post in your other thread read my FAQ and you will find your what you need there, if you have any question me or any other user will try to help.
PS: here is post i made for a user about how to re-bloat but the thing is that i post the list of all the B&N apps for reference to you so it might be helpfull.
~ Veronica
i have a little knowledge about batch file, so i think i can edit the script
(just edit the wrong file name -> make it become correct file name)
but i don't know what files are inside the folder /system/app/
for example: the file Accessories.apk is not exist, so how should i edit the script
nooktablet said:
i have a little knowledge about batch file, so i think i can edit the script
(just edit the wrong file name -> make it become correct file name)
but i don't know what files are inside the folder /system/app/
for example: the file Accessories.apk is not exist, so how should i edit the script
Click to expand...
Click to collapse
Well you got the error probably 'cause when you ran the script it removed that file so when you typed the same command again it won't remove it because is already gone.
In the link i provided is the list of all the B&N applications that are removed in the extreme debloat option. So you basically have keep that part of the code plus the intro to get in adb shell.
In that post you will also find a link to the complete system/app folder just in case you by "playing around" with adb remove any important system app, so you can push it back.
~ Veronica
lavero.burgos said:
Well you got the error probably 'cause when you ran the script it removed that file so when you typed the same command again it won't remove it because is already gone.
In the link i provided is the list of all the B&N applications that are removed in the extreme debloat option. So you basically have keep that part of the code plus the intro to get in adb shell.
In that post you will also find a link to the complete system/app folder just in case you by "playing around" with adb remove any important system app, so you can push it back.
Click to expand...
Click to collapse
no, when i chose extreme debloat, it closed the command prompt window, before it closed, i saw something "failed...". when i typed the command again it showed "failed...", i'm sure it's exactly what it said before,
and i know after debloat, it should go back and do other command like "thank you for using" (i read the batch file). i also saw B&N apps were still on my NT, debloat didn't work because of the missing file -> the script stopped.
btw, you said i can use adb to push the apps back. so that means i can also use adb to remove apps? can i not debloat when rooting, and after root, i use adb to remove apps later? will adb work at that time?
and can i use adb to explore what files are in the /system/app/ folder? or any other program?
nooktablet said:
no, when i chose extreme debloat, it closed the command prompt window, before it closed, i saw something "failed...". when i typed the command again it showed "failed...", i'm sure it's exactly what it said before,
and i know after debloat, it should go back and do other command like "thank you for using" (i read the batch file). i also saw B&N apps were still on my NT, debloat didn't work because of the missing file -> the script stopped.
btw, you said i can use adb to push the apps back. so that means i can also use adb to remove apps? can i not debloat when rooting, and after root, i use adb to remove apps later? will adb work at that time?
and can i use adb to explore what files are in the /system/app/ folder? or any other program?
Click to expand...
Click to collapse
Yes adb works at anytime even in dockworkers (CWM) .
To know how to use adb go to my FAQ (link below in my signature) and look in the how-to's made by me section for the how to use and install adb.
"adb shell rm -r" is one of the adb commands and is used for remove files.
adb shell = is to get superuser permissions (root/su)to run advanced commands.
rm = remove
-r = recursive
~ Veronica
Sent from my Nook Tablet using xda premium
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
EDIT:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
lalalalas said:
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
Click to expand...
Click to collapse
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
leadtk said:
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
Click to expand...
Click to collapse
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Quallenauge said:
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Click to expand...
Click to collapse
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
leadtk said:
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
Click to expand...
Click to collapse
From the guide, install using adb. http://forum.xda-developers.com/showthread.php?t=1871912
Originally Posted by surdu_petru
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /local/ ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
If you are a Linux user. http://forum.xda-developers.com/showpost.php?p=48731942&postcount=1
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
leadtk said:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
Click to expand...
Click to collapse
I do not know what i am doing wrong but when i type adb shell ..all i get is BUSYBOX v1.7.2 (2012-10-19 CEST) built in shell (ash) Enter help for a list of built in commands ...
I did have ics blue v04 rom on my tablet that i was trying to go from to 4.4.2 ..
I did this before and had the write problem . any help you can give would be appreciated
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.
Yes, it's possible, and yes, it's pretty much exactly the same process as on your phone. If you've done it there, you can do it on Wear.
Oh, apologies if this is old news to you, but I couldn't find threads on this particular topic, and I'm quite satisfied that it worked, so why not share.
Now, the stock Wear boot animation is great. I personally love it, at least -- so why change it? Well, why do we do most things on XDA? Because we can. Do at your own risk, I take no responsibility if you screw up. Take these notes as suggestions. I mean, they work, but you know. Backups are always a good idea.
tl;dr for people who don't need help with adb:
push the bootanimation.zip to /system/media (back up the original!), then
chmod 644 bootanimation.zip
reboot
done.
Stuff you'll need:
1. An Android Wear device (any should do, I have a Sony Smartwatch 3) that has root access and ADB debugging enabled
2. A custom kernel that has adbd insecure (I used this)
3. ADB drivers on your computer
4. A boot animation. Duh. I used this for testing purposes because the resolution is meh x close enough.
Optional: a file explorer that works on Wear. I use ES.
How to do it (the way I did, I know there are other ways):
1. On your computer: move the .zip file your animation comes in to the folder where you have ADB installed. It's probably something like "C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools".
2. Open a command window in that location by shift+right clicking on the folder and selecting "Open command window here".
3. Connect your watch to your computer no later than now. If prompted, allow debugging (note that if it's your first time, the prompt should show. If not, check developer settings again).
4. In the command prompt, type
Code:
adb devices
This lists the devices that are connected to your computer. You should see the text "List of devices attached", your watch's serial number, and the text "device" next to it. If you don't, check your drivers.
5. Copy the .zip onto your watch:
Code:
adb push bootanimation.zip /sdcard/
The directory doesn't actually matter, just make sure it's not /system and somewhere you can remember.
6. Why not /system? Because it's, by default, a read-only partition we can't access via normal adb commands. Yet that's where that zip is headed. This is where the adbd insecure kernel comes in: with it, you can remount /system as read-write. For that, enter the adb shell:
Code:
adb shell
It'll show (don't write this!)
Code:
[email protected]:/ $
To get the root privileges you'll need, type
Code:
su
What you should get is
Code:
[email protected]:/ $ su
[email protected]:/ #
The # means you're rooted. If it shows without typing "su," great.
7. Remount /system as read-write by typing the following:
Code:
mount -o rw,remount /system
8. We can now alter the partition, and we'll start by backing up your stock boot animation. To do that, we need to "move" the file to an identical file with a different name. If that sounds like it doesn't make sense, that's because it doesn't -- it's stupid, but adb shell doesn't have a rename command. This is to avoid the stock animation from getting overwritten by the new one if anything goes wrong. Anyway, to accomplish that, type
Code:
mv /system/media/bootanimation.zip bootanimation.zip1
This changes the animation's extension to .zip1, which doesn't exist. The point of this is that Android looks for /system/media/bootanimation.zip when booting up, so "bootanimation.zip1" gets ignored and is out of our way. If you'd reboot the watch now, there would be no boot animation, just a plain "Android" text (or as is the case with my 320x320 SW3, "NDROI")
9. Now we'll need to move our new animation to replace the old one. To accomplish that, use the aforementioned "move" command:
Code:
mv /sdcard/bootanimation.zip /system/media/
10. Finally, to make the animation actually display, we'll need to give it proper permissions, which are rw-r-r. "chmod" is the command that alters permissions, rw is represented by a six, and r by a four.
Code:
chmod 644 /system/media/bootanimation.zip
11. Close down /system
Code:
mount -o ro,remount /system
12. Done! Reboot your watch and enjoy your new boot animation!
Worked thanks
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Smackedgnome said:
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Click to expand...
Click to collapse
Good to hear! Now all we need is that the artistically inclined among us make some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
[NUMINIT] said:
Now all we need ... some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
Click to expand...
Click to collapse
Went looking for them and found a few, thought that I would share.
There appears to be a size limit to what boot animation can be used (at least with my Sony Smartwatch 3), the biggest file used being ~3000KB.
Watchdogs
view here
https://www.youtube.com/watch?v=ZhH-4zsMB5w
This is the one I currently use
Cyanogenmod12
(sorry dont have a link/ gif - it looks good trust me )
Nexus 7 boot animation
(no link either sorry and tbh havent tried it yet - theoretically works)
I made none of these myself, they belong to the original owners. (I just cant remember where from lol)
Files are aptly named, dont forget to rename to bootanimation.zip
Enjoy
On my aw2 huawei 2 sport 4g sawshark, the time shows during the boot process. Any way to remove for aw2 or add for aw1?
Sent from my amami using XDA Labs