*****THIS IS FOR 2.1 ONLY*****
*****YOU MUST BE ROOTED*****
This will theme well over 90% of everything you see that has to do with the android os and blur if its still there.
Download my files here http://www.megaupload.com/?d=59KOD7MS
By downloading this you agree to take full responsibility for the actions you are about to preform.
Original files if needed http://www.megaupload.com/?d=0RNAMSQ3
If you have kousch's recovery installed, make a back up, if not use root explorer and make a back up of the following file.
/system/framework/blur-res.apk
download the other original system files here
Sorry no MM method only terminal emulator, so you have to suffer through typing about 10 lines of commands....
Unzip the entire contents onto your sdcard
open terminal emulator
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Services.jar /system/framework
cp /sdcard/framework-res.apk /system/framework
your phone will auto reboot. If you havent already applied a changed services or framework the boot animation will take a long time. If it by chance freezes, or does the boot sound but never shows the screen do a battery pull.
Once your phone reboots you will see a new lock screen and dark status bar with white font, if this is not the case you need to redo the steps above.
If you have root explorer, long press on the /system folder choose permissions. Make note of what permissions are set, grant everything permission for now. Change this back when your done. Failure to do so may cause an apk to not apply.
If you prefer you can reboot after each line command by simply typing reboot and hitting enter, just to make sure it boots clean, but its really not needed.
Put capitol letters when seen!!!! failure will cause duplicate applications!!!
Dont apply anything blur you deleted and dont want on your phone.
In terminal emulator
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/BlurPhone.apk /system/app
cp /sdcard/BlurCalendar.apk /system/app
cp /sdcard/BlurContacts.apk /system/app
cp /sdcard/BlurHome.apk /system/app
cp /sdcard/Browser.apk /system/app
cp /sdcard/Gallery3D.apk /system/app
cp /sdcard/Music.apk /system/app
cp /sdcard/Settings.apk /system/app
this one goes to new directory so pay attention, dont get type happy
cp /sdcard/blur-res.apk /system/framework
now type reboot and hit enter
phone may or may not have an extended boot.
If you use handcent and want it themed, uninstall your old one
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/com.handcent.nextsms.apk /system/app
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Enjoy
Credit to
Me
prodigy
skyraider
tparker76
Teenfaces
stewart1champ
quadjacks
hacku
RinTinTigger
Taypotts
moto
htc
928droid
fabulous
I learned a lot from looking at how everyone else themed to get ideas for mine.
all images came from google searches. Then edited as needed.
reserved for me
please wait... an operator will be with you shortly...
Whens the download going to be up?
Ok. Now that i reverted to stock i can't get my themed google maps to install.... sucks. Also my themed launcher pro keeps my registation code. So if i release that its stealing. I will work on these two tonight and see what i can do.
Either way, a dl will be posted in the morning.
Sorry
Sent via your mom and tapatalk
Maybe try re-signing it then install via adb install command as per the the autosign.bat method in my other post.
ignorant question. Can i install this using Rom manager?
No sir. But you have rom manager and haven't switched to 2.2?
sent by your mom on tapatalk
Yep but I used sbf switched back to 2.1......2.2 had a few bugs that drove me crazy
Sent from my DROIDX using Tapatalk
running this theme
Ok backup made through rom mamnger. So im currently running rooted 2.1. Ive download the files and they are upzip on the root of the SD..can i simply type the codes in termnal emulator app on the phone and this should work?
catalystsupreme2 said:
Ok backup made through rom mamnger. So im currently running rooted 2.1. Ive download the files and they are upzip on the root of the SD..can i simply type the codes in termnal emulator app on the phone and this should work?
Click to expand...
Click to collapse
yup just follow the codes in the OP, you can omit what ever you dont want.
bad4u6669 said:
yup just follow the codes in the OP, you can omit what ever you dont want.
Click to expand...
Click to collapse
Big thanks for the help..everything worked flawlessly..very beautiful theme
catalystsupreme2 said:
Big thanks for the help..everything worked flawlessly..very beautiful theme
Click to expand...
Click to collapse
any time, head over to my 2.2 thread for a few upgrades, they still work for users on 2.1
Advantages or disadvantages
- Odexed ROMs are slightly faster, deodexed ROMs are slightly slower
+ You can make custom themes for your ROM
+ Performance los is negligible.
Requirements
xUltimate - http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
Busybox installed
Root
Automatic deodexing - Method 1, by r33p
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. Select option #15 then "do it all".
Deodexing (little harder, but contains useful information for your future Galaxy Gio modding experience)- Method 2, by me
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. On the main menu of xUltimate, choose option 5 (Pull and deodex all). Everything will be done for you here. Don't worry. You will see all your finished files in the folders 'done_app' and 'done_frame' which are located in the installation directory of xUltimate.
4. move folders 'done_app' and 'done_frame' folders to your sdcard, you can find these folders in the directory of xUltimate as described in the previous step.
5. Make sure the sdcard is not mounted to pc anymore
6. Open Windows Command Prompt and type the following commands.
adb shell
su
stop
mount -o remount,rw /dev/block/stl12 /system
rm /system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/stl12 /system
sync
reboot recovery
Click to expand...
Click to collapse
7. Now data and cache reset in the recovery menu...
8. reboot
If one of the commands, for example 'cp' is not found, try putting busybox in front of the command:
eg: busybox cp /sdcard/done_frame/* /system/framework/
How to odex again
This may put you in the right direction. You may need to edit some steps.
http://forum.xda-developers.com/showthread.php?t=1124034
If you like my work please donate
Paypal:
Bankaccount: in private message
Updated my tutorial. Now everything works.
What does this do to my gio?
// Thanks from the noob
why the hassle? just let xultimate do it all automatic -> select option #15 then "do it all"
yep
Thanks.. ;-)
Would it work with others samsung devices?
Gonna try with 5510
Sent from my GT-I9100 using Tapatalk
dann3_86 said:
What does this do to my gio?
// Thanks from the noob
Click to expand...
Click to collapse
I am curious to
I suggest you google deodexing and zipaligning.
Deodexing in short means that it will allow you to have custom themes.
Zipaligning improves performance of the apk/jar files when reading
There is a lot of information you might want to look up!
I just added r33p's suggestion. Thanks!
Dhuu, just google it.............
I did, but it gives no answers.
I thought it was about the holy grail, or the fountain of youth..............
But no..........
But comes close
So tell me, does it works on the fly or must you reboot to aply changes?
I tiedy this metod and it works. Tank you
I'm having a problem..
I'm on xUltimate, I go to the advanced menu (15) and I type 1 (Do everything) and then it says that I don't have files in done_app folder.
Please help
Edit: I have rooted my phone, it's on Gingerbread.xxkpo. Do I have to Un-Root my phone and then do this ? Also can I root it back when the ROM is on ?
Please reply fast :S
I'm having this issue,,, what does it mean? i pulled out all the files with the automatic process and went fine. But then in the deoxed process:
How can i solve it? Thanks :3
Hi guys,
i got one question to ask - how to deodex my phone?
I used xUltimate and deodexed the apps but the commands to coppy it to the phone seems not to work at all.
So how to copy done_app and done_framework to phone? I tried to use cmd in windows and adb shell but it says that cd command is not valid.
cube7 said:
Hi guys,
i got one question to ask - how to deodex my phone?
I used xUltimate and deodexed the apps but the commands to coppy it to the phone seems not to work at all.
So how to copy done_app and done_framework to phone? I tried to use cmd in windows and adb shell but it says that cd command is not valid.
Click to expand...
Click to collapse
FOLLOW THIS:
http://forum.xda-developers.com/showthread.php?t=1068027
Deodex
Advantages or disadvantages
- Odexed ROMs are slightly faster, deodexed ROMs are slightly slower
+ You can make custom themes for your ROM
+ Performance los is negligible.
Requirements:
Download XUltimate
Busybox installed
Root
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. On the main menu of xUltimate, choose option 5 (Pull and deodex all). Everything will be done for you here. Don't worry. You will see all your finished files in the folders 'done_app' and 'done_frame' which are located in the installation directory of xUltimate.
4. move folders 'done_app' and 'done_frame' folders to your sdcard, you can find these folders in the directory of xUltimate as described in the previous step.
5. Make sure the sdcard is not mounted to pc anymore
6. Open Windows Command Prompt and type the following commands.
adb shell
su
stop
mount -o remount,rw /dev/block/stl12 /system
rm /system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/stl12 /system
sync
reboot recovery
7. Now data and cache reset in the recovery menu...
8. reboot
If one of the commands, for example 'cp' is not found, try putting busybox in front of the command:
eg: busybox cp /sdcard/done_frame/* /system/framework/
both ways don't work. The program seems not to recognize this commands. Can i do it via root explorer?
cube7 said:
both ways don't work. The program seems not to recognize this commands. Can i do it via root explorer?
Click to expand...
Click to collapse
Explain me the exact scenario.
This given method should work by all means. There is no escape.
Check the USB drivers.
Check the connectivity.
Then do it again.
drivers must be right 2 days ago i've flashed the phone. maybe it's adb, i copied it from one click folder.
i will copy the text from cmd as soon as i will be home.
btw, the process is ok till 6th point of the instruction. then it fails at cp command (busybox cp also).
cube7 said:
drivers must be right 2 days ago i've flashed the phone. maybe it's adb, i copied it from one click folder.
i will copy the text from cmd as soon as i will be home.
btw, the process is ok till 6th point of the instruction. then it fails at cp command (busybox cp also).
Click to expand...
Click to collapse
Try booting linux on ur pc as sometimes adb doesnt work for me on windows but for linux users it worked perfectly
Sent from my GT-i5801 using XDA App
alt link: http://forums.androidcentral.com/sa...-guide-stock-2-3-6-replenish.html#post1651482
REVISED TUTORIAL IN ROOTING 2.3.6 SAMSUNG REPLENISH
warning for experienced adb users!: this was made with noobs in mind. you may learn something (from me! a noob! XD) but anyways, enjoy!
this does not affect anything on the phone except for adding the ability to access root permissions. CWM is not permanent, it disappears after you use it, and nothing on the phone is affected, as far as i know, but i had just factory reset the phone, so use at your own risk...
you may need to know:
root of a drive- drives are designated C:\ or D:\ or whatever letter in windows. Just go to "computer" and double click the first item. That location is the "root" of a drive.
Note: make sure you have at least 400 mb of memory (i know, thats alot, but just in case) on your sd card so you can back up your entire phone! i reccomend doing every optional step!!! It'll save you hassle if you have problems. If you can't make room for some reason, and you still wanna try, you should skip step 8. I don't suggest it though.
1. download "odin.zip" and "su" here: https://www.box.com/shared/620b03e95cc0814fefc8 and unzip to your desktop. if you dont have the android sdk, simply copy the "adb.exe" file from "odin.zip" to the root of your primary drive for later. Just go to "computer" and double click the top icon/item. It should say something about C:/. If you're on Mac, sorry. Idk much about it. As for Linux, I have no clue how you'd even try to do this. I love Linux but, sadly, can't experiment with this in it. WINE has its limits....... And I don't think adb or Odin would work.
2. download the "su" file and put into into "platform-tools" where you installed the android sdk, if you have it, or put onto the root of your primary drive if you havent.
3. start phone while holding "spacebar" and "p". "downloading..." should appear on the screen in yellow text
4. plug into the computer and run "Odin_Multi_Downloader_v4.42.exe"
5. select SPHM580.ops for "OPS" and Replenish-CWM5.tar for "One Package" (they should be the only options) DO NOT CHANGE ANYTHING ELSE!!!!!
6. hit "Start" and DO NOT REMOVE PHONE FROM USB.
7. as the phone reboots, hold "u" until CWM opens and set the phone down. you should close Odin now.
8. use the volume keys to navigate to the backup and restore option and use enter to select backup. wait for it to finish completely and take you back to the the CWM main UI. backing up here creates a pure recovery, untouched by anything. CWM is NOT installed into this recovery. continue with the guide.
9. open the command prompt (type cmd.exe in search or run in the start menu, depending on your version of windows) or use some form of terminal emulator on your operating system of choice. command prompt is preferred due to the fact i know it can get the job done, but do what you will.
10. navigate to the drive your sdk is on and into "platform-tools" or to the folder you put the adb.exe and su files on. the default should be [name of drive]:\Users\[username]\. use the "cd.." command til youre at the root of the drive, and if you installed the sdk, type "cd android-sdk-windows/platform-tools" or just go to the root of the drive and go to the next step if you havent. just be sure adb.exe and su are there.
11. type this in line for line, with enters in between. the blue "~#" in the later lines is the prompt you should have. do not type this. it will be in blue. (clockworkmod should still be open on your phone at this point)
adb shell
~#mount -o remount,rw -t rfs /dev/block/stl12 /system
~#exit
adb push su /system/bin/
adb shell
~#chmod 777 /system/bin/su
~#reboot
DO NOT CLOSE THE COMMAND PROMPT YET FOR THE SAKE OF CONVENIENCE
If you have problems with that, try using CWM to mount "/system". Some friendly people over at androidcentral pointed that out. I personally didn't have that problem, but I'm glad it's fixed.
12. when your phone has rebooted, go back to the open command prompt, which should be where it was before you typed "adb shell"
13. type "adb shell". you will see a prompt of "$." type "su." if you have a prompt of "#" rejoice! you have permanent root! now you can go on the Play Store and find "Superuser" and "Busybox" (they should be free. if you cant find it, get ahold of me and ill try to supply the newest updates) if not, and you have a backup from optional step 2, you should go through til you hit CWM and restore the backup. if not, make one now and reattempt everything aside from downloads and the moving the files around on your computer. Also, someone said something about "chmod 06755 /system/bin/su", so if you might try using that instead of "chmod 777 /system/bin/su". 777 worked for me, but maybe this works better for you.
OPTIONAL FINISH STEP: I dont know how you install CWM permanently, but you should do this so you can make backups of your rom and store them somewhere like on a box.com or mediafire.com account if you decide to mess with something on your phone. (use hjsplit to break it into pieces for uploading and reassemble after download for flashing if its too big). to use a recovery, enter CWM (either the way i have here or if you have permanently installed, just reboot and hold "u") and navigate to "backup and restore," "restore," and select the recovery you wish to use on your sd card (make sure when you take out a backup for storage, you zip up the entire folder with the name that contains the date and time of your backup.) it will overwrite everything on your phone to be exactly like it was when you backed it up.
good luck! have fun!
Note: if you rename the CWM backup file, make sure it DOESN'T HAVE A SPACE or it'll give you something about md5 or something not matching. If it says this, remove any spaces in the name and try again. I had it happen on my xperia play and freaked, thinking it was soft-bricked permanently one time, til I found out about cwm's glitch with that.
Also, I uploaded pretty much everything needed for rooting the phone, with comments pertaining to each file. This includes current (as of July 31, 2012) copies of Superuser.apk, a busybox installer, and the busybox and su binaries, as well the Odin package containing the tools to temp flash CWM.
the odin.zip file and the process of achieving CWM temp-flashing was found at http://forums.androidcentral.com/sa...method-samsung-replenish-android-2-3-6-a.html and credit for that part is given to joshua.worth, although I took it a different path than he did.
Update to above info: to simplify things, I uploaded all relevant files to box so people can get them easier. The su file went missing from xda, most importantly, so I fixed that, and added an updated binary in case someone has trouble with the other one.
contact me at [email protected] if you cant pm me.
Sorry if it takes a while to respond. Life's been kinda crazy for me lately, and I am using my new phone (no service) to do this over wifi.
ahh... well, turns out unrooting cannot be done with a CWM backup... you probably have to find a nandroid or a clean version of kernel with rom. the su file dissapears, although root is still there. ill keep playing with it, i have an idea why root stays although su disappears from the system files. anyways, i will still supply a backup thats pre-rooted for anyone who is willing to have a fresh start on their replenish. it will have superuser.apk preinstalled along with busybox, and everything else will be wiped. this will be a sprint backup, so if anyone has the boost version and is willing to back up with CWM and factory reset, then follow my guide, install busybox and superuser.apk, then back it up again, id be eternally grateful to have a copy
by the way, if anyone has problems with restoring a backup due to "md5" tags or whatever it is, make sure the name of the backup has no spaces. i was freaking out til i found that tip on an obscure forum (well, to me. i dont have a Motorola. lol. just a Sony Ericsson and 2 Samsungs)
update: sorry i havent uploaded the backup. i realized it would give whoever used it the number on this phone and i have to fix that. havent had time to anyways, plus it would only work on a sprint phone. it would convert any boost mobile to sprint, so thats a no-go. sorry...
does this work for the boost mobile replenish that is 2.3.6 if so how long does it take to odin
It should work. And Odin just flashes cwm (really fast) for the duration of the next boot cycle, which it automatically initiates, so hold the recovery button (I think it's u) as it goes into it and you'll have temp root. Make sure it's in download mode before you start. Remember, it cannot be unrooted, so if you value your warranty, plz think twice before doing it. I'm just here to supply the how-to if you decide to, not to say you have to. If you do, enjoy root access!
isavegas said:
It should work. And Odin just flashes cwm (really fast) for the duration of the next boot cycle, which it automatically initiates, so hold up (I think it's u) as it goes into it and you'll have temp root. Make sure it's in download mode before you start. Remember, it cannot be unrooted, so if you value your warranty, plz think twice before doing it. I'm just here to supply the how-to if you decide to, not to say you have to. If you do, enjoy root access!
Click to expand...
Click to collapse
Thanks. I did not know if there is a fail safe if something went wrong. so I was second guessing. Very simple to do thank you assuming with odin I made a back up. if I where to mess my system up I can use odin and restore my backup and I be back up and running again no need to sbf
i keep getting : ~ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
bscabl said:
i keep getting : ~ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
Click to expand...
Click to collapse
hmm... i am familiar with the error (ive gotten it with 3 different phones in my attempt to root it, but i have succeeded each time regardless) but are you sure you actually have clockworkmod OPEN on your phone when the error shows up? i cant actually do anything from my end, because i no longer have a computer i can use to test anything, or the replenish i rooted with the method... but i opened the cwm several times before thinking to test the adb and seeing the "~#". i actually restarted the phone and did it again before actually rooting it, seeing if i had rooted it or what, and tho i got the same prompt every time it was booted in cwm, it wouldnt show up if i allowed the phone to boot normally after using odin, i HAD to ACTUALLY boot into the cwm menu, which is completely seperate from the OS itself, although it has access to the system files.
by the way, copy and paste this directly into the command prompt when you get to the step to avoid human error. mount -t rfs -o remount,rw /dev/block/stl9 /system
or, if it wont work, try this mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
sorry bout the babbling XD. anyways, cwm should be circumnavigating the root permissions. hmm.... if you still have problems after that, try skipping to the adb push for the "su" file.
sorry i havent been on top of the thread. ill set up an email notification.
and by the way, something i found very useful on my xperia play when it went into infinite reboot, you can always just restore the system files in the advanced restore option, allowing you to keep all of your app data if, later down the line, your phone needs to be restored. hope this helps. it helped me XD thought id lose all of my messages, but nope. i decided to explore the advanced restore and yay! i got to keep them XD
UPDATE
I don't know if it matters to you anymore, but apparently, some people have trouble with this and fix it by going to the mount menu in CWM and mounting /system
Couple of corrections:
chmod 777 /system/bin/su
should be chmod 06755 /system/bin/su
and then following that command should be
ln -s /system/bin/su /system/xbin/su
and I saw someone say this is unrootable. Thats not correct. Simply running the unroot script would unroot. Doomlord made a nice one.
To use it do the following:
Code:
adb push unroot /data/local/
adb shell chmod 777 /data/local/unroot
adb shell su -c "/data/local/unroot"
adb reboot
[code]
The above will unroot almost any android device.
halfcab123 said:
Couple of corrections:
chmod 777 /system/bin/su
should be chmod 06755 /system/bin/su
and then following that command should be
ln -s /system/bin/su /system/xbin/su
and I saw someone say this is unrootable. Thats not correct. Simply running the unroot script would unroot. Doomlord made a nice one.
To use it do the following:
Code:
adb push unroot /data/local/
adb shell chmod 777 /data/local/unroot
adb shell su -c "/data/local/unroot"
adb reboot
[code]
The above will unroot almost any android device.[/QUOTE]
Unfortunately, Doomlord's method didn't work on it. I tried all manner of one clicks and manual versions and only this got even temporary root. It's a workaround based on forcing the phone to boot into a custom recovery. (I call it custom bc its not an "official" recovery.) And I chose the chmod by looking through many manual ways to root, and that one was popular, and it works. I had full root access afterwards. I tried to unroot afterwards, however, so I could take screenshots and stuff, but the su file would reappear, even after manual deletion or restoring to an unrooted backup. Anyways, point is, this is the only method I could get to work at all, and it does work.
But the "chmod" night help other people, so ill make note of it in the post just in case. Thanks for the info.
Sent from my rooted R800at using xda app-developers app
Click to expand...
Click to collapse
Important fix----
If step 11 doesn't work, go to the "mount" menu in cwm and mount /system. Some people on androidcentral were kind enough to mention that this fixed their problem with mounting /system as rewritable
Sent from my R800at using xda app-developers app
isavegas said:
Important fix----
If step 11 doesn't work, go to the "mount" menu in cwm and mount /system. Some people on androidcentral were kind enough to mention that this fixed their problem with mounting /system as rewritable
Sent from my R800at using xda app-developers app
Click to expand...
Click to collapse
thats because your command is wrong
shabbypenguin said:
thats because your command is wrong
Click to expand...
Click to collapse
How? Throughout my own rooting of one of the phones, I had this working perfectly. Every time I hit a snag, I found a way around it and documented it. A few other people had errors show up because the phone itself hadn't mounted the system, but the problem was resolved, and only a couple people had any other problems, and they were unrelated to that. I assure you, every command works properly, as far as I know.
exactly my point. your command to mount system is wrong.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
lets break it down shall we?
mount - this is teh command
-o remount,rw - this is where you tell it what option you want, in this case remounting as rw.
-t yaffs2 - here you are telling mount that it should expect a yaffs2 formatted device, which is not what the samsung replenish is. the replenish uses RFS (robust file system), the best way i can describe it is like telling your windows computer that your hard drive is fat32 when its actually ntfs.
/dev/block/mtdblock3 - this is where you tell mount what you are looking to mount, the issue here is that the replenish doesnt use MTD blocks, it uses STL's and BML's.
/system here is where you are trying to mount the said device to..
out of 5 parts you did get 3 correct tho. you might wish to modify your guide to reflect the actual mount command, for your device it is the following:
mount -o remount,rw -t rfs /dev/block/stl12 /system
and that will kick out system as r/w
shabbypenguin said:
exactly my point. your command to mount system is wrong.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
lets break it down shall we?
mount - this is teh command
-o remount,rw - this is where you tell it what option you want, in this case remounting as rw.
-t yaffs2 - here you are telling mount that it should expect a yaffs2 formatted device, which is not what the samsung replenish is. the replenish uses RFS (robust file system), the best way i can describe it is like telling your windows computer that your hard drive is fat32 when its actually ntfs.
/dev/block/mtdblock3 - this is where you tell mount what you are looking to mount, the issue here is that the replenish doesnt use MTD blocks, it uses STL's and BML's.
/system here is where you are trying to mount the said device to..
out of 5 parts you did get 3 correct tho. you might wish to modify your guide to reflect the actual mount command, for your device it is the following:
mount -o remount,rw -t rfs /dev/block/stl12 /system
and that will kick out system as r/w
Click to expand...
Click to collapse
Hmmmm.... Odd..... *shrugs* I had no problem with the command, but I guess other ppl had pickier computers or phones. Hell, Vista's buginess might have worked in my favor that time XD. Thanks for the pointer. I didn't really understand the exact way the replenish was built. I just found a lil guide for making it boot into cwm and found it allowed for me to use that as an exploit to root the device. In fact, I've done the same kind of stuff to root the samsung Intercept, except I made their own software flash a pre-rooted kernel. anyways, I'll update the guide on xda and androidcentral. Thanks!
isavegas said:
Hmmmm.... Odd..... *shrugs* I had no problem with the command, but I guess other ppl had pickier computers or phones. Hell, Vista's buginess might have worked in my favor that time XD. Thanks for the pointer. I didn't really understand the exact way the replenish was built. I just found a lil guide for making it boot into cwm and found it allowed for me to use that as an exploit to root the device. In fact, I've done the same kind of stuff to root the samsung Intercept, except I made their own software flash a pre-rooted kernel. anyways, I'll update the guide on xda and androidcentral. Thanks!
Click to expand...
Click to collapse
chances are you had system mounted in cwm without knowing it.
for future knowledge always check the devices fstab for where to mount and filesystem type
https://github.com/Shabbypenguin/android_device_replenish/blob/master/recovery/recovery.fstab
as you can see the proper mounts from the files i used to make CWM for the replenish
shabbypenguin said:
chances are you had system mounted in cwm without knowing it.
for future knowledge always check the devices fstab for where to mount and filesystem type
https://github.com/Shabbypenguin/android_device_replenish/blob/master/recovery/recovery.fstab
as you can see from the files i used to make CWM for the replenish the proper mounts
Click to expand...
Click to collapse
Eh, maybe. For all I know the first thing I did was mount everything with cwm. I DID do this several months ago. I don't even have the phone anymore. The owner of the phone was gonna give it to me after upgrading, but she sold it, so I kept her 500gb laptop hard drive instead. Popped it out of the external hdd casing and stuck it in a laptop. XD. It now has Linux on it.
Anyways, I've updated the guide to have the right command and note that if it doesn't work to use cwm to mount /system. And how do you find the fstab? Just Google it? Or is it somewhere on the device?
Btw, do you know anything about cwm? It refuses to properly back up my xperia play anymore. The .android_secure folder keeps giving it errors.
isavegas said:
Eh, maybe. For all I know the first thing I did was mount everything with cwm. I DID do this several months ago. I don't even have the phone anymore. The owner of the phone was gonna give it to me after upgrading, but she sold it, so I kept her 500gb laptop hard drive instead. Popped it out of the external hdd casing and stuck it in a laptop. XD. It now has Linux on it.
Anyways, I've updated the guide to have the right command and note that if it doesn't work to use cwm to mount /system. And how do you find the fstab? Just Google it? Or is it somewhere on the device?
Btw, do you know anything about cwm? It refuses to properly back up my xperia play anymore. The .android_secure folder keeps giving it errors.
Click to expand...
Click to collapse
its where the recovery is on the device. each device has their own fstab. as for your error sounds like a conflict, either with cwm itself or that folder
shabbypenguin said:
its where the recovery is on the device. each device has their own fstab. as for your error sounds like a conflict, either with cwm itself or that folder
Click to expand...
Click to collapse
It HAS to he cwm, because the folder is regarded as super hidden by the device. The folder itself can be seen, but the contents can ONLY be edited by the rom or a pc, and I haven't touched it with a pc before. It's where your apps go when you move them to the sd card. I've been trying to back my phone up with cwm because I wanted to test the jelly bean alpha release for it. its the xperia play 4g. Stupid backup crashes every time I try and it ends up eating up what room is left in my sdcard.
i followed your guide and have root in shell. however i cant get root permission on any apps, the window doesnt pop up asking me for permission. i also get a toast notification saying superuser access denied for whatever app im trying to open. any ideas?
arodey said:
i followed your guide and have root in shell. however i cant get root permission on any apps, the window doesnt pop up asking me for permission. i also get a toast notification saying superuser access denied for whatever app im trying to open. any ideas?
Click to expand...
Click to collapse
What does your Superuser log show?
Sent from my PC36100
FINALLY MY WIFI CAME BACK !!!
SO I THINK U SHOULD DEODEX UR ROM FOR MORE SPACE AND FLUIDITY
{I COULD NOT CREATE BATCH FILE AS OUR BOOT IMAGE DOES NOT SUPPORT TRUE ADB ROOT AS ITS DEV EDITION}(ANY IDEAS FROM DEVS IS WELCOME)
AGAIN SAYING NOT FOR ATT
OKAY FIRST THANX TO dsixda/Android-Kitchen FOR HELPING TO DEODEX THE ROM
NOW STEPS ::::::
-1.install a third party launcher (like apex for safety purpose)
0.MAKE A BACKUP OF UR SYSTEM (I HOPE U R USING BMM !!!)
1.DOWNLOAD THE APP AND FRAMEWORK FOLDER FROM LINK GIVEN BELOW
2.PUT BOTH THE FOLDERS ON SDCARD AS WELL AS INTERNAL MEMORY (DONNO WHICH IS USED !!)
3.OPEN THE """4.0.4ROOT BY CRC""" FOLDER U DOWNLOADED WHILE ROOTING OR ANY FOLDER WHICH CONTAINS ADB
3.5}NOW HOLDING SHIFT CLICK OPEN COMMAND WINDOW HERE
4.NOW CONNECT PHONE IN MTP MODE WITH DEBUGGING ON
5.TYPE THE FOLLOWING CODE AND U R DONE (WELL IT WILL SLIGHTLY MAKE U FEEL LIKE A TEMPORARY DEV HAAHAH)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodexedapp/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodexedframe/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
note ::
1.its o not zero
2.when u enter su the $ sign will change to # it means u gained root access
3.i dont remember but after pressing su look at ur phone if supersu notification for root access comes allow it if it is there
4.i am not sure or the stock launcher it may fc so firs install a third party launcher for safety purpose
*links ::::
apps::
https://app.sugarsync.com/iris/wf/D8443834_63525726_687588
framework::::
https://www.sugarsync.com/pf/D8443834_63525726_688199
pls hit thanx bros it motivates me !!!!!!!
make an acc on sugarsync the next famous storage systemm it will help u as well as me
What is MTP mode?
brianmoyano said:
What is MTP mode?
Click to expand...
Click to collapse
When ya connect the phone to PC, it will show 3 different modes. Like USB mass storage and stuff. One of em is MTP. pull down the notification bar, you will get those options (when connected of course)
Sent from my muffin LIFE! Under maintenance.!
Good. Thanks for sharing this!
I already Deodexed and zipaligined my rom using this tutorial to achieve the same.
brianmoyano said:
What is MTP mode?
Click to expand...
Click to collapse
Media Transfer Protocol. Gives you access to your SD Card and phone storage without unmounting them from phone so your SD Card is also available through phone as well as on PC. If you access any file on your phone, it will first copy it to PC and then open it which makes it slower. But its good enough for transferring pics and music and basically MEDIA TRANSFER as the name says..
answersamir said:
Code:
adb shell
su
stop
mount -o rw, remount /system/ /system/
cp /sdcard/deodexedapp/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodexedframe/* /system/framework/
rm /system/framework/*.odex
mount -o ro, remount /system/ /system/
reboot
Click to expand...
Click to collapse
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
shubham412302 said:
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
Click to expand...
Click to collapse
On extremely close observations I found out that both are same :sly:
Buddy order doesn't matter
Sent from my ME865 using xda app-developers app
can you upload an alternate link for 'apps' ...download is not completing...it is stopping after 140mb....
poorna said:
can you upload an alternate link for 'apps' ...download is not completing...it is stopping after 140mb....
Click to expand...
Click to collapse
Thats the full size of zipped apps...
But it has all apps
Sent from my jb atrix 2
shubham412302 said:
Thats the full size of zipped apps...
But it has all apps
Sent from my jb atrix 2
Click to expand...
Click to collapse
when i try to extract it ,i get a message invalid file ...the actual size is 185mb ...twice i downloaded. in the 1st attempt i was able to download 146mb...in the 2nd attempt i was able to download 140mb....
poorna said:
when i try to extract it ,i get a message invalid file ...the actual size is 185mb ...twice i downloaded. in the 1st attempt i was able to download 146mb...in the 2nd attempt i was able to download 140mb....
Click to expand...
Click to collapse
Match this with your d/l file.
146 MB (153,457,466 bytes)
CRC: 7FC9D73F
shubham412302 said:
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
Click to expand...
Click to collapse
the phone is not booting... after i type stop and press enter ,the screen turns off,then when i type mount -o rw,remount /system/ /system/ and press enter i get the same line and then i get the # symbol again..then when type rm /system/app/*.odex and press enter i get the same line and then i get the # symbol again ,same thing for the next rm line...but when i type cp /sdcard/deodexedapp/* /system/app/ and press enter i get the same line again and there is no # symbol,the same thing happens to the following lines ....when i typed reboot and press enter the same line(reboot) appears and the phone is not rebooting...i removed the battery and tried to boot the phone is not booting...i downloaded both the links (apps and framework) and extracted them and copied both(deodexedapp and deodexedframe) to internal phone storage and sd card ....what might be the problem here?
poorna said:
the phone is not booting... after i type stop and press enter ,the screen turns off,then when i type mount -o rw,remount /system/ /system/ and press enter i get the same line and then i get the # symbol again..then when type rm /system/app/*.odex and press enter i get the same line and then i get the # symbol again ,same thing for the next rm line...but when i type cp /sdcard/deodexedapp/* /system/app/ and press enter i get the same line again and there is no # symbol,the same thing happens to the following lines ....when i typed reboot and press enter the same line(reboot) appears and the phone is not rebooting...i removed the battery and tried to boot the phone is not booting...i downloaded both the links (apps and framework) and extracted them and copied both(deodexedapp and deodexedframe) to internal phone storage and sd card ....what might be the problem here?
Click to expand...
Click to collapse
Wait for a while....
Until you get the [email protected] again you must not do any thing because the previous step is not done.....
Be patient.
The step copy system apps take 5 minutes...
And there is a space here before remount
mount -o rw, remount /system/ /system/
Sent from my jb atrix 2
What are the advantages of deodexing the stock rom?
I came across this thread and it gave me curiosity to find-out the stuff which I wanted to read for long time. Odex and deodex..
The only advantage I came across of deodexing was posibility of theme modifications.
Some thread on XDA and google said that with odex rom (1) boot will be faster.
With deodexing, they said (1) it will take up more data space (2) theoritically deodexing will slow some performance and (3) longer boot times because of big dalvik cache...
Please can you tell me exactly where I am wrong?
Sent from my jb atrix 2
Download unsuccessful
Download is not starting...it says it has started but nothing is getting downloaded have tried a lot.... any alternate link pls:silly:
hello , it´s only for jelly bean?