--THIS IS FOR THE VERIZON DROID RAZR--
Go here for the test files for international version: http://forum.xda-developers.com/showpost.php?p=19900530&postcount=11
I have enough confirmations that I can now confirm this is working, However the on screen controls appear not to be launching currently, but webtop launches.
What this mod does:
It removes the device ID string check from PortalApp, and enables the webtop option in DockService. Replacing these two apk files effectively allows the webtop to launch without proprietary hardware.
Click to expand...
Click to collapse
What this means to you:
Webtop mode over any HDMI without an expensive dock.
Click to expand...
Click to collapse
Installation:
Method 1: Flashable ZIP
Flash THIS zip.
Click to expand...
Click to collapse
Method 2: ADB install
Download the attached apk files.
First Get the files to the device and remount /system as rw:
Code:
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o remount,rw /system
Backup the original files:
Code:
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
cp /system/app/DockService.apk /system/app/DockService.apk.bak
cp /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
Copy the modded files over fix permissions and reboot:
Code:
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
chmod 644 /system/app/DockService.apk
chmod 644 /system/app/PortalApp.apk
reboot
Click to expand...
Click to collapse
Appreciate my work? Buy Me a Beer:
You are awesome!! Thank You. As soon as I find a spare HDMI port on my TV I'm installing this.
Edit: Is there a way to revert back to stock without doing a ND restore. Only for warranty purposes of course, can't imagine anyone would even know though. <<Ignore that.
love you.
10<3
ah jeeze... just noticed it's for the Verizon RAZR, will it by any chance work on a GSM version?
Just installed it, and on the bionic after connecting to the tv, the phone became a mouse. Here the screen goes black and doesn't respond to touch.
You on a Verizon device? Did the webtop or dock option list come up at all?
Yes, Verizon phone. Everything comes up great on the tv, The webtop option comes up on the list to choise from, when i hit webtop the tv comes on, the phone goes black, but no control of pointer at all.
That's a good sign at least. Did you install via the flash method or the adb method?
Flash. I flashed BigDX ics theme yesterday, maybe it has something to do with it, so restoring a nandroid backup of before and will flash the webtop hack again.
---------- Post added at 10:41 PM ---------- Previous post was at 10:12 PM ----------
Nope. Same. Phone screen goes black, no control of pointer.
That sucks stevessvt, maybe try installing via adb instead and see what happens.
I really want to try it on my GSM RAZR... Don't know what the difference would be. Anyone...?
EDIT:
My stock DockService.apk is 109kb - odex is 173kb, the PortalApp.apk is 1.21mb - odex is 591kb
Can anyone confirm the Verizon file sizes for me?
opensourcefan said:
You are awesome!! Thank You. As soon as I find a spare HDMI port on my TV I'm installing this.
Edit: Is there a way to revert back to stock without doing a ND restore. Only for warranty purposes of course, can't imagine anyone would even know though. <<Ignore that.
Click to expand...
Click to collapse
Try this one with method 2 for the international version: http://www.cheatersedge.org/android/RazrWebtopMod.rar
I'll try to look into the on screen mouse/keyboard issue. It may be slow going seeing as I don't actually have one of these devices to test on.
Sent from my SGH-I777 using XDA App
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
oh now i just got mad since the OTA i lost root so no Webtop for me. i don't wanna loose the OTA so i'm just gonna wait for somebody to find a way to get root again.. since i don't know how to do that.
opensourcefan said:
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
Click to expand...
Click to collapse
You can change the permissions with Root Explorer: Long hold on each file, and set RW- R-- R--, and then reboot, that ought to go it.
As for the command for the adb method it might be "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" Where "/dev/block/mtdblock3" is replaced with the actual block device for /system. You can check this by just typing "mount" and looking at the entry for /system.
only Verizon? not for EU GSM devices?
Doesn't work on mine. As faras I know there are different version for gsm that could be the problem
Sent from my Razr XT910 using xda premium
shady_lanem said:
Doesn't work on mine. As faras I know there are different version for gsm that could be the problem
Sent from my Razr XT910 using xda premium
Click to expand...
Click to collapse
you have a Vaarizon?
9100_it said:
you have a Vaarizon?
Click to expand...
Click to collapse
Download link for international version is posted on top of this page
opensourcefan said:
Sadly everything I try it behaves as if I don't have root. I can get # in ADB just won't let me do anything in /system/app, says read only file system.
I tried to just rename and replace in root explorer but get a repeating force close on the Portalapp service.
I need a different way to mount read/write
Code:
mount -o remount,rw -t yaffs2 /system
or
adb shell sysrw
idunno, not a ADB fan.
Click to expand...
Click to collapse
You have to do
su
To login as root before.
Sent from my awsome Motorola RAZR
Perfect!
I've asked to teach me how to make it, but it's the same. The important thing is that it is available, even if my curiosity reaches an unknown level.
Thanks!
P.S.: Please, edit the thread title to reflect this section rules!
Related
Theres a new version of the Swype beta that is IMMENSELY better than the preloaded swype that comes with the atrix, it literally fixes all the annoying things of the older Swype versions:
http://beta.swype.com/
Swype 3.x beta works with the method below!
Process:
1) Use Root Explorer/Terminal/ADB to backup and then delete Swype.apk from /system/app and libSwypecore.so from /System/lib
2) Download the installer from https://beta.swype.com/android/get/ (on your phone)
3) Use installer to login and install latest version of swype
After your first phone reboot, if you are experiencing Swype Force closes after installing the latest swype, uninstall swype from your phone and then reinstall it; it should no longer force close after reboot.
If you are still experiencing force crashing after reinstall, try wiping your dalvik cache within CWM. Thanks Dudeman Broguy.
If you want to get in the latest beta, sign up over here. Registrations are open right now, hurry before they close them again!
Thanks to playin4sheezy for figuring this out: post #12
yes, i have been using it all day and it looks and feels great! if you have sideloading enabled, when you start the install it will ask to over write the current one.
graemegb said:
yes, i have been using it all day and it looks and feels great! if you have sideloading enabled, when you start the install it will ask to over write the current one.
Click to expand...
Click to collapse
Im trying to use the installer and it tells me to disable swype, and you cant disable the built in one. Can you pm me the apk?
Yea, I get to the point where it says "Licensing Swype, please wait...." and it doesn't get past that.
You need to go into /system/app and move Swype.apk to a backup folder on /mnt/sdcard
Then go into /system/lib and do the same for libSwypeCore.so
Give it a reboot and then try to install the beta. It worked for me
How did you move the apk, it wont allow me to do so
playin4sheezy said:
You need to go into /system/app and move Swype.apk to a backup folder on /mnt/sdcard
Then go into /system/lib and do the same for libSwypeCore.so
Give it a reboot and then try to install the beta. It worked for me
Click to expand...
Click to collapse
woo nice! thanks that worked for me! no more stupid tip window!
Krshaw18 said:
How did you move the apk, it wont allow me to do so
Click to expand...
Click to collapse
you have to use root explorer (and be rooted) or you could use terminal/adb (still have to be rooted)
Sorry for the noob questions! Move it completely? or make a back up of it? and also any apps out there like root explorer but free ?
I tried the above steps but the libswypecore is still in the system folder when i move it as it is read only...
Krshaw18 said:
Sorry for the noob questions! Move it completely? or make a back up of it? and also any apps out there like root explorer but free ?
Click to expand...
Click to collapse
If youre rooted, root explorer is worth the money. You have to move Swype.apk completely, and make sure its not there after moving or the install wont work.
Make sure if you are in Root Explorer that you click the R/W button at the top to make the system folder Read/Write access. Then long press the files and click move and goto sdcard and make a folder named "whatever you want" then click paste..
Or you could do this using adb with Atrix plugged into the computer:
goto command prompt
type the following:
adb shell
su
mkdir /mnt/sdcard/swype_backup
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /system/app/Swype.apk /mnt/sdcard/swype_backup
cp /system/lib/libSwypeCore.so /mnt/sdcard/swype_backup
rm /system/app/Swype.apk
rm /system/lib/libSwypeCore.so
Hopefully this gets you going
playin4sheezy said:
Make sure if you are in Root Explorer that you click the R/W button at the top to make the system folder Read/Write access. Then long press the files and click move and goto sdcard and make a folder named "whatever you want" then click paste..
Or you could do this using adb with Atrix plugged into the computer:
goto command prompt
type the following:
adb shell
su
mkdir /mnt/sdcard/swype_backup
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /system/app/Swype.apk /mnt/sdcard/swype_backup
cp /system/lib/libSwypeCore.so /mnt/sdcard/swype_backup
rm /system/app/Swype.apk
rm /system/lib/libSwypeCore.so
Hopefully this gets you going
Click to expand...
Click to collapse
Thanks a bunch!
Wont let me delete
Sent from my Atrix 4G using XDA App
joshuajoshua said:
Wont let me delete
Sent from my Atrix 4G using XDA App
Click to expand...
Click to collapse
Is your phone rooted? If so, then when you typed su in adb shell(not terminal) did it ask you for superuser permission? If so, then you should make sure and accept it.
If your phone is not rooted, then I don't think your gonna get this working
Sent from my MB860 using XDA App
I didnt need to move/delete libSwypeCore.so and the install worked fine.
andy2na said:
I didnt need to move/delete libSwypeCore.so and the install worked fine.
Click to expand...
Click to collapse
Ok. Be aware that I've had previous issues with swype after few days of use because I didn't remove that file
Sent from my MB860 using XDA App
I would suggest someone testing that you can in fact put it back to the stock setup. Mine somehow got deleted when i first got the phone, and it doesn't come back, factory reset or otherwise.
cegna09 said:
I would suggest someone testing that you can in fact put it back to the stock setup. Mine somehow got deleted when i first got the phone, and it doesn't come back, factory reset or otherwise.
Click to expand...
Click to collapse
i have been messing with swype for the last few days
i can guarentte you that if u installed / mounted a messed up version of swype (WVGA with a language pack in my case), you can just use put the backup stock swype back on /system/app and it'll be fine again
i get an error on sign-in into the installer, says device id dont match. any ideas?
EDIT: I had to log into mySwype and remove my old phone (nexus one) and then now it works!
Can someone knowledgeable please submit a detailed post, which instructs how to remove any files added during the Root Process, as well as any other file permission changes or modifications of any other type?
I see many half assed posts in these forums made by unqualified members, which are nothing but a waste of time and clutter this great resource. I would appreciate it if this post could be addressed by those who truly understand this process.
The file that was used to Root the SCH-i905 from Verizon was the one attached to this post.
Thanks in advance! This could be a great learning tool if answered properly.
Can some one please respond? Or is it that everyone is too scared to post helpful information?
Well, since no one was of any assistance, I was forced to piece together information and come to an understanding of how this works, and how to fully reverse what was done by this Root Update.
To begin, I would like to mention, that removing Superuser.apk from the /system/app folder, along with 'su' from the /system/bin folder, will negate your Root Access, and put you back to your default levels of access. This will prevent Mobile Device Management Solutions, such as AirWatch, Zenprise, or MobileIron from detecting your device as being compromised.
I was not successful in removing these two files via the ADB shell, however I was successful when using a Terminal Emulator App on the Device itself.
1.) I began by installing a free Terminal Emulator from the Android Market.
2.) Launched the Terminal Emulator and typed 'su' , then pressed Enter to gain Root Shell Privileges.
3.) From the Root Shell, I typed the following commands to remount the '/System' Directory to gain Read/Write Access.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
4.) I typed the following commands to remove 'Superuser.apk' and 'su'.
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
5.) Type the following command to remount the '/System' Directory back to Read Only.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
6.) Sync your device with Google under Settings / Accounts & Sync.
7.) Reboot your device, and you are good to go.
It might be a good practice to perform a Factory Reset on your device after doing this, however this is not completely necessary. I tested the Air-Watch Agent installation after performing the procedure mentioned above, and the Air-Watch console no longer detected my device as being compromised.
I will add that on my sch-i905 I found the bin directory under system not under system/app. For me, replacing cd /system/app/bin with cd /system/bin did the trick but the rest worked a treat - thanks for the post!
Thanks for pointing out my typo. I corrected the path in my Post.
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
tbcpn said:
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Stock Recovery isn't required to Root the device. However, if you wish to install CWM via ROM Manager from the Android Market, Root Permissions are required.
If you use an ODIN Flash of CWM, there is no need for Root Permissions because you are flashing via ODIN.
The stock recovery zip file that you referenced in the other post should be fine.
Just use ODIN to Flash back to Stock Recovery and use the process that I mentioned to remove Root Permissions and Super User, and you should be all set to return your device after a Factory Wipe.
Cheers!
~Scott~ said:
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Scott,
I'm sorry for just seeing your post. I'm sure that you figured it out by now. You need to gain Root Access to your device again to remove Super User. You are in a Catch22.
If you are using an SCH-I905, Root your device, then download Script Manager from the Android Market.
Run this very simple Bash Script that I wrote to remove Root and Super User.
Paste this into notepad and save it as Unroot.sh then run with Script Manager.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Be sure to run the Script as Root from within Script Manager. The app will kind of freeze up as soon as it runs, which is normal. This will certainly take care of your problem.
Thanks for your post of stockrec in a different post. You saved me a month ago with that one.
Cheers!
Will Samsung know if I rooted my GT 10.1 LTE after using these commands, and sending in for warranty?
Does anyone know how often airwatch checks for the root? anyway to bypass the checks?
Is this the same for the US Cellular 4G Tablet? I have been reading and all that I have found was WiFi only files. Which if I were to root with those I lose the 4G radio.
Perfect.. Just what I need. Thanks
It seems that nobody is talking about deodexing the Droid X2. Just thought I would let everyone know that xUltimate 2.2.8 works on the Droid X2 with the newest drivers installed. I am currently manually deodexing my root GB Droid X 2.
Some Members Might Not Wanna Take The Risk. With All The ROMs Are Already Deodexed. Me Personally I've Had That Program Downloaded Since The First Time It Was Posted And Have Used It Numerous Times. Now That You Mentioned This, You Should Go Bump That Thread.
If anyone can instruct me on how to successfully create an update zip I would gladly do it for those that don't want to take the risk of deodexing manually. But I am really shocked that a deodexed GB is not in the TBH App and no one seems to be talking about it.
I'm Gonna PM You A Few Websites To Learn How To Do It.
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
dimitri407 said:
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
You Need To Manually Transfer Them Over USB First. Both App And Frame Place Them On Your SD Card.
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
dimitri407 said:
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
Click to expand...
Click to collapse
When You Did "su", Did You Grant The Superuser Request On The Phone?
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
dimitri407 said:
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
Click to expand...
Click to collapse
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
I can't figure it out either. I did this to my Droid X with no problems. But the Droid X 2 just wants to be a pain when I am trying it.
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
I am wondering, since it is not working in adb shell then could I do it in the terminal?
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
So I finally got everything to work but to do so I had to copy the done_app and the done_frame folders to /data/local/tmp then run the cp commands.
For some reason, I could not get to the SD Card or the External SDCard.
you both need to quit hijacking threads and grow up. If I was the mod I would ban both of you.
Sent from my DROID X2 using XDA App
mistawolfe said:
Lol. You beg for 'em. Signature...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Can we please stop hijacking my thread. This is suppose to be about Deodexing the Droid X 2.
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
dimitri407 said:
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
Click to expand...
Click to collapse
Oh God Yes. It's Gonna Faster And Smoother. The Point Of Deodexing Is It Recompiles The Odex Inside The Apk For Easier Themeing And The System Is Able To Read The Apks Faster. Definitely Gonna Help Battery If The System Isn't Working As Hard.
when you connect USB, you MUST be in "charge only" mode w/ usb debugging enabled. ANY OTHER MODE will fail to allow complete access to /sdcard or /sdcard-ext...
or at least that was my experience.
I'll Challenge That I Used PC Mode To Run The Deodex App And Then To Transfer The Completed Files Without Switching Modes. Anytime I Run ADB Operations My Phone Is In PC Mode.
I will check both settings today. But by mounting the partition, it should become available either way. But we will see.
The thing wont recognize my phone and wont show the options to do xrecovery or any of the other options except for Flash...please help im desperate for a rom
You need to root first.
Here: http://forum.xda-developers.com/showthread.php?t=1196421
Then in flashtool click 'ask root permissions' and have your phone unlocked and accept superuser permissions w/the prompt on your phone. Then you're good to go.
*edit- make sure it is the fixed xrec for 2.3.3. I use a Rom w xrec included so I didn't have to install it & I dont remember if that's the one in flashtool now.
Which firmware version are you on?
I have done that already...i am rooted because I have superuser on my phone. Where do I check firmware?
Sent from my X10i using XDA App
zm4 said:
I have done that already...i am rooted because I have superuser on my phone. Where do I check firmware?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
unzip xrecovery file and copy all files manually to the right places using root explorer then check all boxes on permitions.
reboot and try
How do i do that?
zm4 said:
How do i do that?
Click to expand...
Click to collapse
a very old guide written by me HERE
read "2nd mode" but use xrecovery v3 instead the one linked there
will this work for 2.3.3?
zm4 said:
will this work for 2.3.3?
Click to expand...
Click to collapse
these commands still the same you just need to change (eventually) to the right path.
check the zip structure to see that
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/busybox of=/system/bin/busybox
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/xrecovery.tar of=/system/bin/xrecovery.tar
reboot
chargemon to \system\bin
charger to \system\bin
sh to \system\xbin
xrecovery.tar to \system\xbin
i dont see any busybox file or anything like that...please help i dun think busybox has been installed...
zm4 said:
i dont see any busybox file or anything like that...please help i dun think busybox has been installed...
Click to expand...
Click to collapse
ok...you have a reading problem kiddin´
Crowds said:
these commands still the same you just need to change (eventually) to the right path.
check the zip structure to see that
Click to expand...
Click to collapse
type this:
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/charger of=/system/bin/charger
dd if=/sdcard/sh of=/system/xbin/sh
dd if=/sdcard/xrecovery.tar of=/system/xbin/xrecovery.tar
reboot
this should do it
cheers
where do i get this adb thing?
zm4 said:
where do i get this adb thing?
Click to expand...
Click to collapse
forguet it...
copy all files to sdcard then copy/paste to the right places after that use root explorer and do this ON EVERY FILE YOU COPIED:
HTML:
- Press and hold on each file;
- Check all Permitions on the drop down menu;
- After changes were made save and exit;
- Reboot.
try enter on xrec
*Cannot open for read: No such or directory* wth?
where does meta go?
zm4 said:
where does meta go?
Click to expand...
Click to collapse
Anywhere. Just copy the files I told you to. I didn't referred anything about that, did I?
Sent from my X10 Erenz MIUI 1.9.2 using Tapatalk
Just start all over with flashtool it will work then.
Go to settings then applications, then development, check debug mode.
Start flash tool on your pc and connect the phone
IF the phone is rooted, it should be recognized by flash tool
On flash tool click ask root perm, look at your phone screen, superuser should pop up asking if to give permission, simply choose allow.
Then click recovery on flash tool and wait a sec....
should pop up asking which gingerbread version to use. choose 0.3GB, since its gb version you have.
when you're ready to use xrecovery, restart the phone
as soon as the phone comes on and the first sony ericsson name comes up, keep pressing the back button, xrecovery will come up.
i did both kernel things...but the thing is it won't recognize my device as a rooted device...i have superuser and I have used apps that require root...so i guess the problem is well idk...and thats what i need help with sorting out.
1. Install busybox from market (xrec needs busybox)
2. Give root explorer root acces and mount /system writeable (look in settings of your file explorer)
3. Copy files to right place:
chargemon to /system/bin
charger to /system/bin
sh to /system/xbin
xrecovery.tar to /system/xbin
4. Give above files the right permissions (long touch on file and choose property option):
user > read, write, execute
other > read, execute
group > read, execute
I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.