Related
For reference. http://forum.xda-developers.com/showthread.php?t=561579
Advantages:
jubeh said:
...there are two latent benefits to having odexed apps; decreased usage of dalvik-cache (thus, more space in /data) and decreased first-boot time after a wipe.
Click to expand...
Click to collapse
Disadvantages:
jubeh said:
The disadvantage of odexed apps is that, unless the classes.dex is kept inside the .jar or .apk, the app and framework are bound to each other (though an odexed framework can still be used under a full set of non-odexed apks, but not the other way around). This removes mix-and match, and it was the reason why I was waiting for a more current hero-dump that didn't have all it's apps and frameworks odexed...
Click to expand...
Click to collapse
This is just something quick that I threw together after i was asked some questions regarding creating .odex files and the entire dexopt mechanism.
I searched for scripts that allowed me to do this quickly but I only found half assed ones that really didn't fit my needs.
So here's a rough preview of the script: http://pastebin.com/PKxvzMmR
How it works:
After you flash the update.zip below, you'll have both the d3xopt.sh script and the dexopt-wrapper binary. You'll then simply jump into shell
Code:
adb remount
adb shell
and type "d3xopt.sh" and it'll spout out a brief overview of the script:
Code:
Clearing dalvik-cache
Directions:
This script allows you to create .odex files
to optimize dalvik runtime
How to use:
FR - Framework
SA - System Apps
ALL - Framework/System Apps
WARNING! WARNING! WARNING!
DO NOT DEXOPT SYSTEM APPS THEN FRAMEWORK.
ALWAYS DEXOPT FRAMEWORKS THEN SYSTEM
APPLICATIONS.
WRONG ORDER WILL RESULT IN ANDROID
RUNTIME ERRORS.
WARNING! WARNING! WARNING!
Example: d3xopt.sh FR creates the .odex files for core.jar, ext.jar, framework.jar, android.policy.jar, and services.jar in boot order as to not create any problems with runtime. This follows the order set forth by Jubeh here.
I did put in a few 'checks' that will stop the script from running. Right now it's just rough. (checks for Phone.odex and core.odex before initializing, if present, it exits).
Make sure that you nandroid before you run this script, that way, when you get a spam of force closes, you don't have to cry yourself to sleep.
jubeh said:
Also, be sure that if you want to keep an app's ability to be upgraded, don't odex it (actually, don't even have it in /system, toss it to /data/app)
Click to expand...
Click to collapse
Download Here: http://www.4shared.com/file/gz0eJdeY/D3xopt.html
Gonna try it right now on jaybob's Dec17th BlackMod, Thanks Deca!
LOL @ Spam of FC's! I got them, about 30 of them, and they keep coming back! Did I do it wrong or what? It cleared Dalvik, then I tried entering cmd's but none worked, entered FR and got nothing????
OK I figured it out
d3xopt.sh FR
Looks like most if not all the Apps failed... Rebooting now
It did boot up but FC for everything Nandroiding back...
cordell12 said:
Gonna try it right now on jaybob's Dec17th BlackMod, Thanks Deca!
LOL @ Spam of FC's! I got them, about 30 of them, and they keep coming back! Did I do it wrong or what? It cleared Dalvik, then I tried entering cmd's but none worked, entered FR and got nothing????
OK I figured it out
d3xopt.sh FR
Looks like most if not all the Apps failed... Rebooting now
It did boot up but FC for everything Nandroiding back...
Click to expand...
Click to collapse
try odexing on a fresh install before installing anything, also the fc's after the script runs will happen atleast if its anything like the other odex script i used on the vogue, also clearing the dalvik cache AFTER the script runs wont do too much since the dalvik cache gets emptied by the odexing process
Also before you run the script make sure you have atleast 15% of system space left or bad things can happen, and like the Op said is more than a few words, once its odex'd you can never theme it
Sent from my HERO200 using XDA App
Yeah, I dont have much space due to fierats. The dalvik cleared first, I was just out of order on my posting I do to much with themes on phone for this. I didnt see that it wouldnt work, or cause themes in future from working. Boredom, see a new thing and I wanna try it! Anything that can help the Hero is worth a shot
Yea dzo posted a thread about it in the vogue forums, the OP here doesn't exactly say it here but its true and yea FR could cause a problem
Sent from my HERO200 using XDA App
When flashing the zip from recovery, the whole /system/bin/ directory is chmod to 0755 permissions. This causes problems with apps which need superuser permissions. It took me more than a day to figure this out...
Joskevic said:
When flashing the zip from recovery, the whole /system/bin/ directory is chmod to 0755 permissions. This causes problems with apps which need superuser permissions. It took me more than a day to figure this out...
Click to expand...
Click to collapse
herp derp, fail on my part. Took the lazy route and just recursively changed permissions on flash instead of just doing it for the individual files. My bad.
Decad3nce said:
herp derp, fail on my part. Took the lazy route and just recursively changed permissions on flash instead of just doing it for the individual files. My bad.
Click to expand...
Click to collapse
Think you can make an updated version of it to use on my nook? I think odexing one of the nightlies would be pretty awesome
Sent from my PC36100 using XDA App
thoughtlesskyle said:
Think you can make an updated version of it to use on my nook? I think odexing one of the nightlies would be pretty awesome
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I would love an update too, odexing aospCMod would be awesome.
thoughtlesskyle said:
Think you can make an updated version of it to use on my nook? I think odexing one of the nightlies would be pretty awesome
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
il Duce said:
I would love an update too, odexing aospCMod would be awesome.
Click to expand...
Click to collapse
Sure, just need to revise the odexing order for gingerbread. Stuck doing homework right now but I'll have some time later this week.
Decad3nce said:
Sure, just need to revise the odexing order for gingerbread. Stuck doing homework right now but I'll have some time later this week.
Click to expand...
Click to collapse
Also how would I run this via terminal, for some reason my nook isn't recognized via adb
Sent from my PC36100 using XDA App
thoughtlesskyle said:
Also how would I run this via terminal, for some reason my nook isn't recognized via adb
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I was just about to chip in with the same question, I've got a Flytouch 3, we also can't get into ADB via the usb port, if we could run this script as a stand alone working off a directory with the files on a PC it would be extremely useful
hey Deca, wondering if there is a way to use this for /data/app ? I have evo3D now, LOTS of apps, and it boots wicked slow :/
Hi did this ever get updated for GB ??
Very good idea, hope it can work on modded roms.
Thanks.
Dead Link?
Hi dead Link??! Need it for Dev purposes??
Decad3nce,
the link is dead, can you upload the script again ?
thanks
Any idea when a sub forum will be created for this device?
Sent from my HERO200
I was just searching for this as well.
I am interested in knowing this information as well. I am interested in buying the phone but I want to see if any developers plan on supporting it.
Ditto
Sent from my HERO200 using XDA App
In the meantime, I tried running `rageagainstthecage-arm5.bin` that seems to be common between a few phones- Droid2, Optimus S, probably others.
It runs but does not give root- the shell disconnects as normal but the phone will no longer show up as a device from 'adb device' or 'adb shell' until you reboot it.
Edit: z4root does work to root it. Install Superuser, run z4root, it will say it rooted while it didn't really work. Run it again and Superuser will ask for root perms. Permanent root function in z4root does not work.
I sure am hoping they create one. I tweeted them also about adding a Shift 4G sub forum but no one replied as of yet.
Yes please. I'm excited to see what kind of a developer community this phone gets.
Ditto, also. As the proud new owner of a Shift I turn to XDA to help me void my warranty
Sent from my PG06100
also interested in this ^_^
I agree.
Please create a Evo Shift 4G forum.
Thanks.
One of you pull system for me with adb.
Code:
adb pull /system /system
Zip the folder at C:/path-to-sdk/tools/ named system, and upload it and post it in this thread and I'll start working on some custom roms. Picking up this phone when I get the money from donations.
I will do it right now if no one has it up before I get done
http://www.digglesworth.net/evoshift/system.7z
There is the system dump from my phone. I hope this helps out.
Z4root wouldn't work for me. It just acts like its loading.
Sent from my Htc Evo Shift using XDA App
Z4root worked before but now it starts and then the phone restarts and runs really slowly until I do a battery pull.
Sent from my PG06100
I had that happen the last time I ran it (two nights ago?). I think this was after I told z4root to attempt to permanently root it. I haven't run it since and all has been fine.
Advocating this device....
Every time I try to .sh the ratc file I get permission denied. Have already chmod 0755 both root and ratc. Can we also throw a sh file in data/temp, chmod, then run it from there? Maybe?
Ill try it and try pushing busybox to temp when I get home
Sent from my SPH-D700 using XDA App
bubby323 said:
..... Picking up this phone...:
Click to expand...
Click to collapse
very good news to read
I've created three new threads in the XDA general section in an attempt to streamline all Evo Shift discussions.
Root and Development
Issues
General Discussion
I am posting this in the Developer forum, because it is still a little more than a In-experienced user can handle at the moment, and the potential to get into a bootloop is a little higher if you are not familiar with what you are doing here.
If you are at all new / uncomfortable with Android, UNIX/LINUX, this phone, or adb, then: PLEASE DON'T TRY THIS AT HOME.
If you get into a bootloop I am not responsible for this, nor is this the place to complain if that happens. You can ask for support here though if this process has caused that.
If you do get into a bootloop, then try and help me out, with providing as much info as possible with what happened (any output or screen prints are VERY helpful). I am also posting the original /system/etc/init.goldfish.sh file here AT THE BOTTOM OF THIS POST. That way if it does all go wrong it is here to grab. So don't go asking for it someplace else, or even asking here for it.
You have been warned!
Now with that out of the way, on to the good stuff.
1) Go grab some kind of bloat freeze program, from the market. I have used bloat freezer from the market with great success.
Just download and install it, don't run it just yet, if you already have, and frozen the "Device Health Application", then unfreeze it, and reboot, before doing the next step.
It is VERY important that it is done in EXACTLY this order. The reason is, if the Device Health program is frozen when you let the init script run, it will not work exactly as it should and these services will restart, since part of it is frozen when it first runs, and it all has to be disabled in the proper way, so that it can not be restarted remotely, or we will HAVE to use cron to run checks. Cron is an elaborate hack, I don't want to have to do, unless we HAVE to. If you do it in the exact order noted here, cron will not be needed and this will not restart.
2) Go get the init.goldfish.sh file from http://dl.dropbox.com/u/45576654/init.goldfish.sh.tar
push this tarball to your phone:
Code:
adb push init.goldfish.sh.tar /data/local/
End code
Now is the command line part of this hack.
Code:
adb shell
su
mount -o remount, rw /system
cd /data/local
tar -xvf init.goldfish.sh.tar
cp /system/etc/init.goldfish.sh /sdcard/init.goldfish.sh
cp ./init.goldfish.sh /system/etc/init.goldfish.sh
chown root /system/etc/init.goldfish.sh
chmod 550 /system/etc/init.goldfish.sh
mount -o remount, ro /system
reboot
End code
Now when your phone comes back up:
3) Open your bloat freezer program and freeze the "Device Health Application"
Your phone will freak out, and tell you that Device Health has stopped and it will keep asking you to FC, all you can do is pull the battery.
Put the battery back in the phone an boot it up.
Now CarrierIQ should be 100% disabled on your Atrix 2.
As promissed, here is the Original /system/etc/init.goldfish.sh file in a tarball, just use the same code above to put this back in place.
DON'T USE ROOT EXPLORER TO COPY THESE FILES INTO PLACE!!!
Original /system/etc/init.goldfish.sh file:
http://dl.dropbox.com/u/45576654/init.goldfish.sh-orig.tar
The Jedi Master strikes again!
The force is strong in this one. Seriously Jim you absolutely amaze me. You are the Linux guru.
Sent from my MB865
Train us, he will.
Sent from my MB865 using Tapatalk
LOL....
Hopefully I have not scared everyone from trying this.... I just want to let all the newbies who just got this as thier first android phone yesterday, and rooted it today, and now think that this is a good hack to try, that this is not the best thing for them just yet. It can and will bootloop the phone if you get too excited and don't follow the directions exactly... I got mine in a bootloop testing this all out, and finding the exact steps, but it was not hard to get out of, because it gets into android enough to let you adb in, if you screw up...
quick question: Why would rooting followed by freezing not work for that application? I think I did that when I got the phone. I don't see anything called Device Health in my running or installed applications.
Is carrierIQ still running on my phone? Have you got a string I can look for in the 'ps' output in the Terminal to confirm? There are 100000 processes running on these phones these days, most with cryptic names.... I miss the G1 days....
devsk said:
quick question: Why would rooting followed by freezing not work for that application? I think I did that when I got the phone. I don't see anything called Device Health in my running or installed applications.
Is carrierIQ still running on my phone? Have you got a string I can look for in the 'ps' output in the Terminal to confirm? There are 100000 processes running on these phones these days, most with cryptic names.... I miss the G1 days....
Click to expand...
Click to collapse
No just freezing the device health app just stops the collection process.
The part where you run the commands to stop the services in android are where the data can and will be sent to CIQ or AT&T, there are other things collected that att does not care much about (ATT only wants what is collected with the dev health app), and that goes straight to CIQ, so the services at the OS level are VERY important to stop. There is really not a way to see them running, but I have found that these can and will restart if my instructions are not followed 100%. To find out if CIQ is doing anything take a look on youtube there is a video that explains how to look at the system logs and see what is being collected if anything, and what is being sent out. After a lot of trial and error, I found this is the ONLY way to stop it 100%.
Hey Jim. sorry I've been out of the forums for so long on this. I was going to dig around my atrix2 and see what I could find wrt carrieriq. I got stuck on missing shell tools and you gave me some advice wrt paths and such. I was wondering if you could point me in the right direction for fixing up my env when I shell in? I also don't seem to have grep anywhere... odd.
YOu mentioned doing some of the destructive work in an emulator, and I would like to try the same thing, but I've no idea how to get the atrix2 ROM into an emulator. How did you accomplish this?
I followed the instructions above precisely and verified that my init.goldfish.sh is indeed modified correctly with the carrieriq stuff, and have suffered no ill effects. I have not, however, attempted to determine if carrieriq processes have stopped running. I did notice that after having frozen and unfrozen device.health.monitor a few times, it doesn't ever register as a running app... wonder what's up with that.
thanks for the help.
I was wondering....could this be made into a handy dandy flashable zip?
Then after flashing just freeze the app?
Sent from my MB865 using XDA App
tylercarter said:
I was wondering....could this be made into a handy dandy flashable zip?
Then after flashing just freeze the app?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Yep, working on it, should have it up for download tomorrow.... It will also be in my rom.
Jim
Sent from my MB865 using xda premium
jimbridgman said:
Yep, working on it, should have it up for download tomorrow.... It will also be in my rom.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Sent from my MB865 using xda premium
jimbridgman said:
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
NICE! you really are a jedi master!
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
jimbridgman said:
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
Click to expand...
Click to collapse
It said switch to edify scripting. Installation aborted. Something about gingerbread cwm 3. Not sure. Never see this before. I checked the zip and it has 2 updater scripts. One just has a ~ at the end. I know nothing of code but just trying to help.
Sent from my MB865 using XDA App
jimbridgman said:
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
Click to expand...
Click to collapse
Tried this. No go. Here is the error in CWM.
Installing Update...
Amend Scripting (update0script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recover.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation Aborted.
There ya go. Hope this helps.
holeshot77 said:
Tried this. No go. Here is the error in CWM.
Installing Update...
Amend Scripting (update0script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recover.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation Aborted.
There ya go. Hope this helps.
Click to expand...
Click to collapse
hes working on it. wont be much longer
Why not use the app by TrevE?
Sent from my MB865 using xda premium
1.18.12 said:
Why not use the app by TrevE?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
That does not perform the hack, only detects if it is running. The voodoo ciq detection app works much better though.
Jim
Sent from my MB865 using xda premium
I just rooted my phone, applied the hack and used Titanium Backup to freeze the Device Health App but I didn't see any FC.
Although when I opened Ti Backup, it told me that my su right are wrong. They are 4755 instead of 6755 or something like that and TiBu told me that it will fix it. I fixed it then froze the app and no FC or nothing. Phone is running fine but not sure if it worked.
Is it really necessary for the app to FC in order to show that it worked?
Should I try it all over again?
Thank you.
noobsquared said:
I just rooted my phone, applied the hack and used Titanium Backup to freeze the Device Health App but I didn't see any FC.
Although when I opened Ti Backup, it told me that my su right are wrong. They are 4755 instead of 6755 or something like that and TiBu told me that it will fix it. I fixed it then froze the app and no FC or nothing. Phone is running fine but not sure if it worked.
Is it really necessary for the app to FC in order to show that it worked?
Should I try it all over again?
Thank you.
Click to expand...
Click to collapse
Go download and install this, and it will show you if it (CarrierIQ) is active or not.
https://market.android.com/details?id=org.projectvoodoo.simplecarrieriqdetector&hl=en
Hello guys! the instructions are very easy if you do the steps correctly.
This is my first post in the development section.
First, go to market and download OTA Rootkeeper
Second, open the app, Select Create SU Backup.
Third, Select Temp UnRoot(with backup)
Fourth, uninstall Superuser, if you have superuser elite uninstall it also! and uninstall OTA Rootkeeper(dont worry it will not delete UR Backup!)
Fifth, Download and install the OTA.
After it is done and reboot, do a power cycle.
and the last step, go to market, install superuser and ota rootkeeper.
Launch OTA Rootkeeper and Select RestoreRoot, accept the superuser permission, and reboot!
AND ur back with rooted 2.3.6!
Michael
Alternate method! This is Jim's method(Thanks jim for this other way)
To do the 4ever root hack do the following:
1) open root explorer or ew file manager etc...
go to /system/bin
find the file named mount_ext3.sh
touch and hold the file name until the menu appears, go to open in text editor.
Add the following line to the VERY bottom of the file, after the fi
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
2) SAVE!!!! the file.
3) Do the OTA update.
4) You should still have root after the update, now.
Jim
Enjoy, Hope this helps!
I missed step 3 and 4 this is why it did not work for me
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
I don't know but as soon as I get home I'm going to check and see... Just got another A2 today, its going to be a good lil Guinea Pig... (insert evil grin here)
Sent from my MB865 using XDA App
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 644 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root. but if you did not do the update maually, and you used the one-click you might need to add the following line as well....
chmod 4755 /system/xbin/su
Jim
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
cant tell you, i didnt had a custom rom on it while i tried but if i am correct the update will work with stock only. wait till Iggis Pop do the test before attempting.
I just used OTA Rootkeeper normally and it worked fine for me. Backed up root, temp un-rooted, downloaded and applied the update, then restored root from OTA Rootkeeper after the update finished. I have root back just fine...
Did this not work for others?
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
tmease1 said:
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
can you tell me step by step what ou did so i can help you!
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
Michael443 said:
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
Click to expand...
Click to collapse
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
09CarreraS said:
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
Click to expand...
Click to collapse
I'm not Jim but I do have the answers to your questions!
You should flash the fkz's (sbf) files before you update, just a good idea to remove any oddities or potential problems. Also most modifications do relay on a deodexed ROM , so my guess is that it won't work with the new update yet. My personal recommendation would be to wait until lfaber06 incorperates this update into a nice little cwm flashable zip (around this weekend, or next), that will already contain root, as well as the 1 percent mod and the updated theming!
Thanks for the answer! Hey I'm from Ma as well.
well that's what i get for not reading here first. My coworker was demo-ing an app to our CEO and the update notification came in. A few minutes later he comes back and says he hit download then install when it came up. When i got it it was flashing in recovery already
extide said:
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
Click to expand...
Click to collapse
Well, this definitely bricked my phone.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
Are you sure you followed the instructions and put the files in the right directory? I havn't had any problems using this exact method as for a few others.
No way if it was done correctly that it bricked your phone.correctly can be accomplished by navigating to the proper file then copy pasting the code in order.the only thing you are modifying is superuser.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
extide said:
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
Click to expand...
Click to collapse
Not sure, I just pasted those two lines under "fi" or whatever was on the last line. Checked it. Saved it. Rebooted. Boot loop.
So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium
Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium
edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks
edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?
dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2
Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL
Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks
With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2