Adding Parted, Sdparted, and mke2fs utilities to our Devices - Huawei MediaPad M2

So i found this trying to find an answer on another device i was working on, even though I had searched for this one as well.
Anyway, only thing you need to do is download the files, and use whatever method you desire to put them in /system/bin folder.
Change the permissions of the files to 0755 (and yes I mean 0755 and not 0644) and reboot. Enjoy.
Download Here

Related

[Q] Boot Animation Troubles

UPDATE: SOLVED!!!!!!!!!!!!!!!
Much thanks to everyone, esp Zerf!
Okay, So I spent about half the evening last night trying to figure out how to change my boot animation, and I can't get it. I was able to do it before I moved up to Froyo (8.1 leak), but now, nothing. I tried the fix posted elsewhere in these forums, and it didn't work.
So here's what I want. I want the "rotting apple" boot animation from droidboots.com, and I want the "droid" sound to go with it.
First person that comes up with a zip file of only the boot ani, nothing else changes, that I can install in Clockwork Recovery that works, I'll donate $5 to their beer fund. Bonus happy points if you tell me how you did it.
I'm tired of failing, and would just rather it work. PLEASE HELP!?!
Nobody wants to make an easy $5?
I will admit I am much too lazy to actually go out and find the files, but chances are if you've been working at it, you've got 90% of the work done already. Since you've got CWM installed, this should be cake.
1. Boot into CWM recovery, and go to partitions
2. Mount /system
3. go to your desktop, and copy your bootanimation.zip (rotten apple) and android_audio.mp3 (droid sound) files to the same directory as your ADB install
4. Open a command prompt, go into the directory with ADB+the files just mentioned are located, and copy/paste (or just type) the following items:
a. adb push bootanimation.zip /system/media/
b. adb push android_audio.mp3 /system/media/
5. Reboot your phone and enjoy.
6. Donate the $5 to ihftp69's SkyRaider beer fund.
partizan81 said:
I will admit I am much too lazy to actually go out and find the files, but chances are if you've been working at it, you've got 90% of the work done already. Since you've got CWM installed, this should be cake.
1. Boot into CWM recovery, and go to partitions
2. Mount /system
3. go to your desktop, and copy your bootanimation.zip (rotten apple) and android_audio.mp3 (droid sound) files to the same directory as your ADB install
4. Open a command prompt, go into the directory with ADB+the files just mentioned are located, and copy/paste (or just type) the following items:
a. adb push bootanimation.zip /system/media/
b. adb push android_audio.mp3 /system/media/
5. Reboot your phone and enjoy.
6. Donate the $5 to ihftp69's SkyRaider beer fund.
Click to expand...
Click to collapse
They actually don't go there anymore...they go in /system/customize/resource and they need to be named differently...
http://forum.xda-developers.com/showthread.php?t=746875
Otherwise the steps are good.
phikai said:
They actually don't go there anymore...they go in /system/customize/resource and they need to be named differently...
http://forum.xda-developers.com/showthread.php?t=746875
Otherwise the steps are good.
Click to expand...
Click to collapse
Odd, when I flashed SkyRaider 2.2, the files were located there, and when they were replaced in the same location with new files the animations changed properly.
The problem is, for whatever reason, when it changed locations, they changed the file name format. It should have been a simple name change, but it's not, ADB push does nothing but give a blank boot up. I screwed with it for about two hours the other night, and came to the conclusion that I'm:
A) Not knowledgeable enough to do it myself
B) Too Stubborn to let it go and use the Generic one
C) Not going to screw up my phone by not asking for help.
So, thanks for the try!
What flavor of ROM do you have? skyraider needs bootanimation.zip to go into /system/media.. I believe for the original 8/1 leak it's under /system/customize/resource
If you have ROM Manager installed, then go to download ROM and under Ihtfp69.. choose Goodies for 2.2 and you have an option to download a few different boot animations.. with or without sound..
try one of these first and see if you are able to make a switch.. if yes.. then report back.
I'm running the 8/1 froyo update, I've been trying under system/customize/resource with VZW_bootanimation.zip as the file name, as it was stated in another thread that this is the proper way to do it on the 8/1 leak..... I even went so far as to completely copy the "stock" animation, and move all the images, rename them, and make sure all the settings are correct, and trying it that way, nothing.
I JUST did this and it worked for me. I am on the 8/1 2.2 leak as well.
Plug in phone
reboot to recovery
Code:
adb reboot recovery
Once booted in to recovery do
Code:
adb shell
mount -a
It will give you this error. Thats fine (It's just saying it couldnt mount the sdcard which we dont need right now.)
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk1 on /sdcard failed: Invalid argument
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
now type exit to get back to your computer prompt.
Now push your bootanimation.zip you want to /system/customize/resource
Code:
adb push bootanimation.zip /system/customize/resource
now now get back in to adb shell and type
Code:
cd /system/customize/resource
then ls *.zip and it should look like this. l = lowercase L
Code:
/system/customize/resource # ls *.zip
ls *.zip
bootanimation.zip VZW_bootanimation.zip
Now we want to rename the vzw boot animation to .back to save it
Code:
mv VZW_bootanimation.zip VZW_bootanimation.back
Then we want to rename the new bootanimation to the vzw bootanimation
Code:
mv bootanimation.zip VZW_bootanimation.zip
OPTIONAL STEP: IF YOU DONT WANT THE DROID SOUND ON BOOT
Code:
mv Droid.mp3 Droid.back
type exit and adb reboot . It should now boot with your new boot animation.
You sir, are a GOD.
DM me your email, and I'll papal you the $5, or send it to wherever you choose!

help changing boot screen

Hey all, ive been trying to change my boot screen to the haters gonna hate one for a few days now but cant seem to get it to work at all, i have full root and tried to the fastboot method and recovery/adb method. no matter what it stays the same as the one i had originally, i never get errors when trying to push the files if someone can give me instructions for dummies haha or another method id really appreciate it sorry for being a noob at all this.
I had the same problem
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
oh yeah sorry i should have included that i am on evios 1.2 beta 2 rom
I'm not familiar on where to place boot on this rom. Try all three locations I suggested. System customize resource. System media. Data local. Tell me if it works out.
I had this animation on EViO. I just pushed it from my desktop to system/media. Worked fine for me.
how do you push it from the desktop? i tried all 3 methods posted above and none worked. i had the file in the android sdk tools folder though...also whenever i try to do adb remount i get "remount failed:invalid argument" and adb root gives me "error:closed" i tried killing adb and restarting but no luck
This might be an obvious question, but do you have USB debugging enabled on your phone? Under Setting>Applications>Development
You arent going to be able to push anything if you can't get ADB running first.
yeah debugging has been enabled the whole time
ok have you been in recovery mode?
try typing
adb shell
su (make sure #comes up.)
exit (retype until you get back to the tools directory)
then do the push commands to system media, system customize resource, and data local.
Just use this program. Its as easy as it gets.
http://forum.xda-developers.com/showthread.php?t=701295
dkdude36 said:
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
Click to expand...
Click to collapse
Putting sound in boot animation doesn't work with cm6. Just to clarify. No one has been able to get it to work unless you found something out to make it work please share as I have hates going to hate also and want to use haters everywhere mp3 and is perfect for it.
Sent from my PC36100 using XDA App
yeah i have also been in recovery mode every time i tried to run a command prompt for adb...i tried that when i hit adb shell i get # but when i type su after the # it says "/sbin/sh: su: not found"
mount: mounting /dev/block/mtdblock4 on /system failed: Device or resource busy
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
thats what i get when in command prompt when i try to use the program you just posted above
Want a easier way? Use root explorer and copy and paste. Works for my every time. It's in the market. And root explore you can manually turn writeable on and off to move it into system. It's on the top right of screen in root explorer when you go into system folder.
Edit: the command you are tying to put in enables you to push and pull in the system folder. Root explore you can just click a button.
Sent from my PC36100 using XDA App
Good idea
Root explorer works most of the time. If you have the cash, go ahead. You should make site out posted though.
/sbin/sh: reboot: not found
been trying to use adb and i keep on getting that....any of you know a fix?

[Q] Gfree Rooting!

Hey guys,
I took the advice of tons of people here to try the gfree method instead of the hboot or something, or the visionary permaroot.
the thing is, i did it my way and was too lazy to install ADB cuz it always failed and I don;t know how to use it.
I got a desire z- asian version
with a 1.2 version (NOT 1.7 that can't use gfree)
anyway
here's what i did
1) Installed Visionary to Temproot
2) got superuser for terminal emulator (ON PHONE)
3) chmod 777 the GFREE File on SDCARD
4) Tried to run it with the ./gfree -f command
5) IT SHOWS PERMISSION DENIED....WHYYY!???
WTF?
Anyway, if theres no o
ther way than ADBing this, I'll just go ahead and use the .ko file from the other rooting method..
THANKS GUYS
kwhkkwhk said:
Hey guys,
I took the advice of tons of people here to try the gfree method instead of the hboot or something, or the visionary permaroot.
the thing is, i did it my way and was too lazy to install ADB cuz it always failed and I don;t know how to use it.
I got a desire z- asian version
with a 1.2 version (NOT 1.7 that can't use gfree)
anyway
here's what i did
1) Installed Visionary to Temproot
2) got superuser for terminal emulator (ON PHONE)
3) chmod 777 the GFREE File on SDCARD
4) Tried to run it with the ./gfree -f command
5) IT SHOWS PERMISSION DENIED....WHYYY!???
WTF?
Anyway, if theres no o
ther way than ADBing this, I'll just go ahead and use the .ko file from the other rooting method..
THANKS GUYS
Click to expand...
Click to collapse
Ive seen this before, which files did you put on the sdcard, If you put the entire gfree02.zip file on your sdcard this is worng. You need to unzip the gfree02.zip file and place only the gfree file from the unzipped gfree02.zip file on the root of your sd card.
then re-run using this Code:
Code:
$ su
# cd /sdcard
# chmod 777 gfree
# ./gfree
# sync
i did everything as said, moved only the gfree file onto the sdcard.
everything works until ./gfree
it says: "./gfree: permission denid"
i don't really know whats wrong. the kernels right - its a stock 2.2 asian desire z on 1.2 version or something.
thanks SO MUCH For the reply though. I REALLY APPRECIATE IT
The guide says not to use Visionary for temp root before using gfree, in fact it says to either turn it off (if set to auto-soft-root on boot) or uninstall it altogether.
the gfree method has you use the rage method to obtain temp root.
raitchison said:
The guide says not to use Visionary for temp root before using gfree, in fact it says to either turn it off (if set to auto-soft-root on boot) or uninstall it altogether.
the gfree method has you use the rage method to obtain temp root.
Click to expand...
Click to collapse
Thats if your gonna temp root with Rage, requires ADB to push the files, which he is trying to avoid using ADB, gfree has been done the way he is trying before.
I don't believe you can run the gfree program from the sdcard mount point. You should try moving it to the phone itself (try putting it in /data/local directory as instructed in the wiki). That should take care of your permission denied issue.
Also, you may want to copy over all of the other files as listed in the wiki (except for rage since that's not needed for you). The wiki says you need to run the root command after running gfree (it'll set up things like busybox and su for you). You could also do all it manually yourself if you really wanted to...
But how do I move it off the sdcard? I tried using es file explorer but it says gfree can't be moved. And I cant mount the internal memory. Thanks for the advice though
If you are temp rooted you should be able to remount your file system as read/write, you will need to do this to copy files to the /system path and set permissions.
raitchison said:
If you are temp rooted you should be able to remount your file system as read/write, you will need to do this to copy files to the /system path and set permissions.
Click to expand...
Click to collapse
How would I do that?
remounting the file system? i can't find that option in settings...
and by copying the files, is that done through a file manager on the phone?
or on a computer?
thanks so much guys for the help
It shouldn't make a difference if gfree is on /sdcard or not.
To the OP - do you have a # (root) prompt when you are trying to run gfree ? You need that or it won't work. Have you followed exactly the commands that joemm posted, and you didn't get error messages from any of them ?
Yes I do have that sign. Everythin works (chmod, su) until the last code which is to run it.
kwhkkwhk said:
Yes I do have that sign. Everythin works (chmod, su) until the last code which is to run it.
Click to expand...
Click to collapse
Do "ls -l gfree" and copy and paste up here the output please. Something is still wrong.
It shows
Rwxr-x system sdcard_rw 134401 2010-12-11 08:57 gfree
steviewevie said:
It shouldn't make a difference if gfree is on /sdcard or not.
Click to expand...
Click to collapse
By default on my phone (running CM6), the sdcard mount point is mounted with the noexec option (so no direct execution of any binaries). I assumed it was this way on all roms for security reasons, but I'm not familiar with Visionary. Are you saying that Visionary remounts the sdcard as exec for you? Or that it's already that way by default for the stock rom? If so, then yes, you can leave gfree on your sdcard. You can check by running mount in the terminal. You should see an entry for /sdcard with all of its options after it. If you see noexec in there, you will either need to move the files to the phone or remount your sdcard with the exec option instead.
If you want to copy files over to your phone while rooted, you could use Root Explorer (probably easiest way). I believe there are other free programs that allow r/w access, but I haven't tried anyway. Otherwise, you should be able to copy over the files in Terminal. I think the data partition is mounted as r/w but you can verify with the mount command mentioned above (on the line containing /data, look for either rw or ro). If there is a rw, then just use the copy command to copy the files where you need to:
Code:
su
cp /sdcard/gfree /data/local
If the data partition is mounted as ro, you'll need to remount as rw first:
Code:
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /data
Pretty sure that won't be needed though.
ianmcquinn said:
By default on my phone (running CM6), the sdcard mount point is mounted with the noexec option (so no direct execution of any binaries).
Click to expand...
Click to collapse
ooh, ok, thanks, I never knew that. My apologies, that looks like why it's not running then.
If you want to copy files over to your phone while rooted, you could use Root Explorer (probably easiest way). I believe there are other free programs that allow r/w access, but I haven't tried anyway. Otherwise, you should be able to copy over the files in Terminal. I think the data partition is mounted as r/w but you can verify with the mount command mentioned above
Click to expand...
Click to collapse
Yeah, /data is mounted as rw by default, so should be fine to copy as you said.
Alright. This WORKS for running gfree
but for the step that makes the root "stick" according to the guide here...
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
where i says :
"You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
# /data/local/tmp/root
# sync
"
I can't find /data/local/tmp/root
so it fails to run..
any suggestions on this?
gfree runs fine. it says done when I did ./gfree -f
thanks guys for all the help!
kwhkkwhk said:
# /data/local/tmp/root
# sync
"
I can't find /data/local/tmp/root
so it fails to run..
any suggestions on this?
Click to expand...
Click to collapse
root is the binary that actually does the rooting, it's included in the gfree_temp-root zip. Did you copy that to /data/local/tmp or did you copy it somewhere else?
the only thing i did, if you were able to see my previous problem,
was just copying the gfree file over to the /data/local and running it
by ./gfree -f
other than that, i copied nothing else, since the guide using adb and the commands used moved nothing other than the gfree file i moved to /data/local
I didn't use the gfree_temp-root.zip folder, i used the gfree_02.zip (permaroot) folder.
and i temp rooted using visionary to get the needed gfree file onboard.
then do i need other filed then?
thank you so much for the quick reply.
kwhkkwhk said:
then do i need other filed then?
Click to expand...
Click to collapse
Yeah, root is actually just a script that installs things like busybox and su for you (see my earlier post).
You should copy those files to the proper locations listed in the wiki (pretty much every file but rage). It'll make life easier (otherwise, you'll have to do all of that stuff manually).
Congrats, you almost have a fully rooted phone.
THank you so much!
and thank you to all of you guys who helped me!
I managed to root my phone finally! Without adb!
YAY

