ok so to try and not sound redundant ( prob not gonna happen) i had the cm7 release running perfectly no issues ... then i decided to install faux's OC UV kernel which was great ... everything was speedy and working fine up until last night where my phone froze and i had to pull the battery ... after once booted up everytime id try and turn on wifi it wouldnt and i would just recieve a message that says error ... tried rebooting , wiping and reflashing .. tried flashing royals new GB rom exactly the way the instructions said too ... still nothing ... anybody know what might be causing this issue ... ive tried 3 diff roms with different kernels and still no wifi ... could this be hardware ????
bump.
Ive tried wiping everything including /system and davlik and still cant get the wifi to work ... i was told that i might have a bad module so i pushed on from the kernel i was currently using and still nothing ... anybody have any type of advice ?
bump .... im willing to donate !
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Faux my name is neidlinger and I get assfucked by you and other homos.
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Nice to get help from the master himself
Sent from my HTC Glaciee using XDA Premium App
Double post by mistake. my bad
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Sigh ... no luck. I used your GB kernel with the Royal Ginger 1.6 rom ... rafyvitto thinks it might be my hardware so i was prob gonna have somebody take a look at it sometime this week .. what a bad one !
For what ever reason if i am at home, i have to use static ip address to get on my router, no other devices on the network have this issue, including my old phone. its probably not related to your problem but worth trying.
[via XDA premium]
Related
New as of Saturday August 8th
I will update the files every time I find a problem
WARNING PLEASE READ:
Project JIT is highly highly experimental! If you are to do this, MAKE A NANDROID BACKUP IN ROM MANAGER OR RECOVERY! There are always chances of something going wrong. I nor anyone else is responsible of what happens.
Experienced users please know the possible risks:
Boot Looping, requiring a restore
Constant FC's
Wiping everything
These are just the risks, please note it is not 100%
JIT stands for Just in time compiler. It does not like Touchwiz, so download ADW.Launcher or LauncherPro before starting and set it as default.
This whole process is in ADB. If you dont know how, or what it is, DONT DO IT!
Things to do before you start:
-Download a different launcher than TouchWiz
-Make a backup in recovery or Rom Manager
-Did I mention DO A BACKUP!
-If you have an external SD card, pull it out
-Download the vmlibs file
What I expect you to know before you start:
-ADB
-What JIT is
-How this will effect the performance
-The risks
-How its not my fault if you screw your phone over
-How experimental this is
-How to make a nandroid backup
-How to make a nandroid restore
Remember, this is experimental and I cannot guarantee for it to completely work.
Download This- vmlibs.zip
Then follow these steps:
-Make a backup!!!
-Create 2 folders on your internal sdcard: “jit” & “dalbk”
-Extract the vmlibs.zip to the “jit” folder on your sdcard
-Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad, text edit or similiar program.
-Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Edit the following line:dalvik.vm.startheapsize=8m
to: dalvik.vm.startheapsize=12m
-Save the changes
-Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit, but if your phone boot loops, thats why you have A BACKUP!
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
While in recovery, wipe the dalvik cache, this will prevent it from boot looping.
To Disable
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
If that fails, that is why you have a backup. To restore, go to recovery, click on nandroid, and restore from your backup.
Reserved for future posting
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
LGSilva said:
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It didn't here. Not sure if that is due to other fsckup or the fact that I was running I9k rom with my kernel and sdcard hack...
Restoring to stock to give this a whirl
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
hansmrtn said:
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
Click to expand...
Click to collapse
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
NukaCola said:
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
Click to expand...
Click to collapse
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
hansmrtn said:
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
Click to expand...
Click to collapse
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
NukaCola said:
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
Click to expand...
Click to collapse
Yeah, thats why I had to fix some stuff lol. I noticed that it wouldnt go past the att screen. Now it should work correctly. The worst that could happen now is it boot loops on the Galaxy S screen
Haha I was just about to post the same problem, downloading new file and trying it again!
Zilch25 said:
Haha I was just about to post the same problem, downloading new file and trying it again!
Click to expand...
Click to collapse
Hey, when you edit the build.prop to add the dalvik vm line, can you look for the vm heap size and change it from 48 to 32? I am about to test doing that, and I would like more feedback
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Zilch25 said:
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Click to expand...
Click to collapse
Dont worry, I will try it
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Zilch25 said:
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Click to expand...
Click to collapse
Do you know how to run a logcat?
Its gonna take a while because its re writing the dalvik cache
That I do not, but I'm willing to try it if you can give me a quick crash course
Zilch25 said:
That I do not, but I'm willing to try it if you can give me a quick crash course
Click to expand...
Click to collapse
Well I am looking at my logcat now, and it is just repeating boot animation.
A logcat is useful, so how you do it is adb logcat.
I changed a couple things to test around with here is what I did-
I added all of this to the build.prop-
#JIT
dalvik.vm.execution-mode=int:jit
and changed:
dalvik.vm.heapsize=48m
to
dalvik.vm.heapsize=32m
Right now I am resorting to try the older vmlibs with the new settings
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Zilch25 said:
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Click to expand...
Click to collapse
No thanks for the feedback. Its only worked for me once, and then when I rebooted it got stuck in a boot loop.
Whats a device thats running android 2.1, and has a jit hack that is extremely similar to the Galaxy S series?
OK... so I am trying to get the Internet up and running for this Samsung Epic. I almost have it down, but there is something that I know is wrong from the other Android phones that I have flashed before.
For Metropcs internet to work we have to install a script: u2nl and autostart file.
Here is my problem: I can put the autostart file into the data/opt folder, but when I try and paste the u2nls file into /system/bin it tells me that it is only a read only....
Now when I try in commond prompt and I try and do adb remount it now tells me No such file or directory or remount failed.
If I can get that u2nl file to stick in there I know I will be good to go.
I dont know much about adb commands, so here is what I did:
I plugged phone in on charge only mode. USB debug is checked.
cd c:\android\tools
adb remount **wont work either...it will fail, which probably why I cant write into the system/bin file.
adb push c:\autostart.sh /data/opt/autostart.sh
adb push c:\android\tools\u2nl /system/bin/u2nl **wont work
Adb shell
su
chmod 0755 /system/bin/u2nl **gives me an error
chmod 0755 /data/opt/autostart.sh
Please help!!!!!
Thanks.
I have one bad and one good news for you
First the good one...
Reboot into clockwork recovery and mount /system...retry
Bad news...
That method or the anycut method does not work...I already spent 2 days trying so many settings and it just doesn't work.
Do u have mms working?
Sent from my SPH-D700 using XDA App
My MMS does not work since my Internet does not work.
There are people that have gotten this to work on Metro already with everything at my local metro shop in CA.
I am pretty sure once I get this u2nl file to stick, it will work. The 3G arrows starts up and then it seems like it will start to run the autostart script and then errors out.
Let me try what you said and I am also going to try another rom.
under clockwork recovery which mount do I do? mount /sd-ext
What is suppose to be mounted and unmounted?
it says: unmount /system **meaning its already mounted right?
if its says unmount /system..its already mounted
just go to cmd and
adb remount
adb push c:\android\tools\u2nl /system/bin/u2nl
ect..ect..
if the remount doesnt work..download busybox installer and update busybox to the latest version and retry
autostart\u2nl its not required to be able download\send mms..you need to have the right apn settings and the 3g arrows dancing lol,,
ok so when I hit adb remount it says "remount failed: No such file or directory
I downloaded the busybox, when I open it it says:
Busybox 1.17.1 is what I have in phone
Busybox 1.18.0 git (unofficial) I can download
Below that it says where do I want to install busybox:
/system/xbin/ or /sbin/
Where do I install and should I install that unofficial version?
tosh1 said:
ok so when I hit adb remount it says "remount failed: No such file or directory
I downloaded the busybox, when I open it it says:
Busybox 1.17.1 is what I have in phone
Busybox 1.18.0 git (unofficial) I can download
Below that it says where do I want to install busybox:
/system/xbin/ or /sbin/
Where do I install and should I install that unofficial version?
Click to expand...
Click to collapse
should be /system/bin (no x or s before bin)
1.17.1 is fine
try again if that doesnt work..in clockwork recovery try this
adb shell
su
remount rw
exit
exit
and try again..im running out of options here..lol
hey did it work? how is it going with full flash?
also make sure you root with the new zip version..some previous versions dont have the remount scripts
adb commands
u2nl does not need to be run in /system/bin. just edit the autostart.sh to reflect your location change. if u insist on running from /system/bin, then do this
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
exit
exit
then push u2nl to /system/bin
Thanks buddy it looks like it worked....
Now I have the data arrows showing but something is not kicking in yet. I think I am missing something. I changed all the right settings on Qpst have the right passwords now (msl - whiterabbit.org) all files in the right place.
I have done this on Eris full flash, evo full flash, incredible full flash, but this Epic is driving me nuts...
kinda stuck right now.
Lol and now we are 2 stuck in the same place. I had flash tons of droids, evos, but this epic is making me going nuts..I don't know what's going on either..I had seen epics on cricket full flashed with no problem..but seems samsungs don't like metropcs' proxy
Sent from my SPH-D700 using XDA App
What rom r u using bro? Maybe the epic rom I'm using desnt support iptables for some reason..
I'm going to try another rom tomorrow.. either way keep me updated as well.
Sent from my SPH-D700 using XDA App
stock (rooted of coutse) with the iptables file in the bin folder . that used to work in my old droid, just set the correct permissions, andromeda v1.1.x, mixupkernel DI18-voodoo, and epic experience (dont remember which version) and none worked
I have some ultrasecret info..lol..supposedly the normal autostart.sh file does not work with samsungs, there is different modified version for the moment and the fascinate but i cant find it
i cant test this anymore cus i dont have metro but thanks to chimstar in the mo-fi forum, dial ##3282# go to edit mmsc url, type your msl, and edit the mmsc server to the metropcs one
if that doesnt work, download the apn back and restore app, delete all apns and restore metropcs working, if you dont have one, edit the xlm file to match all the correct info
make sure you reboot
see if that gets your mms working..i didnt need to have the autostart method running for my droid to get mms
Solved: See post #4
Obviously for those with a modded kernel and broken MAC.
If we knew the real MAC address for the specific device, couldn't we set the module's MAC to our real one?
Or just a MAC spoofer? But more like an un-spoofer..
Im looking for the answer as well...
I have been through every oc kernel so far, only stock/insmod seems to keep the mac addy. This might be the best option until a proper solution is found, if anyone has an idea on how to insmod on startup that would be good.
I also tried ipconfig eth0 hw ether, but got an invalid argument.
tijuanacartel said:
Im looking for the answer as well...
I have been through every oc kernel so far, only stock/insmod seems to keep the mac addy. This might be the best option until a proper solution is found, if anyone has an idea on how to insmod on startup that would be good.
I also tried ipconfig eth0 hw ether, but got an invalid argument.
Click to expand...
Click to collapse
Can't you setup a script that insmod's and set that up to run on startup?
I'm sure there is somewhere in the ROM where a script can be added for it to run on boot, or at least a boot time Android one...
init.rc perhaps?
Okay i found it... there is a file called /bootcomplete.rc that calls
/system/xbin/busybox run-parts /system/etc/init.d
so, on stock kernel with oc-dz.ko:
Code:
# cd /system/etc/
# mkdir init.d
# cd init.d
# echo insmod /system/lib/modules/oc-dz.ko pll2_l_val=74 > overclock
# chmod 0755 overclock
will load the module at boot. wifi mac is correct
Okay I've been using this for most of the day and just had a hard crash on level 99 of robo defence(F7U13!) Looking into it, it seems this kernel module only seems to step up from 700 straight to 1497! I'm disabling it for now.
Apparently cyanogen is quite a lot faster than the stock Sense, even without overclock. As soon as it hits RC2, I'm gonna give it a shot.
tijuanacartel said:
Okay i found it... there is a file called /bootcomplete.rc that calls
/system/xbin/busybox run-parts /system/etc/init.d
so, on stock kernel with oc-dz.ko:
Code:
# cd /system/etc/
# mkdir init.d
# cd init.d
# echo insmod /system/lib/modules/oc-dz.ko pll2_l_val=74 > overclock
# chmod 0755 overclock
will load the module at boot. wifi mac is correct
Click to expand...
Click to collapse
EDIT
Trying from a Terminal I get: "undable to chmod overclock: Read-only file system"
I tryed from ADB and all commands were accepted, file was created and chmod processed, but after reboot the OC module is not loaded
What ROM are your using ??
Obviously you should remount your system partition rw
tijuanacartel said:
Obviously you should remount your system partition rw
Click to expand...
Click to collapse
OMFG I really need to sleep a little
What ROM are you using ?? Have you changed the Kernel ??
at the time i was using stock.. currently using virtuous from rom manager
I've been strugglin with that command line for days, trying to find a way t make it stick from boot (and not typing it from a console), I finaly made it today via updater script (update.zip).
I also included the stock radio module and the stock kernel (rooted) to the package, so it can serve as a "rescue kit" for other users stuck with the MAC WiFi shizz. I shared it @ devs forum.
I've debranded a UK Orange Flipout and unlocked to use on Vodafone UK.
The mobile signal is terribly weak and spends more time with no bars that with. It makes the phone useless as a phone however great the design is.
Sitting next to another android phone on the same network the bars are almost full on the other phone - when showing nothing on the Flipout.
Does anyone else have this problem? Is there something I can do to re-configure the phone and make it work as a phone? I've had all the data settings from Vodafone reset for MMS and data etc.
If no answer it will have to go back to stock ROM and back to the shop.
Thanks.
Hey, I got the same problem. Had me temporarily switch back to Milestone 'cause Flipout wasn't able to even connect to the service..no signal at all. I noticed that Flipout has slow network acquiration compare to Milestone. But, I have to point out that I flashed it from stock to UK ROM without BLUR so it's more likely possible that something just went wrong. For now I blame the basebands and try to solve it that way..somehow. let me know if any news
Sent from my Milestone using XDA App
ok, it was the baseband.. i changed it from what it was to this (attachment) and everything's fine.
you have to be rooted, and remount system as r/w
the original baseband files are located in /system/etc/motorola/bp_nvm_default
basically you need to replace this folder with the new one and set the same permissions as the original files had. i don't know if you know how so just for sure, here's the how-to
i suggest you doing this:
0]if you are not rooted, install Universal Androot and press Go Root, then reboot your phone
1]unrar the attachment to your phone's sdcard
2]boot up the phone, switch to airplane mode
3a]if you have Root Explorer, navigate to /system/etc and push remount as r/w
3b]if you don't have that, install Root Toolbox go to Mount-System Mount Options-Mount System R/W
4]fire up Terminal Emulator
5]enter those commands: (enter after each line)
Code:
su
cd /system/etc/motorola
cp -R /sdcard/bp_nvm_default bp_nvm_default_nw
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
chmod 755 bp_nvm_default_nw
chown root.root bp_nvm_default_nw
cd bp_nvm_default_nw
chmod 644 *
chown root.root *
cd ..
rm -R bp_nvm_default
mv bp_nvm_default_nw bp_nvm_default
reboot
6]after the reboot, turn off flight mode, let the phone get registered to network and see what happens.. hope this will fix your problem.
it's a bit tricky, i actually had to reboot after mounting system to R/W and giving Superuser permissions and mount again because somehow it didn't work for the first time.. anyway, let me know if anything goes wrong
Thanks, that looks a bit technical but ill give it a go... thanks for info.
Sent from my Transformer TF101 using Tapatalk
Well I gave this a go - and I kept getting permission denied. sounds like problem you had with the system RW refusing to allow a copy.
Anyhow I am hoping I might have fixed it by using this link
http://dext3r.komodin.org/
And there is a radio file you can install under Quick FAQ with different country baseband radio files. Might help someone else ...
it didnt work
well, i did everything as written except i used ES File Manager to mount the /system as R/W and when it came to:
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
it said "cp: can't create symlink '/sdcard....': Operation not permitted" for every file so i just did it manually with ES File Manager... that is only a backup anyway and shouldnt affect anything.
it just doesnt work.
and why cant i just drop the baseband files in there with copy and paste? that didnt work either.
i need baseband files for T-Mobile on the US network for the Flipout. does anyone have any others i could try?
thanks!
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !
Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Click to expand...
Click to collapse
Go to the play store, download & install Goomanager, install TWRP. CWM seems to have a few issues with teh TF101's.
Hello, i have a CWM flashable TWRP recovery, i even tested it, but wasn't able to work with it, it was very slow and didn't found files i was looking for, i will regive it a try.
Edit : I have the exact same problem when flashing SuperSU from TeamWin recovery, everything act as i don't have SU, i can grant rights to anything i want it will still act as i don't have root, and SuperSU is unable to update it own binary at startup
Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !
Click to expand...
Click to collapse
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app
idcrisis said:
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app
Click to expand...
Click to collapse
Hello, i cannot do anything if not under CWM (even ls gives a "not found" if not in CWM)
I tried /system/xbin/su and got a
"sh: /system/etc/mkshrc[8]: id: not found"
Rebooted in CWM and tried to install Busybox
i mounted /system /data and /sdcard
i created the folder /data/local/temp
cp /sdcard/busybox /data/local/temp
applied /sbin/chmod 755 to /data/local/temp/busybox
ran /data/local/temp/busybox --install /system/bin and got a "Invalid cross-device link" error on every commands busybox tried to install
http://pastebin.com/g3DMHbJz
Tried to install it on /system/xbin too, but same error
Note : When i use /system/xbin/su in CWM, it change name to [email protected] from ~# while it doesn't in normal mode
Edit : Titanium backup rework :
In CWM, i copied busybox to /system/bin, and i installed it to /system/bin from /system/bin
cp /data/local/temp/busybox /system/bin
/system/bin/busybox --install /system/bin
I'm now checking if only Titanium backup works or if everything else too
Thanks for your help, i don't know if it's done yet, but i made a progress using your information !
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat
Magissia said:
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat
Click to expand...
Click to collapse
Good to see everything works. Give the candy to some children in the neighborhood mate, I'm watching the calories
Cheers!
Sent from my Transformer TF101G using xda app-developers app