Any way to get cwm back on without usb?

Well as a previous thread I made ive been having a crap load of issues with my usb not syncing with my comp. Some how I have the stock samsung backup with viperrom and dk28 modem.
What else can I do?
I need to atleast get an updated clockwork back on and i cant locate a thread for that without using odin or cwm 2. ect
My phone isnt bricked but it feels like it might as well be. i tried the app anycut to see if I could mass storage so I could atleast go back to stock to see if that was the issue but that didnt help.
I really could use some help as Im at my wits end with this.
Brief rundown:
flashed truly epic rebirth rom
phone goes haywire during low batt
usb mounting no longer works but still charges
installed drivers 5 times and nothing
tried my laptop but same error message
tried flashing other roms by directly downloading from phone and flashing through cwm 3
tried reseting back to stock with noobl thread but all of those aborted due to ext4 script
tried to remove ext4 script by changing clockwork versions
now stuck with stock clockwork and no where to go
downloaded anycut as its supposed to over ride issues with storage
rom manager doesnt work at all when trying to install clockwork. Keeps giving me an error.+
Phone still charges but
come on devs. there's got to be a solution to this or I missing something really easy lol
OK, im gathering that you are having issues with the Drivers, unless its a physical connection issue, like the other thread where the 'tooth' in his micro usb on the phone was not connecting, he bent it back... I would look at that last.
Ok, short of a cardreader and a DI18 update.zip...
Odin to DI18... this will get you back to start...
OK, known USB/driver issues:
Installing drivers, get them off this site, from a thread where others have success, just in case. I am assuming youre on winXP 32bit or whatever is normal... OK, so installing drivers... install drivers with phone unplugged from PC, then after the install, plug the usb into a motherboard USB port, not front, not PCI, not a hub... on the board itself. The PC should recognize it, and start going thru install thingys, of course ignore the install wizard if you have it enabled. What worked for me to get the last half of the drivers to install... I think modem is the one it tends to hang on, if it sits there forever, quickly disconnect the phone and reconnect it.... it should kick it back into installing drivers... you can check for drivers in your device manager in settings... look to make sure theres no ?s and make sure there is adb device...
next, to be sure, using the same USB port, start Odin, THEN plug in the phone, it should come up with a COM port in yellow and you should be able to flash from there, see Odin threads from there.
Oh and dont use the charging cable, thats all its good for, charging. I use a fat old USB from my old berry.
Well I tried everything you posted minus the get a new cord. I might get that tomorrow but it doesnt make sense as I went to sprint and the guy plugged his phone in with my cord and it worked just fine for him.
i remember seeing a update zip file that can be loaded on to the sd and updated through the stock samsung clockwork but i cant seem to find it anywhere?
noobl thread on reflashing without odin didnt do a thing and i honestly think it should be taken down as its posted in the wiki but there's got to be another file here someplace. no hate on noobl but there was so many people having issues with those zips
I keep posting these instructions for people, but apparently no one can find them. If you want cwm 2.5.1.0 instead of cwm 3, get the files from the one-click v2.5.5 instead. Oh and standard disclaimer: you shouldn't do this if you aren't comfortable using the command line on your phone and if you screw up, I'm not responsible.
---
The first thing you need is the OneClickRootCWM3.zip. You need a few files out of it.
Below is a copy of the code from the run.bat that does all the clockwork stuff. We're going to be translating this into something you can do without a computer.
Code:
:Redirector
echo Installing clockworkmod redirector
adb push recovery /system/bin/recovery
adb push recoveryfiles /system/bin/recoveryfiles/
adb push recoveryres /system/bin/recoveryres/
adb shell busybox chmod -R 0755 /system/bin/recoveryfiles/*
adb shell busybox chmod -R 0755 /system/bin/recoveryres/*
adb shell chmod 0755 /system/bin/recovery
adb shell sync
goto:Clockwork
:Clockwork
echo Installing clockworkmod recovery...
adb push redbend_ua /data/local
adb shell chmod 755 /data/local/redbend_ua
adb push zImage /data/local/tmp/zImage
adb shell /data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
If you paid attention to the code, you probably noticed which files we want. They are:
recovery
recoveryfiles/* (the whole folder)
recoveryres/* (the whole folder again)
redbend_ua
zImage
Put these files somewhere easy to find on your sdcard, such as a folder named cwm.
Now, open a terminal on your phone. We'll start with the redirect, just like the one-click does. If you put the files in a folder called cwm, then enter the lines below one at a time into the terminal.
Code:
remount rw
cp /sdcard/cwm/recovery /system/bin/
cp /sdcard/cwm/recoveryfiles /system/bin/
cp /sdcard/cwm/recoveryres /system/bin/
##Then you *may* have to copy the subfolder in recovery res by doing the following
cp /sdcard/cwm/recoveryres/* cp/system/bin/recoveryres/
busybox
chmod -R 0755 /system/bin/recoveryfiles/*
chmod -R 0755 /system/bin/recoveryres/*
exit (to exit busybox and drop back to toolbox)
chmod 0775 /system/bin/recovery
sync
I don't remember for sure, but your phone may reboot now. If it does, then enter "remount rw" again so that you have write access to the system. Now to finish installing cwm.
Code:
cp /sdcard/cwm/redbend_ua /data/local/
chmod 755 /data/local/redbend_ua
cp /sdcard/cwm/zImage /data/local/tmp/zImage
/data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
That last line calls redbend_ua with the "restore" flag and puts "/data/local/tmp/zImage" into the place where the recovery belongs, or "/dev/block/bml8" The phone should reboot now and you will have your new recovery.
Then if you want to clean up the left over stuff
Code:
rm /data/local/redbend_ua
rm /data/local/tmp/zImage
Have fun.
DiGi760 said:
I keep posting these instructions for people, but apparently no one can find them. If you want cwm 2.5.1.0 instead of cwm 3, get the files from the one-click v2.5.5 instead. Oh and standard disclaimer: you shouldn't do this if you aren't comfortable using the command line on your phone and if you screw up, I'm not responsible.
---
The first thing you need is the OneClickRootCWM3.zip. You need a few files out of it.
Below is a copy of the code from the run.bat that does all the clockwork stuff. We're going to be translating this into something you can do without a computer.
Code:
:Redirector
echo Installing clockworkmod redirector
adb push recovery /system/bin/recovery
adb push recoveryfiles /system/bin/recoveryfiles/
adb push recoveryres /system/bin/recoveryres/
adb shell busybox chmod -R 0755 /system/bin/recoveryfiles/*
adb shell busybox chmod -R 0755 /system/bin/recoveryres/*
adb shell chmod 0755 /system/bin/recovery
adb shell sync
goto:Clockwork
:Clockwork
echo Installing clockworkmod recovery...
adb push redbend_ua /data/local
adb shell chmod 755 /data/local/redbend_ua
adb push zImage /data/local/tmp/zImage
adb shell /data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
If you paid attention to the code, you probably noticed which files we want. They are:
recovery
recoveryfiles/* (the whole folder)
recoveryres/* (the whole folder again)
redbend_ua
zImage
Put these files somewhere easy to find on your sdcard, such as a folder named cwm.
Now, open a terminal on your phone. We'll start with the redirect, just like the one-click does. If you put the files in a folder called cwm, then enter the lines below one at a time into the terminal.
Code:
remount rw
cp /sdcard/cwm/recovery /system/bin/
cp /sdcard/cwm/recoveryfiles /system/bin/
cp /sdcard/cwm/recoveryres /system/bin/
##Then you *may* have to copy the subfolder in recovery res by doing the following
cp /sdcard/cwm/recoveryres/* cp/system/bin/recoveryres/
busybox
chmod -R 0755 /system/bin/recoveryfiles/*
chmod -R 0755 /system/bin/recoveryres/*
exit (to exit busybox and drop back to toolbox)
chmod 0775 /system/bin/recovery
sync
I don't remember for sure, but your phone may reboot now. If it does, then enter "remount rw" again so that you have write access to the system. Now to finish installing cwm.
Code:
cp /sdcard/cwm/redbend_ua /data/local/
chmod 755 /data/local/redbend_ua
cp /sdcard/cwm/zImage /data/local/tmp/zImage
/data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
That last line calls redbend_ua with the "restore" flag and puts "/data/local/tmp/zImage" into the place where the recovery belongs, or "/dev/block/bml8" The phone should reboot now and you will have your new recovery.
Then if you want to clean up the left over stuff
Code:
rm /data/local/redbend_ua
rm /data/local/tmp/zImage
Have fun.
Click to expand...
Click to collapse
So will this work when i currently have the stock samsung backup?
Basically i download the OneClickRootCWM3.zip directly from my phone then go into say astrofiles and remove the files you mentioned and put it in a file named cwm and go to android terminal emulator from there?
If i can get this to work and get back to cwm3 what do you suggest I do next to get the phone back to stock since the usb mount work and I can't even use odin? all the flash zips from noobln thread didnt work.
seoulseek80 said:
So will this work when i currently have the stock samsung backup?
Click to expand...
Click to collapse
Yes. This is how the one-click installs cwm over stock backup.
Basically i download the OneClickRootCWM3.zip directly from my phone then go into say astrofiles and remove the files you mentioned and put it in a file named cwm and go to android terminal emulator from there?
Click to expand...
Click to collapse
Get the files below I mentioned below the first code block and put them in a folder called cwm.
If i can get this to work and get back to cwm3 what do you suggest I do next to get the phone back to stock since the usb mount work and I can't even use odin? all the flash zips from noobln thread didnt work.
Click to expand...
Click to collapse
What were you flashing the zips with? They don't work with anything but cwm, so if you don't have cwm...
DiGi760 said:
Yes. This is how the one-click installs cwm over stock backup.
Get the files below I mentioned below the first code block and put them in a folder called cwm.
What were you flashing the zips with? They don't work with anything but cwm, so if you don't have cwm...
Click to expand...
Click to collapse
I was flashing the roms with cwm3 but i mean flashing back to stock with odin as there doesnt seem to be a way to flash back to stock with cwm3.
You probably want to use the "ReRFS" dk28 rom to convert back to RFS, then try flashing noob's di18.
DiGi760 said:
You probably want to use the "ReRFS" dk28 rom to convert back to RFS, then try flashing noob's di18.
Click to expand...
Click to collapse
ok. Ill look for a link for that. in your opinion do you think its possible that reverting back to stock everything might fix this usb mounting issue? I litterelly tried everything else. i mean could have one of the roms messed up the internal phone usb
A rom shouldn't ruin your usb, especially not the roms we have available to us. Having the same issue in different roms would lead me to believe it is a hardware problem. It may just be coincidence that it started after you flashed a rom. If you have the same problem when you make it to di18, then there really isn't anything software can do for you. You'll have to take it to a service center and have them order a refurb from asurion.
Well good news is that sprint will issue a new phone to me through mail as it is a manufacturer defect and not a human error since I'm in the 1 year manufacturers warranty. i thought for a second i was screwed without that service plan but hopefully this fix you posted might help somewhat. well also since I dont want to send in a rooted phone anyways lol
Hehe did you actlly try the usb "tooth" fix? It was something wrong with mine, turned out to be some other guys problem as well. I have an inkling its a common issue. Caused by nothing more than the simple innocent act of unplugging your phone. I'm on my phone, so I can't find the post. If you're on a computer search through my posts to find the thread.
Sent from my baked and emotionless SPH-D700
squshy 7 said:
Hehe did you actlly try the usb "tooth" fix? It was something wrong with mine, turned out to be some other guys problem as well. I have an inkling its a common issue. Caused by nothing more than the simple innocent act of unplugging your phone. I'm on my phone, so I can't find the post. If you're on a computer search through my posts to find the thread.
Sent from my baked and emotionless SPH-D700
Click to expand...
Click to collapse
Wow squshy I wish i could thank you a thousand times. It wasn't the actual tooth but the copper contact that was bent up. So i sat there with my wifes eyebrow pluckers and pulled it and down and boom it works.
It was hardly noticeable but I wouldnt have looked unless you said something. lol
Thanks bro!

[Q] wpa_supplicant.conf permission issue

Hello.
I have had problems with my wifi for a few days. When I press the button in quick settings, nothing happens. When I press the toggle in the settings menu, the toggle switches to "on" but turns gray and it doesn't start searching for wifi networks. I have googled around and read xda forums and found out that it's very likely a problem with the wpa_supplicant.conf file in root/data/misc/wifi.
First I tried some advice that told me to rename the file so that the system would create a new one, and then it would work. I renamed it and even removed the file type ending, but no new wpa_supplicant.conf was created.
I tried setting the permissions for the file to 0755 rwxr-xr-x (I was told this is what they're supposed to be) but every time I reboot the phone they get reset to 0660 rw-rw---- and the problem persists.
I have tried changing the ownership of the file to system.wifi with chown cmd command in both terminal emulator and recovery. I have tried changing permissions both with root explorer and chmod in terminal emulator and recovery.
I can provide the file and any information you ask for on request, I'm not pasting it here from the beginning because I don't know what's relevant and what isn't, and I don't want to clutter the post.
Any ideas?

Categories

Resources